Enterprise Architecture supporting the change by Vladimir Calmic Endava
•Download as PPSX, PDF•
1 like•727 views
The document discusses enterprise architecture (EA) and its benefits. It defines EA as a logical view of an organization's key capabilities and how they are linked together. EA involves defining changes from both a top-down and bottom-up approach using business, application, and technology building blocks. Adopting EA can improve efficiency, reduce costs, increase manageability and consistency within an organization. The document recommends starting to think about EA, using architecture development methods, embracing service-oriented architectures and cloud technologies.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Enterprise Architecture supporting the change by Vladimir Calmic Endava
Similar to Enterprise Architecture supporting the change by Vladimir Calmic Endava (20)
More from Moldova ICT Summit
More from Moldova ICT Summit (20)
Recently uploaded
Recently uploaded (20)
Enterprise Architecture supporting the change by Vladimir Calmic Endava
- 1. Enterprise Architecture supporting the change Author: Vladimir Calmic Date: 17.04.2013
- 2. Agenda •Enterprise Architecture •Defining the change •Benefits of EA adoption 2
- 3. Enterprise Architecture IN YOUR ZONE 3
- 4. Enterprise Architecture: Logical view IN YOUR ZONE 4
- 5. Enterprise Architecture: Change Management Corporate Governance Functional Management Corporate LoB IT Portfolio Portfolio Portfolio Capability 1: Printing Capability Capability 2: Documents Management Management Project Project Project Project Project Project Project Project Project Corporate IT Infrastructure IN YOUR ZONE 5
- 6. Enterprise Architecture: Capabilities Corporate LoB IT Portfolio Portfolio Portfolio IN YOUR ZONE 6
- 7. Enterprise Architecture: Domains Corporate LoB IT Portfolio Portfolio Portfolio Business Data Application Technology IN YOUR ZONE 7
- 8. Defining the Change Building block top-down Business Data Application Technology bottom-up IN YOUR ZONE 8
- 9. Benefits of EA adoption •Efficiency •Cost-cutting •Manageability •Consistency •Go-green ! IN YOUR ZONE 9
- 10. EA tips & tricks •Start thinking EA •Architecture Development Method •Service Oriented Architecture •Don’t model – Transform ! •Continuous improvement IN YOUR ZONE 10
- 11. Embrace the “Cloud” IN YOUR ZONE 11
- 12. This guy has nothing to do with the EA IN YOUR ZONE 12
- 13. Thank you ! Vladimir Calmic | Solutions Architect vladimir.calmic@endava.com Tel +373 22 806 751 IN YOUR ZONE 13
Editor's Notes
- The goal of enterprise architecture is to create a unified IT environment (standardized hardwareand software systems) across the firm or all of the firm’s business units, with tight symbioticlinks to the business side of the organization (which typically is 90% of the firm as seen earlier,at least by way of budget) and its strategy. More specifically, the goals are to promote alignment,standardization, reuse of existing IT assets, and the sharing of common methods for projectmanagement and software development across the organization. The end result, theoretically,is that the enterprise architecture will make IT cheaper, more strategic, and more responsiveThe purpose of enterprise architecture is to create a map of IT assets and business processes anda set of governance principles that drive an ongoing discussion about business strategy and how itcan be expressed through IT. There are many different suggested frameworks to develop an enterprisearchitecture, as discussed later on. However, most frameworks contain four basic domains,as follows: (1) business architecture: documentation that outlines the company’s most importantbusiness processes; (2) information architecture: identifies where important blocks of information,such as a customer record, are kept and how one typically accesses them; (3) application systemarchitecture: a map of the relationships of software applications to one another; and (4) the infrastructuretechnology architecture: a blueprint for the gamut of hardware, storage systems, andnetworks. The business architecture is the most critical, but also the most difficult to implement,according to industry practitioners [KOC200502].