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
Partition dependencies - Exercise
Determine the dependencies between the domain partitions.
This exercise is worth a total of 10 points.
Open the following exercise documents from the download files:
Evaluate the information provided to determine if there are any dependencies between the Sales subsystem and the other subsystems.
Update the package diagram to illustrate your conclusions.
Please provide a brief textual explanation of any dependencies that you identify.
When you read the sequence diagrams, remember to refer back to the partitions that contain the classes to see which partition owns the classes and which partitions simply refer to them.
Remember the different types of dependencies:
Via associations and communication across the associations
Submitting your exercise
To submit the exercise, follow the steps below:
In the text area below, type in your solution. In addition, you can include any questions or comments you have about the exercise. When you are ready to submit the exercise, click the