bedoeld voor architecten modelleren van architecturen ICT en haar omgeving requirements ontwerpprincipes integratie van architecturen ihb tussen business- en ICT-architecturen consistentie van architecturen visualisatie van architecturen potentie van architecturen uitbuiten ontwerp en planning van nieuwbouw en veranderingen preventie en herstellen van systeemuitval communicatie ICT en business faciliteren what-if analyses mogelijk maken
Enterprise Architecture Strategy driven Enterprise Architecture Adrian Campbell
The response of IT was to become more precise, creating technology standards that appeared arbitrary to the business, requiring elaborate time consuming development processes and detailed documentation for new systems and changes to existing systems.
While IT believed that they were imposing a formal discipline on a chaotic system, the business could only see that these stringent requirements stifled innovation and made it difficult for the business to be agile in response to sometimes rapidly changing market requirements.
The current trend in organisations is a renewed focus on business process management (BPM).
This is now allowing business users to make immediate changes to their business process models (BPMN), combined with the technology to implement these changes in near real time, to a process orchestration and execution environment (BPEL).
This trend drives better business and IT alignment and the ability to trace the business strategy straight through to the business execution.
Leading organizations use a business strategy driven architecture approach that focuses on translating the key components of the business strategy into a future state vision and an architecture road map they can implement.
Enterprise architecture is integrated with other strategic planning disciplines, such as programme/project and application portfolio and management
The Enterprise Architecture ensures that the long-term vision of the business is preserved as the enterprise builds new business capabilities and improves on old ones.
A definition of Enterprise Architecture is addressed in 2 constituent parts – enterprise and architecture.
The Open Group defines ‘enterprise’ as follows:
An ‘ enterprise ’ is any collection of organisations that has a common set of goals and/or a single bottom line. In that sense, an enterprise can be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organisations linked together by common ownership.
Gartner define ‘ architecture ’ as follows;
The grand design or overall concept employed in creating a system, as in the architecture of a city or a customer information system; also "an abstraction or design of a system, its structure, components and how they interrelate"
A family of guidelines (concepts, policies, principles, rules, patterns, interfaces and standards) to use when building a new IT capability.
Enterprise Architecture is designed to ensures alignment between the business and IT strategies, operating model, guiding principles, and the software development projects and service delivery.
By taking a global, enterprise-wide, perspective across all the business services, business processes, information, applications and technology, Enterprise Architecture ensures the enterprise goals and objectives are addressed in a holistic way across all the application development projects and their deployment into production.
These architecture domains are interdependent and are developed simultaneously to ensure that the architecture reflects the optimal alignment of IT and the execution environment in support of the business strategy and target operating model.
Concerns the people perspective in the Enterprise answering the ‘Who’ question.
Addresses these in terms of the Locations, Business Actors (people and organisation units), Business Roles and Business Functions (responsibilities), from both an internal (staff, partners) and external (customers, agents) perspective.
An analysis tool to provide abstraction and modelling capabilities at all levels and perspective of the enterprise architecture
A planning tool to translate strategic thinking into architecture roadmap of future development and integration
An analysis tool to clearly plot the key relationships and dependencies between the business services, business processes, applications and technology
A decision-making tool to provide a framework for evaluating-, selecting and justifying strategic development options and architecture decisions
A design tool to provide the required support, in the form of industry best practice design approaches, patterns, guidelines, and reference models
A change management tool to provide a framework for synchronising and coordinating development activities across multiple development projects and initiatives
A governance tool to provide a sole architecture design authority and a master repository for the target enterprise architecture, and a single architectural blueprint of principles, standards, patterns, policies, guidelines, reference models, reusable assets and templates
An alignment tool to provide an essential bridge between business strategy and IT delivery, and to furnish business managers with a non-technical over view of the enterprise architecture and how it supports the operating model
Tool to model, visualize, analyze and communicate enterprise architectures
Based on meta model of open standard ArchiMate
Based on IEEE1471-definition: stakeholders, viewpoints and views
Covers all EA-domains and relations: business goals and principles, business services, products, processes, business functions, business objects, application services, applications, application data, interfaces, infrastructure services, software, hardware,…
Supports many architecture frameworks, like IAF, Zachman, DYA, Tapscott, Nolan-Norton, TOGAF
Concepts Archimate / Architect Business Application Technology Information Behaviour Structure Goals, principles, guidelines Goals, principles, guidelines