Toward an Enterprise Architecture for Administrative Systems

1. Toward an Enterprise Architecture for Administrative Systems

2. CASE Strategic Plan Information Access � Data and information should be available to all stakeholders for reporting and decision making Infrastructure � Core components should provide infrastructure utilities, tools, and processes to deploy administrative systems

3. Case Phase II Implementation of technical infrastructure components including: Hardware infrastructure Middleware infrastructure Software infrastructure Development environment Imaging Historically these elements have grown somewhat organically in our environment

4. � An Enterprise Architecture? Workflow Identity, authentication, and authorization System and application integration Data storage and access User interfaces Development tools and methodologies Metadata models Middleware Business Process Engineering

5. Let�s Consider Some Physical Examples The type of architect needed to design a room:

6. � is different than the architect for a building�

7. �which is different than the architect needed to design an entire campus

8. Similarly� �Building a large complex, enterprise-wide information system without an enterprise architect is like trying to build a city without a city planner. Can you build a city without a city planner? Probably? But would you want to live in such a city�

9. Architecture Definition from ANSI/IEEE 1471-2000 �The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution�

10. Enterprise Architecture The phrase �enterprise architecture� was coined 20 years ago by J.A. Zachmann in an IBM Systems Journal article titled �A Framework for Information Systems Architecture�. Intended to address two problems: System complexity: Organizations were spending more and more money building IT Systems Poor business alignment: Organizations were finding it more and more difficult to keep increasingly expensive IT systems aligned with business needs The cost and complexity of IT Systems have exponentially increased while the chances of deriving real value from the systems has decreased

11. Possible Issues EA Can Address IT Systems that have become unmanageably complex and increasingly costly to maintain IT systems are hindering our ability to respond to current and future conditions in a timely manner Mission-critical information that is consistently out-of-date or wrong A culture of distrust between the business and technology sides of the organization

12. EA Benefits A more efficient IT operation Lower software development costs Increased portability and interoperability of applications and data Ability to address enterprise-wide issues like security Easier upgrade and exchange of system components Better return on existing investment and reduced risks for future investment Reduced complexity in IT Infrastructure Flexibility to buy, build, or out-source solutions Faster, simpler and cheaper procurement

13. EA Methodologies Four commonly used methodologies that account for 90% of architecture efforts Zachmann Framework for Enterprise Architectures The Open Group Architectural Framework (TOGAF) The Federal Enterprise Architecture Gartner Methodology

14. Federal Enterprise Architecture (FEA) �a common language and framework to describe and analyze IT investments, enhance collaboration�� Traces routes to late 1990�s legislation Clinger-Cohen Act of 1996 (Information Technology Management Reform Act) which mandates agencies take steps to improve effectiveness of their IT investments

15. FEA Now run from OMB As of 2004 only �20 of of 96 agencies examined� had established a foundation for effective architecture management More Info http://www.whitehouse.gov/omb/egov/a-1-fea.html

16. FEA Segments

17. FEA Segments Core Mission Area � unique service areas defining the mission or purpose of the agency FEA: Air transportation, pollution prevention UT: Career Placement, Research

18. FEA Segments Business Service � Common or shared business services supporting the core mission areas FEA: Auditing, human resource management, financial management UT: Human resource management, purchasing, financial management

19. FEA Segments Enterprise Service � Common or shared IT Services supporting commons mission areas and business services FEA: Knowledge Management, records management, BI, security UT: Security, identity management, BI

20. The Open Group Architectural Framework (TOGAF) Developed and maintained by The Open Group An Architecture Development Method which is a recipe for creating enterprise architecture

21. TOGAF Categories Business architecture � the processes the business uses to meet its goals Application architecture � how applications are designed and how they interact with each other Data architecture � how are enterprise data stores organized and accessed Technical architecture � the hardware and software infrastructure that support applications and their interactions

22. TOGAF Technical Reference Model

23. ITANA IT Architects in Academia Focused on higher ed but will draw on expertise and methodologies outside higher ed including TOGAF

24. Concerns of AITGC Technical components of enterprise architecture Application architecture Data architecture Technical architecture

25. Next Steps Evaluate EA methodologies Select best fit or hybrid Pursue methodology to crystallize Enterprise Architecture Scope

26. References Federal Enterprise Architecture: http://www.whitehouse.gov/omb/egov/a-1-fea.html The Open Group Architectural Framework: http://www.opengroup.org/togaf/ Enterprise Architecture Methdologies: http://msdn.microsoft.com/en-us/architecture/bb466232.aspx CIO Article: http://www.cio.com/article/129102/A_New_Blueprint_For_The_Enterprise/1