BusinessIntegration.ppt

1、Introductory Remarks,The impetus for change,Business Integration and IT Alignment,Dale Hunter (.on.ca) Tony Brown (),Meeting the challenge with Enterprise Architecture,Information Highways Conference,March 24, 2004,2,Service Delivery,Connecting Government & Citizens,Building Intern

2、al Capacity,Partnerships,Privacy & Access,Security,Information Management,Infrastructure,Applying IM & IT in a comprehensive way to all functions of government,Transformation agenda,Government and cross-jurisdictional collaboration to drive social development, economic competitiveness and regulatory

3、 harmonization,Enterprise management systems and approaches that drive more value from investments, e.g., legacy renewal, back office reengineering, horizontal funding, project management and internal capacity building,Integrated, cross-jurisdictional service delivery through multiple channels that

4、is customer-focused, seamless and convenient,Connecting government and citizens through increased transparency and citizen engagement opportunities,3,The environment,e-Business and e-Government Distributed systems Heterogeneous platforms and languages Legacy and open source and new code and off-the-

5、shelf A need for inter-jurisdictional connectivity Wireless devices Privacy and security XML Financial constraints,4,Business Integration and IT Alignment,Business Integration and IT Alignment,Meeting the challenge with Enterprise Architecture,6,The questions to answer,What is business integration?

6、What is IT alignment and why is it important? What is enterprise architecture? How does it help you achieve business integration? How does it help you align IT investments with strategic business intentions? What is the Ontario Government doing?,7,What is business integration?,To integrate means to

7、combine parts into a whole.,Business merger example:,Company A,8,Business integration (cont.),Redefining business example 1:,Organization,Function,Function,Function,9,Business integration (cont.),Redefining business example 2:,Organization A,Organization B,Core Business A1,Core Business A2,Core Busi

8、ness A3,Core Business B1,Core Business B2,Core Business B3,Virtual Organization,10,Implications of integration,No discontinuity among meanings of concepts across the enterprise Concepts defined once and shared You reuse what has already been defined,Explicitly defined concepts are the Enterprises eq

9、uivalence of Standard Interchangeable Parts.,11,What is IT alignment?,Alignment means working towards a common goal.,IT alignment means all implemented information systems contribute to Managements vision of the organizations future state.,Why is this important?,12,The dilemma,the business is not de

10、fined or described very well? nobody can see much of what needs to be changed? intentions cannot be communicated or share easily? if there is little explicit to align IT solutions with?,How can anyone or any group manage integration and alignment if ,13,The problem,Business knowledge is often locked

11、 in peoples heads or in planning documents Whatever explicit knowledge that might exist is too difficult to analyze in their current forms System designers usually just design solutions for specific business requirements and their designs are not reusable in other applications,14,The remedy,Make bus

12、iness knowledge more explicit Make both business and IT knowledge more granular Make it graphical,Apply the discipline of enterprise architecture to it!,In other words ,15,Enterprise architecture,Descriptive representations of the fundamental components of a purposeful endeavour.,Every enterprise al

13、ready has architecture.,16,Enterprise architecture is ,A thinking tool for analysis, change management and decision making A communications tool Across the enterprise Across the extended enterprise A means to guide business integration and to align IT,How do you create enterprise architecture?,Start

14、 by breaking down the subject area into its essential parts.,The same problem that has faced thinkers for generations.,17,Thinkers ,Aristotle (384 322 BCE) Linnaeus (1707 1778) Mendeleev (1834 1907) Dewey (1851 1931),Aristotelian Syllogistic System Every Greek is a human. Every human is mortal. Ever

15、y Greek is mortal.,The Linnaean System Kingdom Phylum Class Order Family Genus Species,Dewey Decimal System 000 Generalities 100 Philosophy & psychology 200 Religion 300 Social sciences 400 Language 500 Natural sciences & mathematics 600 Technology (Applied sciences) 700 The arts 800 Literature & rh

16、etoric 900 Geography & history,Periodic Table of Elements, and for enterprise knowledge Zachman (1936 - ),18,Zachman says,Inherent in all enterprises are six abstract perspectives.,Plannerthe scope and boundary view,Ownerthe business requirements view,Designerthe logical design view,Builderthe physi

17、cal, technical view,Subcontractorthe detailed components view,Userthe functional view,19,Different aspects or focuses,Whatis itmadeof?,And for each perspective there are six fundamental focuses.,Howdoes itfunction?,Wherearethingslocated?,Whoisinvolved?,Whendothingshappen?,Whyarethingsdone?,20,The Fr

18、amework for Enterprise Architecture,is formed by associating perspectives and focuses.,WHAT,HOW,WHERE,WHO,WHEN,WHY,PLANNER,OWNER,DESIGNER,BUILDER,SUB-CONTRACTOR,USER, 36 different representations for describing an enterprise.,Cells of knowledge,Zachman Framework for Enterprise Architecture,22,Zachma

19、n framework,A device for classifyng enterprise knowledge A framework for describing enterprises (for modeling them) Reduces complexity to manageable proportions Is easy to understand Unites business and IT communities,OK, but what about content?,Zachman Framework for Enterprise Architecture,Importan

20、t Fact #1: Business integration will not occur unless this knowledge is made explicit, shared and reused.,Important Fact #3: IT alignment will not occur unless lower level models are constrained by the upper level models.,Important Fact #2: Business integration will not occur unless you use these mo

21、dels to engineer commonality across the enterprise,24,Ultimate aim,IT Infrastructure,25,Reality check #1,Attempts to architect enterprises from top to bottom always fail not feasible Managements intentions can at least be made explicit at the top feasible System designers can at least use that infor

22、mation, then provide slivers of architecture back to the framework when projects are implemented feasible?,26,Reality check #2,System designers use different automated design tools and modeling languages Raises question of feasibility of drawing info from a common source and putting new info back in

23、,27,Architecture Design Continuum,Which processes involve water safety inspectors?,What transactions require authentication and authorization?,What services would be affected if we change the privacy policy?,If we stop doing these functions, what organization units are affected?,28,Case Study: Ontar

24、io Goverment,Public service transformation (since mid-1990s) e-Government EA program to faciliate integration and IT alignment across government,29,Ontario Government EA program,Advanced Dedicated resources Strong governance structure Integrated with IT planning and approval process Zachman framework approach for creation of architecture products,30,But,31,Which limits ,32,EA advancement requires ,EA models that are: granular (in the form of data) exportable to system design tools System designs that are: created from enterprise models exportable as data A repository,Due to