ENTERPRISE ARCHITECTURE DEVELOPMENT
Developing an Enterprise Architecture consists in maintaining documents of detailed description of an enterprise structural and functional blueprint and how its components fulfill requirements as mandated by its specific stakeholders. This document is oriented towards facilitating the acquisition and transitioning towards newer technology and business processes. As such it offers not only a compatibility view in achieving architecture and enterprise change but it is also the primary tool for selecting technology by IT investment managers for strategic goals.
Developing an Enterprise Architecture has become a critical function helping organizations refine their business strategy and capabilities.Recognizing the unique role of information technology as the key driver to competitiveness and innovation, Enterprise Architecture effectively manages incorporating various stakeholders concerns in defining systems requirements and adapting systems modernization to the organization business processes documenting an Enterprise Architecture offers the following benefits:
-allows seamless integration of disparate systems
-promotes open standards
-prevents single vendor lock-in
-articulates every stakeholders’ concerns
-reduce complexity and cost while improving efficiency
-offers a blueprint for evolving the enterprise processes
-map & orchestrate enterprise change and innovation
-implements enterprise-wide risk management, etc
A component-based approach gathers a comprehensive highly detailed formal description of the environment, design principles, structure, entities and relationships governing the organization whole set of enterprise architecture called artifacts.
ARCHITECTURE DEVELOPMENT METHODOLOGY
An architecture framework such as TOGAF can be conceptually divided into four sub domains:
1.The Business Architecture describes strategy, governance and the organization with its key business processes.
2.The Data Architecture assigns a logical and physical attribute to the organization data assets. The logical part helping understand the logical flow of organization data as part of the business processes.
3.The Application Architecture offers a listing of the different applications deployed, their interactions, and relationship to the core business processes of the organization.
4.The Technology Architecture describes the set combination of the software and hardware capabilities and their logical functions in support of the business data and application operations.
Using a model-based approach
TOGAF uses the term Enterprise Continuum to describe the family of assets, models, patterns, architectures, descriptions form the industry body of knowledge.
ABB (Architecture building blocks) offers open industry standards defining services and components of enterprise specific architecture.
The Federal Enterprise Architecture reference model is used by federal government to map its services, strategic objectives, missions and capabilities to the underlying physical infrastructure of integrated systems, human resources and processes horizontally across mission entities and lines of business.
performance reference model
business reference model
service component reference model
data reference model
technical reference model
DELIVERABLES
Developing an Enterprise Architecture entails a tedious amount of work gathering organization functional mission descriptions, processes and operations, documents highlighting the strategic imperatives and combining them to the information/technology artifacts. A realistic and cost effective approach relies in selecting an appropriate framework for developing models that leverage on the Continuum and other industry-wide open standards:
1.Identify Enterprise assets
-programs
-processes
-information
-applications
-technology
-investments
-personnel
-organizations
-facilities
2.A reference model governing assets use
-performance model
-business model
-data model
-services model
-technology model
PLEASE CONTACT US FOR FURTHER INQUIRY OR USE THE FORM BELOW
