BUSINESS ANALYST TRAINING
Feb - 2014
DAY 10
Requirements Modeling via Use Cases
Modeling
Benefits
Concepts
Symbols
Process
Project Management
USE CASE MODELING
User Center Development – A process of developing a
system based on understanding the needs of the Project
Stakeholders and the reasons why the system should be
developed.
Use Case Modeling – The process of modeling a system’s
function in terms of business events, who initiated them
and how the system will respond to those event.
Use Case – An Object Oriented Modeling Approach
Compliments Traditional Modeling Tools
Effectively Communicated
Easily Understandable & Maintainable
Easily Verified & Validated
BENEFITS OF USE CASE MODELING
Provides tool for capturing functional requirements.
Helps in decomposing system into manageable sub-
systems.
Provides a means of communication with concerned
Users / Stakeholders, in the language which they can
understand.
Provides means of Identifying, Assigning, Tracking,
Controlling, & Managing system development
activities.
Provides basis for Estimating Project Scope, Efforts, &
Schedule.
Test Plans, Text Cases, Baseline for Documentation,
Requirements Traceability, Helps in creating DB & UI,
Project Management.
CONCEPTS FOR USE CASE MODELING
Use Case – A behavioral related sequence of
scenarios / steps, both automated and manual,
for the purpose of completing a single business
task / process.
Use Case Diagram – A diagram that depicts the
interaction between the users, internal system
and other external systems.
Use Case Narration – A textual description of the
business event and how the user will interact
with the system to accomplish the task / process.
7-6
BASIC USE CASE SYMBOLS
Use Case – A subset of the overall system
functionality.
Actor – Anyone or Anything that is interacting
with the system to exchange information.
Human
Organization
External System
External Device
Time as Trigger
TYPE OF ACTORS
Primary Business Actor
Stakeholder who is primarily benefits from the execution of
use case.
Primary System Actor
Stakeholder that directly interfaces with the system to
initiate / trigger the business / system event.
External Server Actor
Stakeholder that responds to a request from the use case.
External Receiver Actor
Stakeholder that is not the primary actor but receives
something of value from the use case.
USE CASE ASSOCIATION RELATIONSHIP
Use Case Association – A relationship between and
actor and use case in which an interaction occurs
between them.
Association With Arrow – User Initiated Use Case
Association Without Arrow – Receiver Actor
Association may be Uni / Bi - Directional
EXTENDS RELATIONSHIP IN USE CASES
Extension Use Case – Use Case consisting of
steps extracted from another Use Cases to
simplify the original one.
Extends the functionality of original one.
Generally not identified in requirements phase.
EXTENDS relationship represented as arrow
beginning at the extension use case and pointing to
use case it is extending.
DEPENDS ON RELATIONSHIP IN USE CASES
Depends On – Use case relationship that specifies
which other use cases must be performed before the
current use case, which ultimately helps in Sequence
Determination.
INCLUDES RELATIONSHIP IN USE CASES
Abstract Use Case – Use case that reduces redundancy
in two or more other use cases by combining common
steps found in both.
Relationship between Abstract Use Case and Use Case that
includes / uses, it is called Includes / Uses Relationship.
INHERITANCE RELATIONSHIP IN USE CASES
Inheritance – A use case relationship in which the
common behavior of two actors initiating the same use
case is shown and assigned to a new Abstract Actor to
reduce redundancy.
Other actors can inherit the interaction of the Abstract
Actor.
PROCESS OF REQUIREMENTS USE CASE MODELING
Objective is to elicit and analyze enough requirements
information to prepare a model that:
Communicates what is required from a user perspective.
Is free of specific details about how system will be
implemented.
To effectively estimate and schedule project, may need
to include preliminary implementation assumptions.
Steps
Identify Business Actors.
Identify Business Use Cases.
Construct Use-Case Model Diagram.
Documents Business Requirements Use-Case Narratives.
1 – IDENTIFY BUSINESS ACTORS
For identifying actors:
Who or what provides inputs to the system?
Who or what receives outputs from the system?
Are interfaces required to other systems?
Are there events that are automatically triggered at a
predetermined time?
Who will maintain information in the system?
Actors should be named with a Noun or Noun
Phrase
Visitor
Subscriber
Administrator
Distribution Center
Time
2 – IDENTIFY BUSINESS USE CASES
Business Requirements Use Case - a use case
created during requirements analysis to capture
the interactions between a user and the system
free of technology and implementation details.
During requirements analysis, strive to identify
and document only the most critical, complex,
and important use cases, often called Essential
Use Cases.
2 – IDENTIFY BUSINESS USE CASES
For identifying the use cases
What are the main tasks of the actor?
What information does the actor need from the
system?
What information does the actor provide to the
system?
Does the system need to inform the actor of any
changes or events that have occurred?
Does the actor need to inform the system of any
changes or events that have occurred?
Usecases should be named with a verb
phrase specifying the goal of the actor;
Create Registered User
Submit Subscription Order
Fetch Report Details
3 – USE CASE CONSTRUCTION
4 – DOCUMENT BUSINESS USE CASE NARRATION
Document first at high level to quickly obtain an
understanding of the events and magnitude of
the system.
Then expand to a fully-documented business
requirement narrative.
Include the use case’s typical course of events
and its alternate courses.
A HIGH LEVEL USE CASE NARRATION
EXPANDED USE CASE NARRATION - 1
EXPANDED USE CASE NARRATION - 2
EXPANDED USE CASE NARRATION - 3
USE CASES & PROJECT MANAGEMENT
Project Management can be done on Use Case Model.
Project Manager / System Analysts provides Estimates
& Schedules on the basis of Use Cases.
Build Cycles are created on the basis of importance of
use cases and time it takes to implement the use case.
To determine importance of use case, one has to create:
Use Case Ranking & Evaluation Matrix
Use Case Dependency Diagram
Use Case Points Based Estimation
USE CASE RANKING & PRIORITY MATRIX
Use Case Ranking & Priority Matrix – A tool used to
evaluate use cases and to determine their priorities.
Evaluation Criteria:
1. Significant impact on the architectural design.
2. Easy to implement but contains significant functionality.
3. Includes risky, time-critical, or complex functions.
4. Involves significant research or new or risky technology.
5. Includes primary business functions.
6. Will increase revenue or decrease costs.
USE CASE RANKING & PRIORITY MATRIX
USE CASE DEPENDENCY DIAGRAM
Use-case dependency diagram – graphical depiction of
the dependencies among use cases.
Benefits of Use Case Dependency Diagram:
Graphical representation of system’s events and their
states.
It also enhances understanding of system functionality.
Helps in identification of missing use cases.
Helps in facilitating Project Management by representing
which use cases are more critical.
USE CASE DEPENDENCY DIAGRAM
USE CASE POINTS BASED ESTIMATION
Actors Classification
Actor Type
Weightage
Use Case Classification
Use Case Type
No. of Transactions
Weighting Factor
Technical Factors Classification
Easy to Install, Third Party Access, Reusable Code, Security,
Portability, Complex Processing, etc…
Environmental Factors Classification
Application Experience, Motivation, Requirements Stability,
Technical Capability, End User Engagement, etc…
Actors Classification Use Case Classification
Unadjusted Actor Weights - UAW
Unadjusted Use Case Weights – UUCW
Unadjusted Use Case Points – UUCP = UAW + UUCW
Technical Factors Classification Environmental Factors Classification
TCF = 0.6 + (0.01 x TFactor)
EF = 1.4 + (-0.03 x EFactor)
Adjusted Use Case Point = UUCP x TCF x EF
THANK YOU
