当前位置:文档之家› 企业架构框架TOGAF 术语官方中文版本

企业架构框架TOGAF 术语官方中文版本

企业架构框架TOGAF 术语官方中文版本
企业架构框架TOGAF 术语官方中文版本

Open Group Standard

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese

Copyright ? 2012, The Open Group

The Open Group hereby authorizes you to use this document for any purpose, PROVIDED THAT any copy of this document, or any part thereof, which you make shall retain all copyright and other proprietary notices contained herein. This document may contain other proprietary notices and copyright information.

Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise any license or right under any patent or trademark of The Open Group or any third party. Except as expressly provided above, nothing contained herein shall be construed as conferring any license or right under any copyright of The Open Group.

Note that any product, process, or technology in this document may be the subject of other intellectual property rights reserved by The Open Group, and may not be licensed hereunder.

This document is provided "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you.

Any publication of The Open Group may include technical inaccuracies or typographical errors. Changes may be periodically made to these publications; these changes will be incorporated in new editions of these publications. The Open Group may make improvements and/or changes in the products and/or the programs described in these publications at any time without notice.

Should any viewer of this document respond with information including feedback data, such as questions, comments, suggestions, or the like regarding the content of this document, such information shall be deemed to be non-confidential and The Open Group shall have no obligation of any kind with respect to such information and shall be free to reproduce, use, disclose, and distribute the information to others without limitation. Further, The Open Group shall be free to use any ideas, concepts, know-how, or techniques contained in such information for any purpose whatsoever including but not limited to developing, manufacturing, and marketing products incorporating such information.

If you did not obtain this copy through The Open Group, it may not be the latest version. For your convenience, the latest version of this publication may be downloaded at https://www.doczj.com/doc/b14774719.html,/bookstore.

In the event of any discrepancy between this Translation Glossary and the official TOGAF 9 documentation, the TOGAF 9 documentation remains the authoritative version for certification, testing by examination and other purposes. The official TOGAF 9 documentation can be obtained online from https://www.doczj.com/doc/b14774719.html,/togaf.

Technical Standard

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese

ISBN: TBA

Document Number: TBA

Published by The Open Group, 2012.

Comments relating to the material contained in this document may be submitted to:

The Open Group, Apex Plaza, Forbury Road, Reading, Berkshire, RG1 1AX, United Kingdom

or by electronic mail to:

ogspecs@https://www.doczj.com/doc/b14774719.html,

ii Technical Standard (2012)

Contents

1Introduction (1)

1.1Objective (1)

1.2Overview (1)

1.3Future Directions (1)

2Glossary (2)

2.1Definitions (2)

2.2Supplementary Definitions (16)

A Extended Glossary (Informative) (30)

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese iii

Preface

The Open Group

The Open Group is a global consortium that enables the achievement of business objectives

through IT standards. With more than 400 member organizations, The Open Group has a diverse

membership that spans all sectors of the IT community – customers, systems and solutions

suppliers, tool vendors, integrators, and consultants, as well as academics and researchers – to:

?Capture, understand, and address current and emerging requirements, and establish policies and share best practices

?Facilitate interoperability, develop consensus, and evolve and integrate specifications and open source technologies

?Offer a comprehensive set of services to enhance the operational efficiency of consortia

?Operate the industry’s premier certification service

Further information on The Open Group is available at https://www.doczj.com/doc/b14774719.html,.

The Open Group publishes a wide range of technical documentation, most of which is focused

on development of Open Group Standards and Guides, but which also includes white papers,

technical studies, certification and testing documentation, and business titles. Full details and a

catalog are available at https://www.doczj.com/doc/b14774719.html,/bookstore.

Readers should note that updates – in the form of Corrigenda – may apply to any publication.

This information is published at https://www.doczj.com/doc/b14774719.html,/corrigenda.

This Document

This document is the Technical Standard for the TOGAF 9.1 Translation Glossary: English –

Simplified Chinese. It has been developed and approved by The Open Group.

iv Technical Standard (2012)

Trademarks

ArchiMate?, Jericho Forum?, Making Standards Work?, The Open Group?, TOGAF?, UNIX?,

and the “X”? device are registered trademarks and Boundaryless Information Flow?,

DirecNet?, FACE?, and The Open Group Certification Mark? are trademarks of The Open

Group in the United States and other countries.

All other brands, company, and product names are used for identification purposes only and may

be trademarks that are the sole property of their respective owners.

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese v

Referenced Documents

The following documents are referenced in this Technical Standard:

?TOGAF Version 9.1 (English version), available online at

https://www.doczj.com/doc/b14774719.html,/architecture/togaf9-doc/arch, and also available as TOGAF

Version 9.1 “The Book” (ISBN: 978 90 8753 6794, G116) at

https://www.doczj.com/doc/b14774719.html,/bookstore/catalog/g116.htm

vi Technical Standard (2012)

1 Introduction

1.1 Objective

The objective of this Translation Glossary is to establish a common and unambiguous

vocabulary for translation work related to TOGAF 9.1 material.

1.2 Overview

This document is the English to Simplified Chinese Translation Glossary for TOGAF 9.1. The

scope of this document is translation of terms in the TOGAF 9.1 specification.

This document is structured as follows:

?Chapter 1 is an introduction.

?Chapter 2 defines the Translation Glossary containing translations and explanations

corresponding to Chapter 3 and Appendix A of the TOGAF 9.1 specification.

?Appendix A (Informative) contains an Extended Glossary containing translations and

explanations of concepts from other sections of TOGAF 9.1.

Directions

1.3 Future

It is anticipated that in future this document may expand to cover additional TOGAF 9.1

documentation beyond the specification.

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 1

2 Glossary

2.1 Definitions

This section contains the list of terms and definitions corresponding to TOGAF 9.1, Chapter 3,

Definitions together with translated explanations.

English Chinese TOGAF 9.1 Reference

Abstraction

The technique of providing summarized or generalized descriptions of detailed and complex content. Abstraction, as in level of abstraction, can also mean providing a focus for analysis that is concerned with a consistent and common level of detail or abstraction. Abstraction in this sense is typically used in architecture to allow a consistent level of definition and understanding to be achieved in each area of the architecture in order to support effective communication and decision-making. It is especially useful when dealing with large and complex architectures as it allows relevant issues to be identified before further detail is attempted. 抽象

对详细而又复杂的内容进行总结性或概

括性描述的技术。

“抽象层次”中的抽象也意味着,为了能进

行一致且一般性细致或抽象程度上的分

析,而提供分析的焦点。从这个意义上

说,抽象通常用在架构中,以确保在架

构的各个领域中都能达成一致的定义和

理解,从而支持有效的沟通和决策。它

在处理大型且复杂架构时尤其有用,因

为它允许在尝试进一步地展开细节前,

先识别出相关的问题。

§3.1 Abstraction

Actor

A person, organization, or system that has a role that initiates or interacts with activities. 施动者

以某种角色发起活动或与活动进行交互

的个人、组织或系统,如出差拜访客户

的销售代表。施动者可以处于组织内部

或外部。在汽车行业中,汽车经销商认

为,原始设备制造商(original equipment manufacturer,OEM)是与其供应链活动

进行交互的某种施动者。

§3.2 Actor

2 Technical Standard (2012)

Application

An application is a deployed and operational IT system that supports business functions and services. Applications use data and are supported by multiple technology components but are distinct from the technology components that support the application. 应用

一种支持各种业务功能和服务的已部署

且运行的IT系统,如薪资管理系统。应

用使用数据,由多个技术构件所支持,

但与对其进行支持的技术构件之间有着

明显的区别。

§3.3 Application

Application Architecture

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets. 应用架构

对应用之间结构和交互的描述,这些应

用作为多组能力提供关键业务功能和管

理数据资产。

§3.4 Application

Architecture

Application Platform

The collection of technology components of hardware and software that provide the services used to support applications. 应用平台

硬件和软件的技术构件集合,它提供支

持应用的各种服务。

§3.5 Application Platform

Application Platform Interface (API) The interface, or set of functions, between application software and/or the application platform. 应用平台接口

应用软件和/或应用平台之间的接口或功

能集。

§3.6 Application Platform

Interface (API)

Architectural Style

The combination of distinctive features in which architecture is performed or expressed. 架构风格

表现或表示架构独特特征的集合。

§3.7 Architectural Style

Architecture

1. A formal description of a system, or

a detailed plan of the system at component level to guide its implementation.

2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. 架构

1、对系统的正式描述或在构件级对系统

的详细规划,旨在引导系统实施。

2、构件结构、构件间相互关系、以及随

时间演进对构件设计与演进加以治理的

原则和指引。

§3.8 Architecture

Architecture Building Block (ABB)

A constituent of the architecture model that describes a single aspect of the overall model. 架构构建块

架构模型的一种组成要素,它描述整个

模型的一个方面。

§3.9 Architecture Building

Block (ABB)

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 3

Architecture Continuum

A part of the Enterprise Continuum. A repository of architectural elements with increasing detail and specialization. This Continuum begins with foundational definitions like 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. 架构连续系列

架构连续系列是企业连续系列的一部分

。它是架构元素的存储库,细节和专业

化分工程度可不断增长。架构连续系列

从一些基础定义开始,如参考模型、核

心战略和基本构建块等。在此基础上,

架构连续系列逐步扩展到行业架构,并

最终扩展成为某个组织的特定架构。

§3.10 Architecture

Continuum

Architecture Development Method (ADM)

The core of TOGAF. A step-by-step approach to develop and use an enterprise architecture. 架构开发方法

架构开发方法(ADM)是TOGAF的核

心。它是开发和使用企业架构的一种循

序渐进式方法。

§3.11 Architecture

Development Method

(ADM)

Architecture Domain

The architectural area being considered. There are four architecture domains within TOGAF: business, data, application, and technology. 架构领域

架构设计中需要考虑的架构区域。

TOGAF包括业务架构、数据架构、应用

架构和技术架构四个架构领域。

§3.12 Architecture Domain

Architecture Framework

A conceptual structure used to develop, implement, and sustain an architecture. 架构框架

用于开发、实施和支撑架构的概念结构

§3.13 Architecture

Framework

Architecture Governance

The practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It is concerned with change processes (design governance) and operation of product systems (operational governance). 架构治理

在企业范围级别管理和控制企业架构和

其他架构的实践与定位。架构治理关注

流程变更(设计治理)和生产系统运营

(运营治理)。

§3.14 Architecture

Governance

Architecture Landscape

The architectural representation of assets in use, or planned, by the enterprise at particular points in time. 架构景观

企业在特定时点使用或规划的各类资产

的架构呈现。

§3.15 Architecture

Landscape

Architecture Principle

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

对架构应满足目的的定性陈述。一个架

构原则至少具备一个支撑依据和一项重

要测度。

§3.16 Architecture

Principles

4 Technical Standard (2012)

Architecture Vision

A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development. 架构愿景

对目标架构的简洁描述。架构愿景描述

了目标架构的业务价值以及因其成功部

署所导致企业发生的各种变化。它是详

细架构开发的期望愿景和边界。

§3.17 Architecture Vision

Artifact

An architectural work product that describes an aspect of the architecture. 制品

一种描述架构某个方面的架构工作产品

§3.18 Artifact

Baseline

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 procedures or a type of procedure such as configuration management. 基线

已经过正式评审并获得一致认可的规范

。基线确立后,将作为进一步开发或变

更的基础。并且,如果要变更基线,只

能够通过正式的变更控制流程或诸如配

置管理这样的流程才能进行。

§3.19 Baseline

Boundaryless Information Flow?

1. A trademark of The Open Group.

2. A 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. An infrastructure that provides Boundaryless Information Flow has open standard components that provide services in a customer's extended enterprise that combine multiple sources of information, securely deliver the information whenever and wherever it is needed, in the right context for the people or systems using that information. 无边界信息流

1、无边界信息流(Boundaryless

Information Flow)是The Open Group的

商标。

2、无边界信息流是对“访问集成信息以

支持业务流程改进”的简短表述。它代表

满足组织业务需要的特定企业基础设施

的期望状态。

提供无边界信息流的基础设施采用开放

的标准构件,这些构件为客户扩展型企

业提供各种服务。客户扩展型企业能够

?整合多种信息来源。

?在合适的时间和地点安全地传递信息

§3.20 Boundaryless

Information Flow

Building Block

1. Component of the architecture.

2. Package of functionality.

3. A Building Block represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building block to deliver solutions. 构建块

架构构件。

功能包。

3、构建块代表业务能力、IT能力或架构

能力的一种(也许可重用的)构件。该

构件能够与其他构建块进行结合,形成

架构和解决方案。

§3.21 Building Block

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 5

Business Architecture

A description of the structure and interaction between the business strategy, organization, functions, business processes, and information needs. 业务架构

对业务战略、组织、功能、业务流程与

信息需要之间结构和交互的描述。

§3.22 Business

Architecture

Business Function

Delivers business capabilities closely aligned to an organization, but not necessarily explicitly governed by the organization. 业务功能

业务功能交付与某个组织紧密结合的业

务能力,但这些能力并非必须受该组织

直接治理。

§3.23 Business Function

Business Governance Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation. 业务治理

业务治理致力于确保业务流程和策略

(及其运作)能够交付业务成果并符合

相关业务规程。

§3.24 Business

Governance

Business Service

Supports business capabilities through an explicitly defined interface and is explicitly governed by an organization. 业务服务

业务服务通过定义的显式接口支持各种

业务能力,并明确地接受组织治理。

§3.25 Business Service

Capability

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. 能力

组织、个人或系统具有的才能或能力。

能力通常以高度概括的语言表示,并且

通常需要综合组织、人员、流程和技术

等几方面的因素才能获得。例如,市场

营销、客户联络或推式电话营销等。

§3.26 Capability

Capability Architecture

A highly detailed description of the architectural approach to realize a particular solution or solution aspect. 能力架构

对实现特定解决方案或解决方案某个方

面的架构途径的详细描述。

§3.27 Capability

Architecture

Capability Increment

A discrete portion of a capability architecture that delivers specific value. When all increments have been completed, the capability has been realized. 能力增量

能力架构的一个离散部分,提供特定价

值。当所有能力增量完成时,就实现了

这种能力。

§3.28 Capability Increment

6 Technical Standard (2012)

Communications and Stakeholder Management

The management of needs of stakeholders of the enterprise architecture practice. It also manages the execution of communication between the practice and the stakeholders and the practice and the consumers of its services. 沟通和利益相关者管理

对企业架构实践中利益相关者需求的管

理,也包括对企业架构实践与利益相关

者之间以及与其服务消费者之间的沟通

执行进行管理。

§3.29 Communications and

Stakeholder Management

Concerns

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 the system’s functioning, development, or operation, including considerations such as performance, reliability, security, distribution, and evolvability. 关注

利益相关者对某个系统的主要兴趣点,

这些兴趣点决定该系统的可接受性。关

注可以与系统功能、开发或运营的任何

方面相关,包括对性能、可靠性、安全

性、分布和可演进性等方面的考虑。

§3.30 Concerns

Constraint

An external factor that prevents an organization from pursuing particular approaches to meet its goals. 约束

阻碍组织寻求特定方法实现其目标的外

部因素。例如,由于组织内部各地区或

全国范围内的客户数据不一致,限制了

组织提供有效客户服务的能力。

§3.31 Constraint

Data Architecture

The structure of an organization’s logical and physical data assets and data management resources. 数据架构

对企业主要数据类型与来源、逻辑数据

资产、物理数据资产以及数据管理资源

的结构和交互的描述。

§3.32 Data Architecture

Deliverable

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. 交付物

由合同规定,并依次经过利益相关者正

式评审、认可及签核的架构工作产品。

交付物代表项目产出,并且以文档形式

存在的交付物通常会在项目结束时加以

归档或作为参考模型、标准以及某个时

点架构景观的快照存入架构存储库。

§3.33 Deliverable

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 7

Enterprise

1. The highest level (typically) of description of an organization and typically covers all missions and functions. Enterprise will often span multiple organizations.

2. Any collection of organizations that has a common set of goals and/or a single bottom line. 企业

1、通常指对组织的最高级描述,涵盖了

组织的所有使命和智能。一个企业往往

包括多个组织。

2、任何具有共同目标和/或单一底线的组

织的集合。

§3.34 Enterprise

Enterprise Continuum

A categorization mechanism useful for classifying architecture and solution artifacts, both internal and external to the Architecture Repository, as they evolve from generic Foundation Architectures to Organization-Specific Architectures. 企业连续系列

架构制品和解决方案制品的一种分类机

制。在架构制品和解决方案制品从通用

基础架构向组织特定架构演进时,该机

制有助于将这些内外部制品分类存储到

架构存储库之中。

§3.35 Enterprise

Continuum

Foundation Architecture

Generic building blocks, their inter-relationships with other building blocks, combined with the principles and guidelines that provide a foundation on which more specific architectures can be built. 基础架构

基础架构由通用构建块、通用构建块与

其他构建块的相互关系以及有关的原则

和指引构成,它为在其之上构建更具体

的架构提供了基础。

§3.36 Foundation

Architecture

Framework

A structure for content or process that can be used as a tool to structure thinking, assuring consistency and completeness. 框架

内容或流程的结构。可以以框架为工具

将构想结构化,从而确保一致性和完整

性。

§3.37 Framework

Gap

A statement of difference between two states. Used in the context of Gap Analysis where the difference between the as-is and to-be architecture is identified. 差距

对两种状态之间差异的陈述。在差距分

析中,差距用于识别基线架构和目标架

构之间的差异。

§3.38 Gap

Governance

Process of monitoring, managing, and steering a business (or IS/IT landscape) to deliver the business outcome required. 治理

监控、管理和把控业务(或IS/IT景观)

以交付所需业务成果的学科。

§3.39 Governance

8 Technical Standard (2012)

Information

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

利用包括文本、数字、图形、(插画)

地图、叙述或视听形式在内的任意介质

或形式传达或表现的各种事实、数据或

观念。

§3.40 Information

Information Technology (IT)

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

2. An umbrella term that includes all or some of the subject areas relating to the computer industry, such as Business Continuity, Business IT Interface, Business Process Modeling and Management, Communication, Compliance and Legislation, Computers, Content Management, Hardware, Information Management, Internet, Off-shoring, Networking, Programming and Software, Professional Issues, Project Management, Security, Standards, Storage, Voice, and Data Communications. Various countries and industries employ other umbrella terms to describe this same collection.

3. A term commonly assigned to a department within an organization tasked with provisioning some or all of the domains described in (2) above.

4. Alternates names commonly adopted include Information Services, Information Management, et al. 信息技术

1、对组织所使用信息和相关技术的生命

周期管理。

2、对与计算机行业相关的部分或全部主

题领域的一种总称,如业务连续性、业

务-IT接口、业务流程建模与管理、通

信、合规性与立法、计算机、内容管

理、硬件、信息管理、互联网、离岸外

包、网络化、编程与软件、专业课题、

项目管理、安全、标准、存储、语音与

数据通信等。不同国家和行业描述同一

技术集合的术语总称有所不同。

3、特定组织部门的常用称谓,该部门的

任务是提供上述(2)中描述的部分或全

部领域的技术。

4、信息服务、信息管理等的常用别称。

§3.41 Information

Technology (IT)

Interoperability

1. The ability to share information and services.

2. The ability of two or more systems or components to exchange and use information.

3. The ability of systems to provide and receive services from other systems and to use the services so interchanged to enable them to operate effectively together. 互操作性

1、共享信息和服务的能力

2、两个或多个系统或构件交换和使用信

息的能力

3、系统提供服务、接收其他系统的服务

,以及使用互换服务促进彼此有效协同

运作的能力。

§3.42 Interoperability

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 9

Logical

An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure. For example, the products from multiple infrastructure software vendors can all be logically grouped as Java application server platforms. 逻辑的

一种与实施无关的架构定义方式,通常

按照相关物理实体的用途和结构对其进

行分组。例如,逻辑上,多个基础设施

软件厂商的产品都可以归类为Java应用

服务器平台。

§3.43 Logical

Metadata

Data about data – of any sort in any media – that describes the characteristics of an entity. 元数据

任意介质中存在的任意类型的“数据的数

据”。元数据描述任意实体的特征。

§3.44 Metadata

Metamodel

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

一种说明如何和使用什么元素以结构化

方式描述架构的模型。

§3.45 Metamodel

Method

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

解决特定类型问题的一种明确定义的可

重复途径。

§3.46 Method

Methodology

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. 方法论

解决特定类型问题的一系列明确定义的

可重复步骤。方法论通常以某个明确定

义的流程为中心,但也可以包括对内容

的定义。

§3.47 Methodology

Model

A representation of a subject of interest.

A model provides a smaller scale, simplified, and/or abstract representation of the subject matter. A model is constructed as a “means to an end”. In the context of enterprise architecture, the subject matter is a whole or part of the enterprise and the end is the ability to construct “views” that address the concerns of particular stakeholders; i.e., their “viewpoints” in relation to the subject matter. 模型

对所关注主题的一种表现方式。模型以

较小的规模、简化和/或抽象的方式呈现

了主题,它被构造为一种“达到目的的手

段”。在企业架构中,主题是整个或部分

企业,而目的则是构造能满足特定利益

相关者关注的“视图”的能力,即构造与主

题相关的“视点”的能力。

§3.48 Model

10 Technical Standard (2012)

Modeling

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. 建模

一种模型构造技术,它允许通过以对主

题本质进行推理、洞察和澄清的形式表

现主题。

§3.49 Modeling

Objective

A time-bound milestone for an organization used to demonstrate progress towards a goal; for example, “Increase Capacity Utilization by 30% by the end of 2009 to support the planned increase in market share”. 目的

组织的一个有时限的里程碑,用于展示

朝着目标的进展。例如,“2009年底前将

产能利用率提高30%,支撑市场份额按

计划增长。”

§3.50 Objective

Pattern

A technique for putting building blocks into context; for example, to describe a re-usable solution to a problem. Building blocks are what you use: patterns can tell you how you use them, when, why, and what trade-offs you have to make in doing so.

Patterns are considered to be a way of putting building blocks into context. 样式

一种将构建块置入情境的技术,如为了

描述某个问题可重用的解决方案。构建

块回答“用什么”,而样式则回答“怎样、

何时、为什么使用它们,以及在使用中

必须做出何种权衡。”

§3.51 Patterns

Performance Management

The monitoring, control, and reporting of the enterprise architecture practice performance. Also concerned with continuous improvement. 绩效管理

对企业架构实践绩效的监控、控制和报

告,同时也关注持续改进。

§3.52 Performance

Management

Physical

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. 物理的

对真实实体的描述。企业架构中的物理

元素在很大程度上仍然可以从解决方案

架构、设计或实现视图中抽象出来。

§3.53 Physical

Platform

A combination of technology infrastructure products and components that provides that pre-requisites to host application software. 平台

一种技术基础设施产品与构件的组合形

态,平台为部署应用软件提供了先决条

件。

§3.54 Platform

Platform Service

A technical capability required to provide enabling infrastructure that supports the delivery of applications. 平台服务

为了提供能够支持应用交付的基础设施

必需的一种技术能力。

§3.55 Platform Services

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 11

Principle

See Architecture Principle. 原则

见“架构原则”。

§3.56 Principle

Reference Model (RM)

A reference model is an abstract framework for understanding significant relationships among the entities of [an] environment, and for the development of consistent standards or specifications supporting that environment. A reference model is 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. 参考模型

参考模型是一种抽象框架,旨在帮助理

解环境中实体之间的重要关系和开发支

持该环境的一致标准或规范。参考模型

以少量统一概念为基础,可以以此为基

础对非专业人员进行教育和标准解释。

虽然参考模型并不直接绑定任何标准、

技术或其他具体实现细节,但它试图提

供可毫无歧义地跨不同实现以及在不同

实现之间使用的通用语义学。

§3.57 Reference Model

(RM)

Repository

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. 存储库

一种管理企业所有数据的系统,包括数

据、流程模型和其他企业信息。因此,

存储库中的数据比数据字典中的数据更

加广泛。数据词典一般仅定义构成数据

库的数据。

§3.58 Repository

Requirement

A statement of need that must be met by a particular architecture or work package. 需求

对必须通过特定架构或工作包满足的需

要的陈述。

§3.59 Requirement

Roadmap

An abstracted plan for business or technology change, typically operating across multiple disciplines over multiple years. Normally used in the phrases Technology Roadmap, Architecture Roadmap, etc. 路线图

业务变革或技术变革的抽象式进度表,

通常跨多个历时数年才能完成的学科。

§3.60 Roadmap

Role

The usual or expected function of an Actor, or the part somebody or something plays in a particular action or event. An Actor may have a number of roles. 角色

施动者具有的通常或预期功能,或某个

人或事物在特定行动或事件中扮演的角

色。一个施动者可以具有多种角色。

§3.61 Role

12 Technical Standard (2012)

Segment Architecture

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

对企业内各区域的正式详细描述。分段

架构在项目群或项目组合层面使用,旨

在对变更活动进行组织和对齐。

§3.62 Segment

Architecture

Service Orientation

An architectural style that supports service orientation. It has the following distinctive features:

?It is based on the design of the

services – which mirror real-world

business activities – comprising the

enterprise (or inter-enterprise)

business processes.

?Service representation utilizes

business descriptions to provide

context (i.e., business process,

goal, rule, policy, service interface,

and service component) and

implements services using service

orchestration.

?It places unique requirements on

the infrastructure – it is

recommended that

implementations use open

standards to realize interoperability

and location transparency. ?Implementations are environment-

specific – they are constrained or

enabled by context and must be

described within that context.

?It requires strong governance of

service representation and

implementation.

?It requires a “Litmus Test”, which

determines a “good service”. 面向服务

一种支持面向服务的架构风格,具有以

下显著特点:

?面向服务以服务设计为基础,这些服

务映射到真实的业务活动,且由企业

(或企业间)的业务流程构成。

?服务呈现利用业务描述提供情境(即

业务流程、目标、规则、策略、服务

接口和服务构件),并使用服务编排

实施服务。

?面向服务对基础设施提出了独特要求

。对于服务实施,推荐使用开放标准

实现互操作性和位置透明性。

?服务实施与具体环境相关,受情境约

束或实现,并且必须在该情境中加以

描述。

?面向服务要求对服务呈现和实施进行

强有力的治理。

?面向服务还要求进行“试金石测试”

,确保“服务良好”。

§3.63 Service Orientation

Service Oriented Architecture (SOA) A style of architecture (business and technology) that is specifically intended to simplify the interoperation of different parts of that business, permitting greater flexibility for change. 面向服务架构

一种(业务和技术的)架构风格,其主

要目的是为了简化业务各部分之间的互

操作,实现更大的变更灵活性。

§3.64 Service Oriented

Architecture (SOA)

TOGAF? 9.1 Translation Glossary: English – Simplified Chinese 13

Solution Architecture

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 requirements into a solution vision, high-level business and/or IT system specifications, and a portfolio of implementation tasks. 解决方案架构

对目标明确的独立业务运营或活动以及

对IS/IT如何支持该业务运营的描述。解

决方案架构通常应用于单个项目或项目

发布,帮助将需求转变成解决方案愿景

、高级业务和/或IT系统规格以及一组实

施任务的项目组合。

§3.65 Solution

Architecture

Solution Building Block (SBB)

A candidate solution which conforms to the specification of an Architecture Building Block (ABB). 解决方案构建块

一种符合架构构建块规范的候选解决方

案。

§3.66 Solution Building

Block (SBB)

Solutions Continuum

Represents the implementations of the architectures at the corresponding levels of the Architecture Continuum. At each level, the Solutions Continuum is a population of the architecture with reference building blocks – either purchased products or built components – that represent a solution to the enterprise's business need expressed at that level. 解决方案连续系列

解决方案连续系列是企业连续系列的一

部分,是针对未来实施工作的可重用解

决方案存储库。它包含架构连续系列中

相关定义的实现。

§3.67 Solutions Continuum

Stakeholder

An individual, team, or organization (or classes thereof) with interests in, or concerns relative to the outcome of the architecture. 利益相关者

与架构产出利益相关或对架构产出具有

相应关注的个人、团队或组织(或其中

的某些群体)。角色各异的不同利益相

关者,其关注也不尽相同。

§3.68 Stakeholder

Standards Information Base (SIB) Provides a database of standards that can be used to define the particular services and other components of an Organization-Specific Architecture that is derived from the TOGAF Foundation Architecture. 标准信息库

各种标准的数据库,可用于定义组织特

定架构的特定服务和其他构件。

§3.69 Standards

Information Base (SIB)

Strategic Architecture

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. 战略架构

对企业的概括性正式描述,提供运营和

变革活动的组织框架和方向设定的管理

级远期视图。

§3.70 Strategic

Architecture

14 Technical Standard (2012)

相关主题
文本预览
相关文档 最新文档