The customer is always right
The first step into writing good code is to make shure that you application works just like the customer wants it to. A good thing to remember is that the customer will never care about use cases and diagrams. They want to see your software acually doing stuff. So no matter how good your list of features and how pretty your diagrams are; if your software doesn’t do what your customer wants, those pretty diagrams aren’t worth anything.
Use case driven development
In this approach you focuse on one scenario in your use case diagram. You must code all the scenarios in one single use case.
Feature driven development
In this approach you start off with a specific feature and before moving on to the next one you complete the previous feature fully.
Which one do I like more?
I like the use case driven development more. I think the FDD is not optimal. I feel like most of the time, the features are all inter-connected. This makes it difficult to code. Of course, if your features are all independent from one another there’s no problem. What I think it’s that most of the time this is not the case. Maybe a few features are independent. But in my short experience the difficult and important features are always dependant on one another.
Cellar Door Blog 