|
|
|
Use Case Modeling – Based on UML 2.0 Notations
… Capture un-ambiguous, clear and precise requirements using this
world class technique
This course provides all team members with the required competencies
for creating use case diagrams and use case scenarios, which serve
as a vehicle for eliciting, analyzing, documenting and communicating
functional requirements. You will practice creating use cases in the
Unified Modeling Language (UML) to graphically represent the
interactions between use cases and actors. To fully gain the
benefits of UML, you will create use case diagrams through an
object-oriented approach, which enables business analysts to sift
through the complexity of a system by breaking it down into smaller
units.
Prerequisite
A familiarity with key requirements management concepts and
terminology is recommended as well as basic knowledge of any
modeling technique.
Course Level
Intermediate
Duration
2 Days
Who should attend?
Any one who deals with requirements and or reads / interprets
requirements and scope documented by others
Performance Focus
This course frames the process of discovering use cases,
beginning with finding the actors, the scope and the various
relationships between them. It gives you access to the
resourceful nature of the use case by focusing on users' needs
and how the system will help satisfy those needs, at the same
time providing traceability from requirements to specifications
to the project.
What You Will Learn
- Employ use cases to elicit, analyze, document and
communicate functional requirements for software
- Use the Unified Modeling Language (UML) to create use
case diagrams
- Determine when to employ use case modeling
- Prioritize use cases based on their importance to the
business and on technical considerations
- Describe ways to develop consistent vocabulary between
use cases and objects
- Analyze and document detailed requirements using an
object model
- Read a class diagram
Content
Basic outline of the course:
Introduction To Use Case Modeling
Organizing requirements with use cases
Use case diagrams as a UML notation
Organizing the model with packages
Identifying And Describing Actors
Use case actors
Business versus system actors
Identifying actors
Mapping stakeholders to actors
Users versus actors
Identifying And Describing Use Cases
Identifying use cases
Writing a use case description
Including preconditions, post conditions, assumptions and scenarios
Writing Use Case Scenarios
Identifying the main success scenario
Identifying alternates and exceptions
Indicating iteration
Advanced Use Case Modeling Techniques
Diagramming an «include» relationship
Diagramming an «extend» relationship
Diagramming generalization and specialization
Considering multiplicity |
Ensuring Use Case Quality
Employing quality assurance techniques
Ensuring use cases are testable
Prioritizing Use Cases
Estimating project cost with use cases
Employing prioritization techniques
Introduction To Object
Modeling
Use cases and object orientation (OO)
Identifying objects and classes
Identifying And Describing
Business Domain Objects
Assigning objects to classes
Guidelines for describing business objects
Describing operations, attributes and Associations
Recap & Closing |
| |
|
|
|