Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

20
  • 3
    Can you provide a source or definition for "traditional software development"? Who used it and what was the context? Commented Jul 18, 2017 at 16:39
  • 2
    My point is, there are lots of other methods for building software, and not all are mutually exclusive. Rapid Application Development, Unified Process, Extreme Programming, PSP/TSP, Scrum, TDD, BDD, FDD, DDD, model-driven development. Some can be paired together nicely. Others can't. I'm not aware of a single, common "traditional software development" that could be referred to. Commented Jul 18, 2017 at 16:43
  • 4
    @johnny: It's not that developers have no idea what the customer wants... it's that the customer has no idea what they want. The way you solve that is by using iterative practices, where you build small prototypes, get feedback, make suggestions, modify the prototype, and repeat this process until the prototype matches the customer's expectations. Commented Jul 18, 2017 at 18:40
  • 4
    As to your word definitions, I strongly suspect that the commentators are using "traditional software development" as a euphemism for "not my latest and greatest software development flavor of the week," in which case you're chasing a red herring. Commented Jul 18, 2017 at 18:42
  • 2
    Dan North is using "traditional software development" as a contrast to "agile software development" and has no corollary with behavior driven development. You can do BDD with waterfall or agile. BDD is a style of writing tests, essentially. Commented Jul 18, 2017 at 19:34