Course Overview Chapter 12 describes the role of an on-line EA repository and support tools in the EA program and the documentation of EA components. The design and structure of an EA repository is discussed, and the relationship to an underlying EA documentation framework. The example of the EA³ Cube Framework and the Living Enterprise™ repository design is used in this discussion. Additionally, different types of EA documentation and support tools are discussed in the context of developing EA component documentation and populating the on-line EA repository. Course Objective • Understand the role of an on-line EA repository in the EA program. • Understand how the EA repository supports documentation of EA components. • Understand how the design of the EA repository relates to an EA framework. • Understand the role of EA support tools in documenting EA components. Course Contents • Introduction • Relating the EA Framework and Repository • EA Repository • Strategic Goals and Initiatives Column • Business Products and Services Column • Data and Information Column • Systems and Applications Column • Networks and Infrastructure Column • Security Solution Column • Tabular Information • EA Support Tools Introduction … (1) • The EA repository is intended to provide a single place for the storage and retrieval of EA artifacts that are created using EA software applications (tools). • A repository works best if it is easy to access and use (web-based EA repository is recommended) • This type of web “portal” for EA should be located on the enterprise’s internal Local Area Network to promote security of the information while still supporting access by executives, managers, and support staff Relating the EA Framework and Repository …(1) Relating the EA …(2) • The approach to the design of the example EA repository (and the underlying EA³ Cube Framework) provided in previous figure is based on the work of John Zachman • It is a very intuitive schema for visually organizing EA information. • He did this by using hierarchical rows and functional columns to create cells that contain “primitive” EA artifacts which answer basic questions about information systems (who, what, why, where, when, and how) EA Repository …(1) • It is based on a separate meta-framework (the EA³ Framework) • It uses three hierarchical levels • The functional columns are not based on basic interrogative questions • The cells of the matrix are changeable and are often populated with EA documentation that represents composite views of several types of primitive products • It has areas for additional information on the EA program • It is designed to be implemented as a website and therefore has navigation and version control features. • This EA repository is linked to EA software tools and a database to store EA data and artifacts. EA Repository …(2) • Example EA Repository Design – Living Enterprise Strategic Goals and Initiatives Column • Mission and Vision Cell • Goals and Initiatives Cell • Performance Measures Cell Business Products and Services Column • Lines of Business Cell • Investment Portfolio Cell • IT Projects Cell Data and Information Column
• Knowledge Management Cell
• Data Flows Cell • Data Dictionary Cell Systems and Applications Column
• Support Services Cell
• Front Office Systems Cell • Back Office Systems Cell Networks and Infrastructure Column • Common Operating Environment Cell • Wide Area Network Cell • Local Area Network Cell Security Solution Column
• Policy and Procedures Cell
• Data Privacy Cell • Data Privacy Cell Tabular Information
• EA Management Plan Tab
• Future EA Summary Tab • EA Standards Tab • EA Program Tab • EA Tutorial Tab • EA Site Map EA Support Tools
• Various types of commercial software applications (tools) are
required to support EA documentation and analysis activities • At present, no one commercial tool can do all of the things that are needed in the EA program • Because no one EA tool can do all that is required in the EA program, a “set” of tools is required (ex : modeling tool, a graphics tool, a word processing tool, a website development tool, a configuration management tool ) • And any application development and programming tools that the enterprise needs to create or modify EA components EA Tools …(1) EA Tools …(2)
• The Relationship and Purpose of EA Documentation Tools
EA Framework Modeling Tools • These software tools are designed to use various EA frameworks that are pre-loaded and support various methodologies to develop EA artifacts throughout the chosen framework • These tools also support the conversion of EA artifacts into HTML and XML formats for increased utilization with websites and other tools EA Repository Web-Application
• Provides a user-friendly graphical front end to support
easy access to, and navigation of EA Artifacts in a way that relates to the chosen EA framework • Provides interfaces with a back-end database that stores the EA artifacts • The database might be integral to the EA repository web application, or might be a separate database software application (e.g., when more robust storageis required). Web Service Development Tools
• These software tools provide the capability to create a
web-based EA repository that links to other web services and web sites. • The development of a web-based EA repository is essential to providing easy access to the entire enterprise via a protected Intranet web site. • Many EA modelling tools have web-based front ends (application interfaces) and can create EAartifacts in HTML. • This allows the EA modeling tool to be directly accessed through the EA repository website. General Graphics Tools
• These software tools support general graphics design
requirements and the custom creation of management views of EA artifacts. • The development of briefings, HMTL pages, enterprise charts, and simple flowcharts are examples of these types of products. Strategy Modeling Tools • These software tools support the development and modeling of EA components at the Strategic Initiatives level of the EA³ Cube Framework. • The resulting EA artifacts include the enterprise’s strategic goals, supporting initiatives (programs and projects), and performance measures for the outputs and outcomes of each initiative • The Balanced Scorecard methodology is a popular pproach to developing these EA Artifacts and several commercial tools support this methodology, including overall EA Framework modeling tools and specific strategic planning tools Business Modeling Tools • These software tools support the development and modeling of EA components and the Business services level of the EA³ Cube Framework. • The resulting EA artifacts include the processes and supply chains in each of the enterprise’s LOBs. Business Process Reengineering (BPR) and Business Process Improvement (BPI) activities can also be documented Information Modeling Tools • These software tools support the development and modeling of EA components at the Information Level of the EA³ Cube Framework. • The resulting EA artifacts include the logical and physical design for knowledge warehouses, data marts, databases, web sites, web portals, and data mining products. • Also documented is the structure and processing of basic data elements using traditional or object-oriented modeling tools, along with the data dictionaries and object libraries that store these products. Application Modeling Tools
• These software tools support the development and
modeling of applications that support general operational and administrative processes and office automation capabilities throughout the enterprise that are not specific to a LOB • This includes financial systems, personnel and pay systems , e-mail, and applications that support collaboration, word processing, graphics, and spreadsheets • The resulting EA artifacts include the specifications for application capabilities, interfaces, standards, license inventories, and required support platforms Network Modeling Tools
• These software tools support the development and
modeling of the enterprise’s internal and external voice, data and video networks, as well as associated backbone cable plants, network operations centers, server rooms, and wiring closets • The resulting EA artifacts include the logical and physical design of the networks, performance specifications, interface points, standards, and inventories Security Analysis and Modeling Tools • These software tools support the development and modeling of security processes, considerations, and capabilities at all levels of the EA³ Cube Framework • The resulting EA artifacts held to develop and model physical security, operational security, personnel security, and information security requirements and solutions as they relate to business services, information flows, support applications, and network infrastructures Linked Software Applications
• These software applications support other IT governance
processes that integrate with the EA program • This includes capital planning, program management, and workforce planning • Being able to easily assess and relate information in these other areas of governance is essential to using EA documentation to improve communication and decision- making regarding the use of EA components in improving mission and/or Line of Business Performance EA Tool Evaluation Matrix Summary • This chapter provided a discussion of the role of an EA repository and documentation tools in the EA program • The importance of developing a web-based EA repository was stressed in that it provides easy access to EA artifacts which can assist planning and decision-making throughout the enterprise • The various types of EA-related software tools were discussed as was the idea that a set of tools are needed to support the overall EA management program and documentation process • EA tool selection criteria were also provided. Question & Answers