Date post: | 22-Dec-2015 |
Category: |
Documents |
View: | 214 times |
Download: | 1 times |
University of California, Irvine
ITAG Face-to-Face -10/18/2010
Marina Arseniev
University of California, Irvine (Administrative Computing Services)
ContentsContentsEnterprise Architecture in OIT/AdComTechnical Reference ArchitectureOur EA Repository Architecture Initiatives Realized ValueNext Steps
University of California, Irvine (Administrative Computing Services)
Our Enterprise Architecture
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
impactLife cycle management, governance
Control proliferation and retirement of technologyHow 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
University of California, Irvine (Administrative Computing Services)
What did we do?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…
University of California, Irvine (Administrative Computing Services)
What did we do, continuedWhat did we do, continuedAdopted 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 ModelProtégé auto-generates forms for capturing informationForms based on our ontology and class definitionsCross-link important facts (Projects to Technologies, etc) for slicing
Documented SDLC and a change management process
University of California, Irvine (Administrative Computing Services)
Our GovernanceOur GovernanceImmatureTechnical 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 neededWorking on data inventory and governance - proposal stage
University of California, Irvine (Administrative Computing Services)
Technical Reference Architecture
Technical Reference Architecture
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”.
Developed Apps Vendor/ASP Apps Security Network Database Operations
Common Conceptual Architectural Principles
University of California, Irvine (Administrative Computing Services)
University of California, Irvine (Administrative Computing Services)
University of California, Irvine (Administrative Computing Services)
Our EA Repository – on holdOur EA Repository – on hold
model uses Zachman EA Framework concepts
stores strategic information – a subset of the Technical Reference Architecture
goals articulatedinitiatives, roadmaps,
projects linked to goalstechnology linked change strategycommunication tool
University of California, Irvine (Administrative Computing Services)
Example: ProtegeExample: Protege
University of California, Irvine (Administrative Computing Services)
Example: ProtegeExample: Protege
University of California, Irvine (Administrative Computing Services)
University of California, Irvine (Administrative Computing Services)
Realized ValueRealized ValueTechnologies 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
University of California, Irvine (Administrative Computing Services)
Next StepsNext StepsFocus on campus IT Consolidation and low hanging
projects rather than on Enterprise ArchitectureFocus 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 TOGAF9Get executive buy-in after campus consolidation settles
down and urgent projects are well under way