language en

Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts

Release: 2019-03-17

Modified on: 2019-03-17
This version:
https://meta.linked.archi/iso42010/0.1.0#
Revision:
0.1.0
Issued on:
2019-03-17
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
Source:
https://www.iso.org/standard/74393.html
See also:
https://www.iso.org/standard/74393.html
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
ISO/IEC/IEEE 42010:2022 Software, systems and enterprise — Architecture description
Provenance of this page
draft

Abstract

Architecture description concepts from ISO/IEC/IEEE 42010, modelled as SKOS concepts with rdfs:seeAlso links to the corresponding classes in the Linked.Archi core ontology.

Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts: Overview back to ToC

This ontology has the following classes and properties.

Classes

Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts: Description back to ToC

SKOS taxonomy of architecture description concepts from ISO/IEC/IEEE 42010:2022. This is the architecture description standard that the Linked.Archi core ontology aligns to. Covers the key concepts of system, architecture, architecture description, stakeholder, concern, architecture viewpoint, architecture view, architecture model, architecture decision, architecture rationale, correspondence, and correspondence rule.

Cross-reference for Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts.

Classes

Architecturec back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#Architecture

Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

Architecture Decisionc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureDecision

A decision that pertains to the architecture of a system. Architecture decisions affect the architecture and are justified by architecture rationale.

Architecture Descriptionc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureDescription

A work product used to express an architecture. An architecture description is composed of architecture views, each conforming to an architecture viewpoint.

Architecture Modelc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureModel

A work product that uses the conventions of its associated model kind to address specific system concerns within an architecture view.

Architecture Rationalec back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureRationale

A record of the reasoning and justification behind architecture decisions, including the alternatives considered, trade-offs evaluated, and the basis for the chosen approach.

Architecture Viewc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureView

A work product expressing the architecture of a system with respect to specific system concerns, governed by its architecture viewpoint. A view is composed of one or more architecture models.

Architecture Viewpointc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#ArchitectureViewpoint

A work product establishing the conventions for the construction, interpretation, and use of architecture views to frame specific system concerns. A viewpoint includes model kinds, notations, and conventions.

Concernc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#Concern

An interest in a system relevant to one or more of its stakeholders. Concerns include system considerations such as performance, reliability, security, distribution, and evolvability.

Correspondencec back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#Correspondence

A relation between architecture description elements. Correspondences express and enforce architecture relations such as composition, refinement, consistency, traceability, dependency, constraint, and obligation.

Correspondence Rulec back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#CorrespondenceRule

A rule that governs correspondences and enforces constraints on architecture description elements, ensuring consistency and integrity across architecture views and models.

Stakeholderc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#Stakeholder

An individual, team, organization, or classes thereof, having an interest in a system. Stakeholders have concerns with respect to the system.

Systemc back to ToC or Class ToC

IRI: https://meta.linked.archi/iso42010#System

A combination of interacting elements organized to achieve one or more stated purposes. A system is a construct or collection of different elements that together produce results not obtainable by the elements alone.

Legend back to ToC

c: Classes

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.