1 / 13

Requirement Specification Fall 2005

This lesson focuses on defining requirements in software development using use case methodologies. Participants will learn how to analyze a situation and draft a straightforward requirement specification for a smaller software system. The lesson covers object-oriented techniques and illustrates how to create use case diagrams. Key resources include excerpts from Graig Larman's "Applying UML and Patterns". By the end of this lesson, students will be equipped to understand primary actors, goals, system boundaries, and the context for writing effective use cases.

min
Télécharger la présentation

Requirement Specification Fall 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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

More Related