Managing Change and Quality

1
Managing Change and Quality

• Sriram Mohan

2
Outline

• Managing Requirements
• Assessing Requirements Quality

3
Factors for Change

• External
• Internal
• Unofficial sources contributed up to half of the
  total scope of the project

4
Managing Change Primary Questions

• How do you capture change requests?
• How do you respond to these (individually
  overall)?
• How does this tie-in with tracing requirements?

5
A Process for Managing Change
Step 1 Recognize that change is inevitable, and
plan for it
6
A Process for Managing Change

• Step 2 Baseline the requirements
• This means they are signed-off on, and
• From then on, they fall under change control
  see below

• Step 3 Establish a single channel to control
  change
• No ad hoc additions
• No ad hoc fixes, either

7
A Process for Managing Change
In ? this big picture, you especially need to
know what release management ? is!
Step 4 Use a Change Control System to Capture
ChangesStep 5 Manage Change Hierarchically
Figure on middle right from http//www.debian.org/
vote/2002/platforms/raphael
8
Follow the link

• There is a dependency between the various
  artifacts involved in requirements mgmt
• Follow the chain and make sure that the change is
  propagated

9
Outline

• Managing Requirements
• Assessing Requirements Quality

10
Products vs. Processes

• Organizations that produce high-quality products
  invest in high-quality processes.
• Product quality can be measured through testing.
• How can we measure process quality?

11
Review Methods

• Informal
• Ask a peer to read and give comments
• Formal
• Ask a peer to prepare for review
• Record and report results of review
• Active
• Interrogate reviewer

12
Checklists

• Look for anticipated defects
• Some defects apply to almost all artifacts
• Does the artifact exist?
• Some defects are artifact-specific
• Have you identified all stakeholders?

13
Problem Statement Checklist

1. Has a problem statement been drafted?
2. Is it written in an easy-to-understand way?
3. Does the team understand it?
4. Has it been circulated for agreement to the key
   stakeholders, including management?
5. Do the team members have agreement that this is
   the problem they are trying to solve?

14
Supplementary Specification Checklist (1/2)

1. Have you established an appropriate template?
2. Are all non-functional requirements included in
   the supplementary specification?
3. Have requirements for usability, reliability,
   performance and supportability been captured?

15
Supplementary Specification Checklist (2/2)

1. Have design constraints been identified?
2. Have supplementary requirements been linked to
   use cases where appropriate?