book

Requirements Management Using IBM Rational RequisitePro

Name: Requirements Management Using IBM Rational RequisitePro
Author: Ph.D. Peter Zielczynski
ISBN: 9780321383006

by Ph.D. Peter Zielczynski

December 2007

Intermediate to advanced

360 pages

English

IBM Press

Read now

Unlock full access

Copyright
Dedication
IBM Press
Rational and Software DevelopmentComputingInformation ManagementWebsphereLotusOpen SourceBusiness Strategy & Management
Foreword
Preface
What This Book Is AboutHow This Book Is OrganizedThe Audience for This Book
Acknowledgments
About the Author
I. Overview
1. Requirements Management
1.1. Definition of a Requirement and a Stakeholder1.2. Requirements Pyramid1.3. Traceability between Requirements1.4. Characteristics of a Good RequirementUnambiguousTestable (Verifiable)Clear (Concise, Terse, Simple, Precise)CorrectUnderstandableFeasible (Realistic, Possible)IndependentAtomicNecessaryImplementation-free (Abstract)ConsistentNonredundantComplete1.5. An Overview of the Requirements Management ProcessEstablishing a Requirements Management PlanRequirements ElicitationDeveloping the Vision DocumentCreating Use CasesSupplementary SpecificationCreating Test Cases from Use CasesCreating Test Cases from the Supplementary SpecificationSystem Design1.6. SummaryReferences
2. Overview of RequisitePro
2.1. InterfaceExplorerViewsToolbar2.2. Word Workplace2.3. Documents2.4. Requirements2.5. Summary

II. Requirements Management Activities
3. Establishing a Requirements Management Plan
3.1. When the RMP Is Created3.2. Decisions That May Be Documented in an RMPWill an RM Tool Be Used?What Requirement Types Will Be Tracked in the Project?What Are the Attributes of These Requirements?Where Will the Requirements Be Created—in the Database Only or in the Documents?Between Which Requirements Do We Need to Implement Traceability?What Documents Are Required?Which Requirements and Documents Will Be Used as a Contract with Customers?If Part of the Project Is Outsourced, What Requirements and Documents Will Be Used as a Contract with a Vendor?Will We Follow the Rational Unified Process or Some Other Methodology?Does the Customer Need Any Specific Documents to Comply with His Development Process?How Will Change Management Be Implemented?Will the Whole System Be Stored in One RequisitePro Project or Spread Among Many Projects?What Process Will Guarantee That All Requirements Were Implemented and Tested?Which Requirements or Views Do We Need to Generate Reports?3.3. Sample Requirements Management Plan3.4. SummaryReference
4. Setting up the Project
4.1. Setting up a RequisitePro ProjectAdding Requirement AttributesChanging Values of Requirement AttributesImporting a Document4.2. Setting up a Rational Project4.3. Summary
5. Requirements Elicitation
5.1. Identifying Stakeholders5.2. Techniques of Requirements ElicitationInterviewsQuestionnairesWorkshopsStoryboardingRole PlayingDialog 1Dialog 2Brainstorming SessionsExampleUsing Affinity DiagramsPrototypingAnalyzing Existing DocumentsUse CasesObservation and Task DemonstrationAnalyzing Existing Systems5.3. Creating the Stakeholder Requests DocumentOpening a ProjectAdding a Document Type to the ProjectCreating a Stakeholder Requests Document5.4. Creating Requirements in RequisiteProAdding Requirements in DocumentsChanging Attributes of Requirement TypesAdding a Requirement from the ExplorerModifying a Requirement in the ExplorerDeleting a Requirement from the Explorer5.5. Using Views to Analyze RequirementsCreating the Attribute Matrix ViewOpening a ViewExporting a ViewQuerying Requirements5.6. SummaryReferences
6. Developing a Vision Document
6.1. The Structure of the Vision Document6.2. Deriving Features from Stakeholder Needs6.3. Attributes of Features6.4. Creating the Vision Document in RequisitePro6.5. Creating Features Requirements6.6. Traceability6.7. ViewsAccessing a Previously Created ViewSetting a Traceability LinkDeleting a Traceability LinkModifying Requirements in the ViewQueriesSuspect TraceabilityOther Operations on ViewsTraceability Tree6.8. SummaryReference
7. Creating Use Cases
7.1. Identifying Actors7.2. Identifying Use Cases7.3. Use Case Diagrams7.4. Structuring the Use Case ModelInclude RelationshipExtend RelationshipGeneralization Relationship Between Use CasesGeneralization Relationship Between Actors7.5. The Use Case Specification DocumentBrief DescriptionBasic FlowAlternative FlowsSpecial RequirementsPreconditionsPostconditionsExtension PointsContext DiagramActivity DiagramState Machine DiagramsScenarios7.6. Scenarios7.7. Use Cases in RequisiteProCreating the Use Case SpecificationCreating Requirements7.8. Creating a New Requirement Type in RequisitePro7.9. SummaryReferences
8. Supplementary Specification
8.1. Eliciting Supplementary Requirements8.2. Classification of Supplementary RequirementsFunctionalityUsabilityReliabilityPerformanceSupportabilityDesign ConstraintsImplementation RequirementsInterface RequirementsPhysical RequirementsDocumentation RequirementsLicensing and Legal Requirements8.3. Deriving Supplementary Requirements from Features8.4. Attributes of Supplementary RequirementsImportanceSatisfaction ShapeSharp Satisfaction ShapeMedium Satisfaction ShapeLinear Satisfaction Shape8.5. Entering Supplementary Requirements in RequisitePro8.6. Traceability to Supplementary RequirementsSetting the Type Attribute for FeaturesSetting TraceabilityQuerying Requirements8.7. SummaryReferences
9. Creating Test Cases from Use Cases
9.1. Creating Test CasesStep 1: Identify Variables for Each Use Case StepStep 2: Identify Significantly Different Options for Each VariableStep 3: Combine Options to Be Tested into Test CasesStep 4: Assign Values to Variables9.2. Business Rules9.3. Creating a New Document Type9.4. Adding Scenarios and Test CasesCreating a New PackageCreating a DocumentAdding Requirements from the Explorer9.5. Setting Traceability9.6. SummaryReferences
10. Creating Test Cases from Supplementary Requirements
10.1. Executing Selected Test Cases in Different Environments10.2. Adding an Additional Check to All Use Cases10.3. Checking and Modifying Specific Use Cases10.4. Performing the Exercise10.5. Checklist10.6. Analysis10.7. White-Box Testing10.8. Automated Testing10.9. Using Robot and Test Manager for Automated TestingRecording a VU ScriptHow to Run a Suite in Rational Test ManagerAnalyzing the Results10.10. SummaryReferences
11. Object-Oriented Design
11.1. System Design from Use Cases11.2. Using IBM Rational Rose for DesignCreating a New ModelCreating Class DiagramsModeling AssociationsCreating Sequence Diagrams11.3. Using IBM Rational Software Architect for DesignCreating a ProjectCreating a Use Case DiagramCreating a Class DiagramCreating a Sequence DiagramPublishing the Design11.4. SummaryReferences
12. Documentation
12.1. Documentation TypesInternal DocumentationTechnical DocumentationUser DocumentationMarketing Materials12.2. Documents Available in RequisiteProCreating a Document from an Available Document TypeAdding a New Document TypeCreating a New Document TypeImporting a Document12.3. Using IBM Rational SoDAGenerating a Report from RequisiteProGenerating a Report from SoDA12.4. SummaryReferences
III. Other Topics
13. Managing Projects
13.1. Printing the Project Summary13.2. RequisitePro File Types13.3. Archiving Projects13.4. Moving and Copying Projects13.5. Cross-Project Traceability13.6. SummaryReference
14. Requirements Management in the Rational Unified Process
14.1. The Rational Unified Process14.2. The Requirements Pyramid and RUPInceptionElaborationConstructionTransition14.3. The Requirements Pyramid and the Waterfall14.4. Moving from Waterfall to RUP Using the Requirements Pyramid14.5. SummaryReferences
IV. Review
15. Summary
15.1. Summary of the Pyramid Approach to the Requirements Management Process15.2. Advantages15.3. RequisitePro
Sample Requirements Management Plan
1. Introduction1.1. Purpose1.2. Scope1.3. Overview2. Tools, Environment, and Infrastructure3. Documents and Requirement Types3.1. Documents3.2. Requirement Types3.3. Traceability3.4. Requirements Attributes3.4.1. Attributes for FEATStatusPriorityBenefitEffortRiskStabilityTarget ReleaseAssigned ToReason3.4.2. Attributes for STRQ3.4.3. Attributes for UCActor3.4.4. Attributes for SUPL3.5. Reports and Measures

Content preview from Requirements Management Using IBM Rational RequisitePro

Chapter 6. Developing a Vision Document

The Vision document is one of the three most important documents created in RequisitePro (the other two are the Use Cases and Supplementary Specification documents). The Vision document contains the following:

A description of the problem being solved by the new system
A high-level description of the solution
A list of the system’s main features

The Vision document may serve as a contract between a customer and developers for the technical requirements. The purpose of the Vision document is to

Define the system’s boundaries
Identify constraints imposed on the system
Gain agreement with the customer on the scope of the project
Create a basis on which to define Use Cases and Supplementary Specification documents

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Just Enough Requirements Management: Where Software Development Meets Marketing

Publisher Resources

ISBN: 9780321383006Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Requirements Management Using IBM Rational RequisitePro

by Ph.D. Peter Zielczynski

Chapter 6. Developing a Vision Document

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.