1 / 27

Traceability From Need To Solution What, Why and How

Traceability From Need To Solution What, Why and How. Tammy Lavi Alon Bar-Ner. Agenda. Traceability: why it is needed Requirement type, attribute, History Management tools: Coverage, Status, Impact, Suspect Requirement Life Cycle and Tools

yale
Download Presentation

Traceability From Need To Solution What, Why and How

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. Traceability From Need To SolutionWhat,Why and How Tammy Lavi Alon Bar-Ner

  2. Agenda • Traceability: why it is needed • Requirement type, attribute, History • Management tools: Coverage, Status, Impact, Suspect • Requirement Life Cycle and Tools • Demo: Implementing traceability in the Rational toolset

  3. Why Traceability in Software? Because It's a Good Idea. • Reduce rework by not having the same argument twice • Be more efficient by knowing what to do when a change happens • Do better planning because you can understand the impact of a change • Be sure that decisions made later in the project are consistent with those made earlier • Ensure that the systems you delver meet the original needs of the stakeholders

  4. Why Traceability in Software? Somebody Forces You. • FDA (U.S Food and Drug Administration) • "Testing requirements should be traceable to the system/software requirements and design" • " A traceability analysis should be conducted to verify that the software design implements all of the software requirements " • IEEE • "[An] audit is held prior to software delivery to verify that all requirements specified in the Software Requirement Specification have been met."2 • ISO 9001 • "The supplier shall establish and maintain documented procedures to control and verify the design of the product in order to ensure that the specified requirements are met." • CMM/CMMI (Capability Maturity Model) • REQUIREMENTS MANAGEMENT SP 1.4-2 - Maintain Bi-directional Traceability of Requirements

  5. Unified Process Phases Process Workflows Inception Elaboration Construction Transition Business Modeling Requirements Analysis & Design Implementation Test Deployment Supporting Workflows Configuration Mgmt Management Environment Preliminary Iteration(s) Iter.#1 Iter.#2 Iter.#n Iter.#n+1 Iter.#n+2 Iter.#m Iter.#m+1 Iterations

  6. RequisitePro, XDE, Rose XDE, Rose + IDE Rose /RQA, Test RT, Purify+ XDE, Rose XDE, Rose TestManager Robot, Test RT TestManager TestManager TestManager ClearQuest System Testing TestResults Test Cases Test Plan Defects – Rational Unified Process, Rational Developer Network – SoDA, ProjectConsole – ClearCase, ClearQuest, Rational Suite ContentStudio Rational Integration and Workflow BusinessModel Requirements & Use Cases Unit Testing Code Model Common Process and Guidance Progress Metrics and Reporting Software Configuration Management

  7. Rational Rational Rational Rational Rational RequisitePro ClearCase Rose ClearQuest TestManager Integrate Requirements Across Tools and Teams Enhancement Requests Use Cases View requirement origin Requirement modeling Requirements input Track flowof events Requirements Stakeholders Developers Test Cases Baselines Team Versioning Test early Testers MS Project ProjectAdmin SoDA

  8. Requirements are capabilities and objectives to which the software or system you are building must conform. What is a Requirement? • Requirements are found in: • Vision documents • Marketing requirements • Designs • Functional specifications • Product requirements • QA plans • Business rules • Test cases • Use cases • Prototypes • And more...

  9. Requirement Specifications in MS Word - Vision Document

  10. Clearly Present Requirements: Word and Views Microsoft Word Database • Requirement packages • Priority lists • Reports • Familiar interface (Word) • Requirement context • Facilitated review Freedom of Word, Power of a database: Easy to use

  11. Analyzing Requirements

  12. Manage Requirements: Queries and Reports

  13. Requirement Specifications in MS Word - Use Case Document

  14. Manage Requirements: Traceability

  15. Traceability TreeChange Impact

  16. Communicate Requirement Changes: Suspect Links

  17. Impact of Requirement Change • Suspect links pinpoint impact of requirement change to other requirements, design (Rational Rose XDE) and test cases Understand and Communicate the Impact of Requirement Changes

  18. Rational RequisitePro Everybody Needs Access to Requirements QA and Test Developersand Designers Tech Writers and Docs Analysts Executives Project Managers

  19. RequisitePro, XDE, Rose XDE, Rose + IDE Rose /RQA, Test RT, Purify+ XDE, Rose XDE, Rose TestManager Robot, Test RT TestManager TestManager TestManager ClearQuest System Testing TestResults Test Cases Test Plan Defects – Rational Unified Process, Rational Developer Network – SoDA, ProjectConsole – ClearCase, ClearQuest, Rational Suite ContentStudio Rational Integration and Workflow BusinessModel Requirements & Use Cases Unit Testing Code Model Common Process and Guidance Progress Metrics and Reporting Software Configuration Management

  20. Traceability in XDE

  21. Quick Access to Up-to-Date Project ArtifactsAvoid Data redundancy by sharing artifacts across tools Requirements Rational RequisitePro Rational ClearQuest What to test? Rational TestManager Testcases Defects / RFEs Requirements

  22. Traceability in IBM Rational TestManager

  23. Traceability to Requirements in ClearQuest

  24. RequisitePro - Trace To Need (Origin) in ClearQuest

  25. RequisitePro, XDE, Rose XDE, Rose + IDE Rose /RQA, Test RT, Purify+ XDE, Rose XDE, Rose TestManager Robot, Test RT TestManager TestManager TestManager ClearQuest System Testing TestResults Test Cases Test Plan Defects – Rational Unified Process, Rational Developer Network – SoDA, ProjectConsole – ClearCase, ClearQuest, Rational Suite ContentStudio Rational Integration and Workflow BusinessModel Requirements & Use Cases Unit Testing Code Model Common Process and Guidance Progress Metrics and Reporting Software Configuration Management

More Related