The document discusses requirements management (RM) with HP Quality Center/ALM. It describes the benefits of tool-based RM for different roles. It also outlines how RM functionality has evolved in HP ALM versions over time to include improved traceability, reporting, and support for agile environments. Finally, it provides guidance on establishing effective tool-based RM practices in an organization.
1 of 26
More Related Content
Requirements Management with HP ALM
1. Requirements Management with
HP Quality Center / ALM in the
Application Lifecycle
Dr. Andreas Birk, Gerald Heller, Software.Process.Management
November 2014
2. Advantages of Requirements Management
2
What benefit will tool-based RM bring to you?
Target Groups
RM
Requirements
Manager
Project
Manager
Business
Analyst
Test
Manager
Product
Manager
Copyright 息 2014, Software.Process.Management
3. Advantages of Requirements Management
3
Target Groups
RM
Requirements
Manager
Project
Manager
Business
Analyst
Test
Manager
Product
Manager
Clarify needed tests early
Facilitate communication &
transparency of requirements
Benefit of RM
for Target Groups
Monitor project
progress & results
Establish clear
requirements ownership
Track & manage changes to
requirements
Determine requirements
status & quality
Make RM more effective & efficient
Increase stakeholder
involvement
Prioritize tests according to
business needs
Copyright 息 2014, Software.Process.Management
4. 4
Modern RM Is
Tool-Based RM
Copyright 息 2014, Software.Process.Management
5. Evolution of RM Functionality in HP QC/ALM
5
New UI, Web Client,
Authoring mode
Agile Manager
Requirements in agile Environments
Business Views,
Application Lifecycle Integration (ALI)
Business Model Integration, IDE Integration
Traceability Matrix, Type Specific Reporting / Templates
Versioning, Baselines, Sharing
Requirement Types and Attributes, Releases and Cycles, Risk based Quality Management
QC Versions
9.2 10.0 11.0
11.5
12
Copyright 息 2014, Software.Process.Management
6. Structure Requirements
HP ALM structural concepts
Folders
Groups
Requirements Types
6
a
Copyright 息 2014, Software.Process.Management
7. Requirements Attributes in HP Quality Center
7
Requirement type specific attributes
and templates in the description
Copyright 息 2014, Software.Process.Management
11. RM Authoring Mode with HP QC 12 Web UI
11
Author mode manages
requirements in chapter
oriented format
Copyright 息 2014, Software.Process.Management
12. Comprehensive
Reporting
12
Company header
Flow format
including attributes
and graphics
Table format
including rich text
and graphics
Copyright 息 2014, Software.Process.Management
13. 13
How to Establish
Tool-Based RM?
Copyright 息 2014, Software.Process.Management
14. RM is Different
14
Different product types & development environments
call for different requirements structures & workflows
Enterprise IT Application Marketed Technology
Product
Agile Development
IT
App
System HW SW Product
Copyright 息 2014, Software.Process.Management
15. From Testing to RM
in Corporate Test Center
15
Project A Corporate Test Center
Project B
Project C
HP ALM
Test Cases
TC
Create Contract
TC
Modify Contract
TC
Cancel Contract
Copyright 息 2014, Software.Process.Management
16. From Testing to RM
in Corporate Test Center
16
Project A Corporate Test Center
Project B
Project C
HP ALM
Requirements Test Cases
TC
Create Contract
TC
Modify Contract
TC
Cancel Contract
SPEC
REQ
Create Contract
HP ALM
Requirements Test Cases
REQ
Title: Manage Contract
Link: http://intra.comp
Description:
The system shall
Owner:
Copyright 息 2014, Software.Process.Management
21. Corporate-Wide Harmonization of
Tool-Based RM Practices
Strategy
Design new HP ALM RM work practices
Align & agree upon new practices across projects
Prepare & plan tool introduction / roll-out
Support roll-out of new tool & RM work practices (training etc.)
Benefit
Corporate-wide use of RM best practice
Effective uniform interface between projects & test center
Projects can be managed easier (staff assignment, reporting, KPI etc.)
Conformance to compliance rules can be assured more easily
Copyright 息 2014, Software.Process.Management 21
22. Important Questions When Setting-Up RM
22
Design of Information
Structures
What requirements types shall we define?
What attribute fields shall requirements types contain?
How shall we structure the overall set of requirements?
How can we map requirements to tests?
Usage & Workflow What requirements reports do we need?
What KPIs and dashboards shall we define?
How shall we involve customers?
How shall we integrate external development partners?
Set-Up & Establish Which projects shall we select for starting with tool-based RM?
How can we train and support users?
How can we adapt RM to agile development?
Copyright 息 2014, Software.Process.Management
23. Conclusions
HP QC/ALM provides a solid set of effective RM functionality
Tool-based RM practices must be customized carefully to
organizational needs & context
Viable strategies exist that can guide organizations in setting-up &
establishing tool-based RM
Copyright 息 2014, Software.Process.Management 23
24. RM with HP QC/ALM: Information Sources
HP QC/ALM community
http://h30499.www3.hp.com/t5/Application-Lifecycle-Management/ct-p/application-lifecycle-mgnt
HP QC/ALM content for download from HP (includes partner offerings)
https://hpln.hp.com/node/10354/contentfiles
HP QC/ALM whats new (release notes)
http://update.external.hp.com/ALM/WhatsNew_Addins_Movies/index.html
HP QC /ALM system requirements specifications
https://hpln.hp.com/page/alm-qc-enterprise-technical-specifications
HP Agile Manager (new portal Pronq)
https://www.pronq.com/software/agile-manager
SQA Forum
http://www.sqaforums.com/forums/hp-alm-mercury-quality-center/
Copyright 息 2014, Software.Process.Management 24
25. RM-Related Events & Trainings
Webinar: Agile Entwicklung mit HP Agile Manager und HP Quality Center / ALM
5 Feb 2015, http://minerva-softcare.de
Seminar: Certified Software Product Manager
10-12 Mar 2015, Karlsruhe, http://www.seminaut.de
Workshop: Requirements-Reuse zum Erfolg f端hren
REConf 2015, 15 Mar 2015, M端nchen, http://reconf.de
Seminar: Requirements-Management in der agilen Software-Entwicklung
5 Mai 2015, Karlsruhe, http://www.seminaut.de
Seminar: Toolgest端tztes Requirements-Management
12 Mai 2015, Karlsruhe, http://www.seminaut.de
Copyright 息 2014, Software.Process.Management 25
26. 26
Dr. Andreas Birk
Gerald Heller
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Copyright 息 2014, Software.Process.Management
Editor's Notes
#7: Explain requirement types in more detail
Functional, non functional, personas, use cases, user stories, even tasks
Interesting to note, that this structure is very flexible. E.g. On the same data elements we might impose a backlog structure, or component view or project view.