(Back)
INCOSE Tools Database Working Group
New or revised questions for 2001 are highlighted.
Previous responses and summaries can be located at the INCOSE Web (submitted this year)
Using existing document information (such as glossary, index, etc.) aids the user in requirement analysis, identification of requirements, etc.
RDD-100Ò provides several mechanisms that aid the user in analyzing requirements and identifying requirements.
A parser tool can be defined and developed using the Report Writer capability in RDD-100 to help the user identify single or compound requirements based on particular parameters (rules) specified by the user. If the user needs to categorize requirements in a specific manner, the rules for this categorization can be captured and automation provided. A standard requirements parser is included with the product.
A standard parser is available for capturing data presented in columns (like an Excel spreadsheet). The user is free to choose which element type (Requirement, Component, Risk etc) appears in each column, the parser uses schema information to present a pick-list of the attributes for the selected element type. The parser allows the user to specify relations between the columns (again, by presenting a list of valid relation names based on the schema).
Another aid provided by RDD-100 to help the user in analyzing the input documents, is the ability to extract requirements from the ASCII form of the electronic document (e.g., delimited text file produced from MS Word, MS Excel, or MS Access). Using this capability the user can selectively choose the text to be captured and stored in the robust, extensible schema provided in the “out of the box” RDD-100.
(Full Compliance)
The ability to compare/contrast two different versions of a source document
RDD-100 provides several mechanisms that aid the user in comparing and contrasting two versions of a source document.
RDD-100 provides the ability to contrast and compare two different versions of any document. RDD-100 can generate change documentation in two formats.
1. The first is the To/From format that shows the “From” condition and “To” condition for each requirement change.
2. The other format is a regenerated version of the source document with change bars and strike-thru text. Depending on the application, one format may be favored over the other.
A more comprehensive option allows the user to compare to full System Design Databases, describing the Requirements and the associated functional, physical, and logical views, producing a detailed change report.
(Full Compliance)
A mechanism for automatic identification of requirements by key words, structure, unique identifiers, etc. to create requirements from the text.
RDD-100 also provides the ability to automatically parse requirements text into RDD-100 by using the mechanisms of the query tool. The parsing mechanisms can be customized to follow the parsing rules identified by the user. These expressions help identify requirements based on keywords, structure, or unique identifiers.
(Full Compliance)
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?”.
RDD-100 provides the ability for the user to interactively identify and capture requirements through the use of the extraction templates. The extractor allows the user to identify and establish within RDD-100 the textual requirements elements; this same extractor mechanism identifies and associates the requirements with the specific file source providing an extra level of traceability for the user.
RDD-100 provides the user with the ability to follow user-specific rules that would find and identify text that matches the those rules. The mechanisms are available through the custom templates developed in the Report Writer provided with RDD-100. These custom templates can be written to provide the user with feedback prompts such as “is this a requirement?” or choices “is this a requirements, a component, or interface” and based on the choices, the current data element is populated. Data population can either be initial or update.
(Full Compliance)
A manual means of identifying or creating requirements.
RDD-100 lets the user manually create and identify requirements through several types of views. The user can view and access all the data (attributes and relationship) as well as navigate through the entire data set using the element editor view (filtered or non-filtered based on user’s preference). If the user’s process stipulates that users are to see limited views into the data (reduced data scope and visibility), RDD-100 supports this process demand through task-based visibility options , or through multi-element views that reflect the user's process.
RDD-100’s Extractor Tool is used with an appropriate Multi-element View template to guide the selection of requirements from a text file and then their creation as elements, attributes and relationships in the data set.
The Report Writer available in RDD-100 also provides the users with ability to manually input the requirements (or other data) with other tools (e.g., MS Word, MS Excel, MS Access) and then load that data directly into RDD-100.
(Full Compliance)
A mechanism for inputting/identifying requirements from outside of the tool.
Users can use a batch mode to capture and create requirements, update requirements, and produce reports within RDD-100 through the use of the Command Reader and the Report Writer.
(Full Compliance)
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
RDD 100 provides the ability for the user to update existing linked documents from new/changed versions of a source document without having to re-establish traceability links.
If the source document is updated under the same name and in the same file location, no change to the traceability linkages are required. If the file name or location changes, the change needs to be reflected in the data stored in RDD-100. If the content of the source changes, even if the location is the same, the SDD needs to be updated. Assuming PUIDs are being used, the parser could do the necessary add/delete process. Otherwise, manual mechanisms are required to do this.
(Partial Compliance)
Does the tool have the ability to classify/categorize requirements during identification?
RDD-100 provides the ability for the user to interactively (or in batch mode) classify/categorize requirements during identification. This ability is provided through several mechanisms such as the Multi-Element Views, extractor, or by using templates that are created for that specific purpose. Classification and categorization may be made either through attributes of the element or through relationship with (link to) another element; the specific mechanism depends on the user’s process and the schema implementation choices made by the program or project.
(Full Compliance)
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.
RDD-100 has the ability to capture and display the various portions of the system implementation. If the user chooses, the physical and functional architectures can be captured and displayed in a hierarchical view with selections made by the user. These views can be created either through the use of built-in hierarchies, custom hierarchies developed from templates, or by using the outline view (through the multi-element view mechanisms).
(Full Compliance)
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.
RDD-100 has the ability to capture and display the various portions of the system implementation. If the user chooses, the physical and functional architectures can be captured and displayed in a hierarchical view graphically with selections made by the user as ad hoc views. These views can be created either through the use of built-in hierarchies or with custom hierarchies developed from templates) or by using the outline view (through the multi-element view mechanisms).
(Full Compliance)
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.
RDD-100 has the ability to capture in a textual format the various portions of the system implementation. If the user chooses, the system elements can be viewed in either an outline or textual view through the embedded multi-element view mechanisms. The textual elements can be linked to (associated with) other elements contained in the system design database.
(Full Compliance)
Once the requirements have been captured and system architecture captured, requirements are allocated to the various system elements.
RDD-100 provides the user the ability to link (associate) requirements with any element in the system’s hierarchy. These associations may be between requirements and other requirements, or between requirements and elements representing the physical, functional, or logical architecture, or between requirements and any other element needed to support the user’s business process rules. RDD-100 supports viewing requirements for all the views of requirements architectures (operational, functional, and physical) as well as the inter-relationships between these views. RDD-100 provides the ability to flowdown requirements from all system stakeholders.
(Full Compliance)
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.
RDD-100 allows the user to derive requirements from other requirements and to link (associate) the derived requirements to their source (a trade study or decision, issue, physical component, or constraint, etc.). Requirements can also be linked to the specific functional behavior that derives them and in turn this can be associated with a specific issue or decision that was identified/made through the process of engineering analysis.
(Full Compliance)
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.
RDD-100 allows the budgets for weight, risk, cost, throughput, etc. to be associated with a requirement or functional behavior or system components. The budgets can be allocated to system requirements. RDD-100 also provides the ability to either calculate these budgets within the tool (based on user-defined “roll-up” algorithm) or to interface with other tools designed for specialty applications. The results of those calculations can be captured, stored, and integrated into the system design database after the application has performed the calculation to provide the user with a complete traceability of decisions and trades.
Holagent Corporation’s IDTC product offering provides the users the ability to capture and track costs as well as have the costs analyzed using the parametric capabilities of Price Systems PRICE software.
(Full Compliance)
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.
RDD-100 allows the user to link (associate) to elements from either end of the link. Once the user has made a link (association) in one direction, the link (association) is automatically made in the reverse direction by RDD-100. The forward and reverse links can be investigated and the user can either see them on-line using the views providedor through produced (published) information products.
(Full Compliance)
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.
RDD-100 supports the capture of allocation rationale,
accountability, test/validation, criticality, issues, etc., through the use of
either provided element types or user extensions to the robust “out of the box”
data storage schema. The mechanisms that RDD-100 uses to categorize and link
information is through the ERA (Element-Relationship-Attribute) model. Various
input and output mechanisms are provided to show on-line and document forms
that present the information both textually and graphically with their complex
inter-relationships.
(Full Compliance)
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.
RDD-100 provides the user with the ability to see the links (associations) made between system design database data elements stored in RDD-100. The user can see the links graphically (through built-in or custom hierarchies) or outline/text (multi-element views) or in hardcopy (through Report Writer query templates). For large sets of requirements, RDD-100 can generate E-size plots of the hierarchies that facilitate requirements reviews. The information needed for traceability analysis includes not only requirements but also rationale, assignments, criticality, test/validation and many other issues to the requirement, allocation, and the system element to which a requirement(s) is/are linked.
(Full Compliance)
The tool should allow the user to identify inconsistencies such as unlinked requirements or system elements (orphans).
RDD-100 provides several mechanisms to help the user identify data inconsistencies. The “out of the box” product comes with a set of predefined consistency checks which identify the most common errors (e.g. orphan elements). If the user’s process has dictated specific rules, these can be implemented using the on-line consistency checking mechanism or discrepancy reports that can be produced and published either as hardcopy or published as PDF format.
The user can collect statistics based on these checks which can be output in format that is compatible with spreadsheet tools. The user can develop process metrics from these collected statistics.
(Full Compliance)
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
RDD-100 provides the user with the ability to investigate existing links on-line through custom hierarchies (graphical) and multi-element views (textual). The user is able to choose the “focus” of the link and then can have visibility in the linkages that reflect upward, download, and lateral traceability. The user can print the graphical and textual views directly from the tool or he/she can develop a report to output the information.
(Full Compliance)
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.
RDD-100 provides the user with the ability to verify that the requirements have been met. The documentation for the verification can be captured using either element types that are provided with the tool or through schema extensions made to meet the tailoring requirements of the user’s project. If the user’s process dictates a specific verification process, that process can be reflected within RDD-100, the process rules defined, and reports templates developed that will provide management visibility into the process.
RDD-100 provides the data storage mechanisms necessary to allow a user to verify the requirement, what test plan and case that verified it, what test report documents it, as well who performed the verification. RDD-100 can support process-specific verification strategies prescribed by the users process.
(Full Compliance)
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).
RDD-100 provides the ability for technical budgets to be allocated and rolled up to support verification of performance requirements. RDD-100 also provides the mechanisms to allow integrated design to cost requirements (in support of initiatives such as the DoD’s CAIV) to be captured and verified. RDD-100 provides the ability to identify variances from the budget (see Holagent Corporation’s IDTC product offering). The user can access budget values (allocated and actual) through the Report Writer. These values can be provided to spreadsheet tools that might be used to provide management insight into the process.
(Full Compliance)
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.
RDD-100 provides the user with the ability to track who, what when where, why, and how a specific requirement or other engineering element changed throughout the course of the project’s life cycle. When a change is made it is tracked through attributes for each element type called “creation date” and “modification date”. The user’s process rules can be used to define the procedures and supporting processes to allow for full configuration management of the data contained in RDD-100.
RDD-100 provides the ability to compare two, user-selected versions of data by running standard reports (Version or Variant Compare) provided with the “out of the box” product.
(Full Compliance)
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.
RDD-100 provides the ability to capture and store baselines in ASCII file format. These ASCII files can be “vaulted” by the procedures prescribed in user’s Quality Assurance/Configuration Management process. The retrieval of these baselined data sets depends on the organization process rules. The retrieved baselines can be compared and reports run (from templates) that will provide insight into the data baseline configuration.
(Full Compliance)
The requirements should be able to be protected from modification, viewing, etc. by individuals or groups.
Access control to RDD-100 is managed through the computer network or can be designated to a particular work station. Access control to the data stored within the system design database can be managed within RDD-100; access control of the data is determined by the rules of the user’s process.
For the network case, assuming that access control is provided by the network and the user has access to RDD-100, data access can be handled via data ownership. This limits the user to have read-only permission on certain information and have write permission on other information. For more restrictive access, query mechanisms are provided to subset the data thus limiting the visibility to a certain portion of the database. The ability to modify data and have the changes reflected in the baseline is a process decision. RDD-100 provides change management support that allows users to make informed decisions prior to updating a particular baseline.
(Full Compliance)
The requirements management tool should output documentation in various military/commercial standard formats (MIL-STD-490, DoD-2167A, etc.).
RDD-100 provides the ability for the user to use standard specification outputs (such as Mil-Std-490, -498, -2167, etc.) or define/tailor an output format for a particular project. RDD-100 also provides the user the ability to generate the formatted document using tailorable Design Guides that reflect over 14 years of “best practice” for our customers or the custom report templates using the Report Writer.
(Full Compliance)
The tool should also support document quality and consistency checking through spell checking, data dictionaries, acronym tables, etc.
RDD-100 provides the ability to check spelling on each element or in a group of elements. RDD-100 provides the user the ability to produce data dictionaries, acronym tables, etc. The user can also define consistency checks based on the process rules to be applied. Quality metrics can be developed based on the rules and the results either presented textually or graphically (by output to spreadsheet tools, such as MS Excel).
(Full Compliance)
Once the information is loaded, the requirements management tool should support the generation of presentation quality charts and graphs.
RDD-100 provides the ability to produce quality documents, including charts and graphs, in postscript format. The user can produce a presentation by using Adobe’s Distiller to generate PDF files from the postscript file.
RDD-100 provides the ability to present reports and graphical views in HTML format through the Report Writer capability. Many of our customers use this ability to allow them to share their work through controlled publishing strategies for inter- and intra-net applications.
(Partial Compliance)
The tool should support the output of documents in finished form including page security markings, graphics/figures, user definable tables, indexes, etc.
RDD-100 provides the user the ability to customize the output format for documents. The user can produce documents in a finished form that includes page-high security markings, graphics/figures produced from within or outside RDD-100, user-defined tables, indexes, and tables of contents, etc. These final documents can be produced through the Report Writer.
(Full Compliance)
The tool should allow the user to view the document on-screen in finished format.
RDD-100 provides on-line previewing of finished output either through postscript viewers or by using Adobe Distiller to convert the postscript files to PDF format. If the user elects, this conversion can be facilitated with the RDD-100 Command Reader and the process can be automated.
(Partial Compliance)
Tool users need to status information in the requirements management tool.
RDD-100 provides status reporting mechanisms through the on-line consistency checking facility, the multi-element view templates, or through the Report Writer templates. Any of these mechanisms can be used to status either what has been achieved or what needs to be done.
(Full Compliance)
Status current technical performance of various allocated performance requirements and monitor progress towards goals.
RDD-100 provides the ability to status the current technical performance of various allocated performance requirements and monitor progress towards goals. RDD-100 provides this capability through the ability for the user to 1) define elements (customize schema) as “goal” and “actual” and 2) produce accountings of elements by using the Report Writer and Command Reader in combination with other tools (which provides the ability represent graphically the status accounting results in spreadsheet tools such as MS Excel).
(Full Compliance)
Status reporting on current compliance/non-compliance to various requirements.
RDD-100 provides the ability to produce status reporting on requirements and other elements in RDD-100 by using the Report Writer or Multi-Element View templates. RDD-100 allows to the user to either use attributes or links (associations) to provide the statusing mechanisms. The statusing mechanism depends on the user’s business and procedures for using the tool.
(Full Compliance)
The requirements management tool should support ad hoc query’s and searches per the user’s discretion.
RDD-100 provides the ability for the user to perform ad hoc query’s or searches.
The user can prepare a multi-element view template that will follow the defined links (associations) for the query elements and display the results in an interactive, editable view, or printed as an ASCII or PostScript document.
The user can use a Multi-Element View (MEV) template and see the results graphically as a custom hierarchy. The user can prepare and use a Report Writer template and see the results as a document or save the results to a file for further analysis with other tools.
(Full Compliance)
RDD-100 provides the ability for the user to select from a set of symbols, such as Greek characters (sigma, omega etc), plus some mathematical/logical symbols (“for all”, “approximately equal”, “therefore” etc). There is a set of symbols available for text fields that includes the Greek alphabet and several mathematical symbols, for example, ", ', $, \ and ^. RDD allows the user full access to the extended ASCII characters during report execution. In addition, 55 common symbols are available on textual panels which display properly on all user views. However, RDD-100 does not support full scientific text representation (for example integral or differential equations, or subscript/superscript annotation).
(Partial Compliance)
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.
RDD uses a master-subordinate structure that allows both the flexibility required during the early stages of a project, and the rigor required once a baseline has been established.
Master copies of the System Design Database can be maintained and distributed under management control to the appropriate individuals. Each engineer can then act on the same published data, either on all the data, the data to which ownership has been assigned to the individual, or only the subset of data provided as a specific task.
The process of assigning and reconciling the change data can be automated with the use of Command Reader and Report Writer functionality. Because this exchange is file-based, it is possible to integrate this process with workflow or PDM systems.
(Full Compliance)
The tool should support a team of engineers reviewing, marking up, and commenting on requirements or implementation alternatives.
RDD-100 supports concurrent review, markup, and commenting through the ability to change the content of an element’s attributes, the ability to associate issues or comments with any specific element, and to re-integrate the changes and comments through the change integration process enabled by the “export to superior”/“import from subordinate” capabilities in RDD-100.
(Full Compliance)
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.
RDD-100 controls access to the data at the user’s image level. The ability to enforce a process of submitting changes for approval prior to baselining the changes is based on the user’s process. Through the use of the Command Reader, Report Writer, and query mechanisms the user can ensure that appropriate levels of control are exercised on the project. The Report Writer can be used to monitor changes to any element in RDD-100.
(Full Compliance)
Requirements management must have the ability to communicate requirements to other domain-specific design tools (CASE, EE, PDM, etc.).
RDD-100 provides the ability for the user to define the semantic mapping between RDD-100 and other tools used in their engineering environment. RDD-100 accepts data through a defined ASCII interface. RDD-100 outputs data through the same ASCII interface, or a formatted ASCII interface for the receiving tool.
The IDTC product offering provides the interface between RDD-100 and Price Systems PRICE tool suite.
(Full Compliance)
What tools will your requirements management tool interface with or talk to?
RDD 100 provides not only requirements management data management but also provides an internally consistent, fully integrated schema that supports functional, information, behavioral, and physical architecture requirements and design exploration and definition. Data stored in RDD-100 can be shared with to tools such as software tools (Rational Rose, Holagent Corporation has a complete semantic mapping to UML 1.0.), hardware tools (CATIA), cost tools (Price Systems), scheduling tools (MS Project), word processing tools (MS Word97,), and project management tools (e.g., MS Excel).
(Full Compliance)
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).
RDD-100 4.1.2 provides access (into and out) to the data contained in RDD-100 through the Command Reader and Report Writer.
Other product offerings from Holagent Corporation provide a documented Public API that allows users to interface middleware developed using C-language calls or with Visual Basic; please contact Holagent at: products@holagent.com for information on these new products.
(Full Compliance)
Does the tool support Open Database standards such as standard query languages or exchange formats?
RDD-100 provides access to the data through the Command Reader and Report Writer. RDD-100 has a standard, published format for getting data into and out of RDD, it is the .rdt format. RDD-100 has the ability to produce the ASCII file format needed by other tools; the user needs to have access the semantic and syntactic rules that govern other tool’s import file format and a template can be produced using the Report Writer that will allow data transfers to be repeatable and selectable based on the user’s needs.
Other product offerings from Holagent Corporation provide a documented Public API that allows users to interface middleware developed using C-language calls or with Visual Basic; please contact Holagent at: products@holagent.com for information on these new products.
(Full Compliance)
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?
RDD-100 has the ability to import existing data such as an ASCII text file that contains link information to create instances of elements without having to re-enter the information. RDD-100 has the mechanisms that allow the user to capture data from other tools such as MS Excel, MS Word, and MS Access.
(Full Compliance)
Since the tool will be used at different sites and different projects, how does the tool exchange information between different tool installations or databases?
RDD-100 supports exchange of information between different installations (geographic sites) through the export/import mechanisms (RDD-100 .rdt files) that can either reflect the total data set or a selected portion or only the differences between a baseline and the changes that have been made.
(Full Compliance)
Does the tool support comparing/contrasting of different same-tool datasets to allow consistency and verification checking?
RDD-100 supports comparison and consistency checking between
same-tool datasets. The schemas used at the various sites should be compatible.
RDD-100’s import of .rdt files provides for schema validation and other
consistency and/or comparison checks on the way in. If conflicts are found a
conflict file (.cft) is generated. RDD-100 provides the user access to the
generated conflict file; the user can use the embedded mechanisms within
RDD-100 to “see the conflicts” and if desired, the users can integrate all the
changes or none or a portion of the changes. The user can select portions of
the data desired to be directly imported from the conflict file; this
capability allows the user to conform to configuration change management
process and procedures dictated by the user’s process.
(Full Compliance)
Is the tool support a single user or multiple concurrent users?
The current release of the RDD-100 (V 4.1.2) supports a single user as well as a group of users through the use of import and export mechanisms.
Which platforms and operating systems does the tool run on?
The current release of RDD-100 (release 4.1.2) runs on:
1. IBM compatible PCs (Win95/98, or Win NT 4.0 or Windows 2000)
2. SUN (SUN OS or Solaris) or HP (HPUX)
Does the tool use a proprietary or commercially available database?
RDD-100 uses database technology that is proprietary.RDD-100 was built on CinCom’s commercially available single-user, object oriented VisualWorks product.
Please identify hardware/software configuration requirements:
The current release of RDD-100 (release 4.1.2) runs on:
1. IBM compatible PCs (Pentium, recommended) (Win95/98, or Win NT 4.0 or Windows 2000); Color Monitor (1024 x 768 pixels); CD ROM; 1.44 MB 3.5-inch Floppy Drive, Postscript compatible laser printer.
2. SUN (SUN OS or Solaris); Color Monitor (1024 x 768 pixels); CD ROM; 1.44 MB 3.5-inch Floppy Drive, Postscript compatible laser printer.
3. HP (HPUX); Color Monitor (1024 x 768 pixels); CD ROM; 1.44 MB 3.5-inch Floppy Drive, Postscript compatible laser printer.
PC compatible: 40 MB RAM (minimum).
SUN: 40 MB RAM (minimum).
HP: 40 MB RAM (minimum).
RDD-100 supports Operating Systems and the CPUs which support those Operating Systems
PC compatible: 60 MB of free space with additional 60 MB need for disk resident On-line help files
SUN: 60 MB of free space with additional 60 MB need for disk resident On-line help files
HP: 60 MB of free space with additional 60 MB need for disk resident On-line help files
Does the user have the ability run a report and look at a requirement at the same time?
RDD-100 provides the user the ability to be doing a particular task while viewing the results of another. The user can have one window open for review and concurrently author or edit requirements (text, behavior, physical architecture) in another. If the user needs to prepare an information product from a baseline (data that the user does not want to change), RDD-100 enforces the concepts of baseline management at the data level by inhibiting access to the data during the processing time required the collect, format, and develop the information product for publication; usually this time is minimal.
(Full Compliance)
If the tool allows for multiple windows/views into the tool--does a change in one view automatically reflect in all other views?
RDD-100 provides simultaneous updates for all views effected by a change. If the data that is being authored/edited changes what is the view open for review, RDD-100 automatically updates (refreshes) the contents the view open for review.
(Full Compliance)
Does the tool support graphical input and manipulation of data?
RDD-100 uses the mouse to support graphic input and manipulation of data. RDD-100 also provides the user the capability to interactively manipulate and input data through a variety of diagrams (Functional Flow Block Diagrams, Behavior Diagrams, Hierarchical Views, N2 Charts, IDEF0, and Data Flow Diagrams). RDD-100 provides the user the capability to prepare data queries through graphical representation (Behavior Diagrams for reports).
(Full Compliance)
If your tool supports a window’s standard, which one(s)?
RDD-100 (V 4.1.2) follows the X-Windows standard.
Does the tool allow the user to create and playback commands or macros that allow the user to automate various tedious tasks?
RDD-100 provides the capability to produce scripts using the Command Reader and to produce macro-like report templates with Report Writer or to produce macro-like on-line templates with the multi-element view editor mechanisms.
Command Reader and Report Writer commands can be contained in files that can be accessed through libraries. The user is provided automation capabilities through Report Writer such as parsing in of information from source documents; the Command Reader provides automation assistance in providing the user the ability to generate subsets of data to be distributed, or providing a method (with UNIX system tools) to execute chronologically-based reports to produce statistics and metrics for management insight.
(Full Compliance)
Does the tool allow a user to access the tool or database with a web browser?
RDD-100 (V 4.1.2) has the ability for the user to access RDD data through a web browser. Currently this capability is through the publishing of the data in HTML files that are produced through the Report Writer. Holagent Corporation has a several new products that provide this capability; please contact products@holagent.com for more information on these new products.
(Partial Compliance)
Does the tool incorporate an Undo feature? Is it multi-level?
RDD-100 4.1.2 has undo features that is a single level per open view. The undo features apply to text or graphic change in the open view. The user can “undo” sets of changes by applying a process-specific baselining set of procedures that would allow the user to fall back to an earlier data set.
(Partial Compliance)
Which military/commercial standards does your tool comply with--including database standards, output document standards, exchange standards, display/graphics standards, etc.
Display standards: X-Windows
Military/Commercial Standards: IEEE-1220, EIA-632, Mil-Std-499A/B, Mil-Std-2167 Mil-Std-490, Mil-Std-498,. Mil-Std-961.
Data Format Standards: ASCII; Postscript.
Database Standards: proprietary database access through ASCII files, published format and syntax of RDD-100’s .rdt file format.
Does your tool have a warrantee, if so what is it?
During the initial 90 days after a customer licenses product, Holagent Corporation provides its standard support and maintenance for the licensed product at no charge. Thereafter, Holagent Corporation will provide such services to the customer for each licensed product for which Customer has purchased a Product Service Unit as set forth in Holagent's then current price list.
Does the tool support network licensing (floating, node locked, etc.), if so which license manager?
RDD-100 is licensed on network/simultaneous-access basis (floating). RDD-100 uses the FlexLM license manager.
How often are software updates released; are updates separately priced items, etc.?
RDD-100 incremental software updates are released as needed and are available from the Holagent Corporation web site. All updates to the RDD-100 product family are included in the maintenance price.
Are the users manuals online, is there online help with the tool?
The current release of RDD-100 has on-line documentation that includes a users guide and on-line help. The on-line documentation is context sensitive from within the tool and has hyperlinks to on-line help.
Does the tool vendor have an Internet e-mail address and/or World Wide Web home page? If so, what is the address and Uniform Resource Locator (URL)?
Holagent Corporation maintains a homepage that can be access at http://www.holagent.com. Support can be reached at service@holagent.com. Product information can be requested through products@holagent.com.
What type of phone support is available from the tool supplier?
Holagent Corporation maintains a Customer Support hotline. In the United States the toll-free number is: 1-888-466-8751. The USA hotline is active from 8:00am PT to 5:30pm PT Monday through Friday. At other times, please leave a message and every effort will be made to return your call on next business day.
The European Help Desk can be reached by phone: +44 (0)14 9487 6490 The European Help Desk is active from 9:00am to 6:00pm Monday through Friday. At other times, please leave a message and every effort will be made to return your call on next business day.
The Korean Help Desk can be reached by phone: +02 3472-8463 The Korean Help Desk is active from 9:00am to 5:00pm Monday through Friday. At other times, please leave a message and every effort will be made to return your call on next business day.
You may contact Customer Service representatives via email; these addresses are:
USA Help Desk email: service@holagent.com.
European Help Desk E-Mail: Euro-Service@holagent.com
Korean Help Desk E-Mail: alkc@nuri.net
Does a User's Group exist? If so, who is the primary contact?
Many of our customers have private User Groups. Holagent Corporation supports meetings of these User Groups when requested. If users are interested in sharing information among themselves (multiple companies), they should contact Holagent’s User Group Coordinator at usergroup@holgent.com. Check our website www.holagent.com for forthcoming user group activities.
Holagent Corporation provides training at the following locations: corporate offices in San Jose Area of California; in throughout Europe and in Seoul, Korea. If these are not convenient, please contact your local Holagent Corporation representative to arrange training at your location.
Holagent Corporation can provide training at a customer’s location. The training classes can be tailored to meet the customer’s needs and can be designed to reflect the customer’s Systems Engineering Process. Please contact training@holagent.com for specific information about customized training.
RDD-100 for training for requirements analysis without additional modeling is two days. Training for model engineering activities is four days. Additional modules for training include Report Writer training (three days) and modeling and simulation basics (DVF training) (three days). More training for process enablement through schema development and user utilities (reports and other templates, consistency checks, etc.) is available as consultancy, please contact your local Holagent Corporation representative to arrange this type of technology transfer for your location.
Please contact training@holagent.com for information about our standard training schedules or to arrange courses tailored to meet your process needs.
If software installation is defined as “install on computer system”, RDD-100 can be installed on the user’s computer system by someone without training in the application of the tool but with administrator privilege for the computer system.
After installation, the responsible process coordinator must insure that the users are provided with the proper schema and report templates to perform their tasks.
Important to the management of requirements is the ability to understand all the relevant issues and requirements of concern in developing today’s complex systems. It is important that models be developed and simulations executed at all phases of the project/program (acquisition) life cycle.
Models and simulations are key components needed to help suppliers and acquirers understand the evolving needs, requirements, and design of complex systems. Early idenfitication of risk areas and understanding of alternatives helps integrated teams to produce quality systems at lower cost.In developing these complex systems, it is vital that the system users, buyers, and developers have a common understanding of the problem from the early stages of the development effort; any tool suite needs to provide the ability to enable enhanced communications among the team members. It is also crucial that they understand what behavioral characteristics are expected of the fielded system.
Also key to understanding the problem are the various characteristics of the problem: process and project/program management requirements, cost considerations (integrated design to cost), reliability, maintainability, logistics, etc. RDD-100 provides the engineering team the ability to consider the different perspectives of the various contributors to the system development effort and to capture and relate all the requirements from a variety of perspectives.
The RDD-100 family has options that allow users to perform trade studies that need both probabilistic and deterministic analyses. RDD-100’s optional Dynamic Verification engine provides users with the ability to model and understand their requirements through discrete event simulation. Some of our clients have used this capability to perform economic impact analyses in the very early phases of a systems acquisition life. Please contact consulting@holagent.com to learn more about these complementary capabilities available to assist the user in comprehensive requirements analysis and management activities.
Holagent Corporation was recently created to be the world leader in Systems Engineering and Life Cycle Management technologies. RDD is the premiere Systems Engineering (SE) software product in use internationally by many of the world's largest corporations in the aerospace, automotive and communications markets.
Headquartered in Gilroy, California, Holagent is a privately held, venture-capital funded company with sales and support offices and affiliates in the United States, Europe, and Asia. Below are listings of your local representatives:
UNITED STATES OF AMERICA
Holagent Corporation, Corporate Office
777 First Street, PMB 524
Gilroy, CA 95020-4918 USA
Sales Information: 925.249.0633
Support: 1-888.466.8751
E-Mail: Information@holagent.com
URL: www.holagent.com
EUROPE
Holagent Europe Limited
PO Box 329, Amersham
HP8 4YF, United Kingdom
Office: +44 (0) 14 9487 1915
Mobile: +44 (0) 77 8532 8023
Fax: +44 (0) 14 9487 2988
E-Mail: jmills@btinternet.com
Help Desk: +44 (0)14 9487 6490
E-Mail: Euro-Service@holagent.com
NORWAY
BSE Knowledge Solutions - Norway
PO Box 139 Boenes
5849 Bergen Norway
Tel: +47 (55) 26 40 02 Fax: +47 (55) 20 34 35
E-mail: norway@holagent.com
SOUTH KOREA
ALK Corporation
#409, Wonhyo Building
1365-22 Seocho-Dong, Seocho-Gu
Seoul, 137-070, Korea
Tel: 011-82-2-3472-8463
Fax: 011-82-2-3472-8464
Help Desk: 011-82-2-3472-8463
E-Mail: alkc@nuri.net