OBJECT ORIENTED

DESIGN AND ANALYSIS

LECTURE # 9

Engr. Rida Ghafoor Hussain

 Contact Information
2

 Instructor: Engr. Rida Ghafoor Hussain

Assistant Professor
Department Of Computer Science
FAST-NUCES (CFD)

 Email: rida.ghafoor@nu.edu.pk
 Office hours:

 Wednesday, 11:00 - 1:00 p.m

 Course Information
3

 Course Name: Object Oriented Analysis And Design

 Course Code: CS309

 Course Link:
http://slate.nu.edu.pk/portal/site/FSDCS309FALL2016CS/page/FSD
CS309FALL2016CS-1300
 4 Topics to Cover
 Use Cases
 High Level Use Case
 Expanded Use Case

Engr. Ali Javed

Use Case is a contract

 Use cases define a contract of how a system will behave.

 A use case captures the details of a software features but a
use case is not a use case if it does not return some
useful/valuable output for the user.
Type of Use Cases
Use Case Descriptions
Specifying Use Case

 Create a written document for each Use Case

 Clearly define intent of the Use Case

 Define Main Success Scenario (HappyPath)

 Define any alternate action paths

 Use format of Stimulus: Response

 Each specification must be testable

 Write from actor’s perspective, in actor’s vocabulary

 High Level Use Case
9

 A UML high level use case is a brief description of the main

processes used to accomplish the system function.
 A high level use case describes each of the major processes in
the system and therefore there is one high level use case for
each of the major processes. The high level use case verbally
describes the following:
 Name of the process.
 The actors involved with the initiating actor defined.
 The type of use case.
 The description of the process.
Example
 Expanded Use Case
11

 A UML expanded essential use case is a more detailed

description of the processes used to accomplish the system
function.
 An expanded use case is built upon a high level use case.
Typical events will happen 80% or more of the time and
alternatives will happen only 20% or less of the time.
 Expanded Use Case
12

 Name of the process.

 Created by- ABC
 Date of creation- dd/mm/yy
 Revised by- XYZ
 Date of revision- dd/mm/yy
 The actors involved with the initiating actor defined.
 The description of the process from the high level
use case.
 Expanded Use Case
13

 Preconditions - Conditions that must be true before

the use case can happen
 Postconditions - Conditions that must be true after
the use case execution
 Normal Flow- the overall flow of use case activity.
 Alternate Flow- Exceptional alternatives that might
arise.
 Expanded Use Case
14

 Frequency Of Use- the tendency of use case

execution. It may be Normal, High or Low
 Special Requirements- instructions for specific
purpose.
 Assumptions- that must be obvious.
 Example: Expanded Use Case :: Apply Algorithm
Use Case: Apply Algorithm
Actor: System
15
Description: System will implement algorithm to solve
constraints
Trigger Constraint Generation
Pre-conditions: Input records and parameters are
available
Post-conditions: All requested constraints will be solved.
Normal Flow: System implements algorithm
One by One parameters are solved
System is now modified to successful
scenario.
Alternate Scenario System implements algorithm
Parameter create an exception
Error is reported
Error Message for error handling.
Special Requirements Dataset must be uniform
Frequency Of Use Normal
Assumptions System is well-trained over algorithm.
Actors
POS system use case diagram
Class Activity

 Find actors and use cases of the system.

 Make system use case diagram.
 Write use cases (Brief level)
 For any query Feel Free to ask
44