slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
November 2006 PowerPoint Presentation
Download Presentation
November 2006

November 2006

206 Vues Download Presentation
Télécharger la présentation

November 2006

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Enterprise Architecture Overview November 2006

  2. Our Areas of Interest • Business – HE Functional Reference Models • Platform Standards – Taxonomy • Architecture Governance • What other Universities are doing in this space • Methods/Tools being used to achieve goals of EA

  3. Where we have come from • Organisational change – 2005 restructure • Legacy Technology unable to support the business going forward • Little or No standards / methodology • No one overseeing the “bigger picture” across the organisation • Decentralised IT

  4. Enterprise Architecture and UoN • Very early stages • Major business and systems change • Organisation Restructure completed early 2006 • Centralised IT • Program of Works (EPMO) within IT • Formation of roles/groups (AAG, CAB, PoW, Change Office, IT Governance Committee) • Introduction of Groups and Processes • Start of ITIL implementation, Change Office (PMO), “formalised” Project Methodology and SDLC, Architecture Governance, Standards • Enterprise Architecture Consultant – “EA in a box” • Light inventory across Business, Information, Applications, Technology • Provided principals, some mapping between inventories, gap analysis • Current Activities/Changes/Lack of Ownership made this difficult – “hitting a moving target” • Tool - System Architect

  5. Enterprise Architecture and UoN • 2006 Program of Works • 50+ Projects with IT underpinning them • Infrastructure (network, server consolidation, etc) • Information Management (BI, ECMS) • Business (HR, Finance, Research, Students, Facilities, etc) • Teaching / Learning (Blackboard/LOMS, Academic Support) • Operational (ID Mngt, Integration,adopt mainstream technology) • Client Services (“17000” Centralised Service Desk, MOE, ITIL rollout) • NUWays: Focussed on Business Process Improvement and EPMO • Formed • Change Office • AAG – Architecture Advisory Group • CAB – Change Advisory Board • Project Portfolio’s – Program of Works

  6. Enterprise Architecture and UoN • Currently only used by IT • Covers PoW and operations • Reaction to the amount of project work being undertaken, realisation for EA out of PoW • AAG Membership • Enterprise Applications • Solutions Architect • Infrastructure • Security • Data Services • Client Services • Web Group • (Note: No Business Representation) • Bottom up approach to EA – driven by IT

  7. Challenges Experienced • Current IT Inventory = 100+ Main Applications • ~65% in-house developed – mainly “gap fillers” around the enterprise applications • Current upgrades will supersede some but still expected to be significant • Mixed blend of technology: • ERP, disparate systems • old and new technology • “islands of data” and “the spider web” of integration (point to point) • Time / Resources / Size of Work for Enterprise Architecture • Standards / Guidelines • Expectations of Business and IT • Implementation, Acceptance and Understanding of Enterprise Architecture within IT • Seen as a hold up for existing processes / projects

  8. Business Model • Business Direction • Stakeholders • Functions • Information Business Architecture Information Architecture Application Architecture • Data Model • Information Flows • Databases • Applications • Application Integration • Application Technology • Server Technology • Network / Communications • Platforms / Operating Systems • Database Systems • Security Technologies • etc. Technology Architecture Our Enterprise Architecture Framework

  9. Technical Application Information High Business Current Model T1 T2 Target Model Medium Detailed Architecture Development Process Business and IT Strategies ensure that architectures align with business needs and priorities Business Strategy IT Strategy Policies Principles give high level direction to enable decision making Enterprise Architecture Principles Architecture layers provide linkage between business models and technical architecture High-level context diagrams present broader picture Subject area models provide the linkage between the global context and projects Detailed models describe the subject matter at a project level Transition Plans provide the implementation “roadmap” Standards and guidelines provide specific direction on implementing architectures Technology Standards and Guidelines


  11. VALIDATEDEGREE INVOICESTUDENTS PROCESSPAYMENT or FUNDING Organise learning TRANSFERLEARNING DESIGNPROGRAM ATTRACTSTUDENTS ENROLSTUDENTS ADMITSTUDENTS ASSESSLEARNING Student Service Delivery Model Getpaid Deliverservices Develop services Get New Business Verify degreerequirementsmet Identify newprogram need Understand target markets Set/verifyadmission rules Set up/verifyProgram Set up/verifycharges Receivepayment Designlearning(1) Design exams (2) Apply payment againststudent debt Design program Promote university Applyadmission rules Set up/verifycourses Publish feecharges Organiseexams Organiseceremony Evaluateprogram(program review) Configure feesand rules(Nustar) Provide program information Makeoffer Publishprogram/courses Deliverlearning Conductexams Conductceremony Set up/verifytimetable(lectures) Run tuitioncalculationprocess (Nustar) Markexams Redesignprogram Providescholarships Set up/verifytimetable(tutorials) Validate and publish results Run billingprocess Reconcile forcompliance Program revised,new programoutlined Events hosted,materialsdistributed Program/courses/timetablespublished Paymentsreceived Gradepublished Degreeconferred Offer/No Offerproduced Learning(1)delivered Bill sent (1) learning includes: courses, lab, tutorial, placements (2) exams: includes all forms of evaluation (lab, tutorial, course work)

  12. Senior Executive level IT Governance Committee IT Management level IT Policy, Standards & Architecture Review Subject matter experts Architecture Advisory Group Adhoc working groups IT service delivery teams Vendors and consultants IT development teams Architecture Governance Model

  13. Business Architecture Information Architecture Application Architecture Technology Architecture Architecture Principles Information Architecture Principles Single Customer Identification Consistent Definition of Products Identification of Customer Contact Points Data Accessible Across University of Newcastle Timely Information Reuse Data Use One Data Master Single Algorithm for Each Business Measure Data Security Common Vocabulary and Data Definitions Centralised Analytical Data Repositories Application Architecture Principles Common Use Applications Ease of Use Re-use Before Buying Buy Before Building Minimise Package Modifications Component-based Architecture Channel and Device Independence Integration Services Independence Interfaces to External Environment Adopt Web-based Technologies

  14. Enterprise Architecture Model Architecture Services for Projects 2. Design 1.Discovery Business idea Project Charter Business Case Business Requirements Specification PROJECT PATH Functional Specification Project Management Technical Design Specification PTO Advice regarding implementation (eg cost/time) of technology solutions Preliminary advice re: solution options & architectural implications Ongoing advice to refine project shape Recommended technology solution 3. Detailed architectural analysis (environmental scanning; gap analysis; assessment of options etc) Solution Options 1. Preliminary consultation 2. Project planning advice Solutions Architect New/changed architectural components required by project Enterprise Architecture Principles Business trends and strategies Enterprise Architect New/changed architectural components required due to external factors Implementation of new/changed architecture components (those not project specific) Technology trends

  15. Enterprise Architecture Model Architecture Services for Projects 2. Design cont’d 3. Deployment Cont’d Technical Design Specification Issues Register PROJECT PATH Project Management Go Live Implementation of new/changed architecture components (project specific) Escalation of architectural issues Resolution of architectural issues Incorporate new/changed elements into the Enterprise Architecture Model Solutions Architect 4. Architectural compliance review 5. Architectural issues management Enterprise Architecture Principles Enterprise Architect

  16. Technology Architecture Components

  17. Where to from Now? • Adoption of Use of Enterprise Architecture outside of IT • Establish an EA group with a business focus • Learn and improve • Work collaboratively • Continual Development of Enterprise Architecture with alignment to the strategic direction of UoN • Become proactive rather than reactive

  18. Thankyou • David Hall • Program Director – Project Office • • Stephen Bosworth • Enterprise Applications • • Carey Steller • Solutions Architect •