UPDM is top level profile root. UPDM UPDM L1 contains UPDM L0 and imports the entire SysML profile. This compliance level contains a set of constraints that specify which SysML stereotypes are applied to the L0 elements. The use of this compliance level is intended to provide more seamless integration with system modeling using SysML and to be able to fully leverage the capabilities of SysML in UPDM. UPDM L1 Performer OCL2.0 context Class inv: UPDM::Performer::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Post OCL2.0 context Class inv: UPDM::Post::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Condition OCL2.0 context DataType inv: UPDM::Condition::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) ExchangeElement OCL2.0 context DataType inv: UPDM::ExchangeElement::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) MeasureType OCL2.0 context DataType inv: UPDM::MeasureType::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) RoleType OCL2.0 context Class inv: UPDM::RoleType::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Materiel OCL2.0 context Class inv: UPDM::Materiel::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) HighLevelOperationalConcept OCL2.0 context Class inv: UPDM::HighLevelOperationalConcept::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) OperationalExchange OCL2.0 context InformationFlow inv: UPDM::OperationalExchange::allInstances()->exists(n|n.base_Class=self) implies SysML::ItemFlow::allInstances()->exists(b| b.base_Class = self) EntityItem OCL2.0 context Class inv: UPDM::EntityItem::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Energy OCL2.0 context Class inv: UPDM::Energy::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Climate OCL2.0 context DataType inv: UPDM::Climate::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) Organization OCL2.0 context Class inv: UPDM::Organization::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) PersonType OCL2.0 context Class inv: UPDM::PersonType::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) LightCondition OCL2.0 context DataType inv: UPDM::LightCondition::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) ExternalType OCL2.0 context Class inv: UPDM::ExternalType::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Responsibility OCL2.0 context Class inv: UPDM::Responsibility::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Environment OCL2.0 context DataType inv: UPDM::Environment::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) ResourcePort OCL2.0 context Port inv: UPDM::ResourcePort::allInstances()->exists(n|n.base_Class=self) implies SysML::FlowPort::allInstances()->exists(b| b.base_Class = self) System OCL2.0 context Class inv: UPDM::System::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) GeoPoliticalExtentType OCL2.0 context DataType inv: UPDM::GeoPoliticalExtentType::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) ResourceArtifact OCL2.0 context Class inv: UPDM::ResourceArtifact::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Capability OCL2.0 context Class inv: UPDM::Capability::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) CapabilityConfiguration OCL2.0 context Class inv: UPDM::CapabilityConfiguration::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) LocationType OCL2.0 context DataType inv: UPDM::LocationType::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) OrganizationType OCL2.0 context Class inv: UPDM::OrganizationType::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Control OCL2.0 context InformationFlow inv: UPDM::Control::allInstances()->exists(n|n.base_Class=self) implies SysML::ItemFlow::allInstances()->exists(b| b.base_Class = self) SecurityAttributesGroup OCL2.0 context DataType inv: UPDM::SecurityAttributesGroup::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) ServiceAccess OCL2.0 context Class inv: UPDM::ServiceAccess::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) ResourceInteraction OCL2.0 context InformationFlow inv: UPDM::ResourceInteraction::allInstances()->exists(n|n.base_Class=self) implies SysML::ItemFlow::allInstances()->exists(b| b.base_Class = self) PhysicalArchitecture OCL2.0 context Class inv: UPDM::PhysicalArchitecture::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) LogicalArchitecture OCL2.0 context Class inv: UPDM::LogicalArchitecture::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) Commands OCL2.0 context InformationFlow inv: UPDM::Commands::allInstances()->exists(n|n.base_Class=self) implies SysML::ItemFlow::allInstances()->exists(b| b.base_Class = self) MeasurementSet OCL2.0 context DataType inv: UPDM::MeasurementSet::allInstances()->exists(n|n.base_Class=self) implies SysML::ValueType::allInstances()->exists(b| b.base_Class = self) Software OCL2.0 context Class inv: UPDM::Software::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) SecurityDomain OCL2.0 context Class inv: UPDM::Node::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) EnterpriseGoal OCL2.0 context Class inv: UPDM::EnterpriseGoal::allInstances()->exists(n|n.base_Class=self) implies SysML::Requirement::allInstances()->exists(b| b.base_Class = self) NodePort OCL2.0 context Port inv: UPDM::NodePort::allInstances()->exists(n|n.base_Class=self) implies SysML::FlowPort::allInstances()->exists(b| b.base_Class = self) Node OCL2.0 context Class inv: UPDM::Node::allInstances()->exists(n|n.base_Class=self) implies SysML::Block::allInstances()->exists(b| b.base_Class = self) UPDM L0 contains all the Core, DoDAF and MODAF elements, and imports parts of SysML – Requirements and ModelElements namely. This compliance level is primarily based on UML and reuse of a minimum of SysML elements. This includes Requirements and Views/Viewpoints. As one of the core principles is reuse, cloning/recreating of these existing SysML structures was considered as inappropriate. UPDM L0 The SWAF section defines the design rules being used by the Swedish Armed Forces and NATO that aid in the development and implementation of information Integration. The design rule describes how military organizations can develop and implement the ability to exchange information with each other to support interoperability issues. Much of this design rule can also be applied when exchanging information with other actors than military organizations Definition of interoperability in this context: The ability of technical systems and/or organizations using technical systems to operate together by making (necessary) data & information and/or services produced by one system or organization available to the others, in an agreed formatmat SwAF Enumeration of development statuses, used to support the status tag of the DesignRule stereotype. DevelopmentStatus Indicates that the development of the design rule is in Identified state. Identified Indicates that the development of the design rule is in Draft state. Draft Indicates that the development of the design rule is in Proposal state. Proposal Indicates that the development of the design rule is in Verified state. Verified Indicates that the development of the design rule is in Rejected state. Rejected Indicates that the development of the design rule is in Obsolete state. Obsolete extension_DesignRule composite A design rule is a solution to a problem in a specific context with the following characteristics: -belongs to a problem domain, -packages knowledge in a reusable form, -standardize solutions to design problems within NBD, -gives value to the re-user. DesignRule DesignRule.ruleKind English Guidance version date identifier context problem * consequence analysis metaData principles * status solution * base_Constraint Elements that are not considered part of the Core architectural model, but necessary for DoDAF. DoDAF This section of the specification contains the Acquisition elements of the DoDAF section. AcquisitionElements extension_ProjectActivity composite UPDM: As in DoDAF DoDAF:A wholePart relationship between a Project and an Activity (Task) that is part of the Project. ActivityPartOfProject ActivityPartOfProject.supplier Value for the supplier property must be stereotyped <<ActualProject>>. ActivityPartOfProject.client Value for the client property must be stereotyped a specialization of <<ProjectActivity>>. base_Dependency DoDAF:A temporary endeavor undertaken to create Resources or Desired Effects. Project base_InstanceSpecification MOAF: NA DoDAF: An activity carried out during a project. ProjectActivity base_Activity extension_Project composite extension_ActivityPartOfProject composite This section of the specification contains the Technical Standard Elements of the DoDAF section. TechnicalStandardsElements extension_TechnicalStandard composite MODAF:NA DoDAF:Functional standards set forth rules, conditions, guidelines, and characteristics. FunctionalStandard base_Class extension_FunctionalStandard composite This section of the specification contains the Data elements of the DoDAF, Technical Standard Elements section. Data extension_SecurityAttributesGroup composite MODAF: Asserts that there is a relationship between two entities (Entity Relationship). DoDAF: A relationship or association between two elements of information. AssociationOfInformation base_Association MODAF:NA DoDAF:The group of Information Security Marking attributes in which the use of attributes 'classification' and 'ownerProducer' is required. This group is to be contrasted with group 'SecurityAttributesOptionGroup' in which use of those attributes is optional. SecurityAttributesGroup base_DataType extension_AssociationOfInformation composite MODAF: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 via the [constrainedItem] property of UML::Constraint (Standard). DoDAF:Technical standards document specific technical methodologies and practices to design and implement. TechnicalStandard base_Class The All View elements for DoDAF specific models. The All View elements provide information about the entire Architecture. They are used for support rather than architectural models. AllElements This section of the specification contains the Measurement Elements of the DoDAF, All Elements section. Measurements extension_Measure composite extension_MeasureType composite MODAF:NA DoDAF: A category of Measures. MeasureType base_DataType MODAF:NA DoDAF:The magnitude of some attribute of an individual. Measure base_InstanceSpecification This section of the specification contains the Environmental Elements of the DoDAF, All Elements section. Environment extension_GeoPoliticalExtent composite DoDAF: All subtypes of << IndividualType>> Location, such as Facility, Site, etc. Location base_InstanceSpecification MODAF: A definition of the conditions in which something exists or functions. An Environment may be specified in terms of LocationType (e.g. terrain), Climate (e.g. tropical), and LightCondition (e.g. dark, light, dusk, etc.) DoDAF: An object that encompasses meteorological, geographic, and control features mission significance.. Condition Any property of the Environment that has influence on the Enterprise. Condition.ownedAttribute English Values for the ownedAttribute property must be stereotyped <<ConditionProperty>> or its specializations. String defining the type of condition being set. conditionKind base_DataType MODAF:NA DoDAF:A geospatial extent whose boundaries are by declaration or agreement by political parties. GeoPoliticalExtentType base_DataType Enumeration of kinds GeopoliticalExtentTypes. geoPoliticalExtentTypeKind String defining custom kinds of GeopoliticalExtentTypes. customKind extension_GeoPoliticalExtent composite Enumeration of kinds of geopolitical extent type, derived from DoDAF, used to support the geoPoliticalExtentTypeKind tag of the GeopoliticalExtentType stereotype.. GeoPoliticalExtentTypeKind Powertype Of Installation. InstallationType Other GeoPoliticalExtentType kind that is not on the enumerated list. OtherType Powertype Of GeoFeature. GeoFeatureType Powertype Of RegionOfCountry. RegionOfCountryType Powertype Of Country. CountryType Powertype Of RegionOfWorld. RegionOfWorldType Powertype Of Facility. FacilityType Powertype Of Site. SiteType extension_Condition composite extension_Location composite extension_EnvironmentProperty composite MODAF: EnvironmentalProperty: Asserts that an Environment has one or more properties. These may be Climate, LocationType, or LightCondition. DoDAF: NA ConditionProperty ConditionProperty.class Value for the class property must be stereotyped <<Condition>> or its specializations. base_Property UPDM: An instance of a GeoPoliticalExtentType MODAF:N/A DoDAF: N/A GeoPoliticalExtent GeoPoliticalExtent.classifier Classifier property value must be stereotyped <<GeoPoliticalExtentType>> or its specializations. base_InstanceSpecification Enumeration of kinds of GeopoliticalExtent. geoPoliticalExtentKind String defining custom kinds of geopolitical extent. customKind Enumeration of geopolitical extent kinds, used to support the geoPoliticalExtentKind tag of the geoPoliticalExtent stereotype, derived from DoDAF. GeoPoliticalExtentKind A base, camp, post, station, yard, center, or other activity, including leased facilities, without regard to the duration of operational control. An installation may include one or more sites. Installation Other GeoPoliticalExtent kind that is not on the enumerated list. Other An object that encompasses meteorological, geographic, and control features mission significance. GeoFeature A large, usually continuous segment of a political state or nation or its territory. RegionOfCountry A political state or nation or its territory. Country A large, usually continuous segment of a surface or space; area. RegionOfWorld A real property entity consisting of underlying land and one or more of the following: a building, a structure (including linear structures), a utility system, or pavement. Facility Physical (geographic) location that is or was owned by, leased to, or otherwise possessed. Each site is assigned to a single installation. A site may exist in one of three forms: (1) Land only, where there are no facilities present and where the land consists of either a single land parcel or two or more contiguous land parcels. (2) Facility or facilities only, where the underlying land is neither owned nor controlled by the government. A stand-alone facility can be a site. If a facility is not a stand-alone facility, it must be assigned to a site. (3). Land and all the facilities thereon, where the land consists of either a single land parcel or two or more contiguous land parcels. Site extension_ composite Enumeration of kinds of information, derived from MODAF and DoDAF, used to support the InformationKind tag of the Information stereotype. InformationKind An arbitrary set of axes with reference to which the position or motion of something is described or physical laws are formulated. PositionReferenceFrame Information describing pedigree. PedigreeInformation Representation of information in a formalized manner suitable for communication, interpretation, or processing by humans or by automatic means. Examples could be whole models, packages, entities, attributes, classes, domain values, enumeration values, records, tables, rows, columns, and fields. Data Information is the state of a something of interest that is materialized -- in any medium or form -- and communicated or received. Information Types of information within the scope or domain of the architecture. DomainInformation This section of the specification contains the Behavior Elements of the DoDAF, All Elements section. Behavior UPDM: Links a Performer to the behavior that it can perform MODAF: NA DoDAF:An overlap of an Activity with a Resource, in particular a consuming or producing Activity that expresses an input, output, consumption, or production Activity of the Resourcee ActivityPerformedByPerformer base_Dependency extension_ActivityPerformedByPerformer composite UPDM:As DoDAF MODAF:N/A DoDAF:Information is the state of a something of interest that is materialized -- in any medium or form -- and communicated or received. Information Information.annotatedElement Value for the annotatedElement property must be stereotyped <<UPDMElement>> or its specializations. base_Comment Enumeration of the kinds of information being passed. informationKind The System View elements for DoDAF specific models. SystemElements Defines the structure parts of the system elements. Structure A DoDAF alias for ResourceArtifact. System base_Class extension_System composite The Operaional View elements for DoDAF specific models. OperationalElements Section of the OperationalElements profile that describe stuctural concepts for DoDAF. Structure extension_OperationalNode composite MODAF:NA DoDAF:Any entity - human, automated, or any aggregation of human and/or automated - that performs an activity and provides a capability. An alias for Node in DoDAF. Performer base_Class This section of the specification contains the organizational Elements of the DoDAF, Operational Elements section. Organizational extension_PersonType composite UPDM:Alias for ProvidesCompetence, the tuple showing the skills and competencies required from a particular role or organization DoDAF:A type property between a PersonRoleType and the Skills it entails SkillOfPersonType base_Dependency MODAF:A specific set of abilities defined by knowledge, skills and attitude (Competence). DoDAF:The ability, coming from one's knowledge, practice, aptitude, etc., to do something well. Skill base_Class extension_SkillOfPersonType composite UPDM: An individual person. MODAF:NA DoDAF: An Individual person. IndividualPersonRole base_InstanceSpecification DoDAF:A category of persons defined by the role or roles they share that are relevant to an architecture. Includes assigned materiel. MODAF:NANA PersonType base_Class extension_OrganizationType composite extension_IndividualPerson composite extension_Skill composite DoDAF:A type of Organization. OrganizationType base_Class This section of the specification contains the Service Elements of the DoDAF section. ServiceElements extension_ServiceAccess composite UPDM: The mechanism by which a service is accessed MODAF: NA DoDAF: NA ServiceAccess base_Class UPDM: Package containing the elements that describe a service, from DoDAF 2. DoDAF:Information necessary to interact with the service in such terms as the service inputs, outputs, and associated semantics. The service description also conveys what is accomplished when the service is invoked and the conditions for using the service. ServiceDescription base_Package extension_ServiceDescription composite This section of the specification contains the Strategic Elements of the DoDAF section. StrategicElements UPDM: As in DoDAF DoDAF: A disposition to manifest an Activity. An Activity to be performed to achieve a desired effect under specified [performance] standards and conditions through combinations of ways and means. ActivityPartOfCapability base_Dependency UPDM:A couple that represents the capability that a resource, node or enterprise phase exhibits (Exhibits). MODAF:An assertion that a Node is required to have a Capability (Capability for node). DoDAF: A couple that represents the capability that a performer has. CapabilityOfPerformer base_Dependency extension_CapabilityOfPerformer composite MODAF:The overall aims of an enterprise over a given period of time. (EnterpriseVision) DoDAF:An end that describes the future state of the enterprise, without regard to how it is to be achieved; a mental image of what the future will or could be like. Vision base_Class extension_Vision composite MODAF:NA DoDAF:A desired state of a Resource. DesiredEffect DesiredEffect.supplier Value for the supplier property must be stereotyped a specialization of <<DesiredState>>. DesiredEffect.client Value for the client property must be stereotyped a specialization of <<Desirer>>. base_Dependency Measures of the DesiredEffect. providedMOE extension_PartOfCapability composite extension_DesiredEffect composite Elements that are not considered part of the Core architectural model, but necessary for MoDAF. MODAF The Acquisition View elements for MoDAF specific models. AcquisitionElements Structure for Acquisition View elements for MoDAF specific models. Structure MODAF:An aspect by which the progress of various Projects may be measured. In UK MOD, this could be one of the defence lines of development (DLOD), or DOTMLPF in the US. DoDAF: NA ProjectTheme ProjecTheme.type Value for the type property must be stereotyped <<StatusIndicators>> or its specializations. base_Property extension_ProjectThemeStatus composite extension_ProjectStatus composite extension_ProjectTheme composite UPDM: Specifies a status for a ProjectTheme (such as training status). MODAF: An enumeration of the possible statuses (MODAF::StatusIndicator) for one of more ProjectThemes. StatusIndicators base_Enumeration MODAF: A ProjectStatus (MODAF::StatusAtMilestone) is a relationship between a Status and a milestone that asserts the status (i.e. level of progress) of a ProjectTheme for the project at the time of the ActualProjectMilestone (MODAF::Milestone). DoDAF: NA ProjectStatus ProjectStatus.definingFeature DefiningFeature value must be stereotyped <<ProjectTheme>> or its specializations. base_Slot Milestones are an event in a Project by which progress is measured. Milestones MODAF:A type of OrganisationProjectRelationship where the organisation is the party responsible for the project. ProjectOwnership base_Dependency extension_ProjectOwnership composite extension_ProjectMilestoneType composite extension_ProjectMilestone composite MODAF: A MilestoneSequence (MODAF::MilestoneRelationship) is a relationship between two milestones. DoDAF: NA MilestoneSequence MilestoneSequence.supplier Supplier must be <<ProjectMilestone>>. MilestoneSequence.client Client must be <<ProjectMilestone>>. base_Dependency MODAF: An OutOfServiceMilestone (MODAF::OutOfService) is a ProjectMilestone that indicates a project's deliverable is to go out of service. DoDAF: NA OutOfServiceMilestone base_InstanceSpecification MODAF: (ProjectMilestone): An event in a ActualProject (MODAF::Project) by which progress is measured. Note: in the case of an acquisition project, there are two key types of milestones which shall be represented using subtypes - IncrementMilestone (MODAF::CapabilityIncrement) and OutOfServiceMilestone (MODAF::OutOfService) DoDAF: NAA ActualProjectMilestone ActualProjectMilestone.slot Slot values have to be stereotyped <<ProjectStatus>> or its specializations. ActualProjectMilestone.classifier Value for the classifier property must be stereotyped <<ProjectMilestone>> or its specializations. Defines time for this ProjectMilestone. date base_InstanceSpecification Description of the ActualProjectMilestone. description Affected resource. resource * extension_MilestoneSequence composite extension_OutOfServiceMilestone composite UPDM: An element representing a collection of themes (e.g. DLOD or DOTMLPF) which is connected to a Project as part of a Project’s definition. This is used as a template for ActualProjectMilestones. MODAF: An event in a Project by which progress is measured.. ProjectMilestone ProjectMilestone.ownedAttributes Owned attributes have to be stereotyped <<ProjectTheme>>. ProjectMilestone.ownedThemes All of the ProjectThemes, owned by a ProjectMilestone, must be typed by the same StatusIndicators. base_Class extension_CapabilityIncrementMilestone composite MODAF: (MODAF::CapabilityIncrement): An ActualProjectMilestone (MODAF::ProjectMilestone) that indicates the point in time at which a project is predicted to deliver or has delivered a Capability. DoDAF: NA IncrementMilestone base_InstanceSpecification MODAF: Asserts that one ActualProject (MODAF::Project) follows from another - i.e. the target ActualProject cannot start until the source ActualProject has ended. DoDAF: NA ProjectSequence ProjectSequence.client Client property value must be stereotyped <<ActualProject>> or its specializations. ProjectSequence.supplier Supplier property value must be stereotyped <<ActualProject>> or its specializations. base_Dependency extension_ProjectSequence composite The All View elements for MoDAF specific models. AllElements This section of the specification contains the Environment elements of the MODAF,All Elements section. Environment extension_Climate composite MODAF:A type of weather condition, or combination of weather conditions (e.g. high temperature & dry). DoDAF: NA Climate base_DataType extension_LightCondition composite MODAF: a specification of environmental lighting conditions. LightCondition base_DataType Ontology elements from All Elements. Ontology MODAF: A reference to an element in a recognized external ontology or taxonomy. DoDAF:NA OntologyReference Unique identifier for the element. url true extension_ExternalType composite extension_ExternalIndividual composite MODAF: An individual (i.e. something which has spatial and temporal extent) defined by an external ontology. DoDAF: NAA ExternalIndividual base_InstanceSpecification extension_Overlap composite MODAF: A definition of an element in the architecture. DoDAF:NAA Definition Definition.annotatedElement Value for the annotatedElement property must be stereotyped <<UPDMElement>> or its specializations. The original or current person (architect) responsible for the element. author * base_Comment A UPDM Artifact used to define an alternative name for an element as used by DoDAF or MODAF. Alias Allias.annotatedElement Value for the annotatedElement property must be stereotyped <<UPDMElement>> or its specializations. The person or organization that uses this alternative name. nameOwner * base_Comment IDEAS:A couple of wholePart couples where the part in each couple is the same. Overlap Overlap.client Values for the client property must be stereotyped <<UPDMElement>> or its specializations. Overlap.supplier Values for the supplier property must be stereotyped <<Element>> or its specializations. base_Dependency UPDM: An TupleType defined in an external Ontology. MODAF:NA DoDAF:NA ExternalTupleType base_Class MODAF: Asserts that two elements refer to the same real-world thing. DoDAF: NAA SameAs SameAs.supplier Values for the supplier property must be stereotyped <<Element>> or its specializations. SameAs.client Values for the client property must be stereotyped <<UPDMElement>> or its specializations. base_Dependency MODAF: Defines an additional stereotype used in the architecture which is not defined in this meta-model. The body attribute contains the name of the new stereotype. The extendedStereotype tagged value shall contain the name of the meta-model stereotype which is extended. The ontologyReference tagged value shall be populated with a reference to the external ontology element represented by the new stereotype. DoDAF: NA StereotypeExtension StereotypeExtension.annotatedElement Values for the annotatedElement property must be stereotyped <<UPDMElement>> or its specializations. base_Comment Ontologicalrefecence associated with an Stereotype extension. ontologyReference * extension_ExternalTupleType composite extension_Alias composite extension_ composite extension_ExternalTuple composite extension_Definition composite MODAF: A type defined by an external ontology. DoDAF: NA ExternalType base_Class extension_ composite UPDM: An instance of ExternalTupleType defined in an external Ontology. MODAF:NA DoDAF:NA ExternalTuple base_Class The Operaional View elements for MoDAF specific models. OperationalElements Structure for Operaional View elements for MoDAF specific models. Structure This section of the specification contains the organizational Elements of the MODAF, Operational Elements section. Organizational extension_RoleType composite MODAF: An aspect of a person or organization that enables them to fulfill a particular function. RoleType base_Class MODAF:Asserts that the trustingParty (either a Node or a KnownResource) trusts the trustedParty to a given level (indicated by the level attribute). Note: No unit of measure is associated with the level - security architects muist define their own scale of trust levels for a given architecture or set of architectures. DoDAF:NAA Trustline Trustline.supplier Values for the supplier property must be stereotyped <<Node>> or its specializations. Trustline.client Values for the client property must be stereotyped <<Node>> or its specializations. base_Dependency String denoting the level of Trust in the information source. level extension_TradeSpace composite MODAF: The boundary containing those Nodes which may be realised by functional resources specified in SV-1. There may be more than one alternative solution for a given ProblemDomain specified as a set of SV suites. There may be only one ProblemDomain in a LogicalArchitecture. DoDAF: NA – covered by the more general temporalWholePart element. ProblemDomain ProblemDomain.class Value for the class property must be stereotyped <<LogicalArchitecture>> or its specializations. ProblemDomain.type Value for the type property must be stereotyped <<Node>> or its specializations. base_Property UPDM: Energy to be exchanged between Nodes. MODAF: A unit of energy that flows along an EnergyFLow or OperationalActivityEnergyFlow DoDAF: NA Energy base_Class extension_Trustline composite extension_Energy composite Behavior for Operaional View elements for MoDAF specific models. Behavior MODAF: An OperationalActivity that is a standard procedure that is doctrinal . Note: This is equivalent to what some defence organisations call JETLs. DoDAF: Work, not specific to a single organization, weapon system or individual, that transforms inputs into outputs or changes their state (DoDAF:: Activity). StandardOperationalActivity base_Activity UPDM:Asserts that an ActualOrganizationalResource owns a Process. OwnsProcess OwnsProcess.supplier Value for the supplier property must be stereotyped a specialization of <<Process>>. OwnsProcess.client Value for the client property must be stereotyped <<ActualOrganizationalResource>> or its specializations. base_Dependency MODAF:The abstract supertype of OperationalActivity and EnduringTask. DoDAF:NA Process base_Activity true extension_OwnsProcess composite extension_StandardOperationalActivity composite MODAF: Anything that is acted upon by an OperationalActivity DoDAF: NA ActivitySubject OperationalActivities that this ActivitySubject is acting upon. actsUpon * true true extension_Process composite Flows for Operaional View elements for MoDAF specific models. Flows MODAF: A type of ResourceInteraction where one Resource (source) controls another (target). --Examples - the driver of a tank, one organisation having operational control of another, a fire control system controlling a weapons system. DoDAF: NA Control Control.informationTarget Value for the informationTarget property must be stereotyped <<ResourceArtifact>> or its specializations. Control.conveyed Value for the conveyed property must be stereotyped <<ExchangeElement>> or its specializations. Control.informationSource Value for the informationSource property must be stereotyped <<OrganizationalResource>> or its specializations. base_InformationFlow extension_Control composite The Strategic View elements for MoDAF specific models. StrategicElements Milestone elements for Strategic View elements for MoDAF specific models. Milestones MODAF: Asserts that an ActualOrganisationResource ceased to use or is slated to cease using a CapabilityConfiguration from a specific point in time. --This is used to describe capabilities going out of service with specific organisations or posts. DoDAF:NA NoLongerUsedMilestone ActualOrganizationalResources that are no longer using CapabilityConfiguration that went out of service at this Milestone. noLongerUsedBy * base_InstanceSpecification MODAF: Asserts that an ActualOrganisationResource started to use, or is slated to start using a CapabilityConfiguration from a specific point in time. --This is used to describe capabilities going into service with specific organisations or posts. DoDAF: NA DeployedMilestone ActualOrganizationalResources using CapabilityConfiguration deployed at this Milestone. usedBy * base_InstanceSpecification extension_ConfigurationNoLongerUsed composite extension_ConfigurationDeployed composite Structure elements for Strategic View elements for MoDAF specific models. Structure MODAF: A type of behaviour recognised by an enterprise as being essential to achieving its goals - i.e. a strategic specification of what the enterprise does. DoDAF: NA EnduringTask base_Activity extension_Enterprise composite UPDM: A WholeLifeEnterprise is a purposeful endeavor of any size involving people, organizations and supporting systems (including physical systems and/or processes). MODAF: An EnterprisePhase that represents the whole existance of an enterprise. DoDAF: NA WholeLifeEnterprise base_Class extension_EnduringTask composite This section of the specification contains the Technical Standard Elements of the MODAF section. TechnicalStandardsElements MODAF: Asserts that a Protocol (upperLayer) uses another Protocol (lowerLayer) ProtocolLayer ProtocolLayer.class Value for the class property must be stereotyped <<Protocol>> or its specializations. ProtocolLayer.type Value for the type property must be stereotyped <<Protocol>> or its specializations. base_Property extension_ProtocolLayer composite The Core contains most of the elements of UPDM profile. These elements are common to both DoDAF and MoDAF or are critical to a complete model of core concepts. The Core is always associated with either the DoDAF or MoDAF profiles. If desired, there is no prohobition of using both MoDAF, DoDAF and Core should the end-user desire to use some or all of the concepts represented. d. Core * Section 1.4.4 of the DoDAF version 1.5 Definitions and Guidelines (Volume I) Define the purpose of the Technical View as follows: "The TV is the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements. Its purpose is to ensure that a system satisfies a specified set of operational requirements. The TV provides the technical systems implementation guidelines upon which engineering specifications are based, common building blocks are established, and product lines are developed. It includes a collection of the technical standards, implementation conventions, standards options, rules, and criteria that can be organized into profile(s) that govern systems and system or service elements for a given architecture." TechnicalStandardsElements MODAF: 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 via the [constrainedItem] property of UML::Constraint. DoDAF: A formal agreement documenting generally accepted specifications or criteria for products, processes, procedures, policies, systems, and/or personnel. Standard The information technology standard category which the <<Standard>> belongs to. InformationTechnologyStandardCategory * base_Class Organization that ratified this Standard. ratifiedBy * The date when this version of the Standard was published. mandatedDate The date when this version of the Standard was retired. retiredDate Short name of the Standard. shortName Represents the revision number of the Standard - e.g. "1.2.1", "v2", ":2004", etc. version Current status of the Standard. currentStatus MODAF: A UML::Comment that when attached to a CapabilityConfiguration indicates that it is a standard pattern for re-use in the architecture. DoDAF: NA StandardConfiguration StandardConfiguration.annotatedElement Value for the annotatedElement property must be stereotyped <<CapabilityConfiguration>>. base_Comment extension_Protocol composite extension_Standard composite UPDM: Abstract element: A connector that implements a specific Protocol. MODAF: An element that can implement a Protocol. ProtocolImplementation The <<Protocol>> which can be implemented by the Connector targets. implements true extension_StandardsConfiguration composite The data portion of the AllElements profile. Data MODAF: Asserts that there is a relationship between two EntityItems. DoDAF: (DoDAF::DataAssociation): A relationship or association between two elements of proceduralized information. EntityRelationship EntityRelationship.endType Values for the endType property must be stereotyped <<EntityItem>> or its specializations. base_Association MODAF: A defined property of an EntityItem. DoDAF: NAA EntityAttribute EntityAttribute.canBeAppliedTo <<EntityAttribute>> stereotype can be applied to Properties that are owned only by <<EntityItem>> base_Property extension_Details composite MODAF: (MODAF::Entity): A definition (type) of an item of interest. DoDAF: NA EntityItem EntityItem.ownedAttribute Value for the ownedAttribute property must be stereotyped <<EntityAttribute>> or its specializations. base_Class extension_Attribute composite UPDM: A tuple used to provide the relationship between an entityItem and an ExchangeElement. Details Details.supplier Value for the supplier property must be stereotyped <<ExchangeElement>>. Details.client Value for the client property must be stereotyped a specialization of <<EntityItem>>. base_Dependency extension_EntityRelationshio composite MODAF: A Standard for communication. Protocols may be composite (i.e. a stack). DoDAF: NA, See TechnicalStandard. Protocol base_Class Models in the System Viewpoint represent alternate realizations in terms of equipment capability of the operational capabilities expressed through models in the Operational Viewpoint and in the User Requirements. The System Viewpoint primarily addresses the specification of the system capability needed (rather than implementation details). Significant changes originally made in MODAF improved the ability for modelers to represent configuration of capability that include people as well as systems and platforms SystemsElements The Structure section of the SystemsElements profile. Structure MODAF:Asserts that a CapabilityConfiguration is a version of a WholeLifeConfiguration. DoDAF:NA VersionOfConfiguration VersionOfConfiguration.class Value for the class property must be stereotyped <<WholeLifeConfiguration>> or its specializations. VersionOfConfiguration.type Value for the type property must be stereotyped <<SystemResource>> or its specializations. base_Property UPDM: ResourceInterface is a contractual agreement between two resources that implement protocols through which the source resource to the destination resource. MODAF: NA DoDAF: An overlap between Performers for the purpose of producing a Resource that is consumed by the other (DoDAF:: Interface). ResourceInterface ResourceInterface.end English the value for the role property for the owned ConnectorEnd must be stereotype <<ResourceRole>> or its specializations. base_Connector Realizing ResourceConnectors. realizingConnector * extension_CapabilityConfiguration composite extension_WholeLifeConfiguration composite MODAF: Abstract. Anything that may be constrained by a ResourceConstraint. SubjectOfResourceConstraint true MODAF: A rule governing the structural or functional aspects of an implementation - this may also include constraints on OrganisationalResources that are part of an implementation. DoDAF: The range of permissible states for an object (DoDAF::Constraint).. ResourceConstraint ResourceConstraint.constrainedElement Value for the constrainedElement property must be stereotyped <<SubjectOfResourceConstraint>> or its specializations. base_Constraint extension_ResourceInterface composite UPDM: Abstract element used as placeholder for resource properties. SystemResource Resource.ownedPort Values for the ownedPort property must be stereotyped with <<ServicePort>> or its specializations. Resource.performs Can perform only <<Functions>>. Resource.ownedOperation Values for the ownedOperation property must be stereotyped with <<ResourceOperation>> or its specializations. base_Class A Linked milestone. milestone * true extension_ResourceInterface composite extension_PhysicalArchitecture composite extension_Artifact composite MODAF: An actual, fully-realised capability. A FieldedCapability must indicate its configuration CapabilityConfiguration. DoDAF: NA FieldedCapability FieldedCapability.classifier Value for the classifier property must be stereotyped <<CapabilityConfiguration>> or its specializations. base_InstanceSpecification extension_VersionOfConfiguration composite extension_FieldedCapability composite extension_Port composite extension_Forecast composite UPDM: A combination of physical element, energy, and data that are combined used to accomplish a task or function. MODAF: A type of man-made object. Examples are "car", "radio", "fuel", etc. (MODAF:: Artefact). ResourceArtifact base_Class MODAF: An executable computer programme. DoDAF: Materiel: Equipment, apparatus or supplies that are of interest, without distinction as to its application for administrative or combat purposes. Software base_Class MODAF: A statement about the future state of one or more types of system or standard. DoDAF: NA Forecast Forecast.supplier Value for the supplier property must be stereotyped <<SubjectOfForecast>> or its specializations. Forecast.pair The client and supplier must be stereotyped by the same specialization of <<SubjectOfForecast>> (e.g. <<Software>> to <<Software>>, <<Standard>> to <<Standard>>, etc). Forecast.client Value for the client property must be stereotyped <<SubjectOfForecast>> or its specializations. Start date of the forecast. startDate base_Dependency End date of the forecast endDate MODAF: Artifact, A type of man-made object. Examples are "car", "radio", "diesel", etc. DoDAF: Equipment, apparatus or supplies that are of interest, without distinction as to its application for administrative or combat purposes. Materiel base_Class UPDM: Port is an interaction point for a resource through which it can interact with the outside environment. MODAF: An interface (logical or physical) provided by a System. A SystemPort may implement a PortType though there is no requirement for SystemPorts to be typed (MODAF:: SystemPort). DoDAF: An interface (logical or physical) provided by a System (DoDAF::Port).. ResourcePort ResourcePort.type Value for the type property must be stereotyped <<ResourceInteractionItem>> or its specializations. base_Port extension_Material composite MODAF:A set of versions of a CapabilityConfiguration over time. DoDAF:NA WholeLifeConfiguration base_Class extension_ResourceConstraint composite extension_SystemResource composite extension_Resource composite MODAF:A configuration of Resources for a purpose. DoDAF:NA PhysicalArchitecture base_Class Enumeration of the roles that a ResourceRole may play in the context of a CapabilityConfiguration or System, derived from MODAF, used to support the MODAFRoleKind tag of a ResourceRole MODAFRoleKind Usage of a ResourceArtifact as a part of another ResourceArtifact. Part (MODAF SoftwareComponent) Asserts that Software is a component of another Software. Component The usage of a PhysicalArchitecture in another PhysicalArchitecture. Used Configuration The role of an OrganizationalResource in a PhysicalArchitecture. Human Resource Usage of a ResourceArtifact as a platform (e.g. vessel, aircraft, etc.) in a particular PhysicalArchitecture. Platform The usage of a ResourceArtifact as a System in a PhysicalArchitecture. System Asserts that one OrganizationType is typically the parent of another - e.g. a squadron may be part of a batallion. Sub Organization (MODAF Post) Asserts that a Post exists in an OrganizationType of the type specified by the related PostType. Post Role (MODAF Role) A ResourceUsage that asserts a given PostType has a RoleType. Responsibility Role A ResourceUsage that asserts a given ServiceAccess is used in the context of a particular service usage. Service Access Role UPDM: Equipment is a physical resource that is used to accomplish a task or function in a system or an environment. MODAF: (MODAF::PhysicalAsset): Usage of an ResourceArtifact (MODAF::Artefact) as a component of a ResourceConfiguration. DoDAF: NA Equipment UPDM: Indicates that a (sub)system is part of another system. MODAF: Usage of an Artefact (UPDM::ResourceArtifact) as a part of another Artefact (UPDM::ResourceArtifact), equates to a MODAF::Part DoDAF: NA Sub System Part Asserts that Software is hosted on a ResourceArtifact (which means the artifact is some kind of computer system). Hosted Software Other MODAF Role kind that is not on the enumerated list. Other UPDM: Abstract supertype for physical resources such as OrganizationalResource. MODAF: A PhysicalAsset, OrganisationalResource or FunctionalResource that can contribute towards fulfilling a capability (MODAF::ResourceType). PhysicalResource base_Class true extension_PhysicalResourceRole composite MODAF: A composite structure representing the physical and human resources (and their interactions) in an enterprise.--A CapabilityConfiguration is a set of artefacts or an organisation configured to provide a capability, and should be guided by [doctrine] which may take the form of Standard or OperationalConstraint stereotypes. DoDAF: Any entity - human, automated, or any aggregation of human and/or automated - that performs an activity and provides a capability (Performer). CapabilityConfiguration Represents the doctrinal line of development of the capability. doctrine * base_Class extension_Software composite UPDM: A physical connection between two resources that implements protocols through which the source resource can transmit items to the destination resource. MODAF: Asserts that a connection exists between two ports belonging to parts in a system composite structure model (MODAF::SystemPortConnector). DoDAF: NA ResourceConnector ResourceConnector.end English The value for the role property for the owned ConnectorEnd must be stereotype <<ResourcePort>> or its specializations. base_Connector Realized ResourceInterfaces. realizedInterface * A list of ResourceInteractions (or specializations) that realized by the ResourceInterface/ResourceConnector. This is derived by navigating from the ResourceInteraction to the ResourceInterfaces/ResourceConnectors using the inverse of the realization/realizingConnector roles.. realizedExchange * UPDM: abstract element. ResourceRole ResouceRole.type An element with the stereotype <<ResourceRole>> applied must have the <<SystemResource>> stereotype (or its specializations) applied to the targets of its extended metaclass property "type". ResourceRole.class Value for the class property must be stereotyped <<SystemResource>> or its specializations. Functions used by the ResourceRole. performsInContext * Enumeration of the kinds of role a resource can play. MODAFRoleKind base_Property MODAF: Abstract Any element that may be subject to a Forecast SubjectOfForecast true The Flows section of the SystemsElements profile. Flows UPDM: ResourceInteraction represents data that is exchanged between the resources MODAF: An assertion that two FunctionalResources interact. Examples : data exchange between systems, conversations between people, people using systems. DoDAF: NA ResourceInteraction ResourceInteraction.realization Value for the realization property must be stereotyped <<ResourceInterface>>, <<ActualOrganizationRelationship>>, or their specializations. ResourceInteraction.conveyedElement Value for the conveyedElement property must be stereotyped <<ResourceInteractionItem>> or its specializations. ResourceInteraction.informationTarget Value for the informationTarget property must be stereotyped <<SystemResource>> or its specializations. ResourceInteraction.realizingConnector Value for the realizingConnector property must be stereotyped <<ResourceInterface>>, <<ResourceConnector>>, <<ServiceChannel>> or their specializations. ResourceInteraction.realizingActivityEdge Value for the realizingActivityEdge property must be stereotyped <<FunctionEdge>> or its specializations. ResourceInteraction.informationSource Value for the informationSource property must be stereotyped <<SystemResource>> or its specializations. base_InformationFlow extension_ResourceInteraction composite UPDM Abstract: Represents the item(s) exchanged between the resources through a ResourceInteraction. MODAF: Formalised representation of data which is managed by or exchanged between systems (MODAF::DataElement). DoDAF: Representation of information in a formalized manner suitable for communication, interpretation, or processing by humans or by automatic means (DoDAF::Data). ResourceInteractionItem The Functions affected by the ResourceInteractionItem. affectedFunctions * true true The Data section of the SystemsElements profile. Data MODAF: A structural specification of data, showing classifications of data elements and relationships between them. DoDAF: NA DataModel DataModel.ownedElement All classifiers owned by DataModel must be stereotyped <<EntityItem>>. true extension_InternalDataModel composite MODAF: A PhysicalDataModel is an implementable specification of a data structure. A PhysicalDataModel realises a LogicalDataModel, taking into account implementation restrictions and performance issues whilst still enforcing the constraints, relationships and typing of the logical model. DoDAF: A Physical Data Model defines the structure of the various kinds of system or service data that are utilized by the systems or services in the Architecture.. PhysicalDataModel base_Package The Behavior section of the SystemsElements profile. Behavior UPDM Artifact that extends a UML StateMachine allied to Resources. ResourceStateMachine ResourceStateMachine.owner Values for the owner property must be stereotyped with <<SystemResource>> or its specializations. ResourceStateMachine.region.state English Values for the region.state property must be stereotyped with <<ResourceState>> or its specializations. base_StateMachine extension_SystemsMessage composite extension_ResourceOperation composite extension_Function composite UPDM: An extension of <<ActivityEdge>> that is used to model the flow of control/objects through a Function. MODAF: A FunctionEdge (MODAF::FunctionFlow) is a UML::ObjectFlow between Functions. NOTE: this has been extended in UPDM to additionally include UML::ControlFlows.s. FunctionEdge FunctionEdge.owner <<FunctionEdge>> must be owned directly or indirectly by <<Function>>. base_ActivityEdge The ResourceInteractionItem that is conveyed. carriedItem * true MODAF: An activity which is specified in context of the resource (human or machine) that performs it. DoDAF: Activity: Work, not specific to a single organization, weapon system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state. Function Function.ownedParameter The values for the ownedParameter property must be stereotyped <<ResourceParameter>>. The ResourceInteractionItem that is the subject of the Function. subject * true base_Activity Relationship between an Function and a ResourceOperation. realizedBy * extension_FunctionEdge composite extension_ResourceEventTrace composite extension_FunctionParameter composite extension_ResourceState composite UPDM: A UPDM artifact that extends a UML Interaction. ResourceEventTrace ResourceEventTrace.owner Values for the owner property must be stereotyped with <<Resource>> or its specializations. ResourceEventTrace.message Values for the message property must be stereotyped with <<ResourceMessage>> or its specializations. base_Interaction UPDM: Represents inputs and outputs of Function. It is typed by ResourceInteractionItem. ResourceParameter ResourceParameter.type Value for the type property must be stereotyped with specialization of <<ResourceInteractionItem>>. base_Parameter UPDM: State identified in the context of an ResourceStateDescription. MODAF:N/A DoDAF:N/A ResourceState base_State UPDM:A partial or full realization of Function. MODAF:NA DoDAF:NA ResourceOperation ResourceOperation.ownedParameter The values for the ownedParameter property must be stereotyped <<ResourceParameter>>. base_Operation Relationship between a ResourceOperation and a Function. realizes extension_SystemsStateMachine composite UPDM Artifact: The FunctionAction is defined as a call behavior action that invokes the function that needs to be performed. --This concept is required for mapping the architecture with UML and does not have a DoDAF or MoDAF equivalent. FunctionAction FunctionAction.behavior Value for the behavior property must be stereotyped <<Function>>. FunctionAction.activity Value for the activity property must be stereotyped <<Function>>. base_CallBehaviorAction UPDM: Message for use in a Resource Event-Trace, implements a ResourceInteraction. MODAF: A specification of the interactions between aspects of a Resources architecture (MODAF::ResourceInteractionSpecification). DoDAF: An overlap of an Activity with a Resource, in particular a consuming or producing Activity that expresses an input, output, consumption, or production Activity of the Resource (DoDAF:: activityResourceOverlap). . ResourceMessage ResourceMessage.receiveEvent.event.operation English Values for the receiveEvent.event.operation property must be stereotyped with <<ResourceOperation>> or its specializations. base_Message Carried ResourceInteraction carries * true The ResourceOperation associated with a ResourceMessage. operation true extension_FunctionAction composite * The AcquisitionElements describe project details, including dependencies between projects and capability integration. These Views guide the acquisition and fielding processes. AcquisitionElements Milestone elements from the acquisition section of the profile. Milestone extension_ProjectType composite MODAF:A relationship between an ActualOrganisation and a Project. OrganizationalProjectRelationship OrganizationalProjectRelationship.client Value for the client property must be stereotyped <<ActualProject>> or its specializations. OrganizationalProjectRelationship.supplier English Value for the supplier property must be stereotyped a specialization of <<ActualOrganizationalResource>>. base_Dependency extension_Project composite extension_ProjectRole composite MODAF: (MODAF::Project): A time-limited endeavour to create a specific set of products or services. DoDAF: (DoDAF::Project): A temporary endeavor undertaken to create Resources or Desired Effects. ActualProject ActualProject.classifier Classifier property value must be stereotyped <<Project>> or its specializations. End time for this Project. endDate Start time for this Project. startDate Sub-projects. part * Parent project. whole Milestones associates with this project. ownedMilestones * true base_InstanceSpecification extension_OrganizationProjectRelationship composite UPDM: The role played by a ProjectMilestone in the context of an ActualProjectMilestone MODAF: NA DoDAF: NA ProjectMilestoneRole ProjectMilestoneRole.type Value for the type property must be stereotyped <<ProjectMilestone>> or its specializations. ProjectMilestoneRole.class Value for the class property must be stereotyped <<Project>> or its specializations. base_Property UPDM: An instance of a ProjectMilestoneRole in the context of an ActualProject. ActualProjectMilestoneRole ActualProjectMilestoneRole.owningInstance Value for owningInstance property has to be stereotyped <<ActualProject>> or its specializations. ActualProjectMilestoneRole.definingFeature Value for definingFeature property has to be stereotyped <<ProjectMilestoneRole>> or its specializations. base_Slot MODAF: A Project (MODAF::ProjectType) is used to define a category of project: For example, "Programme", "Acquisition Project" or "Training Programme". DoDAF: NA (only Individual Project in DoDAF). ProjectType Project.ownedAttribute Values for ownedAttribute property must be stereotyped <<ProjectMilestoneRole>> or its specializations. base_Class extension_ composite A type defined by an external ontology. This may be higher-order - i.e. a type of a type. ExternalTypes extension_ISO8601DateTime composite MODAF: A date and time specified in the ISO8601 date-time format including timezone designator (TZD): YYYY-MM-DDThh:mm:ssTZD. DoDAF: NA ISO8601DateTime base_LiteralString The Service-Orientated View (SOV) is a description of services needed to directly support the operational domain as described in the Operational View. A service should be understood in its broadest sense, as a unit of work through which a provider provides a useful result to a consumer. This could be anything from web-based services to delivering an effect to transporting troops. ServiceElements Behavior elements of the service oriented view. Behavior extension_ServiceStateMachine composite extension_ServiceEdge composite UPDM: A ServiceFunction describes the abstract behavior of ServiceOperations, regardless of the actual implementation. MODAF: A type of activity describing the functionality of a service. DoDAF: Information necessary to interact with the service in such terms as the service inputs, outputs, and associated semantics. The service description also conveys what is accomplished when the service is invoked and the conditions for using the service. . ServiceFunction ServiceFunction.ownedParameter The values for the ownedParameter property must be stereotyped <<ServiceParameter>>. base_Activity extension_ServiceMessage extension_ServiceFunction composite extension_ServiceMessageHandler composite * UPDM: A call behavior action that invokes the ServiceFunction that needs to be preformed. --This concept is required for mapping the architecture with UML and does not have a DoDAF or MoDAF equivalent. ServiceFunctionAction ServiceFunctionAction.activity Value for the behavior property must be stereotyped <<ServiceFunction>> or its specializations. ServiceFunctionAction.behavior Value for the activity property must be stereotyped <<ServiceFunction>> or its specializations. base_CallBehaviorAction UPDM: A ServiceOperation provides the access point for invoking the behavior of a provided service. The ServiceOperations are defined on ServiceInterfaces and mirrored on the providing Resource to handle calls forwarded on by the interface. MODAF: a function or procedure which enables programmatic communication with a Service via a ServiceInterface (MODAF:: ServiceInterfaceOpration). ServiceOperation ServiceOperation.ownedParameter English The values for the ownedParameter property must be stereotyped <<ServiceParameter>> or its specializations. base_Operation Links a ServiceOperation to the abstract description of its behavior, as provided by a ServiceFunction. abstractBehavior extension_ServiceFeature composite UPDM:An instance of an AsynchronousMessage, applied in the service domain. ServiceMessageHandler ServiceMessageHandler.signal English Values for the signal property must be stereotyped with <<AsynchronousMessage>> or its specializations. base_Reception extension_ServiceParameter composite UPDM: Interaction for a service interface MODAF: A model representing how a set of Service classes interacts with one another (MODAF::ServiceInteractionSpecification). ServiceInteraction ServiceInteraction.owner Value for the target property must be stereotyped <<ServiceInterface>> or its specializations. ServiceInteraction.message English Values for the message property must be stereotyped with <<ServiceMessage>> or its specializations. base_Interaction extension_ServiceInteraction composite extension_ServiceFunctionAction composite UPDM: Represents inputs and outputs of Service. It is typed by ResourceInteractionItem. MODAF: A constant or variable passed into or out of a ServiceInterface as part of the execution of a ServiceInterfaceOperation (MODAF:: ServiceInterfaceParameter). DoDAF: NA ServiceParameter ServiceParameter.type The values for the type property must be stereotyped a specialization of <<Resource>>. base_Parameter extension_ServiceInterfaceOperation composite UPDM: An extension of <<ActivityEdge>> that is used to model the flow of control/objects through a ServiceFunction. ServiceFunctionEdge ServiceFunctionEdge.owner Value for the target property must be stereotyped <<ServiceFunction>> or its specializations. base_ActivityEdge UPDM: Message for use in a Service Interaction Specification, implements a resourceInteraction or any of the subtypes. ServiceMessage ServiceMessage.receiveEvent.event.operation English Values for the receiveEvent.event.operation property must be stereotyped with <<ServiceOperation>> or its specializations. base_Message Carried ResourceInteraction. carries * true operation true UPDM:Abstract grouping used to ServiceFunctions to Serviceoperations and ServiceMessageHandlers. ServiceFeature ServiceFeature.ownedParameter The values for the ownedParameter property must be stereotyped <<ServiceParameter>>. ServiceFeature.owner The values for the owner property must be stereotyped <<ServiceInterface>>. base_Feature true UPDM Artifact that extends a UML StateMachine. ServiceStateMachine ServiceStateMachine.owner English Values for the owner property must be stereotyped <<ServiceInterface>> or its specializations. base_StateMachine Structure elements of the service oriented view. Structure MODAF: A property of Service. DoDAF: NA ServiceAttribute base_Property MODAF:A ServiceAttributes indicating the level to which a Resource delivers a Service, in a particular environment. DoDAF:NA ServiceLevelValue base_Slot UPDM: A contractual agreement between two resources that implement protocols through which the source service interacts to the destination resource. A physical connection between two resources that implements protocols through which the source resource can transmit items to the destination resource. MODAF: The mechanism by which a Service communicates. DoDAF: An overlap between Performers for the purpose of producing a Resource that is consumed by the other. (DoDAF::Interface). SOAML: Defines the interface to a Service Point or Request Point and is the type of a role in a service contract. ServiceInterface ServiceInterface.ownedAttribute Values for ownedAttribute property must be stereotyped <<ServiceAttribute>> or its specializations. ServiceInterface.feature Value for the feature property must be stereotyped <<ServiceFeature>> or its specializations. base_Class extension_AsynchronousMessage composite extension_ServiceAttribute composite extension_ServiceLevelValueSet composite MODAF:A type of delivered functionality, specified independently of the resources that provide it. DoDAF: mechanism to enable access to a set of one or more capabilities , where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. The mechanism is a Performer. The "capabilities" accessed are Resources -- Information, Data, Materiel, Performers, and Geo-political Extents. . Service base_Port extension_Service composite UPDM: A constraint governing the consumers and providers of services MODAF: A constraint governing one or more Services. DoDAF: Agreement: A consent among parties regarding the terms and conditions of activities that said parties participate in. ServicePolicy ServicePolicy.constrainedElement English Values for constrainedElement property must be stereotyped <<ServiceInterface>> or its specializations. base_Constraint extension_ServiceInterface composite MODAF:ServiceInterface,The mechanism by which a Service communicates. DoDAF:A part of a Performer that specifics a distinct interaction point through which the Performer interacts with other Performers. This isolates dependencies between performers to particular interaction points rather than to the performer as a whole.. ServicePort ServicePort.actualPropertySets English Values for actualPropertySet property must be stereotyped <<ServiceLevelValueSet>> or its specializations. ServicePort.type English Values for type property must be stereotyped <<ServiceInterface>> or its specializations. Port associated with a service level. providedByResource * true MODAF:A value specification for a set of ServiceAttributes indicating the level to which a Resource delivers a Service, in a particular environment. DoDAF:NA ServiceLevelValueSet ServiceLevelValueSet.slot Slot property value must be stereotyped <<ServiceLevelValue>> or its specializations. base_InstanceSpecification Service level associated with a port. resourceBoundary MODAF:A signal which is transmitted irregularly with respect to time. DoDAF: NA AsynchronousMessage base_Signal extension_ServicePolicy composite extension_Request composite extension_ServiceLevelValue composite UPDM:From SoaML A Request represents a feature of a Participant that is the consumption of a service by one participant provided by others using well-defined terms, conditions and interfaces. A Request designates ports that define the connection point through which a Participant meets its needs through the consumption of services provided by others. MODAF: Similar to requires, Asserts that a Resource requires a Service to be provided in order to function correctly. DoDAF: Similar to ServicePort, A part of a Performer that specifics a distinct interaction point through which the Performer interacts with other Performers. This isolates dependencies between performers to particular interaction points rather than to the performer as a whole. Request base_Port The Strategic Elements are used in the Strategic View which provides an overall Enterprise Architecture assessment of the Capabilities and their relationships facilitating Capability Management (e.g. capability introduction, integration, re-alignment and removal). While an Enterprise will have a number of UPDM Architecture Descriptions that have the Operational, System, Technical Standards, and All Views, only one Strategic View will exist across a number of Architecture Descriptions. StrategicElements Structural section of the StrategicElements profile. Structure Expose.client Value for the client property must be stereotyped <<ServiceInterface>> or its specializations. Expose.supplier Value for the supplier property must be stereotyped <<Capability>>. UPDM: An EnterprisePhase can be sub-divided into structural and temporal parts. StructuralPart describes the EnterprisePhase elements that describe the structure. MODAF: Asserts that one EnterprisePhase is a spatial part of another, (MODAF::EnterpriseStructure) Note:- This is a topological structuring relationship, hence the EnterprisePhase may be physically disjoint StructuralPart StructuralPart.type Value for type metaproperty must be stereotyped <<EnterprisePhase>> or its specializations. StructuralPart.class Value for class metaproperty must be stereotyped <<EnterprisePhase>> or its specializations. base_Property extension_Capability composite UPDM: A property of a capability. MODAF: NA DoDAF: NA CapabilityProperty CapabilityProperty.type Value for type meta property must be stereotyped <<Capability>> or its specializations. base_Property extension_CapabilityProperty composite MODAF: A specific, required objective of the enterprise that the architecture represents. DoDAF: NA EnterprisePhase Enterprise from/to Must fall within the Enterprise to and from time, the complete lifecycle. The time and date at which the Phase ends. endDate The time and date at which the Phase starts. startDate The Goal towards which this Phase is directed and is in support of. goal * The Vision towards which this Phase is directed and is in support of. vision Collection of statement tasks. statementTask * base_Class The EnterprisePhase described by an ArchitecturalDescription. desribedBy * EnterprisePhases associated with a Mission. fulfills * extension_VisionStatement composite MODAF: A specific, required objective of the enterprise that the architecture represents. DoDAF: NAA EnterpriseGoal A description of the usefulness of the Goal in terms of why the state or condition of the Enterprise is worth attaining. benefits * true Phase of the goal. enterprisePhase base_Class MODAF: The overall aims of an enterprise over a given period of time. DoDAF: (DoDAF::Vision): An end that describes the future state of the enterprise, without regard to how it is to be achieved; a mental image of what the future will or could be like. EnterpriseVision A description of the Vision. statement * The phase which temporally locates the Vision. enterprisePhase base_Class extension_EnterprisePhase composite extension_EnterpriseGoal composite UPDM Artifact: An EnterprisePhase can be sub-divided into structural and temporal parts. TemporalPart describes the EnterprisePhase elements that have a time based nature. MODAF: Asserts that one EnterprisePhase is a temporal part of another. Note: This means that both EnterprisePhases have the same spatial extent - i..e this is only a temporal structure (MODAF:: EnterpriseTemporalPart). TemporalPart TemporalPart.class Value for class metaproperty must be stereotyped <<EnterprisePhase>> or its specializations. TemporalPart.type Value for type metaproperty must be stereotyped <<EnterprisePhase>> or its specializations. base_Property MODAF: Asserts that a StandardOperationalActivity is in some way part of a capability. DoDAF: MapsToCapability (DoDAF::ActivityPartOfCapability) is a disposition to manifest an Activity. An Activity to be performed to achieve a desired effect under specified [performance] standards and conditions through combinations of ways and means. MapsToCapability MapsToCapability.supplier Value for the supplier property must be stereotyped <<Capability>>. MapsToCapability.client Value for the client property must be stereotyped a specialization of <<Activity>>. base_Dependency MODAF: A high level specification of the enterprise's ability. DoDAF: The ability to achieve a desired effect under specified [performance] standards and conditions through combinations of ways and means [activities and resources] to perform a set of activities. Capability Capability.ownedAttribute Values for ownedAttribute property must be stereotyped <<CapabilityProperty>> or its specializations. base_Class UPDM: Relationship between a Node and a capability the node provides. MODAF: (MODAF::CapabilityForNode): An assertion that a Node is required to have a Capability. DoDAF: A couple that represents the capability that a performer manifests. Exhibits Exhibits.supplier Value for the supplier property must be stereotyped <<Capability>>. Exhibits.client Value for the client property must be stereotyped a specialization of <<CapableElement>>. base_Dependency The ActualPropertySet that exists between a Capability and a Capable Element. universalCapabilitySet Asserts that a Capability's capabilityMetric (MeasureableProperty) is valid for a particular environment. environmentalConditions * extension_ composite MODAF: A high-level textual description of an EnterpriseVision. DoDAF: An end that describes the future state of the enterprise, without regard to how it is to be achieved; a mental image of what the future will or could be like (DODAF::Vision). VisionStatement base_Comment extension_ composite UPDM:Abstract element used to group Operational and Resource states . DesiredState true extension_ composite extension_ composite extension_EnterpriseVision composite UPDM:Abstract element used to group UPDM elements that might desire a particular effect. Desirer true * OperationalElements group elements used to model product for Operational View. An Operational View (OV) describes the tasks and activities, operational elements, and information exchanges required to conduct operations. A pure OV is materiel independent. However, operations and their relationships may be influenced by new technologies such as collaboration technology, where process improvements are in practice before policy can reflect the new procedures. There may be some cases, as well, in which it is necessary to document the way processes are performed given the restrictions of current systems, in order to examine ways in which new systems could facilitate streamlining the processes. In such cases, an OV may have materiel constraints and requirements that must be addressed. For this reason, it may be necessary to include some high- level Systems View (SV) architecture data as overlays or augmenting information onto the OV products. OperationalElements Behavioral section of the OperationalElements Profile. Behavior UPDM:A partial or full realization of an OperationalActivity. MODAF:NA DoDAF:NA NodeOperation NodeOperation.ownedParameter English The values for the ownedParameter property must be stereotyped <<OperationalParameter>> or its specializations. base_Operation Relationship between a NodeOperation and an OperationalActivity. realizes MODAF: An OperationalEventTrace (MODAF::OperationalInteractionSpecification) is a specification of the interactions between nodes in an operational architecture. DoDAF: The Operational Event-Trace Description (OV-6c) DoDAF-described View provides a time ordered examination of the resource flows as a result of a particular scenario. Each event-trace diagram will have an accompanying description that defines the particular scenario or situation. OperationalEventTrace OperationalEventTrace.message English Values for the message property must be stereotyped with <<OperationalMessage>> or its specializations. OperationalEventTrace.owner Values for the owner property must be stereotyped with <<Node>> or its specializations. base_Interaction extension_OperationalActivityParameter composite UPDM: A state machine describing an operational behavior or property. MODAF: An OperationalStateMachine (MODAF::OperationalStateDescription) is a rule governing an operational behavior or property. DoDAF: The Operational State Transition Description (OV-6b) DoDAF-described View is a graphical method of describing how an Operational Activity responds to various events by changing its state. The diagram represents the sets of events to which the Architecture will respond (by taking an action to move to a new state) as a function of its current state. Each transition specifies an event and an action. OperationalStateDescription OperationalStateDescription.owner Values for the owner property must be stereotyped with specializations of <<SubjectOfOperationalStateMachine>> . OperationalStateDescription.region.state English Values for the region.state property must be stereotyped with <<OperationalState>> or its specializations. base_StateMachine extension_OperationalMessage composite UPDM Represents inputs and outputs of an OperationalActivity. It is typed by OperationalExchangeItem.. OperationalParameter OperationalParameter.type English Value for the type property must be stereotyped by specialization of <<OperationalExchangeItem>>. base_Parameter UPDM: State identified in the context of an OperationalStateDescription MODAF:N/A DoDAF:N/A OperationalState base_State UPDM: The OperationalActivityAction is defined as a call behavior action that invokes the activity that needs to be preformed. MODAF: Used to relate an OperationalActivity to its sub-activities. DoDAF:NAA OperationalActivityAction OperationalActivityAction.activity Value for behavior property must be stereotyped <<OperationalActivity>> or its specializations. OperationalActivityAction.behavior Value for activity property must be stereotyped <<OperationalActivity>> or its specializations. base_CallBehaviorAction UPDM: Message for use in an Operational Event-Trace which carries any of the subtypes of OperationalExchange. This is used to provide additional information about OperationalMessages for display on an OV-6c.. OperationalMessage OperationalMessage.receiveEvent.event.operation English Values for the receiveEvent.event.operation property must be stereotyped with <<NodeOperation>> or its specializations. base_Message Carried OperationalExchange. carries * true The NodeOperation associated with a OperationalMessage. operation true extension_OperationalActivityEdge composite MODAF: A logical process, specified independently of how the process is carried out.DoDAF: An activity is an action performed in conducting the business of an enterprise. It is a general term that does not imply a placement in a hierarchy (e.g., it could be a process or a task as defined in other documents and it could be at any level of the hierarchy of the OV-5). It is used to portray operational actions not hardware/software system functions. NOTE: This is also a specialization of Activity. DoDAF:NANA OperationalActivity OperationalActivity.ownedParameter The values for the ownedParameter property must be stereotyped <<OperationalParameter>> or its specializations. Object acting upon this OperationalActivity. subject * true base_Activity Relationship between an OperationalActivity and a NodeOperation realizedBy * extension_NodeOperation composite extension_OperationalActivity composite extension_ composite extension_OperationalActivityAction composite UPDM Abstract Element: The element being described by the state machine. SubjectOfOperationalStateMachine SubjectOfOperationalStateMachine.ownedBehavior English If elements, that have applied stereotypes that are specializations of <<SubjectOfOperationalStateMachine>> have StateMachines as owned behaviors, then those behaviors must be stereotyped <<OperationalStateMachine>> or its specializations. true extension_OperationalState composite extension_OperationalInteraction composite UPDM An extension of <<ActivityEdge>> that is used to model the flow of control/objects through an OperationalActivity. MODAF: An OperationalActivityEdge (MODAF::OperationalActivityFlow) is a flow of information, energy or materiel from one activity to another. DoDAF:NAA OperationalActivityEdge OperationalActivityEdge.owner <<OperationalActivityEdge>> must be owned directly or indirectly by <<OperationalActivity>>. base_ActivityEdge The item information element carried along an OperationalActivityEdge, associated with the relevant needline. carriedItem * true Section of the OperationalElements profile that describe flows exists or are required between Nodes such as flows of information, people, materiel, or energy. Flows Enumeration of operational exchange kinds, used to support the exchangeKind tag of the OperationalExchange stereotype. OperationalExchangeKind A flow of materiel (artifacts) between Functions. MaterielExchange A LogicalFlow where human resources (PostTypes, RoleTypes) flow between Nodes. OrganizationalExchange A LogicalFlow where energy is flowed from one node to another. EnergyExchange A LogicalFlow where energy is flowed from one node to another. InformationExchange A LogicalFlow where CapabilityConfigurations flow from one node to another. ConfigurationExchange A LogicalFlow where GeoPoliticalExtents (i.e. Borders) flow from one place to another. GeoPoliticalExtentExchange extension_OperationalExchange composite UPDM: An utility element used as common flow for: - InformationExchange - OrganizationalExchange - EnergyExchange - MaterielExchange - ConfigurationExchange - GeoPoliticalExtent An operational exchange is formed when an activity of one operational node consumes items produced by another activity of a different operational node. An operational exchange describes the characteristics of the exchanged item, such as the content, format (voice, imagery, text and message format, etc.), throughput requirements, security or classification level, timeliness requirement, and the degree of interoperability. MODAF: An OperationalExchange (MODAF::LogicalFlow) asserts that a flow exists or is required between Nodes (e.g. flows of information, people, materiel, or energy). eriel, or energy). OperationalExchange OperationalExchange.realization/realizingConnector English Value for realization or realizingConnector property has to be stereotyped <<Needline>>, <<ServiceChannel>>, or their specializations. OperationalExchange.conveyed English In case of OperationalExchange.operationalExchangeKind: = InformationExchange, the conveyed element must be stereotyped <<ExchangeElement>> or its specializations, = MaterielExchange, the conveyed element must be stereotyped <<ResourceArtifact>> or its specializations, = EnergyExchange, the conveyed element must be stereotyped <<Energy>> or its specializations, = OrganizationalExchange, the conveyed element must be stereotyped <<OrganizationalResource>> or its specializations, = ConfigurationExchange, the conveyed element must be stereotyped <<CapabilityConfiguration>> or its specializations, or = GeoPoliticalExtentExchange, the conveyed element must be stereotyped <<GeoPoliticalExtent>> or its specializations. OperationalExchange.informationSource Value for informationSource property has to be stereotyped <<Node>> or its specializations. OperationalExchange.realizingActivityEdge Value for realizingActivityEdge property has to be stereotyped <<OperationalActivityEdge>> or its specializations. OperationalExchange.informationTarget Value for informationTarget property has to be stereotyped <<Node>> or its specializations. OperationalExchange.realizingMessage English Value for realizingMessage property has to be stereotyped <<OperationalMessage>> or its specializations. Enumeration of operational exchange kinds. exchangeKind true base_InformationFlow UPDM An abstract utility element used as common ancestor for: - InformationElement - ResourceArtifact - Energy - OrganizationalResource - CapabilityConfiguration - GeoPoliticalExtentt OperationalExchangeItem true MODAF: Asserts that one OrganisationalResource (source) commands another (target) DoDAF: NA Command Command.conveyed Value for the conveyed property must be stereotyped <<ExchangeElement>> or its specializations. Command.informationTarget Value for the informationTarget property must be stereotyped <<OrganizationalResource>> or its specializations. Command.informationSource Value for the informationSource property must be stereotyped <<OrganizationalResource>> or its specializations. base_InformationFlow extension_Command composite The Data Profile is used to document the business information requirements and structural business process rules of the architecture. It describes the information that is associated with the information exchanges of the architecture. Included are information items, their attributes or characteristics, and their inter-relationships. Data extension_LogicalDataModel composite MODAF: A LogicalDataModel is a specification of business information requirements as a formal data structure, where relationships and classes (entities) are used to specify the logic which underpins the information. DoDAF: A Logical Data Model allows analysis of an architecture’s data definition aspect, without consideration of implementation specific or product specific issues. LogicalDataModel base_Package Section of the OperationalElements profile that describe stuctural concepts. Structure extension_ArbitraryRelationship composite UPDM: An abstract element representing the owners/context of composite structure at the operational level. MODAF:The abstract supertype of all elements that can have child Nodes (LogicalArchitecture, ProblemDomain & NodeType) DoDAF:NA NodeParent true extension_LogicalArchitecture composite extension_SecurityDomain composite The organizational elements of the operational structure. Organizational Actual elements in the organizational part of the structural part of the Operational profile. Actual extension_ActualPost composite MODAF: An actual specific organisation, an instance of an organisation class - e.g. "The US Department of Defense" DoDAF: [DoDAF::Organization]: A specific real-world assemblage of people and other resources organized for an on-going purpose. ActualOrganization ActualOrganization.slot Slot property value must be stereotyped <<ActualOrganizationRole>> or its specializations. ActualOrganization.classifier Classifier property value must be stereotyped <<Organization>> or its specializations. Standards that were ratified by this ActualOrganization. ratifiedStandards * base_InstanceSpecification Army, Navy, Air Force, Marine Corps, Joint code/symbol Service office code or symbol serviceType UPDM:Abstract element used to group ActualPersons and ActualOrganisationalResources. MODAF:NA DoDAF:NA CompetenceProvider true extension_ composite extension_ActualOrganization composite extension_ActualPerson composite extension_FillsPost composite UPDM: A relationship between two ActualOrganizationResources. MODAF: A relationship between two actual specific organisations or parts of an organisation. DoDAF: NA ActualOrganizationRelationship ActualOrganizationRelationship.conveyed Value for conveyed metaproperty must be stereotyped <<ExchangeElement>> or its specializations. ActualOrganizationRelationship.target Value for realizes metaproperty must be stereotyped <<ResourceInteraction>> or its specializations. ActualOrganizationRelationship.source Value for source metaproperty must be stereotyped <<ActualOrganizationalResource>> or its specializations. base_InformationFlow UPDM: An ActualOrganization or an ActualPost. MODAF: An instance of either an actual organisation or an actual post. DoDAF: A specific real-world assemblage of people and other resources organized for an on-going purpose. ActualOrganizationalResource true extension_ActualOrganizationRelationship composite UPDM: An actual, specific post, an instance of a PostType class - e.g. "President of the United States of America." MODAF: NA DoDAF: NA ActualPost ActualPost.classifier Classifier property value must be stereotyped <<Post>> or its specializations. base_InstanceSpecification UPDM: Named individual that fulfills an ActualPost. An individual human being (vs Person which is a type), that is recognized by law as the subject of rights and duties. MODAF: NA DoDAF: An individual person ActualPerson ActualPerson.classifier Value for the classifier property has to be stereotyped <<Person>> or its specializations. base_InstanceSpecification UPDM: Asserts that ActualPerson fills an ActualPost. MODAF: NA DoDAF: NA FillsPost FillsPost.supplier Value for the supplier property must be stereotyped by <<ActualPost>> or its specializations. FillsPost.client Value for the client property must be stereotyped by <<ActualPerson>> or its specializations. base_Dependency Start date startDate End date endDate UPDM: Relates an actual specific organization to an actual specific organizational resource that fulfils a role in that organization. MODAF: NA DoDAF: NA ActualOrganizationRole ActualOrganizationPart.definingFeature Value for definingFeature property has to be stereotyped <<ResourceRole>> or its specializations. ActualOrganizationPart.owningInstance Value for owningInstance property has to be stereotyped <<ActualOrganization>> or its specializations. base_Slot Typical elements in the organizational part of the structural part of the Operational profile. Typical extension_Person composite MODAF: A Post (MODAF::PostType) is a type of point of contact or responsible person. Note that this is the type of post - e.g. Desk Officer, Commander Land Component, etc. DoDAF: A Post (DoDAF:: PersonType) is a category of persons defined by the role or roles they share that are relevant to an architecture. Post base_Class MODAF:: Asserts that an Role requires a Competence (MODAF::CompetenceForRole). DoDAF: An overlap between a Personnel Type and the Skills it entails (DoDAF:: SkillPartOfPersonType). RequiresCompetence RequiresCompetence.supplier Value for the client property must be stereotyped <<Competence>> or its specializations. RequiresCompetence.client Value for the client property must be stereotyped a specialization of <<CompetenceRequirer>>. base_Dependency The measurements associated with a Competence. measurementSet * UPDM:Asserts that a Post or Organization has specific responsibilities. MODAF:NA DoDAF:NA Responsibility base_Class extension_Responsibility composite UPDM:Abstract element used to group Organizations, Post and Responsibilities. MODAF:NA DoDAF:NA CompetenceRequirer true UPDM: A type of a human being that is recognized by law as the subject of rights and duties. This is used to define the characteristics that require capturing for ActualPersons (e.g. properties such as address, rank, telephone number, etc). MODAF: NA DoDAF: NA Person base_Class UPDM An abstract element that represents Organizations and Posts. MODAF: Either an organization, or a post. OrganizationalResource true MODAF: A group of persons, associated for a particular purpose. DoDAF: A type of Organization. Organization base_Class UPDM: Asserts that a Resource type provides a competence. MODAF: Asserts that a Role requires a Competence (MODAF::CompetenceForRole). DoDAF: An overlap between a Personnel Type and the Skills it entails (DoDAF:: skillPartOfPersonType) ProvidesCompetence ProvidesCompetence.client Value for the client property must be stereotyped by a specialization of <<CompetenceProvider>>. ProvidesCompetence.supplier Value for the client property must be stereotyped <<Competence>> or its specializations. base_Dependency The measurements associated with a Competence. universalPropertySet * extension_PostType composite extension_ composite extension_requiresCompetence composite extension_OrganizationType composite MODAF: A CompositeStructureModel whose parts are either NodeRoles (MODAF::Node), ProblemDomains, or KnownResources. DoDAF: NA LogicalArchitecture base_Class extension_Node composite MODAF:NA DoDAF: A NodeType whose members (other Nodes, KnownResources) all share a common security policy. SecurityDomain base_Class MODAF: A specific set of abilities defined by knowledge, skills and attitude. DoDAF: (DoDAF::Skill): The ability, coming from one's knowledge, practice, aptitude, etc., to do something well. Competence base_Class extension_NodeUsage composite extension_Competence composite * MODAF: A purpose to which a person, organization or autonomous system is tasked. DoDAF: The task, together with the purpose, that clearly indicates the action to be taken. Mission The area in which the Mission will take place. MissionArea * base_Activity MODAF: Abstract. An element of the architecture that may be subject to an OperationalConstraint or OperationalStateDescription. SubjectOfOperationalConstraint true MODAF: A Node (MODAF::NodeType) is a logical entity that performs operational activities. Note: nodes are specified independently of any physical realization. DoDAF: A Node (DoDAF::OperationalNode) is an element of the operational architecture that produces, consumes, or processes information. NOTE: This is also a specialization of Performer. . Node Node.ownedOperation Values for the ownedOperation property must be stereotyped <<NodeOperation>> or its specializations. Node.isCapableOfPerforming Is capable of performing only <<OperationalActivity>> elements or its specializations. Node.ownedPort Values for the ownedPort property must be stereotyped <<NodePort>>, <<ServicePort>>, or their specializations. base_Class connectedNodes * true extension_Needline composite MODAF: A NodeRole (MODAF::Node) is used to link a parent Node to its sub-nodes. DoDAF: NA NodeRole NodeRole.class Value for class meta property must be stereotyped a specialization of <<NodeParent>>. NodeRole.type Value for type meta property must be stereotyped <<Node>> or its specializations. base_Property OperationalActivity Performed in the context of a specific role. performsInContext * MODAF: Asserts that a known Resource plays a part in the architecture. DoDAF: NA – covered by the more general temporalWholePart element. KnownResource KnownResrouce.type Values for type property have to be stereotyped <<SystemResource>> or its specializations. base_Property UPDM: A port is a property of a Node that specifies a distinct interaction point between the node and its environment or between the (behavior of the) node and its internal parts. It is the "entry/exit" point where resources (e.g., energy, information/data and people, etc) flow in and out of a node. NodePort NodePort.type Value for the type property must be stereotyped specialization of <<OperationalExchangeItem>>. base_Port extension_NodePort composite extension_KnownResource composite extension_ HighLevelOperationalConcept composite UPDM: Represents a visual indication of a connection used in high level operational concept diagrams. The connections are purely visual and cannot be related to any architectural semantics. MODAF: NA DoDAF:NA ArbitraryConnector ArbitraryConnector.supplier The value for supplier property has to be stereotyped <<ConceptRole>> or its specializations. ArbitraryConnector.client The value for client property has to be stereotyped <<ConceptRole>> or its specializations. base_Dependency MODAF: A relationship between Nodes representing a bundle of InformationExchanges. DoDAF: A needline documents the requirement to exchange information between nodes. The needline does not indicate how the information transfer is implemented. . Needline Needline.end The value for the role property for the owned ConnectorEnd must be stereotype <<NodeRole>>/<<NodePort>> or its specializations. base_Connector UPDM: Abstract, an item which may feature in a high level operational concept. DoDAF:NA ConceptItem true UPDM: An abstract Class that is extended by OperationalConstraint (A rule governing an operational behaviour or property.) and ResourceConstraint. MODAF:A rule governing an operational behaviour or property. DoDAF:A principle or condition that governs behavior; a prescribed guide for conduct or action (Rule). OperationalConstraint OperationalConstraint.constrainedElement Value for the constrainedElement property must be stereotyped by any specialization of <<SubjectOfOperationalConstraint>>. base_Constraint extension_Mission composite MODAF: A generalized model for operations. DoDAF: NA HighLevelOperationalConcept HighLevelOperationalConcept.ownedAttribute English The values for the ownedAttribute properties must be stereotyped with specializations of the <<ConceptRole>>. base_Class Mission that is described by this HighLevelOperationalConcept. mission * extension_ConceptRole composite UPDM: Usage of a ConcepItem in the context of a HighLevelOperationalConcept MODAF:-ItemInConcept, A relationship which asserts that a ConceptItem forms part of the high level operational concept DoDAF: N/AA ConceptRole ConceptRole.type Value for the type property must be stereotyped a specialization of <<ConceptItem>>. base_Property extension_OperationalConstraint composite The AllEllements are elements that are part of the All View. The All-Views (AVs) provide an overarching description of the architecture, its scope, ownership, timeframe and all of the other meta data that is required in order to effectively search and query architectural models. They also provide a place to record any findings arising from the architecting process. The AVs include a dictionary of the terms used in the construction of the architecture – which helps others fully understand it’s meaning at a later date. Since the AVs provide critical information for the future access and exploitation of an architectural model their population is essential whenever an architecture is created or modified. The AVs provide a critical input into the processes that provide architectural governance. AllElements UPDM: Abstract grouping for interactions that exchange messages. MODAF:NA DoDAF:NA Exchange true This section of the specification contains the Structural Aspects of the All Elements section. Structure UPDM: Abstract element placeholder to indicate that resources can be exchanged in Operational and Systems views. MODAF: NA DoDAF: Data, Information, Performers, Materiel, or Personnel Types that are produced or consumed. Resource true Enumeration of possible kinds for constraints. RuleKind An OperationalConstraint that specifies policy for information handling, physical security, encryption, etc. SecurityPolicy Statement that something of importance to the business either exists as a concept of interest or exists in relationship to another thing of interest. StructuralAssertion Statement that concerns some dynamic aspect of the business. ActionAssertion Rule derived from another rule. Derivation A consent among parties regarding the terms and conditions of activities that said parties participate in. Agreement Business Rule, Rule, Restraint, Operational Limitation. Constraint An authoritative statement intended to lead or steer the execution of actions. Guidance extension_InformationElement composite UPDM: A participant is the abstract type of a provider and/or consumer of services. In the business domain a participant may be a person, organization or system. In the systems domain a participant may be a system, application or component. Participant Participant.ownedPort Values for the ownedPort property must be stereotyped <<ServicePort>> or its specializations. true MODAF: A relationship specifying the need to exchange information between nodes. DoDAF: NA - this is a specialization of OperationalExchange (DoDAF::Interface). ExchangeElement base_DataType The relationship between the EntityElement that defines the ExchangeElement. definedBy * true Enumeration of the kinds of information being exchanged. exchangeElementKind true MODAF: An abstract Class that is extended by OperationalConstraint (A rule governing an operational behaviour or property.) and ResourceConstraint (A rule governing the structural or functional aspects of an implementation - this may also include constraints on OrganisationalResources that are part of an implementation). DoDAF: Rule: A principle or condition that governs behavior; a prescribed guide for conduct or action. Subtype: Constraint: The range of permissible states for an object. Rule ruleKind true Enumeration of the types of element being exchanged on an information exchange. ExchangeElementKind An item of information that flows between Operational Activities and Nodes. The structure of an InformationElement may be defined using a LogicalDataModel. InformationElement A formalized representation of data which is managed by or exchanged between resources. DataElement The measurement portion of the AllElements profile. Measurements MODAF: MeasurableProperty: A property of something in the physical world, expressed in amounts of a unit of measure. The property may have a required value - either specified by the [defaultValue] from UML::property attribute, or the [minValue] and [maxValue] to specify a required range. DoDAF: Measure: A Measurement (DoDAF::Measure) is the magnitude of some attribute of an individual. Measurement base_Property UPDM: A set or collection of ActualMeasurement(s). A date of measurement can be set. An intent of ActualMeasurementSet can be "Result", "Required", or "Estimate" MODAF: NA DoDAF: NA ActualPropertySet ActualPropertySet.slot Value for the slot property must be stereotyped <<ActualProperty>> or its specializations. ActualPropertySet.classifier Value for the classifier property must be stereotyped <<PropertySet>> or its specializations. base_InstanceSpecification Measured element. appliesTo Possible kinds of ActualMeasurementSet intention, derived from DoDAF. ActualPropertySetKind Estimate. Estimate Actual Measure. Actual Required Measure Required extension_ composite UPDM: An actual value of the Measurement. MODAF: NA DoDAF: NAA ActualMeasurement ActualMeasurement.definingFeature Value for definingFeature property must be stereotyped <<Measurement>> or its specializations. base_Slot extension_ActualMeasurementSet composite UPDM:The value of a Measure. MODAF:NA DoDAF:NA ActualProperty PropertyValue.owningInstance Value for owningInstance property has to be stereotyped <<PropertySet>> or its specializations. PropertyValue.definingFeature Value for definingFeature property must be stereotyped <<Property>> or its specializations. base_Slot Applicable end date of the measured property. endDate Applicable end date of the measured property. startDate Possible kinds of ActualMeasurementSet intention. intention UPDM: A set or collection of Measurement(s). MODAF: NA DoDAF: NA PropertySet PropertySet.ownedAttribute Values for the ownedAttribute property must be stereotyped <<Property>> or its specializations. Measured element. appliesTo * true extension_MeasurementSet composite UPDM: The defining feature of an actual property, used to capture measurements MODAF: NA DoDAF: NA Property base_Property defaultValue maxValue minValue UPDM: A collection of Measurements. MODAF: N/A DoDAF: N/A MeasurementSet MeasurementSet.ownedAttributes Owned attributes have to be stereotyped <<Measurement>>. base_DataType extension_PropertyValue composite extension_ActualMeasurement composite extension_MeasurableType composite The environmental aspects of the AllElements profile. Environment UPDM:Abstract grouping to capture elements that can have a location. LocationHolder The ActualLocation associated with a LocationHolder(Abstract). physicalLocation * The Environment in which a LocationHolder(Abstract) is active. requiredEnvironment * true Enumeration of location kinds, derived from DoDAF, used to support the locationKind tag of the LocationKind stereotype. LocationKind The space enclosed by a polygon. PolygonArea The space enclosed by a rectangle. RectangularArea The space enclosed by an ellipse. ElipticalArea The space enclosed by a circle. CircularArea Other Location kind that is not on the enumerated list. Other The amount of space occupied by a three-dimensional object of definite shape; not liquid or gaseous. SolidVolume A portion of space having length and breadth but no thickness or regards to time. Surface A geometric figure formed by a point moving along a fixed direction and the reverse direction. Line Unidimensional Individual (dimensionless in space, existent over all time). Point Unidimensional Individual (dimensionless in space, existent over all time). GeoStationaryPoint A two-dimensional portion of space. PlanarSurface MODAF:A definition of the conditions in which something exists or functions. DoDAF:NA Environment Environment.ownedAttributes Owned attributes have to be stereotyped <<EnvironmentProperty>>. base_DataType extension_Environment composite MODAF: A general specification of the surroundings / scenario in which an operation may take place. Examples would be: "desert", "arctic", "at sea", etc. DoDAF: A point or extent in space that may be referred to physically or logically. Includes concepts such as: Facility, Installation, RealProperty, Site, , and instances of conditions such as underwater (as specified in UJTLs). LocationType base_DataType Kind of location taken from the DOD UJTLs. locationTypeKind String defining custom kinds of locationTypes. customKind MODAF: A PhysicalLocation (MODAF::ActualLocation) is a location anywhere on the earth. The means of describing the location is a string (locationDescription). The information contained in that string is governed by the taxonomy reference - e.g. if the PhysicalLocation is a "GPS reference", the string will contain the GPS coordinates. NOTE: this has been extended in UPDM to include non-earth locations. DoDAF: All subtypes of << IndividualType>> Location, such as Facility, Site, etc. ActualLocation ActualLocation.classifier Classifier property value must be stereotyped <<LocationType>> or its specializations. String describing the address of the actual location, i.e. "1600 Pennsylvania avenue" describes the address of the actual location "The White House" address Enumerated value describing the kind of location. locationKind String describing a location kind that is not on the enumerated list customKind Boolean, by default = false, that indicates if the location address is embedded in the location name. locationNamedByAddress base_InstanceSpecification Abstract element indicating what an EnvironmentProperty can be typed by. ConditionType true extension_PhysicalLocation composite extension_EnvironmentalProperty composite extension_Location composite Enumeration of kinds of location types, derived from DoDAF, used to support the LocationTypeKind tag of the LocationTypeKind stereotype. LocationTypeKind Powertype Of PolygonArea. PolygonAreaType Powertype Of RectangularArea. RectangularAreaType Powertype Of EllipticalArea. ElipticalAreaType Powertype Of CircularArea. CircularAreaType Other LocationType kind that is not on the enumerated list. OtherType Powertype Of SolidVolume. SolidVolumeType Powertype Of Surface. SurfaceType Powertype Of Line. LineType Powertype Of Point. PointType Powertype Of GeoStationaryPoint. GeoStationaryPointType Powertype Of PlanarSurface. PlanarSurfaceType MODAF:Asserts that an Environment has one or more properties. These may be Climate, LocationType, or LightCondition. DoDAF:NA EnvironmentProperty EnvironmentalProperty.class Value for the class property must be stereotyped <<Environment>> or its specializations. EnvironmentalProperty.type Value for the type property must be stereotyped <<ConditionType>> or its specializations. base_Property The views section of the AllElements profile. Views MODAF:A specification of a way to present an aspect of the architecture. Views are defined with one or more purposes in mind - e.g. showing the logical topology of the enterprise, describing a process model, defining a data model, etc. DoDAF:NA View Architectural elements contained in the view. architecturalElements * Description of the view. description base_Package The Viewpoints associated with a View. viewpoints * The EnterprisePhase that is covered by a view. coversPhase extension_ArchitecturalDescription composite extension_ composite MODAF: Asserts that one architectural description (referrer) refers to another (referred). DoDAF: NA ArchitecturalReference ArchitecturalReference.supplier Value for the supplier property must be stereotyped <<ArchitecturalDescription>> or its specializations. ArchitecturalReference.client Value for the client property must be stereotyped <<ArchitecturalDescription>> or its specializations. base_Dependency Enumeration of the possible types of architectural framework that the architecture is being developed for. ArchitectureFrameworkKind NATO Architecture Framework. NAF Department of Defense Architecture Framework. DoDAF Ministry of Defence Architecture Framework. MODAF MODAF:An instance of the specified View. DoDAF:NA Viewpoint base_Package String, the stakeholders of the architecture. stakeholders * String,the concerns to be addressed by the viewpoint. concerns * String, the languages used to express the viewpoint. languages * String, the methods employed in the development of the viewpoint. methods * String, the purpose of the viewpoint. purpose MODAF: Annotation that can be applied to any element in the architecture. DoDAF: NA Metadata If the meta data corresponds to the Dublin Core Meta-Data Standard, then the meta-data element name should be listed here dublinCoreElement If the meta data corresponds to the MOD Meta-Data Standard, then the meta-data element name should be listed here. modMetaDataElement The name of the Metadata. name base_Comment extension_Metadata composite extension_Viewpoint composite extension_ArchitectureMetadata composite extension_View composite MODAF: A specification of a system of systems at a technical level which also provides the business context for the system of systems. DoDAF: Information describing an architecture such as an OV-5 Activity Model document. ArchitecturalDescription ArchitecturalDescription.architectureFramework English If the property is set to DoDAF, only aliases scoped under the DoDAF profile can be used – if set to MODAF then only MODAF aliases can be used. Should the property be set to nothing, none of the aliases can be used. References the actual organizational resource that has the authority to approve the architectural description. approvalAuthority * The name of the architect responsible for the ArchitecturalDescription. architect Any assumptions, constraints, and limitations contained in the ArchitecturalDescription, including those affecting deployment, communications performance, information assurance environments, etc. assumptionAndConstraint Describes the ActualOrganizationalResource creating the ArchitecturalDescription. creatingOrganization Date that the Architectural Description was completed. dateCompleted Explains the need for the Architecture, what it will demonstrate, the types of analyses that will be applied to it, who is expected to perform the analyses, what decisions are expected to be made on the basis of each form of analysis, who is expected to make those decisions, and what actions are expected to result. purpose States the recommendations that have been developed based on the architecture effort. Examples include recommended system implementations, and opportunities for technology insertion. recommendations Summarizes the findings that have been developed so far. This may be updated several times during the development of the ArchitecturalDescription. summaryOfFindings Identifies any tools used to develop the ArchitecturalDescription as well as file names and formats if appropriate. toolsUsed Indicates whether the ArchitecturalDescription is existing or future. toBe base_Package Indicates which viewpoints are used in the architecture. viewpoint Indicates the type of framework used. architectureFramework Indicates which views are used in the architecture. views * describes UPDM: Information on ArchitecturalDescription. It states things like what methodology was used, notation, etc. MODAF: A Metadata element that applies to the whole architecture. DoDAF: NA ArchitectureMetadata ArchitectureMetadata.annotatedElement Value for the annotatedElement property must be stereotyped <<ArchitecturalDescription>> or its specializations. base_Comment extension_Entity composite The behavioral portion of the AllElements profile. Behavior UPDM:Tuple defining the relationship between systems and service elements and operational elements MODAF: ActivityToFunctionMapping, Asserts that a Function (at least in part) performs or assists in the conducting of an OperationalActivity. DoDAF: N/A Implements Implements.client Values for the client property must be stereotyped <<SystemResource>>, <<ResourceInteraction>>, <<Function>>, <<ServiceFunction>> or their specializations. Implements.supplier English Values for the supplier property must be stereotyped <<Node>>, <<OperationalActivity>>,<<OperationalExchange>>,<<Function>> or their specializations. base_Abstraction UPDM: An abstract element that represents a behavior (i.e. a Function or OperationalActivity) that can be performed by a Performer. MODAF: NA DoDAF: Work, not specific to a single organization, weapon system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state.. Activity The environment under which an activity is performed. activityPerformableUnderCondition * true extension_ composite UPDM: Links a Performer to the behavior that it can perform. DoDAF: The Performs (DoDAF::activityPerformedByPerformer) relationship is an overlap between a Performer and a PerformedActivity (DoDAF::Activity) wherein the activity is performed by the Performer. IsCapableOfPerforming IsCapableOfPerforming.client Values for the client property must be stereotyped <<Node>>, <<SystemResource>>, <<ServiceInterface>> or their specializations. IsCapableOfPerforming.supplier English Values for the supplier property must be stereotyped <<OperationalActivity>>, <<Function>>,<<ServiceFunction>> or their specializations. base_Dependency UPDM An abstract element that represents a structural element that can perform behaviors (i.e. PerformedActivity). DoDAF: NA CapableElement true extension_ composite UPDM Artifact: Super type for many of the UPDM elements. It provides a means of extending UPDM elements in a common way. With links to the measurement set, it also allows quantitative metrics to be associated with structural and behavioral elements. UPDMElement Standard that this UPDM element is conforming to. conformsTo * Unique identifier for the element. URI Types of measurements corresponding to the actual measurements. propertySet * The actual measurements to which the element must conform. actualPropertySet * Start time of a boundary. startBoundaryType End time of boundary. endBoundaryType true The SOPES profile comprises a the core elements of the Shared Operational Picture Exchange Services (SOPES) Information Exchange Data Model (IEDM) modeling profile described in the Annex A of the OMG SOPES IEDM Specification. The modeling profile seek to use UML to expressing the policies, rules and constraints governing the release and exchange of information between information systems. The UML models provide a means to express these exchange policies in an manner that can be encoded as a set of human and machine readable policies that can be enforced by software applications and services. The goal for adding SOPES to the UPDM is to provide greater fidelity for architecture modeling of information exchange requirements within the DoDAF, MODAF and NAF. Additional elements in the SOPES modeling profiles can be accomplished using standard UML Class diagram constructs and not specifically integrated into the UPDM Specification.ion. SOPES A specialization of "InformationElement" the enables the specification of reusable information building blocks, upon which multiple community semantics can be built. Transactionals describe the constructions plans for data sets realizable from the underlying information/data store. The transactional links the community semantics to the structures and business rules information/data store.e. Transactional Transactional.ownedAttribute English ownedAttribute property value must be stereotyped <<TransactionalAttribute>> or its specializations. base_DataType The "identifier" identifies the subtended Class that holds Unique Identifier or Key needed for the construction of the data set. This subtended class would contain, as a minimum, the base Global Unique Identifier (e.g., Database Key, foreign keys or unique identifier) that would differentiate which transactional or wrappers (information element instances) are included in the construction of the composite. (e.g., foreign key relationships) There exists one and only one "identifier" on each semantic or transactional diagram.m. identifier Represents the relationship between a "Transactional" and its containing "Transactional". Meaning that during the data aggregation process of data represented by the "Transactional" is gathered into the containing "Transactional".". containedTransactionals * Represents the relationship between a "Wrapper" and its containing "Transactional". Meaning that during the data aggregation process of data represented by the "Wrapper" is gathered into the containing "Transactional".. containedWrappers * A specialization of "EntityItem" that links a Transactional to the logical information/data model Elements (e.g., DB Table). Wrappers represent a single instance of "EntityItem" data. Wrapper Wrapper.ownedAttribute English ownedAttribute property value must be stereotyped <<WrapperAttribute>> or its specializations. base_Class A specialization of "InformationElement" the enables the specification of a complete dataset, which is considered meaningful to a community, organization, system or application; meeting one or more of the information flow requirements specification for a needline. The semantic is defined by the community, needline or application interface.. Semantic Semantic.ownedAttribute English ownedAttribute property value must be stereotyped <<SemanticAttribute>> or its specializations. base_DataType The "identifier" identifies the subtended Class that holds Unique Identifier or Key needed for the construction of the data set. This subtended class would contain, as a minimum, the base Global Unique Identifier (e.g., Database Key, foreign keys or unique identifier) that would differentiate which transactional or wrappers (information element instances) are included in the construction of the composite. (e.g., foreign key relationships) There exists one and only one "identifier" on each semantic or transactional diagram.m. identifier Represents the relationship between a "Transactional" and its containing "Semantic". Meaning that during aggregation process of data represented by the "Transactional" is gathered into the containing "Semantic". When all the data represented by the "Transactionals" is gathered - the data set is complete and ready for formatting and exchange.e. containedTransactionals * extension_Semantic composite extension_SemanticAttribute composite extension_WrapperAttribute composite Specialization of Entity Attribute that enables the relationship between logical/Interim-Processing and Operational/Business naming conventions. SemanticAttribute base_Property extension_Wrapper composite Specialization of Entity Attribute that enables the relationship between logical and Interim processing Attribute naming conventions.. TransactionalAttribute base_Property extension_TransactionalAttribute composite extension_Transactional composite extension_Constract composite Specialization of Entity Attribute that enables the relationship between physical and logical attribute naming conventions. WrapperAttribute base_Property A specialization of an "OperationalExchange" a "Contract" specifies an agreement between two or more parties to exchange information. The Contract forms an ontological commitment between parties in a community of interest (CoI) or Community of Practice (CoP). The contract is also used to realize the information exchange requirements of either a needline or a community of interest.est. Contract Contract.conveyed English conveyed property value must be stereotyped <<Semantic>>, <<Transactional>> or their specializations. base_InformationFlow A library of Measurements, MeasurementSets and SecurityAttributesGroup, derived from DoDAF. DoDAF Class Library Properties detailing aspects of Resource Interfaces. CommunicationsLinkProperties capacity infrastructureTechnology Predefined additional DoDAF properties for InformationElement. InformationElementProperties Scope scope * Content content * Accuracy accuracy * Language language * Properties indicating the assurance of a piece of information. InformationAssuranceProperties nonRepudiationProducer * accessControl * availability * confidentiality * disseminationControl * integrity * nonRepudiationConsumer * Enumeration of types of security classification, derived from DoDAF. ClassificationType Secret S Top Secret TS Unclassified U Confidential C COSMIC TOP SECRET CTS COSMIC TOP SECRET - BOHEMIA CTS-B COSMIC TOP SECRET - BALK CTS-BALK COSMIC TOP SECRET ATOMAL CTSA NATO Confidential NC NATO Confidential Atomal NCA NATO Restricted (similar to US For Official Use only)) NR NATO Secret NS NATO Atomal NS-A NATO Secret NS-S NATO Secret Atomal NSAT NATO Unclassified NU Restricted Data (RD) US Nuclear Information OR FOR OFFICIAL USE ONLY R Properties detailing aspects of exchange for Operational Exchange and/or Resource Interaction. ExchangeProperties throughput * accountability * interoperabilityLevelAchievable * classification * classificationCaveat * criticality * periodicity * protectionDuration * protectionSuspenseCalendarDate * protectionTypeName * timeliness * transactionType * protectionDurationCode * releasability * size * Properties detailing aspects OperationalActivities. OperationalActivityProperties cost W3C XML Schema for the Intelligence Community Metadata Standard for Information Security Marking (IC-ISM), which is part of the IC standards for Information Assurance. SecurityAttributes classificationReason SCIControls SARIdentifier releasableTo classification dateOfExemptedSource typeOfExemptedSource nonICmarkings declassException declassEvent declassDate derivedFrom classifiedBy FGIsourceProtected FGIsourceOpen DisseminationControls DeclassManualReview ownerProducer Properties detailing the aspects of a DataElement. DataElementProperties accuracy scope content formatType mediaType unitOfMeasurement org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm org.omg.xmi.nsURI http://www.omg.org/spec/UPDM/20120301 org.omg.xmi.nsPrefix updm org.omg.xmi.nsPrefix updm