1 / 15

ITAG Face-to-Face -10/18/2010

ITAG Face-to-Face -10/18/2010. Marina Arseniev. Contents. Enterprise Architecture in OIT/AdCom Technical Reference Architecture Our EA Repository Architecture Initiatives Realized Value Next Steps. Our Enterprise Architecture.

mari-cross
Download Presentation

ITAG Face-to-Face -10/18/2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITAG Face-to-Face -10/18/2010 Marina Arseniev

  2. Contents • Enterprise Architecture in OIT/AdCom • Technical Reference Architecture • Our EA Repository • Architecture Initiatives • Realized Value • Next Steps

  3. Our Enterprise Architecture • Scoped to campus Administrative Applications and on hold due to campus IT consolidation and Kuali KFS. • Strategic information repository to plan change and impact • Life cycle management, governance • Control proliferation and retirement of technology • How many databases engines do we own? Where are they used? • Application and data security for HIPAA, PCI, SB1386 • Extraction of “Common Requirements” across projects into patterns of reusable tested components

  4. What did we do? • Created a Technical Reference Architecture (2002) • maintain technology lifecycle and architectural control • being re-implemented as part of a tools inventory for the IT consolidation at UC Irvine however, as a low priority. • Adopted Zachman Enterprise Architecture Framework • powerful thinking and organization tool • logical – not J2EE, .Net, Portal, or WebServices • Moving towards TOGAF – slowly…

  5. What did we do, continued • Adopted Stanford’s Protégé Knowledgebase & Ontology Tool for Repository of critical business and technical information • Created a taxonomy model to answer specific questions - lists of applications and how they full-fill goals and initiatives. • Minimized redundancy, increased consistency of information • Populated the Model • Protégé auto-generates forms for capturing information • Forms based on our ontology and class definitions • Cross-link important facts (Projects to Technologies, etc) for slicing • Documented SDLC and a change management process

  6. Our Governance • Immature • Technical Reference Architecture – scoped to critical Administrative Applications • yearly reviews by senior IT staff • Protégé Strategic EA Information Repository • quarterly review and updates by Team Leaders on hold • EA Infrastructure Planning • senior staff agree on common requirements and define reusable components and centralized IT services (TFS…) as needed • Working on data inventory and governance - proposal stage

  7. Documented principles, guidelines, and best practices of Architecture Domains: Lifecycle Management Adopt the “4 year/16 Quarter Sliding Window Methodology” Identifies technologies that are “Approved”, “Maintained but not Upgraded”, in “Sunset”, “Retired”, or “By Approval Only”. Technical Reference Architecture

  8. Our EA Repository – on hold • model uses Zachman EA Framework concepts • stores strategic information – a subset of the Technical Reference Architecture • goals articulated • initiatives, roadmaps, projects linked to goals • technology linked • change strategy • communication tool

  9. Example: Protege

  10. Example: Protege

  11. Realized Value • Technologies retired or consolidated • database and windows servers consolidated • reduced Admin and DBA costs • CICS and Foxpro retirement in progress • Reduced development costs • tested code reuse (SOA reuse for student fee submission) • reuse of staff skill sets • common infrastructure for development that is platform independent

  12. Next Steps • Focus on campus IT Consolidation and low hanging projects rather than on Enterprise Architecture • Focus on replacement of Financial System possibly with Kuali (Proof of Concept in progress) • Complete OIT Tools Inventory and fold it into a simplified consolidated IT Technical Reference Architecture. • Implement Technology Governance per TOGAF9 • Get executive buy-in after campus consolidation settles down and urgent projects are well under way

More Related