ISO/IEC JTC 1/SC 7/WG 42 - Architecture
Architecture
General Information
Frequently Asked Questions
ISO/IEC JTC 1/SC 7/WG 42 is a Subcommittee within the International Organization for Standardization (ISO). It is named "Architecture". This committee has published 4 standards.
ISO/IEC JTC 1/SC 7/WG 42 develops ISO standards in the area of Information technology. Currently, there are 4 published standards from this subcommittee.
The International Organization for Standardization (ISO) is an independent, non-governmental international organization that develops and publishes international standards. Founded in 1947 and headquartered in Geneva, Switzerland, ISO brings together experts from 170+ member countries to share knowledge and develop voluntary, consensus-based standards that support innovation and provide solutions to global challenges.
A Subcommittee (SC) in ISO operates under a Technical Committee and focuses on a specific subset of the TC's scope. Subcommittees develop standards and technical specifications in their specialized area, reporting to their parent Technical Committee. They may also have working groups for detailed technical work.
This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
- Standard62 pagesEnglish languagesale 15% off
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.
- Standard77 pagesEnglish languagesale 15% off
This document establishes a set of process descriptions for the governance and management of a collection of architectures and the architecting of entities. This document also establishes an enablement process description that provides support to these other architecture processes. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable throughout the life of an architecture or a collection of architectures. These processes are applicable for managing and performing the activities within any stage in the life cycle of the architecture entities. Annex D describes the relationships between this document and other standards.
- Standard110 pagesEnglish languagesale 15% off
ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.
- Standard37 pagesEnglish languagesale 15% off