Lecture 10: Object-Oriented Analysis (System Sequence Diagrams, Conceptual Model)

ECE 452- Introduction to Software Engineering
Lecture 10: Object-Oriented Analysis (System Sequence Diagrams, Conceptual Model)

Manish Parashar parashar@ece.rutgers.edu Department of Electrical & Computer Engineering Rutgers University
The Unified Analysis Process & UML
Use Case - What are the domain processes ?

Use Case Diagram
high-level/expanded, essential/real
Conceptual Model - What are the domain concepts, terms ?

Class Diagram (conceptual)
classes, associations, attributes
System Sequence Diagram - What are the system events and operations ?
Interaction Diagram - Sequence Diagram Contract Specs.
Contracts - What do the system operations do ?
ECE 452 - Introduction to Software Engineering
Sample UP Artifacts
Business Modeling
Domain Model
Partial artifacts, refined in each iteration.
Use-Case Model
parameter or return data may be elaborated in the Glossary
:System
Requirements
text use cases system events & data
foo( x ) bar( y )
Glossary system operations
...
system sequence diagrams
system operation contracts
Design Model
Design
design objects to handle the system events
Software Architecture Doc.
Software Dev. Plan
Project Management
Test Plan
Development Case
Test
Environment
From Analysis to Design

Use
Cases Model
What are the domain processes ?

Conceptual System
What are the concepts, terms ?
sequence diagrams
What are the system events and operations ?

Contracts
What do the system operations do ?

System Sequence Diagrams

Determine
system events and operations Derived from Use Cases Typical course of events Identify system functionality (operations) to be designed System boundary is critical

Illustrate
events from actors to systems System sequence diagrams describe scenarios

a scenario is an instance of a use case Ivar Jacobson a real example of the enactment of a use case e.g. Process Sale
Some
UML notation for a sequence diagram is shown on the next slide

Draw
box. Identify each actor that directly operates on the system. Draw a line for each such actor. From expanded use case identify system events that each actor generates. Ilustrate them. Optionally include use case text on left.
a line representing the system as a black
A System Sequence Diagram

system as black box Buy Items-version 1 Actor Cashier
:System
Repeat until no more items
enterItem(UPC, quantity)
endSale() Text which clarifies control, logic, iteration, etc. May be taken from the use case. system event it triggers a system operation
makePayment(amount)
System events
System Event
An external input event generated by an actor to a system the system is seen as a black box
System operation
the method invoked in response to a system event
Use the same names for system event and system operation System events may have arguments

enterItem( UPC, quantity ) raise( money )

System Sequence Diagrams from Use Cases

: Cashier Simple cash-only Process Sale scenario: 1. Customer arrives at a POS checkout with goods and/or services to purchase. 2. Cashier starts a new sale. 3. Cashier enters item identifier. 4. System records sale line item and presents item description, price, and running total. Cashier repeats steps 3-4 until indicates done. 5. System presents total with taxes calculated. 6. Cashier tells Customer the total, and asks for payment. 7. Customer pays and System handles payment. ... makeNewSale( ) enterItem(itemID, quantity) description, total * [more items] endSale( ) total with taxes makePayment(amount ) change due, receipt :System
Naming System Events and Operations
: Cashier better name enterItem(itemID, quantity)
:System
scan(itemID, quantity) worse name
SSD with Use Case Text

Simple cash-only Process Sale scenario: 1. Customer arrives at a POS checkout with goods and/or services to purchase. 2. Cashier starts a new sale. : Cashier makeNewSale( ) enterItem(itemID, quantity) description, total * [more items] endSale( ) total with taxes makePayment(amount ) change due, receipt :System
3. Cashier enters item identifier. 4. System records sale line item and presents item description, price, and running total.
Cashier repeats steps 3-4 until indicates done. 5. System presents total with taxes calculated. 6. Cashier tells Customer the total, and asks for payment. 7. Customer pays and System handles payment. ...
System Behavior - Contracts

Contracts
help define system behavior Contracts are defined in part by preconditions and postconditions Examples in this chapter document system operations such as
enterItem endSale makePayment However, contracts also apply to low-level methods
The Conceptual Model- Introduction

Conceptual
Model
illustrates meaningful concepts most important artifact in OO analysis need use cases as input
but can develop uses cases as you do conceptual model
Question:
Provide names for the uses cases you found
let's share this information now (use whiteboard)
Domain Analysis
Object
level Objective: Create a library of reusable components for a particular domain Ongoing activity of the software process (not tied to a specific project) Domain analysis model specifies objects and classes that characterize the domain
oriented analysis at the business area
Domain Analysis
Define
domain to be investigated Categorize the items extracted from the domain Collect a representative sample of applications in the domain Analyze each application in the sample Develop an analysis model for the objects Define reuse guidelines
Conceptual Models
Conceptual
Model
created for the use cases of the current cycle in the language of the problem domain
Must
identify
concepts - objects in our system associations between concepts
is part of, contains, manages, is-a, ... instance variables needed to hold state
attributes of concepts
Conceptual Modeling...
Conceptual
models should not contain design
information
software artifacts, methods, etc.
Better
to over specify then under specify Concepts v/s attributes

when in doubt make it a concept
Specification/Description
concepts
Conceptual Modeling
Associations
less important than identifying concepts show only need-to-know association (avoid redundant or derivable associations) name, multiplicity, navigability multiple associations
Conceptual Model
Attributes
Attributes Vs. Concepts

keep attributes simple if in doubt define it as a concept no attributes as foreign keys (use associations)
A Partial Conceptual Model

See
example for POST on page 88 also on next slide

shows attributes name some instance variables now ________ shows associations name a label now contains multiplicity
numbers at the ends of the association lines 1, 0..1, 1..4 (one to four players), * means many direction reading arrow which could be left-to-right and topto-bottom by default (but this is not a standard rule) Arrows help readability
Figure 9.1

typically can read the multiplicity both ways
More
on associations and multiplicity later

Concept
Sales LineItem quantity 1.. * 0..1
Records-sale-of 1
Item
*
Stocked-in
Association
Contained-in 1 Sale Store address name 1 Houses Paid-by 1 Payment amount ECE 452 - Introduction to Software Engineering POST 1 1.. * Captured-on 4 1
Attributes
date time 1
We're shooting for something like this for your final project
Conceptual Model
Concepts
help with domain vocabulary Conceptual models are not models of software designs
dont be thinking windows and files here no responsibilities yet, do this in design
Concept:
an idea, thing, or object
symbol: a word or image representing a concept definition extension: set of examples to which the concept applies
Example Concept
POST
Sale
date time
Sale
concept's symbol
symbol: Sale definition

represents the event of a purchase transaction, and has a date and time
"A sale represents the event of a purchase transaction. It has a date and time."
concept's definition
extension: the set of all sales
sale-1 sale-2
sale-3
concept's extension
sale-4
Example Concept
POKER
Card
CardDeck rank suit
concept's symbol
symbol: Card definition:

represents one card in a poker deck that has a rank (2..14), and a suit
A card represents one of the entities to make up a hand in a poker game
concept's definition
extension: the set of all cards
Ace
King 5
concept's extension
Conceptual model and partitioning

Structured
Analysis (still in use today)
Divide and Conquer

at the function level
Object-Oriented
Analysis (still growing)
Partition
at the level of concepts (objects)
Identifying Concepts
One
strategy for getting concepts
Look for the concepts in the problem specification and in your uses cases
read the final project specification specifying too many concepts is good is is better too have too many than too few concepts may have no attributes
It is better to have too many at first than too few

Try
not to think of Java classes as you do this

later on, think of some classes to implement
Concept Category
Physical
or tangible things
POST A Point of Sale Terminal

Specifications
POST ProductDescription
Transactions
POST Sale, Payment
More Concept Categories

Things
in a container noun concepts
POST Sales Line Item

Abstract Events
POST Waiting line rage POST Sale
More Concept Categories

Rules
and Policies
POST RefundPolicy
Organizations
POST SalesDepartment
For more, see pages 91-93
Concepts?
page 96-97
Use vocabulary of the users Users are not usually present for college programming projects However, Poker has users
the users are you this isn't a Library with Patrons and Librarians
Do
not include irrelevant things
no casino, no pit boss

Do not include things that don't belong no Lottery System, no Starship Enterprise, no pit bull
Finding Concepts
Make

a list of candidate concepts (objects)
look for noun phrases

be careful to avoid ambiguities see page 95 POST Item, Store, Sale, Payment, Customer
Common Mistake

Do not mistake an attribute for a concept All others things are likely a concept
if in doubt, make it a concept
Attributes are numbers, booleans, strings, date
Example: Payment in the POST problem could be thought of as the amount of a Sale
a primitive attribute like 9.75 But a payment could be made by check, cash, credit card, could be in various currencies of the world, could require change This outgrows being a simple attribute
Resolving Similar Concepts

Naming
things correctly is
similar concepts with different names
important sometimes hard to agree:

POST 1 Records 6 or?
Register 1 Records6
*
Sale
*
Sale
Abstract Concepts
Some concepts don't feel real

Telecommunications
and that is okay
Connection, Route, Protocol Strategy, View
Poker
Encoding images with some compression scheme or encrypting messages for privacy
Compression, Encryption, Privacy
Concepts in the problem domain exist even if they do not seem to be part of the real world
POST Concepts
Accounts Receivable Drivers License
Credit Authorization Service Check Authorization Service
Credit Approval Request Credit Approval Reply
Check Approval Request Check Approval Reply
Cash Payment
Credit Payment
Check Payment
Credit Card
Check
POST
Item
Store
Sale
Product Catalog
Sales LineItem
Cashier
Customer
Manager
Product Specification
Defining Terms in the UML

unreal things
The Software class diagram will look a lot like the conceptual model You will see associations, boxes, multiplicity... Larman uses concept to refer to real world things and Classes refer to software specifications and implementations. UML defines class as
a description of a set of a objects that share the same attributes, relationships, and semantics
the three Amigos: Grady Booch, Ivar Jacobsen, Jim Rumbaugh
Other UML terms

Operation
a service that can be requested from an object to affect behavior

Type
either a class or an interface specification with no methods

Interface
the set of externally visible operations
Could mean a Java interface
Adding Associations
Next
step in the conceptual model
adding associations between two concepts an association is
a relationship between concepts that indicates some meaningful and interesting connection
Name the association with a hyphen connected verb phrase which reads well between concepts
association
POST
Records-current 1 1
Sale
Associations
Associations
imply
our knowledge of the relationship must be preserved for some time (1 ms to forever)
between what objects do we need to remember a relationship?

POST: does a driver's license remember a product catalog? Poker: does a game need to remember it's Player(s)? Poker: does the winner need to know the card image collection?
The UML Association Notation

UML
Association:
a line between two concepts and a name zero or more; they are bi-directional T * "many" can have a multiplicity 1.. * one or more T exist in conceptual models and 1..40 one to forty T class diagrams
Multiplicity adornments
5 T exactly five
T ECE 452 - Introduction to Software Engineering
3, 5, 8
exactly three, five or eight
Possible Associations

A is a physical part of B Drawer - POST A is a logical part of B SalesLineItem - Sale A is physically contained in B POST-Store A is logically contained in B ItemDescription-Catalog A is recorded in B Sale - POST A uses or manages B Cashier - POST A communicates with B Customer - Cashier A is related to a transaction B Customer - Payment Draw some poker associations now
Let's try to get one for each of the bullets above

Associations
Some
useful associations
A is a physical or logical part of B A is physically or logically contained in/on B A is recorded in B
Association Guidelines
Concepts
are more important than associations Focus on need to know associations

the relationship must be preserved for some time
Better
to have too few associations than too
many
Multiplicity
Multiplicity
defines how many instances of type A can be associated with one instance of type B at some point can differ
Game 1 1..6 Player
Mother
1 performs-in *
1+
Child
Actor is associated with 0 to many films. A film is associated with 0 to many actors
Actor
Film
can optionally name an association

Depends on Context
Are
all three associations possible?

Car Car
1 4
Wheel Wheel
Car
Wheel
Association Names
Upcase / hyphenate
Try reading this

Store 1 Contains 1.. * POST
Type-VerbPhrase-Type
Captures 1 1.. *
Sale
Paid-by 1 1
Payment
Not yet worrying about messages, instance variables, data flow, or software objects Just show some concepts are connected
No Implementation Yet
The
associations may later become implemented in software in terms of visibility

Related as an instance variable of a class Related as an argument in a message Related through an inheritance relationship
Some
associations will not be implemented
Others will be discovered during coding

Conceptual
Model should have associations suggested by requirements and use cases

Any unforgettable Relationships?

POST
Post Captures Sale Sale Paid-By Payment ProductCatalog Records Specification
Conceptual Model for the POST associations are not all need to know Records-sale-of
Described-by 1 Product Specification Contains 1 1 1.. *
Product Catalog
0..1 Sales LineItem
*
Store 1 1.. * Logscompleted 6 1
Used-by
Describes
*
Stocks 1 Item
Contained-in 1 Sale
Houses
1.. * POST Manager 1
*
Captured-on 1 1 1
Started-by 1 1
Paid-by 1 Payment
Initiated-by 1 Customer
3 Records-sales-on 1
Initiated-by 1
Cashier
see pages 116-117
Not need to know
No need yet to have POST Started-By Manager

Records-sale-of Described-by 1 Product Specification Contains 1 1 1.. *
Product Catalog
0..1 Sales LineItem
*
Used-by
Describes
*
Stocks 1 Item
Contained-in 1 Sale
Houses
1.. * POST
*
Captured-on 1 1 1
Paid-by 1 Payment
Initiated-by 1
Cashier
see pages 116-117
Not need to know
No one said Store Stocks Items

Records-sale-of Described-by 1 Product Specification Contains 1 1 1.. *
Product Catalog
0..1 Sales LineItem
*
Used-by
Describes
*
Item 1
Contained-in 1 Sale
Houses
1.. * POST
*
Captured-on 1 1 1
Paid-by 1 Payment
Initiated-by 1
Cashier
see pages 116-117
Need to Know vs. Comprehension
Could do a strict need-to-know model
bounded by current requirements only but it may not convey a full understanding the conceptual model may not communicate key ideas and relationships has need to know requirements what the system must do clearly communicates important concepts
By eliminating concepts and associations that are not currently required need to know Make your conceptual model so it
could have View as a concept
Summary
Doubting
whether to keep a concept? whether to keep an association?
keep it
Doubting
drop it
Do
not keep derived associations
Where A relates to B and B relates to C usually leave out the A to C relationship

Does
model satisfy all need to know associations and still present a clear complete picture?
Identifying Attributes
The
final piece to the conceptual model is to add the attributes needed to support use cases Attribute: a logical data value of an object
not necessarily in the final design, though some attributes will end up in the code
Example:
A bank customer has an account ID and a balance

both could be attributes in the conceptual model both could be instance variables in a class diagram
Keep attributes simple

Look Do
for simple data types as attributes

like data base primitives
boolean, date, number, string
not use complex ideas as attributes UML puts attributes in 2nd row of concept box
Sale date startTime : Time attributes
Attribute or Association?
Easy
Worse
to mistake a concept as an attribute

Cashier name currentPOST not a "simple" attribute
Better name
Cashier
Uses
1 number
POST
Attribute or Association?
Attributes
should be simple, if complex, write it as a concept with an association

Worse Flight destination destination is a complex concept
Better
Flight
Flies-to
Airport

Lecture 10: Object-Oriented Analysis (System Sequence Diagrams, Conceptual Model)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lecture 10: Object-Oriented Analysis (System Sequence Diagrams, Conceptual Model)

Uploaded by

Copyright:

Available Formats

ECE 452- Introduction to Software Engineering

Lecture 10: Object-Oriented Analysis (System Sequence Diagrams, Conceptual Model)

The Unified Analysis Process & UML

Use Case - What are the domain processes ?

Conceptual Model - What are the domain concepts, terms ?

classes, associations, attributes

Contracts - What do the system operations do ?

ECE 452 - Introduction to Software Engineering

Partial artifacts, refined in each iteration.

parameter or return data may be elaborated in the Glossary

Glossary system operations

system sequence diagrams

system operation contracts

design objects to handle the system events

Software Architecture Doc.

Software Dev. Plan

ECE 452 - Introduction to Software Engineering

From Analysis to Design

What are the domain processes ?

What are the concepts, terms ?

What are the system events and operations ?

What do the system operations do ?

System Sequence Diagrams

ECE 452 - Introduction to Software Engineering

System Sequence Diagrams

events from actors to systems System sequence diagrams describe scenarios

UML notation for a sequence diagram is shown on the next slide

ECE 452 - Introduction to Software Engineering

System Sequence Diagrams

a line representing the system as a black

A System Sequence Diagram

Repeat until no more items

ECE 452 - Introduction to Software Engineering

enterItem( UPC, quantity ) raise( money )

System Sequence Diagrams from Use Cases

ECE 452 - Introduction to Software Engineering

Naming System Events and Operations

: Cashier better name enterItem(itemID, quantity)

scan(itemID, quantity) worse name

ECE 452 - Introduction to Software Engineering

SSD with Use Case Text

ECE 452 - Introduction to Software Engineering

System Behavior - Contracts

The Conceptual Model- Introduction

but can develop uses cases as you do conceptual model

Provide names for the uses cases you found

let's share this information now (use whiteboard)

ECE 452 - Introduction to Software Engineering

oriented analysis at the business area

concepts - objects in our system associations between concepts

models should not contain design

to over specify then under specify Concepts v/s attributes

ECE 452 - Introduction to Software Engineering

ECE 452 - Introduction to Software Engineering

Attributes Vs. Concepts

ECE 452 - Introduction to Software Engineering

A Partial Conceptual Model

example for POST on page 88 also on next slide

typically can read the multiplicity both ways

on associations and multiplicity later

Sales LineItem quantity 1.. * 0..1

an idea, thing, or object

symbol: Sale definition