本文件规定了组织和记录企业、系统和应用软件领域架构评估的方法。 本文档的目的是实现架构评估，该评估用于: a） 验证架构是否解决了利益相关者的问题； b） 评估与预期用途相关的建筑质量； c） 评估架构对其利益相关者的价值； d） 确定架构实体是否满足其预期目的； e） 提供有关架构实体的知识和信息； f） 评估实现架构目标的进展； g） 澄清对问题空间以及利益相关者需求和期望的理解； h） 识别与架构相关的风险和机遇；和 i） 支持涉及架构的决策制定。 注:本文件旨在评估架构，而不是评估架构描述的适用性。 有关架构（architecture）描述评估的事项属于ISO/IEC/IEEE 42020中定义的架构（architecture）概念化和架构（architecture）细化过程的范围。然而，有时架构描述的评估与架构本身的评估同时进行。 被评估的实体可以是几种类型，如以下示例所示:企业、组织、解决方案、系统、子系统、业务、数据（作为数据元素或数据结构）、应用程序、信息技术（作为集合）、任务、产品、服务、软件项、硬件项等。实体的类型还可以是产品线、系统系列、，系统体系等。它还涵盖了利用数字技术的各种应用，如移动、云、大数据、机器人、物联网（IoT）、web、桌面、嵌入式系统等。 本文件中规定的通用体系结构评估（AE）框架可用于支持ISO/IEC/IEEE 42020中定义的体系结构评估过程。 具体的框架可以从这个通用框架中派生出来，它可以提供到ISO/IEC/IEEE 15288中的系统生命周期过程或ISO/IEC/IEEE 12207中的软件生命周期过程的映射。

This document specifies the means to organize and record architecture evaluations for enterprise, systems and software fields of application. The aim of this document is to enable architecture evaluations that are used to: a) validate that architectures address the concerns of stakeholders; b) assess the quality of architectures with respect to their intended purpose; c) assess the value of architectures to their stakeholders; d) determine whether architecture entities address their intended purpose; e) provide knowledge and information about architecture entities; f) assess progress towards achieving architecture objectives; g) clarify understanding of problem space and of stakeholder needs and expectations; h) identify risks and opportunities associated with architectures; and i) support decision making where architectures are involved. NOTE This document addresses the evaluation of an architecture and not an evaluation of the architecture description's suitability. Matters concerning the evaluation of the architecture description fall within the scope of the architecture conceptualization and architecture elaboration processes as defined in ISO/IEC/IEEE 42020. However, it is sometimes the case that the architecture description is evaluated concurrently with the evaluation of the architecture itself. The entity being evaluated can be of several kinds, as illustrated in the following examples: enterprise, organization, solution, system, subsystem, business, data (as a data element or data structure), application, information technology (as a collection), mission, product, service, software item, hardware item, etc. The kind of entity can also be a product line, family of systems, system of systems, etc. It also spans the variety of applications that utilize digital technology such as mobile, cloud, big data, robotics, Internet of Things (IoT), web, desktop, embedded systems, and so on. The generic Architecture Evaluation (AE) framework specified in this document can be used in support of the Architecture Evaluation process defined in ISO/IEC/IEEE 42020. Specific frameworks can be derived from this generic framework, which can provide a mapping to the system life cycle processes in ISO/IEC/IEEE 15288 or to the software life cycle processes in ISO/IEC/IEEE 12207.