Build the Enterprise Architecture

Creating an enterprise architecture is a lot like creating a building architecture. Both involve a disciplined development cycle, use rigorous techniques, and require the right tools.

A building is constructed using architectural diagrams (blueprints) that clearly depict the building's infrastructure (structural elements, walls, electrical wiring, plumbing, etc.). Enterprise architectures include architectural models of enterprise infrastructure (policies, goals, measures, critical success factors, data elements, etc.).

Blueprints are also used to enlarge a building or make any significant modifications. Without a diagram of the infrastructure, such changes are quite difficult and very costly -- and can even be dangerous. It is the same with enterprise architectures. Managing change means first updating the enterprise's architecture model so that it reflects changes (new product lines or services, for example) and then modifying the information systems to support the changed enterprise.

Enterprise architecture engineering is easier and less costly when based upon an accurate architectural model of the enterprise. Further, strategic information based upon the architecture is easier to use and consistently produces desired outcomes when decision-makers have access to an enterprise architecture that accurately reflects enterprise infrastructure.

It is imperative that an enterprise information architecture reflects both strategic information requirements and day-to-day operational data requirements. The architecture must be closely linked to the enterprise strategic plan and corporate performance measures.

Enterprise information needs, corporate performance measures, and critical success factors should be documented in a central repository, along with a corresponding logical data model. The logical model should include operational data entities as well as strategic information data entities that will tell executives and managers how well their enterprise is performing.

Activities critical to capturing a clear understanding of an enterprise’s information architecture include providing a clear and unambiguous definition of every data entity, describing the way each is used, defining derivation formulas and aggregation categories, and documenting data collection and retention time periods. The resulting enterprise architecture model, which links enterprise needs with data entities and enterprise rules, becomes both requirement documentation and a source for communicating the contents of the architecture (and its metadata) to its users.

Contact Us, and learn more about how Metro InfoDesign Information Architecture and Metadata Management services apply to your business requirements...