1. Eva TrosborgSlide no.: 1Requirement Specification Requirement Specification Fall 2005 Agenda Requirement definition through use cases by Eva Trosborg

2. Slide no.: 2Requirement Specification After this lesson you should : Be able to analyze a given situation and write a simple requirement specification for a smaller software system using object oriented techniques such as use case diagrams

3. Eva TrosborgSlide no.: 3Requirement Specification Sources to this lesson Graig Larman; Applying UML and Patterns Chapter 4 - 7

4. Eva TrosborgSlide no.: 4Requirement Specification Fig. 5.1

5. Eva TrosborgSlide no.: 5Requirement Specification Fig. 6.1 Scenarie = use case instance = one specific path through the use case Requirements Use Case cover all possible scenario’s p63

6. Eva TrosborgSlide no.: 6Requirement Specification Fig. 6.2 Primary actors and goals at different system boundaries p86

7. Eva TrosborgSlide no.: 7Requirement Specification Fig. 6.3 Partial use case context diagram p90

8. Eva TrosborgSlide no.: 8Requirement Specification Fig. 6.4 Notation suggestions p91

9. Eva TrosborgSlide no.: 9Requirement Specification Fig. 6.5 Alternate actor notation p91

10. Eva TrosborgSlide no.: 10Requirement Specification Fig. 6.6 Use case diagram (“context diagram”) for Monopoly system p94 Table 6.1 Sample requirements effort across the early iterations; not a recipe p96 Your project??

11. Eva TrosborgSlide no.: 11Requirement Specification Fig. 6.7 process and setting context for writing use cases p97

12. Eva TrosborgSlide no.: 12Requirement Specification Fig. 7.1

13. Eva TrosborgSlide no.: 13Requirement Specification Assignment for the 13. September Project establishment. Preparing the presentation of the different project roles, Dream group “agreement”. Slides to be sent to trosborg@itu.dktrosborg@itu.dk