Requirements wiederverwenden am Beispiel Jama

Requirements wiederverwenden
Requirements-Praktiken am Beispiel Jama
Handout-Version
Dr. Andreas Birk und Gerald Heller, Software.Process.Management
9. Mai 2014, Webinar der QA Systems Akademie

Gestatten ...
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller

Today’s Agenda
Understand reuse
Learn how Jama supports reuse
Discuss reuse approaches & experiences

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

Benefit of Requirements Reuse
Be fast & efficient
Escape maintenance hell
Sustain quality
Improve other disciplines like architecture & testing
Improve other disciplines like architecture & testing

Business context
determines what are suitable
reuse approaches

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

Reuse Support in Jama
Manage release information
Reuse & synchronize requirements
Manage requirements change
Manage requirements versions

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

Define and Manage Releases
Define releases and
assign items to it

Get the Complete Picture about Releases

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

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

Create Similar Project
Alternatively create new project
and select individual
requirements for synchronization

Selective Reuse
In this example only the
non functional
requirements were reused
Note the little blue dot
at the requirement

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

Visual Indicators About Shared Fields

Stay Informed About Differences
Project B is not in sync

Manage Changes Across Projects
Get details about
items not in sync

Sync Back Changes – Single or All

Jama Supports Change Processes
Across projects

Use Baselines to Capture Status of Project
Baselines provide a mechanism for
testing to identify reusable test

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

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?

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

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

Vielen Dank
Dr. Andreas Birk
Software.Process.Management
info@swpm.de
http://www.swpm.de
Blog & Resources
http://MakingOfSoftware.com
Gerald Heller

Requirements wiederverwenden am Beispiel Jama

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Requirements wiederverwenden am Beispiel Jama

Semelhante a Requirements wiederverwenden am Beispiel Jama (20)

Último

Último (20)

Requirements wiederverwenden am Beispiel Jama