Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.

transcript

Requirements Management and Requirements Management and Changes Changes

Copyright, 2003 © Jerzy R. Nawrocki

Jerzy.Nawrocki@put.poznan.pl

www.cs.put.poznan.pl/jnawrocki/require/

Requirements EngineeringRequirements Engineering

Lecture Lecture 1010

J. Nawrocki, Requirements Management ..

IntroductionIntroduction

SCI = “Information that is created as part of the software engineering process.” [R.Pressman]

Types of SCIs:• computer programs (source code or

exec)• documents (also requirem. specification)• data (e.g. test cases)

Soft. Configuration Item (SCI)

if (a > b) a-= b;

A specification or product that has been formally reviewed and agreed upon,

that thereafter serves as the basis for further development, and

that can be changed only through formal change control procedures.

Baseline [IEEE 610-1990]

Specification

DesignCode

Test cases

Base-line

Baseline or SCI?

Engineering

Change it!

Change control

Baseline library

Baseline

Soft. Configuration Control Board

SCCBSCCB

Authorises:• the establishment of software baselines,• the identification of configuration items,• the creation of products from the baseline

library.Represents the interests of the project

manager and all groups affected by changes to baselines.

Reviews and authorises changes.

CMM & Change ManagementCMM & Change Management

Ac5. Change requests & problem reports for all SCIs are

• initiated, • recorded, • reviewed,• approved, and• trackedaccording to a documented procedure.

Remove2nd floor!

Change control

Change request

User S.C. Manager

Change request

Developer

Change report

Deci-sion

Change control

Change request

User S.C. Manager

Change request

Developer

Change report

Deci-sion

Change order

P. Manager

CMM & Change ManagementCMM & Change ManagementChange request

Change request number: ............................Sender: .........................................................Sender’s e-mail: ...........................................Date: ..............................................................Urgency: ................. Importance: ..............Description: ............................................................................................................................................................................................... Evaluator: .....................................................Evaluate by: ........... Type (in/external) .......

CMM & Change ManagementCMM & Change ManagementChange report

Change request number: ..........................Evaluator: ...................................................Evaluator’s e-mail: .....................................Date: ............................................................Urgency: ................ Importance: ..............Is the change justifiable? ..........................Main risk factors: .......................................Possible implementor: ..............................Change implement. effort (expect): .........Change evaluation effort (actual): ............

Overview of RE guidelinesOverview of RE guidelines

The requirements documentRequirements elicitationReqs analysis & negotiationDescribing requirementsSystem modellingRequirements validationRequirements managementRE for critical systems

Basic Interm Adv

86543442

36-6213333

21-11--124

Basic guidelinesBasic guidelines

Requirements management

• Uniquely identify each requirement

• Define policies for requirements Define policies for requirements managementmanagement

Requirements Management Policy

Goal: Understand the requirements

Obligatory practices:

1. Define specialised terms using the template available at www.cs.put.poznan...

• Define traceability policiesDefine traceability policies

Traceability policy

• Traceability information• Who is responsible

Problems

Visions

Requirements (FURPS)

Acceptance test cases

User documentation

Design

• Define traceability policiesDefine traceability policies• Maintain a traceability manual

Intermediate guidelinesIntermediate guidelines

• Use a database to manage requirements

• Define change management policies

• Identify global system requirements

Advanced guidelinesAdvanced guidelines

• Identify volatile requirements• Record rejected requirements

SummarySummary

CMM approach to changesRequirements management

practices

Quality assessmentQuality assessment

1. What is your general impression? (1 - 6)

2. Was it too slow or too fast?3. What important did you learn

during the lecture?4. What to improve and how?

Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.

Documents