1 / 14

Requirement Bi-directional Traceability Matrix

Requirement Bi-directional Traceability Matrix . BY: KANDIKANTI ASHOK BAGANSHI STUDENT ID: 102062. INTRODUCTION. This software is used to maintain the mapping from the requirement through design, coding and testing.

norina
Télécharger la présentation

Requirement Bi-directional Traceability Matrix

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement Bi-directionalTraceability Matrix BY: KANDIKANTI ASHOK BAGANSHI STUDENT ID: 102062

  2. INTRODUCTION • This software is used to maintain the mapping from the requirement through design, coding and testing. • Requirement Bi-Directional Traceability Matrix is used for automating the requirement management process. • Traceability is used to ensure that the right products are being built at each phase of the software development life cycle, to trace the progress of that development and to reduce the effort required to determine the impacts of requested changes.

  3. background • The requirement volatility is a major challenge in making the changes for the requirement. • A research group report says that 31% of all the projects are cancelled before they ever got completed and nearly 53% of the project costs almost twice their original estimates due to lack of proper requirement management.

  4. challenges • Requirements might be missed at any stage of development. • Requirement may not be properly implemented. • When any of the requirements gets deleted, we may not know the area affected.

  5. V –PROCESSMODEL Requirement Acceptance Test cases Design Functional Test cases Coding Unit Test cases

  6. Software Execution Process as per v-process Model TESTING REQUIREMENTS DESIGN CODING UT FT AT Acceptance Test Cases Functional Test Cases Unit Test Cases Test cases

  7. Software Execution Process as per v-process Model Software development process of RBDTM have the following phases: • Requirement • Design • Coding • Testing The objective is to ensure that each requirement is implemented in the product and that each requirement is properly tested.

  8. Features of RBDTM • Mapping • Forward Traceability • Reverse Traceability • Changes in the Requirements

  9. Forward Association Mechanism: Design 1...n Requirement 1...n Coding 1...n Testcases

  10. Forward Association Mechanism • Forward Traceability is the step by step process in the forward direction from Requirement phase to Testing phase.

  11. Reverse Association Mechanism Design n…1 n…1 Coding Requirements n…1 Testcases

  12. Reverse Association Mechanism‏ • Reverse Traceability is the step by step process in the Backward direction from Testing phase to Requirement phase.

  13. RBDTM Web Client (Browser) System Design • The application of this system comes under the domain of software engineering. Requirement Bi-Directional Traceability Matrix is used for automating the requirement management process. • Web client is an external interface which is used to interact with our system to store and update the data.

  14. CONCLUSION • Requirement bidirectional traceability matrix software is mainly to manage the requirements properly in a automated way. It ensures that all the requirements are mapped and the effected sections when a change is made it is shown so that the problems that are occuring due to improper requirement management system are reduced.

More Related