Advanced Use Case Modeling Workshop
Overview
|
Course 338 - 2 Days
|
The Advanced Use Case Modeling Workshop goes beyond the basics
of use case writing. It is intended for Analysts that have taken
an introductory use case course and/or have at least 2-3 months
use case writing experiences. While introductory courses cover
the basics to get people started, many questions and challenges
arise only after the Analysts have written several use cases. This
workshop is designed to answer all of those tough questions and
to provide a thorough coverage of the intricacies of use case modeling
and analysis.
Objectives
- Master the creation of a detailed use case description
- Improve use case description readability, consistency
and completeness
- Get a thorough understanding of pre-post conditions
- Identify and prevent common problems that arise from
misuse of include, extend and generalization relationships
- Learn how to capture business rules
- Apply an objective criteria for reviewing use cases
- Answer all questions that typically come up after
someone has been doing use cases from several months to a year
Who Should Attend
Business analysts, managers, business experts, project leaders,
developers and anyone who requires a practical knowledge of the
nuts & bolds of use case modeling.
Instructional Methods
The workshop combines lecture, case study, exercises and group
discussion. This is a hands-on workshop – there is 60 /
40% split between lecture and exercises and discussion, because
this is how people learn the best. We encourage the participants
to bring in samples of their work and have all their questions
answered by experienced instructor. Prerequisites
Requirements Analysis with Use Cases or equivalent, and/or at least
2 months experience writing use cases
Workshop Content
Getting Started with Use Case Modeling
- Putting together the preliminary use case model
- Defining project scope with use cases
- Mapping use cases to business goals
The Use Case Model – Discovering
Actors and Use Cases
- Overview of use case modeling
- Primary and secondary actors
- Guidelines for applying Actor generalization / specialization
relationships
Actor meta-types
- Getting the big picture – preliminary use case model
- Primary & secondary
use cases
- Challenges with the use case level of granularity
The Use Case Specification
- Components of use case specification template
- Use cases styles – formal / informal / essential
- Handling special requirements
- Evolutionary approach to specification writing
- Guidelines for use case writing and review
Specifying the Main Flow of Events
- Writing the use case skeleton
- Numbering and specifying steps
- Specifying data details
- Initiating & ending steps
- Conditional and iterative logic in the flow of events
- Getting the right level of detail
- Using Activity diagrams to represent a complex flow of
events
- Main flow of events check list
Iteration and Concurrency
- Identifying and iteration & concurrency in the flow
of events
- Pros and cons for different options for handling iteration
and concurrency
- Modeling iteration and concurrency
Pre-and Post-Conditions
- What is system state?
- Guidelines for defining pre and post conditions
- Traps to avoid
- Verifying completeness with pre and post conditions
- Specifying Alternatives
Identifying and labeling alternatives
Specifying alternatives
- Inserting reference points
- Modeling alternative variations
- Specifying alternative post conditions
Modeling Business Rules
- What are business rules?
- Where do rules come from
- Specifying rules & inserting business rules reference
points
- Handling complex business rules
Include & Extend Relations
- Factoring out mandatory common behavior with includes relation
- Referencing inclusion
- Separating optional behavior with extends relation
- Alternative flow of events vs. extends relation
- Capturing extension points
Applying Generalization Relation
- When to use generalization relation
- Top-down vs. bottom up approach
Alternative representations
- Guidelines for applying generalization
Capturing Additional Requirements
- When to use Activity diagrams
- Activity diagrams to model use case dependencies
- Specifying user interface requirements
- Specifying non-functional requirements; quality, performance,
etc.
Validating Use Cases – The Use Case Review
- A review check list
- Organizing review
- Getting the most out of the use case reviews
Review & Discussion |
