INCOSE Requirements Management Tools Survey - Cradle Response
Cradle
is a comprehensive, user-extensible, multi-user, and multi-project systems
engineering environment which provides a robust, proven database structure for
concurrent development of large and complex systems. From concept to creation,
Cradle has been deployed successfully in a broad range of aerospace, defense,
manufacturing, process control, telecommunications and transportation projects
worldwide.
Cradle
combines two sets of capabilities. The first is a Project Data Module (PDM) that
provides an extensible framework and database for the control and management of
information. The second is a set of specifically-targeted modules designed to
meet your systems engineering needs, addressing Requirements Management, System
Modeling, Performance Modeling, Software Engineering, Web Access, Web Printing
and Document Generation.
Cradle
provides an assortment of project infrastructure capabilities including access
control, user roles and privileges, project organization and database schema,
cross referencing, impact analyses and configuration management.
With
its wide range of interoperability features and open architecture, Cradle
integrates seamlessly into existing IT infrastructures with desktop publishing
tools. This Cradle architecture provides a systems engineering environment with
proven industrial strength and scalability.
Using existing document information (such as glossary, index, etc.) aids the user in requirement analysis, identification of requirements, etc.
FULL COMPLIANCE
The ability to compare/contrast two different versions of a source document
FULL COMPLIANCE-
with associated impact analyses performed.
A mechanism for automatic identification of requirements by key words, structure, unique identifiers, etc. to create requirements from the text.
FULL COMPLIANCE- to
all of the above discriminators.
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 COMPLIANCE- in
both this and fully automatic mode above, automated completeness checks are
provided to validate the extent of requirements capture.
Plug-ins for
Microsoft Word and Excel have been created that allow the user to capture
paragraphs and tables from Word and spreadsheet rows from Excel as Cradle
requirements, system notes or process specifications.
A manual means of identifying or creating requirements.
FULL COMPLIANCE-
Cradle provides a MS Word/Excel interface that supports creating requirements in
the database from either Word or Excel.
A mechanism for inputing/identifying requirements from outside of the tool.
FULL COMPLIANCE- CSV
import.
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 COMPLIANCE-
yes.
Does the tool have the ability to classify/categorize requirements during identification
FULL COMPLIANCE-
requirements grouping, classification, and categorization all fully supported.
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.
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 COMPLIANCE-
yes, extensive library of modeling notations allows user to capture system
implementation and associated linking.
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 COMPLIANCE-
user defines (database) item type. Requirements can be cross-referenced into
other data types as well as system models.
Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements.
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 COMPLIANCE-
requirements derivation hierarchies fully supported, as well as decomposition
and merging. Requirements history
tracking and evolution fully supported.
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 COMPLIANCE-
user defines (database) item type. Performance requirements can be
cross-referenced into other data types as well as system models.
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 COMPLIANCE-
Cradle provides bi-directional, many-to-many, typed, attributed, transitive
cross-references.
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 COMPLIANCE-
complete flexibility in attaching frame information to item, including text,
spreadsheets, tables, equations, video, sound clips, CAD/CAM drawings, etc.
External referencing mechanisms are also provided.
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.
The tool should allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans).
FULL COMPLIANCE-
Hierarchical diagrams provide a graphical depiction of requirements links to
display anomalies. Additionally, analysis tools are provided for identification
and correction of ambiguity, contradiction, duplication and omission.
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 COMPLIANCE- project-defined link types and groups; several traceability templates, traceability diagrams and reports provided. Predefined queries provided to allow user to immediately examine requirements traceability. Hierarchy diagrams are available in the Cradle Cross Referencer that provide a view showing all items that are directly linked to the current item and, for each of them, the items that they are cross referenced to, for a specified number of levels.
Completeness assessment and impact analyses of requirements to system cross referencing available.
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 COMPLIANCE-
complete traceability throughout lifecycle, with attachable item frame data to
capture complete requirements history. Impact
analyses and change assessments supported.
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).
FULL COMPLIANCE- requirements linked to constraints on
performance of the system design model in which performance is assessed using
mathematical models based on user configurable performance parameters.
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 COMPLIANCE-
complete requirements evolution is provided through history records, external
user annotations and CM baselines. Full
configuration audit logs also provided.
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.
FULL COMPLIANCE-
complete support of formal reviewing, and subsequent baselining and version
control and management. Extensible
database schema to allow encapsulation and use of existing QA documents within
existing QA/QC procedures.
Using the Web
Publisher Module, Cradle can also publish different baselines, or
work-in-progress, into separate website components, for comparison between
approved and current activities.
The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
FULL COMPLIANCE-
complete access controls provided based on project-configurable combinations of
security classifications, user privileges and project organization.
Formal change control provided via Change Requests and Change Tasks.
The requirements management tool should output documentation in various military/commercial standard formats (490, 2167, etc.).
FULL COMPLIANCE-
user-defined templates provided, with reports producible in the following
formats: Mil-Std-490, 498, 961 and 2167; IEEE-1220; DoD-5000; EIA-632;
and C4ISR.
Cradle also allows
the user to define a desired specification format (outline) in Microsoft Word,
and Cradle will subsequently populate the appropriate fields in the outline to
produce the corresponding report.
Finally, the Web
Publisher Module allows you to publish sections of your Cradle database (or
document) as fully hyperlinked website components, with diagrams published as
hyperlinked SVG files for ease of use and display.
The tool should also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc.
FULL COMPLIANCE-
data dictionaries, acronym tables supported; spell checking available via
invoking of external text editor.
Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
FULL COMPLIANCE-
Cradle supports a wide spectrum of output formats, including Postscript, RTF,
HTML, Interleaf, SVG, FrameMaker, HP LaserJet, HPGL, EPS, etc.
The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc.
FULL COMPLIANCE
The tool should allow the user to view the document on-screen in finished format.
FULL COMPLIANCE- The
document can be viewed in either the Document Generation Module on-screen, or in
the Web Publisher Module as fully hyperlinked website components.
Tool users need to status information in the requirements management tool.
FULL COMPLIANCE-
All Cradle tools provide status information prompting the user for the function
of its UI controls, for the completeness and integrity of requirements and other
items as they are manipulated, and for both system-level and project-level
reports.
Status current technical performance of various allocated performance requirements and monitor progress towards goals.
FULL COMPLIANCE-
accomplished via combination of user defined item types (system notes)
assigned for tracking and annotation of performance related requirements
into any number of models created in the Cradle design modeling domain.
Status reporting on current compliance/non-compliance to various requirements
FULL COMPLIANCE-
accomplished via combination of user defined item types (system notes) assigned
for tracking and annotation of cross references linking requirements into the
analysis and design domain models and to supplemental project risk and issue
items.
The requirements management tool should support ad hoc queries and searches per the user’s discretion.
FULL COMPLIANCE-
complete library of more common inquiries and searches are provided, with
capability to create additional user-defined queries as needed.
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.
The tool should support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives.
FULL COMPLIANCE-
fully multi-user project database supporting distributed data sources and users;
many Cradle projects are intercontinental or international, with simultaneous
access to shared or replicated databases.
Cradle provides a
mechanism called “Alerts” to allow users to send status messages to other
users, their team, or the entire project. The Configuration Management System
(CMS) generates urgent alerts to the reviewers of information and to everyone in
the project when a baseline is opened, closed or restored.
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 COMPLIANCE-
fully user-defined access controls by the project to include: project
organizational structures (users, teams, groups); controllable item ownerships;
customizable user privileges, item and user security clearances, personnel
skills and roles; customizable user access rights to tools in the environment.
Configuration Management System (see above) provides formal change
request/action/review/control.
Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.).
What tools will your requirements management tool interface with or talk to?
DOORS, RDD, Core, RTM, SLATE, Rational Rose, Teamwork, StP, OpNet, SMA.
Cradle has a Data Converter menu that prompts the user on how to convert a data file from many of these other products into a specified Cradle import/export file.
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 COMPLIANCE- programming interface to database fully supported with open database structure specified in online documentation. Unidirectional and bi-directional message-based interface between Cradle and any external software tool is available using user-defined message formats and dialog (protocol).
Does the tool support Open Database standards such as standard query languages or exchange formats?
FULL COMPLIANCE-
yes, supports UML Modeling; RTF, MIF, OPS for document exchange; SQL via
external RDB engine; CSV for data exchange.
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 COMPLIANCE-
yes, full CSV (comma separated value) capability for data exchange.
Cradle also provides
plug-ins to directly capture Microsoft Word and Excel data as discussed in
Section 1.3.
Since the tool will be used at different sites and different projects, how does the tool exchange information between different tool installations or databases?
Cradle supports true
client/server environments for information exchange. User can also create export file for information transmission
and exchange.
Cradle also supports
fully distributed projects (e.g., international), with simultaneous access to
central or distributed data repositories by widely distributed users. This
capability means that exchanges of data between Cradle installations can be
minimized, by simply distributing the project across the organizations involved.
Does the tool support comparing/contrasting of different same-tool datasets to allow consistency and verification checking?
FULL COMPLIANCE-
Cradle provides a complete set of data consistency and integrity functions.
However, with Cradle the need for such functions is minimal, since Cradle is
fully multi-user and multi-project compatible, allowing users shared access to a
common, shared database – irrespective of how widely separated the groups
involved in the project are.
It is far better to combine all users into a single
shared repository as Cradle does, than to have to synchronize the efforts of
separate user groups into an integrated whole.
Does the tool support a single user or multiple concurrent users?
Both environments supported. Cradle is a fully multi-user environment, has provided these facilities since 1990, and has demonstrated continued success in large distributed projects.
Which platforms and operating systems does the tool run on?
UNIX
Sun: SunOS 4.1.4, Solaris 2.5 or later
IBM RS6000: AIX 4.2 or later
DEC Alpha: OSF/1 (server only)
DEC MIPS: ULTRIX
HP: HP-UX 10.20 or later
Windows
Microsoft: 95, 98, NT4, 2000, XP
Does the tool use a proprietary or commercially available database?
Proprietary database
- derivative of commercial Informix database.
Commercial SQL
engine can be attached onto a Cradle database for ad-hoc user queries if deemed
necessary by the project.
Please identify hardware/software configuration requirements:
For UNIX platforms, 16MB minimum, plus an additional 4MB recommended for second and subsequent concurrent user whose toolset will execute on same host machine.
For Windows platforms, 95 and 98 operating systems require 64MB minimum. NT and 2000 require 128MB minimum if host is also running Cradle Database Server (CDS).
Minimal for
UNIX, any configuration is acceptable. In practice, the more users there are,
the higher performance server that is needed.
For Windows
platforms, 200MHz minimum is preferred.
150 MB for UNIX.
50-150 MB for Windows, depending on software components loaded.
Does the user have the ability to run a report and look at a requirement at the same time?
FULL COMPLIANCE-
yes.
If the tool allows for multiple windows/views into the tool--does a change in one view automatically reflect in all other views?
FULL COMPLIANCE-
yes. The multiple views are enabled via a Query menu button that has been added
to allow the user to create, delete, list, view, and edit his/her personal and
site-wide query definitions.
Does the tool support graphical input and manipulation of data?
FULL COMPLIANCE-
provides multiple graphical editors including the following types: functional,
behavioral, hierarchical, process, data flow, architecture and object oriented.
Numerous notation styles within each graphical type are also supported.
If your tool supports a window’s standard, which one(s)?
Microsoft Windows.
Does the tool allow the user to create and playback commands or macros that allow the user to automate various tedious tasks?
All repetitive,
tedious tasks are automated by Cradle directly.
Does the tool allow a user to access the tool or database with a web browser?
Yes, via the Web
Access Module. This module consists of a Cradle Web Server (CWS) and a set of
template and query files. Users access via browsers pointed at the CWS, where
they can login to a database via a login screen.
Also, using report writing procedures provided in the Web Publishing Module, user can create HTML documents that can be viewed by web browser.
Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.
See Section 6.1.
Does your tool have a warrantee, if so what is it?
90 days. Annual
Maintenance Program provides free software upgrades and continuous technical
support via Hotline.
Does the tool support network licensing (floating, node locked, etc.), if so which license manager?
FULL COMPLIANCE-
Cradle has connection and tool licenses; both are floating (available from any
machine on the network) and dynamic (active when a user starts a tool, released
when user closes tool). Connection
licenses are Read-Write or Read-Only. Proprietary License Manager.
How often are software updates released; are updates separately priced items, etc.?
Major releases at least annually, available at no cost under Maintenance Program. Official upgrades also available at least quarterly, with associated newsletter to those users on Maintenance Program.
Are the users manuals online, is there online help with the tool?
FULL COMPLIANCE- Cradle comes with online help, and the Cradle CD software includes the full set of Manuals (including Primer and Tutorial) and Data Sheets in PDF format, with Browser to access and read. Users can customize online help to record project processes and procedures.
Does the tool supplier have an Internet e-mail address or World Wide Web home page location? If so, what is the Uniform Resource Locator (URL)?
E-mail: info@threesl.com
Web Site: http://www.threesl.com
What type of phone support is available from the tool supplier?
Telephone Hotline Support available 12 hours per day, 7:00am to 7:00pm (CST in US, GMT in UK)
US: 1-256-722-5020 Fax:
1-256-722-5030
UK: +44 (0) 1229 838867
Fax: +44 (0) 1229 870096
E-mail requests encouraged: support@threesl.com
13.
Training
13.1 Recommended training time
What is the
recommended training time for a user to become proficient in using the tool?
1-2 days for Requirements Management and Analysis. Additional training available for other Cradle modules.
14.1
System Modeling
The Cradle
Systems Modeling (SYS) Module provides a rich set of fully integrated graphical
modeling notations (all using the same Graphical Editor) which supports
Functional and Physical Architecture representations of the system using
traditional modeling notations, as well as the UML Object Oriented notations.
Cradle also supports Information Modeling techniques. In all, Cradle supports
close to 20 different modeling techniques that are fully integrated in the
database. These techniques are provided to support the output specification and
architecture standards discussed in Section 6.1.
Requirements
can then be allocated (and traced) to functions, behavior, processes, system
components and system software subsystems. Cradle most completely supports the
notion of Model Driven System Design (MDSD).
14.2
Performance Modeling
The Cradle
Performance Modeling (PERF) Module, a mathematical modeling tool, provides the
basis for performance assessment of system and subsystem data flow and
architecture models based on characteristics of system behavior. Cradle PERF is
a predictive tool, defining constraints on the next design level from the level
before it.
14.3
Software Engineering
A critical link
in requirements management and systems engineering activities is the allocation
and traceability into the software world. The Cradle Software Engineering
(SWE) Module provides the link between the software design and the system
implementation. Cradle SWE contains a suite of code generation, reconstruction
and reverse engineering tools to support systems developed in C, Ada, and
Pascal.
North
American Sales:
Name:
3SL Inc.
Address:
P.O. Box 310
Olney, MD 20830
Contact:
Fred W. Knopf
Phone:
301-570-6120
Fax:
301-570-6143
E-mail:
ussales@threesl.com
International
Sales:
Name:
3SL
Address:
Craven House
Michaelson Road
Barrow-in-Furness
Cumbria LA14 2RJ
United Kingdom
Contact:
Mark G. Walker
Phone:
+44 (0) 1229 838867
Fax:
+44 (0) 1229 870096
E-mail:
sales@threesl.com
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