An introduction to enterprise architecture

The enterprise architect can achieve this on the design level using AquaLogic BPM designer, for example. This common work should lead to a common language and a common taxonomy shared holistically throughout the organization.

Enterprise architecture as strategy pdf

A common language will promote the reuse of the functional building blocks and the data that will be shared between those blocks. These business services are the ideal SOA building-block candidates. The chosen patterns will work with everything else. In the context of the banking example, the accounting services and the authorization services are being reused on the organization level. Those entities will be represented by canonical models, one for the account data and another for client data. Because its perspective is very long-term, and organization-wide, it needs to be able to talk with high-level administrators and you will typically pay these people a lot of money. Governance considerations should define the way those models should be designed, accessed, validated, and amended. I won't describe the technical plan in detail, my main objective being to propose an approach promoting a better alignment of IT to business through a common ground. Project teams browse a catalog of patterns to identify what work is needed. Those messages can be easily mapped to XML messages that then can be used throughout the organization. Enterprise architecture is most commonly associated with information technology. That way the problem is solved not just for the current service but for all future services. These services should have the necessary capabilities to be reused and recomposed, providing the agility required by the business. The business processes plan is owned by the business.

These business services are the ideal SOA building-block candidates. A city-planning metaphor can be used in this plan: Assembling the functional building blocks into quarters and zones relate to the different lines of business in the organization.

Enterprise architecture as strategy ebook pdf

The authorization block may rely on functions in the risk management block. Those models will be shared holistically through the organization. They are accessed through common services that are part of the organization building blocks. Enterprise Architecture supports IT process improvement, by creating a place for process improvement knowledge to be stored and used again. After identifying those functional building blocks, communication between those blocks should also be defined, which means a canonical data model is defined. These functions are the business services of the LC block; these services will rely on functions provided by the authorization block, by the accounting block, and by the payment block. It consists of describing the current and future structure and behavior of an organization's processes, information systems, personnel, and organizational business units so they align with the organization's strategic direction, going beyond information technology. The account and client are the entities defined in the shared business models across the organization. Every line of business forms a quarter when applying the city-planning metaphor. The architect's role consists mainly of capturing the business needs and identifying common business services usable through different business lines in an organization. This common work should lead to a common language and a common taxonomy shared holistically throughout the organization. Common entities and common domain models are defined in such a way that they have common meaning in the organization and can be reused in different lines of business. Enterprise Architecture supports service management, by informing Service Design.

I will describe them in more detail. Enterprise Architecture supports IT process improvement, by creating a place for process improvement knowledge to be stored and used again.

enterprise architecture as strategy pdf

Enterprise Architecture supports service management, by informing Service Design. Governance considerations should define the way those models should be designed, accessed, validated, and amended.

Enterprise architecture at work: modelling, communication and analysis

This common language should be shared across the entire organization. Can you build a city without a city planner? This common work should lead to a common language and a common taxonomy shared holistically throughout the organization. In the context of the banking example, the accounting services and the authorization services are being reused on the organization level. Lines of business participation in the choice of those functional blocks and the data that needs to be shared by those blocks should provide enterprise architects the necessary business knowledge to allow the canonical data models, domain UML models, and data repositories to be reused and understood by the entire organization. The idea is these people are overall saving the organization a lot of time and money by enabling change, reducing the costs of those changes, and increasing the quality of everything they touch. I will describe them in more detail. The chosen patterns will work with everything else. Both processes should be using common authorization services and common accounting services. After identifying those functional building blocks, communication between those blocks should also be defined, which means a canonical data model is defined. These services should have the necessary capabilities to be reused and recomposed, providing the agility required by the business. EA patterns can be designed to ensure high levels of warranty. Using AquaLogic BPM Designer, business analysts can simulate the business processes, providing a measurement of the optimization that occurs when doing process reengineering. I won't describe the technical plan in detail, my main objective being to propose an approach promoting a better alignment of IT to business through a common ground.

It consists of describing the current and future structure and behavior of an organization's processes, information systems, personnel, and organizational business units so they align with the organization's strategic direction, going beyond information technology.

The current enterprise architecture should ideally be controlled by governance groups. In the context of the banking example, the accounting services and the authorization services are being reused on the organization level. An Introduction to Enterprise Architecture by Gabriel Bechara Pages: 1, 23 Enterprise architecture relates to the practice of business optimization that addresses business architecture, performance management, organizational structure, and process architecture.

Rated 7/10 based on 45 review
Download
A brief introduction to enterprise architecture (EA)