Академический Документы
Профессиональный Документы
Культура Документы
www.jamasoftware.com
| 1.800.679.3058
Challenges
Improve Quality
Increase Visibility
Reduce Development Costs
Accelerate Innovation
Terminology
Traceability
Downstream
Coverage Report
Impact Analysis
Version History
Suspect Links
ISO 9001
Trace Relationship
Upstream
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058
Document changes for complete visibility and a detailed audit trail with Version History
Stay synced with Stream communication. By referencing people and items through
@mentions, you can easily track comments through filters and history
Trace Relationships
As in many aspects of life, your product and system development success is highly dependent on relationships. All details
such as user requirements, functional requirements, test cases and other items that define the scope of what youre
building are related in some fashion, either directly or indirectly. Heres an example of a common process flow:
Stakeholder
Requirements/
Objectives
Whats the vision
for this product?
System
Requirements
System
Architecture
Whats the
story of what
users need?
How should it
work to fulfill
the needs?
Verifications
How will the
system be tested
to ensure it meets
the requirements?
Trace relationships to connect artifacts together to map out interdependencies between the different items. These
relationships are the foundation for effective traceability. Below is an example of traceability showing both upstream and
downstream trace relationships.
Traceable relationships are as much about connecting the people involved as they are about connecting all items. Each
requirement in the system has members of your team associated with itanalysts, architects, development, verification
and quality assurance among themand stakeholders and customers who care about its status.
When one item changes, it has a
ripple effect on other related items
and the people associated with the
items. Keeping track of this ripple
effect is crucial to the success of
your projects. Its one of the primary
reasons organizations need
intuitive traceability.
Specifically, tracing relationships
identifies the individuals and teams
affected by change and allows them
to discuss and make decisions
in context.
Jama Software, Inc
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058
Coverage Explorer
Every test case has a comment and activity stream accessible to all
users. Testers and contributors can capture decisions, answer questions
and resolve issues transparently and responsively.
Impact Analysis
What if you could anticipate the impact of a change on your project and the entire team before it occurred? Will this
change request send the development team over the edge? What if you could predict the whether? These insights
are possible with Impact Analysis. Impact Analysis relies on the trace relationships you set up, and it reports on the
complete picture of all the items that are directly and indirectly affected.
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058
Heres an example of an automated impact analysis report for a high-level business requirement. If this requirement
changes, three directly related system requirements, downstream software requirements and numerous verification tests
would all be affected.
Version History
Capturing a complete and detailed record of all changes is a critical element for reaching higher levels of requirements
maturity within your process, such as ISO 9001.
Version History is for those among us who like to (or have to) roll up our sleeves and get deep into the details of every
change. It also helps companies meet regulatory compliance standards in fields such as aerospace and medical devices.
One of the benefits of traceability is having a comprehensive audit trail of changes, so you can analyze the who, what, when
and why of every change made. At the same time, you can easily roll back to an earlier version because its all stored in the
definitive system of record and action.
Heres an example of a
side-by-side comparison
of two versions, using an
automated process within
Jama. For efficiency gains,
the specific field that
changed is highlighted in
yellow, so you dont have to
spend time hunting around
the full requirements
specification document to
pinpoint and understand
precisely what changed.
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058
Real-Time Communication
You need to be sure that everyone impacted by a change is in the loop. At the same time, you dont want to flood the entire
organization with irrelevant emails. What do you do?
In the example above using Jama, you can instantly send a direct link to the specific requirement that changed, with version
notes, to only the relevant groups or individual users affected. Notification is part of the overall change management
workflow. Stay in the loop. Avoid noise.
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058
Picture this: Traceable communication. Documented decisions and actions. All product and
systems info organized and contextualized from concept to launch. With Jama, its your reality.
Try Jama and see how we can help you solve your teams systems engineering challenges.
Ask a Question
Call us direct:
Page No.
www.jamasoftware.com
Request a Quote
Schedule a Demo
503.922.1058