Requirement Specification Fall 2005

1. Requirement SpecificationFall 2005 by Eva Trosborg Agenda Requirement definition through use cases

2. 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. Sources to this lesson • Graig Larman; Applying UML and Patterns Chapter 4 - 7

4. Fig. 5.1

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

6. Fig. 6.2 Primary actors and goals at different system boundaries p86

7. Fig. 6.3 Partial use case context diagram p90

8. Fig. 6.4 Notation suggestions p91

9. Fig. 6.5 Alternate actor notation p91

10. 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. Fig. 6.7 process and setting context for writing use cases p97

12. Fig. 7.1

13. 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.dk