Architectural analysis is the first of two steps in the design process. In this phase you match the requirements gathered from the project initiation and problem analysis phases and map them to the technologies and architectures that are best suited to support the requirements.
You should now be able to:
- Explain the purpose and function of architectural partitioning
- Create architectural partitions and define their behaviors
- Specify how responsibilities are distributed in two-tier, three-tier, and n-tier architectures
- Apply the deployment diagram to model the system architecture
In the last module you learned how to partition the problem domain. In this module you learned how to break down each domain partition (or subsystem) into technological layers or tiers. The partitioning process followed a simple pattern of separate, assign responsibility, and reconnect using an interface. The result is a layered design with a set of highly cohesive partitions that are loosely coupled. This form of architecture improves the modularity of the system by isolating each unique type of design problem. Modularity, in turn, allows easier maintenance and updates to the system.
Click the Exercise link below to work on the course project. In this exercise you will apply architectural partitioning to domain partitions.
Partition Project Domain - Exercise