Updated July 6, 1998
Outline
1. Capturing Requirements/Identification
1.1 Input document enrichment/analysis
Not supported in this version.
1.1.1 Input document change/comparison analysis
Not supported in this version.
1.2 Automatic parsing of requirements
The user defines keywords and the tool automatically finds requirements that meet the keyword specifications. FULL
1.3 Interactive/semi-automatic requirement identification
Requirements are identified based on keywords or based on highlighting text with the mouse. Requirements may be identified and extracted automatically or identified and extracted based on interaction with the user. FULL
1.4 Manual requirement identification
Requirements are manually identified with mouse highlighting by the user. FULL
1.5 Batch mode operation
Import capability allows for updating of requirements from external sources. FULL
1.5.1 Batch-mode document/source-link update
Not supported in this version.
1.6 Requirement classification
XTie-RT has 3 kinds of attributes to help classify requirements - Single-value attributes, Multi-value attributes, and Text value attributes. FULL
2. Capturing system element structure
2.1 Graphically capture systems structure
A graphical view of the system structure may be displayed to show the relationships between documents and their hierarchical structure. FULL
2.2 Textural capture of systems structure
Requirement Links are displayed textually to show the relationships between requirements and the system structure. FULL
3.1 Requirements derivation (req.to req. to analysis/text)
New requirements may be manually created using the requirement editor. A new requirement may also inherit data from the requirement it was derived from and at the same time a link may be created. FULL
3.2 Allocation of performance requirements to system elements (weight, risk,cost,etc)
Attributes may be created and each requirement assigned an individual value to represent items such as weight, risk, cost. These requirements may also linked to to independent data. FULL
3.3 Bi-directional requirement linking to system elements.
XTie-RT supports the Parent/Child links which are up/down links and Peer Links which is a parallel link. FULL
3.4 Capture of allocation rationale, accountability, test/validation, criticality, issues, etc.--if so show and what mechanism does it use?
The use of attributes allows the user to capture the allocation of rationale, accountability, test/validation. criticality, issues, etc. With three types of attributes (Single-value, Multi-value, and Text Value) all possibilities are covered. FULL
4.1 Identify inconsistencies (orphans,...if so what kind of...)
XTie-RT can identify all requirements with no parent links, child links or peer links. FULL
4.2 Visibility into existing links from source to implementation
Links or lack of links may be shown from the requirements in the source document all the way to implementation by viewing the actual requirements on screen or on printed report. FULL
4.3 Verification of requirement (was it done, how was done)
With XTie-RT, all the attributes values for a requirement and its links may be viewed in one window to show verification of a requirement. FULL
4.4 Requirement performance verification from system elements (roll up of actuals)
No Supported in this Version
5.1 History of requirement changes, who, what, when, why, how
A history log may be enabled for each document to log all additions, changes, and deletions of a requirement. The change made, who made the change and the date and time the change occurred by be logged. Why and How would be logged in a text valued attribute. FULL
5.2 Baselining/Version Control
Baselines of Documents may be made and kept for viewing and reporting. Baselines may not be changed. FULL
5.3 Access Control (modification, viewing, etc)
Five (5) levels of access control are supported. Access privileges may even be set to allow the user full read/write privilege to everything with exception to specified attributes, where he will be . FULL
6. Documents and other output media
6.1 Standard specification output (if so, what kind)
6.2 Quality and consistency checking (spell, data dictionary)
Pull-down lists may be created for attribute names, values, and paragraphs which eliminates the need for some typing, but spell and data dictionary do not exist in this version. PARTIAL
6.3 Presentation Output
Textual reports may be generated thru XTie-RT and graphical outputs may be generated using Crystal Reports, a product of Seagate, and imported into XTie-RT for use in directly in the application. FULL
6.4 Custom output features and markings (user definable tables, figures, security markings ...)
Report Titles and column headings may be defined using XTie-RT. Headers, footers and graphics may be created using Crystal Reports, a product of Seagate, and imported into XTie-RT. FULL
6.5 WYSIWYG previewing of finished output
All output may be previewed on the screen just as it will appear on paper. FULL
6.6. Status Reporting
6.6.1 Requirement progress/status reporting
The use of attribute values allows for status and progress reporting. FULL
6.6.3 Other ad hoc query’s and searches
Working sets are used to do ad hoc queries and searches. These are user-defined and may be saved for use at a later time. Find is also available for text searches. FULL
7.1 Support of concurrent review, markup, and comment
XTie-RT allows up to 128 concurrent users. FULL
7.2 Multi-level assignment/access control
XTie-RT provides several levels for access control. Access control may be set for each user allowing read/write for an entire project, read/write for specified documents only, read only for specified documents, or no access. In the multi-user environment, simultaneous users are blocked at the requirement level. FULL
8.1 Inter-tool communications
8.1.1 Interfaces to other tools _______?
XTie-RT accepts imports of data in any delimited format. Exports may be done to other tools such as WORD, EXCEL, LOTUS. Data may also be exported to delimited files so that they may be imported by other tools. XTie-RT also accepts custom report formats created in Crystal Reports. FULL
8.1.2. External Applications Program Interface Available
Not supported in this version.
8.1.3 Support Open database system (standard query access)
Queries on database items are done within XTie-RT. NO
8.1.4 Import of existing data from various standard file formats?
XTie-RT accepts data imported in any delimited format, this includes all common third party applications such as WORD, EXCEL, LOTUS, etc. FULL
8.2 Intra-tool communication
8.2.1 Exchange of information between same-tool different installations
Databases (including links and attributes) from one installation of XTie-RT may be exported and then imported into another installation of XTie-RT. The data may append an existing database or replace an existing database. FULL
8.2.2 Consistency/comparison checking between same-tool datasets
Consistency/comparison checking may be done by manually creating links between common requirements then finding all requirements that are not linked. PARTIAL
9.1 Single user/multiple concurrent users
XTie-RT is available in a stand-alone or multi-user version. The multi-user version supports from 1 to 128 concurrent users. FULL
9.2 Multiple platforms/Operating Systems
The XTie-RT server is supported on Windows 95, Windows NT, and Sun Solaris. The XTie-RT client is supported on Windows 95 and Windows NT. FULL
9.3 Commercial vs. unique database
XTie-RT is designed around a proprietary database. FULL
9.4 Resource requirements
9.4.1 Memory requirements
Recommended amount for OS
9.4.2 CPU requirements
PC (486 minimum) for client and server
9.4.3 Disk space requirements
8 Mbytes minimum
10.1 Doing one thing while you are looking at another
XTie-RT allows the user to perform simultaneous tasks. For example, a link may be created between two requirements, while also viewing data in another document that is unrelated. FULL
10.2 Simultaneous update of open views
All affected views are updated when a change occurs. For example, an attribute value may be renamed and all open views containing that value will be updated simultaneously. FULL
10.3 Interactive graphical input/control of data
Not supported in this version
10.4 Which window’s standards do you follow?
Windows 95
10.5 Executable via scripts (recordable) or macros?
Working set queries and report formats may be saved and used at a later time. FULL
11 Standards-which one’s do you comply with?
XTie-RT was developed by a ISO9000 compliant and SEI CMM company. It also complies with many other standards. FULL
12.1 Warrantee
XTie-RT offers a 30-day full satisfaction money-back guarantee. FULL
12.2 Network License policy
XTie-RT is licensed with a registration key that must be paired with a license key in order to operate. FULL
12.3 Maintenance and upgrade policy
Major releases featuring at least two significant new features will occur every 6-12 months for an upgrade charge. There is no maintenance fee. FULL
12.4 On-line help
Full reference manual is available as on-line help. FULL
12.5 Internet access/WWW home page location
Technical and Pricing information is available on the XTie-RT web page. Also available are an automated demo of XTie-RT and point releases. These may be downloaded. Website: " http://www.tbe.com/products/xtie " FULL
12.6 Phone support
An 800 number and direct phone numbers to technical staff are provided for support on M-F 8am-5:30pm Central time. FULL
13.3 Recommended training time
Formal training is not required. Using the tutorial, which is included with the software, a user can learn the tools basics in less than one day. FULL
14. What other features are important?
XTie-RT supports a Multi-value attribute which allows a user to assign multiple values to one requirement.
XTie-RT supports a point and click query mechanism. Users are not required to learn complex SQL statements.
XTie-RT is built on a proprietary database which places no limits on the number of requirements and response time is excellent even with very large databases.
XTie-RT is easily applied to any methodology.
Cost effective prices allow for more users on a project.
XTie-RT is easy to learn and use while remaining full featured.
Return to INCOSE Home
Content Owner: TDWG Chair
Contact us at info@incose.org
Copyright 1998-2004 International Council on Systems Engineering
Last Modified: September 22, 2004