Architect the application

1. Major separate modules:
Petstore web site: serves as a front end to the user
order fulfillment center: on the back end

2. Choosing architecture pattern: MVC, Micro-kernel,etc... for each separate modules
Object design becomes important as applications grow more complex. Large
scale development of object-oriented software requires frameworks that define
how objects interact. The framework must enable software designs and code to be
easily reused. It must also identify the responsibility of each component; that is,
the division into components must ensure the unambiguous identity of what the
component represents and what it must accomplish.
Additionally, for multitier enterprise applications, it is important to:
• Separate stable code from code that changes more frequently. Usually the presentation
and user interface change more often than business rules and database
schemas. The overall architecture should separate stable portions of the
application from the more volatile parts.
• Divide development effort along skill lines. The people that comprise an enterprise
development team typically represent a very diverse set of skills. There
are Web page designers who do HTML layout and graphics, programmers,
application domain experts, and enterprise information system resource access
specialists, among others. The decomposition should result in a set of objects
that can be assigned to various subteams based on their particular skills. This
division of labor allows work on each object to proceed in parallel.

petstore website: MVC
order fulfillment center: process workflow

3. Identifying functional specifications(requirements) for each separate module, therefore, application will be able to partitioned into multiple separate functional models.

4. Application is roughly partitioned into multiple layers based on choosed architecture pattern.

5.