System Object Design
Review Project Life Cycle
Transition Analysis Design
Analysis Work Products
Process Phase Conclusion
Partitioning Analysis Model
Partitioning Process Goal
Partitioning Design Conclusion
Domain Partitioning Resources
Package Modeling Purpose
Three Step Domain Partitioning Process
Partitioning based On Use Cases
Define Dependencies between Partitions
Domain Partitioning Conclusion
Three Tier Architecture
Partitioning Architecture ntier
Additional ntier Architectures
Architectural Analysis Conclusion
Statechart to Object Design - Quiz
Price Planning Domain Partitions
Example #1: The Price Planning domain partition
Price Planning includes three use cases: Update PriceTier, Update Discount, and Update PricePlan.
Update PriceTier creates and maintains PriceTier objects.
Update Discount creates and maintains Discount objects.
Update PricePlan creates and maintains PricePlan objects.
No other objects are required in order to establish and maintain a PricePlan, so there are no additional referenced objects. The complete subsystem definition looks something like this.
Example #2: The Show Pricing domain partition
Identify the classes that the Price Show use case references. To do so you would typically read the use case narrative. The first step in pricing a show is to select a show to price. I'll use gray shading to indicate that the class belongs to another partition but is being referenced here.
The next step is to select the PricePlan to use for the Show.
Create the link between the Show and the PricePlan.
Once you have the Show and the PricePlan, you must select a set of ShowSeats to price.
Select the PriceTier to assign to the selected ShowSeats.
Create the links between the PriceTier and each of the selected ShowSeat objects.
The completed package definition would include the use case and the participating classes.