A01BestPracticesPart2-class

A01BestPracticesPart2-class - Unified Software Practices v...

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

View Full Document Right Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon

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

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

Unformatted text preview: Unified Software Practices v 5.0 - D Copyright 1998 Rational Software, all rights reserved 1 Practice 2: Manage Requirements Control Changes Develop Iteratively Use Component Architectures Manage Manage Requirements Requirements Model Visually Verify Quality A report by Standish Group cites forty percent of software projects fail. This failure is attributed to: poor requirements management ; ((eliciting) capturing, (documenting) modeling, verification; prototyping; agreeing w/customer on how changes will be handled, ...) incorrect definition of requirements from the start of the project; and (feedback, verification) poor requirements management throughout the development lifecycle. (handling Change!!!) (Source: Chaos Report, http://www.standishgroup.com). Unified Software Practices v 5.0 - D Copyright 1998 Rational Software, all rights reserved 2 Requirements are dynamic -- Expect them to change during software development Change cannot be stopped, but it can be managed!! Practice 2: Manage Requirements Elicit, organize, and document Elicit, organize, and document required functionality and required functionality and constraints constraints Evaluate changes and determine Evaluate changes and determine their impact their impact Track and document tradeoffs and Track and document tradeoffs and decisions decisions Getting comprehensive system Getting comprehensive system requirements is a requirements is a continuous continuous process! process! Obtaining a complete, exhaustive Obtaining a complete, exhaustive set of requirements prior to set of requirements prior to development is impossible! development is impossible! Unified Software Practices v 5.0 - D Copyright 1998 Rational Software, all rights reserved 3 Definitions: Requirements and Their Management A A requirement requirement is a condition or capability to is a condition or capability to which the system must conform which the system must conform Requirements management Requirements management is a systematic is a systematic approach to approach to Eliciting, organizing, and documenting the requirements of the system, and Establishing and maintaining agreement between the customer/user and the project team on the changing requirements of the system Requirements specify what the system must Requirements specify what the system must do - not how! do - not how! Requirements Management will be successful Requirements Management will be successful only if it allows for uncertainty early in only if it allows for uncertainty early in development development Requirements Management must ensure Requirements Management must ensure Unified Software Practices v 5.0 - D Copyright 1998 Rational Software, all rights reserved 4 Agreement on What the System Should Do The Goal Surrogate Goal Requirements Verification Customer User Community Requirements System To Be Built Adapted from Al Davis Must write down the requirements Form must be understandable by both user and developer Serve as criteria for testing and accepting system Unified Software Practices v 5.0 - DUnified Software Practices v 5....
View Full Document

Page1 / 21

A01BestPracticesPart2-class - Unified Software Practices v...

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

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