INCOSE Requirements Management Tool Survey Response
INCOSE Requirements Management Tool Response
The table below contains Innoslate's responses to the survey questions for the INCOSE Requirements Management Tools Survey developed by the INCOSE Tools Database Working Group (TDWG).

Date of Submission: 8/1/2013
Requirements Management Survey Questions Compliance (Full, Partial, None) Responses
1. Capturing Requirements/identification
1.1. Input document enrichment/analysis: Using existing document information (such as glossary, index, etc.), aid the user in requirements analysis, identification of requirements, etc. Full Innoslate's automated parser extracts Statements and Requirements using the structure of the Microsoft Word (DOCX), Microsoft Excel (CSV), or IBM Rational DOORS (CSV) document. The Analyzer portion of the tool also provides a means to check the quality of the requirements (is it clear, complete, etc.) by reading the descriptive information. The document itself is also automatically saved as an Artifact for later use.
1.1.1. Input document change/comparison analysis: The ability to compare/contrast two different versions of a source document. Full Innoslate allows you to capture multiple versions of source documents and using the multiple tabs of any modern browser, you can compare documents side by side to determine the changes. If using the tool itself, the history feature provides information about what changed in different entities, thus making it ideal for generating the source requirements documents themselves.
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 As above, the "check quality" tool can be used in the Requirements View or for individual entities to determine if the Requirement is clear, complete, consistent, correct, design, feasible, modular, traceable, and verifiable. Definitions of each of these factors are provided with the tool.
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 The automated quality checker provides suggestions on how to fix the requirement to enhance its quality score. The quality checker also enables the user to override the automated analysis. In either case, an overall quality score with a color coded bar appears for each entity.
1.4. Manual requirement identification: A manual means of identifying or creating requirements. Full Again, each entity quality parameter can be changed manually or using the automated tool. In addition, the schema extension capability allows the database owner to add or hide the quality factors.
1.5. Batch mode operation: A mechanism for inputting/identifying requirements from outside of the tool. Full The Analyzer tool provides the best way to extract requirements from documents. The tool also imports data from Microsoft Word, DOORS, XML, and CSV formats.
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 Innoslate provides smart CSV importers to intelligently update existing documents from other tools.
1.6. Requirement classification: Does the tool have the ability to classify/categorize requirements during identification Full Innoslate provides labels to support classification/ categorization of requirements at any time. In addition, relationships to other schema entities are available, including to the Measures class, which provides ways to capture metrics.
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 Innoslate provides hierarchy, organization, and spider charts to show relationships between parents and children (e.g., WBS), organizational Assets, and any (respectively). Requirements can be traced to any other entities in the database and viewed graphically using the spider diagram. In addition, Innoslate provides an Asset diagram that shows the physical architecture using pictures of each entity, lightning bolts, colored lines, and binary (10011) forms to make it look like a Visio diagram. The Action diagram provides the sequencing of functions and data flow together.
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 In addition to capturing textual information and tables in each entity, large complex reports, such as those for a CONOPS or JCIDS document, come with wizards to capture the information in an easy to understand process, while automatically putting the information into the correct classes and giving them appropriate labels, thus making report generation from the database much easier.
3. Requirements flowdown: Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements.
3.1. Requirements derivation (req. to req, req. to analysis/text): The ability to derive/create additional requirements and link between them such as requirement to requirement, or requirement to text (representing trade studies) to derived requirements. Full Requirements can be traced to any other entities in the database. For example, if a Requirement affects an Input/Output entity or a Connector (e.g., Interface, Link, etc.). Requirements (and all other classes) can have children using the decomposed by/decomposes relationships. In addition, peer-to-peer relationships between all classes (related to/relates) are provided as well.
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 Performance requirements can be related to Characteristic or Measure entities. We suggest using Characteristics for non-qualitative requirements, such as color, and Measures for quantitative requirements, such as weight or power. These Characteristics and Measures can be related to any Asset (system, component, person, etc.) and displayed using a Radar Chart. This chart shows the various performance requirements values, including thresholds and objective values for further analysis.
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 All relationships (linking) are bi-directional. The schema requires that all relationship be bi-directional and the inverse relationship is automatically created. Hence, Requirements that trace to Actions, Assets and any other class can immediately be traced back from the other classes.
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 To capture the allocation rationale, etc. we recommend using the Decision class. It has the attributes already designed for this. In addition, every entity has a place for comments that can be used by anyone who has access to the database. For larger documented trade studies or other rationale, Artifacts provide a way to link these detailed analyses to any entity.
4. Traceability analysis: Once the allocations are complete, the user will want the ability to see the links where they come from, where they go, and why they apply.
4.1. Identify inconsistencies (orphans,...if so what kind of...): The tool should allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans). Full Relationship between entities can be viewed graphically and in the Entity view with the relationships tabs. Related entities show directly on these views. Also a Requirements Gap report can be generated to identify unsatisfied and unverified requirements.
4.2. Visibility into existing links from source to implementation-i.e. follow the links: With the requirement links in place, the user needs the ability to follow the links to see where they come from and where they go to. Full The Entity view also allows the user to view related entities and follow the trail of relationships wherever they go. For a more visual view we recommend the spider diagram that presents all the related entities in a single picture (to 3 levels).
4.3. Verification of requirement (was it done, how was done): Throughout the life of the project, the requirement management tool will be used to verify that the requirements have been met. The tool should provide the ability to document that the requirement was fulfilled, how it was done, and who was responsible. Full The base schema for Innoslate provides a "verified by" relationship between the Requirement and any other class, thus making requirements verification easy. In addition, the base schema has the "satisfied by" relationship to track who or what fulfills the requirement.
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 Test Center rolls up the test status. Roll ups are also provided for cost, time and resources using the discrete event and Monte Carlo simulators. The Monte Carlo simulator provides standard deviations and means for these values. Other values can be rolled up using Innoslate's SDK and scripting.
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 Innoslate provides a history of every change to every entity at the entity level. This feature includes changes to relationships and all attributes, as well as descriptions. It also captured which user made the change and has the ability to revert to previous versions if it has been determined that a change was made in error.
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 Baselining your requirements document creates a snapshot of your requirements document at the moment in time when the baseline is created. All document entities, their relationships and attributes will be captured. Innoslate also includes the ability to baseline, branch, and copy (fork) entire projects.
5.3. Access control (modification, viewing, etc.): The requirements should be able to be protected from modification, viewing, etc. by individuals or groups. Full Access control is provided at the user level in three levels: Owner, Read/Write, and Read Only. Read Only viewers (which can include Free version users) can provide comments about any element.
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 Innoslate has a number of complex reports and corresponding input wizards, including a CONOPS reports and all the JCIDS documents (DCR, ICD, CDD, and CPD). User's manuals for each of the documents are also provided and available as downloadable PDF files on the open website.
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 All fields (e.g., name, number, description) provide spell checking integrated with your browser's dictionary. Reports for all entities exist to provide a full data dictionary for every entity in the tool. Statements can also capture acronyms and provide glossary definitions.
6.3. Presentation output: Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs. Full All diagrams can be saved as graphics files and are automatically provided in reports. In addition, any kind of graphic format (e.g., PNG, JPEG, etc.) can be uploaded for any entity. A title and description for each picture can be added as well. This additional information is used in diagrams, such as the Asset Diagram and accessible in Innoslate's high quality reports.
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 User defined tables are generated through report wizards. Classification heading/footers can also be added via this mechanism.
6.5. WYSIWYG previewing of finished output: The tool should allow the user to view the document on-screen in finished format. Full All documents are captured as Artifacts, which can then be downloaded and viewed on-screen in finished format. Therefore, versions of the document can be generated and traced. If changes are made in a word processing program, that file can then be uploaded back into the Artifact for storage and retrieval.
6.6. Status reporting: Tool users need to status information in the requirements management tool. Full Status can be provided using labels, which can be applied in large numbers to entities in the Database or Requirements views. These labels become part of the reports provided. In addition the schema can be extended to add status information.
6.6.1. Technical Performance Measurement status accounting: Status current technical performance of various allocated performance requirements and monitor progress towards goals. Full We recommend the use of the Measure class entities to capture this information at present.
6.6.2. Requirement progress/status reporting: Status reporting on current compliance/non-compliance to various requirements Full Innoslate provides quality checks for every requirement. These quality checks are partially automated. An overall quality score is given for every requirement.
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 Ad hoc queries are provided using the search capability and class/label filters.
7. Groupware: Since Systems Engineers rarely work as individuals, the ability for a team of engineers to look/work on the same information at the same time is critical.
7.1. Support of concurrent review, markup, and comment: The tool should support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives. Full Innoslate was designed for collaboration. Projects can be shared with anyone. Users can initiate a chat to discuss what each other are planning to do with the entity.
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 Innoslate provides control at the user level and recommends keeping separate database that other groups should not access. Comments available for every entity to Read only users. Separate project can be easily integrated using the import/export capability.
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 Requirements can be exported to other tools using the XML export feature.
8.1.1. Interfaces to other tools: What tools will your requirements management tool interface with or talk to? Full XML export enables the potential for interfacing between any tools. An explicit MS Project is also currently available.
8.1.2. External Applications Program Interface available: To support the wide variety of tools in use by engineers, the requirements management tool should have programmable access to the information contained in the tool's database (to get access to and deposit information). Full A Software Development Kit (SDK) and REST API is available to Professional users.
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 We have standard query access to search the database and we support the Lifecycle Modeling Language (LML) standard XSD.
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 Microsoft Word, Microsoft Project, DOORS, and Microsoft Excel CSV files can be imported automatically with Innoslate's Import Analyzer.
8.1.5 Support for Data Exchange Standards (AP-233, XML,..) Full Innoslate uses XML for interchange standard following the Lifecycle Modeling Language (LML) open standard. Innoslate cam also import XMI from many modeling tools.
8.2. Intra-tool communications Full Innoslate has an XML import/export capability.
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 Innoslate's XML provides a means to externally import and export information, however, we recommend using the "Sharing" feature whenever possible to avoid the tedious "import/export" activity. Sharing provides worldwide access to the same database.
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 Since the Innoslate database is available to any user anywhere, if shared, then
9. System Environment
9.1. Single user/multiple concurrent users: Is the tool support a single user or multiple concurrent users? Full The cloud version of the tool provides for unlimited numbers of concurrent users. The server based version allows for as many users as your servers can handle.
9.2. Multiple Platforms/Operating Systems ______?: Which platforms and operating systems does the tool run on? Full Innoslate uses any modern (HTML5 compliant) we browser as it's user interface and therefore runs on any platform (e.g., PC, Mac, iPad, iPhone) and any operating system.
9.3. Commercial vs. unique database: Does the tool use a proprietary or commercially available database? Full Since no fully scalable cloud database is available at present, Innoslate Cloud uses a proprietary middle layer that was built on Google's "Big Table" database. Innoslate Enterprise uses Microsoft SQL Server as it's primary datastore.
9.4. Resource requirements: Please identify hardware/software configuration requirements: Full No minimum requirements except those to operate the platform.
9.4.1. Memory requirements Full 1GB RAM
9.4.2. CPU requirements Full > 1GHz
9.4.3. Disk space requirements Full > 10GB
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 Yes by peeling off separate windows or tabs from the browser.
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 Using the browser capability to peel off tabs a user can have multiple views open. To see changes the user may have to refresh the page.
10.3. Interactive graphical input/control of data: Does the tool support graphical input and manipulation of data? Full Yes using the HTML5-compliant browsers.
10.4. Which window's standard do you follow?: If your tool supports a window's standard, which one(s)? Full Innoslate supports the HTML5 standard and works in all current browser versions (Chrome, Safari, Firefox, Internet Explorer) and most devices including Windows, Linux, MAC OS X, iPad, iPhone etc.
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 Innoslate includes both a Discrete Event and Monte Carlo Simulators. The Monte Carlo simulator computers both standard deviation and mean values for time, cost, and resources. Custom scripts can also be created with the Innoslate SDK.
10.6 Web browser interface? Full Yes! All HTML5 compliant browsers (Chrome, Safari, Firefox, IE10 support)
10.7 Edit Undo Function Support Full The History system tracks both attributes and relationships changes of all entities through time and allows reverting (undo) of these changes. All diagrams include undo/redo buttons and most other views support CTRL-Z undo operations.
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 JCIDS report output, DoDAF views, and MODAF views; IDEF0; N2; LML; SysML; DoD Risk Matrix
12. Support and Maintenance
12.1. Warranty: Does your tool have a warranty, if so what is it? Full 30 day money back warranty. As a subscription service, software updates are automatically provided to all cloud users. For local server version updates are provided quarterly.
12.2. Network license policy: Does the tool support network licensing (floating, node locked, etc.), if so which license manager? Full No license manager is required for our cloud version. Just sign up for the service and pay on-line or make enterprise arrangements. For the local host version the license manager is integrated with the software and can scale to as many users as needed.
12.3. Maintenance and upgrade policy: How often are software updates released; are updates separately priced items, etc.? Full Using an Agile development cycle, updates are provided automatically in bi-weekly to monthly releases. You may have to refresh your browser to use the latest release.
12.4. On-line help: Are the users manuals on-line, is there on-line help with the tool? Full User's manuals and videos are available on the main open website. The tool provides built-in help by using hover to provide definitions of all classes, relationships and attributes
12.5. Provide Internet Web page location for company/tool info Full www.innoslate.com and www.specinnovations.com
12.6. Phone support: What type of phone support is available from the tool supplier? Full Telephone support is available during normal US Eastern time zone; chat is also available during that same time
12.7 Support User's Group Full User's can provide Feature Requests 24/7/365 and can submit XML files (parsed documents and models) for sharing using the Sharespace feature on the open website.
13. Training
13.1 Tool specific training classes Full Standard 1/2, 1, 2 and 3 day are available if needed, as well as custom, training options are provided. They include how to do systems engineering and enterprise architecture development as part of the training. On-line video training is also available.
13.2 Training available at customer's location Full Yes. We can conduct any class at the customer's location or over the web.
13.3 Recommended training time: What is the recommended training time for a user to become proficient in using the tool? Full No actual training should be required if the user has had some familiarity with this class of tool. The tool has been designed for usability with the built-in help, user's manuals and videos. We offer more in-depth training for customers working on complex problems.
13.4 Software installation with only basic training Full No software installation is required (except the Server version, which [if necessary] SPEC Innovations personnel will come out and provide).
14. Additional Comments
14.1 What other requirements management features do you as a tool supplier think are important (modeling, etc.)? Full Innoslate was designed as a Systems Engineering as a Service (SEaaS) product. It integrates both the technical and program management aspects of systems engineering per INCOSE's definition and supports the entire lifecycle. Thus it enables the systems engineering to optimize cost, schedule and performance. It was designed to scale to very large databases and enable worldwide collaborate. The modern design meets all current (2013) standards for usability. It includes a built-in simulator capability that not only shows time, but also cost and resource impacts. But perhaps the most important feature is the desire to rapidly evolve the tool to provide all the different capabilities needed by systems engineers to perform analysis, not just capture data.

Give us a call

Need help? Call us today and speak with our support engineers

+1 (571) 485-7800

Request a demo

Learn more about about how Innoslate can help your organization

Request a demo

Start a free trial

Explore the benefits of Innoslate, free for 30-days

Start a trial
;