Definition of the various Logical level architectural views supports the analysis of the business processes, generic technology choices, and other aspects, permitting optimizations to be discovered. A better understanding of the business and how technology supports it is also developed. The Logical (and Technical) level structures and decisions are linked directly back to the business drivers through the Business level. The Architectural Decision taken at the Logical level will typically involve choices regarding generic technology and architectural patterns.

Multiple iterations are done to create the required Logical level models, with enough detail defined to support the objectives of the exercise. Many activities can be done in parallel, but good communications is needed in order to keep the models consistent, but good tool support makes this a non-issue. The following items are produced:

• Logical Entity Model for the system;
• Logical Process Model for the system;
• Logical Locations Model for the system;
• Logical Roles Model for the system;
• Update the Architecture Glossary and define Architectural Decisions as required.

Once a complete perspective is defined a peer review is done to decide if the IT architecture is complete, or if additional iterations are required.

These activities are best carried out by a small team staffed by cross-functional team members, lead by an IT architect. Issues that are typically architecturally significant include process, locations, and roles, along with the generic technology choices. The team should include members with business domain experience and ideally logical level modelers and IT experts as required. The team should have experience with model organization and layering. From the provided inputs, the team will need to be able to synthesize the architecture views.