Development is serial in the large. You can see this in the fact that the left side of the diagram are mostly requirements artifacts, that as you proceed towards the right that the artifacts focus on analysis, then design, then finally code.
Development is iterative in the small. On any given day I am likely to work on several artifacts and will iterate back and forth between them.
This diagram is arguably a high-level meta model relating development artifacts that implies traceability strategies for your team.
What I’m really talking about is “modeling normalization” — using each artifact for what it is good for and referring to information in other models (e.g. a use case refers to a business rule) but not copying that information. This approach ensures highly cohesive models that are loosely coupled to one another.
Figure 2, taken from the article Development Phases Examined, shows the various categories of models and how you iterate back and forth between them as needed. It’s basically an update, and generalization, of Figure 1.
Figure 2. Categories of models.
Printing This Article
If you’re trying to print this, you’ll likely need to print it in landscape mode.