Requirements wiederverwenden - Requirements-Praktiken am Beispiel Jama
Ein Webinar von Software.Process.Management für die QA Systems Akademie
Referenten: Dr. Andreas Birk und Gerald Heller
Content:
- Understand reuse
- Learn how Jama supports reuse
- Discuss reuse approaches & experiences
2. Gestatten ...
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller
4. What is Reuse?
Don‘t re-invent the wheel
Identify commonalities of
software application domains
Develop a collection of
reusable assets
Balance standardization &
customer-specific adaptations
5. Benefit of Requirements Reuse
Be fast & efficient
Escape maintenance hell
Sustain quality
Improve other disciplines like architecture & testing
Improve other disciplines like architecture & testing
7. Scenarios of Requirements Reuse
Evolve a product over a series of sequential releases
Develop a product with a series of overlapping releases
Ensure that a fixed set of standards is implemented in every product
Implement functionality of project B similar to previous project A
Develop business application for several different countries
Develop variants of product for several different customers
9. Reuse Support in Jama
Manage release information
Reuse & synchronize requirements
Manage requirements change
Manage requirements versions
10. Reuse Support in Jama
Manage release information
Reuse & synchronize requirements
Manage requirements change
Manage requirements versions
11. Scenario: Sequential Releases
Evolve a product over a series of sequential releases
Define requirements with regard to target product
Assign each requirement to one of several incremental releases
Add new requirements on an ongoing basis
Flexibly re-assign requirements between releases
Reuse tests and other artefacts associated with requirements across releases
14. Reuse Support in Jama
Manage release information
Reuse & synchronize requirements
Manage requirements change
Manage requirements versions
15. Scenario: Projects Share Requirements
Implement functionality of project B similar to previous project A
(Re-)Use requirements from project A as a baseline for project B
Manage commonalities & differences between projects
Propagate requirements updates across projects
16. Two Levels of Reuse Capabilities in Jama
Define the elements of reuse
Entire project with all requirements?
Only a collection of selected requirements?
Define the entities of synchronization
Fields to be kept in sync
Fields specific for project
19. Selective Reuse
In this example only the
non functional
requirements were reused
Note the little blue dot
at the requirement
20. Define the Elements of Reuse
Each requirement has shared
fields and project specific fields
The project specific fields will
not be considered in later
synchronization in Jama
shared
shared
not
Global ID
Name
Description
Rationale
Author
Status
Status Remark
Responsible
Project A – Req x
Global ID
Name
Description
Rationale
Author
Status
Status Remark
Responsible
Project B – Req x
29. Challenges of Requirements Reuse
Organizational Technical
Methodological
Coordinate attributes of reused
requirements across projects
Manage links between
requirements during reuse
Keep requirements structures
in sync with software architecture
Manage dependencies
across projects
Manage budget
for shared assets
Set-up & maintain reuse infrastructure
Raise upfront investment:
Develop for reuse
Cognitive challenge for
team members: Abstract thinking
30. Important Questions on RM Process Design
How can we know what reuse-based RM approach fits for us?
How can we introduce new RM & reuse practices?
How can we disseminate reuse throughout our organization?
31. RM Tools Enable
Effective Requirements Reuse
Experience confirms: Tool-based requirements reuse can be effective
Example case using Jama as RM tool:
Catalog-based reuse involving several 10K of requirements in reuse base
Deep requirements hierarchy with full requirements tracing
Reuse from catalog to platform product
Within platform: Reuse across a sequence of product variants
32. Additional Information & Resources
The presentation slides of this webinar will be published on SlideShare
Related presentations already available:
Requirements strukturieren und nutzen — Requirements-Praktiken am Beispiel Contour
http://de.slideshare.net/softwareprocessmanagement/20130322-requirements-strukturierenambeispielcontour-
18607659
Requirements flexibel und agil managen — Requirements-Praktiken am Beispiel Contour
http://de.slideshare.net/softwareprocessmanagement/20130411-webinar-rmmitcontour
Upcoming Training on 6. November, 2014
Requirements-Management in der agilen Software-Entwicklung
http://www.qa-systems.de/akademie/einzelansicht.html?tuid=36
Case study report Intel Mobile Communications from REConf 2014 available upon request (info@swpm.de)
Pferdewechsel bei vollem Galopp:
Toolwechsel und Weiterentwicklung des RE in einer großen, komplexen Plattformentwicklung
33. Vielen Dank
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller