EA Terms & Definitions

[glossary-cats order=”desc” num=”20″]

EA Cube:
[glossary-terms order=”desc” num=”20″ tax=”ea-cube”]

Architecture Segment. A part of the overall EA that documents one or more lines of business, including all levels and threads.

Artifact.  An EA artifact is a documentation product, such as a text document, diagram, spreadsheet, briefing slides, or video clip.  EA artifacts document EA components.

Business Case. A collection of descriptive and analytic information about an investment in resource(s) and/or capabilities.

Capital Planning. 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.

Component. EA components are those plug-and-play resources that provide capabilities at each level of the framework. Examples include strategic goals and measures; business services; information flows and data objects; information systems, web services, and software applications; voice/data/video networks,and associated
cable plants.

Composite. An EA artifact that uses several documentation modeling techniques and/or represents several types of EA components.

Configuration Management. The process of managing updates to EA components and artifacts, ensuring that standards are being followed.

Crosscutting Component. An EA component that serves several lines of business.  Examples include email systems that serve the whole enterprise, and financial systems that serve several lines of business.

Culture. The beliefs, customs, values, structure, normative rules, and material traits of a social organization.  Culture is evident in many aspects of how an organization functions.

Current View. An EA artifact that represents an EA component or process that currently exists in the enterprise.

Data. Data items refer to an elementary description of things, events, activities, and transactions that are recorded, classified, and stored, but not organized to convey any specific meaning. Data items can be numeric, alphabetic, figures, sounds, or images.  A database consists of stored data items organized for retrieval.

Enterprise. An area of common activity and goals within an organization or between several organizations, where information and other resources are exchanged.

Enterprise Architecture. The analysis and documentation of an enterprise in its current and future states from an integrated strategy, business, and technology perspective.

Framework. A structure for organizing information that defines the scope of the architecture (what the EA program will document) and how the areas of the architecture relate to each other.

Future View. An EA artifact that represents an EA component or process that does not yet exist in the enterprise.

Governance. A group of policies, decision-making procedures, and management processes that work together to enable the effective planning and oversight of activities and resources.

Horizontal Component. A horizontal (or crosscutting) component is a changeable goal, process, program, or resource that serves several lines of business.  Examples include email and administrative support systems that serve the whole enterprise.

Information. Information is data that have been organized so that they have meaning and value to the recipient.  The recipient interprets the meaning and draws conclusions and implications.

Line of Business. A distinct area of activity within the enterprise.  It may involve the manufacture of certain products, the provision of services, or internal administrative functions.

Methodology. The EA methodology defines how EA documentation will be developed, archived, and used; including the selection of a framework, modeling tools, and on-line repository.

Program. A group of related projects managed in a coordinated way. Programs usually involve an element of ongoing activity.

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

Primitive. An EA artifact that uses one modeling technique to describe an EA component.

System. A type of EA component that is comprised of hardware, and software, and activities that has inputs and outputs.

Vertical Component. An EA component that is contained within one line of business.  Examples include a system, application, database, network, or website that serves one line of business.