IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner

IBM Software Group 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

IBM Software Group 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

IBM Software Group 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 Maintain Bi-directional Traceability of Requirements

IBM Software Group Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Phases Process Workflows Iterations Supporting Workflows Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration Mgmt Requirements ElaborationTransitionInceptionConstruction Unified Process

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

IBM Software Group Enhancement Requests Test CasesBaselines Use Cases Requirements Integrate Requirements Across Tools and Teams Requirements input Track flow of events Stakeholders Developers Team Requirement modeling Project Admin Testers Test early View requirement origin Rational RequisitePro Rational ClearQuest Rational Rose Rational ClearCase Rational TestManager Versioning SoDA MS Project

IBM Software Group 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... Requirements are capabilities and objectives to which the software or system you are building must conform.

IBM Software Group Requirement Specifications in MS Word - Vision Document

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

IBM Software Group Analyzing Requirements

IBM Software Group Manage Requirements: Queries and Reports

IBM Software Group Requirement Specifications in MS Word - Use Case Document

IBM Software Group Manage Requirements: Traceability

IBM Software Group Traceability Tree Change Impact

IBM Software Group Communicate Requirement Changes: Suspect Links

IBM Software Group 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

IBM Software Group Everybody Needs Access to Requirements Executives Project Managers Developers and Designers QA and Test Tech Writers and Docs Analysts Rational RequisitePro

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

IBM Software Group Traceability in XDE

IBM Software Group Quick Access to Up-to-Date Project Artifacts Avoid Data redundancy by sharing artifacts across tools What to test? Requirements Rational ClearQuest Rational RequisitePro Rational TestManager Test cases Requirements Defects / RFEs

IBM Software Group Traceability in IBM Rational TestManager

IBM Software Group Traceability to Requirements in ClearQuest

IBM Software Group RequisitePro - Trace To Need (Origin) in ClearQuest

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

IBM Software Group