Diagram cookbook
- 1. Requirements and diagrams cookbook
- 2. Requirements Very important! Project is done when requirements are fullfilled. Functional requirements What should the system be able to do? Non-functional requirements Extra stuff: Performance, company imposed constraints and other stuff. Be prepared for the question ”Why is that a requirement?”
- 3. Use case diagrams Shows how users wil interact with the system.
- 4. Do the diagrams See next slide
- 5. 5-10 use cases per diagram Compare the use case diagrams with the requirements. Do the diagrams cover the requirements?
- 6. Use case diagram cookbook Decide on Use case diagram subject
- 8. What should each actor be able to do with the system? This is the use cases .
- 9. Are there use cases that the actors cannot do directly? Use <<include>> or <<extends>>
- 10. Activity diagrams Flowchart of what the system does External view! Use messages to describe details
- 11. Activity diagram cookbook Decide the scope and title of the diagram Decide on start point and end point. Go through the steps needed from start to end. Any decisions ? (Label all exit paths)
- 12. Actions and activities has verbs in their names. Check that decision nodes end in merge nodes , and forks end in joins
- 13. References to the book “System analysis and design with UML version 2.0” by A. Dennis [Wiley 2005]
- 14. Requirements: Chapter 5
- 15. Use case diagrams: Chapter 6 Notation on page 179 Activity diagrams: Chapter 6 Notation on page 166