Ch22 - Recall The Team Skills 1. 2. 3. 4. 5. Analyzing the...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System Definition 1. Software Requirements: a more rigorous look 2. Refining the Use cases 3. Developing the Supplementary Specification 4. On Ambiguity and Specificity 5. Technical Methods for Specifying Requirements 6. Building the Right System
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 22 Developing the Supplementary Specification Role of the Supplementary Specification Nonfunctional Requirements Design Constraints Linking the Supplementary Spec. to the Use Cases
Background image of page 2
The Role of the Supplementary Specification There are many requirements can’t be implemented as in the use-case model. Example: "The application must run on Windows XP" So there is a need for supplementary specification . Supplementary: because we assume the use- case format will contain most of the functional requirements for the system, and we'll supplement the use-case model with these additional requirements.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Exploring Nonfunctional Requirements Nonfunctional requirements can be organized into four categories: Usability Reliability Performance Supportability
Background image of page 4
Usability ( ease of use ) 1. Specify the required training time for a user to become minimally productive : able to accomplish simple tasks) and operationally productive: able to accomplish normal day- to-day tasks). 1. Specify measurable task times for typical tasks or transactions that the end user will be carrying out. 2. Compare the usability of the new system with other state-of-the-art systems that the user community knows and likes.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Usability ( ease of use ) 4. Specify the existence and required features of online help systems, wizards, tool tips, user
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 23

Ch22 - Recall The Team Skills 1. 2. 3. 4. 5. Analyzing the...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online