This document discusses requirements management (RM) and how to structure requirements and use RM practices using the Contour tool as an example. It describes customizing Contour for different development approaches like project-oriented and continuous development. It covers setting up a requirements structure with folders and types, attributes, representation as rich text, and linking requirements to testing. Workflow monitoring, dashboards, release management, and ensuring requirements-based testing are also discussed. Principles discussed are customizing RM tools and integrating processes with tool practices.

1. Requirements strukturieren und nutzen
Requirements-Praktiken am Beispiel Contour
Handout-Version
Dr. Andreas Birk und Gerald Heller, Software.Process.Management
22. März 2013, Webinar der QA Systems Akademie

2. Gestatten ...
2
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller
22. März 2013 Copyright © 2013, Software.Process.Management

3. Requirements Management (RM) Is …
[Requirements management is] a systematic
approach to eliciting, organizing, and documenting
the requirements of the system, and a process that
establishes and maintains agreement between the
customer and the project team on the changing
requirements of the system.
[Leffingwell & Widrig, 2003]
22. März 2013 Copyright © 2013, Software.Process.Management 3

4. RM Is Different: Typical Approaches to RM
22. März 2013 Copyright © 2013, Software.Process.Management 4
Product
Product Product Product
Product Product Product
Project-oriented
development
Continuous product
development
Change request driven
development
Combinations and blends

5. RM in the Development Lifecycle
22. März 2013 Copyright © 2013, Software.Process.Management 5
Define Business
Goals and Context
Develop
Requirements
Specification
Develop
Architectural
Design
Coding and
Developer
Testing
Integration
and Testing
Requirements Engineering
Requirements Management
Central
Requirements
Repository
Manage Change
Requests and
Defect Reports
Note: This is a view of software engineering activities in a logical
sequence. During the development lifecycle, these activities are
performed repeatedly and often concurrently.

6. RM Is The Hub of Software Development
22. März 2013 Copyright © 2013, Software.Process.Management 6
RM
Manage
Project
Define
Business
Goals &
Context
Define
Requirements
Specification
Develop
Architectural
Design
Coding and
Developer
Testing
Integration
and Testing
Manage
Change
Requests and
Defect
Reports
Manage
Quality

7. What Activities Shall RM Tools Support?
Define and structure requirements
Communicate and discuss requirements
Prioritize requirements
Maintain status on requirements
Track changes of requirements
Version requirements
Trace relationships between requirements and other development artefacts
Source: http://makingofsoftware.com/2013/rm-tools-what-are-they-anyway
22. März 2013 Copyright © 2013, Software.Process.Management 7

8. Features of Modern RM Tools:
Example JAMA Contour
22. März 2013 Copyright © 2013, Software.Process.Management 8

9. Customize Jama Contour for RM in
Project-Oriented Development
Requirements Structure
Requirements Attributes
User Roles & Permissions
Filtering & Reporting
Workflow Design
…
22. März 2013 Copyright © 2013, Software.Process.Management 9
Product

10. Requirements Structure
22. März 2013 Copyright © 2013, Software.Process.Management 10
Volere:http://www.volere.co.uk
S.RobertsonandJ.Robertson:Masteringthe
requirementsprocess(3rdEd.),Addison-Wesley,2012.
Establish suitable
requirements structure,
based on standards or
good practice
Examples:
 IEEE Std. 830-1998
 Volere Template
Project Drivers
1. The Purpose of the Project
2. The Stakeholders
Project Constraints
3. Mandated Constraints
4. Naming Conventions and Terminology
5. Relevant Facts and Assumptions
Functional Requirements
6. The Scope of the Work
7. Business Data Model & Data Dictionary
8. The Scope of the Product
9. Functional Requirements
Non-functional Requirements
10. Look and Feel Requirements
11. Usability and Humanity Requirements
12. Performance Requirements
13. Operational and Environmental Requirements
14. Maintainability and Support Requirements
15. Security Requirements
16. Cultural and Political Requirements
17. Legal Requirements
Project Issues
18. Open Issues
19. Off-the-Shelf Solutions
20. New Problems
21. Tasks
22. Migration to the New Product
23. Risks
24. Costs
25. User Documentation and Training
26. Waiting Room
27. Ideas for Solutions

11. Requirements
Structure in Contour
Use the following concepts of
Jama Contour:
 Folders
 Requirements Types
22. März 2013 Copyright © 2013, Software.Process.Management 11

12. Requirements
Structure in Contour
Use the following concepts of
Jama Contour:
 Folders
 Requirements Types
22. März 2013 Copyright © 2013, Software.Process.Management 12

13. Requirements Attributes
Example: Volere Shell
22. März 2013 Copyright © 2013, Software.Process.Management 13
Volere:http://www.volere.co.uk
S.RobertsonandJ.Robertson:Masteringthe
requirementsprocess(3rdEd.),Addison-Wesley,2012.

14. Requirements Attributes in Jama Contour
22. März 2013 Copyright © 2013, Software.Process.Management 14

15. Representation: Rich Text Requirements
22. März 2013 Copyright © 2013, Software.Process.Management 15

16. Volere: Structure, Content, and Process
22. März 2013 Copyright © 2013, Software.Process.Management 16
Project Drivers
1. The Purpose of the Project
2. The Stakeholders
Project Constraints
3. Mandated Constraints
4. Naming Conventions and Terminology
5. Relevant Facts and Assumptions
Functional Requirements
6. The Scope of the Work
7. Business Data Model & Data Dictionary
8. The Scope of the Product
9. Functional Requirements
Non-functional Requirements
10. Look and Feel Requirements
11. Usability and Humanity Requirements
12. Performance Requirements
13. Operational and Environmental Requirements
14. Maintainability and Support Requirements
15. Security Requirements
16. Cultural and Political Requirements
17. Legal Requirements
Project Issues
18. Open Issues
19. Off-the-Shelf Solutions
20. New Problems
21. Tasks
22. Migration to the New Product
23. Risks
24. Costs
25. User Documentation and Training
26. Waiting Room
27. Ideas for Solutions
Volere:http://www.volere.co.uk
S.RobertsonandJ.Robertson:Masteringthe
requirementsprocess(3rdEd.),Addison-Wesley,2012.

17. Product Product Product
Customize Jama Contour for RM in
Continuous Product Development
Release Management
Monitor Development
Status
Requirements-Based
Testing
…
22. März 2013 Copyright © 2013, Software.Process.Management 17

18. Release Management with Requirements
22. März 2013 Copyright © 2013, Software.Process.Management 18

19. Project Support through Workflow Monitoring
22. März 2013 Copyright © 2013, Software.Process.Management 19

20. Dashboard View on Project Progress
22. März 2013 Copyright © 2013, Software.Process.Management 20

21. Requirements-Based Testing
22. März 2013 Copyright © 2013, Software.Process.Management 21
Requirements
Coding &
(Dev.) Testing
Architecture &
Design
Test Strategy &
Test Cases
Test Execution
Test
Preparation
t

22. Requirements-Based Testing
22. März 2013 Copyright © 2013, Software.Process.Management 22
Requirements
Coding &
(Dev.) Testing
Architecture &
Design
Test Strategy &
Test Cases
Test Execution
Test
Preparation
t
Start testing as early
as possible

23. Volere:http://www.volere.co.uk
S.RobertsonandJ.Robertson:Masteringthe
requirementsprocess(3rdEd.),Addison-Wesley,2012.
Fit Criterion: Link RM with Testing
22. März 2013 Copyright © 2013, Software.Process.Management 23
Fit Criterion: A measurement of the requirement such that it is possible
to test if the solution matches the original requirement

24. Feedback from Testing about
Quality of Requirement
22. März 2013 Copyright © 2013, Software.Process.Management 24

25. Testing
22. März 2013 Copyright © 2013, Software.Process.Management 25

26. Test Coverage
22. März 2013 Copyright © 2013, Software.Process.Management 26

27. Principles of Tool-Based RM
RM tools are platforms that must be customized
Align and integrate RM processes with RM tool practices
RM tools can be great enablers of productive development practices
22. März 2013 Copyright © 2013, Software.Process.Management 27

28. Vielen Dank
28
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller
22. März 2013 Copyright © 2013, Software.Process.Management

29. Webinar am 11. April 2013, 15:00–16:00 Uhr
Requirements flexibel und agil managen —
Requirements-Praktiken am Beispiel Contour
Von Klärung & Definition über Change Management & Reviews bis
zur Agilität, erlernen Sie bewährte Praktiken des toolgestützten
RMs....
http://www.qa-systems.de/akademie/einzelansicht.html?tuid=46
Gerne nehmen wir Ihre Themenwünsche und Fragen vorab
entgegen
22. März 2013 Copyright © 2013, Software.Process.Management 29