INCOSERMToolSurveyConsolidatedResults (1) - Kopia

INCOSE Requirements Management Tools Survey Updated 8-August-2010
Background This survey was first developed by the INCOSE Requirements Working Group in the late 1990's. Results are posted as part of the INCOSE Tools Database at: http://www.incose.org/ProductsPubs/products/toolsdatabase.aspx Information Regarding the Survey 1. This Excel file contains one tab that consolidates thirty-four responses to the Requirements Management survey as of August 8, 2010. There are also links to individual tabs for each tool as well as one displaying the blank survey instrument. WARNING: Printing the entire workbook will take a 1/2 ream of paper. 2. The Tools Database Working Group reserves the right to remove/edit answers that are blatant overstatements/misstatements about the capabilities of a particular tool. 3. All questions relating to the RM Tool survey should be directed to the Requirements Working Group (RWG) at rwg-info@incose.org. All questions relating to the completion of this RM Tool survey should be directed to the Tools Database Working Group (TDWG) at toolsdb@incose.org.
Overview of INCOSE Requirements Management Tools Survey Categories

1. Capturing Requirements/identification 2. Capturing system element structure 3. Requirements flowdown 4. Traceability analysis 5. Configuration Management 6. Documents and other output media 7. Groupware 8. Interfaces to other tools 9. System Environment 10. User Interfaces 11. Standards 12. Support and Maintenance 13. Training 14. Other Comments
INCOSE SE Tools Database: Consolidated RM Surveys

ACCEPT 360 (Updated: 9/30/2008)
Updated: 8 August 2010
Tool/Version/Update: Requirements Management Survey Questions 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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification 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. 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.
Acclaro DFSS v5 Aligned Elements Avenqo PEP v1.2 (Updated: (Updated: (Updated: 12/3/2009) 9/16/2008) 9/1/2008)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full Full
None Partial
Partial Partial
Full None
None Full
None
Full
Full
Full
Full Full
Full Full Full
Full Full None
Full Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 2 of 450

Tool/Version/Update: Requirements Management Survey Questions 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. 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. 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). 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. 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.
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None)
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 3 of 450

Tool/Version/Update: Requirements Management Survey Questions 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) None Full Full Full
Full
Full
Full
Full
Full
None
Full
Partial
Full
None
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Partial
Partial
Full
Full
Full
Full
Partial
Full
Full
Full Partial
Full Full
Full Full
Full Full
Page 4 of 450

Tool/Version/Update: Requirements Management Survey Questions 6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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. 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. 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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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?
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Partial None Full
Full Full
Partial Full
Full Full
Full Full
Full
None
Full
Full
Full
None
Full
Full
Full
Partial
Full
Full
Partial Full
Partial None
Full Partial
Full Full
Full
None
Partial
Full
Full
Full
Full
Full
Page 5 of 450

Tool/Version/Update: Requirements Management Survey Questions 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Partial Partial Full Full Partial Full Full Partial Partial Partial Full
None
None
Full
Full
Full N/A N/A N/A N/A N/A N/A Full Full
Full
Full Full Full Full Full Full Full
Full Full Full Full Full Full Full Full Full
Full Full
Full Full
Full Full None
Partial Full None
Full Full Full
Full Full None
Full Full
None Partial
Partial Full
Partial Full
Page 6 of 450

Tool/Version/Update: Requirements Management Survey Questions 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) N/A N/A Full N/A
None N/A Full Full Full Full None Full Full Full N/A N/A
Full Full Full Full Full Full Full Full Full Full Full
Full Full Full Full Full Full Full Full Full Full Full N/A
N/A
N/A
Page 7 of 450

Blueprint Requirements Center 2010 (Updated: 5/28/2010) Cameo Requirements+ v4.0 (Updated: 6/24/2010)
CASE Spec Cognition Cockpit v8.15 (Updated: v5.1 (Updated: 9/29/2008) 9/11/2008)
Full None
None Full
Full Full
Full Full
Full
None
Full
Full
Full Full Full
Full None None
Full Full Full
Full Full Full
Full
Full
Full
Full
Full
None
Full
Full
Full
Full
Full
Full
Page 8 of 450

Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 9 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Partial None Full Full
Full
Full
Full
Full
Full
None
Full
Full
Full
None
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Full
Full
Full Full
Full None
Full Full
Full Full
Page 10 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Partial Full Full Full
Full Full
None Full
Full Full
Full Full
Full
None
Full
Full
Full
None
Full
Full
Partial
Full
Full
Full
Full Partial
Full Full
Full Partial
Full Full
Full N/A Full Full
Full
Full
Full
Full
Page 11 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Partial Full Full Full Full Full Partial Full Full Full Full Full
Full
Full
Full
Full
Full Full N/A Full Full Full Full None Full
Full Full None
Full Full Full
Full Full Partial
Full Full Full
Partial Full
None Full
N/A Full
Full Full
Page 12 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) N/A Full Full N/A
Full None Full Full Full Full Full Full Full Full Full N/A
Page 13 of 450

Contour v2.4 (Updated: 9/5/2008) Core v7.0 (Updated: 09/20/2010)
Cradle 5.7 (Updated: 1/6/2009)
Dimensions RM v10.1.4 (Updated: 9/24/2008)
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full Full Full
Full Full Full
Full Full Full
Full Full Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Full
Full
Page 14 of 450

Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 15 of 450

Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Partial
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Page 16 of 450

Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 17 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full Partial Full Full Full Full Full Full Full Full
Full
Full
Full
Full
Full Full Full Full Full Full Full Full Partial
Full Full Partial
Full Full Full
Full Full Full
Full Full Partial
Full Full
Full Partial
Full Full
Full Partial
Page 18 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) N/A N/A N/A N/A
Full Full Full Full Full Full Partial Full Full Full Full N/A
Page 19 of 450

Enterprise Architect v7.1 (Updated: 2/8/2009) Envision VIP v9.0 (Updated: 10/3/2008)
IBM Rational DOORS v9.2 (Updated: 3/8/2010)
IBM Rational RequisitePro v7.0 (Updated: 9/25/2008)
None None
Full Full
Full Full
Full Full
Partial
Full
Full
Full
None Full Partial
Full Full Full
Full Full Full
Full Full Full
Partial
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 20 of 450

Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Page 21 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) None Full Full None
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
None
Full
Full
Partial
Partial
Full
Full
Partial
Full
Full
Full
Partial
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Page 22 of 450

Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 23 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Partial Full Full Full Full Full Full Full Full
Full
Full
Full
Full
Full Full Full
Full Full Full Full
Full Full
Full Partial Full
Full Full Full Full Full Full
Full Full Full None Full
Full Full Full Full Full
Full Full Partial
Full Full Full
Full Full Full
Full Full Partial
Partial Partial
Full Full
Full Partial
Full Partial
Page 24 of 450

Full Full Full Full Full None Full Full Full Partial Full N/A
Page 25 of 450

inteGREAT v4.7 (Updated: Tool/Version/Update: 3/3/2010)
Requirements Management Survey Questions 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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification 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. 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.
IRQA v4 (Updated: 10/3/2008)
Kovair Global Lifecycle v5.5 (Updated: 10/14/2008)
MagicDraw SysML v16.8 (Updated: 6/21/2010)
Full Full
Full Full
Full Full
None None
Full
Full
Full
None
Full Full Full
Full Full Full
Full Full Full
Full Full None
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Page 26 of 450

Requirements Management Survey Questions 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. 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. 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). 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. 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
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 27 of 450

Requirements Management Survey Questions 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
Full
Full
Full
Full
Full
Full
None
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full Full
Full Full
Full Full
None None
Page 28 of 450

Requirements Management Survey Questions 6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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. 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. 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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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?
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full
Partial Full
Full Full Full
None Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
None
Full
Full
Full
Page 29 of 450

Requirements Management Survey Questions 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full Full Full Full Full Full Full Full Full Full
Full
Full
Full
Full Full Full
Full Full Full Full
Full Full Full Full Full Full Full Partial Full
Full Full Partial
Full Full Full
Full Partial
Full Full
Full Full
Partial Full
Page 30 of 450

Requirements Management Survey Questions 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Page 31 of 450

MKS Integrity 2009 (Updated: 3/2/2010) PACE v3 (Updated: 3/4/2010)
Polarion Requirements V2.0 (Updated: 1/6/2009)
Psoda v5.02.1 (Updated: 3/8/2010)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full Partial
Full Full
Full Full
Full Full
None None
Full
Full
Full
None
Full Full Full
Full Full Full
Full Full Full
Full Full Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Full
Full
Page 32 of 450

Psoda v5.02.1 (Updated: 3/8/2010)
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 33 of 450

Psoda v5.02.1 (Updated: 3/8/2010)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full None
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Partial
Full
Partial
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Page 34 of 450

Psoda v5.02.1 (Updated: 3/8/2010)
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 35 of 450

Psoda v5.02.1 (Updated: 3/8/2010)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Full Full Full Full Full Full Full Full Full Full
Full
Full
Full
Full
Full Full Full
Full Full Partial
Partial Full Full
Full Full Full
Full Full
Full Full
Full Full
Full Full
Page 36 of 450

Psoda v5.02.1 (Updated: 3/8/2010)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) N/A N/A N/A Full
Full Full Full Full Full Full None Full Full Full Full N/A
Page 37 of 450

PTESY v5.4 (Updated: 9/23/2008) RaQuest v3.0 (Updated: 09/08/2008)
ReqMan v2.0 (Updated: 12/12/2008)
Reqtify v2010-1A (Updated: 1/20/2010)
Full Full
None None
Partial Partial
Full Full
None
Partial
Full
Full
Full Full Full
Full Full Partial
Full Partial Full
Full Full Full
Full
Full
Full
Full
None
Full
Partial
Full
Full
Full
Full
Full
Page 38 of 450

Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 39 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full None Full Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Partial
Full
Full
Full
Full
Full
Full
None
Partial
Partial
Full
None
Full
Full
Full
Full
Partial
Full
Full
Full Full
Partial Full
Full Full
Full Full
Page 40 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full None Full Full
Full Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
Partial
Full
Full Full
Full Partial
Full Partial
Full Full
Full
None
Partial
Full
Full
Full
Partial
Full
Page 41 of 450

Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Partial Partial Full Full Full Full Full Full Full Full
Full
None
Partial
Full
Full Full Full Full Full None Full Full Full
Full Full Full
Full Full Partial
None Full Partial
Full Full Partial
Full Full Full
Partial Full
Full Partial
Full Full
None Full
Page 42 of 450

Full Full Full Full Full Full None Full Full Full Full N/A
Full Full Full Full Full None Full Partial Partial None None N/A
Page 43 of 450

Requirements Manager (ReMa) (Updated: Tool/Version/Update: 9/9/2008)
Requirements Management Survey Questions 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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification 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. 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.
RTIME v5 (Updated: 9/9/2008)
Teamcenter Requirements v9 (Updated: 11/8/2008)
TraceCloud (Updated: 10/12/2009)
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) Full Partial Full Full
Partial Partial
Full Partial
Full Full
Partial Full
None
None
Full
Full
Full Full Full
Full Full Full
Full Full Partial
Full Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 44 of 450

Requirements Management Survey Questions 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. 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. 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). 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. 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
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Page 45 of 450

Requirements Management Survey Questions 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) None Full Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full
None
Full
Partial
Partial
Full
Full
Full
Full
Full
Full Full
Full Full
Full Full
Full Full
Page 46 of 450

Requirements Management Survey Questions 6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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. 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. 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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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 Full
Full Full
Full Full
Full Full
Full
Full
Full
Full
Full
Full
Full
Full
Full
Partial
Full
Full
Full None
Partial Partial
Full Full
Full Full
None
Full
Full
Full
Full
Full
Full
Full
Page 47 of 450

Requirements Management Survey Questions 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support
Compliance (Full, Compliance (Full, Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial, None) Partial, None) None None Full Partial Partial Full Full Full None Full Full
None
None
Full
Full
Full Full Full N/A N/A N/A N/A Full Full
None Full Full
Partial
Full Full Partial
Full Full None
Partial Partial
Partial
Full Partial
Full Full
Page 48 of 450

Requirements Management Survey Questions 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full Full Full Full Full None None None None Full Full N/A
Full Full Full Full Full Full Partial Full Full Full Full N/A
Full None Full Full Full Partial None Full Full Full Full N/A
Page 49 of 450

WTDN (Updated: 2/18/2010)
workspace.com Reqts Management (Updated: 3/4/2009)
Compliance (Full, Compliance (Full, Partial, None) Partial, None) Partial Partial
None None
Full Full
None
None
Full None None
Full Full None
Full
Full
None
Partial
Full
Full
Page 50 of 450

Compliance (Full, Compliance (Full, Partial, None) Partial, None)
None
Full
Partial
Full
None
Full
Full
Full
Partial
Full
None
Full
Full
Full
Page 51 of 450

Compliance (Full, Compliance (Full, Partial, None) Partial, None) None Full
Full
Full
None
Partial
Full
Full
Partial
Full
None
Partial
Partial
Full
None
Full
Full
Full Full
Page 52 of 450

Compliance (Full, Compliance (Full, Partial, None) Partial, None) None Full
None Full
Full Full
Partial
Partial
Partial
Full
Partial
Partial
Partial None
Full None
Full
None
None
Full
Page 53 of 450

Compliance (Full, Compliance (Full, Partial, None) Partial, None) None None None None None Partial
None
Partial
Full Full Full Full Full Full Full Full Partial Full Full
None
Partial None
None
None
Full Partial
Full Full
Page 54 of 450

Compliance (Full, Compliance (Full, Partial, None) Partial, None) N/A N/A
Full None Full Full Full Full None Full Full Full Full N/A
Full Full Full Full Full Full Partial Partial None Full Full N/A
Page 55 of 450
Accept Requirements 360

Date of Submission: 30-Sep-08
Requirements Management Survey Questions

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.
Compliance (Full, Partial, None) Comments

Full Accept 360 can import requirements from Microsoft Excel spreadsheets and tab-delimited files. In addition, users can copy and paste any rich text (from Microsoft Word, wiki pages, etc.) into the rich content sections of requirements. Accept 360 requirement elements contain far more structured data and relationships than are possible to represent in any office automation tool such as Word or Excel. No Response Added. Accept 360 can import requirements from Microsoft Excel spreadsheets and tab-delimited files. No Response Added.
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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.
None Partial
None
Full
Accept 360 provides a comprehensive requirements input capability with wysiwig rich text editor along with structured data about the requirement such as its lifecycle, priority, release assignment, ownership, stakeholders, etc. In addition, the user can specify the relationship of the requirement to other elements in the system, such as customers or prospects, market segments, marketing themes, and competitors. These relationships, which are easy to navigate forward and backward within the rich user interface, can be used for analytical prioritization of the requirements within a release, or throughout the system in a variety of what-if scenarios. Import via Excel or tab-delimited files allows batch mode requirement input.
1.5. Batch mode operation: A mechanism for inputting/identifying requirements from outside of the tool. 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 Full 56

Full Accept 360 supports requirements of different types (defined by the Accept system administrator to match the methodology of the organization), as well as definition of any number of "custom properties" for each requirement type. Using Accept 360's filtering mechanism, users can easily "slice and dice" the requirements in various ways (such as by which release they are assigned to, their status or lifecycle, to whom they are assigned, and many other options and combinations of options) so they can work with the exact set of requirements desired. This filtering capability can also be used to make selections of requirements against which to apply changes as a group.

1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification
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 The hierarchical structure of Accept 360's requirements Full system implementation (such as architecture, functional decomposition, WBS, breakdown, and the hierarchical structure of releases etc.) and display them graphically such that requirements can be linked to them. shown in Accept's Roadmaps module, both provide visualization of the overall structures of the systems under development. In addition, Accept 360 can graphically show the dependency relationships between requirements across releases, as well as the prioritization of requirements versus costs in our 2x2 analysis charts. 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 See above.
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 You can define a hierarchical requirements structure in Full derive/create additional requirements and link between them such as Accept 360 consisting of such a set of relationships (or any requirement to requirement, or requirement to text (representing trade studies) other that you desire, such as business requirement -> user to derived requirements. requirement -> functional requirement -> specification, for example). 57

Full

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.
Accept 360 includes a full "market model" including customers, segments, themes, competitors and risks. Every requirement can have weighted relationships to elements of this market model. These relationships can later be leveraged within Accept 360's Analysis module to perform analytic prioritization of requirements. 3.3. Bi-directional requirement linking to system elements: The linking of The weighted relationships between requirements and other Full requirements to system elements can be accomplished from either end of the Accept 360 elements are bidirectional and can be easily link--from the implementation back to the requirement or from the requirement navigated within the system, as well as reported on and down to the system element. used for analysis. 3.4. Capture of allocation rationale, accountability, test/validation, criticality, Accept 360 elements such as requirements, the various Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the market model components (customers and prospects, ability to attach rationale, assignments, criticality, test/validation and many other segments, themes, competitors, etc.), suggestions, defects, issues to the requirement, allocation, and the system element to which a and use cases, can all be flexibly associated with birequirement is linked. directional relationships that can be used to drive analysis, reporting, and traceability. 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 Accept 360 provides a number of reports and views that Full allow the user to identify inconsistencies such as unlinked requirements or enable inconsistencies to be flagged and addressed, system elements (orphans). including dependency management between requirements as well as orphan detection in requirement hierarchies (requirements whose parents are assigned to be implemented when they themselves are not assigned to be implemented). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Accept 360's rich user interface provides full interactive linkFull links: With the requirement links in place, the user needs the ability to follow the following, along all the relationships amongst Accept 360 links to see where they come from and where they go to. elements - requirements to their related market elements, releases to their associated requirements, suggestions to the sources (customers), and so on. 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. 58 Full Requirements support a full lifecycle model, including implementation estimates and task breakdowns (as desired), which is supported by Accept 360 table views and filtering as well as reporting.

None No Response Added.

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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Full
Accept 360 stores a complete history of all changes to all elements.
Full
Requirements and releases can be baselined, frozen, and rolled back, as needed.
Full
Accept 360 has multiple levels of permission settings, on both modules and on individual elements. Permissions can be granted to individual users, or via permission groups.
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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
Full
Accept 360 produces requirements documents in a variety of formats. Accept 360 provides a spell checker for all text and rich text entry fields. Some Accept 360 reports include charts that can be used for presentations. In addition, the Analysis module produces compelling 2x2 charts showing the strategic value versus cost of a set of requirements assigned to a plan. These charts are valuable in presentations to illustrate *why* product decisions are made. Users can define headers and footers, as well as logos and styles sheets, for all Accept 360 reports.
Full
Partial
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
59

Full Partial Accept 360 reports are generated as live HTML, and are always up to date when viewed or tested. Accept 360 reports and dashboards provide a view of the status of releases, sets of requirements, suggestions, defects, and other Accept elements. In addition customers can create their own reports with the Accept 360 Report Builder. Accept 360 provides a variety of pre-built status reports such as requirement and release status reports and a comprehensive defect history report, as well as a Report Builder with which end users can create their own reports.

6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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
6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
This information is reported in the pre-defined Accept 360 Graphical Roadmap report and is also accessible in the Accept 360 Report Builder with which end users can create their own reports. 6.6.3. Other ad hoc query's and searches: The requirements management tool Accept 360's filter capability allows for ad hoc searches and Full should support ad hoc query's and searches per the user's discretion. queries of all the different Accept elements, using logical combinations of operators the search criteria. These filters 7. Groupware: Since Systems Engineers rarely work as individuals, the ability for a team of engineers to look/work on and same information at the same time is critical. 7.1. Support of concurrent review, markup, and comment: The tool should Accept 360 is designed from the ground up to be support Full support a team of engineers reviewing, marking up, and commenting on distributed teams working together to get successful requirements or implementation alternatives. products defined, planned, created, and released. All stakeholders for an element in the system - requirements, customers, suggestions, etc. - can review and comment, and depending on permissions, change or update, the element. The notification system ensures that all stakeholders are kept up to date with any changes. Full 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. 8. Interfaces to Other Tools 60 Full Accept 360 has a multi-level permissions and access control system, covering each individual module, and the elements and hierarchies within the modules.

Full Accept 360 provides a complete SOAP-based web services API for convenient integration with third-party systems. Accept 360 supports export to Microsoft Project and Microsoft Excel, as well as import from Excel. Yes. Accept 360 provides a complete SOAP-based web services API for convenient integration with third-party systems. In addition, Accept 360 provides a simple XML data exchange capability for basic table views. Accept 360 provides a complete SOAP-based web services API, including extensive query functions, for convenient integration with third-party systems. The system also provides database views allowing access to the Accept 360 repository from standard database tools. Accept 360 supports input of most elements via Microsoft Excel spreadsheets, as well as importing elements from Salesforce.com and Siebel systems. Accept 360 provides an XML data exchange capability based on our flexible built-in table views and filters. Typically customers use a single instance of the application across their organization, due to its ability to support a global product management and planning organization Import/export features can be used.

8.1. Inter-tool communications: Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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?
Partial Full
Full
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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications
Full
Partial Partial
8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 61
Partial
None
No Response Added.
Full
Accept 360 supports multiple users, geographically dispersed, over the web.

N/A N/A N/A N/A N/A N/A Full Full Accept 360 is offered as a service hosted by Accept Software for a monthly per-user fee. N/A (Accept 360 is a hosted solution) N/A (Accept 360 is a hosted solution) N/A (Accept 360 is a hosted solution) N/A (Accept 360 is a hosted solution) N/A (Accept 360 is a hosted solution) A variety of Accept 360 windows can be open and accessible at the same time. A variety of Accept 360 windows can be open and accessible at the same time. Yes. Accept 360 provides a desktop-like look and feel, while running 100% over the Web. Accept 360 uses a rich web-based application framework (the Mozilla Gecko engine, also used in the Firefox browser and Thunderbird email client) to provide a "desktop-like" application experience in a true web application. The application is tested and supported on a Microsoft Windows desktop environment.

9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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)?
Full Full
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? 10.6 Web browser interface?
None
Full
10.7 Edit Undo Function Support 11. Standards 62
Full
Accept 360 uses a rich web-based application framework (the Mozilla Gecko engine, also used in the Firefox browser and Thunderbird email client) to provide a "desktop-like" application experience in a true web application. The application is tested and supported on a Microsoft Windows desktop environment. Accept 360 supports "Undo" in all the text editing fields.

N/A Accept 360 is a standards-compliant web-based application.

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes
None N/A Full Full Full Full None Full
Accept 360 is offered as a service hosted by Accept Software for a monthly per-user fee. The monthly hosted access fee includes maintenance and support Accept 360 includes full online help. http://www.acceptsoftware.com 866.423.8376
13.2 Training available at customer's location
Full
13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full N/A
Accept Software provides a complete menu of training options, including online, in-house, and on-site and including a variety of different courses. Accept Software provides a complete menu of training options, including online, in-house, and on-site and including a variety of different courses. 2-days to 1 week, depending on the user's role. Accept 360 is offered as a service hosted by Accept Software for a monthly per-user fee. A full market model for enabling analytical prioritization of requirements. Support for globally distributed teams. Flexible configuration options to match the methodologies existing at customers. Ability to implement the application and be successful with little or no consulting cost. Ability to access the system anywhere there is an internet connection available.
N/A
63
Acclaro DFSS v5
Date of Submission: 3-Dec-09

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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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?"
Compliance (Full, Partial, None)

Full
Partial Partial
Full
1.4. Manual requirement identification: A manual means of identifying or Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Full from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Full to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Full classify/categorize requirements during identification 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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to them.
Page 64 of 450
Acclaro DFSS v5
Full

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.
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 Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, Full 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 Full 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, Full 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. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). Page 65 of 450
Acclaro DFSS v5
Full

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. 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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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
Full
Full
None
None
Partial
Full
Page 66 of 450
Acclaro DFSS v5
6.3. Presentation output: Once the information is loaded, the requirements Full management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Partial security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements Full management tool. 6.6.1. Technical Performance Measurement status accounting: Status current Partial technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Partial compliance/non-compliance to various requirements 6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 None support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database None 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Partial ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Partial tool interface with or talk to?
Page 67 of 450
Acclaro DFSS v5
None

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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements
None
Full
Partial Partial
None
Full
9.4.2. CPU requirements 9.4.3. Disk space requirements 10. User Interfaces Page 68 of 450
Acclaro DFSS v5
Full Full

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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Partial Full None
None Partial N/A
Page 69 of 450
Acclaro DFSS v5
N/A

14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Page 70 of 450
Acclaro DFSS v5
Comments
An additional complementary utility is also available that makes it easy to extract requirement statements from verbose Microsoft Word documents.
he allocation of requirements to sub-system elements takes se sub-systems elements.
Page 71 of 450
Acclaro DFSS v5
Comments
This is a key strength of Acclaro. It not only CAPTURES various proposed system implementations, but includes a set of modules that help designers ensure that 1) the proposed architectures a) follow best design practices codified as axiomatic design strategies, b) honor constraints, c) honor critical precedence requirements, d) avoid introducing quality-reducing variation and coupling and 2) they've chosen the best solutions based on a rigorous analysis of the criteria
architecture captured, requirements are allocated to the various
ility to see the links where they come from, where they go, and
Page 72 of 450
Acclaro DFSS v5
Comments
spell check yes, data dictionary & acronym tables no
Page 73 of 450
Acclaro DFSS v5
Comments
Risk charts and Traceability Graphics yes
Not out of the box, though this could be added
Text searches yes.
eam of engineers to look/work on the same information at the
Takes input from Word (by means of a Word Add-In utility) and Windows Clipboard
Page 74 of 450
Acclaro DFSS v5
Comments
Branches of the system architecture can be exported and distributed for actions at different sites, then those branches can be re-imported by an administrator
Single user All JAVA supported systems Proprietary
Pentium (or later ) based PC Microsoft Windows compatible computer system 180 MB available ram (256 MB recommended) 60 MB of disk space (including JAVA runtime)
Page 75 of 450
Acclaro DFSS v5
Comments
ISO/TS 16949
FlexLM One year annual maintenance and updates included with purchase
ICAD conferences On-site at user facility when contracted 8 hours 3 hours Page 76 of 450
Acclaro DFSS v5
Comments
Product and project risk management and reporting linked to customer and functional requirements, requirement prioritization (via Analytical Hierarchy Processing), ability to simulate and assess various alternative solutions, tools to rigorously and scientifically judge the goodness of alternative solutions, tools to manage requirements that are contrain the choice of solutions, tools to capture and share knowledge about the requirements with other stakeholders; tools to determine if there's a necessarily required order in which functional requirements must be delivered to achieve robust operation; tools to unearth derived and lower level requirements that arise from constraints and higher level solutions; tools to mitigate requirement trade-offs (such as TRIZ tools), affinity mapping to simplify requirements handling, tools to systematically map requirements to metrics and hone in on the requirements most likely to achieve customer satisfaction (HOQ)
Page 77 of 450
Aligned Elements v1.5


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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification

Full
Full
None
Full
Full Full None
Full
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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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
Page 78 of 450

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 Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 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
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans).
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
Page 79 of 450

Full

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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
Full
Full
Full
Full
Full
Full
Full
Page 80 of 450

Full

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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full None
Full
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Full tool interface with or talk to?
Page 81 of 450

Partial

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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements
Partial
Full
Full Full Partial
Full
Page 82 of 450

Full

9.4.2. CPU requirements
9.4.3. Disk space requirements
Full
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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support
Full Full
Full Full Full
Partial Full
11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? Page 83 of 450
Full
Full Full Full

Full Full Full Full Full Full Full Full

12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
N/A
Page 84 of 450
Comments
Requirements can be imported from Word documents based on user identification and selection. The user decides whether changes to requirements in the doc should update the existing requirements in the tool or not. No automatic parsing is available.
Requirements can be imported from Word documents based on user identification and selection.
User defines and inserts requirements through natural language rich text input. Requirements can be imported from csv and xml files. No response added
The user defines and customizes requirement classification through any type and number of additional attributes.
he allocation of requirements to sub-system elements takes se sub-systems elements. The requirements and their links to other document objects (such as specifications, test cases, risks etc) are visualized in a Trace Diagram (i.e. a graph displaying the relations between the document objects) A Folder tree structure and a project-module hierarchy is used to represent the structure of a project and the relation between projects.
Page 85 of 450
Comments
"Copy" functionality exist to reuse data from one requirement to another. "Generate" functionality to propagates data from e.g. a requirement to a specification or from a use case to a test case including automatic set of trace between parent and child object. Any number and type of attribute can be added to a requirement e.g. weight, risk, cost etc.
Any document object in the system can be traced to any other document object. The forward and backward traces are visualized in several ways. Any number and type of attribute can be added to a requirement e.g. weight, risk, cost etc.
ility to see the links where they come from, where they go, and Inconsistent requirements and other document objects are clearly marked in the application. Inconsistency rules can be applied to all object types. An inconsistency summary page provides an overview of the current project status. The requirements and their links to other document objects (such as specifications, test cases, risks etc) are visualized in a Trace Diagram (i.e. a graph displaying the relations between the document objects)
Page 86 of 450
Comments
Requirement verification is governed via inconsistency rules that clearly indicate the status of each element of the project, i.e. the current status and the outstanding issues that prevent it from being complete. Performance verification is governed via inconsistency rules that clearly indicate the status of each element of the project, i.e. the current status and the outstanding issues that prevent it from being complete.
All changes made to any document object are recorded in a project history including the user, date and change comment of the event. Objects can be disabled but not deleted. The project history can be searched, sorted, filtered and compared, All requirements have a revision and can be included in baselines (called ""Snapshots""). Snapshots can be compared. Inconsistencies and trace relations for snapshots are available. User rights are governed on operations on each document object type according to FDA QSR 21 CFR Part 11.
Output can be generated in Word, partly in PDF and Excel, and exported to XML or CSV A large number of validation rules can be set up and customized to ensure consistency of all requirements. The user defines and customizes output templates. Standard templates are delivered with the installation.
Page 87 of 450
Comments
Since the main output source is Word, the output results are well visible in Word including print preview functions.
Since the main output source is Word, the output results are well visible in Word including print preview functions. Status is displayed in generated PDF reports. No Response Added
The progress is visualized through the increasing revision numbers and the state of the validation rules (i.e. on which accounts a requirement is inconsistent or not)
The user can set up and execute Queries based on a large number of filter possibilities. eam of engineers to look/work on the same information at the Specific Review functionality is integrated to ensure structured and complete capture of reviewing of all objects in the system. Access control is guided through user right management built according to FDA QSR 21 CFR Part 11.
Aligned Elements is bi-directionally integrated with Word.
Aligned Elements offers import and export possibilities via CSV and XML format to external application or data sources. Page 88 of 450
Comments
Aligned Elements offers import and export possibilities via CSV and XML format to external application or data sources. Aligned Elements is based on Nhibernate and uses SQL Sever 2005 as default database. The user can import requirements from Word or transfer it from another database or import external objects as long as they follow the Aligned Elements XML or CSV format Aligned Elements implements an XML and a CSV interface for import and export of individual data objects Full The databases can be copied from one site to another. Individual Objects, users, user groups, chapter structures can be exported and imported between application instances. Snapshots can be compared with each other or the current state of the project.
Aligned Elements is a multiclient, multi server system that supports current users. Windows XP SP2, Windows Vista Server: Microsoft SQL Server 2005 (online), Microsoft Compact Edition (offline) The database is installed a server. The client application is installed on each client computer. Server: See Microsoft's Specifications: (http://msdn2.microsoft.com/en-us/library/ms143506.aspx) Client: 1 GB RAM
Page 89 of 450
Comments
Server: See Microsoft's Specifications: (http://msdn2.microsoft.com/en-us/library/ms143506.aspx) Client: P4 running at 3.0 GHz Server: See Microsoft's Specifications: (http://msdn2.microsoft.com/en-us/library/ms143506.aspx) Client: 1 GB HD User can view and edit requirements simultaneously. Changes made by one client immediately updates all other clients (all views) The interface uses drag-and-drop and context menus extensively. Aligned Elements uses no explicit window standard but look and feel is very close to Visual Studio. The database can be accessed directly for specific actions.
URL:s can be used as part of the requirement data. All text and rich text fields uses the normal Windows undo function. Object data can be reverted to data of previous revisions of object. User management is built according to FDA QSR 21 CFR Part 11 and X.509 Class 3 for Digital Signatures
Service Packs are delivered as a part of our support offer. Floating or Node Locked client licenses are available. Aligned Elements launches approximately two major releases per year and service packs according to necessity. Page 90 of 450
Comments
User Manual is downloadable from company web site (www.aligned.ch) See www.aligned.ch for more information See www.aligned.ch for more information See www.aligned.ch for more information See www.aligned.ch for more information See www.aligned.ch for more information 2 x 4.5 hours gives full training for a normal user. Client software is downloaded from the web and installed automatically. Aligned Elements is targeted for Design History File Management in the Medical Device Industry. For such targeted support, Aligned Elements integrates Risk Analysis and Structured Reviews.
Page 91 of 450
Avenqo PEP v1.2



Full
None Full
Full
Full Full Full
Full
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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Page 92 of 450
Avenqo PEP v1.2

Full

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. 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
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the Full 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.
Page 93 of 450
Avenqo PEP v1.2

Full

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).
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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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
Partial
Full
Full
Partial
Full
Full
Page 94 of 450
Avenqo PEP v1.2

Full

6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format.
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 Full
6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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 Full
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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 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
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.). Page 95 of 450
Full
Avenqo PEP v1.2

Full

8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to?
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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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
Full
Full
Full Full Full
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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database?
Full
Full Full Full
9.4. Resource requirements: Please identify hardware/software configuration Full requirements: 9.4.1. Memory requirements Full Page 96 of 450
Avenqo PEP v1.2

Full Full Full Full

9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group
Full Full None
Partial Full N/A
Full Full Full
Full Full Full Full
Page 97 of 450
Avenqo PEP v1.2

Full Full Full Full

13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
N/A
Page 98 of 450
Avenqo PEP v1.2
Comments
Parsing input text for keywords.
no Will be implemented using the API of Avenqo PEP. The advantage of this approach is that this process is completely customizable for the user and his needs. It's included in item 1.2.
Of course. Can be developed using the API of Avenqo PEP. One way to link documents is to attache them as a file or a link to a requirement. The user can define different types of requirements e.g. functional & non-functional requirements, Use Cases etc.
he allocation of requirements to sub-system elements takes se sub-systems elements. There are different ways to show graphical information (html, gif, ) as requirement content or attachments.
Users can derive functional and nonfunctional system requirements from given customer requirements as text, graphics, documents, and many more.
architecture captured, requirements are allocated to the various Page 99 of 450
Avenqo PEP v1.2
Comments
Avenqo PEP supports different kinds of link types (in Avenqo PEP, links are called 'Traces') in accordance to the SysML. The user can define Attribute Types to provide these information to readers.
The direction of a trace is unique expressing an 'impact' factor. The users defines the appliance of the direction of a trace. Issue and Test management are integrated in Avenqo PEP. Other external information can be linked to requirements.
ility to see the links where they come from, where they go, and In Avenqo PEP different kind of Filters, Views and Reports can be used to identify issues, inconsistencies etc. This job can be done by using Trace-In and Trace-Out Views, showing the customer the impact and the source of each requirement. Each requirement has customizable attributes. Using a 'Status Attribute' will help to fulfill this request.
Page 100 of 450
Avenqo PEP v1.2
Comments
Performance requirements are stored in Avenqo PEP as non-functional requirements. These can be linked to Test Cases (as a part of Avenqo PEP Test Management) which can provide full coverage. Verification of Actuals is typically handled through the integrated Test Management Component of Avenqo PEP.
Each update of a requirement is stored including info about the changes (who, when, what was changed).
The export of Project Baselines including requirements, issues and test cases is possible. The format is XML so different baselines can be compared. Currently, we are working on a viewer. Avenqo PEP the ability to define detailed permissions on various Requirement Types. Beside this, each user can set a Lock on a requirement. Using the reporting feature of Avenqo PEP provides the ability to define any template structure for document export. The tool supports any kind of glossary. Consistency checks are supported using the report feature. Spell checking is supported, if you use an external editor like MS-Word. The report engine gives you a wide range of charts, diagrams etc. to present the quality status of requirement sets. The reports engine supports different output formats. Using MS Word as output format will provide all the required capabilities. Page 101 of 450
Avenqo PEP v1.2
Comments
A requirement can be defined as e.g. a MS-Word document or as a HTML document. In both cases the user can edit requirements in WYSIWYG editors. Also the generated documents are visible in Avenqo PEP. See 6.6.1 - 6.6.3 As per status in general, Avenqo PEP provides an ability to specify the performance status information via - user defined attributes - user defined folders where the requirements is contained - assigned Labels (Bookmarks) - assigned Tasks (internal Task Management)
In combination with the status feature, the report provides the ability to generate any kind of status report. Because Avenqo PEP is based on a SQL-Repository, any kind of query is supported concerning projects or the whole repository (database).
eam of engineers to look/work on the same information at the A specific feature called 'Discussions' allows to the user to comment and discuss requirements with selectable participants, similar to e-mails. A participant receiving a new discussion gets a notification e-mail on desk. The various user access configurations are extensive. You have the opportunity to allocate users to groups and configure individual rights to each group such as reading/writing rights to single attributes or complete requirement types. Additionally, each user having write permissions can 'lock' a requirement to protect it for changes. Avenqo PEP provides an API to support this feature.
Page 102 of 450
Avenqo PEP v1.2
Comments
RaQuest has interfaces to the following tools: * RequisitePro * Microsoft Word (Requirements Import/Export) * Microsoft Excel (Requirements Import/Export) * MS Project Avenqo PEP provides an API to support this feature.
Access is available to the underlying database via the industry standard SQL database query language. This is possible by using the API.
Currently, XML is supported see 8.2.1 - 8.2.2 The user can export complete projects and import them into a different database (installation or type). He can decide if he wants to import the whole project or just a template of a project (containing requirement and attribute types, document templates etc.). In this case a baseline should be exported from both projects and than be compared.
Concurrent users. MS Windows, Linux Commercial and open source databases (SQL Server, MySQL, IBM Derby or any other JDBC compliant database). see 9.4.1 - 9.4.3 0,5 GB Page 103 of 450
Avenqo PEP v1.2
Comments
Pentium III 1 GB Yes Yes
Different input formats are supported. Uses the look and feel of the chosen operating system (Windows, Linux).
All requirements sets can be published via web using the export feature. Provided for text and MS Word editors. Software is based on the following standards: 1. XML formats for export & data transfer 2. SQL compliant database used for repository storage 3. Java language Is part of the License Agreement. Node locked mode and company licenses Avenqo provides full software support and maintenance for Avenqo PEP. All upgrades are free of charge for customers holding valid support contracts. Avenqo PEP includes on-line help (English, German) and a tutorial. see www.avenqo.com Standard support is web-based & dial-in and office hour based. Page 104 of 450
Avenqo PEP v1.2
Comments
Avenqo offers on-site trainings. Courses can be tailored depending on customer needs. Yes, all over the world. 1-2 day user training plus 1 day administration. No installation necessary. Just copy and unzip. That's all.
There are several interesting points provided by Avenqo PEP: - Workflow Management helps to ensure the consistency of the requirements model, configurable to the specific need of our customers (V-Model, RUP, XP etc ...) - Collaboration Management improves the process of idea exchange an integrates it in the Requirements Engineering process - integration of Test Management in AVenqo PEP supports CMMI accordance concerning vertical traceability - using Project Templates to help enforce corporate standards - using of Requirements Templates to help enforce project and corporate standards
Page 105 of 450
Blueprint Reqts Ctr 2010
Date of Submission:
28-May-10


Full Blueprint Requirements Center is a product for defining, simulating and validating requirements for software development projects. You can define any type of Requirements, Glossaries, high level Business Processes, Use Cases, Actors, UI Mockups, and Data to aid in requirements analysis. Yes, with Requirements Center, you can generate a customized Word document that displays changes between selected versions of the requirements. No, we do provide the ability to automatically create a requirement by parsing another requirement. Requirements are identified by their requirement type and their unique ID.
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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
None
Full
1.4. Manual requirement identification: A manual means of identifying or Yes, you can manually create requirements. Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements You can import requirements that have been captured in a Full from outside of the tool. Microsoft Excel spreadsheet. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability If the linked document has changed, then you do not need Full to update existing linked documents from new/changed versions of the source to re-establish the link. documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Yes, Requirements are classified/categorized by their Full classify/categorize requirements during identification requirement type. 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.
Page 106 of 450

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 Yes, there are multiple ways to capture system structure. With Requirements Center you can model business processes, activity flows, and other diagrams as part of your requirements definition effort. Also, you can develop use cases within your requirements model, and add details and supporting information until your project has enough information to proceed with development and testing. Finally, creating traced relationships in your models helps you understand all the dependencies that things have on one another in a software project, and helps control the impact of change.
Yes, Requirements Center lets you capture your textual requirements in the form of hierarchical lists within your requirements model, so that you can use them as the basis for developing detailed use cases, UI mockups, data elements and operations. Requirements Center allows you to trace any element to any other element in the model. 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 Yes, Requirements Center is a requirements definition tool Full derive/create additional requirements and link between them such as that allows you to create any type of requirement and link requirement to requirement, or requirement to text (representing trade studies) between those requirements. to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, Yes, you can create your own custom properties (such as Full cost, etc.): The ability to link performance requirements to system elements weight, risk, cost, etc.) such as weight, cost, throughput, etc. This also includes the ability to allocate portions of that performance requirement to system elements. Full 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 Yes, you can switch between To and From traceability directions, which is useful if you want to trace requirements in either direction.
Page 107 of 450

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
Yes, Requirements Center provides the flexibility to customize existing Requirement Types such as allocation rationale, accountability, test/validation, criticality, issues, etc. Also, you can specify a link to an external file that may contain rationale, assignments, criticality, test/validation and many other issue, etc. 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 Yes, the Show orphan artifacts only / Show all artifacts Full allow the user to identify inconsistencies such as unlinked requirements or toggle button lets you filter the current Traceability view, to system elements (orphans). show only those elements that have no implicit or explicit trace relationship to any other element. This is useful, for example, for identifying requirements that are not linked to anything. 4.2. Visibility into existing links from source to implementation--i.e. follow the Yes, the Relationship area provides you with a way to see Full links: With the requirement links in place, the user needs the ability to follow the traceability information while you work. Hovering your links to see where they come from and where they go to. mouse over each related element displays details for that artifact. 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 Yes, there are a couple of ways to verify the requirements. Requirements Center lets you automatically generate a Customized MS Word Document. Also, the Requirements Center Simulator lets you present your requirements model in a way that is meaningful to customers, developers and business analysts. The Simulator allows you to simulate the users inter-action scenarios and to walk your audience through the behavior of your system under definition. You can also use custom properties or the staus field of the comments to identify the "verification state" of individual requirement elements.
Page 108 of 450

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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.).

Partial There is no automatic script generation, variance calculation or notification within Requirements Center, however, customers have created custom attributes that allow for the capture of actual versus allocated values, with roll up (sum) capabilities. Yes, Requirements Center provides change management functionality via the Blueprint Team Repository, which allows you to automate management of the changes you make to your Requirements Center projects and all of their contents. The Repository will maintain a history of requirement changes, who changed it, when it was done, why it was done, etc. Yes, you can create a baseline of the Requirements Center project. Also, Requirements Center allows you to visually compare two versions of the same project and display the differences. Yes, the Blueprint Team Repository maintains access control of individuals or groups having read/write access to a Requirements Center project. Yes, you can create your own Word templates (various military/commercial standard formats) to use when generating Customized Word Documents in Requirements Center. While there are multiple templates that are provided OOTB, there are not any specific "standards" templates. Requirements Center comes with its own spell checking tool, that allows you to verify the spelling in the text of your requirements and attributes.
Full
Full
Full
Full
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
Page 109 of 450

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

Partial
Charts and graphs are not supported within Requirements Center, but you can always link/attach to charts and graphs, which can be reported out. You can also export information out of Requirements Center, and develop desired charts/graphs/pivot tables in a standard solution, such as Excel or leverage the native report generation features of an existing solution, such as HP Quality Center, after data has been published to that target platform. 6.4. Custom output features and markings (user definable tables, figures, You can use the Rich Text toolbar to format the description Full security markings..): The tool should support the output of documents in field for your requirements, therefore add user definable finished form including page security markings, graphics/figures, user definable tables. tables, indexes, etc. You can also include security markings in your Word templates for Custom Word Reports. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Requirements Center lets you automatically generate a Full view the document on-screen in finished format. Customized MS Word Document, which can be viewed onscreen prior to printing/publishing. 6.6. Status reporting: Tool users need to status information in the requirements You can create your own custom property on status and Full management tool. report on that status. 6.6.1. Technical Performance Measurement status accounting: Status current Through custom properties/attributes, Requirements Center Partial technical performance of various allocated performance requirements and can track status of technical performance requirements, monitor progress towards goals. and these status "values" can be reported out via documentation. However, there is no inherent monitoring support in Requirements Center 6.6.2. Requirement progress/status reporting: Status reporting on current You can create your own custom property on Full compliance/non-compliance to various requirements compliance/non-compliance values and report on those values. 6.6.3. Other ad hoc query's and searches: The requirements management tool Yes, Requirements Center provides a model-wide search Full should support ad hoc query's and searches per the user's discretion. tool . 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.
Page 110 of 450

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 Yes, Requirements Center Package are created by you specifically for the purposes of grouping elements such that they can be edited concurrently. Also, you can view and add comments on model elements such as steps, use cases, actors, UI mockups, data objects, requirements folders and requirements. The Blueprint Team Repository maintains access control of individuals or groups having read/write access to a Requirements Center project.
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. 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
Partial
Please see 8.1.1 for ALM tools that Requirements Center communicates with. Also, with our XML export capabilities (see 8.1.2 response), there is the ability to build custom utilities should there be a need to integrate in to tools for which Blueprint has not already developed an intergration.
Page 111 of 450


Full You can export to the following ALM tools: Rational Rose lets you export your project or model for Rational Rose users (in MDL or PTL format). These formats can then be fed to additional Rational solutions, such as RSA and RSM. DOORS lets you export your requirements model into Telelogic DOORS. RequisitePro lets you export your requirements model into an existing RequisitePro project Enterprise Architect (XMI 1.3) lets you export to an XMI 1.3 file, which can be used in other UML-based tools such as Enterprise Architect. HP Quality Center lets you export your requirements model elements and test scenar-ios to HP Quality Center.
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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..)
Partial
Requirements Center provides and XML output to get access to the data outside of the tool.
N/A
Full
Requirements Center does not require a database. The Blueprint Team Repository is Subversion, which is a free/open-source version control system that comes with Requirements Center. You can import requirements that have been captured in a Microsoft Excel spreadsheet.
Partial
Page 112 of 450
Requirements Center can publish information in a structured XML format, and the schema is provided to our customer base. In addition, we have also makde available an XML Export Utility, available in our customer support Knowledge Base.

8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?

Full All information is stored in the Blueprint Team Repository. You can replicate data between two repositories.
Full
Requirements Center allows users to compare two unique data-sets / models within the product to illustrate any deltas that may exist across all requirement components.
Full Full
Yes, the tool supports single user/multiple concurrent users Requirements Center works with the following OS: Windows Server 2003 R2 Windows XP (SP2 or higher) Windows 7 Blueprint Team Repository works with the following OS: Red Hat Enterprise Linux 5.x Windows Server 2003 R2 Windows XP SP2 , Windows XP SP3 Requirements Center does not require a database. The Blueprint Team Repository is Subversion, which is a free/open-source version control system that comes with Requirements Center. Please go to the following site to see the system requirements for Requirements Center http://www.blueprintsys.com/product_rc_tech.php http://www.blueprintsys.com/product_rc_tech.php http://www.blueprintsys.com/product_rc_tech.php Not in the current version, but multi-tasking during report generation is on our roadmap. Yes, any change you make in one window is synchronized with the other views.
9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database?
N/A
9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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 Full Full Full None Full
Page 113 of 450

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? 10.6 Web browser interface?

Full Full None Yes, Requirements Center allows you to create data elements and define their initial values. Requirements Center window standard is based on Eclipse IDE Requirement Center does not support the use of macros in its current version. No Web browser interface. Given the nature of our primary user community, the normal work environment is "offline" with server connectivity necessary only to communicate with the repository server for check in/out. By keeping the work "local", users can be more mobile without having to be dependent to a server connection to access the product. There is the capability to publish Use Case and Test case assets to an HTML site in the current version, and this feature will be expanded so that all requirement elements will be generated to an HTML site for review (next Feature Pack - September/Oct 2010). Our next major release (2011) will provide full web browser capability and online/offline usage options. Yes, Requirements Center supports Undo Blueprint does not require a backend database, so any relevant standards would not be applicable to our solution. With our document generation capability, the ability to create customized document templates based on existing standrads is fully supported and Blueprint has complted and complied with our survey VPAT - 508. Per our standrad license agreement, Blueprint does provide a 90-day warranty from date of product delivery. Yes, Blueprint does support full concurrent/floating license structure via a license manager (Orion).
Partial
10.7 Edit Undo Function Support 11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full N/A
12. Support and Maintenance 12.1. Warranty: Does your tool have a warranty, 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?
Full Full
Page 114 of 450

12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?

Full Blueprint typically delivers 1 major upgrade every 12 months, and feature/services packs on a quarterly basis. These items are included in the annual support and maintenance subscription and are not seprately priced items. Yes, there are two help options. Resource Center displays the Blueprint Resource Centers Home page, which lets you obtain guidance on how to use Requirements Center via downloadable video clips and instructions. Requirements Center Help allows you to access the Help system. http://www.blueprintsys.com/ Yes, you can reach customer support via the phone. You can also reach support through our website or the support email address. Currently, Blueprint does provide a customer and executive advisory board, based on invitation-only memebrship. Blueprint does provide an interactive Knowledge Base and discussion Forum to promote an online community of user exchange and interaction. Yes, Blueprint does offer a variety of product specific training courses, and information on these classes can be found at: http://www.blueprintsys.com/Education_Training.php Additionally, Blueprint offers conceptual skills development courses aimed at best practice approaches to authoring requirements and use cases, which are then reinforced within the product itself. Yes.
12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool?
Full
12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group
Full Full
Full
13. Training 13.1 Tool specific training classes
Full
Full Page 115 of 450

13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool?

Full The complete duration of basic product training is 2.5-3 days. Typical implementation services do include a few addiitonal days of training/mentoring/consulting, but a normal deployment is going to be 1-2 work weeks before a user is fully self-sufficient. Installation takes a matter of minutes, and the most basic training program would cover 2-3 days, onsite.
13.4 Software installation with only basic training 14. Additional Comments
Full
Page 116 of 450

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

N/A The Requirements Center product suite allows you to perform the following tasks: Requirements Development: Requirements Center allows you to define, verify, modify, validate and track your software requirements, from textual requirements through to use cases, data and user interface mockups. Modeling and Simulation: Based on your requirements model, Requirements Center allows you to simulate the behavior of your future product, effectively involving all stakeholders interactively in the review, refinement and validation of your requirements. Project Documentation: Requirements Center automatically produces consistent, clear, professional documentation, in your choice of Word, Excel or HTML formats. You customize the layout and look of the documentation reports that are generated for use cases and test scenarios. UI Mockups and Simulation: Requirements Center allows you to not only build UI mockups using a pre-defined library of widgets, but also to model the details of UI event interaction. You can then interact with those screens as you move through a test-drive simulation. Automatic Generation of Test Scenarios: Requirements Center automatically generates test scenarios based on your requirements model, and provides options to extend the test scenarios into test cases, all before any code is written. Integration with Test Tools: You can generate requirements blueprints and automatically-generated test scenarios for test automation and management tools such
Page 117 of 450
Cameo Requirements+ v4.0
Date of Submission:
21-Jun-10


Full * Require DataHub to provide documents import (support CSV)
None Full Import HTML document as requirements with Glossary.
None
1.4. Manual requirement identification: A manual means of identifying or We support SysML requirements diagram schema for Full creating requirements. requirement classification. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements None from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability None to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to We support SysML schema for requirements classification. Full classify/categorize requirements during identification 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 None system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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

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. 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
Full
3.3. Bi-directional requirement linking to system elements: The linking of * Require DataHub to provide traceability function to link to Full requirements to system elements can be accomplished from either end of the element outside of the Cameo Requirements+ repository. 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, Full 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. 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 With dependency matrix we can have the traceability Full allow the user to identify inconsistencies such as unlinked requirements or coverage. system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the * Require DataHub we can trace to external data source. Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the ** Require Cameo Team Server to provide user roles Full life of the project, the requirement management tool will be used to verify that support in order to identify the requirement owner. (It is not the requirements have been met. The tool should provide the ability to fully supported in Cameo Team Server 4.0) document that the requirement was fulfilled, how it was done, and who was responsible. 4.4. Requirement performance verification from system elements (roll up of ** Require Cameo Team Server to provide full version None actuals): Once performance requirements have been allocated to system control features (Version compare) in order to support it. elements, the requirements management tool should support the verification of (This feature is not supported in Cameo Team Server 4.0) those requirements by rolling up actuals and reporting on variances (this is the allocated weight versus the actual weight). Page 119 of 450

5. Configuration MaN/Agement 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.

Full ** Require Cameo Team Server to provide a full version control, discussion board and user management in order to provide such information. (It is not fully supported in Cameo Team Server 4.0)
None
** Require Cameo Team Server to provide a full version control, discussion board, Baseline management, and user management in order to provide such information. (This feature is not supported in Cameo Team Server 4.0) ** Require Cameo Team Server to provide full user management and access security to support this features. (This feature is not supported in Cameo Team Server 4.0)
None
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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
*** Require professional services. User can create any report template from any standard. Cameo Req+ 4.1 will include some standard template.
Full
Full
We support open office impress format and Microsoft office open xml format. report engineecan generate Open Office and MS Office (Open XML only) files
Full
Full None ** Require Cameo Team Server to provide us the collaboration features and workflow in order to support it. (This feature is not supported in Cameo Team Server 4.0)
Page 120 of 450


Full ** Require Cameo Team Server to provide us the full collaboration features to integrate with other issues tracking tools in order to support it. It is now a manual process to monitor and update status. (Cameo Team Server 4.0 does not have full collaboration functionalities to fully support it yet.) ** Require Cameo Team Server to provide us the full collaboration features and integrate with our compliance in order to support it. (This feature is not supported in Cameo Team Server 4.0)
None
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 ** Require Cameo Team Server to provide us the full None support a team of engineers reviewing, marking up, and commenting on collaboration features in order to support it. (This feature is requirements or implementation alternatives. not supported in Cameo Team Server 4.0) 7.2. Multi-level assignment/access control: Access by the team to the database ** Require Cameo Team Server to provide us the full None must be tempered by multi-level access control (i.e. the ability to protect things collaboration features in order to support it. (This feature is from being modified). This also includes the ability to submit changes into an not supported in Cameo Team Server 4.0) approval cycle (for acceptance/voting) before committing the changes to the tool for everyone to see. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the * Require DataHub we can integrate with MagicDraw. Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management * Require DataHub. Any tools that have a driver with Full tool interface with or talk to? DataHub. 8.1.2. External Applications Program Interface available: To support the wide * Require DataHub. Both Cameo Requirements+ and Full variety of tools in use by engineers, the requirements management tool should Cameo Team Server 4.0 does not support open API or web have programmable access to the information contained in the tool's database services. However, this can be done with DataHub. (to get access to and deposit information). 8.1.3. Support Open database system (standard query access): Does the tool In Cameo Req+ 4.0 we support our own query language. (In Full support Open Database standards such as standard query languages or Cameo Req+ 4.5 we will support OCL and SQL as the exchange formats? query language.) Page 121 of 450

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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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 With we support image import with our HTML importer.
Full Full Full
With DataHub we can export to other Requirements management tools repository. We support cmzip merge functionality. SO it is supported in the stand alone edition.
Full
Cameo Requirements+ 4.0 support comparism on the same cmzip file. (However, the server base comparism we need Cameo Team Server to provide such functionality. This feature is not supported in Cameo Team Server 4.0)
9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users?
Full
** require Cameo Team Server. With Cameo Team Server we support multiple concurrent users. But we does not support user management and access security. All user in Cameo Team Server are administrator. Cameo Requirements+ and Cameo Team Server run at all platform that support Java. ** Require Cameo Team Server. Cameo Team Server support major database that CDO support such as Oracle, MySQL etc. Cameo Team Server support client server architecture 2GB and above Core 2 Due and above 1 GB and above (depends on data) Yes
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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?
Full Full
Page 122 of 450

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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. AdditioN/Al Comments

Full
Full Full Full Eclipse RCP We support JSR-233
None Full Full SysML and UPDM
Full None Full Full Full Full Full Full Full Full Full
We have software assurance program to give our user technical support and free upgrade. Cameo Requirements+ 4.1 will support floating license. We have a 4 releases cycle per year (2 majors and 2 minors)
a week
Page 123 of 450


N/A Domain Schema modeling and Storyboarding
Page 124 of 450
CASE Spec v8.15



Full
Comments
Full Full
Full
1.4. Manual requirement identification: A manual means of identifying or Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Import/export tools allow importing data from Full from outside of the tool. documents, spread sheets, etc 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Full to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Full classify/categorize requirements during identification 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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to them. 2.2. Textural capture of systems structure: Can the tool textually capture Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them textually such that requirements can be linked to them. 3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Page 125 of 450
CASE Spec v8.15

Full

Comments
Parent-child, peer-to-peer relationships can be established
Full
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 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 Provides complete gap analysis tools Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the Full 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. 4.4. Requirement performance verification from system elements (roll up of Full 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). Page 126 of 450
CASE Spec v8.15

Full

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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Comments
Full
Full
6. Documents and other output media 6.1. Standard specification output (if so what kind): The requirements Full management tool should output documentation in various military/commercial standard formats (490, 2167, etc.). 6.2. Quality and consistency checking (spell, data dictionary): The tool should Full also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Full management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user Full to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the Full requirements management tool. 6.6.1. Technical Performance Measurement status accounting: Status current Full technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Full compliance/non-compliance to various requirements Page 127 of 450
CASE Spec v8.15

Comments
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Import/export tools are useful. Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Full tool interface with or talk to? 8.1.2. External Applications Program Interface available: To support the wide Partial 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). 8.1.3. Support Open database system (standard query access): Does the tool Full support Open Database standards such as standard query languages or exchange formats? 8.1.4. Import of existing data from various standard file formats?______: Does Full 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) Full 8.2. Intra-tool communications Partial 8.2.1. Exchange of information between same tool, but different installations: Full Since the tool will be used at different sites and different projects, how does the tool exchange information between different tool installations or databases?
Page 128 of 450
CASE Spec v8.15

Full

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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, if so what is it?
Comments
Scalable from 1-1000's of concurrent users Windows Includes an enterprise embedded database.
1 GB RAM 1 GHZ 1 GB Hard drive
Full Full Partial
N/A Full Full
CASE Spec is a web enabled multi-tier application.
Full
Page 129 of 450
CASE Spec v8.15

Full Full Full Full Full Full Full Full Full Full N/A Online and on-site training classes are available. http://www.casespec.net

12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Comments
License manager is not required. It automatically handles licenses.
Zero configuration and administration tool. Scalability, flexibility, traceability and affordability.
Page 130 of 450
Cognition Cockpit v5.1



Full Cockpit inputs/parses requirements from standard Word and Excel template formats as well as user defined formats and styles based formats. These imports can identify and allocate requirements in any format or classification set by the user. Cockpit will import multiple versions of a source document and can do a "compare" or "view differences" on each. Cockpit inputs/parses requirements from standard Word and Excel template formats as well as user defined formats and styles based formats. These imports can identify and allocate requirements in any format or classification set by the user. Cockpit uses Active X controls for communicating with Word documents which allow user to identify and select requirements anywhere in the document.
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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
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.
Full
Cockpit has several methods to manually create requirements. Users can type requirements directly into Cockpit, share/link requirements from other Cockpit projects on their network, and drag/drop requirements from any project section to any other section. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Cockpit has several templates/formats to let users Full from outside of the tool. input/create/update requirements from outside Cockpit. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Cockpit can automatically update requirements from Full to update existing linked documents from new/changed versions of the source changed source documents without the need to re establish documents without having to re-establish traceability links. links. 1.6. Requirement classification: Does the tool have the ability to Cockpit can automatically classify requirements on Full classify/categorize requirements during identification import/creation. Users can create any classification schemes and can have more than one classification/categorization scheme in each project. 2. Capturing system element structure. Once the requirements have been captured, the allocation of requirements to sub-system elements takes Full
Page 131 of 450

Full Cockpit has a built in graphical editor (similar to Free Mind mind mapping software) that lets users create entire structures, classifications, decomposition, requirements, critical parameters, risks/failures, WBS/BOM, costs, voices, etc. This graphical mode is available at any time; users can switch back and forth between standard mode and graphical mode at any time. All changes made in either mode are automatically updated/synchronized by Cockpit. Cockpit can import/parse system structure from an external source. Users can also create system structure from within the Cockpit. All structural information created is dynamic and accessible for links with requirements, documents, risks/failures, voices, costs, etc.

Full
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various 3.1. Requirements derivation (req. to req, req. to analysis/text): The ability to Cockpit provides multiple rich methods for requirements Full derive/create additional requirements and link between them such as derivation at all levels in the requirements flowdown. All requirement to requirement, or requirement to text (representing trade studies) links between all requirements are dynamic, instantly to derived requirements. traceable links. This is a standard, out of the box function and will also work with mathematical transfer functions. For example, if a user defines a transfer function, such as an equation, to calculate a requirements current state, Cockpit will automatically derive/create sub requirements based on the equation variables. 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 Cockpit has a very powerful notion of what it calls "metrics". Examples of metrics include cost, weight, MTTR, etc. Cockpit will automatically generate metrics on demand or the user can create metrics wherever desired. Cockpit can recognize metrics and "roll up" their values to track satisfaction (for example, if cost is a performance requirement, Cockpit will know to make the rollup using a "sum with quantity and own value" algorithm.)
Page 132 of 450

Full Cockpit supports linking in all directions for all elements in the system. This includes requirements, specifications, critical parameters, costs, failures/risks, tests, voices, etc. Cockpit will automatically capture allocation of rationale, accountability, owner/author, test, etc. This is done through links created in the external source, links created internally in Cockpit, or manual links made after each item is created. It is up to the user to decide which method or combination of methods works best in each situation. All items are linked to the performance requirement, system element, and any other item in the project as needed.

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.
Full
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 4.1. Identify inconsistencies (orphans,...if so what kind of...): The tool should Cockpit has several built in functions to let users identify Full allow the user to identify inconsistencies such as unlinked requirements or items that are not linked, not documented, or orphaned. system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Cockpit includes this functionality as part of its standard Full links: With the requirement links in place, the user needs the ability to follow the configuration. This is a very powerful part of Cockpit where links to see where they come from and where they go to. users can follow any and all links instantaneously in either a text/explorer view or a graphical/tree mode. This traceability is a core part of Cockpit. 4.3. Verification of requirement (was it done, how was done): Throughout the Cockpit provides several options for users to verify Full life of the project, the requirement management tool will be used to verify that requirements including time/date stamps, approvals, the requirements have been met. The tool should provide the ability to satisfaction tracking of numerical requirements, target document that the requirement was fulfilled, how it was done, and who was convergence reporting to show a requirements trend over responsible. time, and many others.
Page 133 of 450

Full Simply put, this is the most powerful section of the Cognition Cockpit software. Cockpit supports the concept of numerical values with variation for both targets and design/process/test values on requirements. The means users can create statistical transfer functions to define the behavior of a requirement based on sub requirements in the system. Cockpit supports direct, two way, traceable transfer functions using internal formula calculations, Excel, Crystal Ball, @Risk, Minitab, Enventive, Matlab. Cockpit also supports customization to integrate with other internal analysis tools that exist at a customer site. Requirements will show verification/satisfaction indicators including design margin, Cpk, PNC, Z Score, DPMO.

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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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
Cockpit provides total trace and total history/change notification/approval for all items in a project including the entire project. Cockpit tracks the actual changes, who, when, and why. Notification of changes/approvals can be made via internal dialogs and via email. Cockpit supports full baselining and version control at the project level and at the individual requirement level. Cockpit allows user to "show differences" between versions. Cockpit provides complete access control including view only, modify, delete, approve, etc. Access control is set for individual users and/or for user groups. Cockpit has many out of the box output formats. Users can easily add/customize any formats to meet specific format needs. The cockpit rich text editor includes full spell checking.
Full
Full
Full
Full
Page 134 of 450

Full Cockpit supports generation of presentation quality graphics to Word, Excel, PowerPoint, print, etc. Cockpit supports document output including user defined output features and markings.

6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full Full Full
All Cockpit documents appear in WYSIWYG format within the Cockpit UI. Cockpit provides full status reporting on documents, individual requirements, total project, etc. Cockpit provides complete TPM management and reporting at all levels within a project and across projects.
Cockpit reports on the status of all requirements including workflow stage/completion, approval, version, predicted value (including statistical likelihood of meeting target), and other status indicators. 6.6.3. Other ad hoc query's and searches: The requirements management tool Cockpit supports comprehensive ac hoc query with a Full should support ad hoc query's and searches per the user's discretion. project and across all projects. 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 7.1. Support of concurrent review, markup, and comment: The tool should Cockpit supports team wide markup, review, action items, Full support a team of engineers reviewing, marking up, and commenting on comments, and approvals at any level or item in a project. requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Cockpit provides multi level access control / privileges for all Full must be tempered by multi-level access control (i.e. the ability to protect things items in a project and for all users of a project. This includes from being modified). This also includes the ability to submit changes into an view/modify/delete privileges as well as submit for approve / approval cycle (for acceptance/voting) before committing the changes to the tool approve privileges. for everyone to see. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Cockpit supports XML, Excel, and Word formats to transfer Full ability to communicate requirements to other domain-specific design tools requirements and other data to and from other domain (CASE, EE, etc.). specific design tools. Cockpit also supports exchange through modeling such as UML / SySML. 8.1.1. Interfaces to other tools: What tools will your requirements management MS Word, MS Excel, MS PowerPoint, SMTP mail, Crystal Full tool interface with or talk to? Ball, @Risk, Matlab, Enventive, Minitab, PLM/PDM (various), other Req Mgt. tools. Page 135 of 450 Full

Full Cockpit comes standard with a complete API.

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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full
Cockpit supports several query access methods.
Full
Full Full Full
Cockpit has standard import templates from MS Word and MS Excel to create structures within a Cockpit project with having to re enter information by hand. These standard import template file formats can be altered by the user as necessary. Cockpit uses XML as it standard for all data exchange. Other standards are available to users as needed. Cockpit supports exchange of project information to different installations via standard XML.
Full
Cockpit checks for consistency, duplicates, errors, etc.
Full
Full
9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements
Full Full Full
Cockpit is designed as a multi user tool with simultaneous access by multiple users in multiple locations all through a web browser. Cockpit server is a Windows application. Cockpit client is platform independent and only needs users to run MS Internet Explorer 6 or higher. No client installation of Cockpit is required. Cockpit uses a standard commercial database called Object Store from Progress Software. For client/end user, no special requirements. For server, contact Cognition for IT whitepaper. For client/end user, no special requirements. For server, contact Cognition for IT whitepaper.
Page 136 of 450

Full Full For client/end user, no special requirements. For server, contact Cognition for IT whitepaper. For client/end user, no special requirements. For server, contact Cognition for IT whitepaper. Cockpit fully supports users performing multiple tasks at the same time including running a report while looking at/editing a requirement at the same time. Cockpit supports multiple views including standard text/explorer mode and a built in graphical mode (and others.) Each of these modes acts on the same objects in the database so all information is by definition automatically updated and current. Cockpit comes standard with a built in graphical mode very similar to Free Mind mind mapping software. Cockpit uses a Microsoft Internet Explorer User Interface using Web 2.0 technologies. Cockpit is executable via scripting such as XML and Java.

9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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
Full
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? 10.6 Web browser interface?
Full Full Full
Full
Full
Cockpit comes standard as a browser based application. For user access the only way to use Cockpit is through a browser. Cockpit provides several methods to undo or return to a previous state or condition within a project. Cockpit supports ISO standards such as 14971 and others, mil standards such as 961E and others, SQL / ODBC queries, COM, OLE, MS Word formats, MS Excel formats, and the Cockpit's built in graphic interface.
N/A
Full Full
90 days Cockpit includes a license manager and comes standard as floating licenses.
Page 137 of 450

Full Major Cockpit updates are typically once per year with minor releases as necessary. All updates are included to any user under a current maintenance contract and to any user under a current subscription/lease contract. Cockpit help is available online as downloadable files and also as pop up help tips. http://www.cogntion.us Cockpit is supported via phone/fax/email/in person as needed. Most support is standard business hours. Special extended hours support is available for a small additional charge. Yes, contact Cognition for details. Cognition offers several courses for all levels of Cockpit users both at Cognition sites and on site at the user's location. Yes, Cockpit training is available at user's location. Cockpit training is standard one day for standard user and three days for lead user/administrator. Cockpit installation requires minimal or no assistance from Cognition. Cockpit is provided with full instructions with the software and online.

12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier?
Full Full Full
12.7 Support User's Group 13. Training 13.1 Tool specific training classes
Full Full
13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Full Full Full
14. Additional Comments
Page 138 of 450

N/A Cockpit redefines the phrase "Requirements Management" to include more of the Product Development Process including Voice of Customer management, FMEA/Risk Management, Cost Management, Critical Parameter Management, and V&V/Test Management. The combination of these activites in a single workspace with a single UI and a single database provides users with more visibility into the entire system. Cockpit allows dynamic, live traces between any parts in the model. For example: trace from a process capability on a low level input to specifications, requirements, Voice of Customer, suveys/interviews, and risks/failures/mitigations. This comprehensive connection of information brings a true systems engineering approach to Requirements Management. In addition, Cockpit allows requirements to be "active", with numeric targets and numeric values. Cockpit runs transfer functions through complex internal formulas as well as through two way connections with third party software (Excel, Minitab, Crystal Ball, Enventive, @Risk, Matlab) to "roll up" variation throughout the requirements structure. This gives a true statistical likelihood of satisfaction for any requirement and enhances a true

Page 139 of 450
Contour v2.9


Full Provides requirement name, unique ID, description and other reportable attributes such as status, owner, priority, etc. All drop down fields customizable by project Full version and change history in side-by-side view. Import utility for multiple sources of requirements and other project data Ability to "tag" requirements via MS Word styles
Full Full
Full
1.4. Manual requirement identification: A manual means of identifying or Easily add new requirements and other items through menu Full creating requirements. or project tree 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Robust import function from MS Word of Excel Full from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Linking allows user to maintain links without having to reFull to update existing linked documents from new/changed versions of the source establish links after updating documents. documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to User definable classification by project Full classify/categorize requirements during identification 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 Contour itself isn't a system modeling tool, but it can link to Partial system implementation (such as architecture, functional decomposition, WBS, and graphically display visual diagrams within the UI. In etc.) and display them graphically such that requirements can be linked to them. addition custom integrations with Ravenflow, Autodesk DRAW or other modeling tool are available. 2.2. Textural capture of systems structure: Can the tool textually capture Explorer tree provides flexibility for hierarchical project Full system implementation (such as architecture, functional decomposition, WBS, organization etc.) and display them textually such that requirements can be linked to them. 3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Page 140 of 450
Contour v2.9
Full Rich traceability functionality allows users to setup relationships (both list and visual relationship tree) between requirements, use cases, defects and any items in the system (even cross-project) Requirements may be assigned to various attributes such as estimates, risks, assigned to, etc.

Full
3.3. Bi-directional requirement linking to system elements: The linking of Any artifact (item) in the system may have trace Full requirements to system elements can be accomplished from either end of the relationships established. Each item displays both forward link--from the implementation back to the requirement or from the requirement and backward trace links. down to the system element. 3.4. Capture of allocation rationale, accountability, test/validation, criticality, Along with detailed requirements attributes, each Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the requirement may be linked to use cases, test cases, tasks ability to attach rationale, assignments, criticality, test/validation and many other and other items within the system. Requirements may be issues to the requirement, allocation, and the system element to which a assigned a priority and status. Estimates tracked along with requirement is linked. requirements 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 Contour includes a traceability matrix for graphically viewing Full allow the user to identify inconsistencies such as unlinked requirements or and establishing trace relationships. Trace matrix provides system elements (orphans). visual insight into missing links. 4.2. Visibility into existing links from source to implementation--i.e.. follow the Links are clickable within the system so users can easily Full links: With the requirement links in place, the user needs the ability to follow the navigate to other items and explore relationships. links to see where they come from and where they go to. 4.3. Verification of requirement (was it done, how was done): Throughout the Status and other requirement attributes along with Full life of the project, the requirement management tool will be used to verify that traceability track verifications. 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. 4.4. Requirement performance verification from system elements (roll up of Available through roll-up reports that calculate summary Full actuals): Once performance requirements have been allocated to system values based on dependencies 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). Page 141 of 450
Contour v2.9
Full Contour tracks all changes made to requirements for full version history. Requirements are versioned with each save automatically. History tab provides list of changes, dates and by user. The compare feature provides side-byside comparison of 2 versions with differences highlighted. User may save and load multiple baselines. Contour includes baseline reports.

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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
Full
Granular users, groups and roles provide detail level security.
Full
All reports can be generated as Word, Excel, CSV, PDF, Text or XML formats. Spell check is included through browser as well as glossary.
Full
Full
Contour includes enterprise reporting engine for custom professional reporting of both textual and graphical data. Custom reporting is available.
Full
Full
Full
6.6.1. Technical Performance Measurement status accounting: Status current Full technical performance of various allocated performance requirements and monitor progress towards goals. Page 142 of 450
Contour provides both inline editing of requirements documents as well as preview of all reports in multiple formats. Contour provides a number of reports and status summary views such as project dashboards that give users immediate access to the status of projects. Can report on status vs. goal
Contour v2.9
Full

Contour includes widely adopted BIRT reports for internal reporting. All reports are fully customizable and use XML and CSS for formatting. 6.6.3. Other ad hoc query's and searches: The requirements management tool Contour offers rich search and ad hoc querying (filters) Full should support ad hoc query's and searches per the user's discretion. within the system, and also through the custom reporting engine. 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 Contour is a collaborative, Web-based application built for Full support a team of engineers reviewing, marking up, and commenting on team interaction with inline discussions, push/pull email requirements or implementation alternatives. notifications, tags and workflow 7.2. Multi-level assignment/access control: Access by the team to the database Contour includes granular control over permissions and Full must be tempered by multi-level access control (i.e. the ability to protect things security to edit/delete items. 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Contour is built on open standards allowing for rapid Full ability to communicate requirements to other domain-specific design tools integration with other tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Contour currently integrates with Selenium for test Full tool interface with or talk to? automation and custom integrations available with Atlassian JIRA, Microsoft Project, Ravenflow, Autodesk DRAW, Siemens Teamcenter, HP QualityCenter and Jive Clearspace 8.1.2. External Applications Program Interface available: To support the wide Contour is fully customizable through CSS for user Full variety of tools in use by engineers, the requirements management tool should interface, language packs for internationalization, XML and have programmable access to the information contained in the tool's database Web services for custom interfaces (to get access to and deposit information). 8.1.3. Support Open database system (standard query access): Does the tool Contour is built on Hibernate for database independence as Full support Open Database standards such as standard query languages or well as object query support. exchange formats? 8.1.4. Import of existing data from various standard file formats?______: Does Contour supports a full set of import formats. Full 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) XML Full Page 143 of 450
Contour v2.9
Full Built for enterprise-wide deployment with department/team level control over projects, data, users, etc. Contour is a rich Web application designed to be highly scalable and support multiple teams or departments within one enterprise installation. Security can be set at an organizational or team level, or project-by-project based on the needs of the customer. Contour's database provides XML import/export and allows for comparisons between different data sets

8.2. Intra-tool communications
8.2.1. Exchange of information between same tool, but 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
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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users?
Full
Full
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements:
Full Full Full
Contour is designed for single user or concurrent user access across enterprise-wide deployment. Contour is available as a Web-based app installed locally (no client to install) or it can be fully hosted by Jama as Contour OnDemand with zero software/hardware requirements Contour works across multiple platforms: Windows, Linux, Unix, Solaris, Mac Multiple - MySQL, SQL Server, HSQL, etc. Dependent on installation & number of users; for basic system requirements we recommend a minimum of 512MB memory allocated to the Contour application and 20GB disk space for a 15 user setup. Using Contour as a document repository may require additional disk space. Min 512 MB, but varies based on # of users. Varies based on # of users. 20 GB, but varies based on # of users. Contour provides a tabbed user interface for multi-tasking within the web-browser. Contour utilizes an event-driven architecture, such that changes made will be reflected immediately within the system
9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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?
Page 144 of 450
Contour v2.9
Full Drag and drop within the browser; Contour mimics the full functionality of enterprise desktop application but within a browser. Web standards, CSS. Contour supports Firefox and Internet Explorer. Contour allows for saved filters, search, report automation and copy/reuse of projects, requirements and other items Contour is a pure Web application, the entire application is built for Web browser interface Roll-back to previous saved version, undo in editor Custom reports and templates built for industry-specific requirements documentation standards for aerospace, medical devices, etc. such as DODAF, MODAF, CMMI Included with support plan Can buy Contour as single named user, floating user or as fully hosted On-Demand service All product upgrades and maintenance included with support plan Full documentation, online support and user forum available at Jama Backstage http://www.jamabackstage.com http://www.jamasoftware.com Phone, email and Web support available from 8am - 5pm PDT with International partners in Europe, Australia, South America http://www.jamabackstage.com 1-day and multi-day training sessions available, administrator training provided free with Contour Base Package Both web training and on-site training options available, customized for individual customers

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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes
Full Partial
Full Full N/A
Full Full Full Full
Full Full
Full Full
Full
Page 145 of 450
Contour v2.9
Full 30 minutes for implementation and quick start; 1-day training for end-users to become proficient with Contour. Contour is designed to be intuitive with inline editing, drag & drop, easy add/edit of new projects and requirements Installation, configuration and basic training provided free with Contour Base Package Requirements reuse, Impact analysis, Change request management, Task management, Team collaboration, Project workflow, Defect/Test management, Product management & release planning

13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full
N/A
Page 146 of 450
CORE v7.0


Full
CORE can import data using standard file exchange formats such as ASCII, Rich Text Format (RTF), Microsoft Word, Microsoft Excel, etc. There are several mechanisms for input, including parsers (formatted text and delimited text), semiautomatic (select and transfer), and manual entry. Input scripts can also be modified to equate different parts of documents and/or header information to requirement names, types, and hierarchy location. CORE's scripting capabilities can easily facilitate the comparison/contrast of two different versions of a source document or identify changes to a source document relevant to an existing project data base. CORE provides an automatic parsing utility. The time required to capture requirements is dependent on their format. For example, 100 requirements contained in an EXCEL file or other parsable format can be automatically parsed in just seconds. Input scripts can also be modified to equate different parts of documents and/or header information to requirement names, types, and hierarchy location. CORE's easy-to-use Element Extractor feature allows the user to easily import information into the database using simple text formats (ASCII, Rich Text Format-RTF) or Microsoft Word or Excel file formats with a click of a button. Users may then decompose elements, such as Requirements or Documents, into lower level elements by linking them with an appropriate relationship. CORE's Database Editor allows quick and easy entry of new requirements. When entering data from source documents, the Element Extractor is helpful for analyzing requirements and eliminating compound requirements and ambiguous language.
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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
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?"
Full
1.4. Manual requirement identification: A manual means of identifying or creating requirements.
Full
1.5. Batch mode operation: A mechanism for inputting/identifying requirements from outside of the tool.
Full
CORE's .csv parser and .xml import capabilities provide the ability to pull in requirements from most external data sources.
Page 147 of 450
CORE v7.0
Full Documents created from a CORE project file automatically include new and/or changed requirements imported from external data sources.
While utilizing CORE's Element Extractor in identifying the requirements, one can simply change the classification of requirements (Type attribute) and categorize the them (Origin attribute) at the same time.

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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification
Full
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. CORE is founded upon the concept of using models to support 2.1. Graphically capture systems structure: Can the tool graphically capture Full systems engineering. Graphical representations are key to system implementation (such as architecture, functional decomposition, WBS, providing the necessary understanding and communications to etc.) and display them graphically such that requirements can be linked to them.
engineer a successful system or process. Representations available within CORE include: expanded functional flow block diagrams (eFFBDs), physical block diagrams (PBDs), functional flow block diagrams (FFBDs), IDEF0 or data flow diagrams (DFDs), interface charts (N2), and hierarchy diagrams. A white paper addressing this in detail is available in the Vitech Technical Library on the web: http://www.vitechcorp.com In addition to the graphical views, each element within the integrated design repository can be displayed in an easy-to-use text view so that all information associated with the element can be viewed and edited: name, number, description, attributes, relationships, targets, etc. All requirements and system definition elements can be traced back to appropriate project/WBS elements.
Full
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. CORE allows the user to allocate, link, build relationships 3.1. Requirements derivation (req. to req, req. to analysis/text): The ability to Full between requirements, originating documents, physical structure, derive/create additional requirements and link between them such as etc. requirement to requirement, or requirement to text (representing trade studies) to derived requirements.
Page 148 of 450
CORE v7.0
Full
CORE allows the user to create/manipulate many attributes of the requirements, functions, physical components, etc, through that element's property sheet; weight, cost (units), value, KPP, etc. The assignment of risk to a requirement is performed by creating a risk element and linking the two through the System Definition Language's "caused by" relationship. CORE's inherent System Definition Language automatically links elements within the database in the reverse direction of that created (i.e. When a requirement is given a relationship to a lower level requirement of "refined by" the child requirement will automatically be assigned the relationship to the parent of "refines." CORE allows the user to create/manipulate many attributes of the requirements, functions, physical components, etc, through that element's property sheet; weight, cost (units), value, KPP, etc. The assignment of risk to a requirement is performed by creating a risk element and linking the two through the System Definition Language's "caused by" relationship.

Full
Full
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. CORE includes a variety of utility checks to monitor and identify 4.1. Identify inconsistencies (orphans,...if so what kind of...): The tool should Full element relationship inconsistencies and orphaned requirements. allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). Complete traceability can be scene graphically both graphical and 4.2. Visibility into existing links from source to implementation--i.e.. follow the Full through easy navigation through the data set. Traceability can links: With the requirement links in place, the user needs the ability to follow the also be queried and reported on. links to see where they come from and where they go to. CORE incorporates the ability to trace requirements through 4.3. Verification of requirement (was it done, how was done): Throughout the Full verification objectives to actual test events, and can be used to life of the project, the requirement management tool will be used to verify that automatically construct test planning documentation. 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.
Page 149 of 450
CORE v7.0
Full CORE provides for attribute fields to be included as part of mathematical operations that "roll up" requirement distributions/allocations such as weight.

Full
CORE records information on: who made the last change, when the change was made, what was changed, and when the element was last exported to file. Each user may have a unique login name and password that governs what information they have access to. CORE records the username and time of the last attribute change for each element in the database.
Full
Previous versions of requirements can be tracked, viewed, and reverted to through CORE's version control utility.
Full
CORE provides a fully featured Access Control capability through a user administration tool that allows the definition of users, system privileges, creation and assignment of user groups, and permission grating by group or user access to projects and elements within each project. 490, 498, 632, 2167, and DoDAF
Full
Full
Full
CORE includes standard spell checking, data dictionary, etc. CORE allows you to check within a single element or within the entire database and any portion thereof. Creation of glossaries and acronym lists are supported. CORE is delivered with a robust script generator that allows the generation and tailoring of output reports in user defined format, including tabular and multiple graphical output styles.
Page 150 of 450
CORE v7.0
Full
CORE is delivered with a robust script generator that allows the generation and tailoring of output reports in user defined format. A Rich Text Format (RTF) output feature allows Microsoft Word to read, edit, and print the produced documents. CORE is delivered with a robust script generator that allows the generation and tailoring of output reports in user defined format. A Rich Text Format (RTF) output feature allows Microsoft Word to read, edit, and print the produced documents, real time, on the screen in its finished format. The CORE user interface provides the ability to edit the status fields of all element classes including requirements at any point in time. CORE provides the ability to query and report on the status of requirements satisfied through linkages to functional and physical design elements and verification. CORE includes the capability to filter, query, and report on the status of requirements satisfied through linkages to functional and physical design elements. CORE comes with a drag and drop based query builder (Script generator) to allow the generation or editing of queries. CORE also provides the ability to do simple queries by specifying

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. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full
Full
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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. Through using a CORE Enterprise Server License & multiple 7.1. Support of concurrent review, markup, and comment: The tool should Full Enterprise Client Licenses, multiple users may interact with the support a team of engineers reviewing, marking up, and commenting on design repository at any point in time. Updating/changing element requirements or implementation alternatives.
attributes are only limited to the first user to access the element having changing rights until they "release" the element for another to work with. Each program must assign an administrator to the CORE Database, who can assign multi-level access control through all elements and the all lower level attributes, as well as accept or reject changes.
7.2. Multi-level assignment/access control: Access by the team to the database Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). Page 151 of 450
CORE interfaces to DOORS, RDD-100, Vital Link, Software thru Pictures, Rational Rose, Microsoft Office (Word, Excel, PowerPoint), Microsoft Project, and many others.
CORE v7.0
Full
CORE interfaces to DOORS, RDD-100, Vital Link, Software thru Pictures, Rational Rose, Microsoft Office (Word, Excel, PowerPoint), and Microsoft Project. CORE's C/C++ API provides open access to the database from other engineering or project management tools or applications. Thus, CORE's database can be utilized as a central repository for all project-related data. CORE provides support via simply query language and data exchange via .xml files. CORE can import data using standard file exchange formats such as ASCII, Rich Text Format (RTF), Comma Separated Variable (CSV), XML, etc. CORE is able to produce and accept XML files. The purveyors of CORE are working with the AP-233 standard community.

8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..)
Full
Full
Full
Full
8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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 Full
Should an Enterprise Server/Client license be employed, all the "clients" directly interact with the same database, housed on the Enterprise server. Location has no effect on this. Should several Workstation Licenses be employed an ultimate Administrator of the database will need to retrieve database updates from the outlying other Workstations and integrate them. This instantiation can be accomplished by generate a script to perform the comparing/contrasting between the various received database updates.
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? 9. System Environment
Full
Page 152 of 450
CORE v7.0
Full
CORE supports both. Single and multiple concurrent users are supported via our Workstation or Enterprise products. In addition, the CORE2net Enterprise Web Server provides access to all information and models contained in a CORE database. A separately licensed component of the CORE Enterprise Server, CORE2net turns the CORE Enterprise system into a Web server. CORE2net users require only appropriate access permissions and an Internet Browser. CORE2net is a "CORE viewer" that does not require any special software to be installed on a user's workstation.CORE2net makes the information contained in CORE available to an entire organization. System engineering, like every other art or science, has creators and consumers. The creators are the engineers that create systems engineering designs. The consumers are the rest of the world that needs access to the work of the creators. CORE is a product designed for the creators; CORE2net is for the consumers.The CORE2net Enterprise Web Server is compatible with Internet Explorer and Netscape.

9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users?
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database?
Full Full
CORE can run on Windows 98/NT/ME/2000/XP/2003/Vista. CORE utilizes a true object oriented database (OODB) in both versions: CORE Workstation and CORE Enterprise. To produce an integrated and executable model of an architecture, an OODB is critical for this type of application as it allows for each element of an architecture definition to be treated, stored, and accessed as an object. Utilizing an OODB also facilitates the export of entire architecture definitions to one data file such as an XML file. It also allows organizations to easily modify the meta-model to suit their needs without impacting the functionality of the tool. For CORE Workstation, a proprietary OODB is utilized. For CORE Enterprise, a third party OODB from Gemstone Systems Incorporated, is utilized. Both versions interoperate and can be utilized in one environment. To the user, the difference between the versions of CORE and the associated database engines is not perceptible.
Page 153 of 450
CORE v7.0
Full
CORE is not a resource-intensive application. A simple rule of thumb is to determine if your machine is capable of running Microsoft Word XP. If so, your system can run CORE. CORE is not a resource-intensive application. A simple rule of thumb is to determine if your machine is capable of running Microsoft Word XP. If so, your system can run CORE. For Workstation installation: 1 GHz processor or higher. The faster the CPU, the faster script and simulation (using COREsim) execution will be. For Workstation installation: 100 MB free disk space for the software, documentation and online help files. Additional disk space required for CORE Workstation project databases.

9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements
Full
Full
Full
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? 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? 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 Full
CORE provides the ability to easily work on multiple tasks with various methods to enter data or execute tasks. Yes, the tool allows multiple activities to be performed at the same time. Should a change be made to a requirement while another user is viewing that requirement, the viewing user would see the changes real-time. CORE dynamically generates views and diagrams directly from the database ensuring that views are consistent with current design details.
Full
Full Full
All currently supported releases.

The addition of discrete event simulation capability to CORE with the COREsim option allows execution of the integrated architecture by dynamically interpreting the behavior model that resides in the system design repository. Discrete-event simulation logic identifies timing, resource utilization, and model inconsistency. CORE is delivered with a robust script generator that allows the generation and tailoring of custom scripts as well.
Page 154 of 450
CORE v7.0
Full
The CORE2net Enterprise Web Server provides access to all information and models contained in a CORE database. A separately licensed component of the CORE Enterprise Server, CORE2net turns the CORE Enterprise system into a Web server. CORE2net users require only appropriate access permissions and an Internet Browser. CORE2net is a "CORE viewer" that does not require any special software to be installed on a user's workstation. CORE2net makes the information contained in CORE available to an entire organization. System engineering, like every other art or science, has creators and consumers. The creators are the engineers that create systems engineering designs. The consumers are the rest of the world that needs access to the work of the creators. CORE is a product designed for the creators; CORE2net is for the consumers. The CORE2net Enterprise Web Server is compatible with Internet Explorer and Netscape. CORE 7.0 has a versioning feature that will track all attribute changes, allowing you to quickly review and revert back to previous iterations of text. CORE is compliant with several engineering standards, including IEEE-1220, EIA-632, Mil-Std-490A, DoDAF 1.0,1.5,2.0, and 7 of the 9 of SysML diagrams. The tool was built as a System Architecting tool and is intended to support variations in engineering process and reporting standards. Information contained within the tool repository may be expanded to allow compliance with most of todays evolving standards. Vitech is an active participant in emerging efforts for ISO10303-233 (AP233) the standard for systems engineering data exchange and the Object Management Group's Systems Modeling Language (SysML).

10.6 Web browser interface?
10.7 Edit Undo Function Support
Full
11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
N/A
12. Support and Maintenance 12.1. Warranty: Does your tool have a warranty, if so what is it?
Full
Vitech offers a 30 day warranty on all software products. Subscription to the annual Maintenance Plan includes all upgrades and telephone/email technical support.
Page 155 of 450
CORE v7.0
Full Full
CORE supports three licensing options: USB key, node-locked, and network licensing mechanisms. CORE publishes two feature enhancing releases per year; and service packs as needed. All releases and service packs are included in the Maintenance plan. All support information is available on-line. Additional information is available on-line as well, including methodology, project samples, case studies, technical notes, Department of Defense Architecture Framework resources, and Capability Maturity Model information. http://www.vitechcorp.com; info@vitechcorp.com The CORE support hotline is staffed 10 hours per day (EST Business hours) by Vitech employees located in the United States. Messages are recorded at all other times. E-mail requests are preferred for quickest response and can be submitted via the website or sent to support@vitechcorp.com. CORE has an formal Users Group that meets twice a year. There is also a web-based CORE Users Group with a wealth of resources available to users. Vitech offers introductory and advanced CORE-specific training classes that are scheduled on-site at our client's location: Modelbased Systems Engineering with CORE; CORE Quick Start Course; CORE Refresher Course; Fundamentals of CORE Scripting; and Model-Based Systems Engineering for Business. Vitech also offers custom on-site training and and various WebEx's and workshops addressing a broad range of topics. All of the CORE training courses can be delivered at a customer location: Model-based Systems Engineering with CORE; CORE Quick Start Course; CORE Refresher Course; Fundamentals of CORE Scripting; and Model-Based Systems Engineering for Business. Our worldwide representatives also offer convenient CORE training upon request. Courses may also be tailored to the customer's needs.

12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool?
Full
12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier?
Full Full
12.7 Support User's Group
Full
Full
Full
Page 156 of 450
CORE v7.0
Full
We recommend that new users attend a 4-day introductory class that exposes them to the majority of the tools capabilities, however many users with a strong systems engineering and Architecting background are successful with little or no formal training. Many users can be self-taught using our comprehensive Guided Tour, which typically takes no more than three hours. We also offer 1 and 2 day courses and custom workshops to meet our client's varying needs. CORE is easily installed on a client workstation. Workstation requirements are available at http://www.vitechcorp.com

13.4 Software installation with only basic training
Full
N/A
Vitech believes behavior/activity modeling and allocation is crucial to the completion of the requirements analysis process that identifies control flow, activity/function flow, and data flow. Behavioral models are executable via COREsim, a discrete event simulator. Data links and resources can be modeled to assess communication dynamics, and resource utilization and contention.
Page 157 of 450
Cradle v5.7
Date of Submission: 6-Jan-09


Full
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document.
Full
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
Page 158 of 450
Cradle v5.7
Full

Full
Page 159 of 450
Cradle v5.7
Full

Full
Full
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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to them.
Full
Page 160 of 450
Cradle v5.7
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 Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements.
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.
Full
Full
Page 161 of 450
Cradle v5.7
Full

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.
Page 162 of 450
Cradle v5.7
Full

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).
Page 163 of 450
Cradle v5.7
Full

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.
Page 164 of 450
Cradle v5.7
Full

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
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
Page 165 of 450
Cradle v5.7
Full

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.
5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Full
6. Documents and other output media
Page 166 of 450
Cradle v5.7
Full

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
Page 167 of 450
Cradle v5.7
Full

Full
Full
6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
Page 168 of 450
Cradle v5.7
Full

Full
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
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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives.
Page 169 of 450
Cradle v5.7
Full

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.
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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to?
Full
Full
Page 170 of 450
Cradle v5.7
Full

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).
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? 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
Full
8.1.5 Support for Data Exchange Standards (AP-233, XML,..)
Full
Full
Page 171 of 450
Cradle v5.7
Full

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
Full
Page 172 of 450
Cradle v5.7
Full

9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full
Full Full
Full
Page 173 of 450
Cradle v5.7
Full

9.4.3. Disk space requirements 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?
Full
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
10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data?
Full
10.4. Which window's standard do you follow?: If your tool supports a window's standard, which one(s)?
Full
Page 174 of 450
Cradle v5.7
Full

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
Full N/A
Full
Page 175 of 450
Cradle v5.7
Full

12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager?
Full
Full
Full Full
12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location
Partial Full Full Page 176 of 450
Cradle v5.7
Full Full

13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Page 177 of 450
Cradle v5.7
N/A

Page 178 of 450
Cradle v5.7
Comments
Cradle can identify differences between successive versions of external source documents, and identify which requirements or other items may be affected by these changes. Associated impact analyses can then be performed. Cradle does not store multiple copies of items for different versions, effectively managing the version histories such that database size is controlled and performance impacts are minimized. The Cradle REQ module allows the user to parse requirements based on identified key words, paragraph number or structure, or unique identifiers. Requirements (and the desired numbering system) can be created directly from the text. Cradle also has Word and Excel Plug-ins, facilitating data capture from these tools and automated entry into the Cradle database. When capturing from Word or Excel tables, Cradle can selectively import from just those columns that you want, skipping columns not needed. Additionally, Cradle has a read/write API to support special purpose database access requirements. Cradle REQ allows for manual (interactive) and semiautomatic (e.g., groups at a time) parsing and identification of requirements. In both this and the fully automatic mode above, automated completeness checks are provided to validate the extent of requirements capture. Plug-ins for Microsoft Word and Excel allow the user to capture desired paragraphs and tables from Word and spreadsheet rows from Excel as Cradle requirements, system notes or process specifications.
Page 179 of 450
Cradle v5.7
Comments
Cradle REQ allows for manual (interactive) and semiautomatic (e.g., groups at a time) parsing and identification of requirements. In both this and the fully automatic mode above, automated completeness checks are provided to validate the extent of requirements capture. Plug-ins for Microsoft Word and Excel allow the user to capture desired paragraphs and tables from Word and spreadsheet rows from Excel as Cradle requirements, system notes or process specifications. Cradle REQ provides the mechanism to scan and individually identify and create requirements and their definitions. Cradle also provides an MS Word/Excel interface that supports creating requirements directly in the database from either Word or Excel. Cradle provides a Word plug-in that allows any collection of paragraphs or table rows to be imported into new items in the database. When importing paragraphs, users can specify values for all attributes to be created in the new database items. When importing from a table, users can define a mapping between the table columns and the attributes of the items to be created in the database, optionally omitting some of the table columns. Cradle provides an Excel plug-in that allows any range of cells to be imported into new items in the database. When importing from a spreadsheet, users can define a mapping between the data columns and the attributes of the items to be created in the database, optionally omitting some of the columns. To simplify the creation of this mapping, Cradle will attempt to automatically match data columns to database item attributes by reading the column headings.
Page 180 of 450
Cradle v5.7
Comments
Cradle REQ provides the mechanism to scan and individually identify and create requirements and their definitions. Cradle also provides an MS Word/Excel interface that supports creating requirements directly in the database from either Word or Excel.
Yes, requirements grouping, classification, and categorization are all fully supported. Cradle can store arbitrarily many, arbitrarily large attributes of any data type to support the classification process. Cradle databases are extended by a point-and-click interface. Cradle can store requirements in any number of hierarchies or other structures concurrently. Any requirement(s) can appear in any document. he allocation of requirements to sub-system elements takes se sub-systems elements. Yes, Cradle provides an extensive library of modeling notations that allows the user to capture system implementation and associated linking. Representative Cradle notation sets include: functional (data flow, state transition, entity relationship, data structure, structure charts); behavior; process; architectural (function block, hierarchy, physical, software) and object oriented (class, use case, sequence, collaboration, statechart, activity, component, deployment). Cradle supports multiple levels of model hierarchies which can be used to show phases in a program life cycle, levels of scope as in a system-ofsystems, and alternatives for product designs. Yes, the user defines the appropriate (database) item types and the corresponding data dictionary or specification textual descriptions. Requirements can then be crossreferenced into these data types as well as associated system model items. Page 181 of 450
Cradle v5.7
Comments
Cradle fully supports requirements derivation hierarchies, as well as decomposition, merging and history tracking. In Cradle, you create links as needed (provided you have the right to do so). Cradle provides the facility for user-defined cross reference link attributes (attributes within cross references in which the user can store information) that can be used within search criteria. These link attributes can be displayed in Tables using Cradle WorkBench. Cradle allows the user to group links, to search based on any link type defined in a link group, and to create any number of link groups (each containing any number of types of link). The Cradle user defines these system elements as (database) item types. Performance requirements can then be cross-referenced into these data types as well as items in the system models (e.g., other requirements, functions, interfaces, etc.). Cradle provides bi-directional, many-to-many, typed, attributed, transitive cross-references to system elements. Cradle has the capability of mapping and linking Work Breakdown Structure (WBS), System breakdown Structure (SBS) or Product Breakdown Structure (PBS) elements with requirements.
Page 182 of 450
Cradle v5.7
Comments
Cradle provides complete flexibility in attaching frame information to items, including text, spreadsheets, tables, equations, video, sound clips, CAD/CAM drawings, etc. These frames can be typed, for defining new data types, the privileges associated with them, and customized interfaces to interact with data of such types. Cradle can color code its requirement attribute values, based on the value of another related attribute. For example, criticality can be addressed by coding all Mandatory requirements (and their frame information) red, Highly Desirable requirements blue, etc. This color coding makes it easy to visually scan and understand a set of information. The colors are reproduced when attributes are printed, can be used in tables, and appears in output RTF and HTML. Cradle can also reference associated requirements data (e.g., related test data) in external files, at URLs, and within external environments. Cradle provides for regular expressions (regex), the most powerful and flexible search expression for retrieving the data. Cradle can also display matrices or nested tables (such as tests for each acceptance criteria for each requirement). Tables can be generated with any amount of nesting and exported directly to RTF, HTML and Excel. Users can define any number of these tables through a simple point-and-click interface.
ility to see the links where they come from, where they go, and
Page 183 of 450
Cradle v5.7
Comments
Hierarchical diagrams provide a graphical depiction of requirements links to display anomalies. Cradles hierarchy diagrams always show the existence of all children of a node, and provide full control over the expansion and collapse of nodes. In its hierarchy diagrams, Cradle also provides full control over which item attributes are shown; the user can also specify the diagram colors, appearance (sizing, alignment) and style. When the user has resolved all inconsistencies in the hierarchy diagram, he/she can save the diagram as a static snapshot of the database structure (to be included in a report, for example). These diagrams are not the only means to identify database inconsistencies. Cradle provides many, independent tree views of the database structure. Cradles WorkBench module also provides coverage analysis by allowing userdefined queries into the database to look for all unlinked items, undefined items, unspecified inputs/outputs and other anomalies of interest. For example, when searching for orphan items (such as requirements), Cradle provides 'Orphan', 'Unconnected', 'Disconnected' and other such alternatives as single-click options, in addition to the above functionality. Finally, analysis tools are provided for identification and correction of ambiguity, contradiction, duplication and omission instances within the database.
Page 184 of 450
Cradle v5.7
Comments
Cradle allows any items, such as requirements, functions, architecture components, verifications, acceptance criteria, trade studies etc) to be linked (optionally by links of specific types) in any manner. Link rules can be defined to impose rigour into such relationships and ensure consistency and integrity. Linking can be done through drag-and-drop between Explorer-style requirements/function/component hierarchies, and through graphical HIDs. Cradle allows for project-defined link types and groups; several traceability templates, traceability diagrams and reports are provided with the software. WorkBench provides predefined queries that allow the user to immediately examine and assess requirements bi-directional traceability. Extended sorting, table viewing and querying capabilities all exist in WorkBench to help assess requirements definition and linkage. Hierarchy diagrams are available in Cradle 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 user-specified number of levels. A formal Requirements Traceability Matrix (RTM) template is provided in the Document Publisher library. Generating this matrix will also provide complete visibility into all project database links from source to implementation. Completeness assessment and impact analyses of requirements to system cross referencing can be accomplished using these mechanisms.
Page 185 of 450
Cradle v5.7
Comments
Cradle provides complete traceability throughout the lifecycle, with the ability to attach item frame data to capture the complete requirements history. Impact analyses and change assessments of this history can be performed. A formal Verification Cross Reference Matrix (VCRM) template is available in the Document Publisher library. Generating this matrix will provide the user complete visibility into the plans for verifying the requirement (how and when), and who is responsible for the verification test. Holes or inconsistencies in the verification plans will become evident after review of this matrix. Performance requirements are linked to constraints on performance of the system design model. Cradle then assesses the system performance by executing the design model using mathematical models based on user configurable performance parameters. Results of this analysis provide allocated versus actual system parameter comparisons. Cradle provides complete edit histories of requirement (or any item) changes. In addition, Cradle can record full details of each and every edit to each and every item, recording the date and time of the edit, who did the edit, the reason for the edit, and the old and new values of all attributes modified by the edit. A Pending Delete facility is available, where deleted requirements can be recovered if necessary. Total requirements evolution is provided through history records, external user annotations and CM baselines. Cradle also provides full configuration audit logs within its internal Configuration Management System. Cradle provides command line utilities to create automated incremental and full database backups.
Page 186 of 450
Cradle v5.7
Comments
Cradle provides a free, integrated, extensible Configuration Management System (CMS), offering complete support of formal review and change, and subsequent baselining and version control and management. Cradle has a baseline mode facility which permits the user to select between viewing the full database, or the latest baselined version of the database. In either mode, user read-write or read-only access to the data is defined by user permissions in their profile. Cradle has 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 works-in-progress, into separate website components, for comparison between approved and current activities.
Cradle provides complete access controls based on projectconfigurable combinations of security classifications, user privileges and project organization. Formal change control is provided via Change Requests and Change Tasks within the CMS. For cleared viewers, Cradle offers an electronic post-it annotation mechanism for read-only external reviewers who can record their comments in annotations to items in the database.
Page 187 of 450
Cradle v5.7
Comments
The Cradle Document Publisher enables the user to use Microsoft Word to construct arbitrarily large and complex documents from datasets in a Cradle project database. Word documents or reports are user-defined through Word templates (outlines) constructed with tags or bookmarks that are keyed to access database information and the layout/format of the information in the output document. User-defined templates provided, with reports producible in the following formats: Mil-Std-490, 498, 961 and 2167; IEEE1220; DoD-5000; EIA-632; and DoDAF. Cradle provides typical systems engineering report templates as starting points, such as the Systems Engineering Management Plan (SEMP), Performance Requirements Based Specification (PBS), Systems Requirements Specification (SRS), Interface Requirements Specification (IRS) and System Design Description (SDD), to mention a few. In any case, the user can define his/her own template or modify existing ones to suit individual needs. The Requirements Traceability Matrix (RTM) and Verification Cross Reference Matrix (VCRM) templates are also included in the Cradle template library. 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. Data dictionaries and acronym tables are an inherent part of the Cradle infrastructure. Since the Cradle Document Publisher creates all reports in Word, the user has access to all the associated word processing quality and consistency checking features (e.g., spell checking and grammar) available in Word.
Page 188 of 450
Cradle v5.7
Comments
The new Cradle Document Publisher produces quality Word reports and presentation charts with contents including tables, diagrams, graphics and images. Output directly to Excel by the Document Publisher will be available soon (currently have an option to output tables in CSV for reading in Excel). Additionally, Cradle supports a wide spectrum of output formats, including Postscript, RTF (for PowerPoint), HTML, Interleaf, SVG, FrameMaker, HP LaserJet, HPGL, and EPS. The Cradle Document Publisher creates and publishes all of these features. User defined tables and graphics are specifieded as tags or bookmarks (by a point-and-click interface) on a Word template, and the corresponding data is extracted from the project database by the Publisher and output in a finished report. Cover page information, security markings, disclaimers, etc. are all part of the report template, again defined by the user. The Table of Contents, List of Figures and List of Tables are all dynamically generated as the report is being produced. For users without access to Word, Cradles Document Printer is used to define (again by a point-and-click interface) templates depicting the desired document structure, layout and contents. The Document Publisher report output file can be previewed as a Word document on the screen immediately after it is produced. Alternately, the Web Publisher Module will present the output as a fully hyperlinked website component . All Cradle tools provide status information or dialog boxes 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 reporting.
Page 189 of 450
Cradle v5.7
Comments
Cradle users accomplish performance status accounting by defining a combination of user defined item types (system notes) that are assigned for tracking and annotating performance related requirements into any number of models created in the Cradle design modeling domain. Cradle WorkBench is then used to query the progress/status of these item types. Cradle users accomplish status reporting by defining a combination of user defined item types (system notes) that are assigned for tracking and annotating cross references linking requirements into the analysis and design domain models and to supplemental project risk and issue items. Cradle WorkBench is then used to query the progress/status of these item types. Cradle WorkBench provides a complete (point-and-click) library of the more common requirements-related user inquiries and searches of interest, with the capability to easily create additional user-defined queries as needed.
eam of engineers to look/work on the same information at the The Cradle infrastructure fully supports a multi-user project database with distributed data sources and users. Cradle provides a mechanism called Alerts to allow users to send instantaneous status messages to other users, their team, or the entire project. Additionally, the electronic post-its annotation process is extremely useful for read-only external reviewers to record their comments relative to items in the database. The Cradle 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.
Page 190 of 450
Cradle v5.7
Comments
Cradle provides 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; and customizable user access rights to tools in the environment. These controls are used to implement and monitor the review and approval of informal or evolving changes. Cradles internal Configuration Management System provides the necessary change request/action/review/control processes associated with formal change approval cycles.
Cradle has data convertors for RDD-100, CORE, Teamwork and BPWin, and uses the CSV standard for data exchange with DOORS, StP and RTM. Cradle also has Word and Excel Plug-ins, facilitating data capture from these tools and automated entry into the Cradle database. In the case of DOORS, the plug-in connects to a DOORS server and asks the user to authenticate. After this, the user can choose to export any module(s) from DOORS into the plug-in, where they are converted to AP233 format files which are then imported into the Cradle database. Cradle provides a separate utility to browse the AP233 files through a tree-viewer. The same plug-in can be used to import requirements back into DOORS (typically a new module since DOORS cannot overwrite existing items in the database). Additionally, Cradle has a read/write API to support special purpose database access requirements. Cradle has a data convertor 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. Page 191 of 450
Cradle v5.7
Comments
Cradle has a C/C++ Applications Program Interface (API) that provides open access to the database from other engineering tools or project management applications. This API supports getting data from the database as well as writing into the database. The API also supports VB and VBA applications. Thus, Cradle's database can be utilized as a central repository for all project-related data. 3SL uses the Cradle API to create Cradle tools. Specifically, the Cradle Document Publisher and Spell Checker are examples of tools that we have created with the API. Yes, Cradle supports UML Modeling; RTF, MIF, OPS for document exchange; SQL via external RDB engine; and CSV for data exchange. Yes. Cradle provides several mechanisms for direct data import without the need to re-enter information: full CSV (comma separated value) capability for data exchange; the Cradle REQ parsing engine; the Cradle Word/Excel Plugins (to directly capture Microsoft Word and Excel data); the Cradle Applications Program Interface (API); and external tool data convertors. Yes, Cradle supports these Data Exchange Standards. The Cradle DOORS plug-in converts to AP-233 format files for import into the Cradle database.Cradle supports XML based file formats for information exchange, including:(a) XMI files for the exchange of model data(b) SVG files for the presentation and exchange of diagrams.
Page 192 of 450
Cradle v5.7
Comments
Cradle supports true client/server environments for information exchange. A user can also create export file(s) for information transmission and exchange. Cradle 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. 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.
Cradle supports both user environments. Cradle is a fully multi-user environment, has provided these facilities since 1990, and has demonstrated continued success in large distributed projects. Cradle has been deployed in very large installations with over 1,000 active desktops and more than 500 concurrent users. In addition, Cradle supports a single user having more than one defined profile with profileunique permissions, which allows that user to function in different roles for different teams on a given project.
Page 193 of 450
Cradle v5.7
Comments
Cradle supports all 32-bit Windows 2000, XP, and 2003; Solaris 2.8 or later on the Sparc architecture; IBM AIX 5.1 or later on PowerPC; HP-UX 11.0 or later on the PA-RISC architecture; and 32-bit compatible versions and types of Linux. Cradle 5.7 also supports MS Office 2000, XP, 2003, and 2007; all popular web browsers including Safari for the Apple Mac and Firefox (If using Firefox, recommend upgrade to Firefox 3.0.); and MS Sharepoint. Any Cradle component running on any platform can link to the same or any other component of Cradle running on the same, or any other, platform. The format of all project databases is identical across all platforms. This means that databases can be moved between Cradle systems platforms without any need to convert them. Cradle has a proprietary and open database. Cradle databases are processed as relational databases whose attributes can contain, or reference, BLOBS (binary large objects). Each Cradle database is a collection of 46 CISAM file groups. Each file group contains an arbitrarily large collection of data records that are simultaneously indexed by multiple indexes (some file groups have over 30 concurrent indexes) to provide pre-sorted information retrievals in multiple different sort orders. This eliminates the need for Cradle tools to retrieve large amounts of data and then sort it locally.
Memory requirements: For Windows platforms: 64MB minimum, 128MB if host is also running CDS. Additional 64MB for XP, 2003. For UNIX and Linux platforms: 32MB minimum. CPU requirements: For Windows platforms: 233MHz or faster is preferred. For UNIX platforms: minimal, any configuration is acceptable. In practice, the more users there are, the higher performance server that is needed. Page 194 of 450
Cradle v5.7
Comments
For Windows platforms: 70-220 MB, depending on components loaded. For UNIX platforms: 220 MB. Yes. The modular architecture of Cradle allows a user (or users) to perform simultaneous operations on the database. For example, while viewing and analyzing a set of requirements (or building a design model), the user can also be running a report with the Document Publisher. Yes. In the WorkBench module, Cradle allows any number of views to be opened on the same or different sets of information at the same time. Any changes made through one view will be automatically propagated through all other views. Yes. Cradle provides a graphical editor for creating multiple types of diagrams, including: functional, behavioral, hierarchical, process, data flow, architecture and object oriented. Numerous notation styles within each graphical type are supported. The graphical models are input via a point-and-click interface to the graphics icon library, and manipulated or modified by a drag-and-drop process. The graphics icon symbols can be replaced by (GIF or JPEG) images to more clearly convey the intent of the graphics. Graphics (diagrams and images) in Cradle can easily be viewed and output for publication or presentation via the Document Publisher. Similarly, Cradle database entities (items, attributes, types, etc.) can be input, controlled and viewed using the WorkBench query and data form user panes. Microsoft Windows.
Page 195 of 450
Cradle v5.7
Comments
All repetitive operations in Cradle have a macro capability, such as requirements parsing, import/export, and performance analysis. These macros can be defined, stored and reused. Cradle tasking can also be controlled through its API, or through a fully user-definable Message Programming Interface (MPI). Yes. Cradle can support secure web access and provides secure access control logic within its web and non-web environments. The Cradle Web Access (WEBA) module allows remote users access to Cradle databases over the Internet or corporate intranet using only a web browser and an appropriate project authorization. Users access via browsers pointed at the Cradle Web Server (CWS), where they can login to a database via a login screen. Users can create, view, edit and delete items, and manipulate and follow cross-references using customizable screens. Also, by using report writing procedures provided in the Web Publishing Module (WEBP), a user can create HTML documents that can be viewed by a web browser. Cradle5.7 supports all popular web browsers including Safari for the Apple Mac and Firefox. If using Firefox, recommend upgrade to Firefox 3.0. Cradle 5.7 also supports MS Sharepoint. Yes, in both text and diagrams. All web-based and non-web-based access to Cradle databases is controlled by a password protected login process that is compliant with BS 7799 and ISO 7799. Links between web browsers and the Cradle Web Server (CWS) can use HTTP or HTTPS protocols. See Section 6.1 for documentation standards. Cradle has a 90-day warranty. We also offer an Annual Maintenance Program that provides free software upgrades and tool operational support. Page 196 of 450
Cradle v5.7
Comments
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. The Cradle License Manager is proprietary. Major software releases are provided at least annually, available at no cost under the Annual Maintenance Program. Official upgrade downloads with release notes are also available quarterly from the 3SL corporate ftp site to users under the maintenance program. Yes. The Cradle CD, the 3SL web site and the corporate ftp site all maintain a current full set of Manuals and Data Sheets in PDF format (with browser to access and read). The Cradle software comes with online help. 3SL now offers Internet-based support to all customers with active maintenance contracts who have access to a PC or UNIX workstation with a web browser and Internet access. Our web-based service allows us to create a web meeting in which our engineers can run Cradle systems that appear on the users screen. The user can control the Cradle systems (that are running on a 3SL PC) to ask a question, illustrate a problem, or propose a desired enhancement. E-mail: info@threesl.com Web Site URL: http://www.threesl.com Telephone Hotline Support available 12 hours per day, 7:00am to 7:00pm (EST in US, GMT in UK) US: 1-937-8328529 UK: +44 (0) 1229 838867 E-mail requests encouraged: support@threesl.com Formulation of Cradle Users Group under evaluation. Wide variety of Cradle training available - from overview sessions to comprehensive tool usage workshops. Yes, training available onsite as needed. Typical class size is 8 - 10 students. Page 197 of 450
Cradle v5.7
Comments
1-2 days for Requirements Management and Analysis. Additional training available for other Cradle modules. Available to fit customer needs. Our consultants are trained to provide onsite or online installation support and Cradle Systems administration training.
Page 198 of 450
Cradle v5.7
Comments
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 (including DoDAF/C4ISR) of the system using traditional modeling notations, as well as UML Object Oriented and other code structure model 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-Based Design (MBD). 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. 14.4 Metrics: Using the Cradle Metrics (MET) module, the user can define and run metrics that allow a project to gauge the completeness, coverage and consistency of
Page 199 of 450
Dimensions RM v10.1.4

Compliance Comments (Full, Partial, None)

Full Dimensions RM is capable of taking requirements, use cases, test cases, etc from MS Word, XML, MS Excel, or plain text documents. This data is parsed via a series of configurable rules and stored as individual occurrences of classes. This allows Dimensions RM users to manage these objects (requirements, etc) as they prefer: either in an online document-like view or a grid view. Dimensions RM has the ability to organize requirements into documents or collections that can be baselined. These baselined documents may be compared to each other or to the latest version of the document producing a detailed, printable comparison report that shows additions, deletions, and changes. The Dimensions RM Import tool provides extensive patternmatching and parsing abilities for identifying requirements and document content in order to create the individual requirements rather than simply copying the document. The Import Tool recognizes Microsoft Word structures such as headers and paragraphs as well as tables and lists. These formatting elements are transferred to Dimensions RM along with the content. Dimensions RM has the ability to capture requirements from both text and Microsoft Word document via a set of configurable rules. The results can be previewed prior to creating the requirements. Once imported, Dimension RM's rich Web-base UI allows users to manage the textual data via search/find/replace and well as copy/paste. Requirements can be either imported from text files, MS Word documents, XML, or MS Excel files. They can also be created or updated via a rich web-based UI.
Full
Full
Full
Full
Page 200 of 450
Full Requirements and links can be put into the Dimensions RM database in batch fashion many different ways. Dimensions RM provides the ability to batch input and update requirements and links from comma separated value (CSV) formatted files. This feature provides the ability to import data from popular software products such as Microsoft Excel and Microsoft Project as well as from other engineering tools. In addition to being able to import and update requirements via CSV files, users can also perform batch updates of requirements and links based on specified attribute values. In addition, as Dimensions RM offers a rich Web Service api one can easily gather requirements form other Web Service-enabled applications. When coupled with Serena Business Mashups, Dimensions RM can participate in complex business processes to share data with various other software tools. There is also a powerful Synchronization tool that allows Dimensions RM to share data with 3rd party tools such as HP Quality Center. Dimensions RM provides detailed requirements traceability at a more granular level than document. The original source document (or any other) may be made part of the requirement either as an attachment or as a URL or other link. Because Dimensions RM does not store the requirements in a document structure directly, a single requirement may be part of multiple documents thus eliminating the need for redundant maintenance and eliminating the risk of having stale documents. In addition, users are not required to use a document view of the requirements as they may also manage the requirements in a grid view.

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
Page 201 of 450
Full Broad categorization of object types, such as Business Requirements vs. Business Rules vs. System Requirements vs. Test Cases, etc., is accomplished with our Class Definition feature. This allows different sets of attributes to be assigned to each object type, as appropriate, and constraints to be placed on which object types can be associated (linked) to which other object types. Finer categorization of object types, such as by source business area or application type, is accomplished through the use of list-type attributes.

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. The Dimensions RM class definition tool allows the user to model visually any type of hierarchical project data (e.g. requirement document hierarchies, system element structure, WBS, etc.) Once the hierarchy is defined generic relationships can also be established to allow crossreference link information to be established between any active data item. These relationships can then be visualized through the web-based Traceability View that also allows for adjustments of the structure via drag-and-drop. In addition, any object in Dimensions RM (requirement, use case, etc) can have a graphic item either imbedded in the text or attached. 2.2. Textural capture of systems structure: Can the tool textually capture Dimensions RM captures textual and non-textual Full system implementation (such as architecture, functional decomposition, WBS, requirements with equal ease. All may be captured and etc.) and display them textually such that requirements can be linked to them. displayed together for each object. The type of content allowed is controlled by the configuration in the Class Definition tool. 3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Full
Page 202 of 450
Full Dimension RM's web-based UI allows users to organize and derive their requirements according to their needs. An object in Dimensions RM (requirement, use case, test case, etc) can be linked to any other object. Each object may have an unlimited number of links to or from it. These relationships can then be viewed and managed via the Traceability View. Dimensions RM easily supports the ability to link performance requirements to any other type of data item in the Dimensions RM repository. Dimensions RM does not support the concept of linking a "portion" of a requirement. Dimensions RM treats a requirement as the lowest level traceable object in the database as the user may define requirement objects to a very granular level base upon their needs. This capability is fully supported in Dimensions RM. Dimensions RM provides the capability for easily establishing links between any type of object in any direction. Dimensions RM provides several basic user defined attribute types which can be instantiated by the user into an unlimited number of user-defined attributes. The user defined attributes can be modified at any point in the project lifecycle. Attributes can be defined as mandatory and default values may be supplied. Dimensions RM provides the capability to assign any number of attributes or descriptors to a group of objects. These attributes are easily reported on via wizard based reports.

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
Full
Full
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.
Page 203 of 450
Full Dimensions RM's powerful reporting wizard allows easy selection of objects that do or don't satisfy certain conditions, such as having specific attribute values, or being related to specific objects. An example "orphan" might be a Test assigned to a Use Case that has been deleted or delayed to a later release. Orphans such as these would be very easy to find using the reporting wizard. The Dimensions RM Traceability View allows the user to navigate traceability information in any direction. This tool allows for a detailed impact analysis to be performed at any level in the hierarchy as an example. Dimensions RM provides several mechanisms for maintaining requirement verification status and history. Project classes can be defined to record information about verification events. Requirements can be linked or allocated to verification events. Pre-defined attributes which track user comments, completion criteria, etc. together with project defined attributes can be used to maintain status for both requirements and verification events. Dimensions RM maintains a complete audit history trail for changes to all types of information objects. Any two versions of a requirement can be compared showing a detailed difference report. Together these capabilities fully support the ability to analyze a requirements database for allocation verification.

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. 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
Full
Full
The Dimensions RM Query Wizard and Report generation facility can provide rollups of actuals for any given attribute of a specific requirements type. The system does not automatically provide comparisons between the rollup of actuals versus the rollup of allocated values, however the tool can provide adjacent column totals and the user can easily see the difference.
5. Configuration Management Page 204 of 450
Full Dimensions RM goes much further than just providing a version history for changes over time to requirements. Dimensions RM provides a separate copy of the object for each version of a requirement over time, which supports the ability to establish traceability versioning over time. Dimensions RM also automatically stores time date stamp information for every requirements change creating a complete audit history for who changed a requirement, when did they make the change, and what were the criteria and related information for the change. This history is visible to the users via the web-based UI which also allows for a comparison between any 2 versions of the object. The baselining of requirements is a very straightforward process within Dimensions RM. Baselined requirements can be locked so that updates will be prevented. Dimensions RM supports the ability to compare and contrast between baselines. Dimensions RM supports a highly configurable access control model both for individual categories of requirements as well as links or relationships between groups of requirements. Establishment of access control is maintained by the Dimensions RM administrator so that the access controls themselves are safeguarded. The access controls can be established at the user, group, and project level. Default access controls can be established for those projects that do not wish to use this capability.

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.
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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Full
Full
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
Page 205 of 450
Dimensions RM provides the ability to generate requirements output in native formats for Excel, XML, MS Word, etc. This output can be directed into an existing standards template for final document creation or the user can define a set of publishing templates that Dimensions RM will use to format the output. In addition, all query output can be exported into numerous formats including HTML, XML, text, and CSV.
Partial Although the Dimensions RM toolset itself does not include a spell checker, open-source or other 3rd party HTML spell checking tools can easily be added to the Web UI. Dimensions RM does not product charts; however, any chart can be attached or embedded in the text of the requirement to allow for direct publishing. This coupled with Dimension RM's flexible Document View allows for the organizing and formatting of the requirements, use cases, test cases, etc into a document that can then be published directly to MS Word. Dimensions RM implements this capability through the Web UI. Users work is a WYSIWYG interface such that they can format their requirements and documents on-line. Publishing then using this format as well as offering even more formatting options. The Dimensions RM web-based UI allows users to format the requirement and document on-line before publishing. Dimensions RM provides a number of pre-defined requirements attributes for maintaining status, reason for change, proposed changes, and general discussion. The true multi-user characteristics of the toolset make Dimensions RM an excellent mechanism for implementing on-line management of requirements. Dimensions RM provides an excellent mechanism for monitoring progress of many characteristics of a new system, e.g. performance, cost, weight, power consumption, etc. through attribute value rollup capabilities found in the Query and Report generation function. This again is a fundamental concept supported by Dimensions RM.

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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
Partial
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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
Full
Full
Full
Full
Page 206 of 450
Full

The Dimensions RM Query and Report generation wizard provides the user with a point and click ad hoc report/query definition capability which does not require any end user knowledge of search languages like SQL or other proprietary scripting languages. 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 Dimensions RMs multi-tier architecture provides a scalable Full support a team of engineers reviewing, marking up, and commenting on multi-user solution for any number of users. Dimensions RM requirements or implementation alternatives. allows all users access to the same requirements at the same time. This capability coupled with the pre-defined set of attributes for tracking status, reason for change, and discussion of proposed changes makes Dimensions RM an excellent mechanism for a team of engineers to work requirements on line. Dimensions RM provides a built-in change request feature, which allows engineers to propose changes to requirements as part of Engineering Change Proposals (ECPs). 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 Multi-level access control is fully supported by Dimensions RM. Dimensions RM also supports the ability to capture change proposals to the requirements under a separate access privilege keeping changes under consideration out of the concern for most project personnel. The built-in change request capabilities allow proposed changes to be made, reviewed, and commented upon prior to being accepted into the baseline. Dimensions RM provides the ability to grant users access to all, some, or none of these capabilities. Inter-tool communication and data integration is achieved via commercial standard interfaces (e.g. CSV, XML) as well as through the fully documented Dimensions RM web services. In addition, Dimensions RM supports the Application Lifecycle Framework (ALF) standard.
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
Page 207 of 450
Full Because of its public web services, Dimensions RM can integrate with any web service enabled tool. In addition, Dimensions RM has a rich integration with Serena Dimensions CM allowing a unified process between requirements management and configuration and change management. Dimensions RM also integrates with Serena Business Mashups (formerly known as TeamTrack) allowing the user to create infinite business processes in which Dimensions RM can participate. RM also offers outof-the-box integration with MS Word, MS Excel, MS Project, HP Mercury Quality Center, and Rational System Modeler. Dimensions RM delivers an comprehensive set of web services through which any third party tool can exchange data. In addition, Dimensions RM provides an ALF Event Emitter service that will automatically send event information to Serena Business Mashups allowing custom business processes to consume Dimensions RM data. Access is available to the underlying Oracle database access layer via the industry standard SQL database query language; however, most access is performed via web services rather than direct database access. Data import is supported from: Microsoft Word, Microsoft Excel, Delimited text (including CSV), tool-to-tool interfaces using Web Services. Export is supported to: Microsoft Word, Microsoft Excel, RTF, CSV, text, XML, HTML.

Full
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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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
Full
Partial Full Full
Page 208 of 450
For multi-site projects connected via a network the underlying multi-tier architecture of Dimensions RM allows users to access remote databases seamlessly. There are no changes from the user interface or workflow point of view. Multi-site connections can be established using Dimension RM's Synch Engine tool to move data across the various sites.
Full Dimensions RM provides a variety of comparison mechanisms: -Dimensions RM provides the ability to compare the versions of requirements in a captured document to their versions in the database. -Dimensions RM provides the ability to view data in relationship forms. Dimensions RM provides the ability to run reports that will allow for manual comparison. -Dimensions RM provides the ability to compare specific versions of a requirement. Dimensions RM provides the ability to produce a baseline comparison report. Dimensions RM provides a multi-tier architecture capable of supporting any number of concurrent users. Dimensions RM is designed to run on any Microsoft Windows-based server running either IIS or Apache web servers. Users may connect to the web-based UI using either Internet Explorer or Firefox. Its datastore is an Oracle database which may run on any Oracle-supported platform including Windows, Solaris, AIX, UNIX, Linux. Commercial database (Oracle). Serena Software has an excellent working and business relationship with the Oracle Corporation. Dimensions RM has always been implemented on the Oracle solution.

9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full Full
Full
9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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?
Full Full Full Full
Suggested requirements: Web Server: 1 GB or more; Database Server: 1GB o
600 MHz or better. Database Server: 5GB or more; Web Server: 1 GB or more
Full
Yes. Users can run reports and perform other operations simultaneously. Dimensions RM is a multi-user, multi-taskbased application.
Page 209 of 450
Partial The Dimensions RM toolset does support multiple views onto the requirements data from multiple users at the same time. Upon user request the toolset automatically reflects updates from one users view into another users view in a synchronous fashion. Dimensions RM supports multiple users working on the same requirements at the same time by implementing locking control on a requirement by requirement basis. The system can also be configured to allow concurrent updates and provides a merge capability to handle collisions. The Dimensions RM toolset supports the ability to capture graphical information either as attachments or a embedded images in the text. Dimensions RM is a web-based application and utilizes AJAX through the UI. Dimensions RM does not directly support the creation and execution of scripts; however, users may use any of a number of industry standard or open source tools to accomplish this. All but administrative functions are accessed via a Web browser: Microsoft Internet Explorer or Firefox.

Full
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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full Partial
Full Partial N/A
Compliant with POSIX 10003-1, SQL, SAML, X11R5, CH V3.0 ANSI C Programming Standards. Web services follow the gsoap standard. Dimensions RM is delivered on the Open Oracle database solution. This is the leading COTS database technology. SQL can be used as a standard data access capability. Military Standards: Dimensions RM is configurable to support many military or commercial document or exchange formats. Document Standards:
The product is warranted as described in Serena Software's License Agreement.
Full Dimensions RM is delivered utilizing the FlexLM floating network licensing manager allowing for both concurrent and named licenses. Software updates are provided to customers currently under the Serena software maintenance agreement. Product releases occur every 6-9 months. Dimensions RM provides context sensitive on-line help. All Reference material including manuals and tutorials are provide electronically, as well. http://www.serena.com/ Toll free telephone support provided 24 hours/day via the worldwide support organization. Serena Software hosts an annual customer User's Group. In addition, Dimensions RM holds a Customer Advisory meeting with select customers 5x per year. There are also customer-led user groups for the Dimensions suite of products which includes RM and CM.

12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group
Full
Full
Full Full Full
13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location
Full Full
All Serena Dimensions RM training is available for delivery at a customers site. From time-to-time, certain Serena Alliance Partners offer DimRM training in public classroom training. Serena is exploring web-based, on-demand, training. On site training DimRM training combines user and administrator training. The user training portion is more directed toward a business analyst. The administrator training is more directed to whomever is responsible to administer and manage the system. In concert with exploring web-based, on-demand training, Serena is also considering adopting a role-based curriculum approach to training.
Full
Page 211 of 450
Full A detailed Installation Guide is provided with our products that enables user's to install and configure the products without any training. Our support engineers are available for consultation during this process.

Page 212 of 450
N/A Full ALM integration Prototyping Business process integration Serena Software believes that a highly integrated Application Lifecycle Management (ALM) solution is what benefits customers most. Therefore, Serena's Dimensions RM is designed not only to have state-of-the art requirements management functionalities, but it also is part of a suite of products that allow for end-to-end management of requirements from concept to code. Primary to this endto-end view is a rich and powerful integration with Serena Dimensions CM. With an full set of Web Services Serena Dimensions RM can easily be integrated to most 3rd party tools. Another powerful coupling with Dimensions RM is Serena Prototype Composer which allows users to visualize their concepts as executable prototypes and the elicite requirements that can be seamlessly managed in Dimensions RM. Prototype Composer is offered free by Serena. Serena Software also believes that tools should adapt to the customer's business processes rather than the other way around. Therefore, Serena also offers Serena Business Mashup (formerly known as TeamTrack). This tool allows users to define and automate their business process by "mashing up" or combining various tools into a unified endto-end process. Dimensions RM is a participant in this by offering rich web services and by logging events that can trigger actions in other tools through a mash up.

Page 213 of 450
Enterprise Architect v7.1

Date of Submission: 8-Feb-09

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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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. 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.

Partial Project Glossary in model, import pre-enriched document templates into RTF document generator None None
Partial Offered by 3rd party addins, refer to: http://sparxsystems.com/products/3rdparty.html None Full Partial
Input from Comma-Separated Values (CSV) file Supported using built-in RTF document generator and using Master Documents, refer to: http://sparxsystems.com/downloads/whitepapers/Working _with_the_RTF_generator.pdf On import/entry, names can be prefixed/suffixed, 'level 1.6. Requirement classification: Does the tool have the ability to Partial numbering' on Project Heirarchy classify/categorize requirements during identification 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 Full system implementation (such as architecture, functional decomposition, WBS, Fully extensible UML 2 - based visual modelling including, etc.) and display them graphically such that requirements can be linked to BPMN 1.0, SysML 1.0 and Requirements modeling them. 2.2. Textural capture of systems structure: Can the tool textually capture Full system implementation (such as architecture, functional decomposition, WBS, Fully extensible UML 2 - based modelling using tabular etc.) and display them textually such that requirements can be linked to them. entry via the Elements List feature 3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Page 214 of 450

3.1. Requirements derivation (req. to req, req. to analysis/text): The ability to Full Fully extensible UML 2 - based relationships between derive/create additional requirements and link between them such as elements supporting dependencies, associations, flows requirement to requirement, or requirement to text (representing trade studies) and nestings to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, Full cost, etc.): The ability to link performance requirements to system elements such as weight, cost, throughput, etc. This also includes the ability to allocate Using SysML 1.0 allocation (SysML 1.1 support planned) portions of that p 3.3. Bi-directional requirement linking to system elements: The linking of Full Fully extensible UML 2 - based relationships between requirements to system elements can be accomplished from either end of the elements supporting dependencies, associations, flows link--from the implementation back to the requirement or from the requirement and nestings down to the system element 3.4. Capture of allocation rationale, accountability, test/validation, criticality, Full 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 Using SysML 1.0 (SysML 1.1 support planned) other issue 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 In-built model validation to identify unsatisfied allow the user to identify inconsistencies such as unlinked requirements or requirements. Partial system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the Full Full relationship traceability via heirarchy tree & matrix links: With the requirement links in place, the user needs the ability to follow views the links to see where they come from and where they go to. 4.3. Verification of requirement (was it done, how was done): Throughout the Partial 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 Built-in SysML 1.0 and user-defined Reports & Searches document that the require 4.4. Requirement performance verification from system elements (roll up of None actuals): Once performance requirements have been allocated to system elements, the requirements management tool should support the verification of Planned those requirements by rolling u 5. Configuration Management
Page 215 of 450

Full Built-in model auditing automatically tracks change history on every element, relationship, property Full Built-in baseline/compare, integration with 3rd party Version Control tools (eg: Subversion). Refer to: http://sparxsystems.com/WhitePapers/Version_Control.pdf Full Built-in security and user group configuration 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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. None

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 o 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Partial Built-in spell checker Full Model diagrams can be printed, exported, copied into presentation tools Full Fully-customizable template-based document generator (for HTML and RTF). Supports importing of RTF templates Full Full Partial Planned Full Reports & Searches based on element type, status Full Fully-customizable search feature Built-in WYSIWYG output preview Fully-customizable status field supported on all model elements
Page 216 of 450

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 Full support a team of engineers reviewing, marking up, and commenting on Model repository hosted on DBMS for concurrent access requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the Full 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 Built-in security and user groups configuration changes into an approval cycl 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.). MDG Link for DOORS, Visio, MDG Integration for 8.1.1. Interfaces to other tools: What tools will your requirements management Partial Microsoft Visual Studio, Eclipse, Teamcenter Systems tool interface with or talk to? Engineering 8.1.2. External Applications Program Interface available: To support the wide Full variety of tools in use by engineers, the requirements management tool should COM, .NET and Java API have programmable access to the information contained in the tool's database COM and .NET Addin extension API (to get access to and 8.1.3. Support Open database system (standard query access): Does the tool Full Repository is a standard, open, relational database support Open Database standards such as standard query languages or accessible via SQL query exchange formats? 8.1.4. Import of existing data from various standard file formats?______: Does Full 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 Comma-separated Values (CSV) file re-enter the i OMG-standard XMI data interchange format 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) Full 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but different installations: Full Since the tool will be used at different sites and different projects, how does the tool exchange information between different tool installations or databases? Project 'Transfer' command, XMI file interchange 8.2.2. Consistency/comparison checking between same-tool datasets: Does Full the tool support comparing/contrasting of different same-tool datasets to allow consistency and verification checking? Page 217 of 450

Full Supported, refer to: http://sparxsystems.com/downloads/whitepapers/EA_Depl oyment.pdf Windows. Linux and Mac OS X (intel) support under WINE Commercially-available database (standard relational using SQL)

9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
Full Full
Full Full Full
128MB RAM, refer to: http://sparxsystems.com/products/ea/sysreq.html Intel Pentium II or Higher, refer to: http://sparxsystems.com/products/ea/sysreq.html 70Mb, refer to: http://sparxsystems.com/products/ea/sysreq.html
None Full
Full Full Standard Windows (Office-2003, Visual Studio 2005) Partial Available in EA 7.5 For HTML-generated documents Undo support for diagram/view edits
Partial Partial
Page 218 of 450

N/A UML 2, SysML 1.0 (SysML 1.1 Planned), BPMN, IDEF1X, DODAF, MODAF XMI Document Interchange Diagram outputs: JPG, BMP, GIF, PNG, WMF, EMF Document outputs: HTML, RTF Yes, Refer WARRANTIES AND LIABILITY in EULA, http://sparxsystems.com/products/ea/eula.html Floating license keys and Sparx-supplied keystore Full Updates generally available bi-monthly. License entitles you to 12-months of updates with renewal, refer to: http://sparxsystems.com/products/ea/purchase.html Help supplied with tool. Online help available, refer to: http://www.sparxsystems.com/uml_tool_guide/ http://www.sparxsystems.com Phone support available via Sparx Partners, Trainers and Sister companies within geographical regions, refer to: http://sparxsystems.com/partners/index.html Sparx Systems Forums, refer to: http://sparxsystems.com/cgi-bin/yabb/YaBB.cgi Worldwide training partner network, refer to: http://www.sparxsystems.com/partners/trainers.html In-house training available by partners, as above Average 3 days Self-guided tutorials, demonstrations available free at: http://www.sparxsystems.com/resources/index.html Modeling of systems, systems of systems, families of systems, business processes, business strategies, architectural modeling.

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
Full Full
Full Full None
12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full
Full Full Partial Full
N/A
Page 219 of 450
Envision VIP v9.0

Date of Submission: 3-Oct-08


Full Envision VIP provides a fully extensible repository for housing each piece of a document. This includes phrases or words that a user uses in a document. Envision automatically keeps track of all key terms [requirements and system elements] and all references to them. Envision VIP provides a completely customizable reporting facility that provides unlimited ways of viewing and building information such as indexes or glossaries. In addition, it provides a custom query facility that produces Excel type spreadsheet reports, a data repository browser facility, and a repository tool box. Envision VIP can generate identical documents from two versions of a project. Envision VIP can generate documents directly into Word, WordPerfect, or any other word processor. The user then can use the word processors compare facility to compare the two documents. Most users prefer to use highlighting to identify substantive changes. For example, they may use strikethrough for deleted text and double underlining to identify additions. Envision VIP supports the use of strike-thru and underlined text to show proposed changes in place. It also has the capability to "Roll Forward" or "Roll Backward" based on these conventions. A dynamic in place spell checking capability is also available similar to the way MS Word works. If a history of various versions is desired to be maintained, there are several ways to address this issue as well.
Full
Page 220 of 450
Envision VIP v9.0

Full Because Envision VIP uses an object oriented repository, it can quickly identify words, structures and unique identifiers. Requirements themselves can be defined as objects, simple or compound. Key words, structures, etc. can also be tracked as even more primitive objects. Relationships are automatically maintained by Envision. In addition, because the tool is fully customizable, users can create and manage their own consistent set of key words, identifiers etc. to meet their needs. Since all requirements are objects in the repository, when a user uses an object in a text file as a linked object, the system automatically identifies it using color. In addition, the requirements are accessible through this link. This objectoriented approach provides complete referential integrity throughout the document. Should an objects name or attribute change, the system changes it throughout the document. Envision VIP provides a fully customizable data entry facility for entering any type of information. Its internal text processing facility provides all types of highlighting features such as color and font change capability.

Full
Full
Page 221 of 450
Envision VIP v9.0

Full Envision VIP provides several different ways of importing data from external sources. Envision VIP provides an import/export facility to exchange data between projects and to import data from other tools. A utility has been developed and is available for setting up and running a set of predefined scheduled batch processes. This feature can be used for updating, publishing, & checking the integrity of the underlying repository. A powerful XML export/import capability is also available. Another exciting feature is the ability to copy data base tables or an Excel spreadsheet and simply drop it into Envision VIP. Envision VIP will identify the affected class of information and the corresponding associated attributes and place the information into an existing class or if no class exists it will automatically create the class and attributes for you. Additionally a powerful template driven import/export facility allows Envision to input/output virtually any type of information from/to any other external programs and data bases. Envision does have the capability to maintain a consistent set of linked documents by automatically generating updates when needed. When changes are made in the Envision models, views, item values the repository manages all such changes. This enterprise information can be easily published in the form of MS Office Documents [e.g. MS Word files or perhaps MS Excel files] with any appropriate linkages desired. During this process the Envision repository assures the latest and most up to date terminology, linkages, properties, models from the common repository are incorporated into the output products.

Full
Page 222 of 450
Envision VIP v9.0

Full

The Envision VIP object-oriented repository lets users classify and type any requirement during identification or at any future time. New attributes or categorizations can be added at any time and are fully compatible with all previously existing information. Any subsequent access to the information will always show the latest version of all categories and classifications. 2. Capturing system element structure. Once the requirements have been captured, the allocation of requirements to sub-system elements takes 2.1. Graphically capture systems structure: Can the tool graphically capture Envision VIP tool provides a fully customizable graphical Full system implementation (such as architecture, functional decomposition, WBS, capture system not only for text but also for diagrams. etc.) and display them graphically such that requirements can be linked to them. Users can use any modeling methodology including, but not necessarily limited to, UML, Structured Analysis or Object Oriented Analysis. The tool automatically links every aspect of a diagram. It can also link to other diagrams and requirements. When on a diagram, a user only needs to double click on an item and the system will automatically display the linked requirement or diagram. Of course, links also work in reverse. A user can select a requirement, obtain a list of diagrams that the object appears on, and then directly jump to the desired diagram. If a modeling technique is not being used, the user can set up a virtual library with books and bookshelves. The tool is limited only by the users imagination.
Full
The tool has a completely customizable reporting facility that provides unlimited ways of viewing and building information from both diagrams and textual information.
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various As mentioned previously, the repository based management of all 3.1. Requirements derivation (req. to req, req. to analysis/text): The ability to Full requirements, relationships, allocations, and presentation of derive/create additional requirements and link between them such as information make this very intuitive. requirement to requirement, or requirement to text (representing trade studies) to derived requirements.
Page 223 of 450
Envision VIP v9.0

Full
Envision VIP is fully customizable. This allows a user to add any type of attribute to any requirement at any time to the repository such as weight cost or throughput. The attributes can even perform mathematical calculations such as summing costs or throughput. The connections, interactions, references, and relationships between requirements and various system elements are automatically maintained by Envision. All linkages are bidirectional and allow information to be accessed in any conceivable manner As mentioned above, Envision VIP is fully customizable. This allows a user to add any additional attributes to any requirement at any time. The attributes can even include totally new diagrammatic sub views, links to other programs, and even Internet/Intranet URL references.

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.
Full
3.4. Capture of allocation rationale, accountability, test/validation, criticality, Full 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. 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 In addition to the capabilities mentioned in Section 3.3 above, 4.1. Identify inconsistencies (orphans,...if so what kind of...): The tool should Full Envision VIP offers several other truly unique analytical allow the user to identify inconsistencies such as unlinked requirements or capabilities. A number of matrices are available to observe and system elements (orphans).
analyze the interaction and connection between requirements, processes, data, and tasks. In fact, the Envision repository and analytical tools allow for the easy definition and analysis of ANY user relationships desired. Envision VIP is also capable of generating diagram trees and any other desired type of hierarchal views of processes, data, or requirements expansion. The Envision Data Repository Browser also allows immediate access to all stored information. Several where operations allow users to find requirement references on diagrams imbedded in other attributes and documents.
Page 224 of 450
Envision VIP v9.0

Full
As mentioned immediately above, Envision has unique analytical capabilities that allow easy identification of all desire interconnections. Envision can show this in several different ways: via a Connections Matrix or via a special Connections button available on the spec sheet [property sheet] for any given requirement or system element. Envision provides CRUD matrix capabilities to identify the functions that Create, Read Update and Delete information. These capabilities are integral and unique to Envision and do not require any special data entry or manipulation. Envision is fully customizable. This allows a user to add any type of attribute to a requirement in the repository such as who is responsible for a requirement, who is responsible for its verification, completion date, level of completion, text description of progress, or any other desired property for tracking. A user can quickly and easily query the attributes for their current status or generate virtually any type of status report desired. The status of any of these properties or attributes can be easily updated via custom spec sheets or custom data entry matrices. The inputs can also be quickly imported from external programs like Excel, Access, Word, etc. As mentioned above, Envision supports calculated attributes including multi-level collection and rollup of user defined management metrics. A calculation macro language is provided for easy and intuitive specification and collection of this information. Envision VIP provides both an automatic tracking facility that records who created a requirement, who last modified it, an explanation of the reason for the change, and when changes were made. In addition, users can add their own custom tracking attributes

Full
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). 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
Full
Page 225 of 450
Envision VIP v9.0

Full
Envision VIP supports an unlimited number of baselines and revisions to baselines. Envision supports the capability to lock down selected sets of objects [e.g. requirements and system elements] and assign their control to a specified Controller/Owner/Specifier. Other team members can see the published baseline objects and revision. However, only the controlling official has the power to actually modify such a requirement or system element. Envision VIP provides log on protection, check-in/check-out protection, and user profile protection. Security levels can also be defined for users and projects when desired. Envision will then force the security levels only allowing assigned users with the proper security level access to your project. Users are also specifically granted access to projects. The data is not available to unauthorized users. Read or Write access is granted to each user for each project they are allowed to access.

Full
Full
Envision VIP provides a fully customizable reporting facility. This facility uses customized templates that can be used to layout information in virtually any format. Envision VIP can generate straight text, formatted text, XML, or HTML. The Envision RTF attribute type supports any Windows font on the machine thus supporting special character sets, mathematical symbols and formulas, and scientific notation, etc.. In place real-time spelling checks are provided by Envision. Suspect words can be immediately fixed or added to the user dictionary at either the user or project level. It follows closely the approach users expect from Envision provides an extensive data dictionary. Users can select any object from the dictionary and insert it into text using either drag or drop or an interface. Users can add an unlimited number of items to the dictionary. Item names, Requirements, System Elements, and any of their attributes, when inserted into Envision, are leveraged from ONE common definition. Thus, ALL references to any given item are automatically updated whenever any item renaming or attribute modification occurs.
Full
Page 226 of 450
Envision VIP v9.0

Full
Envision VIP can quickly generate numerous reports and graphics, including selected subsets of diagrams, charts, or graphs. Additionally high quality reports with headers/footers, automatic page numbering, etc. can be physically or logically printed and used in conjunction with other word processing or charting programs. Custom linkages can also be easily created to link directly with Excel, Access, Project, Word, etc. for any additional final polished output. Envision VIP provides a fully customizable reporting facility that allows a user to control virtually every aspect of an output document. Customized headers/footers, paragraph numbering, font control of paragraphs, and many other capabilities are included in the Envision reporting system. Envision has a very powerful RTF with spell checking capability. Envision VIP can produce formatted or textual output. Formatted output can be easily linked with systems, such as Adobe Distiller or the internal MS Office document publishing capability, to produce electronic on-screen finished documents. Other Windows capabilities support output to virtually any other printer, or file. Envision VIP provides a fully customizable reporting facility. Users can use this facility to generate status information. Additionally the extensive analytical tools like the various matrix analysis capabilities and query tools can be used to easily find any desired status information. The customizable Spec Sheets [property sheets] can easily display any specific status information desired. Since they are also customizable, the actual presentation of the information can be tailored to the intuitive desires of typical systems users. Envision VIP provides a fully customizable reporting facility. A user can generate status information and performance information. Access to any of this information is available via diagrams, matrices, and the Envision Data Repository Browser.

Full
Full
Full
Full
Page 227 of 450
Envision VIP v9.0

Full
Envision VIP provides a fully customizable reporting facility. A user can utilize any of the Envision query, matrix, and browser capabilities to access this information or generate custom reports showing compliance and non-compliance information. Envision VIP provides a fully customizable reporting facility. A user can generate any type of ad hoc query. In addition to the reporting facility, Envision VIP has a matrix analysis tool, data browser tool, and data repository tool. All these tools provide additional ad hoc query capabilities.

Full
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 7.1. Support of concurrent review, markup, and comment: The tool should Envision VIP provides the ability to record and report on Full support a team of engineers reviewing, marking up, and commenting on comments on any object in the requirements. Envision requirements or implementation alternatives. automatically records the user that made the most recent changes and time stamps those changes. Envision also has several roll back type capabilities. Individual modifications can be easily discarded to revert back to the last official published version of any object. Additionally, full system backups or check points can be easily produced whenever desired. Envision VIP has an advanced check-in/check-out facility. 7.2. Multi-level assignment/access control: Access by the team to the database Full Envision VIP is specifically designed for the multi-user must be tempered by multi-level access control (i.e. the ability to protect things environment. Envision VIP provides the ability to maintain a from being modified). This also includes the ability to submit changes into an published or working copy of any object [requirement, system approval cycle (for acceptance/voting) before committing the changes to the tool element, or attribute] as well as a private editable copy which is for everyone to see.
assigned to one and only one individual at a time. Items in an approved state can be easily frozen so that no one can modify them until a vote is taken and the system architect decides to modify the frozen or controlling definitions.
Full
Envision VIP can communicate with any other tool through its fully customizable import/export facility. Envision also has its own native CASE type capabilities and can easily leverage the requirements and systems elements mapping them directly to detailed designs, architectures and pseudo-code.
Page 228 of 450
Envision VIP v9.0

Full
Envision VIP can interface with virtually any other windows compliant tool. The tool can import and export, cut and paste various diagrams or textual information to virtually any other Windows application including Excel, Access, and various word processors etc. Through the powerful customizable reporting system and import/export capabilities including extensive XML capabilities, a user can interface to any program they desire. All information in Envision VIP's repository is accessible either by the tools reporting and query facilities or directly from the data tables. Extensive XML export/import capabilities are available. A powerful SaveAsWeb site feature allows models to be published to the web for browser access to the project Envision VIP provides an SQL query facility. Extensive XML capabilities Envision VIP can import data in a variety of formats. Often, this can be done by simply copying the text to the clipboard and then pasting it into Envision. The Envision formatted import/export is template driven and by simple modifications, the templates can be tailored to accept or produce virtually any desired ASCII textual tile desired. Extensive XML capabilities allow importing from numerous sources. A smart VISIO import facility allows complex diagrams with their accompanying backup data to be automatically imported into Envision. All data and models [even including meta-data] can be exported to and imported from Envision's powerful XML capabilities. Envision supports numerous intra/inter tool communications capabilities. Extensive support for Drag/Drop & COPY/PASTE sharing of information is supported both within Envision, and between Envision and numerous other programs including the MS Office Suite of applications. Additionally powerful XML import/export capabilities allow easy sharing of additional information.

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). 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? 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
Full
Full
Full
Full
Page 229 of 450
Envision VIP v9.0

Full Envision VIP allows the exchange of data between projects at any location. Various import/export capabilities are provided. When coordinating activities between two or more physical sites a combination of the check-in/check-out and import/export capabilities allow for the orderly control of project information.
Envision VIP repository allows the user to compare any datasets.

Full
Full
Single and Multiple. Envision's check in/out capabilities allow for the orderly support for workgroups. In contrast to many other systems which show inconsistent work in process to all users or experience "Reverse Race Conditions" [last person to check something IN can erase the work of others who happened to be concurrently working on changes but managed to check their changes in FIRST], Envision carefully avoids these problems. Windows Vista, Windows XP, Server 2003, and 2008. We recommend using the latest service patches for all systems. Commercially available database. [Raima Data Manager a widely used OEM DB]. SQL Server runtime used for one web viewing/commenting optional capability. Any standard Windows capable hardware. The application can run standalone or be configured to store projects on a central server. There are no special requirements other than reasonable network response and normal server access capabilities. Recommend 1+ GB RAM for XP; 2+ GB RAM for Vista and Server 2003 or 2008 and 10+ GB disk availability. We recommend Intel Core 2 or equivalent AMD and beyond however, it will actually run on much lesser hardware. Recommend 10 GB but can work on less. Depends mainly on the number and size of the projects you develop.
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements:
Full
Full
Full
9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 10. User Interfaces
Full Full Full
Page 230 of 450
Envision VIP v9.0

Full
Envision allows a user to view any number of concurrent diagrams and spec sheets at the same time. The data browser and matrix analysis capabilities also allow for concurrent access to different reports, diagrams, spec sheets, and queries. Envision also has a diagram tree view which allows the user to easily see the forest for the trees. It can also be used to very quickly switch between various diagrams and property sheets. Envision allows for multiple views and changes are reflected in all views. Envision has a fully customizable graphical input facility through which users can input and manipulate data. Envision diagrams reside on a virtual diagram and can be easily scaled and zoomed to accommodate any size diagram. The diagram items [objects], graphics, connections, and rules for connections and cardinality are all part of the customizable characteristics of an Envision model. Manipulation of these models results in an extremely intuitive graphic representation of any desired input. Envision is capable of producing presentation quality graphics while at the same time maintaining a rigorous and consistent model of any system.

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?
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? 10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data?
Full
Full
10.4. Which window's standard do you follow?: If your tool supports a window's standard, which one(s)?
Full
Envision is compatible with Windows XP, Vista, Server 2003 & Server 2008. The newest version of Envision uses the Microsoft .NET 3.5 framework. When publishing to the web the Microsoft IIS capabilities are used to provide maximum functional capabilities for the published web sites.
Page 231 of 450
Envision VIP v9.0

Full
The user can save any report and query for future use. Most of the powerful capabilities of Envision are controlled by model and template driven tables and forms. The performance of these table driven algorithms greatly exceeds many competitive macro driven alternatives. Our reporting system is driven by a series of playback type commands. Our calculation capabilities use an Excel-like macro language to specify the operators and operations involved. Batch exporting or reporting capabilities can be scheduled for overnight execution. Envision VIP has a very powerful web publishing/updating capability. It is capable of COMPLETELY generating a FULL web site. No additional effort is required to complete the web site. Envision has very powerful web viewing plug-ins for easily locating and finding any and all diagrams and item specifications via a Windows Explorer type web browser. A powerful commenting/discussion capability is also available for communicating with an unlimited number of stakeholders and collecting their respective feedback. Envision allows the user an unlimited number of undo's for diagram changes. Undo operations are also supported in our RTF attribute fields. Envision can meet virtually any output document standard. We follow the activities of ISO, the Open Group, OMG, DOD, NATO, various governmental organizations and others. We also work directly with a number of world-class consultants including the Process Renewal Group, Zachman International, BP Trends and others. Envision solutions/projects support numerous Frameworks including Zachman, TOGAF, Process Renewal Group, DODAF, et al. Industry specific terminology and dictionaries can literally be dragged and dropped into Envision ensuring subsequent and consistent use of terminology. [Note this ALSO INCLUDES support for NON-ENGLISH modeling activities. Envision uses Windows GUI standards.]

Full
Full
N/A
12. Support and Maintenance Page 232 of 450
Envision VIP v9.0

Full
Envision is sold with a maintenance agreement. Support is provided to a trained customer support group. Updates are provided to that group as needed and normally include a version update every 6-9 months. Network licensing is possible. Various contract and hardware options are available. Updates are free and released approximately every 6 months to customers with a maintenance agreement. Envision provides a complete set of online manuals and a complete Help facility. http://www.future-tech.com Support is available during normal business hours or under special arrangement either directly from the tool supplier or through a network of consultants. Future Tech Systems, Inc. maintains an active web site and international support pages with up to date information. Submission of problem reports and the distribution of updates is often done directly over the internet. This support site and e-mail messages are checked and processed in a timely fashion. Internet conferences are held on a periodic basis. User training 1-2 days. System Administrator training. 5 days. Consultation and project assistance are available as needed. Training is normally performed at the user/customer site. User training 1-2 days. System Administrator training. 5 days. Consultation and project assistance are available as needed. Available but not recommended unless an Envision Consultant is available to the user community.

12.1. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier?
Full Full
13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments
Full Full
Full
Page 233 of 450
Envision VIP v9.0

N/A
Having the ability to FIND and analyze the usage of virtually any "Enterprise Asset" is very important. Being able to track ownership/stewardship of requirements and trace them to strategic plans, processes, services, organizations, projects, or any other desired enterprise stakeholders and/or factors is highly desireable. Having the ability to communicate and gather comments via the WEB is also very useful. It is also very important to be able to create an "Intuitive User Friendly" environment which allow all levels of stakeholders to see the "Big Picture" in diagrams and reports that are elegant and straightforward. Having ALL diagrams/views, reports, documents driven by a common repository of enterprise data allows for maximum leveraging of enterprise information and avoidance of inconsistencies which would otherwise result if standalone files, documents and models are allowed to store key information in a set of linked office programs, files and folders.

Page 234 of 450
IBM Rational DOORS v9.2

Date of Submission: 8-Mar-10


Full Automatic input parsers analyze text for keywords and create attributes for recognized data such as references and security classification. Following parsing requirements can be automatically labeled based on any search criteria. The spreadsheet import does automatic updates of new versions. Other parsers may be user modified to compare existing with new data. Also, a document compare function can be used to compare two documents that have been separately imported Multiple parsers are available to read all kinds of data. All parsers may be configured to fit the users' particular needs. Automatic parsers will recognize requirements without intervention unless input data is ambiguous in which case the user will be prompted Requirements can be entered manually into DOORS. Full batch loading of requirements from multiple source formats is provided Requirements that are updated, either directly or in batch operations, retain their links. New versions of documents may be used to update the requirements, however, the use of constant requirements identifiers in the source documents significantly aids the process. It should be noted however, that DOORS provides a fully featured Microsoft Word-like editing environment to negate the need for external modification and in many instances remove the need for repeated update from external sources. Where needed links can also be loaded in batch mode from external files Page 235 of 450
Full
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. 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. 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
Full
Full Full Full

Full

DOORS provides supports for user-defined attributes. An attribute to classify /categorize requirements can be created. 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 DOORS Analyst provides a mechanism of describing Full system implementation (such as architecture, functional decomposition, WBS, functional decomposition and analysis in the form of UML 2, etc.) and display them graphically such that requirements can be linked to them. stored, viewed and edited directly within DOORS 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 DOORS can be used on its own to textually describe systems structure or in conjunction with DOORS Analyst which enables the textual descriptions and the graphical representations to be kept in synch with each other.
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 Derived or additional requirements may be created directly Full derive/create additional requirements and link between them such as using DOORS full requirements editor or using requirement to requirement, or requirement to text (representing trade studies) decomposition tools to automatically allocate, sub-divide or to derived requirements. combine requirements or other data. Links are created automatically by the tool when this is done. DOORS Analyst can be used to provide rationale behind how requirements have been derived i.e. capture requirements, perform some sort of analysis on them with DOORS Analyst and then write down any derived requirements from the Analysis. Full traceability is captured from high level requirement through to analysis and onto to derived requirements
Page 236 of 450

Full DOORS supports this using attributes associated with the requirements or independent data linked to the requirements. Performance metrics and other calculations may then be performed on the data. Metrics and other numerical data can be calculated/allocated/dispersed between requirements or other data at the same level or across different levels through links This is the natural way of working in DOORS and very little difference is made between linking up, down or at the same level. Note that linking is done through a simple drag-anddrop approach within the same document or between documents All rationale, test/validation, critical issues may be associated with the requirements using assigned attributes or other associated objects in the database. Importantly, this information may also be associated with the link directly as well as the object/requirements itself so that relationships may include a rationale. If required, DOORS can be set to prompt the user for rationale, etc, upon creation or change of any requirement or data object

Full
Full
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 DOORS can identify objects/requirements with no links at Full allow the user to identify inconsistencies such as unlinked requirements or all, with no outward links or with no incoming links or with no system elements (orphans). links of certain type. This can also be conditional on other data types. For example, show all unlinked tests that have not yet been performed or all links to failed tests
Page 237 of 450

Full Link analyses (up, down or sideways) may be performed from any starting point throughout the entire chain of links. This may be performed on line or printed in the form of a matrix style report. DOORS also offers the users visible "link-tips" to show links directly in the document and traverse them with the simple click of the mouse. Importantly DOORS can show an unlimited number of link traversals on the same screen at the same time for powerful analysis. Links are also visible in exported HTML versions of the documents and in data viewed directly via the Internet/Intranet using DOORS Web Access

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. 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
This is achieved in DOORS by the use of links and/or attributes.
Full
Pre-written scripts provided in the DOORS library support roll up values either within a set of requirements or across data linked from many modules. Analysis may also be automated to highlight requirements or other objects where actuals exceed allocated values. If necessary, such discrepancies may be automatically e-mailed to key users. DOORS also offers a statistics tool to automatically generate graphical displays of metrics or calculated values
5. Configuration Management
Page 238 of 450

Full DOORS automatically records who, what (down to the actual attribute changed), when and how automatically. The why can also be captured either through the voluntary entry of data by the user, or forced via DOORS' automated trigger mechanism such that the user would not be able to save the change without entering a rationale. DOORS also supports a full Requirements Change Management process for collecting change requests and formally reviewing them via a CCB before changes get into the documents or data sets. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. Full Full baselining is supported as well as the comparison of any two baselines. Baselines in DOORS are saved, locked versions of data sets such as requirements, system elements, tests, etc. that may be viewed, flexibly reported, but never changed Access control in DOORS may be achieved at three levels in DOORS. First, sets of data such as requirements in a document or all test cases may be controlled. Second, individual objects such as a single requirement may be controlled. Third, access controls may be imposed on attributes within objects. For example, users may be able to edit a comments attribute but not modify the allocated cost attribute. Access rights can also inherited by children from parent objects. Access levels include the ability to read, create, modify, delete and control access itself. Further, a mechanism called propagation allows access right to be imposed on documents or requirements not yet in existence

Full
Full
DOORS provides document templates for various military and commercial document standards.
Page 239 of 450

Full DOORS includes a spell checker. Other mechanisms such as acronym tables may be implemented by the user with DOORS modules making use of the Object Oriented database DOORS can generate color graphs and charts for displaying metrics data, results of calculations and statistics. Examples of such charts produced by DOORS include a volatility chart showing numbers of changes over time for a document or data set. These charts and graphs can be generated and printed directly from DOORS without the use of an external graphics package. DOORS document hierarchies may be viewed graphically and traceability may be viewed as "tree" structures in the Traceability Explorer Title pages, contents pages, headers, footers, graphics, etc. are all part of the DOORS print output

Full
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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to see 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full Full Full
DOORS provides a print preview capability DOORS provides support for status information
DOORS configurable/programmable attributes allow status monitoring of any held information, either within a document or across links in multiple documents Links and link attributes combined with Full configurable/programmable attributes in DOORS support reporting and statistical analysis of compliance or noncompliance 6.6.3. Other ad hoc query's and searches: The requirements management tool DOORS supports searches and queries on any data Full should support ad hoc query's and searches per the user's discretion. according to users needs either by sets that fulfill criteria or each next object that meets defined criteria. Search and filtering can be on attribute value, substring searches or the presence or absence of links 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. Page 240 of 450

Full DOORS provides support for both informal and formal reviews. Informal reviews can be conducted using the DOORS Discussions feature - users can raise discussion topics against individual requirements and other users can add their comments to open topics. When the discussion is concluded the owner can close it. Both DOORS desktop client users and DOORS Web Access users can participate in discussions (enabling stakeholders like development, QA, marketing, customers or suppliers who may not need full access to the requirements to participate in collaborative evolution and review of requirements). Formal reviews are supported through the Requirements Change Management capability. Requirements documents can be put under formal change control, and changes routed through a Change Control Board for approval. Full redline markup of proposed changes is supported.

Full
DOORS provides multi-level role-based access control access control at project, document, requirement and requirement attribute level is provided. DOORS provides a formal Requirements Change Management capability for submission of proposed changes. Proposed changes are routed to members of the Change Control Board to review, comment, and approve/reject online. Accepted changes are promoted into the document or dataset automatically.
Full
DOORS has the most flexible method of inter-tool communication. Not only is there a full API, but the DOORS eXtension language (DXL) can be used to write imports and exports to other tools in almost any format. DXL being Clike is very easy to learn and use. DOORS also supports OLE automation for integration such as those used by Microsoft tools
Page 241 of 450

Full The IBM DOORS program for interfaces with other tools is the most comprehensive in the industry. We now have over 25 interfaces to the most popular tools for design, analysis, text, CM, etc. For a full list of current interfaces contact IBM (www.IBM.com). DOORS has the most flexible method of inter-tool communication. Not only is there a full API, but the DOORS extension language (DXL) can be used to write imports and exports to other tools in almost any format. DXL being Clike is very easy to learn and use. DOORS also supports OLE automation for integration such as those used by Microsoft tools The DOORS extension language allows data to be accessed more easily than SQL using standard high level programming techniques. DXL is easily programmable by those conversant with C such that SQL knowledge is unnecessary DOORS can import information in many forms such as MSWord, ASCII, Spreadsheet, FrameMaker, Interleaf and RTF, so that structures, attributes and links may be set up automatically without manual input

Full
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
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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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
Partial Full Full
DOORS offers a feature called DDM (Distributed Data Management) where users can export controlled sections of the database with read or read/write access to other databases. Data can be returned to the master database at any time with full merge abilities. Distributed parts can be defined down to the single requirement/single attribute level DDM (see above) and the import methods provided by DOORS include the capability to compare data to see if it is new or existing. These comparisons allow updating of existing data and creation of new requirements. Updates can show inconsistencies and variations between data sets
Full
9. System Environment
Page 242 of 450

Full Full DOORS supports multiple concurrent users The DOORS database server is supported on: Windows 2003 Server Windows XP Professional Windows Vista (Business or Enterprise Edition) Solaris 9 and 10 HP-UX 11i 64-bit Red Hat Enterprise Linux 4 & 5 The DOORS desktop client is supported on: Windows XP Professional Windows Terminal Server on Windows 2003 Server (Standard or Enterprise Edition) Windows Vista (Business or Enterprise Edition) Citrix Presentation Server V4.5

9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data?
Full Full Full Full
Dependent on number of users, size of database, and profile of usage. Please contact IBM for details. Dependent on number of users, size of database, and profile of usage. Please contact IBM for details. Dependent on number of users, size of database, and profile of usage. Please contact IBM for details. Dependent on number of users, size of database, and profile of usage. Please contact IBM for details. Yes. Yes.
Full Full
Full
Yes
Page 243 of 450

Full Full The DOORS user interface is based on Windows wherever appropriate Automation of tasks is supported through a user configurable language. These automated scripts may then be added as menu items and appear just like other functions of the tool. Alternatively scripts may be run from the operating system command line for batch operation Yes, DOORS Web Access provides web browser access to the DOORS database server. DOORS supports multi-level Undo back to the last save. Documents adhering to various military and commercial standards in multiple output formats can be produced from DOORS. DOORS also supports the needs of the disabled as defined in Section 508 of the US Disabilities Act. Our development processes are ISO 9001 compliant

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?
10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full Partial N/A
12. Support and Maintenance 12.1. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes
Yes. 30 days. Yes, FLEXlm DOORS is normally released every 6 - 12 months with additional patches to facilitate support. Yes http://www.ibm.com/software/awdtools/doors Tool support is available during normal business hours around the world. Weekend and out of office support can also be arranged. Yes. IBM hold annual User Conferences around the world. Please visit our website for details. Yes. Please see our website for details. IBM also offers requirements management methodology and requirements writing techniques courses. Yes.
Full
Full

Full The tool can be learnt in a single day although IBM provide additional training courses . Please see our web site for details. Tool training is not required for installation View and update data in context: Users should be able to view and update requirements in context (usually a document format) along with other associated data (attributes and traceability). Not having to switch to completely different display models or tools to view and update all the data associated with requirements greatly improves understanding and productivity. Data model definition: The ability to group logical sets of requirements together in projects or folders and to define the legal relationships between these sets that support the users process supports the development of a consistent data model and reduces the learning curve for new project members because they are guided through the process. In addition to this, the ability to insert and edit UML analysis in the context of the requirement they are performing the analysis against (i.e. inside of the requirements management tool itself). Suspect links. The indication that data on which a requirement is dependent has changed without having to change your current context or run a report improves the awareness of change and ability to maintain a consistent data set.

13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full N/A
Page 245 of 450
IBM Rational RequisitePro v7.1



Full
Full Full
Full
1.4. Manual requirement identification: A manual means of identifying or Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Full from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Full to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Full classify/categorize requirements during identification 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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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

Full

Full
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the Full 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. 4.4. Requirement performance verification from system elements (roll up of None 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). Page 247 of 450

Full

Full
Partial
6. Documents and other output media 6.1. Standard specification output (if so what kind): The requirements Partial management tool should output documentation in various military/commercial standard formats (490, 2167, etc.). 6.2. Quality and consistency checking (spell, data dictionary): The tool should Partial also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Partial management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements Full management tool. 6.6.1. Technical Performance Measurement status accounting: Status current Full technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Full compliance/non-compliance to various requirements Page 248 of 450

6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Full tool interface with or talk to? 8.1.2. External Applications Program Interface available: To support the wide Full 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). 8.1.3. Support Open database system (standard query access): Does the tool IBM DB2 V8.1, V8.2, V9.1 Full support Open Database standards such as standard query languages or IBM DB2 Universal Database Components for Rational exchange formats? Products V8.1, V8.2, V9.1 IBM DB2 Express V8.1, V8.2, V9.1 IBM DB2 Express-C V8.1, V8.2 Oracle 9.2, 10 Microsoft SQL Server 2005; 2000 SP2, SP3, SP4; V7 SP4 Note: Microsoft Access software is not supported. 8.1.4. Import of existing data from various standard file formats?______: Does Full 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? Page 249 of 450

Full Full Full

8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full
Full Partial Microsoft Windows 2000 Server, Advanced Server SP4 Microsoft Windows 2003 Server, Enterprise Server Initial, SP1 Microsoft Windows 2003 Server x64 (must be running in 32bit mode on 64-bit processors) Microsoft Windows Vista, Enterprise, Ultimate and Business editions
9.3. Commercial vs. unique database: Does the tool use a proprietary or Full commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration Full requirements: 9.4.1. Memory requirements Full 9.4.2. CPU requirements Full 9.4.3. Disk space requirements Full 10. User Interfaces 10.1. Doing one thing while you are looking at another: Does the user have the Full ability run a report and look at a requirement at the same time? 10.2. Simultaneous update of open views: If the tool allows for multiple Full windows/views into the tool--does a change in one view automatically reflect in all other views? 10.3. Interactive graphical input/control of data: Does the tool support graphical Full input and manipulation of data? 10.4. Which window's standard do you follow?: If your tool supports a window's Full standard, which one(s)? Page 250 of 450

Partial

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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full Partial N/A
Page 251 of 450
inteGREAT v4.7


Full inteGREAT enables users to develop and manage requirements knowledge base. It also provides the capability to identify and define enterprise knowledge using 10 dimensions using variety of requirements templates like RUP, Use Case etc. inteGREAT provides this capability by producing a Difference/Comparison report between two versions of projects and also maintains log of events and version history of documents published. Based on the knowledge or requirements identified in elicitation process, inteGREAT automatically produces requirement documents and generate use cases and test cases. Based on the knowledge or requirements identified in elicitation process, inteGREAT automatically produces requirement documents and generate use cases and test cases. Users can enter project requirements in elicitation wizard manually. User can write requirements in excel/word and that can be imported into inteGREAT. Documents produced are on demand, any changes in requirements will automatically be updated with a single mouse click.
Full
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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification
Full
Full
Full Full
Full
Based on the properties selected, all types of requirements can be categorized/classified in inteGREAT tool. 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. Full Page 252 of 450
inteGREAT v4.7
Full inteGREAT captures all types of requirements graphically including the entire system 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. 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
inteGREAT captures the business, system /user, functional and data requirements textually and allows to graphical transformation.
3. Requirements flow down: 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 Yes derived or additional requirements may be Full derive/create additional requirements and link between them such as created using inteGREAT, and links are created requirement to requirement, or requirement to text (representing trade studies) automatically by the tool when this is done. to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, inteGREAT has the capability to set up performance, Full cost, etc.): The ability to link performance requirements to system elements effort(hours/days) and risk requirements. 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 inteGREAT supports full Bi-directional requirements Full requirements to system elements can be accomplished from either end of the linking. 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, inteGREAT allows to associate rationale, Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the test/validation, critical issues with the requirements ability to attach rationale, assignments, criticality, test/validation and many other using comments or requirement properties. issues to the requirement, allocation, and the system element to which a requirement is linked. 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 inteGREAT fully supports this capability by identifying Full allow the user to identify inconsistencies such as unlinked requirements or orphan requirements and also produce various system elements (orphans). documents to show unlinked requirements
Page 253 of 450
inteGREAT v4.7
Full inteGREAT shows information on linked objects from where they are coming from and with what requirements they are connected and in how many views they are reused. inteGREAT provides this capability by displaying if the requirements in project life cycle are in "defined", "approved", "in progress" on implementation status etc.

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. 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. 4.4. Requirement performance verification from system elements (roll up of actual): Once performance requirements have been allocated to system elements, the requirements management tool should support the verification of those requirements by rolling up actual and reporting on variances (this is the allocated weight versus the actual weight). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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
Full
Full
inteGREAT provides view/change log feature which records changes by made by who, what, when and where in the project
Full
inteGREAT provides baseline and version management of projects and specifications which can be compared for differences.
Full
Full
inteGREAT provides custom reporting capability which allows to produce any kind documentation. Specification and spell checker verifies the quality of requirements.
Full
Page 254 of 450
inteGREAT v4.7
Full Custom reporting facilitates this.

6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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
Custom reporting facilitates this.
Documents can be pre-viewed in the tool before they can be exported to word or excel All requirements can be marked with appropriate Full status values. All requirements can be marked with appropriate Full status values, goal/requirement traceability provides information on associated functional requirements and their progress. 6.6.2. Requirement progress/status reporting: Status reporting on current All requirements can be marked with appropriate Partial compliance/non-compliance to various requirements status values. 6.6.3. Other ad hoc query's and searches: The requirements management tool Ad hoc and advance search capabilities of Full should support ad hoc query's and searches per the user's discretion. inetGREAT fulfills this requirement. 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 inteGREAT supports concurrent reviews and Full support a team of engineers reviewing, marking up, and commenting on discussions and receiving updates from other users requirements or implementation alternatives. on changes made to the project requirements. Full 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. 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.). Partial
Full
Supports integration with HP Quality Center , MS VSTS, XMI for design tools, XML, CSV,Word, Excel.
Page 255 of 450
inteGREAT v4.7
Full Apart from above mentioned, inteGREAT supports Erwin , MS office, MS project, Share Point Portal integration

8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database?
Full
Full
SQL server , XMI/XML
Full
We support XMI/XML data exchange.
Full Full Full
We support XMI/XML data exchange. inteGREAT supports this through Import export utility and Specifications
Full
inteGREAT provides this capability through Specification Checker, Baselining and difference/comparison report features. Multiple concurrent users Windows 2000/ 2003 / XP / Vista/Windows 7 inteGREAT uses SharePoint as a database repository and it can also HPQC and TFS ,
Full Full Full
Page 256 of 450
inteGREAT v4.7
1. Dot Net Framework v 1.1 2. Service Pack 1 for Dot Net Framework v 1.1 3. Microsoft Dot Net 1.1 SP1 hot fix 899511 (http://support.microsoft.com/?kbid=899511) 4. Microsoft Dot Net 1.1 SP1 hot fix NDP1.1sp1KB928366-X86.exe (http://support.microsoft.com/?kbid=928366) 5. inteGREAT setup file 6. Microsoft Visio 2003 or above version 7. Microsoft Visual SourceSafe 6.0 8. Microsoft SharePoint Server in either of the following flavours i. MOSS2007 ii. WSS 3.0 1 GB RAM or above 1.5 or above GHz Hard disk space: Minimum 55 MB Yes Multiple views of knowledge base can be opened updated at a time Yes inteGREAT support this capability. inteGREAT user interface is based on Windows wherever appropriate

9.4. Resource requirements: Please identify hardware/software configuration requirements:
9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface?
Full Full Partial
Full
Yes, inteGREAT provides web browser interface for online requirement management. inteGREAT provides capability to revert to last saved state.
10.7 Edit Undo Function Support 11. Standards
Partial
Page 257 of 450
inteGREAT v4.7
N/A Documents adhering to various military and commercial standards in multiple output formats can be produced from inteGREAT

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier?
Full Full Full inteGREAT is released twice a year with additional patches to facilitate support. Yes , online help is available with the tool and also on www.requirementscafe.com Yes, Please see the link below: Corporate Website : /www.edevtech.com/ Whether you want to schedule a services engagement, speak to an eDev consultant, need inteGREAT training or online support or have questions regarding your new inteGREAT software, please feel free to contact us by your preferred means - we are here to help you: Contact Information:Tel:416.469.3131Toll Free:1.877.473.2881 Email:info@edevtech.com inteGREAT online user community : www.requirementscafe.com We conduct beginner/intermediate and advance boot camp trainings twice a month with no cost associated. Yes we provide on-site trainings. 4-5 weeks that includes self training through online training manuals, video etc, on-going boot camp trainings followed by Advance inteGREAT course and then mentoring by inteGREAT expert .
Full Full Full
Full
Full
13.2 Training available at 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 Full
Page 258 of 450
inteGREAT v4.7
Full We provide installation instructions plus additional technical support if required. inteGREAT supports uniqure capabilities of a true Requirements Management tool such as Requirement Elicitaion, Automated Simulation UI generation, Custom Reporting,Automated Diagraming, Automated Use case Test case generation and Requirements Reuse.

N/A
Page 259 of 450
IRQA v4


Full IRQA can either import the unique IDs for Requirements, Services and Test Cases from the document or assign them following the numbering pattern specified by the user ( Prefix, Suffix, number of digits, etc ). During the import process, elements imported from documents can be assigned to different subsystems, access partitions or specific element type inside the IRQA repository. If requirements are captured from an external document (MS Word, MS Excel or XRI format), IRQA analyses them in order to identify the new requirements and the modified ones. The user is allowed to accept changes, reject them or capture the modified requirements as new ones with a link to the old ones. This is also available for services and test cases.
Full
Page 260 of 450
IRQA v4
Full Parsing can be used in IRQA in several ways: 1. Parsing can be used for automatic identification of requirements and their hierarchical relationships from a Microsoft Word text file. By simply selecting MS-Word type styles or delimiting tags, requirements are parsed and imported from documents into the requirements repository. 2. Parsing can also be used for automatic identification of requirements from a Microsoft Excel file. Not only requirements code, name, description and hierarchy can be imported but attributes such as priority, status or any other user defined attribute can also be imported by simply selecting the column heading of the Excel sheet where they appear. 3. Requirements and their attributes can also be imported from XRI format files. This is an XML-based format defined by Visure Solutions in order to allow the exchange of information between different RM tools. 4. IRQA Text Analyzer is mainly used for discovering (and assigning) relations between reqs and different specification items (concepts, services, attributes) by parsing reqs description. 5. CSV files can be used to import requirements. 6. Finally, Quality Analizer parses requirements descriptions in order to measure their quality based on some rules customizable by users (description length, use of desing words, ambiguity...)

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.
Full
Codes can be user configured so that the tool automatically proposes a value. The code is composed of a numerical part and, optionally, a prefix and a suffix.
Full
The codes automatically proposed by the tool can be manually change
Page 261 of 450
IRQA v4
Full IRQA provides three methods: 1. IRQA's import utility ( see 1.2). 2. Via CSV ( text delimited ) files. 3. Using IRQA-Face ( a COM API ), requirements can be entered into IRQA repositories from external applications. 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 The IRQA Report Manager provides the ability to schedule report generations in batch mode, including any information in the database, including traceability, metrics, calculations or charts, and in any output format, including HTML, PDF and rtf. The tool allows to create new attributes to be assigned to the requirements. Requirements grouping, classification, and categorization are fully supported via two methods: 1. Creating classical hierarchical "hard" structure ( assigning parent requirement or creating a child from another ) 2. Using our "soft" classifying method based on usercreated attributes. It will allow users to have as many attributes ( and so, points of view for requirements classifications ) and attribute values as they need. They can be shown either as a tree, or in a graphical mode through active block diagrams. 2. Capturing system element structure. Once the requirements have been captured, the allocation of requirements to sub-system elements takes

Full
Page 262 of 450
IRQA v4
Full In addition to the generic structural elements, the tool provides the following graphical features: 1. Block diagrams: They represent Blocks and the relationships between them, and they are used to navigate across the specification and to show traceability between elements contained in related blocks. In this sense, block diagrams may serve as Traceability Diagrams, WBS or functional decomposition, among others. 2. Domain diagrams: They are used to represent Domains and their relationships (basically used as Architecture diagrams or graphical representations of subsystem decomposition). 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 The tool provides several elements to textually capture system structure: 1. Multivalued attributes: Can be used as classification elements that depend on the problem description. 2. Blocks: Sets of elements with some common characteristic (for example, functional requirements, system requirements, stress test cases, etc.). They are qualified containers. User defined attributes of different types (numeric, date, text, enumerated, etc.) can be assigned to different blocks, which allows to characterize requirements and other specification elements according to the structural group they belong to. 3. Domains: Groups of elements that permit to represent sub-systems or other architecture-dependant elements.

3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various
Page 263 of 450
IRQA v4
Full IRQA provides several mechanisms to derive requirements: 1. Traditional hierarchy 2. Services: Explicit specification elements separated from requirements, which may be linked to them with the semantics "service solves requirements". They are traditionally known as "System/Software Requirements", and may be described as Use Cases within IRQA. 3. Block diagrams: Blocks may represent different levels of requirements detail, and the relations between them represent the derivation/partitioning from one level to another (traceability matrixes can be accessed through these relationships). 4. Relationships between requirements: The user can establish direct relationships between manually selected requirements and enter information on the reason why this relationship is established.

Full
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
Services are IRQA system specification elements. They represent system functions and can be directly linked to any type of requirements (functional and non-functional). Quantitative values may be associated to requirements (nonfunctional in the case mentioned) or services through userdefined dynamic attributes. In IRQA, services are system specification elements. They can be directly linked to requirements. IRQA allows to visualize indirect links through coherent intermediate steps. Block diagrams allow not only to show a traceability chain in both directions ( req->system element, system element->req ), but also to edit and show derived traceability relationships between non-subsequent blocks. Intermediate elements depend on the derivation structure established. Basic derivation in IRQA takes into account Services (and other lower level specification items, like activities and sub-activities).
Page 264 of 450
IRQA v4
Full Basic requirement's structure may be enriched by the addition of customized attributes such as criticality, importance, cost, etc., that can be of any type (text, Boolean, numeric, date, user-definable types, etc.) Tests are explicitly treated by the tool through specific modeling elements called "Test Scenarios" that may be allocated to requirements or services to represent acceptance tests. Moreover, each requirement has a Fitcriteria property to establish the criterion to check nonfunctional requirements compliance. Traceability Matrices include req.-system element or req.test scenarios relationships, among others. For each requirement a Comments field is available, where issues of all kind can be documented. Apart from that, any file type ( text, tables, spreadsheets, drawings, etc ) can be linked to a 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

Page 265 of 450
IRQA v4
Full The list of requirements can be ordered by the system functionalities related to them. This simple feature allows the user to immediately identify requirements which are not taken into account in the solution specification, or system functions which are not linked to any requirement. The Traceability Matrix allows users to examine the relationships between requirements and their related system elements ( concepts, test scenarios, services, diagrams, etc ). For example, one can discover requirements not related to any test scenario by simply showing the Requirement-Test Scenarios Traceability Matrix. So, that information can be used as an analysis tool for identification and correction of ambiguity, contradiction, duplication and/or omission. Suspect links management highlights the relationships in which at least one of the members has been modified, and therefore, the relationship needs to be checked in order to avoid inconsistencies. Apart from these features, the tool provides the following automatic consistency checks and reports: Undefined elements. Non-linked elements. Requirements with no tests associated. Consistency according to block diagrams which checks the consistency of links according to the diagrams that represent the structure of the specification.

Page 266 of 450
IRQA v4
Full In the Traceability Matrix, all the cells display several options to navigate through the elements involved. At the element level, specific tabs in all views show listed basic information about all elements linked for each requirement/service/test scenario/etc. So, you don't need to navigate among different views to have full visibility of existing links. On the other hand, Block diagrams in combination with direct and indirect traceability matrices and associated reports provide this feature at the architectural level. IRQA also provides an XMI interface with OO tools that allows to export/import UML elements and establish direct links between requirements and implementation classes. 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 Complete traceability throughout lifecycle ( from requirements to acceptance test ) is supported within IRQA: no need to go to any other tool to verify whether the requirements have been met or which requirements are fulfilled by which system element. Impact analyses and change assessments supported. Additionally, IRQA support the traceability between tests and requirements, allowing through this to verify which requirements are validated by tests. This can be done graphically by a traceability matrix filtering by related/non related elements. In the same way, this can be done between requirements and services (use cases)

Page 267 of 450
IRQA v4
Full Requirement attributes can be used to record "planned" vs. "actual" values. Both values can be included in reports so the variance can be implicitly shown. Additionally with the new workflow feature it is possible to associate a script to an attribute value transition. This script can update the value of another attribute that will show the variance

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
Complete individual requirements ( and also other elements like services, test scenarios, diagrams, blocks...) evolution through version control may be maintained in the repository. The history of each element may be tracked through the versions ( configuration audit logs ) and the rationale of each change may be saved. Requirement date, time, user, change reason, among others, are recorded in addition to requirement name and description changes in requirement history. Users can compare two different versions of an element obtaining the differences between them.
Full
Configuration management is supported in two different ways in the tool: 1. Project versions. IRQA allows to create project versions, storing the current state of all specification elements. These versions can be compared or restored. 2. Baselines. IRQA also allows to create multiple baselines for each project , where the user can select the elements (requirements, services , test scenarios, diagrams...) that will belong to it. Baselines can be compared and restored. 3. These functions are available only to users with the appropriate security level.
Page 268 of 450
IRQA v4
Full As an administrative feature, the tool provides complete access controls, based on Access Partitions (project organization) and User Profiles combination, configurable for each project. The specification administrator can define the different access rights (no access, read, read/write) that each group has over each partition. The tool also provides a check-in/check-out mechanism to avoid incoherent updates to the repository. 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
Reports can be configured by the user, including which information to include in the report, styles to use, position inside the template where IRQA will write the information, fonts, etc. Since you can define your own report set and structure, you can obtain reports in the standard format you may need: 490, 498, etc. These reports can be then exported to any format like PDF, MSWord (.doc), HTML, etc. Additionally IRQAFace can be used to access IRQA elements and use then into third party applications like crystal report Grid-like views and traceability matrixes can be exported to Microsoft Excel files. Diagrams can also be exported to .bmp or .jpg files. Through Quality Analyzer requirements are checked so they have the right extension, lack of ambiguity, have dictionary terms, etc. Additionally graphical and textual report are generated with the quality of our requirements and suggestion to improve them Supported diagrams ( class diagrams, use cases diagrams, block diagrams, etc.) can be included in reports. Charting and graphing can be easily done connecting IRQA repository to MS Access or Excel via ODBC.
Full
Full
Page 269 of 450
IRQA v4
Full Users create their own document templates, look & feel and report structure, including configurable tables. IRQA Report Manager can combine dynamic information obtained from IRQA with static information previously added to the document in order to obtain finished documents after generating them. Additionally, once generated, these documents can be exported to HTML, .doc, PDF, etc. Before generating the reports, users can see the final result of the report so it can be reviewed. Grid-like views and traceability matrices can be exported to Microsoft Excel files, where they have exactly the same appearance as inside the tool. By using the appropriate Status attribute(s), users can track the status of each element, at different levels, and include status information in IRQA reports. It is also possible to filter the information to be included in the report according to this criterion. Since architecture, functional decomposition or WBS can be managed via Block Diagrams, users can add technical progress and technical risk/difficulties attributes to each block. This information, along with cost assessment information ( which can be maintained within IRQA ), and schedule performance will provide Project Managers a more accurate progress assessment of their projects. Besides that, a customized Technical Performance Measurement status report can be created through IRQA Report Manager based on above attributes. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements Full As in 6.6.1, Req.Name-Req.Status is one of the possible reports IRQA may produce listing what has failed or passed up to report date.

Full
Full
Full
Page 270 of 450
IRQA v4
Full By using our powerful Filter Engine, you can obtain complex searches ( AND, OR, and NOT operators supported ) filtering by any combination of: author, date, relationships, text, classification item, user-defined attributes, parent requirement and specification item, among others. In any case, if you need an ad-hoc query, you can always access ( in read-only mode ) the repository via SQL (ODBC mechanism), although up to now, IRQA users have never needed this option. 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 7.1. Support of concurrent review, markup, and comment: The tool should IRQA uses the standard check-in/check-out technique, so Full support a team of engineers reviewing, marking up, and commenting on when a requirement is being modified, it cannot be modified requirements or implementation alternatives. by any other user until it is explicitly released, although other user can read it while the requirement is locked ( if he has the appropriate read permission ). With IRQA, users can set different partitions and the database will remain consistent among all "views". Furthermore, any change will be reflected dynamically across the database. For managing implementation/specification alternatives: 1. You can always create implementation/specification alternatives by using IRQA modelling capabilities. 2. And relate them to the specific item they come from ( requirement or change proposal ). For each requirement a Discussion tab exists, where every user with read permission can enter a text commenting on some aspect of the requirement, this will lead to a small discussion forum associated to the requirement

Page 271 of 450
IRQA v4
Full Fully user-defined access control supported. The IRQA administrator can define different access levels, by: 1. Creating a Users structure, via User Groups 2. Creating Partitions, and including specification elements in them 3. Assigning privileges to the User Groups to those partitions. ( Privileges include: Read Only, Write Own and/or Write all ) You can only make changes ( such as status in approval cycle ) to those elements you have been granted permission to. The approval cycle can be customized for every project or organization through the user-defined attributes. 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

Page 272 of 450
IRQA v4
Full 1. XMI 1.0 (XML Metadata Interchange OMG standard) Import/Export capabilities with UML design tools: Rational Rose, Together, Rhapsody, Magic Draw and any XMI compliant tool. 2. IRQA-Rational Rose live-link. 3. Export/import of requirements to/from other RM tools via XRI (an XML-based format). 4. Microsoft Word: requirements capture, reports generation. 5. Microsoft Excel: requirements and attributes capture, gridlike views and traceability matrix export. 6. SCCI compliant Configuration Management tools (PVCS, Visual Source Safe, CVS, etc.) to manage the associated files. 7. Interface with Mercury TestDirector to allow visualization of TestDirector test cases in IRQA and establishment of direct links between IRQA requirements and TestDirector test cases. We provide an open COM API ( IRQA-Face), which is intended to be used for those purposes via both compiled and scripting standard languages ( ASP, Visual Basic, PHP, etc ). 1. Any commercial RDBMS can be used as IRQA repository container ( Oracle, Informix, SQL-Server, MS-Access, MySQL ). 2. You can use SQL for accessing IRQA repositories ( although only query access is recommended ). 3. Standard ODBC and DSNs mechanisms are used for connecting IRQA to repositories.

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). 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
Full
Page 273 of 450
IRQA v4
Full Five import/export standard formats are allowed: 1. CSV format, for the entire project structure. 2. Microsoft Word files, for requirements and services. 3. Microsoft Excel files, for requirements and services with associated attributes. 4. XRI (XML-based format) for requirements, attributes and specification structure. 5. XML format: XMI for UML elements. The standards used to exchange data are the ones mentioned above: CSV and XML (XRI and XMI). See 8.1.4.

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
Full Full
IRQA-NET, our web client, allows users in different locations to read and modify IRQA data bases through the Internet, with a browser. IRQA also allows the exchanging of information between different installations through the import/export of CSV and XRI files. IRQA Project Comparison functionality allows users to view differences between IRQA projects/datasets.
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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full
Full
Full
IRQA is engineered as a fully multi-user environment, and supports as many concurrent users as your commercial DB engine can manage. 1. PC-Client: PC platform using Microsoft Operating Systems: MS Windows 95, 98, Millennium, NT 4.0, 2000, XP, Server 2003. 2. Web Client ( IRQA-Net ): Any Java enabled web browser. 3. License Server (multi-user): PC/NT 4.0, 2000, XP, Server 2003. 4. Repository : Any RDBMS server with ODBC connectivity.
Page 274 of 450
IRQA v4
Full Commercial database. The commercial RDBMs supported are: Oracle, MS SQLServer, MS Access. Projects are scalable: they could initially be created in MS-Access and, if they grow, they could be exported into Oracle or SQLServer on-the-fly.

9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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?
128 MB minimum. 256 MB minimum for Administrators (for repository a Pentium II or higher. 100 MB per client. The tool GUI is designed in independent windows. For example, two different projects may be opened at the same time and different views of the same project may be managed in parallel. Views are automatically updated, although some of them have a Refresh button to prevent users from being shown unnecessary updates and save reload time. Data input in IRQA through the user interface includes all controls needed to prevent erroneous data from getting into the data base. Different graphical modeling techniques ( UML, E/R, DFDs, etc ) are fully supported by IRQA. Graphical editors are included to create and maintain those graphs. MS Windows copy and paste functionality is allowed for all text fields in the tool, and also in order to duplicate elements in an IRQA project or even to copy elements between different IRQA projects. Data input in IRQA are written on the data base directly after being entered .
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? 10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data?
Full
Full
10.4. Which window's standard do you follow?: If your tool supports a window's Full standard, which one(s)? Page 275 of 450
IRQA is a Microsoft Windows application following the look & feel of standard Microsoft applications.
IRQA v4
Full Although IRQA automates tedious tasks, we provide an open COM API (IRQA-Face), which can be used for those purposes by using standard scripting languages, such as ASP or PHP, not having to learn a new scripting language.

10.6 Web browser interface? 10.7 Edit Undo Function Support
Full Full
IRQA -Net allows users to access IRQA repositories with a standard w IRQA includes a wastebasket where deleted items are stored. Users can restore items from the wastebasket if they have permission to. IRQA also implements a fully version system with the undocheckout option that allows to undo the changes in the element Database: Open ODBC connection to repository Information exchange: CSV format, XML format Graphics: UML notation, E/R diagrams, DFDs. Output documents: Reports may be produced in a variety of industry standard formats or user-defined formats.
N/A
Full
Full
Visure Solutions guarantees that the products shall substantially work in accordance with the User's Manual of each product for a period of 90 days, provided that the same are operated in accordance with the technical and operational specifications that are featured in the User's Manuals. IRQA supports both floating and seat/node locked licensing. For now, a proprietary license manager is used, although future releases may use a commercial one. Major IRQA versions are released annually, approximately, available at no cost under Maintenance contract (25% of the list price of the licenses at the time of purchase). Official patch updates are also available at no cost under Maintenance contract.
Full
Page 276 of 450
IRQA v4
Full Both online help and printed manual are included with the tool. The IRQA CD includes also a full set of Manuals in PDF format, as well as a set of tutorials, Basic Tutorial and Advanced Tutorial, to support the user in learning the IRQA features. E-mail: info@visuresolutions.com URL www.visuresolutions.com Visure's Helpdesk around the world: Spain: +34 91 8 06 17 13 Rest of the world: See list of partners in http://www.visuresolutions.com/company/partners/listofpartn ers.php In addition, questions can be emailed to: support@visuresolutions.com Basic support includes: Bugs and associated fixes/patches information. Installation & configuration support. Germany is the first country to hold the IRQA Germanspeaking User Group, involving both local representatives, IRQA managers and customers. This User Group not only includes support issues, but also user needs for future evolutions of the tool. The following IRQA training courses are available: IRQA Basic Course: 1 Day ( 7 hours ) IRQA and Requirements Engineering Advanced Course: 3 days ( 20 hours ) Customized training is also available. IRQA training courses can be made available at customers location. The training time ranges from one to three days to become proficient with the tool, depending on the user profile and the level of interaction the student will have with IRQA.

12.5. Provide Internet Web page location for company/tool info
Full
12.6. Phone support: What type of phone support is available from the tool supplier?
Full
Full
Full
13.2 Training available at 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 Full
Page 277 of 450
IRQA v4
Full Software installation is very easy. An Installation Wizard leads the user through the process. Additionally, an Installation Guide is provided in pdf format. No specific training is necessary.

Page 278 of 450
IRQA v4
N/A 1. IRQA supports the complete Requirements Engineering process: Requirements Capture Requirements Analysis Requirements Organization & Classification Specification building Acceptance Test management Requirements Management 2. Both classical functional and Object Oriented approaches are supported for requirements analysis and specification building. 3. With IRQA, you can implement your RE management process. 4. The following modelling capabilities for each Requirements Engineering activity are supported: Requirements Organization & Classification: Block diagrams Domain diagrams Multidimensional classification Classical "hard" hierarchy Requirements Analysis Concept models Classification models System Specification building Use Case diagrams (UML) State Charts (UML) Sequence Diagrams (UML) Scenarios (semi-graphical notation) Software Analysis O.O. Models (UML) E/R Models Software Specification building State Charts (UML)

Page 279 of 450
Kovair Global Lifecycle v5.5


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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document.

Full Using Kovair's Word Import Addin a table of content (TOC) may be analyzed and identified for Requirements hierarchy. Once an external document is imported using Kovair's Word Import Addin, the version comparison feature of Kovair can be used for identifying changes in two versions. Otherwise Microsoft Word's document comparison feature can be used to compare two documents. Kovair's Word Import Addin provides automatic identification of requirements not only by keywords but also with Styles and Delimiters to parse and extract requirements from the text. Requirements can also be inserted from MS Excel or csv files. Requirements can also be automatically extracted from a mail using services like Webmail and Gmail. Kovair's Word Import Addin allows users to semiautomatically identify different sections of an input document and convert them into Requirements. Moreover using simple copy and paste portions of input document may be converted into Requirements preserving the original formatting. Apart from automatic identification, Kovair's Word Import Addin also provides manual identification of requirements from a Word document. The specific texts are selected by the user, and tagged as requirement titles or description using a menu option available in the Add In. Upon parsing, requirements are automatically inserted into Kovair Global Lifecycle.
Full
Full
Full
Full
Page 280 of 450

Full Kovair Global Lifecycle provides customizable CSV Import. It allows inserting new entity items as well as updating existing items from an Excel or CSV file. Additionally Kovair Word Import Addin allows to import a set of rich text formatted requirements from a Word Document by means of wizard. The third way of entering multiple Requirements in one shot, is by using Kovair's grid like interface called Multi-add. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification Full Due to Database centric architecture of Kovair, the individual Requirements may be independently modified with optional versioning. All of these changes preserve the existing Traceability and other relations. Kovair Global Lifecycle allows to create various kinds of custom fields based on different data types, e.g. Lookups, Single line text, date, etc, which can be used to classify and categorize requirements during identification. Kovair also has some unique advanced data-types e.g. Electronic Signature, Calculated Field, Grid Field, Summary Field which allows users to extend the capability of Requirements Management with ease. 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 Kovair meets the requirement by embedding design Partial system implementation (such as architecture, functional decomposition, WBS, drawings or integrating with other design tools. Kovair's rich etc.) and display them graphically such that requirements can be linked to them. text editor allows any such graphical drawing to be embedded in the Requirements Description. These graphical elements can also be attached to a Requirement as files. The most interesting way Kovair deals with the graphical elements generated by other tools is by integrating with the tool using Kovair's Omnibus technology.

Full
Page 281 of 450

Full Users can create Entities in Kovair to represent different system elements. Using Kovair's traceability and other userdefined relations the items of these Entities may be related to each other as well with other Requirements.

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 Kovair Global Lifecycle allows to keep Requirements in the Full derive/create additional requirements and link between them such as same family together by creating Sub-Requirements, subrequirement to requirement, or requirement to text (representing trade studies) sub-Requirements to any depth. The users can Create, to derived requirements. Move, and Delete Requirements across the hierarchy. Additionally, Kovair Global Lifecycle allows users to organize requirements in a folder like structure. Folder structure is highly customizable. Folders can be nested. Some examples below. Business Requirements High Priority Welcome Screen Low Priority Advanced Search Screen User Requirements High Priority Create a Module Edit Module Low Priority View Module 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 Kovair's flexible user defined relationship feature enables users to create different kind of relations between Entities, even between items of the same Entities. A many-to-many relation between Performance Requirements and System Elements also include custom variables to allocate only part of one item to the other. E.g. 30% of a Performance Requirement may be allocated to a System Element and vice versa.
Page 282 of 450

Full Users are allowed to use Grid interface to create 1 Way / 2 Way (Bidirectional) relations between requirements. Any impact due to traceability can send notifications to the appropriate people. User can create Custom Reports to show the Traceability Relations for each such Requirement. An Exception Report can be generated for those Requirements that are missing traceability relations. Traceable relations can be automatically created by using the Policy Engine. The different entity items of Kovair Global Lifecycle can all be linked/related to one another by means of uni-directional or bi-directional impacting or non-impacting traceability relationships.

3.4. Capture of allocation rationale, accountability, test/validation, criticality, Full 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. 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 By setting up Traceability relationships in Kovair Global Full allow the user to identify inconsistencies such as unlinked requirements or Lifecycle among the different or same entity items, and system elements (orphans). using the Traceability Matrix, Kovair Global Lifecycle provides a graphical representation to identify unlinked requirements or orphans. Moreover different reports can be generated to show items filtered by different criteria including orphan Requirements. The identified inconsistencies may be as complex as - 'System Requirements of Module X which can be traced back to Functional Requirements and have at least one Test case failed in the last Test cycle'.
Page 283 of 450

Full Kovair Global Lifecycle allows you to create One-to-Many, Many-to-Many, One-to-One, One-way/ Two-way Traceability Relationships between the same entity as well as between different entities. In this way, we can link Requirements -> Use Case -> Design Elements -> Test Cases -> Issues. Thus using this linked path, we can on one hand trace an Issue to the source requirement and on the other hand trace a Requirement and drill down to the evolved Issues, thereby ensuring a complete visibility from the source to its implementation. Kovair has two different interfaces to achieve that - by a hierarchical textual reporting and a graphical network diagram. Kovair Global Lifecycle allows you to define a Process that automatically create multiple Tasks for different users for a particular Requirement at runtime. You can have multiple parallel tasks for any number of users. A built-in Task management system helps managing multiple tasks both independent and related to other Entities. As and when the users completes their own Task, the status of the requirement keeps changing. And finally when the last activity of the process is completed, it implies that the requirement is successfully implemented. A Process View can be created that shows the current Processing status of each requirement. At every stage of this automated process artifacts either managed within Kovair as separate Entities or managed by other 3rd party Tools integrated by Kovair's Omnibus technology, can be related to the Requirements using Traceability and other relationships (e.g. containment, parent-child, successor-predecessor...). This produces a complete network of related artifacts created during the lifecycle of the Requirements.

Full
Page 284 of 450

Full Using Kovair's powerful custom fields and various performance tracking attributes, the planned vs. actual values may be tracked and compared. Moreover, these values may be rolled up at an appropriate level.

4.4. Requirement performance verification from system elements (roll up of actual): Once performance requirements have been allocated to system elements, the requirements management tool should support the verification of those requirements by rolling up actual and reporting on variances (this is the allocated weight versus the actual weight). 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. 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
Kovair Global Lifecycle keeps a record of all the changes made to each Requirement with Who, What and When information for a complete Audit Trail.
Full
Kovair clearly distinguishes between Updates and a true Version Change to a Requirement. Versioning Requirements/ Issues triggers audit trails and traceability impacts. Each version also stores its contextual threaded Comments with all attachments. Comparison between versions show the differences between the description of two versions. The Baseline functionality in Kovair Global Lifecycle captures full snapshots and allow comparison of all the entity items of the project. Once baselined the entity items included in that baseline cannot be rolled back to any previous version if needed. Kovair Global Lifecycle provides extensive access control by using Access Groups. By defining an Access Group, you not only control who can do what, but also who can view what. For example, if there is a group of users (lets call it Client), you can restrict them to viewing only certain Requirements. The Client will be able to view only Requirements created by their group members and not any others.
Full
6. Documents and other output media
Page 285 of 450

Full Kovair Word Reports can create templates in Microsoft Word, and use these templates to create any kind of reports or documents. Completely formatted Word Documents can be generated based on user-defined templates such as MRDs, SRS, and RFPs. In a single document, different sections can be created using different Custom Filters and different sets of information. Kovair Word Report is a perfect tool for those situations where dynamically changing information needs to be reported. In addition Reports may be generated in HTML, Crystal and Excel formats. Kovair's rich text editor includes both spell checker and thesaurus for quality control of Requirements. Full Kovair Global Lifecycle's integration with Crystal Reports application allows users to generate all kinds of textual and graphical reports with drilldown capabilities that can be viewed and printed from the browser. Also it allow you to create custom Crystal Reports from the Crystal Reports application itself and later upload it from the Kovair Global Lifecycle application for viewing. Kovair's dashboard function allows many such reports - both graphical and textual to show on a dashboard page. Kovair Word Reports can create templates in Microsoft Word, and use these templates to create any kind of reports or documents. Completely formatted Word Documents can be generated based on user-defined templates such as MRDs, SRS, and RFPs. In a single document, different sections can be created using different Custom Filters and different sets of information. Kovair Word Report is a perfect tool for those situations where dynamically changing information needs to be reported. Kovair's Crystal, Word and Excel reports allow a WYSIWYG preview capability.

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
Full
Page 286 of 450

Full Kovair reports can mix the Requirement descriptions and any combinations of various attributes including Status fields. The same set of HTML, Crystal, Word, Excel reports may be configured to show status information in conjunction with Requirement descriptions. Kovair allows users to create number of user defined fields to track any number of performance metrics. In addition Kovair's calculated and summary fields can calculate complex metrics based on user defined criteria. Kovair allows users to create number of user defined fields to track any number of Compliance status. In addition Kovair's calculated and summary fields can calculate complex metrics based on user defined criteria. Full Kovair Global Lifecycle allows you to create Custom Filters with complex conditions including Boolean AND, OR, NOT and condition grouping. Filters can use any System and Custom Fields. One Kovair Global Lifecycle innovation is the Filters with runtime parameters which allow users to specify the parametric value at runtime. Additionally you can perform searches based on IDs and free text keywords.

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.
Page 287 of 450

Full Kovair Global Lifecycle allows multiple users to access and work on different Requirements simultaneously. With 100% browser based interface the users can access it from anywhere anytime. Moreover, edit locks eliminates possibilities of parallel edit of the same item. However multiple users can edit multiple items in parallel independently. Unlike most other Requirements Management tool, Kovair Global Lifecycle built-in process automation engine allows you to define an Automated Process where you can define activities like Review, Markup, Comment or any other customized activities for a Role or a single user. On execution, the Process automatically generates tasks for the respective users for each Requirement. Users can have many discussion threads within the context of each Requirement. Attachments can be made at a Comment level. Discussions are in the context of a particular 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 Kovair Global Lifecycle provides extensive access control by using Access Groups. By defining an Access Group, you not only control who can do what, but also who can view what. For example, if there is a group of users (lets call it Client), you can restrict them to viewing only certain Requirements. The Client will be able to view only Requirements created by their group members and not any others.

8. Interfaces to Other Tools
Page 288 of 450

Full Kovair Global Lifecycle Management offers an open, vendor neutral and seamless integration platform called OMNIBUS. ALM tools like DOORS for Requirements Management, ClearCase for Configuration Management, Quality Center for Test Management, Rational Rose for Modeling, Visual Studio IDE etc. or any custom homegrown ALM product can be easily plugged in through Kovair Adapters to OMNIBUS. Organizations can choose best-of-breed ALM tools from multiple vendors to support different application lifecycle phases yet remain integrated through OMNIBUS to ensure cross-lifecycle transparency, macro and micro level process automation and correspondence of activities across disciplines. IBM Rational Requisite Pro, HP Quality Center, Perforce, Microsoft Project 2003, Visual Studio 2005, IBM Rational Test Manager, IBM Rational Rose, Microsoft Word, Crystal Reports, Clear Case, Sub Version and Mail Integrations with Webmail and Gmail. Kovair has open and published Web service based API which any developer can use to access wide range of internal functionality of Kovair. Kovair also has API for Omnibus Integration Technology for creating easy integrations with other ALM tools. Yes. Kovair Global Lifecycle supports the standard query language like SQL and exchange formats like Xquery (XML based query). Kovair can import standard as well proprietary CSV file formats. The CSV file can create hierarchical as well as Traceability relationship without the need of manual reentry. The same thing is possible while importing from Excel spreadsheet as well. Kovair Global Lifecycle supports XML. A set of requirements and other entities may be exported from one instance of Kovair and imported in another instance. Import/ export this way preserves all relationship and internal structure within Kovair.

8.1. Inter-tool communications: Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.).
Full
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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications
Full
Full
Full Full
Page 289 of 450

Full Similar to having adapters for external tools, Kovair has a self adapter that can be used to plug in a separate instance of Kovair installation into Omnibus, thereby information can be exchanged between the two instances of Kovair installed at different sites and projects. Using Kovair's Baseline capability, two Baselines may be compared for existence and differences of Requirements included in the Baselines. Full Kovair Global Lifecycle supports multiple concurrent users. Kovair Global Lifecycle has been engineered to be highly scalable and can support thousands of users with no perceptible degradation in performance. Operating System: Server: Microsoft Windows 2000/ 2003 Server Client: Microsoft Windows XP, Vista, Win 2000, Win 2003 Database: Microsoft SQL Server 2005 Kovair Global Lifecycle only supports Microsoft SQL Server 2005 database with Service Pack 2

Full
Full
Page 290 of 450

Full For a small installation single server installation is possible. Otherwise a two server installation is recommended - one for Database & Document Server and the other as Web Server. Database and Document server or Single Server Installation: 2 x Dual Core Xeon 9000 or Quad Core Xeon Processor 7300 with max CPU cache (Microsoft SQL Server can be configured to utilize all CPU and cores) 14,000 rpm SCSII Hard Drive Min 100 Mbps LAN connectivity 2 x Ethernet Cards one for direct connection with the Web Server the other with the LAN for backup and administrative access. Web server: 2 x Dual Core Xeon Processor 7200 with max CPU cache (IIS can utilize all CPU and cores for multi web session threads) 14,000 rpm SCSII Hard Drive Min 100 Mbps LAN connectivity Min T1 Bandwidth for Internet connections, T3 is preferable. 2 x Ethernet Cards one for direct connection with the Database Server the other with the LAN for backup and administrative access. 9.4.1. Memory requirements Full Database and Document server or Single Server Installation: 4 GB RAM Web server: 4 GB RAM

Page 291 of 450

Full Database and Document server: 2 x Dual Core Xeon 9000 or Quad Core Xeon Processor 7300 with max CPU cache (Microsoft SQL Server can be configured to utilize all CPU and cores) 14,000 rpm SCSII Hard Drive Min 100 Mbps LAN connectivity 2 x Ethernet Cards one for direct connection with the Web Server the other with the LAN for backup and administrative access. Web server: 2 x Dual Core Xeon Processor 7200 with max CPU cache (IIS can utilize all CPU and cores for multi web session threads) 14,000 rpm SCSII Hard Drive Min 100 Mbps LAN connectivity Min T1 Bandwidth for Internet connections, T3 is preferable. 2 x Ethernet Cards one for direct connection with the Database Server the other with the LAN for backup and administrative access. 9.4.3. Disk space requirements 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? 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? 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)? Full Full Full 80 GB Free Hard Disk Space Yes. Kovair Global Lifecycle lets you to open and work on multiple windows concurrently Yes. In Kovair Global Lifecycle, changing one View, gets automatically reflected in all other views. Kovair has many graphical drag-and-drop tools. In fact for configuring Kovair no coding is necessary, as everything is achievable by drag and drop only Microsoft

Full
Page 292 of 450

Full Kovair Global Lifecycle's in built Process and Policy engine can be configured so that it automatically generates various Tasks for the respective users during execution. For this the user does not need to create and playback commands or macros. The system is designed and architected from the ground-up to be an enterprise class, 100% browser based system. This allows users to access Kovair Global Lifecycle from remote locations and enables collaboration across geographically distributed teams. Maintenance and Upgrades to the software are seamless to the end-user and are of light over-head to the IT departments Edit function is available with Undo. Kovair Global Lifecycle's flexible process configurability allows users to configure it to meet multiple military and commercial standards including various methodologies CMMI, Agile, Waterfall, CFR 21 Part 11, ITIL, COBIT. It is also to a large extent complies with section 508 accessibility standard. Yes, as per software license agreement. Kovair Global Lifecycle can be purchased with either named (single user) or floating (concurrent user) licenses. Minor releases occur every 3 months and major releases every 6 months. All updates are absolutely free to customers with an active AMC (Annual Maintenance Contract) with Kovair. Kovair Global Lifecycle includes complete online help. http://www.kovair.com

Full
Full N/A
12. Support and Maintenance 12.1. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
Full Full
Full
12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info
Full Full
Page 293 of 450

Full Standard Support: 9:00 AM 6:00 PM Pacific Time, with two-hour callback time during business hours Premium Support: 9:00 AM 6:00 PM Pacific Time, with one-hour callback time during business hours and pager-based support during off hours with a two-hour callback time. Kovair has company organized Users Group Meeting Yes Yes, Kovair provides training at customer's location around the world. 1 week Kovair takes the responsibility of software installation at the customer's site, free of cost. Additionally Kovair provides a detailed step by step Installation guide that can be referred during the Installation process. No basic training is provided as such but can be arranged if requested by the customer.

12.6. Phone support: What type of phone support is available from the tool supplier?
12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Page 294 of 450

N/A 1. Process Automation to implement and automate Requirements and other processes. 2. Collaborative Ranking 3. What-if Analysis for Release Planning 4. Multi-threaded Discussions in the context of each Requirement. 5. Traceability and other Relations with Requirements and other ALM Entities like Test cases, Issues, Change Items... 6. Electronic Signature for Critical Approval Process. 7. Planned and Actual Time and Effort Tracking for each individual and group of Requirements. 8. Reporting showing Traceability and other relations. 9. Multiple Rich-Text Fields. 10. Complete Audit Trail 11. Requirements Network Diagram To know more about Kovair Requirements Management and other built-in application of Kovair Global Lifecycle Go to: http://www.kovair.com/resources.asp

Page 295 of 450
MagicDraw & SysML Plugin v16.5
Date of Submission:
24-Jun-10

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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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.

Full * Require Cameo DataHub we can import CSV file or other requirement management tools data into MagicDraw. This is a planned capability. This is a planned capability. Customers can use scripting.
None None
None
This is a planned capability.
Full Full * Require Cameo DataHub we can import CSV file or other requirement management tools data into MagicDraw.
1.5.1. Batch-mode document/source-link update: Does the tool have the ability This is a planned capability. None to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to We support SysML Standard Full classify/categorize requirements during identification 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 SysML Requirement diagramming Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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 SysML Requirement diagram table view


Full
Full
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 4. Traceability aN/Alysis: 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 * Require Cameo Datahub we can have traceability change Full allow the user to identify inconsistencies such as unlinked requirements or monitoring capability. system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the ** Require Teamwork Server we can have team collaborate Full life of the project, the requirement management tool will be used to verify that capability with version control. 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. 4.4. Requirement performance verification from system elements (roll up of MagicDraw Validation Suite can help us to evaluate the Full actuals): Once performance requirements have been allocated to system value between requirement and the implementation elements, the requirements management tool should support the verification of element. those requirements by rolling up actuals and reporting on variances (this is the allocated weight versus the actual weight). Page 297 of 450

5. Configuration MaN/Agement 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.

Full ** Require Teamwork Server.
None
This is a planned capability of Cameo Team Server to support baseline management and version control
Full
** With Teamwork Server we can have access control by user. (We does not support group in Teamwork Server. Cameo Team Server is suppose to provide such capability)
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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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
*** Our report engine support all kind of standard. (Professional Service is needed)
Full
Full
MagicDraw report engine can generate Open Office and MS Office (Open XML only) files The table of contents need manual operation in MagicReport generated document.
Full
None None Full Require Cameo Team Server to provide us the collaboration features and workflow in order to support it. Require Cameo Team Server to provide us the full collaboration features to integrate with other issues tracking tools in order to support it. It is now a manual process to monitor and updeate status.
Page 298 of 450


None Require Cameo Team Server to provide us the full collaboration features and integrate with our eCompliance in order to support it. MagicDraw does not support any query language.
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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. 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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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 ** Require Teamwork Server
Full
** Require Teamwork Server (We will need Cameo Team Server to provide a full user management access control to support this feature)
Full
* Require DataHub
Full
Full
* Require DataHub (by default we support Borland CaliberRM, IBM Doors & RequisitePro, CSV, and Cameo Requriements) MagicDraw provide full Open API but not our Teamwork Server and DataHub.
None
Full
MagicDraw support XMI import and export. * With DataHub we support IBM Doors & RequisitePro, CSV, and Cameo Requriements)
Page 299 of 450


Full MagicDraw support XMI import & export. With our script engine we also support AP233 (http://homepages.nildram.co.uk/~esukpc20/exff2005_05/a p233/ap233/highapi.html) ** Requrie Teamwork Server
Full Full
8.2.2. Consistency/comparison checking between same-tool datasets: Does Full 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 Full multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and Full operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or Full commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration Full requirements: 9.4.1. Memory requirements Full 9.4.2. CPU requirements Full 9.4.3. Disk space requirements Full 10. User Interfaces 10.1. Doing one thing while you are looking at another: Does the user have the Partial ability run a report and look at a requirement at the same time? 10.2. Simultaneous update of open views: If the tool allows for multiple Full windows/views into the tool--does a change in one view automatically reflect in all other views? 10.3. Interactive graphical input/control of data: Does the tool support graphical Full input and manipulation of data? 10.4. Which window's standard do you follow?: If your tool supports a window's Full standard, which one(s)? 10.5. Executable via scripts (recordable) or macros: Does the tool allow the Full user to create and playback commands or macros that allow the user to automate various tedious tasks? Page 300 of 450
** Require Teamwork Server
Commercial and file based.Currently SQL-based but moving to OODB with SQL capabilities.
2 GB Core due 500 MB Reports are updated live in tool. Printing reports is fairly fast with minimal work interruption. Tool built on model view controller architecture. All views update when data is modified.User may delay some highercost matrix updates as required.
Swing We support JSR-233

10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. AdditioN/Al Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?

Partial Full Full MagicDraw support UPDM/Dodaf/Modaf, XMI, and AP233 Support for minor updates via web/sync and a read-only html version.
We provide software assurance to allow the user get full support and upgrade. We provide both mobile and floating license We provide software assurance to allow user get upgrade
1 to 2 weeks
UML/SysML/UPDM modeling, traceability between requirements and model elements, impact analysis with dependency matrix, Scripting support for calculation, forecasting and simulation, Model validation.
Page 301 of 450
MKS Integrity 2009



Full Input documents can either be referenced in external systems, related to requirements/requirements documents via file attachments or imported directly into the system as documents and content which can then link directly to the requirements derrived from them and other downstream assets and activities. If imported into the system, parsers can be created to respond to structure, keyword, style or other document property such that the voice of the customer is properly captured and classified in the repository. The MKS solution offers the ability to compare two arbitrary documents (or requirements) or two versions of a single document (or requirement). Bidirectional integrations, such as those that are available for MS-Excel, HP/Mercury Quality Center or Telelogic DOORS, can directly compare and update existing information within the MKS repository. The MKS gateway technology allows the mapping of data between systems and the definition of parsers to respond to structure, keyword, style or other property in the creation of requirements objects from text. Additionally the MKS solution includes a full command line interface for custom inport scripting and a full API for creating single direction or bidirectional integrations into home grown or custom applications.
Full
Full
Page 302 of 450
MKS Integrity 2009

Full The import of requirements is generally an automatic process unless the parser cannot determine how the content should be mapped to the various fields defined. That said, some integrations offered use a tagging methodology where-by the user can interactively define, or modify, how the parser will map content to data and meta-data fields of a requirement or other document content. Requirements can be defined directly within the MKS solution using the document interface, list interface, hierarchical interface or the item details interface -whichever is most comfortable for the end user to interact with. All interfaces conform to the same security and other constraints defined by the system, project or requirement type. The MKS solution fully supports batch loading of requirements information either through dedicated integrations, the command line interface or the API as discussed in response 1.2 above. Yes, through suspect linking or automated trace management capabilities the MKS solution can update or notify linked items with or of change. That being said, best practices suggest that once in the system, the requirements and requirements documents should be managed and updated from within the system. The MKS solution provides many interfaces, including a document-style editor, to facilitate this method of work and minimize or remove the need to manipulate the requirements from outside the system. Yes, the MKS solution provides both default and user defined mechanisms for classifying and categorizing individual requirements, groups of requirements and requirements documents.

Full
Full
Full
Full
Page 303 of 450
MKS Integrity 2009

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 Full When structure and relationships are the primary system implementation (such as architecture, functional decomposition, WBS, area of interest, rather than the complete content of etc.) and display them graphically such that requirements can be linked to them. the item, the hierarchical tree view enables users to graphically view, navigate and create links between requirements and from requirements to any other object in the system (i.e. functional designs, tasks, test cases, etc.). 2.2. Textural capture of systems structure: Can the tool textually capture Full For some users dealing with requirements in a flat list system implementation (such as architecture, functional decomposition, WBS, is a more productive method of working. Using the etc.) and display them textually such that requirements can be linked to them. list view is an easy way to spot unwanted duplication in your requirements set or to perform batch operations. For example, you can easily assign work to users, do quick edits and create traces on multiple items in this view. All relationships, links, data and meta-data have textual representations and thus using the list view, command line or API the user has all the power they would have with the web or native client interfaces. 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 Full The MKS solution allows you to directly create related derive/create additional requirements and link between them such as items within the tool, whether those are derrived requirement to requirement, or requirement to text (representing trade studies) requirements, peer requirements or otherwise, and to derived requirements. automatically create traces to those items and define any attributes and/or content of those items.
Page 304 of 450
MKS Integrity 2009

Full The MKS solution allows you to define any number of attributes for requirements or other objects captured within the system as well as rollup or perform calculations based on that data for use in the item itself or in reports, charts and dashboards. Further, the workflow for the individual requirements can interact with or be constrained by these attributes as the business dictates. MKS Integrity permits users to seamlessly trace and navigate interactively between documents and through various levels of requirements to design features and specifications, assigned tasks, testing and deployment activities and view activity in context with associated source code changes -- all within in a single system and user interface. These relationships can be defined explicitly or via drag and drop type gestures within the product if they are not created automatically by other higher level operations.

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
Data such as that described by this section can be captured on the requirement itself or linked to the requirement through the unified change management functionality within the tool. Whether it is trace relationships to change requests or approvals, discussion fields, categorization and attribute fields or workflow stages this information is available in any of the views presented to the user (hierarchical relationships, document view, details view or list view). 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. 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
Page 305 of 450
MKS Integrity 2009

Full The MKS solution provides many queries and reports to help in analyzing a set of requirements and their related data in addition to field capabilities which can compute and display indicators reporting the status of the requirement, the state in the requirements workflow or other criteria. The relationship view is designed with the primary task of navigating trace and other relationships. This view allows the user to traverse the various links coming in to and going out of a given requirement to all other areas of the application lifecycle. The MKS solution captures, via workflow, fields and related assets and activities, all verification type information as well as enables the user to navigate to all instances of the requirements use across projects (where user permissions allow) and view their implementation and test details as well as task assignments and other meta-data stored with the requirement and its related assets and activities. Further, the MKS solution records, for audit purposes, all change to the requirement or requirement set/document as it evolves over time. Powerful querying, charting, reporting and dashboards provide management visibility into requirements progress and project status and enables users to mine data directly from the system to monitor such key performance metrics as requirements churn and rework. Performance goals and results can both be recorded on the individual requirements and related test objects and rolled up to any level within the hierarchy as desired.

Full
Full
Full
5. Configuration Management Page 306 of 450
MKS Integrity 2009

Full The MKS solution captures all change to an item, be it a requirement, requirements document or any other artifact in the repository, within history and associates it with the user that made the change and the time the change was made. At any point in time you can view an item as it existed at a given point in time and you can compare items across time. In addition to this individual fields can be made mandatory during certain stages of the items workflow or under certain conditions of other fields on the item, electronic signature can be used to securely approve change and editability can be controlled or prevented by related change requests which authorize changes. Version is defined as a meaningful point in an individual item's history, where that item could be a requirement, requirements document or any other artifact in the repository. Baseline is a term used to denote a meaningful point in a set of items, a requirements document for example, history. The MKS solution supports history, versions and baselines within the product for all item, asset, and activity types, and users can compare items over at any of these granularities. The visibility and editability of an item, whether it is a requirement, requirements document or any other object in the repository, can be controlled at the system, type, project, item or item attribute level (i.e. any level of granularity desired by the customer) as well as at the user and group level. The MKS solution allows for specific reports and report templates to be created that adhere to market, military, commercial or industry standards.

Full
Full
Full
Page 307 of 450
MKS Integrity 2009

Full Spellcheck is a feature of the MKS solution, and it includes the ability to add customer-specific terminology. Consistency checking triggers can be written to verify certain data fields conform to corporate standards. All manner of charts, reports and dashboards can be created directly within the tool for the presentation of date in the system. The example configuration ships with many such examples of requirements related metrics, statistics, calculations, reports and charts for incorporation into any specific configuration. Graphics, indexes, headers and other finished document elements can be created using the reports and report template functionality within the MKS solution. All reports and charts can be displayed in the native or web interface prior to being printed. In addition to the reports, charts and dashboards which can communicate status information from the items in the repository with the MKS solution, you can also create computed fields and metrics on the items themselves, whether they are requirements, requirements documents or other repository assets and activities, and bubble those numbers and results, such as standard status metrics, up to any level in the hierarchy as appropriate.

Full
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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
Full
Full Full
Page 308 of 450
MKS Integrity 2009

Full In addition to the reports, charts and dashboards which can communicate status information from the items in the repository with the MKS solution, you can also create computed fields and metrics on the items themselves, whether they are requirements, requirements documents or other repository assets and activities, and bubble those numbers and results, such as adherence to performance goals, up to any level in the hierarchy as appropriate.

In addition to the reports, charts and dashboards which can communicate status information from the items in the repository with the MKS solution, you can also create computed fields and metrics on the items themselves, whether they are requirements, requirements documents or other repository assets and activities, and bubble those numbers and results, such as testing status, process metrics and project compliance, up to any level in the hierarchy as appropriate. 6.6.3. Other ad hoc query's and searches: The requirements management tool Full The MKS solution allows users to search on any should support ad hoc query's and searches per the user's discretion. attribute or combination of attributes as well as create, save and share queries, reports, charts and dashboards as needed. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements Full
Page 309 of 450
MKS Integrity 2009

Full The MKS solution is an enterprise class solution which supports globally diverse teams which span the application lifecycle and business as a whole. Through process and workflow, comment and discussion fields, approvals and e-Signatures or related discussion items the MKS solution fully supports this method of working. The list view is ideal for review board type meetings where annotations and approvals can be made inline and items progressed in their workflows appropriately. Conflict detection, user and group access and permissions, document sharing, federated server architecture and notifications are some of the many features within the solution which support multi-user environments. 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 The visibility and editability of an item, whether it is a requirement, requirements document or any other object in the repository, can be controlled at the system, type, project, item or item attribute level (i.e. any level of granularity desired by the customer) as well as at the user and group level. Further, MKS Integrity integrates with existing system security realms for system level access control. Flexible and powerful workflow with approval cycles ensures only authorized personnel can alter or add requirements. The MKS solution offers a full command line interface in addition to a complete Java and C API for integrating with standard and custom applications. In addition MKS supports a server side trigger framework where custom extensions can be written in JavaScript and integrated into the system.

Full
Page 310 of 450
MKS Integrity 2009

Full MKS supports a wide array of integrations into third party products from domains that span the application lifecycle. Microsoft tools, like Word, Excel and Project as well as testing tools like Quality Center, configuration management tools like ClearCase, Perforce and Subversion in addition to the native Source functionality, design tools like Rational Software Modeller and System Architect, IDEs like Visual Studio .Net and Eclipse and even legacy requirements offerings like IBM/Telelogic DOORs. In addition to this MKS offers a full Java and C API to create custom integrations into home grown or other commercial applications. MKS provides a fully documented open API for both Java and C. MKS supports Oracle, Microsoft SQL Server and DB2 databases for its artifact repository. Through scripting via the command line, existing integrations or by creating a custom integration using the Java or C API the MKS solution can import data from a number of existing tools and in a number of standard formats. MKS supports XML data exchange and supports the RIF (Requirements Interchange Format) standard.

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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..)
Full
Full
Full
Full
Page 311 of 450
MKS Integrity 2009

Full Communication between MKS servers can be done via the command line, Java or C API to facilitate communications between various installations. Further, the MKS performance and scalability testing suggests that this is rarely necessary and a single Integrity installation can accomodate thousands of concurrent users and millions of repository assets and activities. There are no need for data replication, consistency or comparison checking tools, primarily because the Federated Server Architecture essentially guarantees that distributed datasets will be consistent. Stated another way, there is been no need for disparate systems within our enterprise customer base. MKS provides both named user and concurrent user licensing. Both allow for multiple concurrent users, and the licensing model is scalable to thousands of concurrent users. Windows Server 2008 R2 Enterprise/Standard 64-bit, Windows Server 2008 Enterprise/Standard 64-bit, Windows Server 2003 R2 Enterprise/Standard 64-bit, Sun Solaris 9/10/10-Containers, IBM AIX 5L 5.3/6.1, SUSE Linux Enterprise Server 10 for x86_64, HP HPUX 11i v3 (English), RedHat Enterprise Linux 5 (base server) for x86_64/x86, VMWare ESX 3.5 -- for a complete up to date list of supported systems, please visit www.mks.com.

Full
Full
Full
Page 312 of 450
MKS Integrity 2009

Full MKS does not use a proprietary database but rather a number of commercially available relational databases such as: Oracle 11g 64-bit/32-bit, MS SQL Server 2008 64-bit/32-bit, MS SQL Server 2005 32bit, MS SQL Server 2005 32-bit, IBM DB2 9.5/9.1 64bit for AIX/Windows/Linux/Solaris, IBM DB2 9.1 32bit for Windows, IBM DB2 for i5/OS V6R1/V5R4 -- for a complete up to date list of supported database systems, please see www.mks.com. Dependent on number of users and usage profile -please see the Recommended System Requirements documentation on www.mks.com or contact MKS directly. Dependent on number of users and usage profile -please see the Recommended System Requirements documentation on www.mks.com or contact MKS directly. Dependent on number of users and usage profile -please see the Recommended System Requirements documentation on www.mks.com or contact MKS directly. Dependent on number of users and usage profile -please see the Recommended System Requirements documentation on www.mks.com or contact MKS directly. Yes, the MKS solution supports a multiple task usage pattern. Yes, the MKS solution supports a dynamic update usage pattern such as is described. Yes, the MKS solution offers both a native GUI and Web UI for graphical data input and manipulation.

Full
9.4.1. Memory requirements
Full
Full
Full
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? 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? 10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data?
Full Full
Full
Page 313 of 450
MKS Integrity 2009

Full The MKS solution is a Java application and will take on the look and feel, either Windows or Motif, of the underlying operating system. Yes, the MKS solution offers a complete command line interface for use in scripting and automation processes. Custom Actions allow users and administrators to execute pre-defined actions with a single gesture. Further, on Windows systems the MKS solution ships with the MKS Toolkit product which is a powerful set of UNIX and Windows scripting tools for the Windows platform. Yes, the MKS solution supports a Web UI. Yes, the MKS solution supports multi-level undo capabilities when modifying rich text fields prior to committing to the database. MKS has features which support CFR21 Part 11 regulations, can produce reports and documents adhering to a number of commercial, industry and military standards and has customers using the solution as part of HIPAA, CMMI, ISO, and other standards and governance iniatives. MKS Integrity also meets standards such as FIPS. MKS offers a standard 30 day warranty. MKS supports network licensing, and uses the FlexNET licensing system.

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
10.6 Web browser interface? 10.7 Edit Undo Function Support
Full Full
N/A
Full Full
Page 314 of 450
MKS Integrity 2009

Full MKS Customer Care provides easy access to technical support by 800 toll-free phone number, email/web request service, or fax. By going to our Customer Community you can have access to automatic product notifications, product upgrades and patches, and our enhanced online support services portfolio. MKS is on a roughly annual release cycle with patches being released as needed by a given release of the software. Both patches and full releases are free for customers on existing maintenance contracts. MKS documentation is provided in HTML and PDF format with every purchase. Electronic help is both in manual format as well as F1 context help. www.mks.com Customer care subscribers receive unlimited access to the MKS customer support team by phone, email or fax plus preferred access to the MKS Customer Community and Knowledge Base. Support hours vary by location and customer care program purchased -please see www.mks.com/support for more information. Users forum, discussion threads, knowledge base as well as other self, peer and MKS support is available through the MKS Customer Community.

Full
Full Full
Full
13. Training
Page 315 of 450
MKS Integrity 2009

Full MKS's education team offers a diverse set of best practices education delivered in concert with partners, and directly through training courses for end users and administrators. Public classes take place at our offices in Waterloo, ON, and Oakbrook Terrace, IL, and onsite at our customers' locations. Our training courses are designed to quickly optimize your understanding of ALM and ITIL and to deliver quick payback on your investment in MKS Integrity. MKS offers end-user and administrator training programs for customers in all areas of the product.

13.1 Tool specific training classes
Full Full
Full
Yes, MKS offers training courses on customer site. It is recommended that users new to the system take a one day users course to ensure they are as productive as possible when using the tool. Yes, MKS can offer a basic installation and training offering.
Page 316 of 450
MKS Integrity 2009

N/A Software development teams have software configuration management tools to support parallel development, baselining of software configurations and reuse of software components. Today's sophisticated requirements management users have a similar, but unmet need to associate and reuse requirements in a parallel development scenario while maintaining traceability throughout the lifecycle. No traditional, first generation requirements management vendor today can offer capabilities that scale to meet the demands of today's user, and none of these generation one vendors have the core product architecture to do so in the near term. MKS Integrity's requirements reuse and persistence offers a unique capability allowing for groups of requirements to be associated and re-used in a parallel development scenario. Process enforcement capabilities tied back to requirements protect the project schedule by restricting development of features and preparation of test plans until requirements have reached an appropriate state. MKS also provides rich integrations into many modeling tools that enable complete traceability from Requirements to models and individual model elements. Having this level of traceability provides the capability to perform gap analysis and impact analysis between changing requirements and models. Read the whitepaper entitled "An Innovative Approach to Managing Software Requirements" available at www.mks.com to learn more about the

Page 317 of 450
PACE v3


Full PACE can use document information, including headings and to help analyze and identify requirements. PACE also has a built-in glossary which is accessible over the web. PACE allows users to compare and contrast different versions of documents. PACE supports fully automated parsing of requirements from documents and other files. PACE supports interactive requirements identification from documents
Full Full
Full
Full Full
PACE allows users to manually identify requirements PACE provides multiple, automated batch-mode mechanisms for inputting and identifying requirements from outside the tool. PACE enables existing requirements to be updated from new/changed versions of source documents without having to re-establish traceability links.
Full
1.6. Requirement classification: Does the tool have the ability to PACE can classify requirements during identification. Full classify/categorize requirements during identification 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 PACE can graphically capture system implementation Full system implementation (such as architecture, functional decomposition, WBS, and display them graphically. etc.) and display them graphically such that requirements can be linked to 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 PACE can textually capture system implementation and display them graphically.
Page 318 of 450
PACE v3
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 PACE supports requirements derivation. Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, PACE supports easy custom element allocation. Full 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 All links in PACE are bi-directional Full 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, PACE supports easy capture of allocation rationale, Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the etc. PACE allows objects to be extended with ability to attach rationale, assignments, criticality, test/validation and many other assignments, criticality, etc. PACE also allows issues to the requirement, allocation, and the system element to which a requirements to be linked to other objects such as requirement is linked. tests/validations. 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 PACE provides easy (Single button) identification of Full allow the user to identify inconsistencies such as unlinked requirements or orphans. More complex inconsistency identification system elements (orphans). can be achieved through the use of filters and reports. 4.2. Visibility into existing links from source to implementation--i.e. follow the PACE easily traces across the life-cycle. Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the PACE supports verifications, and allows tracking of Full life of the project, the requirement management tool will be used to verify that verification method, scheduling, time of execution and the requirements have been met. The tool should provide the ability to responsible party. document that the requirement was fulfilled, how it was done, and who was responsible.
Page 319 of 450
PACE v3
Full PACE supports performance verification and variation reporting

Full
PACE maintains a full history (Audit trail) of requirement changes
Full
PACE supports baselines and version control of requirements
Full
PACE supports granular access rights and access control for information
Full
PACE can output data to virtually any specification format, through a unique and powerful template system. PACE has one of the most powerful document generation features available today. PACE supports quality and consistency checking through spell checking, data dictionaries, glossaries, acronym tables, etc. PACE supports the generation of presentation quality charts and graphs after data has been loaded. For a larger array of charts PACE can aggregate ans export data to a charting package
Full
Partial
Page 320 of 450
PACE v3
Full PACE supports customization of output features and markings, including user definable tables, security markings, graphics/figures, etc. PACE has one of the most powerful document generation features available today. PACE supports WYSIWYG preview of finished output. PACE provide status reporting in the tool.

6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements Full management tool. 6.6.1. Technical Performance Measurement status accounting: Status current PACE supports technical performance measurement Full technical performance of various allocated performance requirements and status accounting and monitoring. monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current PACE supports requirement progress/status Full compliance/non-compliance to various requirements monitoring and reporting. 6.6.3. Other ad hoc query's and searches: The requirements management tool PACE includes one of the most powerful ad-hoc Full should support ad hoc query's and searches per the user's discretion. query reporting engines available. 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 PACE allows users to review, markup and comment Full support a team of engineers reviewing, marking up, and commenting on requirements and/or implementation alternatives requirements or implementation alternatives. concurrently. 7.2. Multi-level assignment/access control: Access by the team to the database PACE supports multi-level assignment control, in Full must be tempered by multi-level access control (i.e. the ability to protect things addition to role-base access control. 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the PACE is built atop a standards-based infrastructure Full ability to communicate requirements to other domain-specific design tools which supports easy communication with other (CASE, EE, etc.). domain-specific design tools - even if they are internal/home grown tools.
Page 321 of 450
PACE v3
Full PACE talks to most other tools (as long as they are not closed), due to its standards-based architecture. Examples include: MS Word, MS Excel, MS Project, Testing tools, Design tools, Defect Tracing Tools, Code Management tools, Metrics/Measurement tools PACE provides easy access, standards-based API

Full
Full
PACE supports standard query language (SQL) and open exchange formats PACE supports import of data from standard file formats, and can create links, requirements and other objects by import, without having to re-enter information PACE supports Data Exchange Standards for import and export PACE fully supports standards-based communication with other tools. PACE allows data to be exported and imported between different installations
Full
Full Full Full
Full
PACE supports consistency/comparison checking between same or different tool datasets
Full Full
PACE supports both single and multiple concurrent users PACE server and database can be installed on virtually all popular Operating Systems (UNIX, Linux, MacOS, Windows, etc), and on various versions.
Page 322 of 450
PACE v3
Full Full PACE is standards-based and uses commercially available databases PACE initial resource requirements are modest and PACE performance scales with available resources Server: 4GB+ recommended; Client - As desired Server: Multi-core recommended; Client - As desired Server: 20GB+ recommended; Client - As desired PACE is a multi-threaded, multi-processing application that allows users to multitask, and supports multiple users simultaneously. PACE supports multiple views, and changes in one view are immediately transmitted everywhere. To avoid confusion and disruption, certain views support user-refresh before displaying the new data. PACE supports graphical input and manipulation of data PACE support web 2.0 standards for its main frontend, JAVA and windows component standards for integrated tools PACE supports the creation and playback of commands, and integrates closely with platform scripting and SQL for this purpose. Such scripts primary operate via the PACE API, and are programmable rather than recordable. PACE is web-based. A web interface is not an addon, it is the main interface. PACE supports edit and undo functions

9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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 Full Full Full
Full
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 Full
Partial
10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
Full Full
Page 323 of 450
PACE v3
N/A PACE process configurability allows compatibility with, and support of virtually any process. PACE standards permit PACE out and conversion into virtually any format. Examples include: ASCII, CSV, HTML, XML, RTF, etc. PACE does have a short warranty, but support and maintenance is managed through maintenance, consistent with enterprise software PACE supports network licensing using PACE network and standards licensing modules PACE software updates are typically released every 60 to 90 days to include customer requested features. PACE includes context-sensitive help on virtually every screen. PACE also maintains online usermanuals. PACE information can be located at: http://www.viewset.com Telephone Support is available for PACE. Support centers are located in the USA and in Europe. PACE User Group information, application and is available via the PACE web site: https://www.viewset.com Training courses for PACE are available in various formats, including at the customer site, at ViewSet premises and over the web. Training courses for PACE are available in various settings including at the customer site, at ViewSet premises and over the web.

11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full
12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group
Full Full
Full
Full Full Full
Full
Full
Page 324 of 450
PACE v3
Full PACE users can be trained to use the tool in 2 hours, as PACE operations are intuitive, and based on Web and Desktop operations already familiar to the user. Advanced Admin and User training in available in 1 day and 2 day durations, respectively. PACE software installation assistance with only basic training is available PACE includes many features which are critical to the requirements management process, such as Information Modeling, Life-Cycle reporting, Multi and Dynamic Process support, Document Management and Advanced Content Management. Many of these features are unique to PACE as integrated, advanced components.

Full
N/A
Page 325 of 450
Polarion Requirements v2


Full
Full
Full
Full
Page 326 of 450
Full

Full
Full
Full
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 Partial system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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. Page 327 of 450
Full
Full
Page 328 of 450
Full

Full
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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans).
Page 329 of 450
Full

Full
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). 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
Full
Page 330 of 450
Full

Full
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.). 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
Full
6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format.
Full
Full
Full
Page 331 of 450
Full

6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full
Full
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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives.
Page 332 of 450
Full

Full
Page 333 of 450
Full

Full
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
Page 334 of 450
Full

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
Full Full
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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on?
Full
Full Full
9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? Page 335 of 450
Full
Full Full

9.4.2. CPU requirements 9.4.3. Disk space requirements
Full Full
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?
Full
Partial
Partial
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? 10.6 Web browser interface?
Full
Full
Full
Page 336 of 450
Full

11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
N/A
Full Full Full
Full Full Full Full
Full Full Full Full
N/A
Page 337 of 450
Comments
Polarion Requirements provides several different ways to gather requirements structure from input documents: - requirements identifiers are recognized during LiveDoc (MS Word and Excel) checkin. According to these, links are established b/w requirements - requirements structure is replicated from indentation of headers when importing from MS Word - requirements structure is preserved when importing from DOORS - links are created when importing requirements from a FreeMind MindMap - links to source pages are automatically created when requirements are created from the built-in Wiki Polarion Requirements directly stores MS Word and MS Excel files in its versioned repository. Upon each document commit, a new version of the document is created and a comparison report between two versions can be created and stored. Requirements can be recognized in several ways: - during MS Word import they are recognized from the structure of the document (this can be configured by the user, example heading 2 are new requirements) - during MS Word LiveDoc check-in they are recognized by xml tags and local identifiers - during MS Excel LiveDoc check-in they are recognized from each line These features are supported while authoring content in MS Word or in the embedded Wiki
Page 338 of 450
Comments
Requirements can be directly authored in the embedded Requirements Designer. Requirements Designer is a MS Word-like web tool embedded in the Polarion Requirements client (web browser) that allows authoring requirements content, attributes, structure and links Polarion Requirements is an open tool. Through Polarion API and Web Services any kind of importer can be defined. Some existing examples are: import from MS Word, import from MS Project, import from DOORS, Test Director synchronizer, Enterprise Architect connector, FreeMind MindMap connector Yes, this is fully supported for MS Word and Excel authored documents by Polarion Requirements' LiveDoc technology
Yes, requirements' categories and any attribute can be set by importers. An example is a 3rd party mailet plugin that allows requirements creation out of incoming e-mails. The sender e-mail address determines the project where a requirement must be created. Information are also extraced from the subject and from the e-mail body to set the category, priority etc. he allocation of requirements to sub-system elements takes se sub-systems elements. Polarion Requirements does not embed in its UI graphical features for System element structure. The Full compliance to this requirement is however achieved using Sparx Enterprise Architect for modelling and the available Sparx Enterprise Architect <-> Polarion Requirements connector Yes, any system can be textually represented in terms of items inside Polarion Requirements and links can be established with editable Traceability Matrix and/or filtered tree-views Page 339 of 450
Comments
In Polarion Requirements any kind of artifact can be defined in terms of Work Items (Test Case, Change request, System Element, System Component, ...) or in terms of textual specification in the embedded Wiki. Requirements can be derived into Requirements, into Work Items, into Wiki specifications. Links are automatically created and maintained. Link roles can be defined and automatically selected when deriving a requirement. So a requirement will be, for example, automatically linked to another requirement using the "derived from" role, a Requirement can be connected to Test cases by the "is verified by" role etc. Performance requirements can be expressed in Polarion Requirements in different ways: - if this information is a value, a description or a set of picked items, standard or custom attributes are the best choice - if the information is a complex object, the requirement can be linked to a work item representing the complex object The allocation of portions of the performance requirements to system elements is achieved by splitting the requirements into parts.
Page 340 of 450
Comments
Polarion provides powerful features to create and maintain links. Among these features we have: - requirements can be linked to any other artifact existing in the same project, in another project, inside or outside Polarion Requirements - link role customizability (has parent, relates to) - ability to show impact trees and traceablity matrices filtered by role - ability to link requirements to external items (documents, URLs, artifacts) - ability to link requirements to specific revisions of artifacts - ability to put links in "suspect" mode to allow change propagation through the requirements and artifact structure
Any work item type can be defined in Polarion requirements and linked to a requirement. To improve the usabilit^y project templates are available so, when creating a new project, the user can choose what kind of project it is (example: a project where requirements are linked to risk analysis, have an attached rationale etc.). Constraints can be defined so when saving a requirement or changing its state Polarion Requirements checks if the constraint is satisfied (example, the test case is defined or the rationale is linked to the requirement). Beside this, a requirement can contain or link to a document, a picture, a diagram, etc.
ility to see the links where they come from, where they go, and This can be achieved in two ways: - browsing the impact tree or the traceability matrix - running a query even across links
Page 341 of 450
Comments
Visibility of links is available in the following ways: - inside each requirement there are the lists of incoming and outgoing links - a traceability tree can be created starting from a selection of requirements. To create such tree the user can choose: link role, link direction, tree depth and links to committed changes to artifacts performed to implement a requirement - a traceability matrix is available. In such a matrix the user can filter requirements or any other work item on rows and columns, check the existence of links b/w them, create links, export the matrix or print it In Polarion Requirements every requirement, artifact or work item is versioned. Any change is registered, including the author of the change and the timestamp. Beside this every requirement and work item is managed by a workflow engine. This engine can be easily configured so every change can have constraints. For example, a requirement cannot be turned into the "verified" state if the linked test case has not been passed. This can be easily obtained by an Excel report of a traceability tree.
Every requirement and every artifact are stored and maintained in a Subversion repository. Full version and change management features are available including access control, history and comparisons.
Page 342 of 450
Comments
Baselines can be created at any time. A comparison tool let the user compare any pair of baselines, highlighting every change occurred. Stored documents through LiveDoc technology can be compared as well. For example, this support the ability of sending a MS Word document for an external review, checkin the reviewed document and see which changes have been applied to the document itself. This can be done at requirement level or at field level. Access control is both driven by user access rights and by workflow engine as well. As an example: the requirement description cannot be changed by the requirement submitter when the state of the requirement is "approved".
Any custom MS Word template can be used to export requirements. PDF export for Wiki content is supported as well. Data dictionaries and acronym tables can be easily created in the embedded Wiki. Spell checking is provided by the browser itself (where Polarion requirements runs) or by MS Word/Excel when they are used to author requirements. This can be done in two different ways: - exporting data to Excel and generating graphs there - purchasing one Polarion ALM Enterprise license and use its customizable dashboarding features Any custom MS Word template can be used to export requirements. Requirements and requirements fields and attributes can fill tables, indexes etc. Fully provided by MS Word or Wiki.
Page 343 of 450
Comments
Every requirement lifecycle is managed by a workflow engine. So every requirement state is visible. Beside this, it's also possible to run queries like "show all the requirements that include the word Xyz submitted by John that are in the approved state" Easy to obtain by running a query and export the resulting traceability tree to MS Excel where any calculation can be performed. This can be done in three different ways: - running a query to show compliant or not compliant requirements - exporting data to Excel and generating graphs there - purchasing one Polarion ALM Enterprise license and use its customizable dashboarding features Polarion Requirements provides full-text indexing of every stored information. A powerful query builder supports the user in easily defining his/her queries. Complex expressions using the query language can be directly entered in the search bar as well. Queries can be saved and shared with the project team or with the whole organization.
eam of engineers to look/work on the same information at the Polarion Requirements is built on a Web 2.0 architecture and every information is stored in Subversion. Collaboration is ensured by such architecture and by features like: - embedded corporate and project Wikis - comment threads over single requirements - workflow engine to support requirements lifecycle
Page 344 of 450
Comments
Access control is granted at single requirement level and can be furtherly refined at single attribute level. Normally users have read or read/write access to projects or to item types (requirements, test cases etc.). By adding a Polarion Enterprise license on the server, every Polarion Requirements user can benefit of the "hats" technology. Hats technology provides user and workflow driven User Interface and data protection. As an example, for the user whose "hat" is "customer" a requirement's descriptions is in read and write mode when the requirements is in the "draft" state. Same description is read only when is in "approved" state and budget assignement to the requirement is always hidden in his UI.
Polarion Requirements has a fully programmable OpenAPI and provides access through Webservices. So any integration (data importers, exporters, synchronizers, triggers) can be established with any other open technology. Some powerful integrations are available for free download from Polarion's website including: - HP Mercury Test Director - IBM Telelogic DOORS - Sparx Enterprise Architect - MID Innovator - Freemind - MS Visual Studio - Eclipse
Page 345 of 450
Comments
Polarion Requirements has a fully programmable OpenAPI and provides access through Webservices. So any integration (data importers, exporters, synchronizers, triggers) can be established with any other open technology. Some powerful integrations are awailable for free download from Polarion's website including: - HP Mercury Test Director - IBM Telelogic DOORS - Sparx Enterprise Architect - MID Innovator - Freemind - MS Visual Studio - Eclipse Polarion Requirements has a fully programmable OpenAPI and provides access through Webservices. So any integration (data importers, exporters, synchronizers, triggers) can be established with any other open technology. Some powerful integrations are awailable for free download from Polarion's website including: - HP Mercury Test Director - IBM Telelogic DOORS - Sparx Enterprise Architect - MID Innovator - Freemind - MS Visual Studio - Eclipse The query language supported by Polarion Requirements is the Lucene query format (http://lucene.apache.org)
Page 346 of 450
Comments
External data including linking information can be imported from - Comma Separated Value files - XML files - MS Excel tables - MS Word documents Polarion Requirements' data are stored in XML format. So they can be natively exchanged with any other tool. Beside this, several export formats are supported, such as CSV, Ms Excel etc. The Polarion Requirements database is a Subversion repository. Every Open Source or commercial solution to manage data replication, load balancing, fault tolerance issues can be used. Due to the fact that Polarion Requirements is a Web 2.0 application, however, it is pretty uncommon that our customers perform data replication: they access the same server through VPN. Polarion Requirements has been successfully tested on the field with 1500 users on the same server accessing from 10 different locations. As for 8.2.1, any Open Source or commercial technology available to perform Subversion repositories can be used to check data consistency or verification. Multiple concurrent users are natively supported as Polarion Requirements is a Web 2.0 application. The Polarion Requirements server can be installed on every Windows or Linux/Unix platform. The client runs in a Web Browser, so every computer equipped with MS Explorer or Firefox can be used. Polarion Requirements stores information in Subversion that is Open Source. Page 347 of 450
Comments
Minimum 0,5 GB, 2 Gb Ram recommended on Server. No installation on Clients as Polarion Requirements runs in Web Browser. Minimun 10GB, 40Gb recommended on Server. No installation on Clients as Polarion Requirements runs in Web Browser. Polarion Requirements is a Web 2.0 application, the user can open as many browser windows or tabs he/she needs and perform several jobs in parallel. Server jobs like exports or imports can be scheduled in background. Polarion Requirements is a Web 2.0 application, the user can open as many browser windows or tabs he/she needs and perform several jobs in parallel. Changes in one window sometimes need page reload to be visible in other windows. Polarion Requirements itself doesn't provide modelling or design features. Editable Traceability Matrix is available to graphically maintain links. Other visual edits can be performed using Sparx Enterprise Architect or Freemind. Polarion Requirements is a Web 2.0 application, when the browser is running in Windows, some usability features are available through WebDAV. Yes, through API scripts or Web Services access.
Polarion Requirements is a Web 2.0 application, it works natively in a web browser, so every functionality is available via Web.
Page 348 of 450
Comments
Using the features provided by Subversion, that is the Polarion Requirements' storage, it is possible to go back to any point of time in data life. Any standard can be supported.
License fee includes one year maintenance Polarion Requirements has an embedded license manager providing access to named users. A major release is issued every year. Service releases are provided every 6-8 weeks. Every major release upgrade and service release are free for customers with running maintenance contract. Yes. www.polarion.com or contact mailto:sales@polarion.com E-mail and phone support are available during business hours. SLA for 16X5 and 24X7 support are available. User blogs and opensource projects (components, connectors, integrations) in www.polarion.org Open training classes available Yes. Two days hands-on workshop recommended. Polarion Requirements can be downloaded and installed with one-click installation. No training needed.
Page 349 of 450
Psoda v5.02.1
Date of Submission:
8-Mar-10


Partial Default values can be provided for missing fields in the CSV import file.
None None
None
Full Full Full
Manual entry of requirements including dependancies for traceability. Import requirements from a CSV file
Requirements can be matched based on their reference number to update existing entries rather than add new entries. Requirements can be classified as part of the reference Full field, using the category field and by associating requirements with high-level requirements or product features. Requirements can also be batched together into sub-projects. 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 Requirement traceability can be visualised in a traceability Full system implementation (such as architecture, functional decomposition, WBS, matrix as well as in a dependancy tree. etc.) and display them graphically such that requirements can be linked to 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 Requirements can be structured in a hierarchy with full traceability.
Page 350 of 450
Psoda v5.02.1
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 Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, System elements can be defined as sub-projects or Full cost, etc.): The ability to link performance requirements to system elements requirements. Dependant requirements can then be such as weight, cost, throughput, etc. This also includes the ability to allocate associated with these. portions of that performance requirement to system elements. 3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Owner allocation, traceability to test-cases, priority, Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the traceability from issues, traceability from change-requests, ability to attach rationale, assignments, criticality, test/validation and many other traceability from risks. issues to the requirement, allocation, and the system element to which a requirement is linked. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the User-customisable lifecycle (workflow). Requirement status Full life of the project, the requirement management tool will be used to verify that will track the stage of the requirement. Attachments to the the requirements have been met. The tool should provide the ability to requirement can include additional details. document that the requirement was fulfilled, how it was done, and who was responsible.
Page 351 of 450
Psoda v5.02.1


None
Full
Full automatic tracking of changes to a requirements including date, who made the change and previous values.
Full
Projects can be baselined, including all requirements, dependencies, risks, issues, defects, test-cases etc.
Full
Fine-grained access control down to individual actions on an object.
Full
6.2. Quality and consistency checking (spell, data dictionary): The tool should Partial also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Partial management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. Page 352 of 450
All requirements can be exported to CSV/Excel format for inclusion in an external report. User-customisable report templates can produce outputs to any specification. Reports can be exported to ASCII, HTML, MSWord, Excel and PDF formats. Spell checking can be performed by most browsers (for example Firefox) Some charts are supported, including burn-down and piecharts. Customisable report templates allow users to create any ASCII, HTML, MSWord, Excel and PDF report.
Psoda v5.02.1
6.6. Status reporting: Tool users need to status information in the requirements Full management tool. 6.6.1. Technical Performance Measurement status accounting: Status current User-configurable lifecycle (workflow) with automatic Full technical performance of various allocated performance requirements and tracking of status change times. monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Based on requirement status field Full compliance/non-compliance to various requirements 6.6.3. Other ad hoc query's and searches: The requirements management tool Query tables can be sorted on most fields. Report templates Full should support ad hoc query's and searches per the user's discretion. can perform all other queries. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the All requirements can be exported to CSV/Excell format for Full ability to communicate requirements to other domain-specific design tools inclusion in external tools. XML export of all data. Web(CASE, EE, etc.). services API allows for integration with 3rd party tools. 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? Full MSWord, Excel, CSV, HTML, XML. Full internal integration with other modules including Programme & Project Management, Test Management and Product Management. Web-services API
Full
Full
Full access to all datastructures via web-services API
Page 353 of 450
Psoda v5.02.1

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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..)

Full Requirements and test-cases can be imported from CSV files.
Full
Export of all data to XML. Export of all tables to CSV or Excel. Report templates can generate any ASCII, HTML, Excel or MSWord format. Import from CSV. The tool is fully hosted with no need to exchange data between specific sites.
Full Full
8.2.2. Consistency/comparison checking between same-tool datasets: Does Full 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 Full multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and Full operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or Full commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration Full requirements: 9.4.1. Memory requirements Full 9.4.2. CPU requirements Full 9.4.3. Disk space requirements Full 10. User Interfaces 10.1. Doing one thing while you are looking at another: Does the user have the Full ability run a report and look at a requirement at the same time? 10.2. Simultaneous update of open views: If the tool allows for multiple Full windows/views into the tool--does a change in one view automatically reflect in all other views? 10.3. Interactive graphical input/control of data: Does the tool support graphical Full input and manipulation of data? 10.4. Which window's standard do you follow?: If your tool supports a window's Full standard, which one(s)? Page 354 of 450
This is not required as the same dataset is available across all sites.
Multiple concurrent users with automatic row-level locking Any modern browser including Firefox, Chrome, IE, Opera and the Symbian browser. MySQL
Client-side only a browser is required. Client-side only a browser is required. Client-side only a browser is required.
Refresh may be required in other windows
XHTML, JavaScript, CSS, WAI WCAG
Psoda v5.02.1

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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes

Full The report templates are script driven. Other tasks can be automated via the Web-services API. The UI is web-based Edit undo within the current form. Change history is automatically stored. XHTML, JavaScript, CSS, WAI WCAG, MSWord, Excel
Full Full
Full
Full Full Full
Warranties does not apply as the tool is fully hosted and all updates are directly available to all users. The tool uses a per user per month subscription model. Updates automatically become available to all end-users. No additional costs are associated with upgrades. Online context-sensitive help is available. http://www.psoda.com/cms.php/what-is-psoda/requirementsmanagement 24/7 phone support at +64 21 224 3617
Full Full Full None Full
Training classes are available for basic users, advanced users and administrators. These are normally held onsite.
Full Full Full
Basic user - 4 hours;Advanced users - 8 hours;Administrators - 8 hours No software installation is required other than an Internet browser
Page 355 of 450
Psoda v5.02.1


N/A Test-case management with traceabiltiy from requirements; Attachments to requirements; Product/release/feature/release note tracking with traceability to requirements; Risk management with traceability to requirements. Task and Budget planning and tracking. Benefits Management. Product Management.
Page 356 of 450
PTESY v5.4


Full Index and glossary of the documents can be imported in the PTESY archive (DocBook). PTESY allows freezing a requirements root (root is the alphanumeric part of the requirements ID), to compare differently frozen roots, to evidence the differences, and other analytic functions. PTESY imports requirements from MSWord on the simple rule of 1 title = 1 requirement, and from Microsoft Excel, taking each Excel row as a requirement (columns can be dynamically assigned to record fields by the user). The requirement content is imported graphically, with all pictures, tables and text. The system assigns a unique ID to each imported requirement. PTESY always imports the whole document. The user will then specify, for each requirement, the verification method (Test, Analysis, Review of Design, Visual Inspection, None, or other methods, according to his/her used methodology). Requirements can be created inside the tool. see point 1.2 PTESY can export a new version of the document, in MSWord or Microsoft Excel, formatted as the original document, with titles levels, pictures, tables and text. Furthermore, PTESY allows to link documents, both internal (codified inside the PTESY db) and external (not codified). Linked documents can be upgraded without loosing the link, provided that the file name remains the same.
Full
Full
None
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. 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 Full Full
Page 357 of 450
PTESY v5.4
Full PTESY ReqBook allows the user to classify and categorize requirements according to several keys (structural, management, time, authors, owners, etc), at identification time and during the whole project life cycle.

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 None system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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 PTESY allows to define several structural objects, namely: subsystems, subassemblies, work packages, packages, verification methods, test types, requirements types, and others. Subsystems and subassemblies are structured, in a cascade, parents-children, mode. Each methodologic object, belonging to all the methodologic categories requirements, test procedures, test cases, problems, events, etc can be assigned to one or more subsystems and subassemblies. PTESY also allows to refer (reference link) each object to any other object, for instance a requirement can be referred to other requirements, problems, test cases, events, documents, i/o signals, etc
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements.
Page 358 of 450
PTESY v5.4
Full PTESY allows to clone requirements (and any other methodologic object) from objects existing in the database. PTESY also allows to create parents-children links among requirements of different levels (e.g. a system requirement can be linked as a child to one or more user requirements). Parents-children links can be created also among test cases and the covered requirements, as well as among I/O signals and parents requirements. PTESY allows the user to produce traceability matrices, in MSWord format, of all the links categories, with the possibility to choose the columns to be exported. Traceability matrices can be sorted by parents or by children. It is also possible to get the orphans matrices, and the childless matrices. Each requirement (including performance reqs.) can be linked to any subsystem / subassembly, to risks and to configuration items.

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.
Full
Full
Links can be established among requirements and configuration items (system parts) and vice versa. Traceability matrices can be produced, sorted by parents or by children.
Page 359 of 450
PTESY v5.4
Full PTESY includes a specific tool for test engineering management, TestBook. By means of such a tool it is possible to define test procedures, test cases, and step procedures. It is also possible to compile the test report, while the test are executed. Each test case can be linked to its covered requirements. Traceability matrices can be produced, sorted by test cases or by requirements. PTESY includes as well a tool named EventsBook, that allows the user to take note of any criticality or meaningful event related to requirements implementation, validation, etc PTESY includes as well a tool named LogBook, that allows the user to record and manage any detected problem, during test execution or outside test execution. Each logged problem can be referred to one or more violated requirements, to the test case which allowed to detect the problem, and to other objects.

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 PTESY allows full traceability, along the whole project life Full allow the user to identify inconsistencies such as unlinked requirements or cycle, from user requirements, to system requirements and system elements (orphans). architectural design, to system items, to test cases, to detected problems. Traceability matrices of all levels can be produced, as already mentioned point 3. PTESY allows the user to list orphans and childless objects, exporting the list in table format, MSWord and Microsoft Excel. 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 PTESY allows the user to see the whole tree of any object. E.g., one can point to a user requirement, and graphically see all the children and nephew objects, through the different life cycle levels: system requirements, architectural design, system items, test cases, problems (if any).
Page 360 of 450
PTESY v5.4
Full PTESY allows, by means of ReqBook, selecting frozen or unfrozen requirements, both implemented and not. By means of TestBook, it is possible to see the executed test cases, and the verified requirements. The workflow function of requirements allows defining how many states the user wants, i.e. issued, frozen, implemented, verified, and selecting requirements according to different states, in order to check the work in progress. PTESY TestBook allows the user to see the test reports, where each test step actual information gives the detailed result of the tested requirements. Test reports can be select in order to show only the test cases of the performance requirements, if the user wants so.

Full
Full
Full
Full
PTESY is highly configurable, according to the used methodologies and preferred practices. PTESY holds a copy of each version of each object (requirements, test cases, etc). Each change causes a save of the old version in the historical archive. All the old versions of each object are visible in a special age, and the user has the possibility to fetch it and to resume it, if needed. PTESY allows the user to freeze a requirements root (root is the alphanumeric part of the requirements ID), to compare differently frozen roots, to evidence the differences, and other analytic functions. Based on the access & privileges control, only the users defined by the administrator have the privilege to modify or introduce objects, be they requirements, test cases, or any other methodologic objects. PTESY can export documents in MSOffice format (MSWord and Microsoft Excel). PTESY allows the user to export documents respecting the document structure setup by the user, titles, titles formats, as the document was imported and modified after import.
Full
Page 361 of 450
PTESY v5.4
None

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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements management tool.
None
Full
Full
Full
Full
PTESY archives the methodologic objects in full graphic format. When exported, documents include pictures, tables, text, and all the graphic signs contained in the original document (or inserted in the database, if the document originates in the db). PTESY builds the document in MSWord or Microsoft Excel format, and opens it once produced, allowing the user to see it. PTESY has different tools for reporting: Test Reports, Problems Reports, Events Reports. Test Reports can be configured by the user in order to get test summary and statistics, detailed test case results, problems report (detailed or compact), events report. Test Reports can also be customized by the user, choosing which fields (of test procedures headers, test case headers, etc) to be printed or not. PTESY TestBook and Test Reports provide all the functions for reporting and monitoring the test activities in progress. LogBook provides functions for problems logging, categorization, selection and reporting, minutes of meetings, sharing of problems, solutions, action items. PTESY LogBook allows the user to create Non Conformance Reports, including classes of problems, under an NCR code, received from the Corporate Quality Office or Dept. NCR format reports violated requirements and all the info foreseen by methodologies. PTESY provides very powerful research forms, allowing the user to select different keys, in order to select the desired ensemble of objects.
Full
Full
Page 362 of 450
PTESY v5.4
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 PTESY is a full client server application, specially designed Full support a team of engineers reviewing, marking up, and commenting on to share information among participants to project teams. requirements or implementation alternatives. PTESY ReqBook has a function specifically targeted to allow project team members to add comments to each issued requirement. 7.2. Multi-level assignment/access control: Access by the team to the database The PTESYs access & privilege control allows only to Full must be tempered by multi-level access control (i.e. the ability to protect things persons granted by proper privileges to write and modify from being modified). This also includes the ability to submit changes into an data in the different archives. Read/Write/Audit privileges approval cycle (for acceptance/voting) before committing the changes to the tool are granted to persons upon a grid including projects and for everyone to see. different tools, e.g. one person could be allowed to read/write requirements (ReqBook), only read test procedures (TestBook), have no access to i/o signals (IO_Manager). 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the PTESY is not only a requirements management tool, but an Full ability to communicate requirements to other domain-specific design tools integrated system to manage: Requirements, Test (CASE, EE, etc.). Procedures, Test Reports, Problems, Documents, I/O Signals, Risks, Configuration Items, Events. Full traceability across all the methodologic objects. PTESY is based on MS SQL Server relational database, fully open to ODBC and JDBC interface tools. It is very easy to develop proper import-export software procedures, also using standard SQL language. The technical documentation allows skilled user to know tables and fields, in order to write queries. 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? Full PTESY is already integrated, therefore all the tools are normally communicating, linkable and traceable each-other: a) ReqBook = requirements management tool; b) LogBook = problems log and management; c) TestBook test procedures and test cases; d) DocBook documents management; e) IO_Manager i/o signals management; f) EventsBook events and notes management g) RiskBook risks management tool.
Page 363 of 450
PTESY v5.4
Full see point 8.1

Full
yes, see point 8.1
Full
yes, PTESY can import structures detailed in ascii and/or xml files.
Full Full
Full
- xml PTESY is a full client server application, based on a unique centralized database, therefore all tools included in PTESY can very easily communicate each other. PTESY allows the user to work offline, e.g. log problems on the commissioning site, where no internet connection is available. When reconnecting to the server, the offline cached data can be merged on the server database. Yes, such operations can be done by means of customer written procedures, connecting the two databases.
Full
Full
PTESY supports multiple concurrent users. MS SQL Server allows thousands of concurrent connections. PTESY is commercialized on the basis of the number of purchased concurrent client licenses: the bigger the number of client licenses the lower the price of each single license. PTESY runs on Microsoft platforms: On server: Windows 2000 Server, 2003 Server; On clients: Windows 2000 professional, Windows XP professional; Office 2000 or Office 2003 is required. PTESY uses Microsoft SQL Server, commercial database
Full
PTESY v5.4
Full Full Full Full

9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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?
Client = 1 gbyte ram; Server = 1 gbyte ram Client = Pentium IV; Server = a server machine, even a small one (like Client = 50 Mb for software; Server = according to the foreseen database dimension Yes, but never forget that we are working on a Microsoft machine (J), better to let it work when producing an MSWord document If the change is on a database record, no, until the transaction is not committed. PTESY locks the record, when one user starts editing it, all other users who attempt to modify it will be notified that the record is locked and they must wait. However all the users can see the last committed version of the record, even if somebody is editing it. As to the views changes, PTESY is made of several pages (one per tool), and can physically connect different projects databases. When the user changes project connection or decides to work with a different tool, all the views change accordingly PTESY uses an embedded html editor. PTESY uses standard Microsoft Windows windowing. PTESY uses MS SQL Server database. It is possible to use SQL scripts and also to make customer software procedures (using any language to make an external ad hoc application script or application, like VisualBasic, VBA, VB script, C++, Java, ), to automatically manage repetitive tasks. However such actions are not available to any user, and should be made by our expert personnel. not yet, with new version, in progress, yes. All editing operations can be rolled-back before commit.
Full
Full
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 Full Partial
10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
Partial Full Page 365 of 450
PTESY v5.4
N/A ISO9001, ESA PSS05, ECSS, MIL STD 498, ISO 9001:2000, CMMi, ISO 12207, ISO 15504 (SPICE).

11.1. 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. Warranty: Does your tool have a warranty, if so what is it?
Full
Full
Full
Full
Full Full
Bugs are fixed for free, if any, to all customers, for one year after licenses installing. Starting with second year, customers can sign the maintenance contract, giving right to all new releases, telephone assistance, remote assistance and/or on site interventions (according to the purchased level). PTESY is sold on the basis of the number of purchased client licenses. The higher the number of client licenses, the lower the single license price. Each client license is linked to the client workstation where it is installed. PTESY issues 1 or 2 releases per year. New releases are free for the customers who signed the maintenance contract, and can be purchased by the customers who didnt. PTESY has three help systems. One paper manual (pdf), an online help function (normal Microsoft help standard) and detailed context sensitive tutorial cards, which can be activated or deactivated for automatic prompt when a PTESY page or form is accessed. http://www.andromeda-srl.com/ Phone assistance is provided to customers who signed the maintenance contract. Phone assistance is by now limited to Italy business hour, we foresee to open soon a point of assistance in the US. When the customer has a public IP, we can provide remote assistance through an internet VPN.
None Full Several education and support activities are provided by Andromeda: a) specific training on the PTESY tool; b) methodologic education courses; c) consultancy for project life cycle management.
Page 366 of 450
PTESY v5.4
Full Usually Andromeda gives the basic training in conjunction with the product installation, on the customers site. An introductory seminar is given, for the PTESY users, including a detailed demo and an essential discussion of the methodology. After that, we give one day of training on the job, helping the users to make a first project environment, import the initial documents, defining structures. If the customer requires it, we can provide longer training periods, or provide activities of project life cycle management, in consultancy. It depends on whether the user is already used to standard methodologies or not. If yes, two days are normally enough. If not, a proper education on standard methodology is strongly suggested: space, military or ISO, or, when the customer is not constrained to use one of the above, we can give our essential methodology (it summarizes the minimum indispensable of the most popular methodologies). We prefer that our skilled personnel make the installation, both for server and client licenses.

Full
13.4 Software installation with only basic training 14. Additional Comments
Full
Page 367 of 450
PTESY v5.4
N/A As to our philosophy and methodology, requirements management is only one phase of the project life cycle. Test Engineering and Commissioning especially in infrastructural and industrial automation, are very relevant, at least like requirements. Many commitments fail on commissioning, not on requirements. Therefore, we give the same relevance to test engineering, and to the traceability of the whole project life cycle objects. Thats why we made a fully integrated system, since we dont work only in aerospace and defense, but also in the automation segment. PTESY includes a full requirements management tool, but it is an integrated system to manage: Requirements (ReqBook), Test Procedures (TestBook), Test Resports (TestBook), Problems (LogBook), Documents (DocBook), I/O Signals (IO_Manager), Risks (ReqBook), Configuration Items (ReqBook), Events (EventsBook). Full traceability across all the methodologic objects.

Page 368 of 450
RaQuest v3.0

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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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. 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.

Full
None None
Partial
Full
Full
1.5.1. Batch-mode document/source-link update: Does the tool have the ability Partial to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Full classify/categorize requirements during identification 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
Page 369 of 450
RaQuest v3.0
Full

Full
3.3. Bi-directional requirement linking to system elements: The linking of Full 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, Full 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. 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 Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans).
Page 370 of 450
RaQuest v3.0
Full

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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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
None
Full
Full
Partial
Full
Page 371 of 450
RaQuest v3.0
Partial

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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format.
Full
Partial
Partial
Full
6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
None
Full
6.6.3. Other ad hoc query's and searches: The requirements management tool Full should support ad hoc query's and searches per the user's discretion. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives.
Page 372 of 450
RaQuest v3.0
Full

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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to?
Full
Full
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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment
Partial
None
Full
Partial Full Full
None
Page 373 of 450
RaQuest v3.0
Full

9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements:
Full Full Full
9.4.1. Memory requirements
Full
9.4.2. CPU requirements 9.4.3. Disk space requirements 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 Full Full
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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
Full
None Full Partial
Full Partial
Page 374 of 450
RaQuest v3.0
N/A

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
Full Full Full
12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes
Full
Full None Full
Partial
13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Partial None None
N/A
Page 375 of 450
RaQuest v3.0
Comments
RaQuest can import Requirement form existing documents (data) like EA project file, Word, CSV and also link any documents and graphics to Requirements.
mouse highlighting.
MS Word: Requirements are selected by the user in an MS Word document, and created using a right-click menu option. (Word Add-in) Requirements can also be created directly by the user. RaQuest can import a lot of Requirements from CSV at a time. RaQuest compares their time stamps. If RaQuest finds the difference between them, RaQuest alerts the user, but does not update the link automatically.
RaQuest compares their time stamps. If RaQuest finds the difference between them, RaQuest alerts the user, but does not update the link automatically. Supports comprehensive requirements class typing with User Defined Attributes. he allocation of requirements to sub-system elements takes se sub-systems elements. Yes. RaQuest can capture system implementation using requirement attributes or system implementation requirements that are linked to the requirements. Graphical traceability tree, matrix and UML chart show the relationships between system requirements and Page 376 of 450
RaQuest v3.0
Comments
Yes. RaQuest can capture system implementation from any appropriate text documents and display the relationship textually between system requirements and implementation.
architecture captured, requirements are allocated to the various RaQuest generates requirements derivation automatically and display the relationship graphically between the source requirement and the derived requirements. RaQuest also monitors the update history. When the source requirement is updated, Request alerts RaQuest provides various system elements like Difficulty, Priority, Stability, and Risk to allocate performance requirements.
Bi-directional link is fully supported in Matrix view. Matrix view has the ability to easily establish and abolish links between any type of object in any direction.
RaQuest provides several types of user-defined attributes. The number of user-defined attributes are unlimited. RaQuest provides the capability to assign any number of user-defined attributes to a group of objects. These attributes are easily reported on ility to see the links where they come from, where they go, and RaQuest has the ability to check inconsistencies among linked requirements and report it. It is easy to trace the cause of the inconsistencies.
Page 377 of 450
RaQuest v3.0
Comments
RaQuest visually shows the relations among requirements. This feature generates an EA diagram. RaQuest also shows the relations among requirements in matrix-style and user can easily edit the relations with the matrix diagram. RaQuest has the ability to verify the fulfillment of requirements using Approve Feature. The approved requirement has the information of the approval. (Who? When? How?)
RaQuest records update history of requirements automatically. Each requirement has its update log as the property. The update log shows who, what, when updated the requirement.
RaQuest has ability to generate Baselines as needed. RaQuest also compares the new and old Baselines and shows the difference between them. Enterprise Architect provides full access control to requirements.
RaQuest has the wide documentation ability to output documentation in HTML, Word, CSV, and Excel format.
Page 378 of 450
RaQuest v3.0
Comments
RaQuest has the powerful glossary feature to manage terms used in the project. The glossary feature is completely bidirectional with the glossary feature in Enterprise Architect. RaQuest generates EA diagrams. The diagram is compatible with Enterprise Architect. The user can edit or print it in Enterprise Architect. RaQuest can generate the RTF customizing output.
RaQuest has the ability to allow the user to preview Requirement List on-screen in finished format before its printing, but generated document like Word cannot be previewed on-screen before its generation. RaQuest has Status Counter feature. It gathers up the status information of the project and saves the information. The saved status report can be exported in CSV format.
Filtered information can be used as the status reporting on current compliance/non-compliance to various requirements. RaQuest provides ad hoc queries and searches. The user can combine various search conditions. eam of engineers to look/work on the same information at the RaQuest provides a multi-user solution for any number of users sharing the project information. RaQuest allows all users access to the same requirements at the same time. The automatic lock systems is activated when multiple users access to the same requirement.
Page 379 of 450
RaQuest v3.0
Comments
Multi-level assignment/access control is enabled by User Permissions feature of Enterprise Architect. (for only users of Enterprise Architect Corporate Edition)
RaQuest works with UML tool Enterprise Architect. The project file (data file) is completely compatible for both RaQuest and Enterprise Architect. RaQuest has interfaces to the following tools: * Enterprise Architect (data compatibility) * Microsoft Word (Requirements Import/Export) * Microsoft Excel (Requirements Import/Export) Enterprise Architect provides external applications program interface as the add-in feature.
Yes. RaQuest can import data from the following file formats.* Enterprise Architect project file* CSV format* Microsoft Word (add-in feature) Requirements baselines are saved in XML format. No Response Added. Data can be exchangeable in XML format. Users can open the same project at the same time. And users can use the same project at the same time, when the project is located in database.
Page 380 of 450
RaQuest v3.0
Comments
RaQuest support both a single user and multiple concurrent users. Microsoft Windows2000(32bit SP4)/XP(32bit SP2)/Vista(32bit) RaQuest can be used with commercially available database like Oracle and SQLServer. "[Software] Enterprise Architect 5.0 (or later version) [Screen] 1024x768 screen resolution preferred for showing lists and manipulate Requirement items - 800x600 useable, 640x480 not suitable. " [RAM] depends on OS - 96 MB for Windows 2000, Windows XP and Windows Vista, (more RAM will improve performance). 20MB of available hard-disk space Yes. RaQuest always shows Tree and List. Tree shows the hierarchical structure of Requirements and List shows the summary of Requirements. You can open the properties dialog of a Requirement at the same time. Yes. The change automatically reflect in all other views, when it is saved.
Microsoft Yes. The user can create add-in programs in Enterprise Architect. Requirements can be exported to HTML. attribute can rollback used update log. Page 381 of 450
RaQuest v3.0
Comments
RaQuest supports many output formats/standards. It is currently used in various industries like electric, automobile and IT industries. Support for a full year. Node Locked License or Specify User License or Floating License. Basically every two weeks. However we respond fatal bugs immediately as needed. Registered user can use the latest version for a year at no additional fee. subscription period) At the end of subscription period, registered users can select whether they r Everyone can download the manuals and latest HTML help file from our web site. We also provide email support service. Visit http://www.raquest.com/
Everyone can use User Forum. (Internet Discussion Board)
Startup Manual and Install Guide describe its powerful usability. They can be downloaded from our web site freely. Tool-specified training class in Japan. Contact us if users would like to have a training in Japan, especially near Tokyo area. There are no official data about the recommended training time, but the tool is highly user-friendly. The installation is very easy and the plain installation guide is sent to a registered user with the delivery of license key by email.
Page 382 of 450
ReqMan v2.0
Date of Submission: 12-Dec-08


Full Use of flexible Questionnaire Module to submit document contents and parse the submissions to individual requirements with full traceability. All requirements are treated as separate entities. Requirements and attributes have full change history. All data can be exported to Excel for comparison. Can be done with help of professional services.
Partial
Partial
Full
Use of flexible Questionnaire Module to gather user needs and parse the submissions to individual requirements with full traceability.
Requirements are entered in the web interface or via the Questionnaire module. Requirements can be imported from a variety of formats via Partial professional services. All requirements can have digital links (parent/child/biFull directional). All documents and reports are dynamically updated real-time. It is possible to define specifications with an indefinite treeFull based table of contents. In addition requirement attributes (lists, texts) including validation can be configured on-the-fly to aid the classification. 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 Graphical traceability matrix and tree views show the Partial system implementation (such as architecture, functional decomposition, WBS, relationships between system requirements and etc.) and display them graphically such that requirements can be linked to them. implementation. Full 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 Requirements, post-it notes and attachments can all be stored at the requirement level.
Page 383 of 450
ReqMan v2.0
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 All requirements can have digital links (parent/child/biFull derive/create additional requirements and link between them such as directional). requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, Requirement attributes (lists, texts) including validation can Full cost, etc.): The ability to link performance requirements to system elements be configured on-the-fly. Configurations are dynamically such as weight, cost, throughput, etc. This also includes the ability to allocate available in searches and reports. Configuration can be portions of that performance requirement to system elements. done to suit any specialized needs. 3.3. Bi-directional requirement linking to system elements: The linking of All requirements can have digital links (parent/child/biFull requirements to system elements can be accomplished from either end of the directional). 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, Requirement attributes (lists, texts) including validation can Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the be configured on-the-fly. Bugs and changes requests are ability to attach rationale, assignments, criticality, test/validation and many other traced and dynamically linked. issues to the requirement, allocation, and the system element to which a requirement is linked. 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 Use of traceability matrix in different dimensions: links to Full allow the user to identify inconsistencies such as unlinked requirements or other requirements and custom attributtes and reports can system elements (orphans). be used to identify any inconsistencies. 4.2. Visibility into existing links from source to implementation--i.e. follow the Full traceability via electronic links between user needs, Full links: With the requirement links in place, the user needs the ability to follow the change requests, business requirements, functional links to see where they come from and where they go to. requirements and bugs. 4.3. Verification of requirement (was it done, how was done): Throughout the Full change history is traced at the most detailed Full life of the project, the requirement management tool will be used to verify that requirement level for all attributtes. Requirement attributes the requirements have been met. The tool should provide the ability to (lists, texts) can be configured on-the-fly to register criteria document that the requirement was fulfilled, how it was done, and who was and this can be extracted in reports that will complete the responsible. analysis.
Page 384 of 450
ReqMan v2.0
Full Full change history is traced at the most detailed requirement level for all attributtes. Requirement attributes (lists, texts) can be configured on-the-fly to register criteria and this can be extracted in reports that will complete the analysis. Full change history is traced at the most detailed requirement level for all attributtes. Search capability for creation and modification before or after certain dates an intervals.

Full
Partial
Manual baselining is available using the currently available reports exports. Fully integrated baselining and comparision is on the short-term road map. The entire ReqMan platform is based on a permission model where users are assigned various permissions to the various entities: projects, specifications, requirements, questionnaires etc. Report formats can be configured to comply with any format: word, excel, text, html, xml etc. Support for data dictionaries, acronymtables etc. Spell checking can be done using a third party application such as Microsoft Word. Report formats can be configured to comply with any format: word, excel, text, html etc. Attachments and formatting of requirements are persisted in reports to extent possible.
Full
6. Documents and other output media 6.1. Standard specification output (if so what kind): The requirements Full management tool should output documentation in various military/commercial standard formats (490, 2167, etc.). 6.2. Quality and consistency checking (spell, data dictionary): The tool should Partial also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Full management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. Page 385 of 450
Reports are opened in the respective viewers according to format.
ReqMan v2.0
Full There are multiple options for configuring status settings for specification, questionnaires, tenders, requirements etc. Aggregate status counts can be shown on graphical dashboards. Full change history is traced at the most detailed requirement level for all attributtes. Requirement attributes (lists, texts) can be configured on-the-fly to register criteria and this can be extracted in reports that will complete the analysis. Full change history is traced at the most detailed requirement level for all attributtes. Requirement attributes (lists, texts) can be configured on-the-fly to register criteria and this can be extracted in reports that will complete the analysis. Support for full add-hoc query on all static and dynamic fields. Full support for batch updating multiple requiremetns.

Full
Full
Full
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 Full support for allowing multiple stakeholders to contribute Full support a team of engineers reviewing, marking up, and commenting on comments and attachments. requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database The entire ReqMan platform is based on a permission Partial must be tempered by multi-level access control (i.e. the ability to protect things model where users are assigned various permissions to the from being modified). This also includes the ability to submit changes into an various entities: projects, specifications, requirements, approval cycle (for acceptance/voting) before committing the changes to the tool questionnaires etc. The approval cycle can be managed via for everyone to see. requirement level attributtes or by implementing a fully fledged workflow. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the The platform can either export data in configurable formats Partial ability to communicate requirements to other domain-specific design tools or bi-directional exchange can be done via the API. (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Any tool where you can define the target export format. Full tool interface with or talk to? Examples include: Microsoft Word, Excel, Project, Enterprise Architecht, Rational Rose. Page 386 of 450
ReqMan v2.0
Partial The platform has an API for external access.

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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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?
Partial
Queries can be performed via the API.
Partial
Data can be imported with the help of Professional Services.
Partial Full Full
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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements
Partial
Any data exchange format can be fulfilled via the API. Data is shared amongst functional modules. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenanat architechture. http://www.requirementone.com/Platform_Start.aspx . Any data tranfer or specialized needs can be facilitated by professional services. Any data tranfer or specialized needs can be facilitated by professional services.
Full Full
Multiple concurrent users. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. Recommended browsers: Internet Explorer and Firefox. Commercial. N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture.
Full Full Full Full
ReqMan v2.0
Full Partial Yes. Support for tabs. Data is updated when the web page is refreshed. All data is shared. Drag-drop and graphical selection is available depending on context. Microsoft. Support for 1-click templates at various levels: structure (projects, specification, questionnaires) and content (requirements, notes, users). The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. Undo based on change history. Deleted data is typically placed in a buffer until actively permanently purged. Report formats can be configured to comply with any format: word, excel, text, html, xml etc. Support for templates at various levels: structure (projects, specification, questionnaires) and content (requirements, notes, users). See master subscription agreement here: http://www.requirementone.com/Master_Subscription_Agre ement.aspx N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. Upgrades are applied 4-6 times a year. All upgrades are free. Context sensitive help, Getting Started Guides, Forum and Live Chat available online. http://www.requirementone.com/ReqMan_Start.aspx If you have an active Support Level Agreement with RequirementOne you can contact support via phone, e-mail or chat.

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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full Full Partial
Full Full
N/A
Full
12.2. Network license policy: Does the tool support network licensing (floating, Full node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates Full released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the Full tool? 12.5. Provide Internet Web page location for company/tool info Full 12.6. Phone support: What type of phone support is available from the tool Full supplier? Page 388 of 450
ReqMan v2.0
Full Full Full Full Full Via website and on 3rd party sites. Online demos are available upon request via WebEx. Specialized classes can also be prepared. Available globally but in most instances remote classes are much more price efficient. Stakeholder contribution: No training necessary. Profecient administration 1-2 days. N/A. The platform is delivered as Software-as-a-Service (SaaS) on a multi-tenant architechture. The entire ReqMan product and platform are available free of charge. Why is ReqMan free? See http://www.requirementone.com/ReqMan_IsFreeWhatIsThe Catch.aspx. Full support for the Tender Management process which is an integral part of the ReqMan platform. Access to the tool via Software-as-a-Service (SaaS) on a multi-tenant architechture. Free community developed requirements are available at www.wikirequirements.com. The ReqMan platform is template driven and configurable at all levels from the requirement- to the project level.

12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
N/A
Page 389 of 450
Reqtify v2010-1A


Full Powerfull requirement capture feature based on PERL regular expression element extraction. Explicit rule checker for firest level of requirement syntaxic and fomarlism anaylsis. Tagger Plug-in to automate requirement identafication & capture from document. Requirement Snapshot creation and full changes analysis as new requirements, changed requirements, and deleted ones. Comparaison between older and new requirement description text as attributes values. Documents hierarchy changes can also be managed (Chapters position, model hierarchy, code structure...) Dedicated Macro are available for specific format to identify and capture automatically requirements. Specifc analysis types can be created to automatically capture requirement management elements. Tagger feature give the capability to highlight text from inuts documents and to add PUID , specifca fromalism and capture requiremetns in Reqtify. Tagger tool Tagger tool Reqtify has the ability to update targeted tools (UML, Design and/or Verification tools). You can use Reqtify API to launch those operations in Batch mode as well.
Full
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. 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
Full Full Full
1.6. Requirement classification: Does the tool have the ability to Tagger option is able to create and specifcy attributes Full classify/categorize requirements during identification values attached to each requirements. 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. Page 390 of 450
Reqtify v2010-1A
Full Reqtify is able to capture diagrams from all the interfaced tools and can represent (Text, Rich text or SysML) and also from modeling tools able to capture model Reqtify is able to represent all the system structure by capturing all the hierarchy on systems elements (Specification, Design, Code, Test )

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. 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
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 Reqtify will represent all the High Level Requirements Full derive/create additional requirements and link between them such as adn the refinement in several Low Level requirements requirement to requirement, or requirement to text (representing trade studies) and Derived requirement as well with specific to derived requirements. attributes and corevarge links between all of them (Refine, Verfify, Trace, Partial Coverage, UserChoice) 3.2. Allocation of performance requirements to system elements(weight, risk, Reqtify will kink together all the requirements together Full cost, etc.): The ability to link performance requirements to system elements and will refine with traceability links HLR or SLR such such as weight, cost, throughput, etc. This also includes the ability to allocate as Marketing Requirements/Customer portions of that performance requirement to system elements. Requirements/EndUser Requirements to low level requirements. 3.3. Bi-directional requirement linking to system elements: The linking of Reqtify is fully compliant with the highest quality Full requirements to system elements can be accomplished from either end of the requirements for managing Requirement in a bilink--from the implementation back to the requirement or from the requirement directionnal approach to prove first that we are fully down to the system element. covering requirement and not more than the ones that has been specified (Top-Down and Bottom Up Coverage and Impact Analysis). 3.4. Capture of allocation rationale, accountability, test/validation, criticality, All those informations will be added with attributes Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the that will be allocated to requriement and traceability ability to attach rationale, assignments, criticality, test/validation and many other data. Reqtify will check the consistancy of the issues to the requirement, allocation, and the system element to which a different information with a powerfull customizable requirement is linked. rule checker. 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.
Page 391 of 450
Reqtify v2010-1A
Full Reqtify is offering different views for requriement coverage links and will highlight the global dependency/Traceability graph for each of them. The Rule checked will highlight you all the inconsistencies on your project such as uncovered requirements/Not Unique Ids/ reference to unknown requirements, traceability graph violation ... more than 20 rules by default. Rule Checke is fully customizable to fully comply with your existing process and quality rules. Reqtify give you full coverage and impact graph in a bi-directionnal way. You can add comment on links, requirements all the elements directly in the tool or you can link justification from any sources (Word,Excel, DoorsWhatever) to a Reqtify element. Reqtify is able to manage several configuration of requirements throw an intelligent variant handling depending on different system configuration. (i.e. System Configuration for JP/US/EU)

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. 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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Full
Full
Full
Full
Reqtify will capture information from all the soruces that coudl be accesses by each user with his specifc user rights. Reqtify will provide a summary on changes and an history on changes data for each
Full
You can automatically (by defining Millestones) or manually specifiying baselines (snapshots). You will obtain history on requirements between snapshot and You can specify user rights on project edition and specify project and sub-project for creating spe
Full
Page 392 of 450
Reqtify v2010-1A
Full Reqtify is able to generate automatically all the evidences for Reqtify is able to check requirement consistency by doing syntaxic anaylsis on specific string form and/or used words. Reqtify is able to generate diagrams in output documents (Excel, Word, PDF, HTML, Framemaker). Reqtify provides by default a set of template for automatic Document Genration. It has also

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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full
Full
Full
Full Full
The document template editor gives the capability to see exactly the structure and the adata that will be genrerated as an output of Reqtify. Users are able to add status information with Attibutes/Comment/Marks Reqtify provides metrics to measure compliance with all the requirements categories.
Reqtify can generate automatically a document on Requirement Status and/or review with all the added information. 6.6.3. Other ad hoc query's and searches: The requirements management tool Reqtify provides a search option to find any kind of Full should support ad hoc query's and searches per the user's discretion. elements 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 Reqtify is analysing all inputs changes that will be Full support a team of engineers reviewing, marking up, and commenting on added in a concurrent manner by all the stakeholders. requirements or implementation alternatives. Reqtify give a full concurrent access for adding comments, marks, review attributes. Full
Page 393 of 450
Reqtify v2010-1A
Full Reqtify is able to give different viewpoint depending on the different millestone. He is abe to b elink to Change request tool throw is Reviewer plug-in following the approval cycle on corrective actions.

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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to?
Full
Full
Our solution is the leader on the market for exhchanging requirement between Requirement definition envrionment and both design and verification workbenches We have more than 60 interfaces to other tools such as Requirement Mangement tools like DOORS, RequisitePro, CaliberRM, Slate, Design/CAD tools (Simulink/Stateflow/Statemate/Scade/Rhapsody/ARTi SANStudio/Rose/HDLDesigner/EnterpriseArchitect) , CM Tools (PVCS, Dimension, CVS, Subervison, Clearcase...), IDE/Code(VisualC++, UltraEdit, Eclipse JDT & CDT, Vhdl, Verilog, C, C++, Java...) Testing Environment (TestStand/TestDirector/QualityCenter/RTRT/TestBe d/Cantata++...).(Ask for the full list by sending an email to reqtify@tni-software.com) Most of the tools that are connected with reqtify can be accessed in a read/Write mode to both capture and create requirement management information (Requirements, Attributes, Traceability data, ) The tool is able to connect standard Database such as MySQL, PostGre, Access ODBC, Oracle,and Propriatary Database orineted tools (Ask for the full list by sending an email to reqtify@tni-software.com)
Full
Full
Page 394 of 450
Reqtify v2010-1A
Full Reqtify information capture process is based on the powerfull ans well know PERL Regular Expression. You can automatically import data from ASCII(Test) and/or XML/HTML representation. XML, HTML, RIF. This is one of the main capabiity of the tool. To be able to access locally and/or remotelly severals tools (RM, CM, PLM, CRM, CAD, TT, IDE). After importation data from different sources, Reqtify will be able to give you the full differencies in term of changed/modified, deleted, created on data.

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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users?
Full Full
Full
Full
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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?
Full Full
The tool can be user in a concurrent access mode. As soon as a user is editing an element other have a read only access and will be informed as soon as they can take the edition rights. Windows NT, 2000, XP, VISTA/LINUX/SOLARIS 2.7+/HP-UX/CITRIX Propriatary binary files that can be exported to exchange format as RIF/XML/RTF/CSV
Full Full Full Full
32Mbytes Pentium+ (Low CPU requirments and hardware configuration requirements) 100Mbytes Yes, moreover the user will have the view of the coverae and the impact anaylsis on this requirement Yes full synchonization between views (Coverage mode, impact analysis view, graphical view, management view
10.2. Simultaneous update of open views: If the tool allows for multiple Full windows/views into the tool--does a change in one view automatically reflect in all other views? Page 395 of 450
Reqtify v2010-1A
Full Tracebility links creation, Attrbutes creation and edition, requirement text additon , Comments on elements. As a result an XML file is created that is containing all the added informations Reqtify is a Microsoft Windows application following the look&feel of standard Microsoft applications. Scripting lanaguage fro GUI, interface, converters, batch mode on all Reqtify features. The most opened tool on the market. Planned Yes Standards : ISO26262, DO178b, DO254, MoDaF/DoDaF, IEC61508, CMMI, AUTOSAR, EN50128, SPICE. Requirement Exchange format : XML/RIF/RTF/HTML/CSV... Design Standard : SysML, UML, Reqtify has a 90-day warranty. We also offer an Annual Maintenance Program that provides free software upgrades and tool operational support. FlexLM license management (Floating, Nodelock, User Based, Borrowing) Maintenance give you free access to new Reqtify releases exept new Plug-ins or new product based on Reqtify technology. Average release number per year is 2. All Documentation available for tool usage , installation , cutomization and specific documents fro Plug-ins and interfaces. www.reqtify.com support@geensoft.com Reqtify User Group

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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.?
Full
Full
None Full N/A
Full
12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
Full Full
Full
12.5. Provide Internet Web page location for company/tool info Full 12.6. Phone support: What type of phone support is available from the tool Full supplier? 12.7 Support User's Group Full 13. Training Page 396 of 450
Reqtify v2010-1A
Full User Training : 1 Day Reqtify Introduction Requirement Management: Key Notions Reqtify analysis results My First Project: Traceability analysis, Change Detections Multi-Level analysis: Impact analysis, Filters. Report Generation Typical use cases Reqtify files ========================================= ============================= Advanced Training : 1 Day Reqtify Architecture Analysis type customization PERL Regular Expressions Report Editor Data Model Internal Language Analysis Rules Exercises Specific Interfaces

13.1 Tool specific training classes
13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full Full Full N/A
YES and Intersite training as well 1 Day 1 Hour SysML - Requirement Exchange between OEM/Suppliers - requirement review management
Page 397 of 450
Requirements Manager ReMa



Full Using Import features, requirements can be imported from existing documents like ReMa template, Word, Rich Text Format (RTF), Text etc. It can also import requirements from Telelogic DOORS. ReMa provides option for user to update the existing requirements while importing from documents. Requirements are imported from Word, Text ,RTF and ReMa templates. Import from Word can capture requirements from Table of Contents or from Paragraphs No Comments
Partial Partial
None
Full Full Full
Requirements can be created directly by the user ReMa can import requirements from various formats of files. Allows importing of requirements from various documents and from Telelogic Doors
Requirements can be classified with user defined requirement types and attributes. Document types are also supported for classifying of requirements 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 Traceability Tree and Matrix views shows the relationship Full system implementation (such as architecture, functional decomposition, WBS, between requirements and their implementation. Graph etc.) and display them graphically such that requirements can be linked to them. view gives a brief overview of the system requirements Full 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 requirements can be imported into ReMa and links can be established between imported requirements and existing requirements
Page 398 of 450

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 1.Allocate requirements to system components. Full derive/create additional requirements and link between them such as 2.Create child requirements. requirement to requirement, or requirement to text (representing trade studies) 3.Link Requirements to other files in CVS and OLE objects. to derived requirements. A single requirement can be split into many or many requirements can be merged to form a single requirement. Traceability is established between derived requirements and the source requirement 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. Full User defined attributes can be used to allocate requirements to system elements
Full
Linking of requirements can be done in both ways i.e. from implementation to requirement and from requirement to the system implementation. Inconsistencies are taken care of by having checks for duplicate and circular links. Requirements can be associated with files in Win CVS Allocation rationale, accountability, test/Validation , criticality issues can be captured using user defined attributes, traceability links and change control management system. All the test/validation process shall be recorded in history information for each requirement
Full
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 ReMa flags the orphaned links as "suspected links". It also Full allow the user to identify inconsistencies such as unlinked requirements or provides flexibility to query for linked and non linked system elements (orphans). requirements. Re-association of files from CVS server linked to requirements is provided so that requirements are linked to the latest version of files Page 399 of 450

Full Links are visible directly in ReMa document by simple click of a mouse. Traceability Matrix and Tree views shows unlimited no of link traversals in the same page. Links are also visible in Exported Word format of the documents. Verification of requirements is done through traceability links and attributes. Requirement comments review and Generation of Revision/History reports is also supported

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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Full
None
No Comments
Full
ReMa maintains history of each requirement. This includes version number, date, time and owner. It automatically updates when the changes are made. Users can compare two different versions of an object and view the differences between them. The Change Control Management System allows users to propose changes to requirements ReMa provides creating, copying, reverting and deleting baselines. It also supports comparison of two baselines
Full
Full
ReMa provides different user roles with different permissions for project, packages and documents. Permissions can be changed depending on the user roles in project, packages or documents. Different User views can be allocated to users. User view permissions are checked to allow the user to view or work on the project data
6. Documents and other output media Page 400 of 450

Full ReMa provides exporting of requirements document in various formats RTF, Word, Excel, CSV and ReMa template ReMa provides spell check facility using US dictionary and also customized dictionary. ReMa supports graphical representation of project data through 2-Dimensional and 3-Dimensional Pie Charts, Bar graphs, Line Graphs and Step Graphs ReMa allows users to provide headers and footers for document print. It supports printing of graphs, traceability matrix etc. Printing in Word format provides an option for using Word templates ReMa allows users to preview the requirement document before printing The status information required can be filtered into a view and can be exported or printed. An overall status field shows whether the requirements are closed or open Accomplished through customized status attributes

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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements
Full
Full
Full
Full Full
Full
Requirements query facility can be used to get traceability information and requirements can be filtered based on their overall status 6.6.3. Other ad hoc query's and searches: The requirements management tool ReMa allows querying ,search and filtering on attributes, Full should support ad hoc query's and searches per the user's discretion. requirement identifiers, substrings, keywords, links, status 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 Multiple users can have write access to same document in Full support a team of engineers reviewing, marking up, and commenting on shared mode. The Change Control management system requirements or implementation alternatives. allows proposed changes from multiple users to be reviewed and applied. Comments given by multiple users can also be reviewed and closed. Web based implementation of ReMa is supported Full Page 401 of 450

Full ReMa provides different user roles with different permissions for project, packages and documents. Permissions can be changed depending on the user role in the project, package or documents. ReMa provides a specific process for submission of proposed changes. Specified users review them . Accepted changes are applied in the document automatically. User-views provide restricted access to view a document with the help of userview permissions ReMa has ability to communicate with Telelogic DOORS . The document is exported into some intermediate files. These files are then imported to Doors using Doors extension language (DXL). Also exported documents from Doors can be imported to ReMa ReMa provides interface with the following tools:1.Microsoft Word. 2. Microsoft Excel 3.Telelogic Doors 4.Any tool that accepts data in CSV format No Comments

Full
8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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
None
None
No Comments
Full
ReMa can import data from various file formats like Text, Rich text format, Word, ReMa Template
None Partial Full
No Comments Projects can be accessed from different installations. Data can be exported and imported between different installations
Page 402 of 450

None No Comments

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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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?
ReMa supports multiple concurrent users Win 9x, Win NT/2000/XP/2003/Vista Unique Database
Server- 128 MB or more , Client -256 MB or more Server-IBM PC Compatibles, PA-RISC, Client -IBM PC Compatibles Server - Requires 100 MB or more, Client-500 MB or more
Full
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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
Full
ReMa allows exporting of document and working on other data at the same time. ReMacyber, the web based implementation allows document to be opened in multiple windows Document and requirement reloading is supported. ReMa Views refresh whenever requirements are changed No Comments Microsoft ReMa supports document templates to be assigned with each document eliminating the user from adding requirements manually .Several Keyboard shortcuts are provided to automate tasks ReMaCyber can be used as an interface to database through internet Requirement description provides Undo option.
None Full Full
Partial Partial Page 403 of 450

N/A No Comments

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Full Full Full Full Full None None None None Full
The tool supports maintenance/ customer support for one year. The warranty has to be renewed every year Floating License managed by License Manager Software updates are released every 3 to 6 months usually. Help file, tutor, and user guide are hosted in ReMa website. Support is also provided through e-mail. http://www.rema-soft.com No support through phone. No Comments No Comments No Comments ReMa's tutor and Help documents provide extensive information with the help of which users can become proficient in using the tool in just 1 or 2 days Installation requires running of simple executable and takes 5 mins in normal circumstances. Installation guide is provided to help in the installation process.
Full
N/A
Page 404 of 450
RTIME v5


Partial Using MindManager as a bridge we can pull documents from Word into the MindMap for analysis and then into RTIME for future auditing, tracking, etc. Once requirements are in RTIME, versions of the requirements can be compared using a requirement history report. If using MindManager as a front end capture tool, two maps can be compared. Using MindManager as a bridge we can pull documents from Word into the MindMap for analysis and then into RTIME for future auditing, tracking, etc.
Full
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. 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?"
Partial
None
1.4. Manual requirement identification: A manual means of identifying or Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Excel, Word, MindManager Integration Full from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Full to update existing linked documents from new/changed versions of the source documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Full classify/categorize requirements during identification 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 Full system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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
Page 405 of 450
RTIME v5
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 Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements (weight, risk, Full 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 Full 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, The requirement is linked (via the database) to other Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the elements including tests, issues, projects tasks and assets. ability to attach rationale, assignments, criticality, test/validation and many other Custom field can also enhance tracking requirement issues to the requirement, allocation, and the system element to which a attributes. requirement is linked. 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 Tasks, Tests, Assets, Other Requirements, Custom Full allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e.. follow the Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the Requirements have a status attribute and are linked to tests Full life of the project, the requirement management tool will be used to verify that and tasks. Accountability for the completion if the the requirements have been met. The tool should provide the ability to requirement including the tests executed are all linked and document that the requirement was fulfilled, how it was done, and who was tracked. responsible.
Page 406 of 450
RTIME v5
Full

Full
Full
Full
6. Documents and other output media 6.1. Standard specification output (if so what kind): The requirements Full management tool should output documentation in various military/commercial standard formats (490, 2167, etc.). 6.2. Quality and consistency checking (spell, data dictionary): The tool should Full also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Partial management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements Full management tool. Page 407 of 450
The output includes PDF, Word directly from the database and through MindManager many formats of the requirements can be produced.
Through MindManager Integration
RTIME v5
6.6.1. Technical Performance Measurement status accounting: Status current Full technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Full compliance/non-compliance to various requirements 6.6.3. Other ad hoc query's and searches: The requirements management tool All searches are also exportable to Excel Full should support ad hoc query's and searches per the user's discretion. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Full 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Partial ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management HP Quality Center, Bug Tracking Tools, Others Partial tool interface with or talk to? 8.1.2. External Applications Program Interface available: To support the wide Partial 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). 8.1.3. Support Open database system (standard query access): Does the tool Full support Open Database standards such as standard query languages or exchange formats? 8.1.4. Import of existing data from various standard file formats?______: Does From Excel, Word Via MindManager Full 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) None 8.2. Intra-tool communications Page 408 of 450
RTIME v5
None

8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards
None
Full Full Full Full Full Full Full Full Windows Standard Microsoft SQL Server The software can be delivered on a pre-built appliance or installed on customers own hardware. Minimum No response provided. Minimum Running reports, searching, chatting are among the features that can be done simultaneously to viewing requirements, tasks, etc. Usually a refresh is required. This can be done via mouse click or F5 Through MindManager Integration No response provided. No response provided.
Partial
Partial
Partial
A subset of features are browser based No response provided.
Page 409 of 450
RTIME v5
N/A No response provided.

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.?
Full Full Full We provide full upgrades with purchase of maintenance. Point release are automatically distributed via automatic detection and download. Major releases are released via download. RTIME has a complete on-line help system, tutorial guides and video help www.qavantage.com 1-800-476-7017
Full Full Full Partial Full Full Full
1/2 day web course and 1 - 2 workshop programs are available yes For tool proficiency in terms of product use, 4 hours. For best practice, methodology optimization 2 day workshop. With Appliance delivery 0 time for installation and 4 hours basic product training We offer an end-to-end tool for requirements capture through to delivery. This includes a unique capture method using MindMapping as a front end and or MS Word analysis and extraction tool, prioritization and trade-off analysis capabilities, complete task to requirement traceability for project management, quality management capabilities for ensured test coverage and reporting for all stakeholders.
Full
N/A
Page 410 of 450
Teamcenter Requirements v8
Date of Submission: 8-Nov-08


Full Teamcenter uses Microsoft Word as its standard document import/export and editor. All capabilities/features of Word are available from Teamcenter's Requirements Management solution. Teamcenter has access to Microsoft Word's change tracking/comparison features for highlighting and tracking changes (i.e. changes captured in Word are available/visible in Teamcenter). In addition, different versions of different requirements documents can be compared using Teamcenter's BOM Compare feature. Requirements are automatically parsed based on structure or keywords on document import, creating an equivalent structure inside of Teamcenter. This structure can be managed, configured, etc. like other Bill of Material (BOM) structures inside of Teamcenter. . Requirements can be identified in an interactive/semi-automatic way.
Full
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. 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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification
Full
Full
Full Full
Requirements can be created manually. Teamcenter's Requirements Management solution includes full web-addressable API that supports batch-mode import/export of requirements. Requirements documents may be imported and compared or using Word's document comparison utilities, only those changed portions of a document can be imported. Requirements may be classified by a number of means in Teamcenter including: -folders, sub-typing, attributes, relationships, etc.
Partial
Full
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. Teamcenter supports graphical capture of system structures. Full 2.1. Graphically capture systems structure: Can the tool graphically capture These structures are fully configurable allowing users to configure system implementation (such as architecture, functional decomposition, WBS, different versions of the same architecture, functions, WBS, etc. etc.) and display them graphically such that requirements can be linked to them. Page 411 of 450
Full Teamcenter supports textural capture of systems structures through its outliner feature.

3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements. Requirements may be derived/linked to other requirements. Full 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. Teamcenter includes a calculatable numeric property associated Full 3.2. Allocation of performance requirements to system elements (weight, risk, with requirement and system decompositions. This allows cost, etc.): The ability to link performance requirements to system elements quantifiable requirements to be allocated to children and flowsuch as weight, cost, throughput, etc. This also includes the ability to allocate down and roll-up through a hierarchy. Additionally, Teamcenter portions of that performance requirement to system elements.
includes an Excel-live integration that allows requirements and their properties to be edited with Excel. This gives Teamcenter access to all of Excel's equation/calculation features.
Links in Teamcenter are bi-directional. Requirements may be Full 3.3. Bi-directional requirement linking to system elements: The linking of linked to other requirements or system elements (such as requirements to system elements can be accomplished from either end of the functions, etc.) link--from the implementation back to the requirement or from the requirement down to the system element. Teamcenter allows users to capture rationale through its yellow Full 3.4. Capture of allocation rationale, accountability, test/validation, criticality, sticky notes"" feature. Notes may be attached to any object and issues, etc.--if so how and what mechanism does it use?: Also critical, is the can contain any appropriate information. Teamcenter uses ability to attach rationale, assignments, criticality, test/validation and many other Microsoft Word to capture/edit Note information. issues to the requirement, allocation, and the system element to which a requirement is linked. 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. Reports can report on connections among requirements including Full 4.1. Identify inconsistencies (orphans,...if so what kind of...): The tool should the lack of links (orphans) or types of links. allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). Links, once created, can be followed/reported on manually or via Full 4.2. Visibility into existing links from source to implementation--i.e.. follow the Teamcenter's report facility. 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.
Page 412 of 450
Full Verification is tracked through Teamcenter note and properties features. Notes and properties are completely addressable by API, allowing for real-time data acquisition/test set integration if needed (allowing requirements to be tied to the means of validating them) Teamcenter numeric properties fill this need by allowing individual numeric values to reference other values in calculations. Additionally, because Excel is integrated with Teamcenter, Teamcenter has access to Excel's math/calculation capabilities.

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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
Full
Full
History of who changed what when where is maintained.
Full
Requirement versioning is supported including branching and requirement variants (per CMII standard)
Full
Standard read, write, delete access on all objects is available. Access control is available based on users or objects.
Full
Teamcenter uses Microsoft Word as its standard document import/export mechanism. Templates are applied on export allowing users to output in standard specification formats. Teamcenter uses Word as its direct requirement editor. As such, users have access to all of word's consistency, grammar, spelling, and other checkers. Information can be output in Word, Excel, Visio which in turn can be embedded/linked into PowerPoint presentations. In addition, information can be sent directly to PowerPoint for output (i.e. one requirement per slide)
Full
Partial
Page 413 of 450
Full Teamcenter supports embedded field codes including table numbering, table of content generation. In addition, with Teamcenter 8, Siemens introduced a "Living document" where the output document is the interface to Teamcenter. Changing the document, changes the requirement other in objects in Teamcenter. Teamcenter uses Word for import/export and requirement editing. Word includes a WYSIWYG editing/viewing capability that is tied directly to database objects. Teamcenter includes status reporting based on property (approval status, due dates, etc.), relationships (all things needed to be verified for this requirement) Teamcenter includes calculated numeric properties, when combined with Excel-live allows numeric properties to be the results of calculations in Excel. These values can be compared against requirement values. Teamcenter includes a reporting/search mechanism that can match on properties, relationships, or text/numeric values. Teamcenter includes an Outlook"" type advanced searching capabilities that can match on requirements properties or text. The search produces a ""live"" window which can be manipulated.

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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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
Full
Full
Full
Full
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. Teamcenter allows multiple users to review, markup, and Full 7.1. Support of concurrent review, markup, and comment: The tool should comment on requirements, functions, and other Teamcenter support a team of engineers reviewing, marking up, and commenting on objects. Additionally, Teamcenter allows standard OLE objects to requirements or implementation alternatives.
be included in requirements as markup such as chat sessions.
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. 8. Interfaces to Other Tools
Full
Teamcenter allows access controls to be set by user, by object definition, or by individual objects. Additionally, access may be mapped to individual or groups of users (user groups) or by role.
Page 414 of 450
Full Teamcenter has direct interfaces with a number of domain tools including CAD, EE, CAE, and other. In addition it uses standard data exchange mechanisms including XML, DCOM/OLE, AP-233, as well as TCP/IP Teamcenter support open-data exchange with a variety of tools including Microsoft Office Suite, products across the Teamcenter portfolio, and others. Teamcenter also supports STEP data exchange including AP-233 and others. Fully web addressable SOA API, Java Web-API, C#, HTTP, and SOAP.

8.1. Inter-tool communications: Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to?
Full
Full
Full
Teamcenter uses standard, commercial database technology--as such it supports SQL, ODBC, and other standard query access languages. ASCII CSV, STEP, and other formats are supported, importing can either create new objects or overwrite/update existing objects.
Full
Full Full
XML, AP-233, CSV and other data exchange standards are supported. Each object in Teamcenter is web-addressable. As such, any standard web-based application can exchange information with Teamcenter including other Teamcenter members. Teamcenter was built for always on"" connections"", but the database supports ""intermittent"" connections and synchronization. Teamcenter avoids the consistency/comparison problem by automatically keeping everyone in sync. However, methods are available for disconnected data sets compare/update.
8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users?
Full
Full
Full
Supports thousands of simultaneous users via standard web browsers.
Page 415 of 450
Full Supports mixing environments since Teamcenter uses standard web browsers. Windows, Unix, Linux, etc. Recommend Unix or PC as database servers. Teamcenter uses standard database technologies including Oracle, SQL Server, etc. Standard server configurations are sufficient. Subject to enterprise deployment options. Current standard CPU's are sufficient. Recommend multiple CPU's when scaling as code is multi-threaded to support them. Subject to enterprise deployment options. Supports many people working on the same database at the same time. Allows a single user to have multiple windows up at the same time looking at the same database. All viewable windows are synchronized

9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements
Full Full Full Full
9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface?
Full Full
Full
Full Full Partial.
User interface is interactive--uses standard input/output devices including keyboard, mice, etc. Uses Microsoft Standard look & feel (in fact uses Microsoft Word and Excel as input windows). Although Teamcenter does not support macro recording and playback, Teamcenter is fully configurable such that many of these macro's are not required (i.e. which rules apply in certain situations, what can be linked to what, etc.). Multiple user interfaces are available for Teamcenter depending on the role of the user. They include web client, rich client, Excel, Word, .jsp's, etc. Since Teamcenter is an enterprise-wide RM application, once changes are committed to the database, they are not undoable. Before that, we allow undoing of changes as the interface (i.e. Word, Excel's innate ability to undo).
Full
Partial
11. Standards
Page 416 of 450
N/A Design Standards--IEEE 1220, EIA-632,...Communication standards TCP/IP, Ethernet,...Development standards...CMMI, SEI, ISO9003,...Data Exchange standards...XML, ISO STEP,...UI Standards...Microsoft, Java II,...

11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training
Standard 90 day. Concurrent, Named user licensing. Twice yearly major updates available to all maintenance customers Context-sensitive online help, linked to user manuals. Currently available at http://www.siemens.com/plm 800 phone line support available User groups meet regionally and at annual event-www.plmworld.org Available in 1-3 day courses on different aspects of TcRM Yes. 1 day for tool users, 3 days for tool customizers, 1/2 day for administrators. Software automatically installs on client when user first logs in. Server installation requires a privileged users--takes
Full Full Full Full
Page 417 of 450
N/A Requirements in and of themselves don't do anything for you. They need to go somewhere, be connected to something to have an impact. Teamcenter's Requirements Management allows requirements to be tied into the entire product lifecycle allowing them to influence requirements as design is happening. This means you can build requirement compliance into products as they are developing versus test and integrate compliance in later. Teamcenter's Requirements Management can deliver requirements to the lifecycle through the other Teamcenter members including change, workflow, configuration management, project management, CAE analysis, manufacturing, Maintenance/Repair/Overhaul, etc.

Page 418 of 450
TraceCloud
Date of Submission:
12-Oct-09

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. 1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. 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
Partial 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.
Full
You can store multiple copies of the documents at different events as a Document Template Supports creating requirements from Word using the following mechanisms : a) Identify based on keywords b)Identify based on Word Character Styles c)Identify based on user selection of text d) Identify based on pre-formatted Tables. The last option is powerful, because it lets the user identify not only the requirement, but also the associated collateral like attributes, folder location, traceability at the time of requirement creation. You can select a section of text and mark it as a Requirement, and this can be turned into a Requirement upon upload.
Full Full You can use either Excel or Word to achieve this. That is, you can create all your Requirements, attributes, traceability information using Excel and simply upload them to create new requirements or update existing ones. Using Excel, you can update existing Requirement text /description and attributes
Full
Using Excel, or Word tables, you can set attributes , or create folders of the correct Requirement Type or store then in correct folder at the time of Requirement creation. 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. Full Page 419 of 450
TraceCloud


Full Graphically see the relationship between Requirements. In a Single Requirement mode, you can see one level up and one level down of the relationship between different Requirement Types. In the Trace Tree mode, you can traverse and view arbitrary depths of the tree to see the graphical relationship. Every Requirement has textual mapping of other Requirements its related to.
Full
3. Requirements flow down: 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 complete traceability is provided Full derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, you can add custom attributes to any Requirement Full cost, etc.): The ability to link performance requirements to system elements Type to track values like weight, cost, throughput such as weight, cost, throughput, etc. This also includes the ability to allocate related to the Requirement portions of that performance requirement to system elements. 3.3. Bi-directional requirement linking to system elements: The linking of You can do Trace To and Trace From for any Full requirements to system elements can be accomplished from either end of the Requirement to / from any Requirement 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, Custom Attributes and External URL can be Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the leveraged for this. 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. 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 You can build your own reports or leverage existing Full allow the user to identify inconsistencies such as unlinked requirements or dashboards system elements (orphans). Page 420 of 450
TraceCloud

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. 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. 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). 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. 5.2. Baseline/Version control: At various times the requirements will need to be baseline (saved and locked away). The requirements management tool should support this along with the ability to compare and contrast between various baselines. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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 Trace Trees are powerful visual aids that track this behavior Built in % complete and Burn down charts help track these numbers
Full
Full
Ability to roll up metrics from a Folder, Owner, Baseline, Release or Project perspective.
Full
Requirement Chang log captures any change to this Requirement
Full
It also comes with Baseline Dashboards , which is a collection of reports, metrics and trend charts that report on Requirements that comprise this baseline.
Full
Partial
You can generate Word, PDF and Excel reports . You can also embed requirements into Existing word documents and re-generate your word documents with the collateral from your Requirements on the fly.
None
Page 421 of 450
TraceCloud

6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements

Full Extensive Flash based Trend graphs that show the Completion, Traceability and Approval reports. You can embed requirements into pre-defined word templates and generate word documents on the fly.
Full
Full Full Full
With the PDF / HTML output format, you can view your generated document.
Trend charts that track burn down, traceability holes etc
Dangling, Orphan, Suspect Upstream etc.. Are trended at Folder, User, Baseline, Release and Project levels. 6.6.3. Other ad hoc query's and searches: The requirements management tool support Google like free text search and custom Full should support ad hoc query's and searches per the user's discretion. attribute / comment search. 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 Full support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Folder level access control to create, read, update, Full must be tempered by multi-level access control (i.e. the ability to protect things delete and trace to requirements 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the SOAP based XML over HTTP API Full ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Full tool interface with or talk to? Full Page 422 of 450
TraceCloud


Full
Full
Build on MYQL, so any user with SQL skills can query it. Full Excel support.
Full
Partial Full Full
Once converted to Excel or Word , data can be imported. Export can happen using SOAP XML SOAP based XML over HTTP API Designed with multi environment setup in mind.
Full
Full Full Browser based SAAS version, so works on any browser. However, for On Premises model, it will run on Windows only (because we provide Rich Microsoft Word / Excel integration, we use some packages that work only on Windows). Uses Free MySQL database
9.3. Commercial vs. unique database: Does the tool use a proprietary or Full commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration N/A requirements: 9.4.1. Memory requirements N/A 9.4.2. CPU requirements N/A 9.4.3. Disk space requirements N/A 10. User Interfaces Page 423 of 450
TraceCloud

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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support

Full Full Yes
Full Full None
Full Full
Any Class 1 browser (Firefox, IE 6,7,8, Safari, Chrome) The tool provides a Soft Delete / Restore capability and logs any change to the Requirement . Going forward we plan in implement an ability to revert to a previous version of the Requirement.
N/A
Full No Full
In the SAAS model, you pay on a per user / pre month basis.
12.4. On-line help: Are the users manuals on-line, is there on-line help with the Full tool? 12.5. Provide Internet Web page location for company/tool info Full 12.6. Phone support: What type of phone support is available from the tool Partial supplier? 12.7 Support User's Group None Page 424 of 450
Quarterly Release cycles, and upgrades are free for SAAS customers. For On Premises customers with maintenance contract, upgrades are free. Task Based Videos are available on line.
Only available for On Premises customers with service contract. But being built up
TraceCloud

13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?

Full Full Full Full N/A Tele Conferencing available
Page 425 of 450
WTDN
Date of Submission: 18-Feb-10


Partial WTDN accepts typed user input of ideas from any source and is meant to be a central repository for younger organization with ideas in Excel, Word, Post-It notes, and legal pads, not to mention PM brains. Once an idea is stored in WTDN, each new SAVE of the record becomes the current snapshot, while all prior snapshots are available in history.
None
None
None
Full None None
WTDN provides a user interface for entering ideas into the system interactively. On our future ideas list pending priority shift. Idea records may have multiple links to remote resources via stored URLs. Typical usage is to tie an idea record to supporting documents elsewhere in the organization such as webpages, sharepoint, or other libraries.
Ideas may be categorized by product line, type, purpose, source, target, responsibility, phasing method, scoring method, and status. 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 WTDN is not a system design/capture tool. It is an idea None system implementation (such as architecture, functional decomposition, WBS, capture application with structure and central storage. etc.) and display them graphically such that requirements can be linked to them. Full
Page 426 of 450
WTDN
Full

WTDN is primarily a text-based, list application to store, score, and report (and select) ideas for action. Ideas may be linked to outside resources. Likewise, it is possible to generate URLs linking outside resources to any given WTDN idea record. 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 On our future ideas list pending priority shift. Specifically, None derive/create additional requirements and link between them such as this is for us in reference to peer-to-peer and/or parent/child requirement to requirement, or requirement to text (representing trade studies) relationships among multiple ideas. to derived requirements. 3.2. Allocation of performance requirements to system elements(weight, risk, Categorization of ideas by purpose can be selected (e.g. Partial cost, etc.): The ability to link performance requirements to system elements performance, feature, scalability, supportability, etc). The such as weight, cost, throughput, etc. This also includes the ability to allocate idea scoring methodology in WTDN may also be configured portions of that performance requirement to system elements. with custom templates to offer weighting to various aspects of ideas as appropriate. 3.3. Bi-directional requirement linking to system elements: The linking of None 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, WTDN offers text explanation fields for any supporting Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the arguments. Further, the WTDN scoring methodology ability to attach rationale, assignments, criticality, test/validation and many other specifically allows for valuation of ideas on a level playing issues to the requirement, allocation, and the system element to which a field with consistent questions and answers utilitized to requirement is linked. assure the user input produces valuable scores for prioritization. 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 Reporting with filters allows scanning for idea records that Partial allow the user to identify inconsistencies such as unlinked requirements or are missing user defined values. system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the On our future ideas list pending priority shift. Specifically, None links: With the requirement links in place, the user needs the ability to follow the this is for us in reference to peer-to-peer and/or parent/child links to see where they come from and where they go to. relationships among multiple ideas.
Page 427 of 450
WTDN
Full Idea records may be repeatedly updated with status changes, including comments and state flagging through 1012 well-understand states from conception to delivery. This is managed with WTDN's Phase State page and report format. WTDN as an idea management application captures concepts and valuations, along with estimate information. It is NOT meant to handle the budget-actual aspects, along with project management activities, of project management tools. WTDN is for Product Managers, upwind of development and execution. The WTDN database is completely non-destructive. That is to say every saved image of each idea is stored permanently and may be reviewed and accessed through a history report. Likewise, any historical snapshot can be saved as the current snapshot.

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. 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). 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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
None
Full
None
Full
WTDN allows 5 levels of access per instance: none, readonly, personal r/w, author, and admin. Multiple WTDN database and web server software instances may be used to further segregate users/communities. tab-delimited for speadsheet import
Partial
None
Partial
All web pages and report lists may be printed with good effect from popular browsers.
Page 428 of 450
WTDN
None Custom reporting may be accomplished by exporting to Excel templates.

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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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
via web browser print preview web browser; Excel optional
None
None Full
Advanced Reporting allows searches with wildcarded text fields, filters by well-defined fields, two-level sorting up front, selectable report formats, and for list reports, additional include/exclude/regenerate capability, as well as single column sorting. 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 Supports simultaneously multiple access to any idea record. Partial support a team of engineers reviewing, marking up, and commenting on In case of writeback, all writers will get their snapshots requirements or implementation alternatives. written, but last one in "wins", as most current. There is no record locking. If two users save an idea record that was opened from different historical iterations, there could be disjoint contents to be managed. However, WTDN is for Product Managers, who in fact DO work mostly as individuals, rather than like system engineers. 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. Partial Access control is defined by userid, not by idea record or family membership. There can be Author level users with full R/W capability to all ideas, Readonly users who may see but not modify, and Personal R/W users who may only see and modify their own records. Again, WTDN is for Product Managers who are a bit more siloed overall than systems engineers.
Page 429 of 450
WTDN
Partial WTDN lists are used to produce roadmaps and potential feature lists, which flow to other teams for execution. Excel exports are the typical solution for WTDN users to share approved ideas as projects for project managers, PMO, development teams, etc. Excel Product Management has not demonstrated a need for such an API to date.

8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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?
Partial None
Full
WTDN's database is a flat schema in MySQL, readily readable for user purposes. On our future ideas list pending priority shift.
None
None None None
A simple SQL statement could be written to sweep or update idea record data between instances, provided record numbers are auto-generated as unique in each database.
8.2.2. Consistency/comparison checking between same-tool datasets: Does None 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? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements: Page 430 of 450
Multiple, concurrent users. Linux/Apache or Windows/IIS are demonstrated. PHP 5.x required on web server. MySQL 5.x
WTDN
4gb dual-core, 2ghz or better 1gb Full Partial Yes, with multiple web browser windows. Multiple views are supported. Views are asynchronous from one another.

9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support
None WTDN's user interfaces are web-browser based, Windows agnostic. None
Full Partial
IE, Firefox, Chrome, Safari, Opera tested as supported. Single undo in browser based text fields. WTDN's history reviews can also take the record back to any point by resaving a previous snapshot as the new current image.
N/A
WTDN is not targeted for mil-spec but for civilian business product management purposes.
Full None Full
60 days no-fault return/refund on enterprise licenses; instant cancellation on hosted subscriptions Contractual license for enterprise seats; userid-based licensing for subscription based seats Enterprise licenses require annual maintenance/support agreement; subscription licenses include ongoing maintenance/support. Semi annual maintenance updates anticipated.
Page 431 of 450
WTDN
Full The Administration Guide and User Guide documents are accessible through the WTDN user interface as PDF documents that open in a browser window, parallel to the application window(s) that may be open. www.4sqsolutions.com Email support is available for enterprise and subscription users. Enterprise licensees may call support through a published support number. Not available yet as user community is very small. Yes. Yes. 2 hours for all users, 2 more hours for administrators Yes, for administrators with IT credentials.

12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Full Full
None Full Full Full Full N/A
Page 432 of 450
workspace.com RM


Partial We enable user to set meta data to requirements to sort and organize as required. Users can view and report on requirements historically and as they change over time. Keywords, structure, unique identifiers and meta-data used to parse requriements
Full Full
None
1.4. Manual requirement identification: A manual means of identifying or Complete support for authoring Full creating requirements. 1.5. Batch mode operation: A mechanism for inputting/identifying requirements Complete support for import from Microsoft Word Full from outside of the tool. 1.5.1. Batch-mode document/source-link update: Does the tool have the ability Requirements are maintained directly in the tool. They are None to update existing linked documents from new/changed versions of the source not maitained and updated outside the tool documents without having to re-establish traceability links. 1.6. Requirement classification: Does the tool have the ability to Import of requirements and associated meta-data captured Full classify/categorize requirements during identification 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 The tool can capture, store and manage graphical images. Partial system implementation (such as architecture, functional decomposition, WBS, etc.) and display them graphically such that requirements can be linked to 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
workspace.com RM
Full Requirements may be linked to other requirements or other artifacts in the system.

Full
Custom meta-data may be established and values assigned to requirements as needed
3.3. Bi-directional requirement linking to system elements: The linking of Full linking to other requirements or other system artifacts is Full requirements to system elements can be accomplished from either end of the supported. 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, Full support for assigning and customizing attributes to be Full issues, etc.--if so how and what mechanism does it use?: Also critical, is the assigned to requirements, as well as linking to other items. 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. 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 Filtering capabilities can isolate requirements based on Full allow the user to identify inconsistencies such as unlinked requirements or meta-data or the absence of particular values. system elements (orphans). 4.2. Visibility into existing links from source to implementation--i.e. follow the Links may be followed and traced as needed. Full 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. 4.3. Verification of requirement (was it done, how was done): Throughout the Status of requirements and graphical representation of that Full life of the project, the requirement management tool will be used to verify that status are actively tracked. 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. 4.4. Requirement performance verification from system elements (roll up of Reporting of actuals and variances is fully supported. Full 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). Page 434 of 450
workspace.com RM
Full Complete history of all changes to requriements is maintained.

Partial
Full
Access may be controlled by user and role, as well as restricted by activity such as, create, review, update, delete, approve Output to Word, Excel, PDF are supported
6. Documents and other output media 6.1. Standard specification output (if so what kind): The requirements Full management tool should output documentation in various military/commercial standard formats (490, 2167, etc.). 6.2. Quality and consistency checking (spell, data dictionary): The tool should Partial also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc. 6.3. Presentation output: Once the information is loaded, the requirements Full management tool should support the generation of presentation quality charts and graphs. 6.4. Custom output features and markings (user definable tables, figures, Full security markings..): The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to Full view the document on-screen in finished format. 6.6. Status reporting: Tool users need to status information in the requirements Full management tool. 6.6.1. Technical Performance Measurement status accounting: Status current Full technical performance of various allocated performance requirements and monitor progress towards goals. 6.6.2. Requirement progress/status reporting: Status reporting on current Full compliance/non-compliance to various requirements Page 435 of 450
Spell checking is supported.
Export to Word, Excel, PDF are supported for presentation purposes. This includes image and graphical element export support. Output includes all text, graphics, meta-data or attributes.
Full view of requirements is supported Status may be tracked and values may be customized. Users may assign custom attributes and values to requirements to track technical performance Users may assign custom attributes and values to requirements to track compliance/non-compliance
workspace.com RM
6.6.3. Other ad hoc query's and searches: The requirements management tool Full text search, filters and custom reporting enable users to Full should support ad hoc query's and searches per the user's discretion. easily perform ad hoc queries and search. 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 Users may both mark-up and comment on requirements at Partial support a team of engineers reviewing, marking up, and commenting on same time, but not contemporaneous, i.e., web meeting requirements or implementation alternatives. 7.2. Multi-level assignment/access control: Access by the team to the database Multi-level access control by user and role is supoprted. Full must be tempered by multi-level access control (i.e. the ability to protect things Requirements may also be locked. 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. 8. Interfaces to Other Tools 8.1. Inter-tool communications: Requirements management must have the Export to Word, Excel, PDF are supported. Partial ability to communicate requirements to other domain-specific design tools (CASE, EE, etc.). 8.1.1. Interfaces to other tools: What tools will your requirements management Export to Word, Excel, PDF are supported. Full tool interface with or talk to? 8.1.2. External Applications Program Interface available: To support the wide Programmable interfaces will be available in Summer 2009. None 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). 8.1.3. Support Open database system (standard query access): Does the tool The tool will support database queries through its defined None support Open Database standards such as standard query languages or web services apis. exchange formats? 8.1.4. Import of existing data from various standard file formats?______: Does Import of standard formats supported Full 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) None 8.2. Intra-tool communications None 8.2.1. Exchange of information between same tool, but different installations: The tool is a multi-tenant SaaS tool, so exchange of Partial Since the tool will be used at different sites and different projects, how does the information not required. tool exchange information between different tool installations or databases?
Page 436 of 450
workspace.com RM
Partial The tool is a multi-tenant SaaS tool, so exchange of information not required.

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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 9.4. Resource requirements: Please identify hardware/software configuration requirements:
Full Full Full Full
The tool supports both single and multiple concurrent users. The tool runs on all Operating Systems via virutualization The tool uses Oracle Enterprise To tool is offered as a SaaS hosted service, so only a browser is required. A virtual appliance is also available and minimum requirements are 2.5ghz Pentium4, 2GB RAM, 150GB Hard Disk. For Virtual Appliance 2GB For Virtual Appliance 2.5ghz PentiumIV For Virtual Appliance 150GB
9.4.1. Memory requirements Full 9.4.2. CPU requirements Full 9.4.3. Disk space requirements Full 10. User Interfaces 10.1. Doing one thing while you are looking at another: Does the user have the Full ability run a report and look at a requirement at the same time? 10.2. Simultaneous update of open views: If the tool allows for multiple Full windows/views into the tool--does a change in one view automatically reflect in all other views? 10.3. Interactive graphical input/control of data: Does the tool support graphical Partial input and manipulation of data? 10.4. Which window's standard do you follow?: If your tool supports a window's None standard, which one(s)? 10.5. Executable via scripts (recordable) or macros: Does the tool allow the None user to create and playback commands or macros that allow the user to automate various tedious tasks? 10.6 Web browser interface? Full 10.7 Edit Undo Function Support Full 11. Standards 11.1. Which military/commercial standards does your tool comply with--including N/A database standards, output document standards, exchange standards, display/graphics standards, etc.? 12. Support and Maintenance Page 437 of 450
Multiple browsers may be used to view multiple windows
Graphical input and output is supported. Graphical editing not supported.
CMMi support
workspace.com RM
Full Full Full Full Full Full Partial Partial None Full Full N/A Warranty of Fitness for a Particular Purpose

12.1. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)?
Upgrades are released several times a year. They are included in base subscription price. Online Solution Center and DemoCenter http://www.artifactsoftware.com/products/RequirementsManagement.html 10 hour per day phone support. 24 hour e-mail support. Online forum supported Online training courses available Recommended training time approximately 2 hours. Training is not required Converting other artifacts to requirements such as change requests or defects identified.
Page 438 of 450
Blank Survey

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. 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. 1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification 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. 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. 3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements.
439
Blank Survey
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. 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. 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). 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. 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. 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). 5. Configuration Management
440
Blank Survey
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. 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. 5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. 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.). 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. 6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. 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. 6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. 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. 6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various 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. 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. 441
Blank Survey
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. 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. 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.). 8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? 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). 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? 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? 8.1.5 Support for Data Exchange Standards (AP-233, XML,..) 8.2. Intra-tool communications 8.2.1. Exchange of information between same tool, but 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? 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? 9. System Environment 9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? 9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? 9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? 442
Blank Survey
9.4. Resource requirements: Please identify hardware/software configuration requirements: 9.4.1. Memory requirements 9.4.2. CPU requirements 9.4.3. Disk space requirements 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? 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? 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? 10.6 Web browser interface? 10.7 Edit Undo Function Support 11. Standards 11.1. 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. Warranty: Does your tool have a warranty, 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? 12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? 12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? 12.5. Provide Internet Web page location for company/tool info 12.6. Phone support: What type of phone support is available from the tool supplier? 12.7 Support User's Group 13. Training 13.1 Tool specific training classes 13.2 Training available at customer's location 13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? 13.4 Software installation with only basic training 443
N/A
Blank Survey
14. Additional Comments 14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)? N/A
444
Blank Survey
Comments
ed, the allocation of requirements to sub-system elements takes those sub-systems elements.
em architecture captured, requirements are allocated to the
445
Blank Survey
e ability to see the links where they come from, where they go, and
446
Blank Survey
r a team of engineers to look/work on the same information at the
447
Blank Survey
448
Blank Survey
449
Blank Survey
450

INCOSERMToolSurveyConsolidatedResults (1) - Kopia

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

INCOSERMToolSurveyConsolidatedResults (1) - Kopia

Hochgeladen von

Copyright:

Verfügbare Formate

INCOSE Requirements Management Tools Survey Updated 8-August-2010

Overview of INCOSE Requirements Management Tools Survey Categories

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full Full Full

Full Full None

Full Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full N/A N/A N/A N/A N/A N/A Full Full

Full Full Full Full Full Full Full

Full Full Full Full Full Full Full Full Full

Full Full None

Partial Full None

Full Full Full

Full Full None

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full Full Full Full Full Full Full Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full Full Full

Full None None

Full Full Full

Full Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full N/A Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Full Full N/A Full Full Full Full None Full

Full Full Full Full Full Full Full Full Full

Full Full Full Full Full Full Full Full Full

Full Full Full Full Full Full Full Full Full

Full Full None

Full Full Full

Full Full Partial

Full Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Cradle 5.7 (Updated: 1/6/2009)

Dimensions RM v10.1.4 (Updated: 9/24/2008)

Full Full Full

Full Full Full

Full Full Full

Full Full Full

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010

Cradle 5.7 (Updated: 1/6/2009)

Dimensions RM v10.1.4 (Updated: 9/24/2008)

INCOSE SE Tools Database: Consolidated RM Surveys

Updated: 8 August 2010