0% found this document useful (0 votes)
67 views

Defintion 2

The document defines 33 terms related to enterprise architecture including definitions for abstraction, actor, application, application architecture, and application component. It provides definitions for architectural concepts and how they relate to the structure of an enterprise.

Uploaded by

Mohamed Zaki
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
67 views

Defintion 2

The document defines 33 terms related to enterprise architecture including definitions for abstraction, actor, application, application architecture, and application component. It provides definitions for architectural concepts and how they relate to the structure of an enterprise.

Uploaded by

Mohamed Zaki
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Definitions:

1. Abstraction: The technique of providing summarized or


generalized descriptions of detailed and complex content.

2. Actor: person, organization, or system that has one or more roles


that initiates or interacts with activities. Actors may be internal or
external to an organization.

3. Application: is a software program that runs on your computer.


Web browsers, e-mail programs, word processors, games, and
utilities are all applications.

4. Application Architecture: description of the structure and


interaction of the applications as groups of capabilities that
provide key business functions and manage the data assets.

5. Application Component: An encapsulation of application


functionality aligned to implementation structure, which is
modular and replaceable.

6. Application Platform: The collection of technology components of


hardware and software that provide the services used to support
applications.

7. Architectural Style: The combination of distinctive features


related to the specific context within which architecture is
performed or expressed.
 collection of principles and characteristics that steer or constrain
how an architecture is formed.

8. Architecture: The fundamental concepts or properties of a system


in its environment embodied in its elements, relationships.
 The structure of components, their inter-relationships, and the
principles and guidelines governing their design and evolution
over time.
9. Architecture Building Block (ABB): A constituent of the
architecture model that describes a single aspect of the overall
model.

10. Architecture Continuum: Apart of the Enterprise Continuum. A


repository of architectural elements with increasing detail and
specialization.

11. Architecture Development Method (ADM): The core of the


TOGAF framework. A multi-phase, iterative approach to develop and
use an Enterprise Architecture to shape and govern business
transformation and implementation projects.

12.Architecture Domain: The architectural area being considered.


The TOGAF framework has four primary architecture domains:
business, data, application, and technology.

13. Architecture Framework: conceptual structure used to plan,


develop, implement, govern, and sustain an architecture.

14. Architecture Governance: The practice of monitoring and


directing architecture-related work.
 The goal is to deliver desired outcomes and adhere to relevant
principles, standards, and roadmaps.

15. Architecture Landscape: The architectural representation of


assets in use, or planned, by the enterprise at particular points in
time.

16. Architecture Model: representation of a subject of interest.


 An architecture model provides a smaller scale, simplified, and/or
abstract representation of the subject matter.

17. Architecture Principle: qualitative statement of intent that


should be met by the architecture.
18. Architecture View: representation of a system from the
perspective of a related set of concerns.

19. Architecture Viewpoint: Aspecification of the conventions for a


particular kind of architecture view.

20. Architecture Vision: description of the Target Architecture that


describes its business value and the changes to the enterprise that
will result from its successful deployment.

21. Artifact: An architectural work product that describes an aspect


of the architecture.

22. Baseline: Aspecification that has been formally reviewed and


agreed upon.
 serves as the basis for further development or change and that
can be changed only through formal change control procedures.

23.Boundaryless Information Flow™: Shorthand representation of


"access to integrated information to support business process
improvements" representing a desired state of an enterprise’s
infrastructure specific to the business needs of the organization.

24. Building Block: component of enterprise capability that can be


combined with other building blocks to deliver architectures and
solutions.

25. Business Architecture: representation of holistic, multi-


dimensional business views of:
capabilities, end-to-end value delivery, information, and
organizational structure; and the relationships among these
business views and strategies, products, policies, initiatives, and
stakeholders.

26. Business Capability: particular ability that a business may


possess or exchange to achieve a specific purpose.
27. Business Function: Delivers business capabilities closely aligned
to an organization, but not necessarily explicitly governed by the
organization.

28. Business Governance: Concerned with ensuring that the


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

29. Business Model: Model describing the rationale for how an


enterprise creates, delivers, and captures value.

30. Business Service: Supports business capabilities through an


explicitly defined interface and is explicitly governed by an
organization.

31. Capability: An ability that an organization, person, or system


possesses.
 For example, Enterprise Architecture, marketing, customer
contact, or outbound telemarketing.

32. Capability Architecture: highly detailed description of the


architectural approach to realize a particular solution or solution
aspect.

33.operation management method: describes how company runs


its day-to-day operations, including IT.

You might also like