Elaboration

System Sequence Diagrams

CIS 320-06 1
Inception Elaboration
 Define actors, goals, use  Build the core architecture
cases  Resolve the high-risk
 Vision & Supplementary elements
Spec
 Define most
 Risk list
requirements
 Technical proof of
concept  Estimate the overall
 UI Prototype schedule and resources
 High-level speculation on
architecture and
components

CIS 320-06 2
Ranking Requirements for
Planning
❚ Risk
❙ Effort
❙ Technical complexity
❙ Skills
❙ Usability
❚ Coverage of system
❚ Criticality (business value)

CIS 320-06 3
Ranking Table
Rank Requirement Comment
(Use Case or
Feature)
High UC #1… Time consuming
and will need to
learn some new
techniques
Medium F #3… Should be doable,
but don’t know
how
Low UC #4… Open Source code
is available
CIS 320-06 4
Core Architecture
❚ Wide and shallow
❙ Identify components, their responsibilities and
interfaces
❙ Partially implement to clarify interfaces
❚ Refine inter-module local and remote interfaces
❙ e.g. module wraps the interface to EBAY
❚ Integrating existing components
❙ Reusing already existing components
❚ Implement simplified end-to-end scenarios
❙ e.g., place a snipe

CIS 320-06 5
System Sequence Diagrams
(SSDs)
❚ A notation for illustrating a particular
scenario of a Use Case
❚ Shows actor and system
❚ Shows order of events
❚ Main success scenario
❚ Frequent or complex alternative scenarios

CIS 320-06 6
POS SSD
external
system actor to Process Sale Scenario
: Cashier :System
box may enlose an makeNewSale()
iteration area
the * [...] is an enterItem(itemID, quantity)
iteration
marker
indicating and clause
the box is for
iteration description, total
* [more items]
endSale() aparameters
message with
return value(s)
associated with the
previous message total with taxes itrepresenting
is an abstraction
the
an abstraction that system
entering event
the of
ignores presentation makePayment(amount)
payment data by
and medium some mechanism
the return
optional if line is
nothing is change due, receipt
returned CIS 320-06 7
Relation to Use Case Scenario
SimpleProcess
cash-onlyscenario:
Sale
1. Customer
with goods arrives
and/or : at a
Cashier
services POSto checkout
purchase. :System
2. Cashier
quantity, if enters
greater item
than identifier
one. and
3. System
presents records
item sale
description, line item and
enterItem(itemID,
price, and quantity)
running
Cashier total.
repeats steps 2-3 until indicates
done.
4. System presents total with description,
taxes total
calculated.
5. Cashier tells Customer the * total,
[moreand
items]
asks
6. for
Customerpayment.
pays with cash.
7. Cashier enters cash tendered. endSale()
8. System
change due.records payment and
total presents
with taxes
7. System
does not logs thewith
interact completed
external sale, but
systems.
8.
9. System
Customer presents
leaves receipt.
with makePayment(amount)
receipt and
goods.
change due, receipt
CIS 320-06 8
Naming Events is SSDs

: Cashier :System
better name enterItem(itemID, quantity)

scan(itemID, quantity)
worse name
CIS 320-06 9