RATIONAL SOFTWARE RESPONSE to
INCOSE Survey
For immediate Release, November
20, 2001
Questions answered based on
AnalystStudio v2002 (includes
RequisitePro v2002)
INCOSE Tools Database WG -
Requirements Mgmt. Tool Survey
Last Survey Update:
January 2000, International Business Meeting, Mesa
1. Capturing
Requirements/identification
1.1.
Input document enrichment/analysis
Using existing
document information (such as glossary, index, etc.), aid the user in
requirements analysis, identification of requirements,
etc.
Full. Rational Suite
AnalystStudio contains the Rational Unified Process*, an online knowledge base
of software development best practices. RequisitePro, the requirement management
component of AnalystStudio, provides an out-of-the-box project structure that
complies with the Rational Unified Process software development recommended
practices. That structure includes a set of document templates (glossary, vision
document, use case specification, test plan, test case specification).
* Rational Suite AnalystStudio contains: Rational Unified Process, Rational ClearQuest, Rational RequisitePro, Rational SoDA , Rational Rose Data Modeler, Rational ClearCase LT and Rational TestManager.. The components of AnalystStudio provide a more complete requirements management solution, by automating the three major activities performed during effective requirement management: collection of requests, management of requirements as well as the communication of requirements.
1.1.1. Input document change/comparison analysis
The ability to
compare/contrast two different versions of a source
document
Full.. Document
comparison is supported via MS Word's compare utility.
1.2.
Automatic parsing of requirements
A mechanism for
automatic identification of requirements by key words, structure, unique
identifiers, etc. to create requirements from the text.
Full. AnalystStudio
provides an import wizard to import requirements either from a Word document or
a Comma-Separated Value (CSV) file. Word documents can be parsed for requirement
extraction based on user-defined keywords, Word headings (including Word
highlight), and text delimiters. CSV files provide the ability to import requirement attributes as well. The
import facility is also available for a block of text in a document. Using a
Block Create operation, the user can select a section of a document and parse
requirements located in that section.
1.3.
Interactive/semi-automatic requirement identification
The ability to
identify requirements from a text file via interactive means such as mouse
highlighting of the requirement text or prompting by the system "is this a
requirement?".
Full. Requirement text
is selected using standard text selection in MS Word. Right clicking on the
selection provides a "Create Requirement" context-sensitive menu option. Once
the requirement is created, the requirement text is marked in the Word document.
The Word document remains live and the requirement text can later be modified in
the Word document, without requiring imports of updated documents. Requirements
are maintained in both Word format (requirement text) and a database
(requirement text, attributes, traceability links, and requirement-related
discussions).
1.4.
Manual requirement identification
A manual means of
identifying or creating requirements.
Full. Requirements are
selected by the user in an MS Word document, and created using a right-click
menu option. Upon creation, requirements are automatically entered into the
requirements repository.
1.5.
Batch mode operation
A mechanism for
inputing/identifying requirements from outside of the
tool.
Full. Requirements can be added to the requirement repository using an Extensibility Interface (RPX) script to programmatically enter requirements from another tool or from a file.
1.5.1. Batch-mode document/source-link update
Does the tool have
the ability to update existing linked documents from new/changed versions of the
source documents without having to re-establish traceability
links
Full. Documents are
live in the AnalystStudio project. Document updates are made within the Word
interface of the tool, eliminating unnecessary import of documents, as document
content changes.
1.6.
Requirement classification
Does the tool have
the ability to classify/categorize requirements during identification?
Full. Requirements are
organized by requirement type. Each requirement type defines a visual
representation of requirement text in documents, as well as a set of
user-defined attributes and associated attribute values. When you identify a new requirement, you
can also specify the requirement type and attribute
values.
2. Capturing system element
structure
Once the
requirements have been captured, the allocation of requirements to sub-system
elements takes place. The tool must capture these elements so links/allocations
can be made to those sub-systems elements.
2.1.
Graphically capture systems structure
Can the tool
graphically capture system implementation (such as architecture, functional
decomposition, WBS, etc.) and display them graphically such that requirements
can be linked to them.
Full. Sub-system
allocations can be performed using requirement attributes or one could use
system implementation requirements that are linked to the requirements.
Graphical traceability tree and matrix views show the relationships between
system requirements and implementation.
In addition, the integration between Rational Rose and RequisitePro
allows a linkage between the graphical elements in an analysis or design model
and their related requirements.
2.2.
Textural capture of systems structure
Can the tool
textually capture system implementation (such as architecture, functional
decomposition, WBS, etc.) and display them textually such that requirements can
be linked to them.
Full. System
implementation documents can be imported into the requirements component of
AnalystStudio. Their textual representation can then be itemized into system
implementation requirements. These system implementation requirements can then
be traced to system requirements.
Once the
requirements have been captured and system architecture captured, requirements
are allocated to the various system elements.
3.1.
Requirements derivation (req. to req, req. to
analysis/text)
The ability to
derive/create additional requirements and link between them such as requirement
to requirement, or requirement to text (representing trade studies) to derived
requirements.
Full. Derived
requirements are created either in Word documents or directly into the
requirements repository. They are then traced to the source requirement either
using a right click in a traceability matrix, or setting the requirement
properties.
3.2.
Allocation of performance requirements to system elements (weight, risk, cost,
etc.)
The ability to link
performance requirements to system elements such as weight, cost, throughput,
etc. This also includes the ability to allocate portions of that performance
requirement to system elements.
Full. Requirements are
organized using user-definable requirement types. Using requirement types, users
can create performance requirements, system requirements, marketing
requirements, test requirements, etc. Each requirement type has its own set of
user-defined attributes. Attributes such as weight, cost and throughput can be created.
3.3.
Bi-directional requirement linking to system elements
The linking of
requirements to system elements can be accomplished from either end of the
link--from the implementation back to the requirement or from the requirement
down to the system element.
Full. Flexible
bi-directional traceability relationships are supported. Linking of requirements
to system elements is done via the integration between the requirements
component of AnalystStudio (Rational RequisitePro) and the design component
(Rational Rose).
3.4.
Capture of allocation rationale, accountability, test/validation, criticality,
issues, etc.--if so how and what mechanism does
it
use?
Also critical, is
the ability to attach rationale, assignments, criticality, test/validation and
many other issues to the requirement, allocation, and the system element to
which a requirement is linked.
Full. AnalystStudio
provides unlimited user-defined attributes of types: text, list (single or
multi-value), integer, real, date, time, etc. for any requirement type. Flexible
traceability relationships can be established between any requirements. The
rationale of the requirement can be documented via the attributes mentioned
above, email-enabled discussion groups as well as via the integration with a
full change request management tool (ClearQuest).
Once the allocations
are complete, the user will want the ability to see the links where they come
from, where they go, and why they apply.
4.1.
Identify inconsistencies (orphans,...if so what kind of...)
The tool should
allow the user to identify inconsistencies such as unlinked requirements or
system elements (orphans).
Full. AnalystStudio's
traceability interface provides an easy-to-use query mechanism to efficiently
detect "suspect" traceability links. The query interface allows flexible queries
to find linked and unlinked requirements.
4.2.
Visibility into existing links from source to implementation--i.e. follow the
links
With the requirement
links in place, the user needs the ability to follow the links to see where they
come from and where they go to
Full. Traceability
trees are provided to view the complete path of relationships. A "Requirement Go
To" feature aids navigation.
4.3.
Verification of requirement (was it done, how was done)
Throughout the life
of the project, the requirement management tool will be used to verify that the
requirements have been met. The tool should provide the ability to document that
the requirement was fulfilled, how it was done, and who was responsible.
Full. Querying of
traceability relationships verifies requirement coverage. Requirements
attributes can be used to track who created the requirement, who implemented it
and who tested it.
4.4.
Requirement performance verification from system elements (roll up of
actuals)
Once performance
requirements have been allocated to system elements, the requirements management
tool should support the verification of those requirements by rolling up actuals
and reporting on variances (this is the allocated weight versus the actual
weight).
Partial. Requirement
attributes can be used to record "planned" vs. "actual" values. The
AnalystStudio reporting tool can report on discrepancies between planned and
actual results.
5.1.
History of requirement changes, who, what, when, where, why,
how.
Once requirements
have been captured, the requirement management tool should maintain a history of
requirement changes, who changed it, when it was done, why it was done, etc.
Some of this tracking could be automatic, others could be procedural such as a
rationale for the change and how the change is to be accomplished.
Full. Integral change
history is provided with automated capture of date, time, author, before and
after contents, and annotated change rationale by author.
5.2.
Baseline/Version control
At various times the
requirements will need to be baselined (saved and locked away). The requirements
management tool should support this along with the ability to compare and
contrast between various baselines.
Partial. A
requirements baseline capability is available in AnalystStudio via the
integration between RequisitePro and ClearCase (Rational's configuration
management too). One may create a
new requirements project from a baseline.
Currently, comparing baselines is not supported.
5.3.
Access control (modification, viewing, etc.)
The requirements
should be able to be protected from modification, viewing, etc. by individuals
or groups.
Partial. User
definable groups can have specific security permissions. The security is
granular enough to provide access rights at the document level, requirement
level, requirement attribute level, as well as attribute value level. While current security features can
restrict modification of requirements, it is not currently possible to restrict
persons from viewing them.
6. Documents and other output
media
6.1.
Standard specification output (if so what kind)
The requirements
management tool should output documentation in various military/commercial
standard formats (490, 2167, etc.).
Full. The
AnalystStudio reporting tool is a Word add-in that supports generation of
documents using any Word templates.
6.2.
Quality and consistency checking (spell, data dictionary,
)
The tool should also
support document quality and consistency checking through spell checking, data
dictionaries, acronym tables, etc.
Full. With its tight
integration with MS Word, AnalystStudio provides Word text-checking features
(spelling, auto correction, thesaurus, etc…).
6.3.
Presentation output
Once the information
is loaded, the requirements management tool should support the generation of
presentation quality charts and graphs.
Full. Requirement
metrics can be output directly to MS Excel from which charts and graphs can be
generated.
6.4.
Custom output features and markings (user definable tables, figures, security
markings..)
The tool should
support the output of documents in finished form including page security
markings, graphics/figures, user definable tables, indexes, etc.
Full. Requirement
documents, written in Word, are managed in-situ by AnalystStudio, and can be
formatted using any MS Word functions. Reports from the requirement repository
can also be extracted directly into a template-based Word document, using the
reporting component of AnalystStudio.
6.5.
WYSIWYG previewing of finished output
The tool should
allow the user to view the document on-screen in finished
format.
Full. Because
requirements are modified within a Word interface, requirements documents can be
formatted using the full MS Word support for documents, print preview, etc.
6.6.
Status reporting
Tool users need to
status information in the requirements management tool.
Full. Views of requirement information can be printed and exported. A requirements metrics feature allows for plotting of requirement data in MS Excel.
6.6.1. Technical Performance Measurement status accounting
Status current
technical performance of various allocated performance requirements and monitor
progress towards goals.
Full. Views of
filtered information can be saved and recalled for project status
analysis.
6.6.2. Requirement progress/status reporting
Status reporting on
current compliance/non-compliance to various requirements
Full. The requirements query facility can be used to report on traceability relationships and missing links as well as filter requirements based on attribute values. Queries can be saved in personal or project-wide areas to apply the query at anytime on the current set of requirements.
6.6.3. Other ad hoc query’s and searches
The requirements
management tool should support ad hoc query’s and searches per the user’s
discretion.
Full. A fully
functional query facility is supported. Multilevel queries can be easily
executed. They can also be saved
and recalled by name. Personal queries as well as project-wide queries can be
saved. A Find Requirement function is also provided to look up requirement by
keyword.
Since Systems
Engineers rarely work as individuals, the ability for a team of engineers to
look/work on the same information at the same time is critical.
7.1.
Support of concurrent review, markup, and comment
The tool should
support a team of engineers reviewing, marking up, and commenting on
requirements or implementation alternatives.
Full. Directly
supports MS Word documents linked to a requirements repository, providing full
support for MS Word revision and security features. There is also support for
email-enabled discussion groups to capture any dialog about new requirements,
modifications of requirements, or any requirement-related topics. Offline
authoring of requirement documents allow team members to take a document
offline, work in a separate workspace and then bring back the document online to
be merged with the previous version.
7.2.
Multi-level assignment / access control
Access by the team
to the database must be tempered by multi-level access control (i.e. the ability
to protect things from being modified). This also includes the ability to submit
changes into an approval cycle (for acceptance/voting) before committing the
changes to the tool for everyone to see.
Full. Access control
is provided at the document level, requirement level, attribute level and
attribute value level. Discussion groups allow users to submit proposed changes
prior to committing these changes to the requirement repository. An integration with the change
management tool (ClearQuest) in AnalystStudio also supports an approval cycle
for requirements.
8.1.
Inter-tool communications
Requirements
management must have the ability to communicate requirements to other
domain-specific design tools (CASE, EE, etc.).
Full. AnalystStudio
contains 7 components, all integrated with one another.
* A requirement
management component (Rational RequisitePro) to create and manage
requirements.
* A change request
management component (Rational ClearQuest) stores stakeholder requests that
may drive requirements. Requests can be associated with requirements in the
requirements repository. AnalystStudio also provides the ability to create
requirement from the change request management tool.
* A visual modeling
component (Rational Rose) allows the requirements engineer to model
requirements visually to better communicate with the rest of the team and the
customer. Rose use case elements are seamlessly integrated in the requirements
repository. Rose use cases have use case specifications and requirement
properties (attributes, traceability links) managed by the requirement
management component.
* A reporting
component (Rational SoDA) extracts data directly from any component
(requirements, visual models, change requests, etc.) to generate up-to-date
reports.
* A process
component (Rational Unified Process) provides best software development
practices (including requirements management) and tool mentors on how to apply
these best practices using Rational tools.
* A configuration
management component (Rational ClearCase LT) allows requirements to be
baselined along with other project artifacts like visual models and
code.
* A test management
component (Rational TestManager) that provides the capability to use
requirements as inputs to the testing process.
Because these
components are packaged into one Rational Suite, the integrations between all
components are guaranteed compatible at each release, relieving customers
from integration maintenance
nightmare.
An integration with
Microsoft Project is also provided.
Customers can also write integrations with other tools, using the Extensibility Interface (RPX), a COM-based API. The Rational Unified Partner Program supports companies that write integrations to other products. . Visit http://www.rational.com/partners/index.jsp to see what is available
8.1.1. Interfaces to other tools?
What tools will your
requirements management tool interface with or talk to?
Full. RequisitePro
includes an extensibility interface (RPX), a COM-based API to programmatically
access (read/write) and query the requirements repository. Using the RPX
customers can write integrations to other tools with a compatible
API.
The Rational Unified Partner Program provides a list of companies that have built commercially available integrations using the Extensibility Interface (http://www.rational.com/partners/index.jsp).
8.1.2. External Applications Program Interface available
To support the wide
variety of tools in use by engineers, the requirements management tool should
have programmable access to the information contained in the tool’s database (to
get access to and deposit information).
Full. The
Extensibility Interface (RPX) is a COM-based API that provides programmatic
access to a requirements repository. .
The API comes with a complete online reference manual and set of
examples.
8.1.3. Support Open database system (standard query access)
Does the tool
support Open Database standards such as standard query languages or exchange
formats?
Full. All database access is internally performed via ODBC. Additionally, via the Extensibility Interface, an SQL-like query language is available to perform powerful queries against the database (MS Access, Oracle or SQL Server).
8.1.4. Import of existing data from various standard file formats?
Does the tool have
the ability to import existing data (such as a ASCII text file containing link
information) to create structures within the tool without having to re-enter the
information?
Full. The Import
Wizard can import Word documents and Comma-Separated-Value (CSV) files. Word
documents are automatically parsed based on a user-defined criterion (keywords,
text delimiters or Word headings, including Word highlight). Once a Word
document is imported, modifications to that imported Word document are done
directly in the tool, using the Word interface of AnalystStudio. CSV files can
be used to import information, such as attributes, that are associated with
requirements.
8.2.
Intra-tool communication
8.2.1. Exchange of information between same-tool different installations
Since the tool will
be used at different sites and different projects, how does the tool exchange
information between different tool installations or databases?
Full. Locating the
project on a network drive provides heterogeneous access across Windows95,
Windows98, Windows Millennium and Windows NT/2000/XP (all Windows clients can
share a common repository). There
is a database conversion wizard that allows easy conversion of requirements
databases between Oracle, SQL Server and MS Access.
The AnalystStudio Web client for requirements, RequisiteWeb, provides Web access to requirements projects with ability to modify requirement text, attributes and traceability relationships, save queries and retrieve queries, as well as initiate and participate in discussions.
8.2.2. Consistency/comparison checking between same-tool datasets
Does the tool
support comparing/contrasting of different same-tool datasets to allow
consistency and verification checking?
Partial. AnalystStudio
documents can be compared using the Microsoft Word compare
facility.
9.1.
Single user/multiple concurrent users
Is the tool support
a single user or multiple concurrent users?
Full. Multiple
concurrent users supported.
9.2.
Multiple Platforms/Operating Systems?
Which platforms and
operating systems does the tool run on?
Full. AnalystStudio
supported on Windows 95, Windows 98, Windows Millennium and
NT/2000/XP
The Web interface runs
on the following browsers 1) Netscape Navigator 4.x and later and 2) Microsoft
Internet Explorer 4x and later. The requirements repository can reside on
Windows 95, Windows 98, Windows Millennium, NT/2000/XP or Oracle-supported UNIX
platforms.
9.3.
Commercial vs. unique database
Does the tool use a
proprietary or commercially available database?
Full. AnalystStudio
uses commercially available databases: MS Access, Oracle or SQL Server.
9.4.
Resource requirements
Please identify
hardware/software configuration requirements:
Software: MS Word95,
MS Word97, MS Word 2000 or MS Word XP
Oracle client (for Oracle-maintained repository)
9.4.1. Memory requirements
64 MB minimum
9.4.2. CPU requirements
Pentium.
9.4.3. Disk space requirements
55
MB
10.1.
Doing one thing while you are looking at another
Does the user have
the ability run a report and look at a requirement at the same
time?
Full. Through the integration with Microsoft
Word a user can be view a requirement in a document at the same time as running
a report via the database interface.
10.2.
Simultaneous update of open views
If the tool allows
for multiple windows/views into the tool--does a change in one view
automatically reflect in all other views?
Full, All requirements
information in an open view is dynamically updated when a requirements document
is saved or a requirement in the
database is changed.
10.3.
Interactive graphical input/control of data
Does the tool
support graphical input and manipulation of data?
Full. Requirements may
include embedded objects. Traceability reports are graphic. UML use case
diagrams are supported via the integration with Rational
Rose.
10.4.
Which window’s standard do you follow?
If your tool
supports a window’s standard, which one(s)?
Full. Microsoft
standards.
10.5.
Executable via scripts (recordable) or macros
Does the tool allow
the user to create and playback commands or macros that allow the user to
automate various tedious tasks?
Partial. The API can
be used to write scripts to modify the requirements repository programmatically.
Also saving views with embedded queries automates routine reporting.
10.6.
Web Browser Interface
Does the tool allow
the user to access the data from a web browser?
Full. Using the
RequisiteWeb interface.
11. Standards--which one’s do
you comply with?
Which
military/commercial standards does your tool comply with--including database
standards, output document standards, exchange standards, display/graphics
standards, etc.
Full. AnalystStudio
can use Microsoft Word to document requirements therefore requirements documents
can be based on any Word templates. AnalystStudio provides the Rational Unified
Process recommended requirements templates. Customers can also create their own
requirements templates. These templates can ensure compliance with
military/commercial standards.
Database access is done via the ODBC standard.
12.1.
Warrantee
Does your tool have
a warrantee, if so what is it?
Full. All Rational
products come with a limited warrantee.
The specifics of the warrantee can be found in Section 7 of the standard
license agreement.
12.2.
Network license policy
Does the tool
support network licensing (floating, node locked, etc.), if so which license
manager?
Full. Licenses can be node locked or floating.
A license manager (flexLM from GLOBEtrotter) is provided with AnalystStudio.
12.3.
Maintenance and upgrade policy
How often are
software updates released; are updates separately priced items,
etc.?
Full. There are two
releases per year. All tools in Rational Suite are shipped in a synchronized
release. AnalystStudio comes with a year of support and free product upgrades.
All updates are free to customers with an up to date maintenance
agreement.
12.4.
Online help
Are the users
manuals online, is there online help with the tool?
Full. A printed manual
set plus online help system is included with the tool. A "Let’s Go" wizard is
provided to speed up newcomer’s familiarity with the tool. A tutorial also comes
with the product.
12.5.
Internet access/World Wide Web home page location
Does the tool
supplier have an Internet address or Mosaic home page
location?
Full. Rational’s home page is www.rational.com. AnalystStudio web page is http://www.rational.com/products/astudio/index.jsp
12.6.
Phone support
What type of phone
support is available from the tool supplier?
Phone support during
extended normal business hours is provided to all customers with an up-to-date
maintenance agreement. 7x24 support
can be purchased at an extra cost.
North America
800-433-5444, 408-863-4000 (in English) , support@rational.com
Europe, Middle East,
Africa +31 (0)20 4546 200 (In
French, German and English) , support@europe.rational.com
Asia Pacific +61-2-9419-0111 (in English), support@apac.rational.com
13.1 Are tool specific training classes available?
What geographical areas?
Yes. Rational provides
tool training as well as methodology training. Public classes are provided at
Rational training facilities worldwide. On-site classes are also available. Visit http://www.rational.com/university/index.jtmpl
for details.
13.2 Can training be made available at a customer’s
location?
Yes. Classes can be
delivered onsite, at the customer’s location.
13.3.
Recommended
training time?
What is the
recommended training time for a user to become proficient in using the
tool?
Full. Most users require no tool training; a one-day course is available. Requirements management classes are strongly recommended. Rational University provides a 3-day Requirements Management with Use Cases (RMUC) class.
13.4 Can software installation be performed by an
individual with only basic training in the tool?
Software installation
does not require tool knowledge. However someone familiar with the requirements
management process in the organization should do tool setup in order to optimize
tool usage.
14. What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Return to INCOSE Home
Content Owner: TDWG Chair
Contact us at info@incose.org
Copyright 1998-2004 International Council on Systems Engineering
Last Modified: September 22, 2004