INCOSE Tools Database Working Group

Requirements Mgmt. Tool Survey

Last Updated: January 2000 January Business Meeting, Mesa AZ

 

Please identify which version number (1.0, 3.5 etc.) of the tool this survey refers to.  Please respond to each question with a Full, Partial or No Compliance answer.  Additional text may be included for further explanation.

 

New or revised questions for 2001 are highlighted.

 

Previous responses and summaries can be located at the INCOSE Web site at URL www.incose.org/tools 

Tool Name:_____Team-TRACE____________________________________

Tool Version:__2.1_____________________________________

 

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.

 

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.

 

PARTIAL

 

Team-TRACE recognizes Word style headings which can be imported as separate requirements.

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

 

Users can manually identify requirements within MS Word then import them directly into Team-TRACE.

 

1.4.            Manual requirement identification

A manual means of identifying or creating requirements.

 

FULL

 

1.5.      Batch mode operation

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

 

FULL

 

Team-TRACE identifies Word style headings and imports them as separate requirements, and breaks them down into their parent child relationships accordingly.

 

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

 

Not supported in this version.

1.6.            Requirement classification

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

 

FULL.

 

Team-TRACE allows users to define requirement types.

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

 

Team-TRACE gives a graphical view of the project phases as well as the links between them.

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

 

Team-TRACE can import them directly from Word or they can be entered manually.

3.          Requirements flowdown

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

 

New requirements and the links between them can be easily created.

 

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.

 

PARTIAL

 

Requirements can be grouped by type defined by the user. Additionally, users may define their own fields.

 

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

 

The linking of requirements up or down or at the same level is very simple.

 

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

 

Unlimited user defined fields can be added. The user has the ability to link a requirement to document references. Also, any comments, or objects such as graphs, tables, pictures etc can be stored with the requirement. 

 

 

4.          Traceability analysis

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

 

Team-TRACE has built in reports to allow the user to instantly identify inconsistencies, such as 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

 

By clicking on the ‘Traces’ tab a user can instantly view a requirements’ links to other requirements, be it forward, backward or at the same level.

 

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

 

The project manager has flexible levels of control. If he/she so desires Team-TRACE will record a full change history and will not allow the project to be baselined unless all requirements have been flagged ok.

 

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

 

FULL

 

Users can create their own reports and queries in access based on the data.

 

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.

 

FULL

 

Team-TRACE can automatically keep a full change history of every requirement (who, when, what and how). Team-TRACE also has a fully recorded comments field.

 

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.

 

FULL

 

A project can be baselined and at any time. It then needs to be manually saved and locked away to allow comparing and contrasting at a later date.

 

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

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

 

FULL

 

Team-TRACE has 5  levels of user privilege. Each subsequent level allowing a higher level of access and control.

 

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

 

FULL

 

Team-TRACE outputs into Word, HTML and Windows style HTML Help. Word templates can be designed within Team-TRACE and stored for later use.

6.2.            Quality and consistency checking (spell, data dictionary,etc.)

The tool should also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc.

 

PARTIAL

 

Could be done in Word once a document has been exported.

6.3.            Presentation output

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

 

FULL

 

Team-TRACE has built in ability to create its own reports and queries.

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

 

Fully customizable integration with MS Word.

 

6.5.            WYSIWYG previewing of finished output

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

 

FULL

 

6.6.            Status reporting

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

 

6.6.1.            Technical Performance Measurement status accounting

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

 

FULL

 

By using user defined fields and reporting on those.

 

6.6.2.            Requirement progress/status reporting

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

 

See 6.6.1

 

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

 

Users can build up their own queries and reports in Access.

 

6.7 Support for generation and display of special character sets, mathmatical symbols and formulas, and scientific notation,etc.

 

FULL

 

Importing objects (OLE etc)

 

7.          Groupware

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

 

Users can independently add comments to requirements and Team-TRACE supports reports about those comments.

 

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.

 

Team-TRACE supports simultaneous users working on the same or multiple projects, with 5 levels of access control.

 

 

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, PDM, etc.).  

8.1.1.            Interfaces to other tools?

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

 

FULL

 

Team-TRACE has powerful ability to import and export from Word. It can also interface with Artisan.

 

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

 

Team-TRACE is built on Access.

 

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

 

MS Access supports SQL.

 

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

 

In a Word document the data can be formatted and then imported directly into Team-TRACE, keeping the structure of the document.

 

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

 

For multi-site users Team-TRACE has the ability to syncronize data.

 

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?

 

FULL

 

Fully implemented through Team-TRACE syncronization method.

 

9.          System Environment

9.1.      Single user/multiple concurrent users

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

 

FULL

 

Multiple concurrent or single.

9.2.            Multiple Platforms/Operating Systems?

Which platforms and operating systems does the tool run on?

 

Windows 98/2000/NT4(service pack 6)

 

9.3.            Commercial vs. proprietary database

Does the tool use a proprietary or commercially available database?

 

Commercial. MS Access database.

 

9.4.            Resource requirements

Please identify hardware/software configuration requirements:

 

128 MB RAM on Microsoft Windows 98/2000/NT4

250MHz processor

100 MB disk space for installation

Server for multiple user configuration

 

9.4.1  Memory requirements (MB)

9.4.2  CPU requirements

9.4.3  Disk space requirements (MB)

 

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?

 

NONE

 

Report generation is very quick.

 

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?

 

N/A

 

10.3.            Interactive graphical input/control of data

Does the tool support graphical input and manipulation of data?

 

Not supported in this release.

 

10.4.   Which window’s standard do you follow?

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

 

Microsoft Windows standard.

 

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

 

Team-TRACE allows user defined styles for consistent report generation and data export.

 

10.6.   Web browser interface

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

 

FULL

 

Exports to HTML

 

10.7  Undo Function

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

PARTIAL

 

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

 

MS Access, Word HTML. 

 

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?

 

Tool sold on number of concurrent seats that will be in use at one time.

 

12.3.            Maintenance and upgrade policy

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

 

Updates available every 6 months. Updates included in annual maintenance cost.

 

12.4.            Online help

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

 

FULL

 

Full context sensitive help & help demo.

 

12.5.            Internet access/World Wide Web home page location

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

 

www.team-trace.com

 

12.6.            Phone support

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

 

 

Full telephone support is available during normal working hours UK time.

 

12.7  User's Groups

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

 

Not currently.

 

 

13. Training

 

13.1         Are tools specific training classes available?  What geographical areas?

 

Yes UK

 

13.2         Can training be made available at a customer's location?

 

Yes

 

 

13.3         Amount of training required to become proficient with the tool (number of days)?

 

Formal training  should not be required. Using the demo tutorial and the help guide a user can become proficient in less than a day.

Training can however be made available.

 

 

13.4         Can software installation be performed by an individual with only basic training in the tool?

 

Taining not required for installation.

 

               

14. What other requirements management features do you as a tool supplier think are important (modeling, etc.)?

 

Vendor Contact Information

 

Name: Ben Sutton

Address: Emblem House, Pynes Hill, Exeter EX2 5BA, UK

Phone: +44 (0) 1392 667788

Fax: +44 (0) 1392 667778

E-mail: info@team-trace.com

Website URL: www.team-trace.com