Blog

Enterprise Level Deployment of Delphix - Requirements Traceability Matrix

Thumbnail
By the time we build the Requirements Traceability Matrix we should have already completed the Goals and objectives of the Delphix implementation project as well as completed the Requirements Analysis.

By the time we build the Requirements Traceability Matrix we should have already completed the Goals and objectives of the Delphix implementation project as well as completed the Requirements Analysis. Which means the Requirement Traceability Matrix should be a simple add on to those two steps and perhaps a method for keeping focus on any outstanding GAP solutions. The matrix you design should provide a convenient mechanism to visually track requirements, to solutions, to validation to completion. The purpose of the RTM

  • All requirements are addressed by architecture, design development and quality assurance testing; and
  • No additional requirements are included.

The picture below is a sample of what a Delphix requirements traceability document would look like. The full document template will be made available at the conclusion of my Blog series or sooner if I get requests to provide them.

Tracking and Validating the Requirements

Who is responsible for requirements traceability?
 

  • The requirements analysis team is responsible for ensuring that all requirements are tracked thru the appropriate design, development and testing phases;
  • The data architect, or technical lead, is responsible for ensuring that no extra requirements are included in design documentation;
  • Each designer is responsible for completing a satisfaction of requirements section for each design specification indicating which requirements are addressed by the specification;
  • The peer review process should ensure that no extra requirements are included in development code; and
  • The test manager is responsible for ensuring that all requirements are address by test cases and that test cases are not created to test for things that are not required.

As you manage the document for requirements completion and GAP closures keep in mind you are not going to check all the details--You need to rely on the architects, engineers, and quality assurance team to verify the details as mentioned above.

Next Installment Post - Determining the Integration, Resource and System Dependencies