Managing Software Requirements[c] A Use Case Approach
![Managing Software Requirements[c] A Use Case Approach](/icons/blank_book.jpg "Managing Software Requirements[c] A Use Case Approach"){kind=icon}
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
EAN: N/A
EAN: N/A
Year: 2003
Pages: 257
Pages: 257
- Managing Software Requirements: A Use Case Approach, Second Edition
- Table of Contents
- Copyright
- The Addison-Wesley Object Technology Series
- The Component Software Series
- Foreword
- The Rock Problem
- About This Book
- Preface to the Second Edition
- About the Second Edition
- Acknowledgments
- Preface to the First Edition
- Context
- Requirements Lessons from Building Software for Others
- Lessons from Building High-Assurance Systems
- Lessons from the Requirements Management Business
- Experiences at Rational Software
- Summary
- Introduction
- Chapter 1. The Requirements Problem
- The Goal of Software Development
- A Look at the Data
- The Root Causes of Project Success and Failure
- Summary
- Chapter 2. Introduction to Requirements Management
- Definitions
- Application of Requirements Management Techniques
- The Road Map
- Summary
- Chapter 3. Requirements and the Software Lifecycle
- Traditional Software Process Models
- The Iterative Approach
- Requirements in the Iterative Model
- Summary
- Chapter 4. The Software Team
- Software Development as a Team Activity
- The Case Study
- Summary
- Team Skill 1: Analyzing the Problem
- Chapter 5. The Five Steps in Problem Analysis
- Step 1: Gain Agreement on the Problem Definition
- Step 2: Understand the Root Causes-The Problem Behind the Problem
- Step 3: Identify the Stakeholders and the Users
- Step 4: Define the Solution System Boundary
- Step 5: Identify the Constraints to Be Imposed on the Solution
- Summary
- Looking Ahead
- Chapter 6. Business Modeling
- The Purpose of Business Modeling
- Using Software Engineering Techniques for Business Modeling
- From the Business Model to the Systems Model
- When to Use Business Modeling
- Summary
- Looking Ahead
- Chapter 7. Systems Engineering of Software-Intensive Systems
- What Is Systems Engineering?
- Requirements Allocation in Systems Engineering
- The Case Study: Systems Engineering for HOLIS
- Summary
- Team Skill 1 Summary
- Team Skill 2: Understanding User and Stakeholder Needs
- Chapter 8. The Challenge of Requirements Elicitation
- Barriers to Elicitation
- Summary
- Chapter 9. The Features of a Product or System
- Stakeholder and User Needs
- Features
- Summary
- Chapter 10. Interviewing
- Context-Free Questions
- Solutions-Context Questions
- The Moment of Truth: The Interview
- Compiling the Needs Data
- A Note on Questionnaires
- Summary
- Chapter 11. Requirements Workshops
- Accelerating the Decision Process
- Preparing for the Workshop
- Setting the Agenda
- Running the Workshop
- Summary
- Chapter 12. Brainstorming and Idea Reduction
- Live Brainstorming
- Idea Reduction
- Web-Based Brainstorming
- The Case Study: The HOLIS Requirements Workshop
- Summary
- Chapter 13. Storyboarding
- Types of Storyboards
- What Storyboards Do
- Tools for Storyboarding
- Tips for Storyboarding
- Summary
- Team Skill 2 Summary
- Team Skill 3: Defining the System
- Chapter 14. A Use Case Primer
- The Benefits of Use Cases
- Use Case Basics
- A Step-by-Step Guide to Building the Use-Case Model
- On Use Cases, Storyboarding, and User Interface Design
- The Case Study: The HOLIS Use Cases
- Summary
- Chapter 15. Organizing Requirements Information
- Organizing Requirements of Complex Hardware and Software Systems
- Organizing Requirements for Product Families
- On
- The Case Study: Organizing the HOLIS Requirements
- Summary
- Looking Ahead
- Chapter 16. The Vision Document
- Components of the Vision Document
- The Delta Vision Document
- Summary
- Chapter 17. Product Management
- The Role of the Product Champion
- The Product Manager in a Software Product Company
- Primary Activities for a Product Manager
- Supporting Activities
- The Product Champion in an ISIT Shop
- Summary
- Team Skill 3 Summary
- Team Skill 4: Managing Scope
- Chapter 18. Establishing Project Scope
- The Problem of Project Scope
- The Hard Question
- The Requirements Baseline
- Setting Priorities
- Assessing Effort
- Adding the Risk Element
- Reducing Scope
- The Case Study: Scope Management for HOLIS
- Summary
- Chapter 19. Managing Your Customer
- Engaging Customers to Manage Their Project Scope
- Communicating the Result
- Negotiating with the Customer
- Managing the Baseline
- Summary
- Team Skill 4 Summary
- Team Skill 5: Refining the System Definition
- Chapter 20. Software Requirements-A More Rigorous Look
- Looking Deeper into Software Requirements
- The Requirements Dilemma: What versus How
- More on Requirements versus Design
- A Further Characterization of Requirements
- Summary
- Looking Ahead
- Chapter 21. Refining the Use Cases
- How Use Cases Evolve
- The Scope of a Use Case
- The Case Study: Anatomy of a Simple Use Case
- Extending Use Cases
- Including Use Cases in Other Use Cases
- Summary
- Looking Ahead
- Chapter 22. Developing the Supplementary Specification
- The Role of the Supplementary Specification
- Expressing Functional Requirements in the Supplementary Specification
- Exploring Nonfunctional Requirements
- Understanding Design Constraints
- Identifying Other Requirements
- Linking the Supplementary Specification to the Use Cases
- Template for the Supplementary Specification
- Summary
- Looking Ahead
- Chapter 23. On Ambiguity and Specificity
- Finding the
- Techniques for Disambiguation
- Summary
- Chapter 24. Technical Methods for Specifying Requirements
- Pseudocode
- Finite State Machines
- Decision Tables and Decision Trees
- Activity Diagrams
- Entity-Relationship Models
- Summary
- Team Skill 5 Summary
- Team Skill 6: Building the Right System
- Chapter 25. From Use Cases to Implementation
- Mapping Requirements Directly to Design and Code
- Realizing Use Cases in the Design Model
- From Design to Implementation
- Summary
- Looking Ahead
- Chapter 26. From Use Cases to Test Cases
- A Tester s Perspective: Musings on the Big Black Box
- Is a Use Case a Test Case?
- Common Testing Terms
- Relationships of Test Artifacts
- The Role of the Test Cases
- Use-Case Scenarios
- Deriving Test Cases from Use Cases: A Four-Step Process
- Managing Test Coverage
- Black-Box versus White-Box Testing with Use Cases
- Summary
- Chapter 27. Tracing Requirements
- The Role of Traceability in Systems Development
- The Traceability Relationship
- A Generalized Traceability Model
- Using Traceability Tools
- Proceeding without Traceability Tools
- Summary
- Chapter 28. Managing Change
- Why Do Requirements Change?
- We Have Met the Enemy, and They Is Us
- A Process for Managing Change
- Requirements Configuration Management
- Summary
- Looking Ahead
- Chapter 29. Assessing Requirements Quality in Iterative Development
- Software Project Quality
- Assessing Quality in Iterative Development
- Requirements Artifacts Sets
- Performing the Assessment
- Quality Assessment Checklists for Requirements
- Summary
- Team Skill 6 Summary
- Looking Ahead
- Getting Started
- Dedication
- What You ve Learned So Far
- Chapter 30. Agile Requirements Methods
- Mitigating Requirements Risk with Effective Requirements Practices
- Methodology Design Goals
- Documentation Is a Means to an End
- An Extreme Requirements Method
- An Agile Requirements Method
- A Robust Requirements Method
- Summary
- Chapter 31. Your Prescription for Requirements Management
- Selecting Your Requirements Approach
- On to the Next Release
- Appendixes
- Appendix A. HOLIS Artifacts
- Background for the Case Study
- Team Skill 1: Analyzing the Problem
- Team Skill 2: Understanding User and Stakeholder Needs
- Team Skill 3: Defining the System
- Team Skill 4: Managing Scope
- Team Skill 5: Refining the System Definition
- Team Skill 6: Building the Right System
- Appendix B. Vision Document Template
- Table of Contents
- Appendix C. Use-Case Specification Template
- Table of Contents
- Use-Case Name
- Appendix D. Supplementary Specification Template
- Table of Contents
- Appendix E. Requirements Management in the Rational Unified Process
- The Structure of the Rational Unified Process 1
- Requirements Management in the Rational Unified Process
- Process Integration
- Appendix F. Requirements Management in the SEI-CMM and within ISO 9000:2000
- Requirements Management in the SEI-CMM
- Requirements Management in ISO 9000:2000
- Bibliography
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
EAN: N/A
EAN: N/A
Year: 2003
Pages: 257
Pages: 257
- Using SQL Data Definition Language (DDL) to Create Data Tables and Other Database Objects
- Using Data Control Language (DCL) to Setup Database Security
- Understanding Transaction Isolation Levels and Concurrent Processing
- Repairing and Maintaining MS-SQL Server Database Files
- Writing Advanced Queries and Subqueries
- The Four Keys to Lean Six Sigma
- Key #3: Work Together for Maximum Gain
- Making Improvements That Last: An Illustrated Guide to DMAIC and the Lean Six Sigma Toolkit
- The Experience of Making Improvements: What Its Like to Work on Lean Six Sigma Projects
- Six Things Managers Must Do: How to Support Lean Six Sigma