anootations ieee 42010 : a conceptual model of architecture description

Information System Architecture

iiiiii

IEEE 42010 A Conceptual Model of Architecture Description

The Core of Architecture Description

Emmanuel FUCHS Information System Architecture

iiiiiiStakeholder

Architecture System-of- Interest

Model Kind

has interests in

http://www.iso-architecture.org/ieee-1471/cm/index.html

1

Architecture View

Architecture Model

Concern

Architecture Viewpoint

Architecture Rationale

Correspondance Rule Correspondance

Architecture Description

exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1


iiiiiiArchitecture Description An Architecture Description (AD) is a work product used to express the Architecture of some System Of Interest. An AD describes one possible Architecture for a System Of Interest. An AD may take the form of a document, a set of models, a model repository, or some other form.


iiiiiiSystem-of- Interest



iiiiiiSystem-of- Interest


An Architecture Description (AD) identifies the system-of-interest whose architecture is being expressed. The term system is used as a placeholder. it could refer to an enterprise, a system of systems, a product line, a service, a subsystem, or software. Systems can be man-made or natural.


iiiiiiArchitecture System-of- Interest


exhibits

1 1


iiiiiiArchitecture System-of- Interest


exhibits

1 1

Architecture Systems have architectures. The architecture of a system is defined as:

“fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution”. The definition was chosen : (1)   to accommodate the broad range of things listed above under System:

The architecture of X is what is fundamental to X (whether X is an enterprise, system, system of systems, or some other entity);

(2) to emphasize (via the phrase “concepts or properties”) that a system can have an architecture even if that architecture is not written down.


iiiiiiStakeholder



exhibits

1 1


iiiiiiStakeholder


has interests in


exhibits

1 1

1


iiiiiiStakeholder


has interests in


exhibits

1 1

1

Stakeholder Stakeholders are individuals, groups or organizations holding Concerns for the System of Interest. Examples of stakeholders: client, owner, user, consumer, supplier, designer, maintainer, auditor, CEO, certification authority, architect.


iiiiiiStakeholder


has interests in


exhibits

has

1 1

1


iiiiiiStakeholder


has interests in


Concern

exhibits

has

1 1

1


iiiiiiStakeholder


has interests in


Concern

exhibits

has

1 1

1

Concern A Concern is any interest in the system. The term derives from the phrase “separation of concerns” as originally coined by Edsgar Dijkstra. Examples of concerns: (system) purpose, functionality, structure, behavior, cost, supportability, safety, interoperability.


iiiiiiStakeholder


has interests in


Concern

exhibits

has

1 1

1


iiiiiiStakeholder


has interests in


Concern


exhibits

has

1 1

1


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

has

1 1

1


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

has

1 1

1

Architecture Description An Architecture Description (AD) is a work product used to express the Architecture of some System Of Interest. An AD describes one possible Architecture for a System Of Interest. An AD may take the form of a document, a set of models, a model repository, or some other form.


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

has

1

1 1

1


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

has

1

1 1

1

An AD identifies the system-of-interest whose architecture is being expressed.


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

identifies

has

1

1

1 1

1


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

identifies

has

1

1

1 1

1

An AD identifies the stakeholders of the system-of-interest whose concerns are considered fundamental to the architecture (i.e., "architecturally significant"). When identifying stakeholders, the following are to be considered and included when applicable:

- users of the system; - operators of the system; - acquirers of the system; - owners of the system; - suppliers of the system; - developers of the system; - builders of the system; - maintainers of the system.


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

identifies

has

1

1

1

1 1

1


iiiiiiStakeholder


has interests in


1

Concern


exhibits

expresses

1

identifies

has

1

1

1

1 1

1

- the purposes of the system; - the suitability of the architecture for achieving the system’s purposes; - the feasibility of constructing and deploying the system; - the potential risks and impacts of the system to its stakeholders throughout its life cycle; - maintainability and evolvability of the system.

An AD identifies concerns considered fundamental to the architecture (i.e., "architecturally significant")

When identifying concerns, the following are to be considered and included when applicable:


iiiiiiStakeholder


has interests in


1

Concern



exhibits

expresses

1

identifies

has

1

1

1

1 1

1


iiiiiiStakeholder


has interests in


1

Concern



exhibits

expresses

1

identifies

has

1

1

1

1 1

1

Architecture Rationale Architecture Rationale records the explanation, justification or reasoning about Architecture Decisions that have been made and architectural alternatives not chosen.


iiiiiiStakeholder


has interests in


1

Concern



exhibits

expresses

1

identifies

has

frames

1

1

1

1 1

1



iiiiiiStakeholder


has interests in


1

Concern



exhibits

expresses

1

identifies

has

frames

1

1

1

1 1

1

Each identified concern must be framed by at least one viewpoint. This is so that that all identified concerns are covered. Each architecture viewpoint is defined among others by the concerns framed by this viewpoint and the stakeholders interested in this viewpoint;

An AD includes architecture viewpoint.



iiiiiiStakeholder


has interests in


1

Architecture View

Concern



exhibits

expresses

1

identifies

has

frames

1

1

1

1 1

1



iiiiiiStakeholder


has interests in


1

Architecture View

Concern



exhibits

expresses

1

identifies

governs

has

frames

1

1

1

1 1

1

1 1



iiiiiiStakeholder


has interests in


1

Architecture View

Concern



exhibits

expresses

1

identifies

governs

has

frames

1

1

1

1 1

1

1 1

An AD includes exactly one architecture view for each architecture viewpoint used. This is called the view's governing viewpoint. Each architecture view adheres to the conventions specified by its governing viewpoint



iiiiiiStakeholder


has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

has

frames addresses

1

1

1

1 1

1

1 1


iiiiiiStakeholder


has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

has

frames addresses

1

1

1

1 1

1

1 1

Each architecture view includes one or more architecture models that address all of the concerns framed by its governing viewpoint, and cover the whole system from that viewpoint.


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

has

frames addresses

1

1

1

1 1

1

1 1


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

has

frames addresses

1

1

1

1 1

1

1 1

Each architecture viewpoint is defined by the model kinds used in this viewpoint. A model kind captures conventions for a type of modeling. To efficiently frame a set of concerns, a viewpoint can use one or more model kinds.


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern




exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1

Each architecture model identifies its governing model kind and adheres to the conventions of that model kind; Model kind defines the languages, notations, conventions, modelling techniques, analytical methods and/or other operations useful on models of this kind;


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern



Correspondance


exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern





exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1


iiiiiiStakeholder


Model Kind

has interests in


1

Architecture View

Architecture Model

Concern





exhibits

expresses

1

identifies

governs

governs

has

frames addresses

1

1

1

1 1

1

1 1

1

Correspondences capture relationships between AD Elements. Correspondences and Correspondence Rules are used to express and enforce architecture relations such as composition, refinement, consistency, traceability, dependency, constraint and obligation within or between ADs.

anootations ieee 42010 : a conceptual model of architecture description

Engineering