Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Types of Architecture
The overall architecture of an enterprise can be described by four integrated sub-architectures. These are:
- Business Architecture
- Information Architecture
- Application Architecture
- Technology Architecture
Most frameworks describe analogous or similar subsets of an Enterprise Architecture, as the division is based largely on organizational units performing work in these areas. There are a number of other architectures that could best be described as views, as they cross-cut and are contained by the other architectures, but because of their importance they are often raised to the level of an architecture. These include:
- Security Architecture
- Geospatial Architecture
- Social Architecture
These types of architectures are described in this section.
A well articulated business architecture is the cornerstone for a successful outcome of the overall Enterprise Architecture. It defines the business drivers, the business strategy, operational models, goals and objectives that the organization needs to achieve to transition in a potentially competitive and disruptive business environment. Architects working in the other architecture disciplines need to understand the Business Architecture as the basis for their own architecture descriptions and as a guide to the business outcomes that have to be achieved.
The business architecture will typically consist of a description of the baseline and target architectures, with a series of transitions defined that can be executed and that would be described on Roadmap diagrams.
Enterprise Architect has a wide range of tools that can be used for modeling Business Architecture from the strategic level down to the operational level. Even when Strategic Plans reside in a corporate document repository they can be represented and launched from inside Enterprise Architect. This allows other elements such as drivers, goals and objectives to be traced back to their origin in the strategy documents. Mission and Vision statements can also be modeled alongside Business Capabilities, Processes and Functions. Stakeholders and Organizational roles can be represented and used to show who owns elements of the architecture such as requirements and applications. Business and Stakeholder requirements can be created and managed at any level of detail and the Document Generator can be used to create elegant and comprehensive publications that describe aspects of the business architecture.
Learn More: Business Architecture
Information Architecture is key to the success of an Enterprise Architecture Program, as information is created, consumed and destroyed by the components that make up the other architectures. Understanding which business functions and processes utilize information, which applications serve as the master record, where information is created and destroyed, and which technology components store and manipulate the information, is critical to achieving the business outcomes.
The information architecture will typically consist of a description of the baseline and target architectures, with a series of transitions defined that can be executed and that would be described on Roadmap diagrams.
Enterprise Architect is a profoundly useful tool for creating and maintaining information architectures, with its sophisticated and extensive support for standards and its wide range of tools to support information models, from high level classifications and concepts right down to the level of schemas and the elements and columns they are composed of. Tools such as the Schema Composer and the Database Builder, along with the Unified Modeling Language (UML) Class diagram and Glossary, and the powerful Model Transformation facility, will be invaluable.
Learn More: Information Architecture
The application architecture provides an important catalog of the applications in the enterprise, describing the work that they do to transform, transmit and store information. The architecture also describes the interfaces that are required or provided by the applications and the way the applications interact to carry out the activities described in the business models, such as the Business Process diagrams and Capability models. The catalog of applications, interfaces and the diagrams and matrices that describe their interaction only need to be defined once at the enterprise level. An application architect will be able to draw upon this inventory of existing artifacts to create new architectures, classifying them as part of the baseline and potentially the future state architecture. Where an architecture introduces new applications, these can be added to the description of the target state.
The application architecture will typically consist of a description of the baseline and target architectures, with a series of transitions defined that can be executed and that would be described on Roadmap diagrams.
Learn More: Application Architecture
The technology architecture underpins the other architectures, providing a description of the logical, physical and virtual infrastructure that supports the execution of application services that in turn support information and business functions and services.
Learn More: Technology Architecture
The security architecture is a slice through all of the other architectures from a security viewpoint. It is listed as a separate architecture because of its importance in ensuring that the enterprise security polices are implemented through the architecture. A breach of security could occur at any point from the business architecture through to the technology architecture. This could include demonstrating how the architectures comply with security controls published by the enterprise or available as part of an industry compliance regulation.
Enterprise Architect can be used to model the security controls maintained as a list of elements in the repository and when new architectures are created the applicable controls could be applied to aspects of the architecture such as applications, technology devices, communication paths and more. Significant reuse can be achieved by the use of Patterns, and the use of existing building blocks that have already been certified as compliant with the controls.
The Geospatial Architecture is a slice through all of the other architectures from a geo-spatial or location based viewpoint. It is listed as a separate architecture because of its increasing importance in a world dominated by location based applications and business technology functions. Not every architecture program will have the need to develop separate geospatial architectures and in these cases it can be relegated to a view of the other architectures.
Enterprise Architect is well placed to be a repository for geo-spatial architectures with its integration with some of the leading standards and tools in the market place including support for the Geographic Markup Language (GML), ISO 1900 series standards and tools like ArcGIS and other geodatabases.
Social Architecture has been born in an era that depends on social media and social behavior to achieve a wide range of outcomes in built and digital environments. Increasingly in this period of digital and social disruption, understanding the social aspects of an organization's interaction is critical. This can include the way it interacts with its customers, suppliers and observers and other individuals and communities through what is commonly described as social media.
Enterprise Architect can be used to model the social context of the organization and if significant information is published to social media sites or information is gleaned from these sites these can be modeled in the repository and an architect can create visualizations that show how this information relates to other parts of the business and information architectures.