Data mapping mostly has to do with migrating elements and their relationships to UPDM. As mentioned in section 3 above, there are a lot of conceptual changes between DoDAF and UPDM projects. Table 2 below describes entity mapping and Table 3 relationships mapping.

DoDAF 1.5 UPDM 1.x Properties 

Comments

Asset [Class] 

ConceptRole [Property]

actualImplementation to type representationType. Data is
stored in element’s ToDo property.

Concept role is placed under the High Level Operational Concept element.

Capability [UseCase]

Capability [Class]

mission: Data is stored in element’s ToDo property.

operationalThread to ownedBehavior.


CommunicationsNetwork [Class]

System [Class]

securityClassification: Data is stored in element’s ToDo
property.


CommunicationsPath [Class]

System [Class]

communicationLinks: Data is stored in element’s ToDo property.


CommunicationsSystem
[Class]

System [Class]



Hardware/SoftwareItem
[Class]

System [Class]

vendors/source: Data is stored in element’s ToDo property.


InformationElement [Class]

InformationElement [Class]


ImplementsOperational relationship is created between
Information Element and its implementer if any.

InformationExchange
[InformationFlow]

InformationExchange
[InformationFlow]

consumedBy: Data is stored in element’s ToDo property.

producedBy: Data is stored in element’s ToDo property.

mission: Data is stored in element’s ToDo property.


LAN [Class] 

System [Class]



MAN [Class] System [Class]

Milestone [State]

ConfigurationDeployed [InstanceSpecification]

version: Data is stored in element’s ToDo property.

timePeriod to date.


Objective [UseCase]

EnterpriseGoal [Class]



OperationalActivity [Activity]

OperationalActivity [Activity]

capability: Data is stored in element’s ToDo propertyconsumes does not map.

levelIdentifier: Data is stored in element’s ToDo
propertyperformedAt does not map.

produces: Data is stored in element’s ToDo property.

ImplementsOperational relationship is created between
OperationalActivity and its implementer if any.

OperationalActivityAction
[CallBehaviorAction]

OperationalActivityAction
[CallBehaviorAction]



OperationalNode [Class]

OperationalNode [Class]

levelIdentifier: Data is stored in element’s ToDo
propertyoperationalRole does not map.

performers: Data is stored in element’s ToDo property.

If isExternal is true ExternalNode should be created instead of OperationalNode.

OperationalNodeUsage
[Property]

NodeRole [Property]

operationalRole: Data is stored in element’s ToDo property.


OperationalRule [Constraint]

OperationalRule [Constraint]

type to kind.

Organization [Class]

ActualOrganization
[InstanceSpecification]

responsibility: Data is stored in element’s ToDo property.


OrganizationalResourceUsage [Property]

SubOrganization [Property]



OrganizationType [Class]

Organization [Class]



Performance Measurement
[Slot]

ActualMeasurement [Slot]



PerformanceMeasurementSet
[InstanceSpecification]

ActualMeasurementSet
[InstanceSpecification]

measuredSystem to measuredElement.


PerformanceParameterSet
[Class]

MeasurementSet [Class]

measuredSystems to measuredElement.


PerformanceParameterType [Property]

PerformanceParameter
[Property]

objectiveValue to propertyValue

thresholdValue to maxValue.

unitOfMeasure: Data is stored in element’s ToDo property.


Performer [Class]


performs: Performs relationship are created between performer and performed Elements.


Person [Class]

ActualPerson [InstanceSpecification]

responsibilities: Data is stored in element’s ToDo property.

roles: Data is stored in element’s ToDo property.


ReferenceModel [Package]

UML Package 

source: Data is stored in element’s ToDo property.


Responsibility [Class]

Competence [Class]

persons: Data is stored in element’s ToDo property.

roles: Data is stored in element’s ToDo property.


Role [Class] 

PostRole [Property]

persons: Data is stored in element’s ToDo property.

responsibilities: RequiresCompetence relationships are created between PostRole and Competences.


Service [Package]

Resource [Class]

status: Data is stored in element’s ToDo property.


ServiceArea [Package]

UML Package 

version/date: Data is stored in element’s ToDo property.


ServiceSpecification [Class]

ServiceInterface[Interface]

serviceDescription: Comment is added.


SoaService [Port]

ServicePoint [Port]



Standard [Class]

Standard [Class]



Standards/Performance Subject [Element]

UPDMElement [Element]

measurements to actualMeasurements.

performanceParameterSet to measurementTypes.


StandardsForecastProfile
[Package]

View (SysML) with conforms
to TV-2

basedOn: Data is stored in element’s ToDo property.


StandardsProfile [Package]

View (SysML) with conforms
to TV-1

applicableDate: Data is stored in element’s ToDo property.

basedOn: Data is stored in element’s ToDo property.


System [Class]

System [Class]

participant: Data is stored in element’s ToDo property.

performedFunctions : Performs relationship is created
between function and System.


SystemDataElement [Class]

DataElement [Class]



SystemDataExchange
[InformationFlow]

ResourceInteraction [InformationFlow]

consumedBy: Data is stored in element’s ToDo property.

producedBy: Data is stored in element’s ToDo property.


SystemDataRepository
[DataStoreNode]

Does not map

SystemFunction [Activity]

SystemFunction [Activity]

allocatedAt: Allociation relationship to Systems Node
should be created.

consumes: Data is stored in element’s ToDo property.

parent: Aggregation relationship is created between System Function and parent System Function.

performedBy: Performs relationship is created between System Function and System.

produces: Data is stored in element’s ToDo property.

subfunction: Aggregation relationship is created between System Function and child System Function.


SystemFunctionAction
[CallBehaviorAction]

SystemFunctionAction
[CallBehaviorAction]



SystemRule [Constraint]

ResourceConstraint
[Constraint]

type to kind

SystemsNode [Class]

SystemsNode [Class]

allocatedFunctions: Allociation relationship from System
Function should be created.

ImplementsOperational relationship is created between
Systems Node and its implemented elements if any.

SystemsNodeUsage
[Property]

UsedConfiguration [Property]



SystemUsage [Property]

Subsystem [Property]

participant: Data is stored in element’s ToDo property.


TargetArea [Class]

Location [DataType]



Technology [Class]

Artifact [Class]



TechnologyForecastProfile
[Package]

UML Package 

basedOn: Data is stored in element’s ToDo property.

timePeriod: Data is stored in element’s ToDo property.


TimePeriod [TimeConstraint]

ISO8601Date Time [LiteralString]



TimePeriodList [Class]

Timeline [Package]

timePeriods to ownedElements.


WAN [Class] 

System [Class]



Backup [Usage]

ResourceInteraction
[InformationFlow]


Name is set to "Backup"

CommunicationsLink
[Association, Connector]

SystemConnector [Association, Connector]

communicationsPath: Data is stored in element’s ToDo
property.


Contributing [Usage]

ResourceInteraction
[InformationFlow]


Name is set to "Contributing"

Coordination [Usage]

ResourceInteraction
[InformationFlow]


Name is set to "Coordination"
Direct [Usage] 

Commands
[InformationFlow]



Indirect [Usage]

ResourceInteraction
[InformationFlow]


Name is set to "Indirect"

InformationFlow
[ControlFlow, ObjectFlow]

OperationalActivityEdge
[ActivityEdge]

Interface [Association, Connector]

SystemConnector [Association, Connector]


ImplementsOperational relationship is created between
System Connector and its implemented elements if any.

Line [Association]

ArbitraryRelationshipConnector
[Connector]

representationType: Data is stored in element’s ToDo property


Needline [Association, Connector]

Needline [Association, Connector]


ImplementsOperational relationship is created between
Information Elemented and its implementations if any.

OrganizationalRelationship
[Usage]

ResourceInteraction
[InformationFlow]


Name is set to "OrganizationalRelationship".

SituationDependent [Usage]

ResourceInteraction
[InformationFlow]


Name is set to “SituationDependent”.

TimedStandardsForecast
[Usage]

Forecast [Dependency]

discussion: Data is stored in element’s ToDo property.

requires: Data is stored in element’s ToDo property.

standardStatus: Data is stored in element’s ToDo property.

timePeriod to startDate.


TimedTechnologyForecast [Usage]

Forecast [Dependency]

discussion: Data is stored in element’s ToDo property.

requiredBy: Data is stored in element’s ToDo property.

retiredStandard: Data is stored in element’s ToDo property.

timePeriod to startDate.


Entity and relationship mapping raises further issues that requires specific solutions, all of which are described in sub-section 3.3.