×

Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Applying Use Cases: A Practical Guide / Edition 1
     

Applying Use Cases: A Practical Guide / Edition 1

by Geri Schneider, Jason P. Winters, Jason Winters
 

ISBN-10: 0201309815

ISBN-13: 9780201309812

Pub. Date: 08/28/1998

Publisher: Addison-Wesley

Many projects struggle to define what the software is supposed to do, and endusers often find that the final product does not do what they expect. Use cases allow analysts to identify the required features of a software system based on how each enduser will use the system. This efficient and straightforward analysis process gives endusers direct input into the

Overview

Many projects struggle to define what the software is supposed to do, and endusers often find that the final product does not do what they expect. Use cases allow analysts to identify the required features of a software system based on how each enduser will use the system. This efficient and straightforward analysis process gives endusers direct input into the design of the system that will serve them.

Applying Use Cases provides a practical and clear introduction to developing use cases, demonstrating their use via a continuing case study. Using the Rational Software Development Process as a framework and the Unified Modeling Language (UML) for the notation, the authors step the reader through applying use cases in the different phases of the process, focusing on where and how use cases are applied.

Other highlights include:

  • A collection of realistic examples showing how to apply use cases, drawn from the authors' extensive experience in this area
  • A case study that offers insight into the common mistakes and pitfalls that can plague an object-oriented project
  • An illustration of the new 1998 UML notation for diagramming use cases
  • A practical "how-to" discussion on applying use cases to identify system requirements

Product Details

ISBN-13:
9780201309812
Publisher:
Addison-Wesley
Publication date:
08/28/1998
Series:
Object Technology Series
Edition description:
Older Edition
Pages:
208
Product dimensions:
7.28(w) x 9.16(h) x 0.45(d)

Table of Contents

Forewordxi
Preface to Second Editionxiii
Prefacexv
Chapter 1Getting Started1
An Iterative Software Process2
An Example Project3
The Project Description4
Starting Risk Analysis6
Chapter Review10
Chapter 2Identifying System Boundaries11
Identifying Actors12
Identifying Use Cases14
Describing Actors and Use Cases17
Handling Time21
Potential Boundary Problems22
Scoping the Project23
Chapter Review24
Chapter 3Documenting Use Cases27
The Basic Use Case27
Pre-and Postconditions28
Flow of Events29
Guidelines for Correctness and Completeness31
Presentation Styles32
Other Requirements34
Handling Complex Use Cases34
The Basic Path35
Alternative Paths37
Detailing Significant Behavior40
Documenting Alternatives42
Scenarios47
Adding Direction to the Communicates Association47
Chapter Review48
Chapter 4Advanced Use Case Documentation Techniques51
Include51
Extend53
Inheritance58
Interfaces59
Chapter Review65
Chapter 5Diagramming Use Cases67
Activity Diagrams67
Simple Sequence Diagrams73
Diagramming the User Interface75
Chapter Review77
Chapter 6Level of Detail79
Determining the Level of Detail79
Traceability between Use Cases84
Use Cases for Business Processes85
Chapter Review87
Chapter 7Documenting Use Cases89
Documentation Templates89
Other Documents91
Tool Support for Documents94
Documenting Login95
Documenting CRUD98
Chapter Review99
Chapter 8Reviews101
Review for Completeness101
Review for Potential Problems103
Review with End Users103
Review with Customers104
Review with Development104
Reviewers104
Adding Flexibility to Your System105
Common Mistakes107
Work Flow on a Use Case Diagram107
Use Cases Too Small108
Screens as Use Cases112
Using Vague Terms115
Business versus Technical Requirements120
Chapter Review122
Chapter 9Dividing Large Systems123
Architectural Patterns123
Three-Tier Architectural Pattern124
Pipe and Filter Architectural Pattern125
Object-Oriented Architectural Pattern126
Order-Processing Architecture Example126
Testing the Architecture with Use Cases129
Sequence Diagrams133
Defining Interfaces between Subsystems133
Subordinate Use Cases136
Creating Subsystem Documentation140
Subordinate versus Alternative versus Include141
Chapter Review142
Chapter 10Use Cases and the Project Plan143
Planning the Project143
Build versus Buy Decisions149
Prototyping150
Estimating Work with Use Cases151
Weighting Actors151
Weighting Use Cases152
Weighting Technical Factors153
Use Case Points157
Project Estimate157
Chapter Review158
Chapter 11Constructing and Delivering a System159
Key Abstractions of the Domain159
Identifying Key Abstractions in Use Cases160
Diagramming Scenarios with Key Abstractions161
Diagramming Key Abstractions163
Use Case versus Subsystem View164
The Iteration Schedule166
Delivery and Beyond167
User Guides and Training168
Sales Kits and Marketing Literature168
Use Cases After Delivery168
Chapter Review169
Final Wrap-Up170
Appendix AResources171
Appendix BDocumentation Templates175
System or Subsystem Documents175
Use Case Document176
Appendix CUML Notation179
Appendix DSending Results of the Use Case Estimator185
Appendix EOrder-Processing System187
Order-Processing System188
Risk Factors188
System-Level Use Cases189
Architecture190
Index239

Customer Reviews

Average Review:

Post to your social network

     

Most Helpful Customer Reviews

See all customer reviews