book

Use Cases: Patterns and Blueprints

by Gunnar Övergaard, Karin Palmkvist

November 2004

Intermediate to advanced

464 pages

8h 59m

English

Addison-Wesley Professional

Read now

Unlock full access

Copyright
The Software Patterns Series
Titles in the series
Foreword
Preface
Collecting Models and DesignsThis BookOrganization of the BookOn Patterns and BlueprintsOn ExamplesHow to Use This BookIf You Are an Experienced Use-Case ModelerIf You Are a Novice or Inexperienced with Use Cases in PracticeIf You Are Not a DesignerFuture Use of This BookHistory of Use CasesAcknowledgments
I. Introduction
1. Use-Case Patterns and Blueprints
Reusing ExperienceContents of the CatalogUse-Case PatternsUse-Case BlueprintsCommon Mistakes
2. Using Patterns and Blueprints in Use-Case Model Development
The Internet Bank SystemThe First Draft of the ModelApplying Patterns and BlueprintsLogin and LogoutUse-Case SequenceLegacy SystemMultiple ActorsFuture TaskCRUDAccess ControlBusiness RulesThe Complete ModelConcluding Remarks
II. Use Cases
3. Use-Case Modeling: An Introduction
4. Use Cases
Use Case: A Type of Utilization Providing a ValueA Gray-Box View of the SystemUse-Case Instance: A Specific UtilizationBasic Flow and VariationsInfinitely Large Models?

5. Modeling the System Environment
Actor: An External UserInteraction Between Use Cases and Actors
6. Structuring a Use-Case Model
7. Include: Reusing Existing Use Cases
Include RelationshipDocumentation of the Include RelationshipDependency on Inclusion Use Cases
8. Extend: Expanding Existing Use Cases
Extend RelationshipCharacteristics of the Extend RelationshipExtension PointsConditional ExtensionsDocumentation of the Extend RelationshipDependencies Between Extending Use Cases
9. Include vs. Extend
10. More on Extend and Extension Points
Multiple Fragments of Additional BehaviorMultiple InsertionsMore on Extension Points
11. Use-Case Generalization: Classification and Inheritance
Generalization Between Use CasesDocumentation of the Generalization Relationship Between Use Cases
12. Actor Generalization: Overlapping Roles
13. Describing Use Cases
Documenting Use CasesGuidelines for WritingSections of a Use-Case Description
14. Documenting a Use-Case Model
Use-Case Model SurveyUse-Case DiagramsSupplementary Documents
15. Mapping Use Cases onto Classes
Kick-Starting the Class ModelingAnalysis Models and Design ModelsAnalysis ClassesUse-Case Realization: How Objects Perform a Use Case
III. Use-Case Patterns
16. Business Rules
IntentPatternsBusiness Rules: Static DefinitionModelDescriptionApplicabilityTypeBusiness Rules: Dynamic ModificationModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
17. Commonality
IntentPatternsCommonality: ReuseModelDescriptionApplicabilityTypeCommonality: AdditionModelDescriptionApplicabilityTypeCommonality: SpecializationModelDescriptionApplicabilityTypeCommonality: Internal ReuseModelDescriptionApplicabilityTypeDiscussionSub-Sequence Independent of ContextAdditions to Existing Use CasesSimilar Use CasesCommonality Within a Single Use CaseExampleAnalysis Model
18. Component Hierarchy
IntentPatternsComponent Hierarchy: Black-Box with Use CasesModelDescriptionApplicabilityTypeComponent Hierarchy: Black-Box with OperationsModelDescriptionApplicabilityTypeComponent Hierarchy: White-BoxModelDescriptionApplicabilityTypeDiscussionReplaceable Components: Black-Box ComponentsBlack-Box Components Specified with OperationsBlack-Box Components Specified with Use CasesWhite-Box ComponentsCommon MistakesExampleAnalysis Model
19. Concrete Extension or Inclusion
IntentPatternsConcrete Extension or Inclusion: ExtensionModelDescriptionApplicabilityTypeConcrete Extension or Inclusion: InclusionModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
20. CRUD
IntentPatternsCRUD: CompleteModelDescriptionApplicabilityTypeCRUD: PartialModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
21. Large Use Case
IntentPatternsLarge Use Case: Long SequenceModelDescriptionApplicabilityTypeLarge Use Case: Multiple PathsModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
22. Layered System
IntentPatternsLayered System: ReuseModelDescriptionApplicabilityTypeLayered System: AdditionModelDescriptionApplicabilityTypeLayered System: SpecializationModelDescriptionApplicabilityTypeLayered System: EmbeddedModelDescriptionApplicabilityTypeDiscussionSimple Access of Lower-Layer InformationInclude Lower-Layer Use CasesExtend Lower-Layer Use CasesCombinations of RelationshipsGeneralizationExampleAnalysis ModelSimple Access of Lower-Layer InformationInclude Lower-Layer Use CasesExtend Lower-Layer Use CasesSpecialization of a Use Case
23. Multiple Actors
IntentPatternsMultiple Actors: Distinct RolesModelDescriptionApplicabilityTypeMultiple Actors: Common RoleModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
24. Optional Service
IntentPatternsOptional Service: AdditionModelDescriptionApplicabilityTypeOptional Service: SpecializationModelDescriptionApplicabilityTypeOptional Service: IndependentModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
25. Orthogonal Views
IntentPatternsOrthogonal Views: SpecializationModelDescriptionApplicabilityTypeOrthogonal Views: DescriptionModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
26. Use-Case Sequence
IntentPatternsUse-Case SequenceModelDescriptionApplicabilityTypeDiscussionExampleAnalysis Model
IV. Use-Case Blueprints
27. Access Control
ProblemBlueprintsAccess Control: Embedded CheckModelDescriptionApplicabilityAccess Control: Dynamic Security UnitsModelDescriptionApplicabilityAccess Control: Explicit CheckModelDescriptionApplicabilityAccess Control: Internal AssignmentModelDescriptionApplicabilityAccess Control: Implicit DetailsModelDescriptionApplicabilityDiscussionExampleAnalysis Model
28. Future Task
ProblemBlueprintsFuture Task: SimpleModelDescriptionApplicabilityFuture Task: SpecializationModelDescriptionApplicabilityFuture Task: ExtractionModelDescriptionApplicabilityFuture Task: Performer NotificationModelDescriptionApplicabilityDiscussionExampleAnalysis Model
29. Item Look-Up
ProblemBlueprintsItem Look-Up: StandaloneModelDescriptionApplicabilityItem Look-Up: Result UsageModelDescriptionApplicabilityItem Look-Up: Open DecisionModelDescriptionApplicabilityDiscussionExampleAnalysis Model
30. Legacy System
ProblemBlueprintsLegacy System: EmbeddedModelDescriptionApplicabilityLegacy System: SeparateModelDescriptionApplicabilityDiscussionExampleAnalysis Model
31. Login and Logout
ProblemBlueprintsLogin and Logout: StandaloneModelDescriptionApplicabilityLogin and Logout: Action AdditionModelDescriptionApplicabilityLogin and Logout: ReuseModelDescriptionApplicabilityLogin and Logout: SpecializationModelDescriptionApplicabilityLogin and Logout: SeparateModelDescriptionApplicabilityDiscussionIndependent Use CasesAddition to Normal Login ProcedureVerification Before Each UsageNo Login Use CaseLogoutManage User InformationExampleAnalysis Model
32. Message Transfer
ProblemBlueprintsMessage Transfer: Deferred DeliveryModelDescriptionApplicabilityMessage Transfer: Immediate DeliveryModelDescriptionApplicabilityMessage Transfer: AutomaticModelDescriptionApplicabilityDiscussionExampleAnalysis Model
33. Passive External Medium
ProblemBlueprintsPassive External MediumModelDescriptionApplicabilityDiscussionExampleAnalysis Model
34. Report Generation
ProblemBlueprintsReport Generation: SimpleModelDescriptionApplicabilityReport Generation: SpecializationModelDescriptionApplicabilityReport Generation: Dynamic TemplatesModelDescriptionApplicabilityDiscussionExampleAnalysis Model
35. Stream Input
ProblemBlueprintsStream Input: DiscreteModelDescriptionApplicabilityStream Input: AnalogModelDescriptionApplicabilityDiscussionDiscrete ValuesAnalog StreamExampleAnalysis Model
36. Translator
ProblemBlueprintsTranslator: Static DefinitionModelDescriptionApplicabilityTranslator: Dynamic RulesModelDescriptionApplicabilityDiscussionExampleAnalysis Model
V. Common Mistakes
37. Mistake: Alternative Flow as Extension
FaultIncorrect ModelModelDetectionDiscussionWay Out
38. Mistake: Business Use Case
FaultIncorrect ModelModelDetectionDiscussionPauses in Use CasesWay Out
39. Mistake: Communicating Use Cases
FaultIncorrect ModelModelDetectionDiscussionWay Out
40. Mistake: Functional Decomposition
FaultIncorrect ModelModelDetectionDiscussionWay Out
41. Mistake: Micro Use Cases
FaultIncorrect ModelModelDetectionDiscussionWay Out
42. Mistake: Mix of Abstraction Levels
FaultIncorrect ModelModelDetectionDiscussionWay Out
43. Mistake: Multiple Business Values
FaultIncorrect ModelModelDetectionDiscussionWay Out
44. Mistake: Security Levels with Actors
FaultIncorrect ModelModelDetectionDiscussionWay Out
Glossary
References

Content preview from Use Cases: Patterns and Blueprints

Chapter 37. Mistake: Alternative Flow as Extension

Fault

Modeling an alternative flow of a use case as an extension of that use case.

Keywords: Addition to flow, alternative flow, extend relationship, extracting flow.

Incorrect Model

Model

Detection

A clear sign of this modeling mistake is when the flow of an extension use case is supposed to replace a part of the base use case flow. Another indicator is, of course, that the base use case is not complete without the extension, because it lacks an alternative flow.

Discussion

A use case has one flow, or sometimes multiple flows, considered to be the normal or basic flow of that use case. This flow will be ...

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

Practical Django 2 and Channels 2: Building Projects and Applications with Real-Time Capabilities

Publisher Resources

ISBN: 0131451340Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills