11

Click here to load reader

Enterprise Architecture - why bother

Embed Size (px)

DESCRIPTION

Enterprise Architecture - business benefits and implications

Citation preview

Page 1: Enterprise Architecture  - why bother

Enterprise Architecture

Monthusiotsile Ngwako

1

Page 2: Enterprise Architecture  - why bother

Enterprise ArchitectureStaff (HR)

Business

Processes

Technology & Information

Flows

Finance

Other

Business

Resources

Business Goals

What is EA?• A framework that identifies main components of an organisation (staff,

business processes, Information Technology, financial and other resources), the ways in which they are integrated to achieve business goals and support business processes [1]

• The description of an enterprise as a system in terms of its components, their inter-relationships, and the principles and guidelines governing the design and its evolution [5]

Change

2

Page 3: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

3

Page 4: Enterprise Architecture  - why bother

Benefits and Implications of Using EA

Enterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

• Holistic approach when making decisions [5]• Enable managers to determine the need for

organisational transformation [3]• Understanding of what the enterprise does, when, where,

how and why it does it and what it uses to do it [4]• Improved communication among business departments

[2]

4

Page 5: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

• Better processes for implementing new technologies in response to the changing mission needs [5]

• Facilitate change to any business process [2]

5

Page 6: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

• Better return on existing investment, reduced risk for future investment [5]

6

Page 7: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

• Allow for integration of business disciplines which can reduce resource (time, skill) waste [3]

• Organisations can achieve economies of scale from prudence use of resources [2]

7

Page 8: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR)

Information SystemsSystems Behaviour

• Information Technology will be used to deliver desired business benefits

• Effective management and exploitation of information [5]• Enables the right balance between IT efficiency and business

innovation [5]• Increase accuracy, consistency , integrity, quality, timeliness and

access of information across an organisation [2]

8

Page 9: Enterprise Architecture  - why bother

Benefits and Implications of Using EAEnterprise Architecture

Business

TechnologyIT

Staff (HR) Business Processes Finance Other Resources

Information SystemsSystems Behaviour

• Holistic approach when making decisions [5]• Enable managers to determine the need for

organisational transformation [3]• Understanding of what the enterprise does, when, where,

how and why it does it and what it uses to do it [4]• Improved communication among business departments

[2]

• Better processes for implementing new technologies in response to the changing mission needs [5]

• Facilitate change to any business process [2]

• Better return on existing investment, reduced risk for future investment [5]

• Allow for integration of business disciplines which can reduce resource (time, skill) waste [3]

• Organisations can achieve economies of scale from prudence use of resources [2]

• Information Technology will be used to deliver desired business benefits

• Effective management and exploitation of information [5]• Enables the right balance between IT efficiency and business

innovation [5]• Increase accuracy, consistency , integrity, quality, timeliness and

access of information across an organisation [2]

9

Implications of EA For Entire organisation

• EA establishes standards and guidelines for developing IT system with other integrating components

• Create and maintain a common vision shared by both the Business and IT [6]• Develop a technical architecture framework to be used in all future ISProjects• EA developed in concert with strategic planners as well as the operational staff [2].• EA allows for regular updates of targeted architectures [2]

Page 10: Enterprise Architecture  - why bother

Conclusion

• EA closes the gap between business and IT• It allows decision makers to consider the

impact of their decisions on different components of an organisation

• It is not an IT discipline, but a fusion between Technology (including IT) and Business activities.

10

Page 11: Enterprise Architecture  - why bother

Reference1. Bailey I. (2006), A Simple Guide to Enterprise Architecture, retrieved 12 September 2010, from

www.modelfutures.com/file_download/4/SimpleGuideToEA.pdf

2. Chief Information Officer Council. (2001), The Practical Guide to Federal Enterprise Architecture, retrieved 11 September from, http://www.enterprise-architecture.info/Images/Documents/Federal%20Enterprise%20Architecture%20Guide%20v1a.pdf

3. Finkelstein C., Introduction to Enterprise Architecture, retrieved 07 September 2010, from http://www.ies.aust.com/pdf-papers/bi-ea01.pdf

4. Hirvonen A. (2007), Introduction to Enterprise Architecture, University of Jyväskylä, Finland.

5. Jabłonka R. (2009), Introduction to Enterprise Architecture using TOGAF 9, retrieved 11 September 2010, from http://www.sybase.at/pdf/TOGAF9.pdf

6. Schekkerman J. (2005). The Economic Benefits of Enterprise Architecture; How to Quantify and Manage the Economic Value of Enterprise Architecture. Trafford Publishing. Canada

11