This delivery process defines the activities for doing UAM IT architecture modeling within an enterprise, at any level.
Work Breakdown Structure
Purpose
The purpose of this reference process is to provide the activities and tasks for following the Unified Architecture
Method. This reference process defines many parallel processes and activities, but provides structure where required,
including reviews and milestones.
Description
This process delivers the combined tasks, techniques, and guidance from the Unified Architecture Method (UAM), but
integrated with and augmented through reference to other supporting material. The delivery process is intended to focus
the reader only on those aspects core to UAM architecture definition, and while there may be additional useful
techniques referred to within the methodology, the delivery process brings to the fore the necessary critical elements.
The phases described in this delivery process are intended to be iterative in themselves as well as an assumption that
multiple instances of these processes may be underway with the enterprise. For example, given a complete set of
artifacts from the Business Perspective phase, multiple Logical Perspective phases may be executed to
divide up the architecture effort, likely along business lines, business domains, or projects. Each IT
architecture project will be responsible for progressing a subset of the EA level architecture.
As illustrated in Roadmap: AD Governance it is recommended that the enterprise have a single Enterprise (Chief IT) Architect plus a Business
Line (Domain) Architect for each business line. Enterprise-wide standards and guidance will be provided and managed by
the Enterprise Architect, while the Domain (Business Line) Architects do the same for their portion of the enterprise.
It is likely that IT architectural issues are quite different in each business line, but this will
be dependent upon the size and type of business. This architectural governance structure also has clear spans of
control, with enterprise-wide issue being the responsibility of the Enterprise Architect. A typical, reasonably sized
enterprise, will therefore likely have:
Enterprise Architect - responsible for the overall enterprise IT structure and standards;
Corporate Domain Architect - responsible for the network infrastructure, common services (e.g.,
email, web, etc.), and corporate applications (e.g., HR systems, Financial COTS systems, etc.);
Business Line Architect - responsible for the architecture of business-line specific systems.
Thus, there are typically two basic architects (i.e., Enterprise and Corporate), plus an IT architect for each
business line if the size of the enterprise warrants it.
Usage
Usage Guidance
IT architecture is mandatory in any organization with more than about 100 employees, or even less. System
and processes and people are all interconnected, through networks and other ways, in order to support the goals of the
enterprise. This connectivity cannot be understood, optimized, implemented and managed properly without the
creation of abstract models. These models support the decision making required to evolve the enterprise's information
technology that it turn supports the goals of the organization.
Usage Notes
The delivery process allows for many parallel activities, since there may be multiple strategies underway,
and multiple enterprise or business domain level projects underway. Also, Architectural Decisions may arise at
anytime and anywhere within the enterprise. A separate governance process has been defined for Architectural Decisions:
Roadmap: AD Governance.
UAM has governance processes incorporated into its Delivery Processes, including architectural assessments, and
milestone reviews. See: Delivery Process: IT Architecture Delivery.
However, each enterprise has its own governance processes for the business and associated IT systems. A separate
generic governance process has been defined within UAM that specifies where and how to integrate UAM within these
pre-existing enterprise processes. See: Delivery Process: UAM in the Enterprise
