Introduction

Much of the work done in executing the IUV is performed in the User Need, Requirements and Test Protocol modules. As the IUV set of tests is relatively small in number and executed infrequently, manual execution and evaluation is often preferred over automated testing.

The person(s) executing the IUV should have the following characteristics:

• Should be trained on your Quality Management System
• Should be trained on your IUV process
• Should be trained at minimum as a DOORS (release 9.3 or higher) end user
• (optional) May be a Software Quality Engineer
• (optional) May be the same person who authored/changed the requirements & tests

Test results are exported from DOORS as documents and approved as evidence. The approval process will be in accordance with your IUV process. Industry best practices have shown that minimum approvers generally consist of a Project Sponsor, Quality Engineer and Regulatory Affairs Representative.

Procedure

1. Learn what functionality is needed from your end users

Understanding what type of information management capability is needed is a key first step. The User Needs Module contains typical needs and attributes for a Requirements Management System. You may modify or add to the User Needs information in this module. DOORS keeps a record of all information and allows you to revert data back to a previous state.

2. Learn what capabilities are needed in DOORS in order to satisfy your User Needs

Multiple resources exist for learning about DOORS capabilities. You may choose to work with your local IBM Rational team or study the DOORS online documentation and readme.

The Requirements Module contains both Functional and Non-functional requirements for the DOORS system. You may modify or add to the Requirement information in this module. DOORS keeps a record of all information and allows you to revert data back to a previous state. Note that the Requirements in this module are pre-linked to applicable User Needs.

3. Review Test Plan and Cases in order to document your approach to validating DOORS

The Test Case module contains linked test cases with summary, input & output information and intercase dependency information. You may modify or add to the Test Case information in this module. DOORS keeps a record of all information and allows you to revert data back to a previous state.

4. Review Test Protocols in order to exercise the DOORS software

The Test Protocol module contains multiple linked protocols with placeholders for Test Engineer and Actual Result as well as traceability view(s) from Test Result -> User Need suitable for export. You may modify or add to the Test Protocol information in this module. DOORS keeps a record of all information and allows you to revert data back to a previous state.

5. Run the tests in the non-production sandbox

Open the Test Protocol module and choose the Test Execution Record (TER) View from the dropdown list.

Follow and execute the steps in each of the Protocol Steps sections, entering Actual Result, Pass_Fail and Tester information as appropriate.

6. Review the completed validation information with traceability back to User Needs.

One of the main strengths of DOORS is the ability to visualize multiple ‘levels’ of requirements in context. The Test Protocol module has a pre-created view called ‘Trace from Protocol to User Need’. This view shows the Test Protocol title linked to appropriate Test Case(s), Requirement(s) and User Need(s).

Select the ‘Trace from Protocol to User Need’ view from the drop down list.

7. Export the data to a document

Use Rational® Reporting for Document Generation to export data from formal modules to Microsoft Word, PDF, and HTML. For additional information about this capability go to the DOORS online help: http://publib.boulder.ibm.com/infocenter/doorshlp/v9/topic/com.ibm.doors.requirements.doc/topics/c_rpeexporting.html

Select File->Export->Document Generation->Configure Module from the module menu:

Define applicable header and logo information and then press Create:

Select File->Export->Document Generation->Microsoft Word from the module menu. Select the appropriate Export Options from the Export To Word pop up and then Click Export:

This traceability export may be included as part of your overall IUV document submission.