Ch25 - Recall The Team Skills 1. 2. 3. 4. 5. 6. Analyzing...

Info iconThis preview shows pages 1–8. 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 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
Building the Right System Ch 25. From Use Cases to Implementation Ch 26. From Use Cases to Test Cases Ch 27. Tracing Requirements Ch 28. Managing Change Ch 29 . Assessing Requirements Quality in Iterative Development
Background image of page 2
Chapter 25 From Use Cases to Implementation The Orthogonality Problem Use Cases realization in the Design Model Collaboration From Design to Implementation
Background image of page 3

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

View Full DocumentRight Arrow Icon
Mapping Requirements Directly to Design and Code
Background image of page 4
The Orthogonality Problem It's probably fairly straightforward to find, inspect, and validate the code that fulfills requirements such as "Support up to an eight-digit floating-point input parameter" However, things get a little trickier for requirements such as "The system shall handle up to 100,000 trades an hour"
Background image of page 5

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

View Full DocumentRight Arrow Icon
The Orthogonality Problem There is little correlation between the requirement and the design and implementation; they are orthogonal, or nearly so. In other words, the form of our requirements and the form of our design and implementation are different . There is no one-to-one mapping to make implementation and validation easier.
Background image of page 6
Reasons of orthogonality problem Requirements speak of real-world item, while code speaks about stacks, queues, and algorithms. Some requirements (like non-functional req.s) have
Background image of page 7

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

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 01/17/2012.

Page1 / 21

Ch25 - Recall The Team Skills 1. 2. 3. 4. 5. 6. Analyzing...

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

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