Introduction

This tool mentor describes how to develop and maintain the Validation Plan held in DOORS.

Create Structure for Validation Plan

Open the Validation Plan

Review the structure of the provided template and make changes to create a structure that is appropriate for the current project.

1. Examine the structure of the Validation Plan module
2. Determine if the overall structure is correct and make necessary changes

Create Content for Introductory Sections

Follow the guidance in the module to populate the introductory sections.

1. Set the view to "01 - Guidance"
2. Create content in the first two sections as indicated by the Guidance column.

Create Content for Test

Create objects in the module to describe the conduct of the validation process.

1. Open the Validation Plan (if not already open).
2. Set the view to "01 - Guidance"
3. Identify all participants and describe them in Section 3.1
4. Identify all locations to be used in the validation process and define them in Section 3.2
5. Identify all common configurations to be used in the validation process and define them in Section 3.3
6. Identify all specialist resources to be used in the validation process and define them in Section 3.4
7. Identify all documents to be referenced in the validation process and define them in Section 3.5
8. Define the way in which the test and other validation activities will be carried out and document this in Section 3.6

Create content for Test Cases

Create objects in the module to describe the test Cases.

1. Open the Validation Plan (if not already open).
2. Set the view to "01 - Guidance"
3. Create enough copies of the Test Case subsection (initially this is numbered 4.1, but this may change if test cases have already been created) for all of the test cases
4. Give each Test Case a unique name (level 2 heading)
5. Enter content into each of the other sections (under the level 3 headings) according to the guidance

Create traceability

Create links from the test cases to the requirements being tested and the relevant Use Cases.

Stakeholder-level Traceability

1. Open the Validation Plan (if not already open) and set the view to "02 – Associated Stakeholder-level Information"
2. Open the Stakeholder Requirements module (if not already open) and set the view to “10 – Associated Test Cases”
3. Open the Use-Case Model (if not already open) and set the view to “03 – Associated Test Cases”
4. Create links to relevant Stakeholder Requirements and Use Cases

System-level Traceability

1. Open the Validation Plan (if not already open) and set the view to "03 – Associated System-level Information"
2. Open the System Requirements module (if not already open) and set the view to “06 – Test Cases”
3. Open the Executable Use-Case Model (if not already open) and set the view to “03 – Associated Test Cases”
4. Create links to relevant System Requirements and System Use-Case Blocks

Subsystem-level Traceability

1. Open the Validation Plan (if not already open) and set the view to "04 – Associated Subsystem-level Information"
2. Open the relevant Subsystem Requirements modules (if not already open) and set the view to “06 –Test Cases”
3. Open the System Architectural Model (if not already open) and set the view to “03 – Associated Test Cases”
4. Create links to relevant Subsystem Requirements and Use Cases

Maintain the Validation Plan throughout the Lifecycle

As change requests are received, update appropriate sections as above. To view the history of changes for the module, use File -> Module Properties -> History. To view the history of changes for a single object, use Edit -> Object -> Properties -> History.

DOORS provides extensive tools to manage traceability, for example for impact and coverage analysis. For more assistance, see "Tracking changes and traceability" in the online DOORS Help file.