Head First Object Oriented Analysis & Design (OOAD) Chapter 03
This is the third Chapter learning of Head First Object Oriented Analysis & Design (OOAD) by Bertt Mclaughlin,Gary Pollice and David West
This markdown file is my notes for the third chapter, not sure if any copyright issues are there.
- Requirements will always change as a project progresses.
- When requirements change, your system has to evolve to handle the new requirements.
- When your system needs to work in a new or different way, begin by updating your use case.
- A scenario is a single path through a use case, from start to finish.
- A single use case can have multiple scenarios, as long as each scenario has the same customer goal.
- Alternate paths can be steps that occur only some of the time, or provide completely different paths through parts of a use case.
- If a step is optional in how a system works, or a step provides an alternate path through a system, use numbered sub-steps.
- You should almost always try to avoid duplicate code. Its a maintenance nightmare, and usually points to problems in how you’ve designed your system.