describe levels of activities/items that contribute to achieving an outcome. Outcome measures describe an intended future state.

One method for modeling business processes is known as the Integration Definition for Function (IDEF) technique.

Items that initiate/trigger the activity and are transformed, consumed, or become part.

Guide or regulate the activity; usually indicate when/ how a process will be performed.

The results produced by the activity; the reason for which the process was performed.

Systems, people, and equipment used to perform the activity.

another method for showing business processes that shows activities in horizontal rows

third method for showing business processes that includes events, decision-points, and sequenced flows of the activities

is a standard format document used by project managers, project sponsors, and the project team to improve the conceptualization, documentation, tracking, oversight, and execution of project work throughout the enterprise

is an analysis of the requirements and value of making a particular investment

are used by IT systems analysts and programmers to identify the “things” (data entities) that an enterprise wants IT systems to capture,

Multiple object behaviors invoked by triggering events.

Attributes that carry over between parent and child objects.

Hidden code that protects object attributes and behaviors.

are repositories for the data entities and attributes that an enterprise collects and stores in databases.

are repositories for reusable objects. From a technical perspective, it is the discrete pieces of programming code that actually make up an object, and that are being stored in the Object Library as a complete reusable unit.

are distinct collections of applications, databases, operating systems, and hardware that meet specific business or technology requirements of the enterprise

also called Node Connectivity Diagrams are physical and logical depictions of how and where these interfaces occur.

This is done so that an effective level of business support is maintained, and that an overall IT security solution is established for hosted applications, services, databases, and websites.

There should be a standard method for requesting changes to the EA artifacts

Hardware/Software Inventories one of the functions of the EA is to provide a repository for periodic inventories of the enterprise’s software and hardware assets.

Having future EA views is like having a full set of blueprints for the modification of an existing home or for building a new home

scenarios looking into the future have been used as a military planning tool for millennia.

can be added or deleted from the Strategic Plan’s future view in response to changes in the internal and external operating environment.

the future view of these EA artifacts represents changes to those goals, or new goals that are not yet formally adopted and published as part of the Plan.

serve to direct the development of future operating scenarios, which should capture the priorities and direction of those new goals.

is intended to show the changes that are being planned to existing initiatives as well as new initiatives that will be introduced in coming years

provide taxonomies and standard formats for the data entities that are used in the enterprise’s various IT systems

are similar in concept, except that they store both the formats/standards and the actual modules of code that constitute an object

are a feature of most commercial software programs and are where the designed interface points in the programming code are located.

this section documents the way that policy and decision-making will occur within the EA program. It is also where the underlying principles of the EA program are articulated.

is perhaps best described through a narrative that provides EA program policy

articulate the enterprise’s values as they relate to the EA.

this section documents the budget for the EA program by fiscal year and over the total lifecycle, so that the total cost of ownership (TCO) is identified

Measures This section documents how the effectiveness and efficiency of the EA program will be measured.

Provide resources. Assist in resolving high-level EA issues

Facilitate the establishment and ongoing operation of the EA Program

Manage the EA program and documentation proces

Promote the  identification of IT-related requirements and EA solutions for each LOB.

Collaboratively identify solutions for IT-related problems within  LOBs. Support documentation

Provide technical analysis and design support for database- related EA component selection and implementation

Identify end-user requirements for EA components. Provide feedback on the effectiveness of solutions

Document and verify LOB and end-user requirements. Assist in EA component design and documentation activities

provide data on activities and things, such as how many databases exist, how many e-mail are sent each day, or how closely an IT project is meeting baseline estimates for cost/schedule/performance.

often have both quantitative and qualitative elements to them, while output measures are usually quantitative in nature.

Summary of Current Architecture

This section identifies how the EA program and specific EA components support the attainment of the enterprise’s strategic goals and initiatives.

articulate the enterprise’s values as they relate to the EA

this section emphasizes that one of the main purposes of the EA program is to support and improve the enterprise’s strategic and business planning

this section documents the budget for the EA program by fiscal year and over the total lifecycle, so that the total cost of ownership (TCO) is identified.

This section documents how the effectiveness and efficiency of the EA program will be measured.

this section identifies and emphasizes the role that EA plays in supporting business process analysis and improvement, as well as identifying and optimizing information flows within and between these processes.

This section identifies how current EA components and artifacts at the Systems and applications level of the EA3 Cube Framework support the information flows that are required for LOBs throughout the enterprise

This section discusses the voice, data, and video EA components and artifacts that make up the Technology Infrastructure level of the EA3 Cube Framework

This section discusses the general approach to IT security at all levels of the EA framework.

This section describes the approach to IT workforce planning and training that the enterprise uses in human capital management.

in this section, the future operating scenarios are presented along with a narrative description of the purpose of the scenarios and the spectrum of operating environments that the scenarios respond to.

The planning assumptions from the scenarios are further discussed in terms of what they mean to the priorities of the enterprise as it implements the future EA

section of the EA Management Plan documents the tasks, milestones, and timeframe for implementing new EA components and artifacts.

section of the EA Management Plan serves to support the sub-process by which changes to the EA are managed and the standards in the TSRM are applied

terms is provided along with an Acronym List.

       The management and decision-making process associated with the planning, selection, control, and evaluation of investments in resources, including EA components such as systems, networks, knowledge warehouses, and support services for the enterprise.

process supports EA by planning, selecting, controlling, and evaluating investments in new or upgraded EA components. This cyclic process promotes the attainment of the following:

where a funding decision is made for a proposed investment in an EA component.

is where ongoing development and upgrade projects are evaluated for how closely cost, schedule, and EA component performance milestones are being met, and how well areas of risk are being managed.

is where (1) completed IT projects receive a Post-Implementation Review (PIR), and (2) where operational systems are periodically reviewed for continuing value.

is a professional discipline that focuses on developing, implementing, operating, improving, and/or retiring enterprise resources.

are responsible for meeting the goals of the project or program.

A temporary endeavor undertaken to create a unique product, service, or result.

An ongoing endeavor that manages existing processes/resources, or oversees the development of new processes/resources via projects.

In the area, should promote security and privacy-conscious designs, information content assurance, source authentication, and data access control.

In the area, the Security and Privacy Program should promote user authentication, security awareness, and training as follows

In the area, , the Security and Privacy Program should promote the development of SOPs for EA component security, risk assessment, testing and evaluation, remediation, certification, operation, and disposal.

should be captured in the EA include controls for the facilities that support IT processing, control of access to buildings, equipment, networks, and telecommunications rooms, as well as fire protection, media storage, and disaster recovery systems