Series:
· Solve (Design OO model) a Parking Garage problem
· Solve (UML representation OO model) a Parking Garage problem
· Solve (app pattern) a Parking Garage problem
· Solve (cloud & network deployment pattern) a Parking Garage problem
· Solve (Design OO model) a Parking Garage problem
· Solve (UML representation OO model) a Parking Garage problem
· Solve (app pattern) a Parking Garage problem
· Solve (cloud & network deployment pattern) a Parking Garage problem
We are going to create Structure Diagrams (Class, Object,
Package), and Behavioral Diagrams (State, Sequence, Use Case) for the Parking
Garage problem. Please let us follow KISS principle J We are not going to capture all
the diagrams for the problem.
We will use n-tier application architecture.
Class diagram:
Use Case diagram:
Sequence diagram:
For Check Availability Use Case.
Package diagram:
The main packages of an n-tier architecture. There are
util, etc. packages that is not captured here to keep the diagram simple.
State diagram:
There are two possible state
No comments:
Post a Comment