Scribd Logo
Upload

Welcome to Scribd!

  • 68 views

    Requirement Traceability

    Uploaded by

    Sana Arshad
    This document discusses requirement traceability, which allows requirements to be traced throughout the development lifecycle. It defines requirement traceability and explains why it is important for meeting goals, running tests, making decisions, and detecting risks. It describes the requirement traceability matrix, which maps requirements to test cases. There are three types of matrices: forward, backward, and bidirectional. The document outlines the benefits of requirement traceability and some common challenges.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Requirement Traceability

    Uploaded by

    Sana Arshad
    68 views16 pages
    This document discusses requirement traceability, which allows requirements to be traced throughout the development lifecycle. It defines requirement traceability and explains why it is important for meeting goals, running tests, making decisions, and detecting risks. It describes the requirement traceability matrix, which maps requirements to test cases. There are three types of matrices: forward, backward, and bidirectional. The document outlines the benefits of requirement traceability and some common challenges.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses requirement traceability, which allows requirements to be traced throughout the development lifecycle. It defines requirement traceability and explains why it is important for meeting goals, running tests, making decisions, and detecting risks. It describes the requirement traceability matrix, which maps requirements to test cases. There are three types of matrices: forward, backward, and bidirectional. The document outlines the benefits of requirement traceability and some common challenges.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    68 views16 pages

    Requirement Traceability

    Uploaded by

    Sana Arshad
    This document discusses requirement traceability, which allows requirements to be traced throughout the development lifecycle. It defines requirement traceability and explains why it is important for meeting goals, running tests, making decisions, and detecting risks. It describes the requirement traceability matrix, which maps requirements to test cases. There are three types of matrices: forward, backward, and bidirectional. The document outlines the benefits of requirement traceability and some common challenges.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 16

    SOFTWARE REQUIREMENT ENGINEERING

    REQUIREMENT TRACEABILITY
    Topics to be discussed:

     Introduction
     Requirement Traceability.
     Why RT is important?.
     Requirement Traceability Matrix.
     Types of RTM.
     Parameters.
     Benefits of Requirement Traceability.
     Challenges of RT.
    INTRODUCTION

     As we know Product complexity is growing at an exponential


    rate.
     As it does, requirements move between more and more
    departments and stakeholders throughout the course of the
    development process.
     Traceability helps product teams overcome one of the
    biggest challenges they face with requirements management.
    Requirements Traceability

     Requirements traceability is defined as "the ability to describe and


    follow the life of a requirement in both a forwards and
    backwards direction (i.e., from its origins, through its development
    and specification, to its subsequent deployment and use, and
    through periods of ongoing refinement and iteration in any of these
    phases)".
     Requirements traceability helps minimize the risk of negative
    outcomes and maximize productivity.
     Its benefits include greater team efficiency, easier regulatory
    compliance, and higher-quality products.
    Why Requirements Traceability Is Important?

     Meeting Goals.

     Running the Right Tests.

     Making Decisions.

     Detection of Risks.
    Requirement Traceability Matrix

     Requirement Traceability Matrix (RTM) is a document that


    maps and traces user requirement with test cases.
     It show the representation of requirement traceability.
     It captures all requirements proposed by the client and
    requirement traceability in a single document, delivered at
    the conclusion of the Software development life cycle.
    Types Of RTM

    There are three types of RTM:

     Forward Traceability.

     Backward Traceability

     Bidirectional Traceability.
    Continued….

    Forward traceability:

     This matrix is used to check whether the project


    progresses in the desired direction and for the right
    product.
     It makes sure that each requirement is applied to the
    product and that each requirement is tested thoroughly.
     It maps requirements to test cases.
    Continued…

    Backward or reverse traceability:

     It is used to ensure whether the current product remains on the right


    track.
     The purpose behind this type of traceability is to verify that we are not
    expanding the scope of the project by adding code, design elements,
    test or other work that is not specified in the requirements.
     It maps test cases to requirements.
    Continued…..

    Bi-directional traceability
    (Forward+Backward):

     This traceability matrix ensures that all


    requirements are covered by test cases.
     It analyzes the impact of a change in
    requirements affected by the defect in a work
    product and vice versa.
    Which Parameters to include in
    Requirement Traceability Matrix?

     Requirement ID
     Requirement Type and Description
     Test Cases with Status
    Benefits of requirements traceability?

    1. Management of the solution scope.


     Traceability allows each requirement to be associated with the
    appropriate business objectives, we can evaluate the value of
    each requirement.
     This allows us to effectively prioritize and avoid scope creep.

    2. Quick evaluation of potential changes.

     Good traceability allows us to evaluate the impact of a potential


    change quickly and easily.
    Continued….

    3. Reduced project risk.


    4. Promotes consistency between requirements.
     Identifying relationships between requirements and related items helps us to be
    more consistent and coherent.
     We can detect and correct inconsistencies quickly and use the same
    terminology.
    5. Allows monitoring and control across the lifecycle of
    requirements.
    Common challenges of
    requirement tracebility:

     Differing organizational viewpoints.


     Organization-wide adoption
     Cost of implementation
     Managing change
     Improper management tools
     Insufficient compliance framework
    THANK
    YOU

    You might also like