Lecture 17 review of requirements management

Microsoft PowerPoint REQ17 ppt Requirements Engineering John Vu Senior Scientist Institute for Software Research Carnegie Mellon University Review of Requirements Management 2© John Vu CMU ISR Review Requirements Management Always continually assess your requirements engineering practices once the requirement process begins, by periodically stopping your work to examine practices and deliverables to indentify improvement opportunities Ask team members which requirements practices work and which.

Requirements Engineering

John Vu

Senior Scientist

Institute for Software Research

Carnegie Mellon University

Review of Requirements

Management

Review Requirements Management

engineering practices once the requirement

process begins, by periodically stopping your

work to examine practices and deliverables to

indentify improvement opportunities

work and which ones do not work, making

modifications to the process

end of each iteration to ensure quality work and

additional improvement opportunities

Software Is A Risky Business

The Effect On Business

Root Causes

Primary Root Cause - 1

Primary Root Cause - 2

A Team Efforts

Requirements Models

ƒ Requirements models can:

technical and non-technical people

the requirements

requirements

textual description and visual models to clarify

requirements

Model Progression

Product

Model Progression

Product

Analyze System Behavior

Analysis & Design - 1

Model

Analysis & Design - 2

Model Progression: Test

Requirements Engineering

ƒ A systematic approach to eliciting,

organizing, and documenting the

requirements of the system, and a process

that manages the changing requirements

of the system.

What Are We Managing?

What Do We Need?

ƒ In order to manage requirements we

need:

• Skills to elicit requirements from users and

stakeholders of the system

requirements

the requirements

Skills

Methods & Tools

Defining A Process

Organizing Requirements

Establishing Requirements Traceability

Change History

ƒ As requirements evolve, understand what

changed, when and why.

ƒ Version requirements and their associated

design and implementation artifacts.

ƒ Allow for change to be managed

incrementally.

Tools & Tool Integration

ƒ Organizing and establishing traceability

links requires some form of tool support.

ƒ Tools may be as simple as Excel

spreadsheets and Word documents.

ƒ But, projects of medium and large size will

be better served by more integrated tool

support.

Documenting Requirements

ƒ Use Case

ƒ Models

ƒ Supplementary Specifications

ƒ A Use Case describes the sequence of

actions a system performed that yields

observable results of value to a particular

actor.

Use Case

Models

Supplementary Specification

ƒ Capture the system requirements that are

not readily captured in behavioral

requirements artifacts, such as use cases.

To Sum Up: The Problem

To Sum Up: The Opportunity

ƒ When your software requirements are

complete and accurate and you catch

requirements errors and omissions early in

the project then you have:

and within budget

Questions & Answers