You are on page 1of 29

Prepared by Prof.

Dhanashri Wategaonkar

System Analysis
Domain Model - The DM shows the static
structure of the real-world system and
organizes it into workable pieces.
Application Model Consider the interaction.

Prepared by Prof.Dhanashri Wategaonkar

Finding classes
Classes often correspond to nouns.
Eg- a reservation system sell tickets to
performances at various theater.
Tentative classes would be Reservation, System,
Tickets, Performance and Theater.
Idea is to capture concepts; not all nouns are
concepts, and concepts are also expressed in
other parts of speech.
Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Redundant Classes:
Customer Passenger
Customer-User

Irrelevant Classes:
Occupation
Cost

Vague Classes:

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Preparing a Data Dictionary

Prepared by Prof.Dhanashri Wategaonkar

Finding Association

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Find attributes of Objects and Links.

Prepared by Prof.Dhanashri Wategaonkar

Group classes into packages

Prepared by Prof.Dhanashri Wategaonkar

Determine system boundary

Prepared by Prof.Dhanashri Wategaonkar

Finding actors

Prepared by Prof.Dhanashri Wategaonkar

Find Use Cases

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Finding Initial and Final Events


To understand behavior ,you must understand
the execution sequences that cover each use
case.
You can start by finding the events that initiate
each use case.
Determine which actor initiates the use case
and define the event that it sends to the system.
In many cases ,the initial event is a request for
the service that the use case provides.
Prepared by Prof.Dhanashri Wategaonkar

ATM Example
Initiate session: The initial event is the customers
insertion of a cash card.
There are two final events: the system keeps the
cash card or the system returns the cash card.
Query account: The initial event is the customers
request for account data. The Final event is the
systems delivery of account data to the customer.
Prepared by Prof.Dhanashri Wategaonkar

Preparing Normal Scenarios


A scenario is a sequence of events among a
set of interacting objects.

Prepared by Prof.Dhanashri Wategaonkar

Adding variation and Exception scenarios

Prepared by Prof.Dhanashri Wategaonkar

Finding External Events

Prepared by Prof.Dhanashri Wategaonkar

Prepare activity diagram for use cases

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

With fork & join

Prepared by Prof.Dhanashri Wategaonkar

With swim lanes

Prepared by Prof.Dhanashri Wategaonkar

Prepared by Prof.Dhanashri Wategaonkar

You might also like