Foundation Study Guide Flashcards

1
Q

Activity

A

A task or collection of tasks that support the function of an organization; for example, a user entering data into an IT system or traveling to visit customers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Application

A

A deployed and operational IT system that supports business functions and services;

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Application Architectecture

A

A description of the major logical grouping of capabilities that manage the data objects necessary to process the data and support the business

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Architecture

A

Architecture has two meaning depending upon its contextual usage:

  1. A formal description of a system or a detailed plan of the system at component level to guide the implementation
  2. The structure of components, their inter-relationships and the principles and guidelines governing their design and evolution over time
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Architecture Continuum

A

A part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization. This Continuum begins with foundation definitions such as reference models, core strategies and basic building blocks. From there it spans to Industry Architectures and all the way to an organization’s specific architecture.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Architecture Building Block

A

A constituent of the architecture model that describes a single aspect of the overall model.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Architecture Development Method (ADM)

A

The core of TOGAF. A step-by-step aproach to develop and use an enterprise architecture.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Architecture Domain. Name the four domain.

A

The architectural area being considered. There are four architecture domains within TOGAF: Business, Data, Application, Technology (BDAT)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Architecture Framework

A

A foundation structure, or set of structures, which can be used for developing a broad range of different architectures. It should contain a method for designing an information system in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Architecture Principles

A

A qualitative statement of intent that should be met by the architecture. Has at least a supporting rationale and a measure of importance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Architecture Vision

A
  1. A high-level, aspirational view of the Target Architecture.
  2. a phase in the ADM which delivers understanding and definition of architectural vision.
  3. A specific deliverable describing the Architecture Vision.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Baseline

A

A specification that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development or change and that can be changed only through formal change control procedure or a type of procedure such as configuration management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Baseline Architecture

A

The existing defined system architecture before entering a cycle of architectural review and redesign.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Building Block

A

Represents a (potential re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Business Architecture

A

The business strategy, governance, organization, and key business processes information, as well as the interaction between these concepts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Business Governance

A

concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Capabilities

A

An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve;

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Concerns

A

The key interests that are crucially important to the stakeholders in a system and determine the acceptability of the system. Concerns may pertain to any aspect of teh systems functioning, development, or operation, including considerations such as performance, reliability, security, distribution and evolvability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Constraint

A

An external factor that prevents an organization from pursuing particular approaches to meet its goal;

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Data Architecture

A

The structure of an organization’s logical and physical data assets and data management resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Deliverable

A

An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.

22
Q

Enterprise

A

The highest level of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.

23
Q

Enterprise Continuum

A

A categorization mechanism useful for classifying architecture and solution artifacts, both internal and external to the Architecture Repositotry as they evolve from generic Foundation architectures to Organization-Specific Architecture

24
Q

Foundation Architecture

A

An architecture of generic services and functions that provide a foundation on which more specific architectures and architectural components can be built.

25
Q

Gap

A

A statement of difference between two states. Used in the context of gap analysis where the difference between the Baseline and Target Architecture is identified.

26
Q

Governance

A

The discipline of monitoring, managing, and steering a business to deliver the business outcome required.

27
Q

Information

A

any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic cartographic narrative or audio-visual

28
Q

Information Technology

A

The lifecycle of management of information and related technology used by an organization

29
Q

Logical (Architecture)

A

An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure;

30
Q

Metadata

A

Data about data, or any sort in any media, that describes the characteristics of an entity.

31
Q

Metamodel

A

A model that described how and with what the architecture will be described in a structured way.

32
Q

Method

A

A defined, repeatable approach to address a particular type of problem

33
Q

Methodology

A

a defined, repeatable series of steps to address a particular type of problem which typically centers on a defined process, but may also include definition of content.

34
Q

Model

A

A representation of a subject of interest. Provides a smaller scale, simplified and abstract representation of the subject matter.

35
Q

Modeling

A

A technique through construction of models which enables a subject to be represented in a form that enables reasoning, insight, and clarity concerning the essence of the subject matter.

36
Q

Objective

A

A time-bounded milestone for an organization use to demonstrate progress towards a goal

37
Q

Physical

A

A description of a real-world entity. Physical elements in an enterprise architecture may still be considerably abstracted from Solution Architecture, design, or implementation views.

38
Q

Reference Model

A

A reference model is an abstract framework for understanding significant relationships among the entities of environment and for the development of consistent standards or specifications supporting that environment. Based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non-specialist. A reference model is not directly tied to any standards, technologies, or other concrete implementation details, but it does seek to provide common semantics that can be used unambiguously across and between different implementations.

39
Q

Repository

A

A system that manages all of the data of an enterprise, including data and process models and other enterprise information. Hence, the data in a repository is much more extensive than that in a data dictionary, which generally defines only the data making up a database.

40
Q

Requirement

A

A quantitative statement of business need that must be met by a particular architecture or work package

41
Q

Segment Architecture

A

A detailed, formal description of areas within an enterprise, used at the program or portfolio level to organize and align change activity

42
Q

Solution Architecture

A

A description of a discrete and focused business operation or activity and how IS/IT supports that operation. A Solution Architecture typically applies to a single project or project release, assisting in the translation of requirement into a solution vision, high-level business and/or IT system specifications and a portfolio of implementation tasks.

43
Q

Solution Building Block

A

A Candidate physical solution for an Architecture Building Block (ABB). E.g. a Commercial Off-The-Shelf (COTS) package - that is component of the Acquirer view of the architecture.

44
Q

Solutions Continuum

A

A part of the Enterprise Continuum. A repository of re-usable solutions for future implementation efforts. It contains implementations of the corresponding definitions in the Architecture Continuum.

45
Q

Stakeholder

A

An individual, team, or organization with interests in or concerns relative to, the outcome of the architecture. Different stakeholders with different roles will have different concerns.

46
Q

Strategic Architecture

A

A summary formal description of the enterprise, providing an organizing framework for operational and change activity, and an executive-level, long-term view for direction setting.

47
Q

Target Architecture

A

The description of a future state of the architecture being developed for an organization. There may be several future states developed as a roadmap to show the evolution of the architecture to a target state.

48
Q

Technical Reference Model (TRM)

A

A structure which allows the components of an information system to be described in a consistent manner.

49
Q

Technology Architecture

A

The logical software and hardware capabilities that are required to support deployment of business, data and application services. This includes IT infrastructure, middleware, networks, communications, processing and standards.

50
Q

Transition Architecture

A

A formal description of the enterprise architecture showing periods of transition and development for particular parts of the enterprise. Used to provide an overview of current and target capability and allow for individual work packages and projects to be grouped into managed portfolios and programs

51
Q

View

A

The representation of a related set of concerns. An architecture view may be represented by a model to demonstrate to stakeholders their areas of interest in the architecture. A view does not have to be visual or graphical in nature.

52
Q

Viewpoint

A

A definition of the perspective from which a view is taken. It is a specification of the conventions for constructing and using a view (often by means of an appropriate schema or template). A view is what you see. a viewpoint is where you are looking from