Head First Object Oriented Analysis & Design (OOAD) Chapter 02
This is the second 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 second chapter, not sure if any copyright issues are there.
- Requirements are things your system must do to work correctly.
- Your initial requirements usually come from your customer.
- To make sure you have a good requirements, you should develop use cases for your system.
- Use Cases details exactly what your system should do.
- A use case has a single goal, but can have multiple paths to reach that goal.
- A good use case has a starting and stopping condition, an external initiator, and clear value to the user.
- A use case is a simply a story about how your system works.
- You will have at least one use case for each goal that your system must accomplish.
- After your use cases are complete, you can refine and add to your requirements.
- A requirements list that makes all your use cases possible is a good set of requirements.
- Your system must work in the real world, not just when everything goes as you expect it to.
- When things go wrong, your system must have alternate paths to reach the system’s goals.