Requirements Engineering

(1)

Requirements Engineering

and

_Management

for Software

_Development

Projects

Foreword

_by

Tom

Gilb

(2)

1 Introduction to

_{Requirements Engineering}

and

_{Management....}

1 1.1 What is a

"Requirement"

1

1.2

_{Requirements Management}

4

1.3

_{Requirements Management}

Scenarios 6 1.4

_Agencies

_Responsible

for

_{Managing Requirements}

7

1.5

_Approaches

to

_{Requirements Management}

8

1.6

_{Requirements Engineering}

9

1.7

_Topics

_Proposed

tobe Covered in this Book 10

2

_{Understanding Requirements}

13

2.1 Classification of

_Requirements

13 2.2 Classification of

_Requirements

Based

on

Functionality

Considerations 13 2.3 Classification of

_Requirements

Based

on Product Construction Considerations 18 2.4 Classification of

_Requirements

Based

on Source of

_Requirements

21

2.5 Levels of

_Requirements

23

2.6 Definition of

_Requirements

in the Context

of Software

_Development

24 2.7 Evolutionof

_Requirements

25

3 Elicitation and

_Gathering

of

_Requirements

33

3.1 Introduction 33

3.2 Elicitation of

_Requirements

34

3.2.1 Personal Interviews 35 3.2.2 Customer/Market

_Surveys

40

3.2.3

Questionnaires

41

3.2.4 Observation 42

3.2.5 Demonstration of Product

_Prototypes

42

(3)

3.2.6 ProductDemonstrations 43

3.2.7

Brainstorming

44

3.3

_{Gathering Requirements}

44 3.4 Elicitation and

_Gathering

in

_Agile

Projects

_Gathering

in COTS Product

Implementation

_Gathering

in

_{Testing Projects}

_Gathering

in Software

Maintenance

Projects

49

3.8 Elicitation and

Gathering

in Real Time Software

Development

Projects

50

3.9 Elicitation or

Gathering?

50

3.10 Deliverables of Elicitation and

_Gathering

51 3.11 Pitfalls in

Requirements

Elicitation and

_Gathering

52

3.12 Final Words 54

4

_Requirements

Analysis

55 4.1 Introduction to

_Analysis

55

4.2

_Analysis

of the Information Collected in the Elicitation

and

_Gathering

57

4.3

_Resolving

the Issues that

_Cropped

_up

_During

the

_Analysis

65 4.4 Deliverables of

_Requirements

_Analysis

Phase 65

4.5 Final Words 65

5 Establishment of

_Requirements

67 5.1 Introduction to Establishment of

_Requirements

67

5.2 Documentation 68

5.2.1 User

_{Requirements Specification}

69 5.2.2 Software

_Requirements

_{Specification}

70

5.3

Quality

Control of the Documents 75

5.4

_{Obtaining Approvals}

80

5.5

_{Configuration Management}

81

5.6 Establishment of

_Requirements

in COTS Product

Implementation Projects

82

5.6.1

_Gaps

_Analysis

Document 84

5.6.2 SOW Document 84

_Requirements

in Software

Maintenance

_Projects

86 5.8 Establishment of

_Requirements

in

_{Migration, Porting}

and Conversion

_Projects

87 5.9 Establishment of

_Requirements

in

_Agile

(4)

6

_Quality

Assurancein

_Requirements

_Management

91 6.1 Introduction to

_Quality

Assurance 91 6.2

_Quality

Assurance in the Context of

_Requirements

Engineering

and

_Management

93

6.2.1

Process,

Standards and Guidelines 93 6.2.2

_{Right People}

with

_{Right Training}

95

6.2.3

_Quality

Control 97

6.2.4 Measurement and

_Analysis

97

6.2.5

_Project

Postmortem 98

6.3 Verification 98

6.3.1 Peer Reviews 99

6.3.2

_Managerial

Reviews 102

6.3.3 Best Practices and Pitfalls in Verification 102

6.4 Validation 103

6.4.1

_{Brainstorming}

103

6.4.2

Storyboarding

104

6.4.3

_Prototyping

104

6.4.4

_Expert

Review 104

6.4.5 End User Review 105 6.4.6 Feedback Mechanism from Validation 105

6.5 Determination of

_{Applicable Quality}

Control Activities 105

7

_Planning

for

_{Requirements Management}

107

7.1 Introduction to

_Planning

107 7.2 Definition of

_Planning

107

7.3

_Planning

for

_{Requirements Management}

108

7.4 To Documentor Notto Document? 109

7.5 Different

_Project

Plans 110

7.6

_Planning

for

_{Requirements Management}

in

_Projects

Ill

7.6.1

_Requirements

Elicitation and

_Gathering

Ill

7.6.2

_{Requirements Analysis}

112

7.6.3

_Requirements

Establishment 112 7.6.4

_{Requirements Change}

Control and

_{Management...}

113 7.6.5

_{Requirements Tracing, Tracking}

and

_Reporting.

... 113

7.6.6 Measurement and Metrics 114 7.6.7 Formatsand

Templates

for

_Planning

114

7.7 Best Practices and Pitfalls in

_Planning

114

8

_{Requirements Change Management}

117

8.1 Introduction 117

8.2 Communication of

_Changes

118

8.3

_Origination

of

_Changes

119

8.4

_{Change Request}

Resolution 121

(5)

8.6 CRR 125

8.7

Progress/Status Reporting

of CRs 126

8.8

_Handling

the

_Impact

of CRs 126

8.9 Measurement andMetrics of

_{Change Management}

127

9

_{Requirements Tracing, Tracking}

and

_Reporting

129

9.2

_{Requirements Traceability}

129

9.3 Need for

_{Requirements Traceability}

130 9.4 Mechanisms for

_{Tracing Requirements}

132

9.5 When Should We Tracethe

_{Requirements?}

134

9.6

_Tracking

of

_Requirements

134 9.7

_{Requirements Reporting}

135 9.8 Reconciliation of

_Requirements

136

10 Measurement and Metrics 139

10.2 Measurement and Metrics 139 10.3 MetricsRelevant to

_{Requirements Engineering}

and

Management

141

10.3.1

Productivity

Metrics 143 10.3.2

_{Change Request}

Metrics 145

10.3.3

Quality

Metrics 147

10.3.4 Relative Effort Metrics 149

10.3.5 Schedule Metrics 151

10.4

_Summary

of Metrics 152

11 Roles and

_{Responsibilities}

inREM 153

11.2 Role of the

_Organization

153

11.2.1

_Organization

154

11.2.2 Staff 155

11.2.3 Process 159

11.2.4

_Quality

Assurance 161

11.2.5

_Training

161

11.2.6

_Recognition

and Rewards 162 11.3 Role of the Individuals 163 11.3.1

_{Business/System Analysts}

163 11.3.2

_Quality

Control 164 11.3.3

_{Project Manager}

165 11.3.4 Process Definition and

_{Improvement Group}

166 11.3.5 Senior

_Management

167

(6)

12

_{Requirements Management Through}

SDLC 169

12.2

_Pre-Project

Phase ₁₇₀

12.3 RM in

_Requirements

Phase ofSDLC 171

12.4 Software

_Design

171

12.5 Construction 172

12.6

_Testing

172

12.7

_Acceptance

_Testing

173

12.8 Installation and

_{Commissioning}

174

12.9 RM

_Through

SDLC 175 13 Tools and

_Techniques

for

_Requirements

_Engineering

and

_Management

₁₇₇

13.2 Structured

_{Systems Analysis}

and

_Design

Method 177 13.2.1

_Feasibility

_Study

179

13.2.2

_{Requirements Analysis}

and

_{Specification}

179 13.2.3

_High

Level

_Design

179

13.2.4 Low Level

_Design

₁₇₉

13.2.5 Construction ₁₇₉

13.2.6

_Testing

180

13.2.7

_Delivery

and

_{Implementation}

180 13.2.8 Software Maintenance 180

13.2.9

_Requirements

_Engineering

and

_Management

inSSADM 181

13.2.10 ER

_Diagrams

181

13.2.11 Data Flow

_Diagrams

₁₈₃

13.2.12 Context

_Diagram

185

13.2.13 Structure Chart 186

13.3 IEEE Software

_Engineering

Standards 187

13.4

_Object

Oriented

_Methodology

188

13.5 Unified

_Modeling

_Language

191 13.5.1 Class

_Diagrams

191

13.5.2 Use Cases ₁₉₂

13.5.3

_{Sequence Diagrams}

196

13.5.4 Statecharts 196

13.5.5

_{Activity Diagrams}

196 13.5.6

_{Component Diagrams}

197

13.5.7

_Deployment

_Diagrams

198 13.5.8 Final Words on UML ₁₉₈

13.6

_Agile

Methods 199

13.7

_Planguage

₂₀₀

13.8 Final Words on Tools and

Techniques

in

Requirements

(7)

14 Pitfalls and Best Practices in

_{Requirements Engineering}

and

_Management

203

14.2 BestPractices and Pitfalls atthe

_{Organizational}

Level 203 14.2.1

_Approach

to

_Requirements

_Engineering

and

_Management

204

14.2.2 Provision of Resources 205

14.2.3

Training

and

_Updating

of Skills 206 14.2.4 Definition and

_Improvement

of Process 206 14.2.5 Motivation and Morale of the Resources 207 14.2.6

_Quality

Assurance 209

14.2.7

_{Knowledge Repository}

210 14.3

_Project

LevelPitfalls and Best Practices 211

14.3.1

_Planning

211

14.3.2

_Preparation

for Elicitation and

_Gathering

of

_Requirements

212

14.3.3

_{Misunderstanding}

About

_Requirements

212 14.3.4

_{Vague Requirements}

212 14.3.5

_Modeling

Issues 213

14.3.6 Prioritization of

_Requirements

213 14.3.7

_{Change Management}

213 14.3.8

_Tracing

and

_Tracking

of

_Requirements

214

14.3.9

_Supervision

214

14.3.10

_Project

Postmortem 214

14.4 Final Words of Pitfalls and Best Practices 215

15 REM in

_{Agile Projects}

217

15.2 Extreme

_Programming

219

15.3 Scrum 220

15.4

_Dynamic

_Systems

_Development

Method 221

15.5 Feature Driven

_Development

222

15.6 Test Driven

_Development

223 15.7

_Adaptive

Software

_Development

224

15.8 RUP and AUP 225

15.9 Kanban 226

15.10

_Crystal

Clear 228

_Requirements

in

_{Agile Projects}

229 15.12

_Tracing

and

_Progress

_Monitoring

of

_Requirements

231

(8)

Appendix

A: Documentation Guidelines 233

Appendix

B:

_Planguage

249

About the Author 261