IBM Software Group Traceability From Need To Solution

® 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) 4 "Testing requirements should be traceable to the system/software requirements and design" 4 " A traceability analysis should be conducted to verify that the software design implements all of the software requirements " § IEEE 4"[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 4 "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) 4 REQUIREMENTS MANAGEMENT SP 1. 4 -2 - Maintain Bi-directional Traceability of Requirements

IBM Software Group 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+1 #n+2 Iterations Iter. #m+1

IBM Software Group Rational Integration and Workflow XDE, Rose Business Model Requisite. Pro, XDE, Rose Requireme nts & Use Cases XDE, Rose Model Rose /RQA, XDE, Rose + Test RT, Purify+ IDE Unit Code Testing Test. Manager Robot, Test RT Test. Manager Test Plan Test Cases System Testing Test Results Clear. Quest Defects Common Process and Guidance – Rational Unified Process, Rational Developer Networ Progress Metrics and Reporting – So. DA, Project. Console Software Configuration Management – Clear. Case, Clear. Quest, Rational Suite Content. Studio

IBM Software Group Integrate Requirements Across Tools and Teams Enhancement Requests Rational Clear. Quest View requirement origin Requirements input Requirement modeling Track flow of events Requirements Stakeholde rs Use Cases Rational Rose Developers Rational Requisite. Pro Test Cases Baselines Team Rational Test. Manager Test early Testers So. DA Versioning MS Proje ct Rational Clear. Case Projec t Admin

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

IBM Software Group Requirement Specifications in MS Word - Vision Document

IBM Software Group Clearly Present Requirements: Word and Views Microsoft Word ü Familiar interface (Word) ü Requirement context ü Facilitated review Database ü Requirement packages ü Priority lists ü Reports 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 Communicate the Impact of Requirement Changes

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

IBM Software Group Rational Integration and Workflow XDE, Rose Business Model Requisite. Pro, XDE, Rose Requireme nts & Use Cases XDE, Rose Model Rose /RQA, XDE, Rose + Test RT, Purify+ IDE Unit Code Testing Test. Manager Robot, Test RT Test. Manager Test Plan Test Cases System Testing Test Results Clear. Quest Defects Common Process and Guidance – Rational Unified Process, Rational Developer Networ Progress Metrics and Reporting – So. DA, Project. Console Software Configuration Management – Clear. Case, Clear. Quest, Rational Suite Content. Studio

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 Requirements Rational Requisite. Pro Rational Clear. Quest What. Test. Manager to test? Rational Test cases Requirements Defects / RFEs

IBM Software Group Traceability in IBM Rational Test. Manager

IBM Software Group Traceability to Requirements in Clear. Quest

IBM Software Group Requisite. Pro - Trace To Need (Origin) in Clear. Quest

IBM Software Group Rational Integration and Workflow XDE, Rose Business Model Requisite. Pro, XDE, Rose Requireme nts & Use Cases XDE, Rose Model Rose /RQA, XDE, Rose + Test RT, Purify+ IDE Unit Code Testing Test. Manager Robot, Test RT Test. Manager Test Plan Test Cases System Testing Test Results Clear. Quest Defects Common Process and Guidance – Rational Unified Process, Rational Developer Networ Progress Metrics and Reporting – So. DA, Project. Console Software Configuration Management – Clear. Case, Clear. Quest, Rational Suite Content. Studio

IBM Software Group