THE VALUE AND RISK OF CREATING AN EA Pertemuan_4 Pokok Bahasan :

Slides:



Advertisements
Similar presentations
1 © 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA Flatten, Consolidate & Extend (FCE) FCE Planning Presenter Name.
Advertisements

KOMUNIKASI DALAM MENDUKUNG PENGAMBILAN KEPUTUSAN Pertemuan-7 Mata Kuliah : CSS 113, Konsep Sistem Informasi Tahun Akademik : 2012/2013 Sasaran Pembelajaran.
1 Pertemuan 12 Perencanaan Sistem Informasi Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
POKOK BAHASAN Pertemuan 10 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
Enterprise Architecture The Arkansas Approach. Key Areas What is enterprise architecture? Why is it important? How you can participate Current status.
1 Aspects of IT investment decision process Pertemuan Matakuliah: A Evaluasi Efektivitas Sistem Informasi Tahun: 2006.
POKOK BAHASAN Pertemuan 4 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
POKOK BAHASAN Pertemuan 25 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
1 Pertemuan 5 Bisnis Proses Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
Pertemuan 9-10 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Pertemuan 15 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
POKOK BAHASAN Pertemuan 3 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
DECISION SUPPORT SYSTEM DEVELOPMENT
Mata Kuliah: CSS 113, Konsep Sistem Informasi Tahun Akademik: 2012/2013 Konsep WCA (Work Concept Analysis) Pertemuan - 2 Learning Outcomes Pada akhir pertemuan.
Enterprise Architecture Repository Auckland Council 5 September 2013.
ARCH-6: UML Modeling with Enterprise Architect Phillip Magnay Technical Architect.
Chapter 15 Systems Development
Disaster Management Component Bishkek – 2005 Prepared by Irina Elebesova.
© 2013 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Achievement of an Integrated Applications Environment Enterprise.
Enterprise Architecture Enterprise Architecture = a framework or ‘blueprint’ for how the organization achieves the business objectives at hand and in future.
THE ROLE OF INVESMENT PLANNING AND PROJECT MANAGEMENT Pertemuan-10 Mata Kuliah: CSP311, Perencanaan Strategi Sistem Informasi Tahun Akademik:
1 Pertemuan 26 Making It Happen Matakuliah: A0194/Pengendalian Rekayasa Ulang Informasi Tahun: 2005 Versi: 1/5.
DEVELOPING FUTURE ARCHITECTURE VIEW PERTEMUAN-8 Mata Kuliah : CSP311 Perencanaan Strategic Sistem Informasi Tahun Akademik: 2012/
IT GOVERNANCE  Objective : The objective of this area is to ensure that the Certified Information Systems Auditor ( CISA ) candidate understands and can.
FUTURE TRENDS IN ENTERPRISE ARCHITECTURE Pertemuan-14 Learning Objectives  Familiarize the reader with current issues in the practice of EA  Stimulate.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
POKOK BAHASAN Pertemuan 22 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
Dynamic Trading Pertemuan Mata kuliah: M Konsep E-Business Tahun: 2010.
Systems Thinking and BPR *Traditional Business organisation *Process Based Organisation *Getting from one to the other *Things to think about along the.
E-Supply Chain and Collaborative Commerce Pertemuan Mata kuliah: M Konsep E-Business Tahun: 2010.
TechOrchard Phil Poje, CEO. Benefits and Risks Data Breaches BYOD Mobile Device Management.
12-CRS-0106 REVISED 8 FEB 2013 APO (Align, Plan and Organise)
KNOWLEDGE MANAGEMENT Pertemuan-8
February 24, 2015 Risk Based testing. February 24, What is Risk Based Testing? Process of focusing a project's testing activities on the most important.
Mata Kuliah: CSP 311, Perencanaan Strategi Sistem Informasi Tahun Akademik : 2012/2013 IMPLEMENTATION METHODOLOGY Pertemuan_4 Pokok Diskusi : Section 2:
Shaping the FutureOHT 0.1 SHAPING THE FUTURE MODULE 0: WELCOME AND INTRODUCTION.
Select Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
POKOK BAHASAN Pertemuan 21 Matakuliah: Sistem Informasi Manajemen Tahun: 2008.
IT INVESTMENT MANAGEMENT FRAMEWORK Pertemuan 3-4
Mata kuliah : – CRISIS COMMUNICATION AND PUBLIC REALTIONS
MANAGING THE DATA Sasaran Pembelajaran
THE ENTERPRISE ARCHITECTURE REPOSITORY AND SUPPORT TOOLS Pertemuan-12
AN OVERVIEW OF ENTERPRISE ACHITECTURE (EA)
POKOK BAHASAN Pertemuan 9
Able to locate how an EA framework establish the scope of an EA
Mata kuliah : – CRISIS COMMUNICATION AND PUBLIC REALTIONS
Mata kuliah : – CRISIS COMMUNICATION AND PUBLIC REALTIONS
The Information Society and E-Government
Approaches and instruments for sustainable rural development
Mata kuliah : – CRISIS COMMUNICATION AND PUBLIC REALTIONS
ERP [ Enterprise Resource Planing ]
Identify hazards to the force
Able to locate how an EA framework establish the scope of an EA
ENTERPRISE RESOURCE PLANNING- ERP UNIT-1 INTRODUCTION Overview of Enterprise System Evolution Risks and Benefits Fundamental Technology Issues to be consider.
Project Roles and Responsibilities
Introduction to Enterprise Architecture
SIS Modernization project
دانشگاه شهیدرجایی تهران
تعهدات مشتری در کنوانسیون بیع بین المللی
CAF Quarterly Meeting Measuring the Value of an EA Practice
Simple VS FULL LEADING PRACTICE
3.4 Outcomes Photocopy Management
ESS.VIPs and IT related aspects
POKOK BAHASAN Pertemuan 23
MFP opens doors to community living options.
Review of the Incident Command System
SAMPLE COST ROLL-UP Sample OVERALL COST ROLL-UP
G318 Mitigation Planning Workshop Region 10
ESS.VIP.SERV Shared Services
Systems Architecture and Engineering
Presentation transcript:

THE VALUE AND RISK OF CREATING AN EA Pertemuan_4 Pokok Bahasan : Mata Kuliah : CSP 311 , Perencanaan Strategi Sistem Informasi Tahun Akademik : 2015/2016 THE VALUE AND RISK OF CREATING AN EA Pertemuan_4 Pokok Bahasan : Able to describe the potential value of the EA Able to interpret the risks associated with implementing an EA Able to employ an approach for measuring the costs and benefits of an EA program Able to describe how EA helps integrate strategy, business and technology

Diskusi : Let read home architecture analogy (pp.63) Let discuss about: value; improved planning; decision planning; communications; managing risk and several types of risks; mitigating risks. Quantifying EA Program Value: Shortening Planning Cycles; More Effective Planning Meetings; Shorter Decision Making; Improved Reference Information; Reduction of Duplicative Resources,; Reduce Re-work; Improved Resourced Integration and Performance; Fewer people in a process, Improve Communication, Reduction in Cycle Time.

Diskusi : Quantifying EA Program Value (cont’d): Improved Resourced Integration and Performance; Fewer people in a process; Improve Communication; Reduction in Cycle Time. Quantifying EA Programs Costs: EA program administration and other enterprise administrative tie-ins; salary/benefits for a Chief Architect and EA team staff; etc Linking Strategy, Business and Technology Linking EA and Strategy Linking EA and Business Planning Linking EA and Technology Planning ========== thank for your attention ==========