Applying Use Cases: A Practical Guide 2nd edition [Pehme köide]

Foreword		xi
Preface to Second Edition		xiii
Preface		xv
Getting Started		1	(10)
An Interative Software Process		2	(1)
An Example Project		3	(1)
The Project Description		4	(2)
Starting Risk Analysis		6	(4)
Chapter Review		10	(1)
Identifying System Boundaries		11	(16)
Identifying Actors		12	(2)
Identifying Use Cases		14	(3)
Describing Actors and Use Cases		17	(4)
Handling Time		21	(1)
Potential Boundary Problems		22	(1)
Scoping the Project		23	(1)
Chapter Review		24	(3)
Documenting Use Cases		27	(24)
The Basic Use Case		27	(4)
Pre-and Postconditions		28	(1)
Flow of Events		29	(2)
Guidelines for Correctness and Completeness		31	(1)
Presentation Styles		32	(2)
Other Requirements		34	(1)
Handling Complex Use Cases		34	(1)
The Basic Path		35	(2)
Alternative Paths		37	(3)
Detailing Significant Behavior		40	(2)
Documenting Alternatives		42	(5)
Scenarios		47	(1)
Adding Direction to the Communicates Association		47	(1)
Chapter Review		48	(3)
Advanced Use Case Documentation Techniques		51	(16)
Include		51	(2)
Extend		53	(5)
Inheritance		58	(1)
Interfaces		59	(6)
Chapter Review		65	(2)
Diagramming Use Cases		67	(12)
Activity Diagrams		67	(6)
Simple Sequence Diagrams		73	(2)
Diagramming the User Interface		75	(2)
Chapter Review		77	(2)
Level of Detail		79	(10)
Determining the Level of Detail		79	(5)
Traceability between Use Cases		84	(1)
Use Cases for Business Processes		85	(2)
Chapter Review		87	(2)
Documenting Use Cases		89	(12)
Documentation Templates		89	(2)
Other Documents		91	(3)
Tool Support for Documents		94	(1)
Documenting Login		95	(3)
Documenting CRUD		98	(1)
Chapter Review		99	(2)
Reviews		101	(22)
Review for Completeness		101	(2)
Review for Potential Problems		103	(1)
Review with End Users		103	(1)
Review with Customers		104	(1)
Review with Development		104	(1)
Reviewers		104	(1)
Adding Flexibility to Your System		105	(2)
Common Mistakes		107	(15)
Work Flow on a Use Case Diagram		107	(1)
Use Cases Too Small		108	(4)
Screens as Use Cases		112	(3)
Using Vague Terms		115	(5)
Business versus Technical Requirements		120	(2)
Chapter Review		122	(1)
Dividing Large Systems		123	(20)
Architectural Patterns		123	(6)
Three-Tier Architectural Pattern		124	(1)
Pipe and Filter Architectural Pattern		125	(1)
Object-Oriented Architectural Pattern		126	(1)
Order-Processing Architecture Example		126	(3)
Testing the Architecture with Use Cases		129	(4)
Sequence Diagrams		133	(1)
Defining Interfaces between Subsystems		133	(3)
Subordinate Use Cases		136	(4)
Creating Subsystem Documentation		140	(1)
Subordinate versus Alternative versus Include		141	(1)
Chapter Review		142	(1)
Use Cases and the Project Plan		143	(16)
Planning the Project		143	(8)
Build versus Buy Decisions		149	(1)
Prototyping		150	(1)
Estimating Work with Use Cases		151	(7)
Weighting Actors		151	(1)
Weighting Use Cases		152	(1)
Weighting Technical Factors		153	(4)
Use Case Points		157	(1)
Project Estimate		157	(1)
Chapter Review		158	(1)
Constructing and Delivering a System		159	(12)
Key Abstractions of the Domain		159	(7)
Identifying Key Abstractions in Use Cases		160	(1)
Diagramming Scenarios with Key Abstractions		161	(2)
Diagramming Key Abstractions		163	(1)
Use Case versus Subsystem View		164	(2)
The Iteration Schedule		166	(1)
Delivery and Beyond		167	(2)
User Guides and Training		168	(1)
Sales Kits and Marketing Literature		168	(1)
Use Cases After Delivery		168	(1)
Chapter Review		169	(1)
Final Wrap-Up		170	(1)
Appendix A Resources		171	(4)
Appendix B Documentation Templates		175	(4)
System or Subsystem Documents		175	(1)
Use Case Document		176	(3)
Appendix C UML Notation		179	(6)
Appendix D Sending Results of the Use Case Estimator		185	(2)
Appendix E Order-Processing System		187	(52)
Order-Processing System		188	(1)
Risk Factors		188	(1)
System-Level Use Cases		189	(1)
Architecture		190	(49)
Index		239

Geri Schneider is a senior consultant and trainer at Andrews Technology, Inc., in the areas of iterative development, software project management, object-oriented analysis and design, software architecture, design patterns, and use cases. In addition, she teaches in the software engineering management certificate program for the University of California Santa Cruz Extension. She previously worked for Rational Software Corporation mentoring customers in the areas of iterative development, object technologies, and use case analysis. Jason P. Winters is a staff design engineer for Cadence Design Systems, Inc. He was previously with Lucent Technologies as a staff engineer. At Lucent, he designed and built specialized tools, promoted the use of modern software development practices and tools throughout the company, and mentored projects on object-oriented analysis and design, UML, and use cases.

0201708531AB04062001