Traceability is a key project function that is usually maintained as part of the project co-ordinator’s duties. It is a living document that should be updated and maintained throughout the project lifecycle as change requests and decision requests are created and approved or declined where they have an impact on the requirements… PREPARE BASELINE REQUIREMENTS FOR TRACEABILITY Purpose To prepare the traceability matrix, documenting the requirements identified in the project plan and during the first stage of the project. The traceability matrix prepared in this task forms the baseline to be used in subsequent stages to confirm that all requirements have been met. Document Baseline Document the project requirements for both the application and the technical architecture. Confirm Requirements Ensure completeness by verifying that all of the requirements are included. See Also Manage Scope and Requirements Checklist TECHNIQUE - TRACEABILITY MATRIX Recommended Use Use a Traceability Matrix to: Method: HOW TO RELATE REQUIREMENTS TO A DELIVERABLE Need for Relating Requirements to a Deliverable Taking the time to cross-reference each requirement to a deliverable ensures that a deliverable is consistent with the system requirements. A requirement that cannot be mapped to a deliverable is an indication that something is missing from the deliverable. Likewise, a deliverable that cannot be traced back to a requirement may mean the system is delivering more than required. Use a Traceability Matrix to Match Requirements to a Deliverable There are many ways to relate requirements to the deliverables for each stage of the system life cycle. One method is to: Various traceability matrices may be utilized throughout the system life cycle. Useful ones include: Although the construction and maintenance of traceability matrices may be time-consuming, they are a quick reference during verification and validation tasks. Use a Traceability Matrix to: · verify and validate system specifications, · ensure that all final deliverable documents are included in the system specification, such as process models and data models, · improve the quality of a system by identifying requirements that are not addressed by configuration items during design and code reviews and by identifying extra configuration items that are not required. Examples of configuration items are software modules and hardware devices, · provide input to change requests and future project plans when missing requirements are identified, · provide a guide for system and acceptance test plans of what needs to be tested. Taking the time to cross-reference each requirement to a deliverable ensures that a deliverable is consistent with the system requirements. A requirement that cannot be mapped to a deliverable is an indication that something is missing from the deliverable. Likewise, a deliverable that cannot be traced back to a requirement may mean the system is delivering more than required. Use a Traceability Matrix to Match Requirements to a Deliverable There are many ways to relate requirements to the deliverables for each stage of the system life cycle. One method is to: · create a two‑dimensional table, · allow one row for each requirements specification paragraph (identified by paragraph number from the requirements document), · allow one column per identified configuration item (such as software module or hardware device), · put a check mark at the intersection of row and column if the configuration item satisfies the stated requirement.
USEFUL TRACEABILITY MATRICES
USEFUL TRACEABILITY MATRICES
Various traceability matrices may be utilized throughout the system life cycle. Useful ones include:
· Functional specification to requirements document: It shows that each requirement (obtained from a preliminary requirements statement provided by the customer or produced in the Concept Definition stage) has been covered in an appropriate section of the functional specification.
· Top level configuration item to functional specification: For example, a top level configuration item, Workstation, may be one of the configuration items that satisfies the function Input Order Information. On the matrix, each configuration item would be written down the left hand column and each function would be written across the top.
· Low level configuration item to top level configuration item: For example, the top level configuration item, Workstation, may contain the low level configuration items Monitor, CPU, keyboard, and network interface card.
· Design specification to functional specification verifies that each function has been covered in the design.
· System test plan to functional specification ensures you have identified a test case or test scenario for each process and each requirement in the functional specification.
Although the construction and maintenance of traceability matrices may be time-consuming, they are a quick reference during verification and validation tasks.
No comments:
Post a Comment