 RM White Papers & Reports
Search our library of reports and white papers from industry analysts, consultants, vendors and industry experts to help you make informed decisions about requirements.
 Get the Feed |Subscribe by Email
|
|
Requirements reuse provides organizations with the unique ability to share a requirement across projects without absorbing unnecessary duplication of artifacts within a repository. This is a critical capability that accelerates time to market and cuts development costs.
The concept of reuse is a familiar notion within the software development realm, but less
common when considered in the field of requirements management. There are various definitions and use cases which must be taken into consideration when implementing a solution to address requirements reuse.
This whitepaper discusses the elements that make up a requirement and establishes common
understanding of how requirements evolve, how that evolution is retained, and how
organizations can reuse requirements to speed business innovation, reduce complexity and
control costs.
|
In today’s fast-paced, global business climate, businesses need systems now. Accelerated system delivery produces higher quality systems and increases customer satisfaction in less time. This white paper presents ideas on what a JAD is, when it should be used, and details about a variety of uses for this versatile technique.
|
To be competitive, Model-Based Design can be applied to help bring down the cost of
system design and faster time to market.
|
|
The difference between defect-based testing and requirements-based testing stems from the methods of determining and applying stimuli. Requirements-based testing derives direction from device requirements developed during product planning or design…
|
Model-based software development offers new opportunities and challenges for validation and verification of safety-critical software. In this report, we describe an approach for validating the artifacts
generated in a model-based development process. Our approach divides
the traditional testing process into two parts: one that validates the
formal model implements the high-level requirements and another that
determines whether the code generated from the model is behaviorally
equivalent. The focus in this report is on validation testing; in
particular, we present a framework that enables objective measures of
requirements coverage and provides the ability to achieve a high degree
of automation.
|
|
Errors in requirements are a major source of waste in IT. There have been attempts to reduce the problem, but until recently they have suffered from being dispersed and unco-ordinated across the lifecycle. As enterprises become increasingly interested in cross-discipline application lifecycle management (ALM) solutions, requirements-based testing re-emerges to address the problem in an integrated way. It combines methods from requirements engineering and software testing into an orchestrated set of quality assurance activities and management tools that focus on getting the requirements right from the outset, managing inevitable change and discovering requirements errors before they become extremely costly to fix.
|
Requirements and the way they are dealt with are decisive to the
success of a project. This statement is never really questioned in
modern software engineering circles. Why is it, then, that a systematic
requirements engineering (RE) system is so rarely established? Where do
the problems lie when it comes to implementing such a system? This
paper outlines the challenges and how these may be met using the
example of the automotive industry.
|
This paper addresses issues faced in the requirements-based testing (RBT) process and describes a strategy to integrate testing throughout the development life cycle and focus on the quality of the Requirements Specification. The result is early defect detection and prevention, reducing costs by finding and fixing defects earlier in the development process.
|
|
In current practice, the adequacy of black box test suites is inferred
by examining coverage on an executable artifact, either source code or
a software model. In this paper, the authors define structural coverage
metrics directly on high-level formal software requirements. These
metrics provide objective, implementation-independent measures of how
well a black-box test suite exercises a set of requirements. The focus
on structural coverage criteria on requirements formalized as LTL
properties and discuss how they can be adapted to measure finite test
cases. These criteria can also be used to automatically generate a
requirements-based test suite. Unlike model or code-derived test cases,
these tests are immediately traceable to high-level requirements. To
assess the practicality of our approach, we apply it on a realistic
example from the avionics domain.
|
Independent Report by Forrester Research,
Compliments of MKS
According to Forrester Research, organizations are often
tripped up in their search for the right requirements management solution, and
end up buying a tool that is more complex, more difficult to use, and more
expensive than necessary.
Forrester's application lifecycle management (ALM) team
urges IT and software engineering organizations to consider requirements
management solutions that meet the following critical features:
- Part of an ALM solution.
- Offers baselining.
- Linking and tracing to track relationships amongst requirements.
- Integration with Microsoft Word.
- Requirements reuse to support sharing of common requirements across projects.
- Workflow to automate requirements change processes.
MKS is pleased to offer you a
complimentary copy of this report.
|
This paper reviews the requirements management tools landscape and
introduces you to MKS Integrity for requirements management, the only
solution available today built as an extension of an application
lifecycle management platform. See how with MKS Integrity, requirements
are authored, captured and traced through the downstream lifecycle, how
companies can utilize best practices such as parallel development and
reuse in relation to requirements and how configuration management
concepts such as versioning and base lining can be leveraged for
advanced requirements management practice.
|
This paper presents a simple, practical calculation of the cost of requirements errors in application software development projects. It also recommends a way to find and fix these costly errors early in a project, when they are least expensive to correct.
|
|
