Skip to content

Use Cases Requirements in Context

Spend $50 to get a free DVD!

ISBN-10: 0321154983

ISBN-13: 9780321154989

Edition: 2nd 2004 (Revised)

Authors: Daryl Kulak, Eamonn Guiney, Erin Lavkulich

List price: $54.99
Shipping box This item qualifies for FREE shipping.
Blue ribbon 30 day, 100% satisfaction guarantee!
Buy eBooks
what's this?
Rush Rewards U
Members Receive:
Carrot Coin icon
XP icon
You have reached 400 XP and carrot coins. That is the daily max!

Description:

This timely second edition describes a process based on employing use cases to gather and define software requirements. Use cases, roughly defined, involve the process of figuring out exactly how end-users will use a software system when it is completed before coding begins. Both the process and its presentation have been thoroughly revised based on the authors' more recent consulting experience and on feedback gathered from readers of the first edition over the past three years. Of particular note, the authors have added or enhanced coverage of topics not addressed in other books, even though these topics are vital to successful use case application in industry: for example, project management in a use case driven lifecycle, and use case maintenance or change over time.
Customers also bought

Book details

List price: $54.99
Edition: 2nd
Copyright year: 2004
Publisher: Addison Wesley Professional
Publication date: 7/25/2003
Binding: Paperback
Pages: 272
Size: 6.75" wide x 9.00" long x 0.75" tall
Weight: 1.144
Language: English

Preface
Preface to the First Edition
The Trouble with Requirements
First and Least of All ...
What Is a Requirement?
Functional Requirements
Nonfunctional Requirements
Requirements Gathering, Definition, and Specification
The Challenges of Requirements Gathering
Finding Out What the Users Need
Documenting Users' Needs
Avoiding Premature Design Assumptions
Resolving Conflicting Requirements
Eliminating Redundant Requirements
Reducing Overwhelming Volume
Ensuring Requirements Traceability
Issues with the Standard Approaches
User Interviews
Joint Requirements Planning Sessions
Contract-Style Requirements Lists
Prototypes
Those Troublesome Requirements
Moving to Use Cases
It's All About Interactions
The Unified Modeling Language
Nine Diagrams
Extending the UML with Stereotyping
Introducing Use Cases, Use Case Diagrams, and Scenarios
The Goals of Use Cases
How Use Case Diagrams Show Relationships
The Use Case Template
Paths and Scenarios
Use Cases Apply Here
Use Cases for Inquiry-Only Systems
Use Cases for Requests for Proposals
Use Cases for Software Package Evaluation
Use Cases for Non-Object-Oriented Systems
Applying Use Cases to the Requirements Problem
A Use-Case-Driven Approach to Requirements Gathering
Requirements Specification Tools
Principles for Requirements Success
Three Steps for Gathering Requirements
The Role of the Mission, Vision, Values
The Role of the Statement of Work
The Role of the Risk Analysis
The Role of the Prototype
The Roles of Use Cases
Use Cases Are Effective Communication Vehicles
Use Cases Can Be Used for Functional and Nonfunctional Requirements
Use Cases Help Ensure Requirements Traceability
Use Cases Discourage Premature Design
The Role of the Business Rules Catalog
Managing Success
The Facade Iteration
Objectives
Users
Project Team
Industry Experts
IT Management Group
User Management Personnel
Owners of the Data
Steps in the Facade Iteration
Create the Mission, Vision, Values
Identify and Review Existing Documentation and Intellectual Capital
Get the Executive Sponsor's Unique Viewpoint
Review the Business Process Definitions
Identify the Users, Customers, and Related Groups
Interview the Stakeholders
Create a Stakeholders List
Find the Actors
Create the Use Case Survey (A List of Facade Use Cases)
Collect and Document Nonfunctional Requirements
Start the Business Rules Catalog
Create a Risk Analysis
Create a Statement of Work
Begin Experimenting with User Interface Metaphors
Begin User Interface Storyboards
Get Informal Approval from the Executive Sponsor
Tools
The Use Case Diagram
The Hierarchy Killer
Use Case Name Filters
Actor Filter
Verb Filter
Noun Filters
Packages as Placeholders for Functionality
Facade Filter
Peer Review
User Review
Deliverables
Roles
Context
Summary
The Filled Iteration
Objectives
Steps
Break Out Detailed Use Cases
Create Filled Use Cases
Add Business Rules
Test the Filled Use Cases
Put Some Things Off
Tools
The Stakeholder Interview
IPA Filter
White Space Analysis Filter
Abstraction Filter
Testing Use Cases with Scenarios
Review
Additional Use Cases
Deliverables
Roles
Context
Summary
Focused Iteration
Objectives
What Are Focused Use Cases?
Steps
Merge Duplicate Processes
Bring Focus to Each Use Case
Manage Scope Changes During This Iteration
Manage Risks and Assumptions
Review
Tools
Surplus Functionality Filter
Narrow the Focus of the System
Identify Surplus Functionality Inside the Use Case
Vocabulary Filter
Deliverables
Roles
Context
Summary
Managing Requirements and People
Introduction
Waterfall Lifecycle Management
Nell and the Coffee Shop
Disadvantages of Waterfall
Alternatives to Waterfall
Rapid Application Development (RAD)
Spiral
Staged Delivery
Holistic Iterative/Incremental (HI/I)
Introducing the Holistic Iterative/Incremental Use-Case-Driven Project Lifecycle
The Meaning of Iterative
The Meaning of Incremental
The Meaning of Holistic
The Meaning of Adaptivity
Complex Adaptive Systems
Process
Principles of the Holistic Iterative/Incremental Software Lifecycle
Manage Requirements Not Tasks
The Important Goals Are the Business Goals--Dates and Budgets
Think Like a Businessperson--What Have You Done for Me Lately?
Divide and Conquer
Cut the Job into Programs and Projects
Tie Everything Back to the Business
Create Demonstrable Deliverables
Learn the Art of "Good Enough" Quality
The Pieces Will Be Smaller Than You Think
Expect Negotiation, Not Specification
Forget about Baselines and Sign-offs
Estimate by Doing
Calculate Return-on-Investment in a New Way Using Portfolios
Requirements Traceability
Tracing Back to Use Cases
Analysis Model Traceability
Design Model Traceability
CRC Card Session Traceability
Test Model Traceability
User Interface Design Traceability
Application Architecture Traceability
Project Management Traceability
Documentation and Training Traceability
Product Marketing Traceability
Security Traceability
Release Planning
Tracing Back to Nonfunctionals
Tracing Back to Business Rules
Structural Facts
Action-Restricting and Action-Triggering Rules
Calculations and Inferences
Classic Mistakes
Mistakes, Pitfalls, and Bruised Knees
Classic Mistakes: Make Them and Move On
The Case for Use Cases
Why Did Use Cases Win?
Use Cases Are Sensible to Businesspeople
Use Cases Are Traceable
Use Cases Are an Excellent Scoping Tool
Use Cases Don't Use a Special Language
Use Cases Allow Us to Tell Stories
The Alternatives Are Awful
Use Cases Beyond Software
Service Use Cases
Business Use Cases
Summary
Real Estate Management System
Overview
The Use Cases
The Actors
Technical Requirements and Business Rules
Scope Decisions
List of Use Cases
Refining the Requirements
Investment Returns Calculation
Tightening Requirements
Integrated Systems
Overview
Background
Problem Description
Solution Analysis
Instant Messaging Encryption
Overview
The Use Cases
Order a Product from a Catalog
Bibliography
Index