Enterprise Architecture

Consulting Services 

Our consulting services on Enterprise Architecture are supported by Industry Standards such as Zachman, TOGAF and eTOM, covering the following areas:


Business Vision 

Validate the business principles, business goals, and strategic business drivers of the organization. Identify and prioritize the components of the current architecture effort. Define the relevant stakeholders, and their concerns and objectives. Define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with. Secure formal approval to proceed


Business Processes

Describe the current baseline business architecture (using modeling tools such as UML). Develop a target Business Architecture, describing the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment, based on the business principles, business goals, and strategic drivers. Analyze the gaps between the baseline and target Business Architectures


Data, Components and Applications Architecture 

Develop target architectures covering either or both (depending on project scope) of the Data and Application Systems domains. Data: define the major types and sources of data necessary to support the business – define data entities – no database design. Applications: define the major kinds of application system necessary to process the data and support the business – described as logical groups of capabilities– without reference to particular technologies – stable and relatively unchanging over time, whereas the technology used to implement them will change over time


Infrastructure and Technical Architecture 

Develop a technology architecture that will form the basis of the following implementation work acording with the Technical Reference Model (TRM)


Identify Opportunities 

Evaluate and select among the implementation options identified in the development of the various target architectures (for example, build vs. buy vs. reuse options). Identify the strategic parameters for change, and the top-level work packages or projects to be undertaken in moving from the current environment to the target. Generate an overall implementation and migration strategy


Migration Planning 

Sort the various implementation projects into priority order. Generate a detailed implementation plan


Implementation Governance

Formulate recommendations for each implementation project. Perform appropriate governance functions while the system is being implemented and deployed. Ensure conformance with the defined architecture


Change Management

Provide for the continual monitoring of such things as new developments in technology and changes in the business environment, and for determining whether to formally initiate a new architecture evolution cycle


Requirements Management 

Not a static set of requirements, but a dynamic process whereby requirements for enterprise architecture and subsequent changes to those requirements are identified, stored, and fed into and out of the relevant ADM phases. Changes such as changing market conditions, new legislation and others.
Comments