AttachmentC.doc

SOLICITATION ATTACHMENT #C: Salient features of a Requirement tool for FDA

Sorts Queries, and Parses:

1) The requirement tool shall use a project database for managing requirements in views with sort and query capabilities.

2) The tool should be able to support automatic parsing of documents.

Traceability, Change Management, and Track History:

3) The Traceability features of the tool should be capable of visually indicating how changes affect the project, helping perform impact analysis and make informed decisions for scope management or resource allocation.

4) The tool should assist in managing requirement changes more effectively and keep project on track.

5) The tool should be capable of capturing the change history for each requirement, providing an audit trail of the evolution of project requirements.

6) The integration with database and Word shall help organize and prioritize requirements, trace relationships between them, and track changes that affect them.

7) The tool should be able to manage change by adjusting for a change in all pertinent places

8) The tool should support that requirements are elicited from use cases providing a structured approach to user-system interaction.

9) The tool should be reflect changes in the requirements once the changes are made in use cases.

GMT Time Stamp:

1) The tool should be able to capture GMT time stamp to allow teams to work across different time zones.

Communication and Report:

1) The tool should be able to produce reports on requirements, documents, and several other project items.

2) The tool should be able to produce a simple web interface for organizing and launching reports.

3) The tool should be able to provide the capability to create new report templates.

4) The tool should be able to define multiple data sources per report to pull data from multiple projects.

5) The Tool should be able to validate the Software Requirements Specification (SRS) and Requirements Traceability Matrix (RTM) reports that are migrated from the legacy system (RequisitePro and SoDA) for accuracy.

6) The tool should be able to support communication among team members.

7) The tool should be able to migrate old reports created using SoDA.

Database Compatibility and Migration:

1) The tool should be able to migrate or upgrade the Access databases that were created before easily and smoothly with no problems.

2) The tool should provide database compatibility with the legacy requirement application repository (RequisitePro) for smooth data migration.

3) The tool should have standard feature available for migrating historical data without manipulating historical data such as requirement id and other keys.

4) The tool should be able to migrate the table relationships from the current system in use (RequisitePro).

5) The tool should be able to migrate the change history for each requirement, and audit trail of the evolution of project requirements from the current system in use (RequisitePro).

6) The tool should be able to migrate the existing customized processes for extracting the requirements from the current system in use (RequisitePro) into a Systems Requirements Specification artifact.

7) The tool should be able to migrate the existing Use Cases that are linked to requirements from the current system in use (Requisite Pro).

8) The tool should be able to support generation of test cases, facilitated by the integrated suite Requirements organized into packages stored in a database. From different views of the database, attributes of priority, status, difficulty and version number can be assigned.

9) The tool should be compatible to Oracle database version 10.2 release R2 Web Interface:

1) The tool should provide friendly User Interface design graphics.

2) The tool should provide search option from the web.

3) The tool should be able to support web access to the information stored in the database.

4) The tool should be compatible with IE 7 and IE 8 web browser.

5) The tool should provide user manuals online or hard copies.

6) The tool should have a user friendly web interface for admin functionality such as user management, access management, security management, project management etc.

Web Word authoring:

1) The tool should be able to integrate with Microsoft Word.

2) The tool should be able to edit and save Word documents while working online.

3) The tool should be able to create, delete, and modify requirements in Word documents.

4) The tool should be able to create requirements of any requirement type in the document.

5) The tool should be able to view and edit requirement properties from within the document, as in the Windows native client.

6) The tool should be able to establish parent and child relationships while working in the document.

Feature parity between the client application and the Web Interface:

1) The tool should be able to change the types of requirements from the Web.

2) The tool should be able to show the column requirement name in text in Traceability Matrix views.

Enhanced package security:

1) The tool should provide the Administrators set package permissions for user groups.

2) The tool should allow update, create, or delete permissions to requirements, documents, views, and child packages.

3) The tool should provide security to prevent inadvertent or malicious modifications to information.

4) The tool should offer single and multiple concurrent users.

FIPS-compliant encryption:

1) The tool should provide database password encryption that it complies with the Federal Information Processing Standard (FIPS).

2) The tool should protect accessing LDAP server by a FIPS-compliant password encryption system.

Integrations:

1) The tool should be capable of integration with Rational Suite products. FDA uses Rational products such as IBM Rational TestManager, IBM Rational SoDA, and IBM Rational ClearQuest and Robot. A seamless integration with all Rational suite is a must to keep the entire project team in sync and improve team productivity.

2) The tool should be able to integrate with Microsoft Word for creating and maintaining requirements documents that are linked to the Oracle or Access database for real-time updates to requirements from within documents.

3) The tool should be able to accept the templates and macros developed for use with legacy (RequisitePro) tool.

4) The tool should be able to keep the original requirement IDs from the legacy (RequisitePro) tool and continuity with requirement IDs and traceability of the legacy (ReqPro) tool.

5) The tool should be able to support the reading of requirements from external tools.

6) The tool should be able to support analysis of existing documentation.

7) The tool should allow put documents in an “offline” mode and worked on them outside of Requirement tool and then merge them back in.

Baseline:

1) The tool should be able to baseline requirements document and then compare different baselines.

2) The tool should allow viewing a single baseline using the same view format as that for Compare baselines. Only a single baseline should be displayed.

Support for rich text through Web:

1) The tool should be able to retain font and style enhancements and embedded images for Microsoft word documents when displayed on the web.

2) The tool should be able to support all views in full rich text.

Help System for the Web:

1) The tool should provide a help system that navigation tree, an index, and search capability, and provides new content on reporting, and Web Word authoring.

Help System the client for Windows:

1) The tool should provide a help system for the application client for Windows.

User Defined Templates and Requirement Types:

1) The tool should provide user defined templates Requirements project templates.

2) The tool should provide User-defined requirement types to help organizing requirements into various categories, and making the requirements easier to understand and report. Each requirement type should have a unique set of attributes associated with it (such as priority, status and risk) to weigh each requirement and facilitate scope management.

3) The tool should be able to support the generation of the SRS in standardized formats

Graphical Representation:

1) The tool should be able to capture or generate graphical representations (system architecture,analysis graphs, tables, etc.)