TECHNOLOGY BUILDERS, Inc. RESPONSE to INCOSE Survey

Last Updated: January 20, January Business Meeting, Mesa AZ

1. Capturing Requirements/identification

1.1. Input document enrichment/analysis

Using existing document information (such as glossary, index, etc.) aids the user in requirement analysis, identification of requirements, etc.

Caliber-RM provides a Glossary for users to enter and define ambiguous terms to aid users in writing verifiable requirements and also terms (such as acronyms) specific to their applications and environment. These terms then can be used to promote correct usage by all users, throughout and across projects. When entering a requirement description, if a user enters a term already defined in the Glossary, Caliber-RM will automatically turn the term into a hyperlink. Users then can right-click on linked terms to open the Glossary and see the definition.

The ability to compare/contrast two different versions of a source document.

When changes are made to a requirement, that information is stored in the Change History. Users can view any version of a requirement at any time by selecting a version in the Requirement Version drop-down list. Caliber-RM also supports comparison of two different versions of a single requirement, as well as comparison of different requirements.

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

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?"

1.4. Manual requirement identification

A manual means of identifying or creating requirements.

1.5. Batch mode operation

A mechanism for inputting/identifying requirements from outside of the tool.

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

Caliber-RM can generate customized documents on demand, so users can update documents as needed. Also, Caliber-RM supports links with outside documents through document references. When a file is linked as a reference, Caliber-RM maintains that link indefinitely. If the name of the file changes outside of Caliber-RM, the link remains to the original document. If the document is updated but the name remains the same, the link is still intact.

1.6. Requirement classification

Does the tool have the ability to classify/categorize requirements during identification?

FULL

2. Capturing system element structure

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.

Yes, Caliber-RM’s robust traceability feature allows for system implementation element relationships to be established to allow impact analysis and promote a better understanding of the project. To view these relationships graphically, Caliber-RM provides both the Traceability Diagram and the Traceability Matrix. The Traceability Diagram is a graphical display (network diagram) of requirements that link to other requirements, use cases, tests, etc. and spans multiple levels. Object icons in the view allow for quick identification of object type and the user may modify the display of the objects directly from the view. Double clicking displays an information window about the object. External objects DO NOT need to be stored in Caliber-RM to be displayed (i.e. use cases).

The Traceability Matrix displays all requirement relationships in a filterable grid. These relationships may be with other requirements, development, Software Configuration Management (SCM), or test entities. Also, WBS’s, system architecture diagrams, etc. may be linked to requirements managed in Caliber-RM as external references. In addition, Caliber-RM integrates with Microsoft Project 2000, which will generate a WBS (Work Breakdown Structure) from requirements to serve as a project plan starting point.

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.

Yes, these elements may be manually entered as well as imported from a Microsoft Word Document into the repository.

3. Requirements flowdown

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.

This is supported through the Traceability feature. Requirements can be linked to any other requirements, both within the same project and across projects. In addition, requirements can be linked to related development, source control, and testing information through integrations with leading third-party object modeling, SCM, and test planning and management tools.

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.

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.

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.

Caliber-RM supports unlimited user-defined attributes allowing for many data types (i.e. text box, selection list, real, date, Boolean, etc.) which allows for the capture of this type information. Users also can link document references to requirements to provide additional supporting information.

Caliber-RM also allows user to store verification information directly with the requirement. This ensures that developers and testers have the information they need, including acceptance criteria, to verify that the requirement has been implemented properly.

4. Traceability analysis

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).

Through Caliber-RM’s Traceability Matrix feature, users can see any inconsistencies in traceability linkages, as well as be made aware of suspect links in a concise, customizable, graphical view. When a change is made to one requirement, all traces associated with it are automatically marked as suspect to indicate that other requirements may be affected. From the traceability tab stored with the requirement, users can right-click on a traced requirement to update the status of the trace. The Caliber-RM Traceability Matrix also allows users to modify the status of traces, once the link has been evaluated. Users also can select the "No Traces" button, which highlights requirements that do not link to other requirements in the current view. This allows users to easily identify orphans. The Traceability Matrix also allows users to examine the relationships between requirements and their related development, SCM, and testing information. For example, a user can easily see which requirements are still to be tested, which are attached to source control objects that have been checked out, and which are currently in design.

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.

From Caliber-RM’s Traceability Tab as well as the Traceability Matrix, users may "follow the links" to traverse any of the requirement interdependencies.

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.

User-defined attributes allow for this type of information to be recorded and stored. Caliber-RM also contains a Validation tab that can be used to store verification information and acceptance criteria for each requirement. With the test planning and management integration, Caliber-RM allows users to trace requirements directly to tests, enabling them to store the user acceptance criteria in a comprehensive test management tool and display that information in Caliber-RM.

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).

This is currently supported through an export to a spreadsheet or other similar application. Users may also export a Caliber-RM project to a Microsoft Access database from a command line. Thus, this can be scheduled to run at a predetermined interval. For example, you can set Caliber-RM up to "wake up" each night at midnight and export each of 25 projects stored in Caliber-RM to Microsoft Access format. Users may then query the freshly exported data the next morning with their query/reporting tool of choice (BusinessObjects, for example) without placing any load at all on the Caliber-RM server.

5. Configuration Management

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.

Caliber-RM captures the date, time, user, before and after values, and a comment as to the reason for the change, as well as whether the change is considered a major or a minor requirement revision.

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.

Caliber-RM supports multiple baselines for each project. They can be modified or locked only by users with the appropriate security level. Users can even choose to exclude certain requirements from a given baseline. In addition, Caliber-RM supports baseline comparison, allowing users to select two baselines to compare. Caliber-RM then displays the baselines side-by-side, with icons to indicate the differences.

Caliber-RM does versioning at the requirement level as well. When changes are made to a requirement, that information is stored in the Change History. Users can view any version of a requirement at any time by selecting a version in the Requirement Version drop-down list. Caliber-RM also supports comparison of two different versions of a single requirement, as well as comparison of different requirements.

5.3. Access control (modification, viewing, etc.)

The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.

Caliber-RM supports very granular security profiles that are assigned to groups/users in each project. Security profiles determine which projects users can access, which requirement types users can add, modify or delete, as well as the level of access to individual attributes for each requirement.

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 (MIL-STD-490, DoD-2167A, etc.).

Caliber-RM allows for customizable templates to be used that can be made to conform to a variety of military/government/industry/commercial standard output formats. These templates can then be run through the Caliber Document Factory, and the document is generated automatically. Reports may be scheduled through a scheduling tool to generate documents as needed, on either an ad-hoc or recurring basis through batch processing.

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.

Caliber-RM uses an OLE link to Microsoft Word for these features. In addition, Caliber-RM’s Glossary feature allows users to define commonly used terms as well as incorrect or vague terms so that other team members can access the definition to promote correct usage of terms.

6.3. Presentation output

Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.

Standard reports, traceability matrices and diagrams, and customizable requirement grids may be viewed and printed. Charting and graphing is done via export of the data within the Caliber-RM repository to Microsoft Excel or Access.

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.

Custom documents that include this type of data and more may be produced via the highly extensible Caliber Document Factory.

6.5. WYSIWYG previewing of finished output

The tool should allow the user to view the document on-screen in finished format.

All Caliber-RM documents are viewable in WYSIWYG format before printing.

6.6. Status reporting

Tool users need to status information in the requirements management tool.

Caliber-RM’s system Status attribute, featuring customizable values, tracks the status of each requirement. A standard Status report is available within Caliber-RM. Additional user-defined attributes may be defined for tracking various types of status.

Status current technical performance of various allocated performance requirements and monitor progress towards goals.

This capability is available through user-defined attributes. A report of this information can then be printed through the Caliber Document Factory.

Status reporting on current compliance/non-compliance to various requirements

The Caliber-RM Requirement Grid allows for flexible querying of any attribute data. The Requirement Grid can be sorted and filtered based upon attribute values and printed. In addition, customized reports may be produced using the Caliber Document Factory.

The requirements management tool should support ad hoc query’s and searches per the user’s discretion.

The Caliber-RM requirement grid allows for flexible querying and searching of requirement data and these queries may be saved and reused. In addition, the Caliber Document Factory allows users to filter and sort data for printing in a customized report. Data in the requirement grid may also be updated, allowing for bulk updates. Caliber-RM’s security profiles determine what data users can see.

Caliber-RM supports a variety of special business characters and symbols may be added through scientific keyboards, cut and paste, and through the Windows Character Map program.

7. Groupware

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.

Caliber-RM is engineered from the ground up for enterprise-wide, secure access to the requirement repository. When a requirement is being modified, it is locked and cannot be modified by another user until it is saved. By locking at the requirement level, Caliber-RM allows multiple users to work on the same project at the same time.

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.

Caliber-RM supports multiple users simultaneously working on the same project or multiple projects with multi-level access control (see #5.3 above), including approval cycles.

8. Interfaces to other tools

8.1. Inter-tool communications

Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.).

FULL

The Caliber-RM requirements repository is built on an open architecture.

What tools will your requirements management tool interface with or talk to?

• An integration with Mercury Interactive’s TestDirector is currently supported, allowing requirements to be traced to test sets, tests and test steps in TestDirector. The integration is dynamic, and changes to the status of a test are updated in Caliber-RM automatically.

• Caliber-RM also integrates with Caliber-RBT, TBI’s functional test case design tool, for more robust test case design early in the test planning process. The usage of Caliber-RBT ensures that you have maximum coverage using the minimal number of tests, and allows you to automatically create them using a sophisticated mathematical formula, instead of relying on your instincts and experience to guarantee that you haven’t overlooked any requirements, a common error. The industry average code coverage at test completion is under 50%, while Caliber-RBT based testing results in a 70% to 90% coverage during the initial pass EARLY on in your project, thereby requiring only a minimal supplement to include full coverage.

• Caliber-RM integrates with Rational Rose using the "Drag and Drop Requirements" feature described above. The integration allows for a Caliber-RM user to drag a requirement from the requirement tree in Caliber-RM and drop in onto a Rational object in Rose (a use case, a class, etc.). Once this is done, the user will now notice an association in Rose, right on their Rose tree noting that the Caliber-RM requirement is linked to the Rose object. A double-click on this association will present the user with the requirement name, description without actually having to launch Caliber-RM. Rose users are always looking at the most current requirement data available, without having to export data from Caliber-RM into Rose. Also, Rose users may be notified of requirement changes via email notification from Caliber-RM.
• Caliber-RM’s integrates with GDPro by means of an export from Caliber-RM to GDPro. GDPro then handles all synchronization (resolving added, modified, and deleted requirements.)
• An integration with SELECT Software Tools’ SELECT Enterprise also is currently supported, allowing requirements to be traced to classes, methods, packages, business processes and use cases. The integration is dynamic.

• Caliber-RM currently integrates with the following SCM (Software Configuration Management) tools: MERANT’s PVCS Version Manager & PVCS Dimensions, Rational ClearCase, and Microsoft’s Visual SourceSafe. These interfaces feature a Live-Link^TM dB Synchronization and most SCM functionality can be accessed directly from within Caliber-RM. This means that changes made in Caliber-RM automatically display in the SCM tool without any importing or exporting of information. SCM integration can be enabled or disabled on a per project basis.

• Users may export requirements to Microsoft Project, allowing requirement information to be exported to an existing project plan, or represented in a new project plan. Requirements are imported as tasks and requirement owners are identified as resources. The hierarchy of requirements is preserved.

• The Caliber-RM/ESTIMATE Professional integration allows users to export their requirements to a project in Estimate Professional. Software requirements are entered into Caliber-RM with expected, high and low effort estimates. The user then launches ESTIMATE Professional from Caliber-RM, and all software requirements and their corresponding effort estimates are automatically loaded into ESTIMATE Professional.

• Caliber-RM’s integrates with Business Objects via an export to Microsoft Access.

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).

Caliber-RM uses an open API, which TBI will make available to customers and vendors who wish to access data in Caliber-RM or build custom tools to integrate with Caliber-RM.

Does the tool support Open Database standards such as standard query languages or exchange formats?

Caliber-RM’s open API and the SQM Framework use the Common Object Request Broker Architecture (CORBA) to provide an industry standard interface for the Caliber products as well as third party and custom-developed modules. CORBA is a distributed object technology that enables the SQM system to be platform and language independent. For example, third-party and custom modules can be written in a variety of languages such as C, C++, Smalltalk, Visual Basic and Java. In addition, these modules can run on multiple platforms including Windows 3.1, Windows 95/98, Windows 2000, Windows NT, Macintosh, OS/2 and various UNIX operating systems. Furthermore, TBI makes available the Interface Definition Language (IDL) which allows third-party and custom modules programmatic access to TBI-Caliber modules and SQM Framework service objects, ensuring an open architecture.

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?

Caliber-RM provides an import facility that can import .TXT files automatically. Users can map various fields to attributes in Caliber-RM. In addition, Caliber-RM is closely integrated with MS Word and requirements can be imported manually or automatically from a Word document. Documents imported automatically can be parsed based upon text styles, delimiters, and/or keywords.

8.2. Intra-tool communication

Since the tool will be used at different sites and different projects, how does the tool exchange information between different tool installations or databases?

Caliber-RM is architected to support enterprise-wide access to a single requirements repository in an efficient manner utilizing TCP/IP.

Does the tool support comparing/contrasting of different same-tool datasets to allow consistency and verification checking?

9. System Environment

9.1. Single user/multiple concurrent users

Is the tool support a single user or multiple concurrent users?

Caliber-RM was designed for collaborate environments, supporting multiple users, both local or distributed. Caliber-RM can support more than 100 concurrent users, regardless of project or location. A Caliber-RM server can be placed in one location, and users from any location can connect to it through a modem or TCP/IP connection. Caliber-RM was architected for the Internet to ensure a fast connection with accurate data.

9.2. Multiple Platforms/Operating Systems?

Which platforms and operating systems does the tool run on?

Server - Microsoft Windows 2000 or NT 4.0 Server (Service Pack 3 or higher)

PC Client - Microsoft Windows 95/98/2000, NT 4.0 (Service Pack 3 or higher)

Web Client - Any Java-enabled web browser

9.3. Commercial vs. proprietary database

Does the tool use a proprietary or commercially available database?

9.4. Resource requirements

Please identify hardware/software configuration requirements:

Server - 125 MB minimum

Client - 50 MB minimum

10. User Interfaces

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?

Yes, Caliber-RM allows users to perform more than one activity simultaneously as it was designed for optimal performance. Using client-side caching, Caliber-RM updates only the information each user is currently viewing when changes are made. Changes made by other Caliber-RM clients will only be transmitted to another client if that data is requested. This prevents slow-downs due to excessive network traffic.

An example of multiple activities which a user could perform simultaneously within Caliber-RM include reviewing a requirement’s details via the Details tab, modifying attribute information via the Requirement Grid (for the current requirement or other requirements), modifying traceability information for yet another requirement through the Traceability Matrix, and running a report using the Caliber Document Factory.

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?

Yes, all open views of a given requirement in Caliber-RM are updated in real time with a padlock icon indicating that the requirement in question is being modified by another user (A mouse click identifies the user). Once the change is committed, all views are updated with the new value(s), and the padlock is removed.

10.3. Interactive graphical input/control of data

Does the tool support graphical input and manipulation of data?

10.4. Which window’s standard do you follow?

If your tool supports a window’s standard, which one(s)?

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?

FULL

Does the tool allow a user to access the tool or database with a web browser?

Yes, Caliber-RM has a complete browser-based Web Client with full authoring capabilities for adding, deleting, and modifying requirements. In addition, the Requirement Grid, Traceability Diagram, and Baseline Comparison functions are all supported. This client is Java-based and therefore, has the exact same look and feel as the PC client. There is no need for the users to learn to navigate in yet another interface. The Caliber-RM Web Client is the only RM web client on the market which provides full authoring capabilities, including the real-time creation of new requirements.

In addition, TBI also offer’s Caliber WebView, which allows project teams to view and comment on requirements through a standard, Java-enabled browser. Caliber WebView provides specific functionality for individuals who only need to review requirements and participate in group discussions. Currently, users can enter comments and questions about requirements, as well as update the status and priority. This component offers a lower cost alternative for distributing clients to team members that only need view and comment capabilities.

Does the tool incorporate an Undo feature? Is it multi-level?

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.

12. Support and maintenance

12.1. Warrantee

Does your tool have a warrantee, if so what is it?

12.2. Network license policy

Does the tool support network licensing (floating, node locked, etc.), if so which license manager?

Caliber-RM may be licensed either by seat or on a concurrent user basis.

12.3. Maintenance and upgrade policy

How often are software updates released; are updates separately priced items, etc.?

12.4. Online help

Are the users manuals online, is there online help with the tool?

12.5. Internet access/World Wide Web home page location

Does the tool supplier have an Internet e-mail address or World Wide Web home page location? If so, what is the address and Uniform Resource Locator (URL)?

Yes. The company’s home page is http://www.tbi.com. The product page is http://www.tbi.com/products/caliber.html.

12.6. Phone support

What type of phone support is available from the tool supplier?

Does a User's Group exist? If so, who is the primary contact?

Yes, we do have a Caliber-RM User’s Group. Pamela Davenport, Event Marketing Manager, is the primary contact. She may be reached via phone at 770-937-7822 or email at pamd@tbi.com.

13. Training

TBI provides the following training courses for Caliber-RM:

• Managing Requirements Using Caliber –RM (3 days)
• Introduction to Caliber-RM (1 day)
• Administering Caliber-RM (1 day)

Customized training is also available.

These classes may be taught onsite at your location or at one of TBI’s public training facilities located in Atlanta, GA, Dallas, TX or Parsippany, NJ.

Yes, users who have had basic training may perform software installations. Administrators need no more than one-half day to one day of training to get started with Caliber-RM. It should also be noted that administrators do not need to know Versant, Caliber-RM’s OODB, to administer Caliber-RM, as the back end is totally transparent to them. This leaves them more time to manage requirements and not the requirements management tool.

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