MBSE Round-robin overview – Richard Martin

ISO/IEC/IEEE 42010 Architecture

description

www.incose.org/IW2022
ISO/IEC/IEEE 42010, standard context
ISO/IEC/IEEE
15288 System life
cycle processes
Defines the System
Architecture Definition Process
Defines the Software
Architecture Definition Process
ISO/IEC/IEEE 12207
Software life cycle
processes
30-janv.-22
ISO 15704 Requirements for
enterprise-referencing
Refines architectures and methodologies
Enterprise
Provides the context for
processes Provides
System and its life cycle Enterprise
processes Principles
ISO/IEC/IEEE 42020
Architecture Processes
Provides processes for application of
Provides the context for
architecture description and evaluation
Software and its life cycle
processes
ISO/IEC/IEEE 42010
Architecture Description ISO/IEC/IEEE 42030
Architecture evaluation
www.incose.org/IW2022 2
 Scope and history
 Specifies requirements on architecture description (AD) for various entities
 Distinguishes the architecture of an entity of interest from an AD Aim is to keep
expressing that architecture scope and content
 Specifies requirements on an architecture description framework (ADF), an up to date, with
architecture description language (ADL), architecture viewpoints and regards to the
model kinds evolution of
 Specifies conformance to the requirements for an AD, ADF, ADL, Architecting
architecture viewpoint and model kind activities and
practices in our
 Does not specify processes, architecting methods, models, notations,
organizations.
techniques tools, format or media by which an AD is created, utilized or
managed.
• IEEE Std 1471-2000
IEEE Recommended Practice for Architectural Description of Software-Intensive Systems
• ISO/IEC/IEEE 42010:2011 Systems and software engineering — Architecture description
• ISO/IEC/IEEE 42010 Edition 2 Software, systems and enterprise — Architecture description

30-janv.-22 www.incose.org/IW2022 3
ISO/IEC 42010:2011 Context & Concept Model

30-janv.-22 www.incose.org/IW2022 4
 ISO/IEC/FDIS 42010 – Conceptual model of
architecture description
•Instead of UML class diagrams, the figures use
an informal entity-relationship diagram notation
to facilitate comprehension by non-technical
users. Relations read as propositions

•The term used to refer to the subject of an

architecture description is changed from “system
of interest” to “entity of interest” (EoI) to be
compatible with ISO/IEC/IEEE 42020 and
ISO/IEC/IEEE 42030 standards and to allow
for its application in non-system architecture
situations.

•The term “entity” is also used in this document

when entities are considered as surrounding
things in an environment of an EoI.
30-janv.-22 www.incose.org/IW2022 5
 42010 term taxonomy architecture
– term use in Ed 1 & Ed2
architecture
view architecture environment
description
architecting

entity
of
architecture
Interest
viewpoint
<system>

concern
stakeholder
Defined terms use of other defined terms – all arcs are ‘uses’ relationship
EXAMPLE - architecture viewpoint work product establishing the conventions for the
construction,
30-janv.-22 interpretation and use ofwww.incose.org/IW2022
architecture views to frame specific system concerns
6
 42010 term taxonomy – change from Ed1 to Ed2 architecture
architecture
description
architecture language
view architecture environment ADL
description
architecting
architecture
framework
view architecture
component description entity architecture
(AD) element of
architecture description
Interest framework
viewpoint
<system> ADF
correspondence
information
part concern
stakeholder

model stakeholder
perspective Defined in Ed2 but not
specification kind used in other term definitions
aspect
30-janv.-22 www.incose.org/IW2022 7
Ed2 proper use of aspect and perspective

From that () to this (→)

30-janv.-22 www.incose.org/IW2022 8
 ISO/IEC/IEEE 42010 – Other conceptual models
Domain of Correspondence
Stakeholder
interest method

applies
has identifies to is contained in
typical

Architecture defines
Concern description
identifies framework
typical
has

specifies
frames

organizes used in
Conceptual model of AD
Architecture Structuring Structural
viewpoint formalism category element correspondences
Conceptual model for an architecture
description framework

Conceptual model of an
architecture description language
30-janv.-22 www.incose.org/IW2022 9
ADFs provide predefined viewpoints,
perspectives, aspects and model kinds

30-janv.-22 www.incose.org/IW2022 10
 AD Frameworks propose multi-dimensional
approaches
2D: (Source: OMG/Unified Architecture Framework) (UAF) 3D: (Source: Sherwood Applied Business Security Architecture (SABSA) institute)

2D: (Source: NATO Architecture Framework)

2D: (Source: Zachman Framework)

4D: (Source: ISO 15704 Ed2 (Generalized Enterprise Reference Architecture and Methodology))
30-janv.-22 www.incose.org/IW2022 11
 Correspondences
42010 [2nd edition] Correspondence Architecture
AD Element
relationship between architecture Description
is
description elements or between composition
architecture descriptions of
Examples: Correspondences can include a relates relates
wide range or relationship types, such as 2 or more 2 or more
equivalence, composition, refinement,
AD Element AD
consistency, traceability, dependency,
Correspondence Correspondence
constraint, satisfaction, and obligation.
42010 [2nd edition] AD element
part of an architecture description that
expresses concepts or properties of the governs
architecture
Correspondence governs
Note to entry: AD elements include
stakeholders, concerns, perspectives, aspects, Method
identified in an AD and views, view
components, viewpoints and model kinds An AD can be an AD element in another
included in an AD architecture.
30-janv.-22 www.incose.org/IW2022 12
www.incose.org/IW2022