Architecture Meta-Data Layer

A1 – Meta-Data Definitions

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
ArchitectureView	Type	A work product expressing the architecture of a system from the perspective of specific system concerns.
DublinCoreTag	Type	A MetaDataCategory that is a DublinCore tag.
MetaData	Type	A StringRepresentation that can be applied to any element in the architecture. Note: wherever possible, standard Meta-Data types should be used - e.g. conforming to Dublin Core Note for MOD Users: The MOD Meta Data Standard categories shall be used.
MetaDataCategory	Type	A MetaDataType that defines the category of a MetaData element. example: http://purl.org/dc/terms/abstract
MetaDataCategoryInScheme	Type	A WholePartTypeType that asserts a MetaDataCategory belongs to a MetaDataScheme.
MetaDataScheme	Type	A RepresentationScheme that defines a set of MetaData.
ModemThing	Type	Any Thing that can feature in a MODEM Architecture. Note: things that appear in the MODEM metamodel will not necessarily be instances, unless they appear in an architecture.
ArchitectureViewpoint	Type	A work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns.
ModelElement	Type	A graphical element in an ArchitectureModel.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
URI	Type	A MetaData that is a uniform resource identifier.
URL	Type	A URI that is a uniform resource location.
URN	Type	A URI that is a uniform resource name.
architectureMetaData	TupleType	A metaDataAnnotation that relates a MetaData element to the ArchitectureDescription it annotates.
assumption	TupleType	A describedBy that states an assumption about an ADElement. Note: Any given ADElement may have zero to many assumptions.
categoryOfMetaData	TupleType	A typeInstance that relates a MetaData element to its category.
definition	TupleType	A metaDataAnnotation that provides the definition for a ModemThing.
finding	TupleType	A describedBy that describes a finding about an ArchitectureDescription. Note: Any given ADElement may have zero to many findings.
metaDataAnnotation	TupleType	A representedBy that relates a MetaData element to the ModemThing it describes.
purpose	TupleType	An architectureMetaData that describes the purpose of a StructuredADElement.
recommendation	TupleType	An architectureMetaData that expresses a recommendation arising from a StructuredADElement.
viewCode	TupleType	A metaDataAnnotation that uses MetaData to represent the short code that identifies an ArchitectureViewpoint. Note that viewCode and viewDescription from M3 are handled using the core IDEAS description and naming patterns.
webReference	TupleType	A metaDataAnnotation that asserts URI contains information about a ModemThing.

Table ‑: A1 Element List

A2 – Architecture Products

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
Architecture	Type	Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureFramework	Type	From ISO42010: Uses of architecture frameworks include, but are not limited to: creating architecture descriptions; developing architecture modelling tools and architecting methods; and establishing processes to facilitate communication, commitments and interoperation across multiple projects and/or organizations. NOTE 1 Architecture frameworks frequently encompass both provisions for architecture description and additional architecting practices. EXAMPLES The following are architecture frameworks in the terms of this International Standard: Zachman’s information systems architecture framework [44], UK Ministry of Defence Architecture Framework [27], The Open Group’s Architecture Framework (TOGAF) [41], Kruchten’s “4+1” view model [23], Siemens’ 4 views method [10], Reference Model for Open Distributed Processing (RM-ODP), [ISO/IEC 10746] and Generalized Enterprise Reference Architecture (GERA) [ISO 15704].
ArchitectureModel	Type	No specific definition provided in ISO42010.
ArchitectureView	Type	A work product expressing the architecture of a system from the perspective of specific system concerns.
ArchitectureViewpoint	Type	A work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns.
Concerns	Type	From ISO42010: A concern could be held by one or more stakeholders. Concerns arise throughout the life cycle from system needs and requirements, from design choices and from implementation and operating considerations. A concern could be manifest in many forms, such as in relation to one or more stakeholder needs, goals, expectations, responsibilities, requirements, design constraints, assumptions, dependencies, quality attributes, architecture decisions, risks or other issues pertaining to the system. EXAMPLES The following are concerns in the terms of this International Standard: functionality, feasibility, usage, system purposes, system features, system properties, known limitations, structure, behavior, performance, resource utilization, reliability, security, information assurance, complexity, evolvability, openness, concurrency, autonomy, cost, schedule, quality of service, flexibility, agility, modifiability, modularity, control, inter-process communication, deadlock, state change, subsystem integration, data accessibility, privacy, compliance to regulation, assurance, business goals and strategies, customer experience, maintainability, affordability and disposability. The distribution transparencies described in the Reference Model of Open Distributed Processing [ISO/IEC 10746-1] are concerns in the terms of this International Standard. Software properties as described in SQUARE [ISO/IEC 25010:2011, 4.2] name concerns in the terms of this International Standard.
ConfiguredResourceType	Type	An IndividualResourcePowertype that is a part of a ResourceType another ConfiguredResourceType.
HumanAndNonHumanConfigurationType	Type	A ResourceType that has both Human and Non-Human components.
ISO42010_System	Type	The term system is used in this International Standard to refer to entities whose architectures are of interest. The term is intended to encompass, but is not limited to, entities within the following domains: - systems as described in [ISO/IEC 15288]: “systems that are man-made and may be configured with one or more of the following: hardware, software, data, humans, processes (e.g., processes for providing service to users), procedures (e.g. operator instructions), facilities, materials and naturally occurring entities”; - software products and services as described in [ISO/IEC 12207]; - software-intensive systems as described in [IEEE Std 1471TM:2000]: “any system where software contributes essential influences to the design, construction, deployment, and evolution of the system as a whole” to encompass “individual applications, systems in the traditional sense, subsystems, systems of systems, product lines, product families, whole enterprises, and other aggregations of interest”. This International Standard takes no position on what constitutes a system within those domains—or elsewhere. The nature of systems is not defined by this International Standard.
LogicalArchitecture	Type	A NodeParent whose parts are either Nodes, KnownResources or LogicalDomains.
MetaData	Type	A StringRepresentation that can be applied to any element in the architecture. Note: wherever possible, standard Meta-Data types should be used - e.g. conforming to Dublin Core Note for MOD Users: The MOD Meta Data Standard categories shall be used.
MetaDataCategory	Type	A MetaDataType that defines the category of a MetaData element. example: http://purl.org/dc/terms/abstract
MetaDataCategoryInScheme	Type	A WholePartTypeType that asserts a MetaDataCategory belongs to a MetaDataScheme.
MetaDataScheme	Type	A RepresentationScheme that defines a set of MetaData.
ModelKind	Type	Conventions for a type of modelling. NOTE Examples of model kinds include: data flow diagrams, class diagrams, Petri nets, balance sheets, organization charts and state transition models.
ModelKindPartOfViewpoint	Type	A ModelPartOfViewType where a ModelKind is a typical part of an ArchitectureViewpoint.
ModelPartOfView	Type	A ModelPartOfViewType where a ModelKind is a typical part of an ArchitectureViewpoint.
OrganisationType	Type	A ResponsibleHumanResourceType and a ConstructedHumanResourceType that is a type of Organisation. This is not used as a component of a ResourceType. Examples: Government Department, Commercial Company, Accounting Department.
PersonType	Type	A ResponsibleHumanResourceType that is a type of person.
PhysicalArchitecture	Type	A HumanAndNonHumanConfigurationType that specifies the structure and behaviour of an EnterprisePhase.
PostType	Type	A ConstructedHumanResourceType and ResponsibleHumanResourceType specifying a type of Post. This is not used as a component of a ResourceType. A type of point of contact or responsible person. Note that this is the type of post - e.g. Desk Officer, Commander, etc.
ResourceType	Type	A PhysicalArchitectureIndividualType that is a type of IndividualResource. This is not used as a component of a ResourceType, but may use components. [ABSTRACT]
ResourceTypeConfiguration	Type	A ModemWholePartType that is a relationship between types of ResourceTypeUsages which asserts one ResourceTypeUsage is part of another.
ResponsibleHumanResourceType	Type	A HumanResourceType that is a type of ResponsibleHumanResource. A PostType, OrganisationType or a PersonType.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
ViewPartOfDescription	Type	A WholePartType where an ArchitectureView is part of an ArchitectureDescription.
ViewpointPartOfFramework	Type	A WholePartTypeType that asserts an ArchitectureViewpoint is part of an ArchitectureFramework.
IndividualResourcePowertype	Powertype	The powertype of IndividualResourceState.
EnterprisePhase	IndividualType	An UndertakingState that is a current or future state of a WholeLifeEnterprise or another EnterprisePhase.
Organisation	IndividualType	A ConstructedHumanResource which is an Organisation.
Person	IndividualType	An individual human being.
Post	IndividualType	A HumanResourcethat is a position in an Organisation that may be filled wholly or partly by a ResponsibleHumanResource; in other words, by an Organisation, Person or Post. As the position is in the Organisation, it is a part of the Organisation.
ResponsibleHumanResource	IndividualType	A Person, Post or Organisation. These can be held responsible for their actions, hence are responsible human resources.
WholeLifeEnterprise	IndividualType	An EnterprisePhase that represents the whole existance of an enterprise.
architectureMetaData	TupleType	A metaDataAnnotation that relates a MetaData element to the ArchitectureDescription it annotates.
architectureRealisation	TupleType	A modemIndividualTypeSpecialisation that asserts that a PhysicalArchitecture is a realisation of a LogicalArchitecture.
architectureReference	TupleType	ArchitectureDescription to another ArchitectureDescription it refers to.
categoryOfMetaData	TupleType	A typeInstance that relates a MetaData element to its category.
configurationType	TupleType	A superSubtype that asserts that a ResourceType is a superType of ConfiguredResourceType.
enterpriseStructure	TupleType	A wholePart that asserts that one EnterprisePhase is a spatial part of another.
enterpriseTemporalPart	TupleType	An enterpriseStructure and a temporalWholePart that asserts that one EnterprisePhase is a temporal part of another (i.e. it is a phase of the other).
enterpriseWholePhase	TupleType	An enterpriseTemporalPart where whole is a WholeLifeEnterprise.
exhibits	TupleType	A couple that asserts an ISO42010_System has an Architecture.
expresses	TupleType	A representedBy that asserts and an ArchitectureDescription represents an Architecture.
frameworkGovernsDescription	TupleType	A typeInstance relating an ArchitectureDescription to the ArchitectureFramework it conforms to.
logicalArchitectureOfEnterprisePhase	TupleType	Relates an EnterprisePhase to a LogicalArchitecture that specifies its (logical) structure and behavior.
metaDataAnnotation	TupleType	A representedBy that relates a MetaData element to the ModemThing it describes.
modelKindGovernsModel	TupleType	A typeInstance where an ArchitecturalModel conforms to a ModelKind.
physicalArchitectureOfEnterprisePhase	TupleType	Relates an EnterprisePhase to a ResourceType that specifies its structure and behavior.
stakeholderConcern	TupleType	A couple that relates a Concern to a stakeholder that have the Concern. Note: a concern may be held by more than one Stakeholder, hence there maybe multiple stakeholderConcerns.
systemConcern	TupleType	A couple that relates an ISO42010_System to a Concern that is held against the system NOTE A concern pertains to any influence on a system in its environment including: developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological and social influences.
viewpointGovernsView	TupleType	A typeInstance where an ArchitectureView conforms to an ArchitectureViewpoint.

Table ‑: A2 Element List

A3 – Architecture Correspondence

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
ArchitectureView	Type	A work product expressing the architecture of a system from the perspective of specific system concerns.
Correspondence	Type	From ISO42010: A correspondence defines a relation between AD elements. Correspondences are used to express architecture relations of interest within an architecture description (or between architecture descriptions). Correspondences can be governed by correspondence rules. Correspondence rules are used to enforce relations within an architecture description (or between architecture descriptions).
CorrespondenceRule	Type	From ISO42010: Correspondence rules are used to enforce relations within an architecture description (or between architecture descriptions).
ModelElement	Type	A graphical element in an ArchitectureModel.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
architectureReference	TupleType	A couple that relates an ArchitectureDescription to another ArchitectureDescription it refers to.
ruleGovernsCorrespondence	TupleType	A typeInstance relating a correspondence to the CorrespondenceRule that governs it.

Table ‑: A3 Element List

A4 – Methodology Used

Element Name	Element Kind	Definition
ArchitectureMethodology	Type	A ProjectType that defines a standard way of running an ArchitectureProject.
ArchitectureProject	IndividualType	A Project that delivers an ArchitectureDescription.
projectMethodology	TupleType	ArchitectureProject to the ArchitectureMethodology is conforms to.

Table ‑: A4 Element List

A5 – Architecture Status

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
NextArchitectureVersion	Type	A BeforeAfterType that associates one version of an ArchitectureDescription with another version that follows it.
NextModelVersion	Type	A BeforeAfterType that associates one version of an ArchitectureModel with another version that follows it.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
ArchitectureApprovalMilestone	IndividualType	ADElement is approved by a ResponsibleHumanResource Note: this replaces the dateCompleted tag on ArchitecturalDescription in M3.
ArchitectureProject	IndividualType	A Project that delivers an ArchitectureDescription.
Manager	IndividualType	An OrganisationalRole where the Person's role in the Organisation is as a Manager. Example: when the Organisation is a Project, the role would be as project manager.
Organisation	IndividualType	A ConstructedHumanResource which is an Organisation.
OrganisationalRole	IndividualType	A ConstructedHumanResource that is the state of the ResponsibleHumanResource (that part of its life) where it has the role in an Organisation. Where a role carries the authority to undertake a function - though the human resource given the role has the responsibility.
Person	IndividualType	An individual human being.
Post	IndividualType	A HumanResourcethat is a position in an Organisation that may be filled wholly or partly by a ResponsibleHumanResource; in other words, by an Organisation, Person or Post. As the position is in the Organisation, it is a part of the Organisation.
Project	IndividualType	An Undertaking that is a time-limited endeavour to create a specific set of products or services.
ProjectMilestone	IndividualType	A ProjectPart that marks the end of one ProjectPhase and possibly the beginning of another. Note: the temporal extent of a ProjectMilestone is likely to be finite - e.g. there may be milestone meetings, funding reviews, etc. before another Project or ProjectPhase can start.
ProjectPhase	IndividualType	part of a Project and has been nominated as a phase of a Project.
ResponsibleHumanResource	IndividualType	A Person, Post or Organisation. These can be held responsible for their actions, hence are responsible human resources.
ResponsibleOwner	IndividualType	An OrganisationProjectRole where the ResponsibleHumanResource is the responsible for the Organisation - e.g. a project owner.
approved	TupleType	A couple that relates an ArchitectureApprovalMilestone to the ADElement that is approved.
approver	TupleType	A couple that relates an ArchitectureApprovalMilestone to the ResponsibleHumanResource that approved it.
createdBy	TupleType	A couple that asserts a ResponsibleHumanResource is the creator of an ADElement. Note: this covers the creatingOrganisation and architect tags that were applied to ArchitectureDescription in M3.
humanResourceInRole	TupleType	A responsibleHumanResourceState relationship between the OrganisationRole and the ResponsibleHumanResource that bears the responsibility. Note: the OrganisationRole cannot be passed on. Instead, a new instance of the role is created.
milestoneBegins	TupleType	A startBoundary that asserts a ProjectMilestone marks the beginning of a Project or ProjectPhase.
milestoneEnds	TupleType	An endBoundary that asserts a ProjectMilestone marks the end of a Project or ProjectPhase.
projectWholePhase	TupleType	A projectPhaseTemporalPart where the whole is a Project.

Table ‑: A5 Element List

A6 – Architecture Versions

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
NextArchitectureVersion	Type	A BeforeAfterType that associates one version of an ArchitectureDescription with another version that follows it.
NextModelVersion	Type	A BeforeAfterType that associates one version of an ArchitectureModel with another version that follows it.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
ArchitectureApprovalMilestone	IndividualType	A ProjectMilestone where an ADElement is approved by a ResponsibleHumanResource Note: this replaces the dateCompleted tag on ArchitecturalDescription in M3.
approved	TupleType	A couple that relates an ArchitectureApprovalMilestone to the ADElement that is approved.

Table ‑: A6 Element List

A7 – Architecture Meta-Data

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
ArchitectureView	Type	A work product expressing the architecture of a system from the perspective of specific system concerns.
ArchitectureViewpoint	Type	A work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns.
DublinCoreTag	Type	A MetaDataCategory that is a DublinCore tag.
MetaData	Type	A StringRepresentation that can be applied to any element in the architecture. Note: wherever possible, standard Meta-Data types should be used - e.g. conforming to Dublin Core Note for MOD Users: The MOD Meta Data Standard categories shall be used.
MetaDataCategory	Type	A MetaDataType that defines the category of a MetaData element. example: http://purl.org/dc/terms/abstract.
MetaDataCategoryInScheme	Type	A WholePartTypeType that asserts a MetaDataCategory belongs to a MetaDataScheme.
MetaDataScheme	Type	A RepresentationScheme that defines a set of MetaData.
ModelElement	Type	A graphical element in an ArchitectureModel.
ModemThing	Type	Any Thing that can feature in a MODEM Architecture. Note: things that appear in the MODEM metamodel will not necessarily be instances, unless they appear in an architecture.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
URI	Type	A MetaData that is a uniform resource identifier.
URL	Type	A URI that is a uniform resource location.
URN	Type	A URI that is a uniform resource name.
architectureMetaData	TupleType	A metaDataAnnotation that relates a MetaData element to the ArchitectureDescription it annotates.
assumption	TupleType	A describedBy that states an assumption about an ADElement. Note: Any given ADElement may have zero to many assumptions.
categoryOfMetaData	TupleType	A typeInstance that relates a MetaData element to its category.
definition	TupleType	A metaDataAnnotation that provides the definition for a ModemThing.
finding	TupleType	A describedBy that describes a finding about an ArchitectureDescription. Note: Any given ADElement may have zero to many findings.
metaDataAnnotation	TupleType	A representedBy that relates a MetaData element to the ModemThing it describes.
purpose	TupleType	An architectureMetaData that describes the purpose of a StructuredADElement.
recommendation	TupleType	An architectureMetaData that expresses a recommendation arising from a StructuredADElement.
viewCode	TupleType	A metaDataAnnotation that uses MetaData to represent the short code that identifies an ArchitectureViewpoint. Note that viewCode and viewDescription from M3 are handled using the core IDEAS description and naming patterns.
webReference	TupleType	A metaDataAnnotation that asserts URI contains information about a ModemThing.

Table ‑: A7 Element List

A8 – Standards

Element Name	Element Kind	Definition
FrequencyRange	Type	A MeasureRange that specifies maximum and minimum frequencies, measured in Hertz as real numbers.
ModemIndividualType	Type	The parent (supertype) of all MODEM elements that are types of Individuals e.g. tank, computer, etc.
Protocol	Type	A Standard for communication.
ProtocolStack	Type	A ModemIndividualType that is all the Individuals which conform to one or more specified protocols (ordered into a stack) that may be implemented by one or more ResourcePorts. Note: was called "ImplementedProtocol" in M3.
Standard	Type	A ModemIndividualType that is all the individuals that conform to a ratified and peer-reviewed specification that is used to guide or constrain the architecture. A Standard may be applied to any element in the architecture.
SpectrumAllocation	Type	A Standard specifying a particular frequency range of the electromagnetic spectrum that is allotted to a particular usage.
CalendarPeriod	IndividualType	A Period that corresponds to a recognised date or time Examples: 1st June 1974, 1885, 14:44:01 on 2nd June 1974, December 2008
ModemIndividualElement	IndividualType	An Individual that can feature in a MODEM architecture.
Organisation	IndividualType	A ConstructedHumanResource which is an Organisation.
individualConformsTo	TupleType	A modemIndividualTypeInstance that asserts that an element in the architecture conforms to a Standard.
typeConformsTo	TupleType	A modemIndividualTypeSpecialisation that asserts a type in the architecture conforms to a Standard.
responsibleForRatifying	TupleType	A couple that asserts than an Organisation is responsible for the ratification of a standard. Note: was called "RatificationBody" in M3.
ratifiedOn	TupleType	A couple that asserts a Standard has been ratified on a date.
withdrawnOn	TupleType	A couple that asserts a Standard has been withdrawn on a date.
spectrumAllocationRadioFrequencyRange	TupleType	A radioFrequencyRangeAssignment that asserts a spectrum allocation has been assigned to a frequency range.
isALayerIn	TupleType	A superSubtype that asserts that a ProtocolStack is a kind of Protocol. The Protocol is a layer in the ProtocolStack. The order of the layering is determined by the Protocols' runsOn relations. Note: amalgamates "ProtocolLayer" and "ImplementedOn" in M3.

Table ‑: A8 Element List

Ar – Architecture Roadmap

Element Name	Element Kind	Definition
ADElement	Type	From ISO42010: An AD element is any construct in an architecture description. AD elements are the most primitive constructs discussed in this International Standard. Every stakeholder, concern, architecture viewpoint, architecture view, model kind, architecture model, architecture decision and rationale (see 4.2.7) is considered an AD element. When viewpoints and model kinds are defined and their models are populated, additional AD elements are introduced.
ArchitectureDescription	Type	A work product used to express an architecture.
ArchitectureModel	Type	No specific definition provided in ISO42010.
ArchitectureView	Type	A work product expressing the architecture of a system from the perspective of specific system concerns.
ModelElement	Type	A graphical element in an ArchitectureModel.
SoftwareType	Type	An ArtefactType that is a type of Software.
StructuredADElement	Type	An ADElement that has other ADElements as part of it. Note: this is not in ISO42010, but is required if the model is to be useful.
ArchitectureApprovalMilestone	IndividualType	A ProjectMilestone where an ADElement is approved by a ResponsibleHumanResource. Note: this replaces the dateCompleted tag on ArchitecturalDescription in M3.
Manager	IndividualType	An OrganisationalRole where the Person's role in the Organisation is as a Manager. Example: when the Organisation is a Project, the role would be as project manager.
ModellingSession	IndividualType	A ProjectPart where ArchitectureDescriptions are worked on.
Organisation	IndividualType	A ConstructedHumanResource which is an Organisation.
OrganisationalRole	IndividualType	A ConstructedHumanResource that is the state of the ResponsibleHumanResource (that part of its life) where it has the role in an Organisation. Where a role carries the authority to undertake a function - though the human resource given the role has the responsibility.
Person	IndividualType	An individual human being.
Post	IndividualType	A HumanResourcethat is a position in an Organisation that may be filled wholly or partly by a ResponsibleHumanResource; in other words, by an Organisation, Person or Post. As the position is in the Organisation, it is a part of the Organisation.
Project	IndividualType	An Undertaking that is a time-limited endeavour to create a specific set of products or services.
ProjectMilestone	IndividualType	A ProjectPart that marks the end of one ProjectPhase and possibly the beginning of another. Note: the temporal extent of a ProjectMilestone is likely to be finite - e.g. there may be milestone meetings, funding reviews, etc. before another Project or ProjectPhase can start.
ProjectPhase	IndividualType	An ProjectState that is a temporal part of a Project and has been nominated as a phase of a Project.
ResponsibleHumanResource	IndividualType	A Person, Post or Organisation. These can be held responsible for their actions, hence are responsible human resources.
ResponsibleOwner	IndividualType	An OrganisationProjectRole where the ResponsibleHumanResource is the responsible for the Organisation - e.g. a project owner.
approved	TupleType	A couple that relates an ArchitectureApprovalMilestone to the ADElement that is approved.
approver	TupleType	A couple that relates an ArchitectureApprovalMilestone to the ResponsibleHumanResource that approved it.
createdBy	TupleType	A couple that asserts a ResponsibleHumanResource is the creator of an ADElement. Note: this covers the creatingOrganisation and architect tags that were applied to ArchitectureDescription in M3.
milestoneBegins	TupleType	A startBoundary that asserts a ProjectMilestone marks the beginning of a Project or ProjectPhase.
milestoneEnds	TupleType	An endBoundary that asserts a ProjectMilestone marks the end of a Project or ProjectPhase.
modeller	TupleType	An agentParticipation where a Person conducts a ModellingSession
modellingSessionInProject	TupleType	A projectWholePart relating a ModellingSession to the ArchitectureProject it is part of.
humanResourceInRole	TupleType	A responsibleHumanResourceState relationship between the OrganisationRole and the ResponsibleHumanResource that bears the responsibility. Note: the OrganisationRole cannot be passed on. Instead, a new instance of the role is created.
projectWholePhase	TupleType	A projectPhaseTemporalPart where the whole is a Project.
projectWholeAndPart	TupleType	A projectWholePart where both the whole and part are Projects.
toolUsed	TupleType	A couple that asserts a SoftwareType was used in the production of a StructuredADElement.

Table ‑: Ar Element List