Introduction to the Unit

1. INB/N 205 Enterprise Architecture Lecture 1 Introduction to the Unit Prof. Alistair Barros

2. INB/N 205 Teaching Team • Unit Coordinator: Prof. Alistair Barros • Consultation times, Fri 10-11am • Tel: 3138 1199 • Office: Room 506, Level 5, 126 Margaret St. • Email: alistair.barros@qut.edu.au • Lecturer/tutor: Dr. Bhuva Lakshminaryan • Lecturer/tutor: Ayed Alwaidain • Plus guest lecturers

3. Objectives of unit • To provide a holistic and integrated view of complex enterprises, integrating business practice and IT, through enterprise architecture frameworks • To provide insights in different enterprise architecture methodologies • To develop skills in modelling techniques and languages at the different layers of enterprise architectures

4. Objectives of unit • To consolidate on software application design skills through use of integrated modelling techniques and languages

5. Outcomes of unit • Explain what an enterprise architecture consists of • Contrast different enterprise architecture methodologies and their relative strengths and weaknesses • Apply techniques for analysis at the business level and designing a software solution. This will include integrated data and process modelling and software service mapping;

6. Outcomes of unit • Undertake an enterprise architecture use case • Communicate an architecture at different levels for different stakeholder audiences

7. What is an Architecture? • Architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principle guiding its design and evolution. IEEE Standard 1471-2000

8. Why? • These frameworks integrate the multiple dimensions and views of complex organisations & • Give you a coherent appreciation of alternative modelling techniques used by different sets of professionals designing, implementing and maintaining business planning & operations, business applications and IT infrastructure

9. Because • These concepts are foundational for all IT professionals, for regardless of what you design, develop, administer, procure or govern • Your work impacts a whole organisation – the Enterprise – not just IT

10. Business Intelligent Applications Enterprise applications Legacy application modernization Networking, voice and data communications Server and storage technologies (virtualization) Security technologies Service oriented architectures Technical infrastructure management Documents management Collaboration technologies Top 10 Technology Priorities 2010 Source: Gartner EXP (February 2007)

11. Business and CIO Priorities Business Near Term Expectations of IT • Improve business process • Control enterprise cost structures • Attracting retaining and growing customers • Improve workforce effectiveness • Grow Revenue CIO Near Term Strategies for IT • Improve the quality of IT services • Improve IT governance • Improve the link between business and IT • Demonstrating the business value of IT • Building business skills in IT Source: Gartner EXP (February 2007)

12. SAP, Oracle and Peoplesoft specialists PHP developers C++/CORBA developers Unix network administrators Business analysts Java and J2EE developers Lotus Notes specialists C# developers .NET developers Senior testers Top Tech Jobs 2010 Data compiled based on information from Ambit Recruitment Group, The Olivier Group, Macro Recruitment, Hays Information Technology, the Department of Employment and WorkPlace Relations, and ZDNet Research 2010

13. Professional roles related enterprise architecture Macro-level in enterprise • Business analyst • Solution manager • Product manager • Information manager • Enterprise architect • IT Governance Manager Micro-level in enterprise • Project Manager • Solution architect • Systems architect • Technical architect • Developer/architect

14. Business and IT Dependencies Business level Business process Business products Business information Business services Organisation structure IT level Computing infrastructure Software application End-user devices IT Platform

15. Defence 3427 information systems 200 in inventory management, warehouse and distribution alone! 3 Enterprise Systems! Peoplesoft for HR SAP R/3 for Finance Mincom’s Mims for Logistics 3 Different platforms, each with its own technical support and application support staff Several different WAN Operational Administration Public 100,000 PC’s Queensland Health 13th largest in Australia Information Systems Portfolio 45 corporate systems 1 Enterprise System delivering Financial System Support (SAP) 1 HR System delivering HR support (AURION) 4,000 local systems Technical Environment 400 networked sites 700 servers 22,000 desktops 28 sizable “data centres” 250 PABXs 290 videoconferencing sites 150 satellite television sites Sample Complexity in Organisation

16. A stand-alone program. It implies an application that does not integrate with or share data or resources with other applications University example – stove pipe applications • Enrollments and Billing • Developed separately, for different people, for different purposes. • What information do they need to share? • What are some problems if they are on different systems (e.g. IBM mainframe and Dell server?) • How do they connect (network issues, security issues) • What are some issues related to privacy of data (e.g. addresses, telephone numbers, ages …)

17. Other Examples • QUT • http://www.its.qut.edu.au/qutinfosys/ • Student information system project • Ipswich City Council • http://www.zdnet.com.au/insight/toolkit/businessapps/erp/soa/Ipswich_City_Council_plans_IT_led_transformation/0,39028255,39215929,00.htm • 750 application systems for 1200 employees • Many Access DB and Excel Spreadsheets • EventPro (for event management) 3 different versions • http://www.itwire.com.au/content/view/2172/49/ • http://www.cio.com.au/pp.php?id=683917670&fp=512&fpid=128555889

18. Ipswich City Council • “Ipswich City Council plans to embark on a major enterprise resource planning (ERP) implementation after signing Fujitsu Australia to help deliver a AU$37 million business transformation project. The council has signed a four year contract with the services vendor -- encompassing supply of hardware and software, provision of consulting resources and expert methods -- to assist in the business project, which includes the ERP implementation. • Ipswich City Council information technology board chairman councillor Paul Tully said the total project budget over its lifespan would exceed AU$37 million. • The contract builds on a series of projects between the council and Fujitsu over the past 12 months.” http://www.zdnet.com.au/insight/toolkit/businessapps/erp/soa/ Ipswich_City_Council_plans_IT_led_transformation/0,39028255,39215929,00.htm

19. And in Information Management John Zachman in the preface to Introduction to Enterprise Archictectures Scott Barnard

20. Also in Information Systems …. John Zachman in the preface to Introduction to Enterprise Archictectures Scott Barnard

21. So to become relevant & ensure continued relevance John Zachman in the preface to Introduction to Enterprise Architectures Scott Barnard

22. Also in Information Systems …. Enter Enterprise Architecture

23. Conceptual Layers of Enterprise Strategic (mission, goals, policies) Tactical (policies, capabilities, functions) Operational (business channels, business services, Business processes, business info, org. resources/roles) IT Operational (end user devices, software applications, middleware platforms, computing infrastructure, networking)

24. Web services choreography . . . Company A Company B External web services Web services orchestration Internal web services Business objects Application adapters Legacy applications IT Service-Oriented Architecture

26. Zachman Framework for Enterprise Architecture abstractions DATA What FUNCTION How NETWORK Where PEOPLE Who MOTIVATION Why TIME When perspectives List of Things - Important to the Business List of Processes - the Business Performs List of Organizations - Important to the Business List of Events - Significant to the Business List of Business Goals and Strategies List of Locations - in which the Business Operates SCOPE Planner contextual Entity = Class of Business Thing Function = Class of Business Process Node = Major Business Location People = Class of People and Major Organizations Ends/Means=Major Business Goal/Critical Success Factor Time = Major Business Event e.g., Logistics Network e.g., Semantic Model e.g., Business Process Model e.g., Work Flow Model e.g., Master Schedule e.g., Business Plan ENTERPRISE MODEL Owner Process = Business Process I/O = Business Resources conceptual Entity = Business Entity Rel. = Business Relationship Node = Business Location Link = Business Linkage People = Organization Unit Work = Work Product Time = Business Event Cycle = Business Cycle End = Business Objective Means = Business Strategy e.g., Application Architecture e.g., Logical Data Model e.g., Distributed System Architecture e.g., Human Interface Architecture e.g., Processing Structure e.g., Business Rule Model SYSTEM MODEL Designer logical Time = System Event Cycle = Processing Cycle Entity = Data Entity Rel. = Data Relationship Process.= Application Function I/O = User Views Node = IS Function Link = Line Characteristics People = Role Work = Deliverable End = Structural Assertion Means =Action Assertion e.g., Physical Data Model e.g., System Design e.g., Technical Architecture e.g., Presentation Architecture e.g., Control Structure e.g., Rule Design TECHNOLOGY CONSTRAINED MODEL Builder Node = Hardware/System Software Link = Line Specifications physical Time = Execute Cycle = Component Cycle People = User Work = Screen/Device Format End = Condition Means = Action Entity = Tables/Segments/etc. Rel. = Key/Pointer/etc. Process= Computer Function I/O =Data Elements/Sets e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification e.g. Data Definition e.g. Program DETAILED REPRESEN- TATIONS Subcontractor out-of-context Node = Addresses Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-condition Means = Step Entity = Field Rel. = Address Process= Language Statement I/O = Control Block FUNCTIONING ENTERPRISE DATA Implementation FUNCTION Implementation NETWORK Implementation ORGANIZATION Implementation SCHEDULE Implementation STRATEGY Implementation

27. NETWORK Artifact (Where) The cells contain primitives e.g., Logistics Network Node = Business Location Link = Business Linkage Artifacts contain model data Described as Single-variable Model PEOPLE Artifact MOTIVATION Artifact DATA Artifact FUNCTION Artifact NETWORK Artifact TIME Artifact LOGICAL ARTIFACTS (What) (How) (Where) (Who) (When) (Why) Composite Models are the Work Products Designer’s View LogicalScenarios LogicalPackages Logical Interactions Logical Components Primitives to Work Products

28. <<entity>> <<entity>> TASC:Company Company Customer Description = <unspecified> + Description : char + Description : char persistent persistent Acme Business:Customer Systems Engineering:"Business Unit" Description = <unspecified> Description = <unspecified> <<entity>> Business Unit Alpha:Project + Description : char Name = <unspecified> <<entity>> Organization = <unspecified> Project Description = <unspecified> persistent + Name : char + Organization : char Enterprise Architecture:Section + Description : char Description = <unspecified> Beta:Project persistent Name = <unspecified> Organization = <unspecified> Description = <unspecified> <<entity>> <<entity>> Section Architectural Description + Description : char + Description : char persistent TASC:"Architectural Description" persistent Description = <unspecified> Business Concepts Example Model UML Class Diagram