If you went through the previous sections of the manual, you probably noticed that a large number of element properties were either marked “Data is stored in element’s ToDo property” or replaced by relationships in UPDM.
“Data is stored in element’s ToDo property” indicates that element properties which can not be mapped will be placed in element’s ToDo property. For example, if you have Capability in a DoDAF project that has mission property defined, the migration mission value will be placed in the ToDo property of Capability in the following text form: “DoDAF mission = UseCase [Element Name]”.
Value of the element property that does not map is placed in owner’s ToDo property.
Use the Find ToDo feature to search for elements containing ToDo information. From the Edit main menu, choose Find ToDo.
The following migration issues require properties to map relationships:
- Implements and implementedBy properties of DoDAF elements are mapped to implementsOperational relationship. Relationship source is implements property owner and target is implementedBy property owner. As you will notice, these properties also exist in UPDM. However, they are derived ones and as such can not be edited, which means they are calculated from implementsOperational relationships.
- Performs and performedBy properties of DoDAF elements are mapped to performs relationship. Relationship source is a performs property owner and target is a performedBy property owner.
Problems can also arise when UML or SysML relationships are used instead of UPDM ones. All these are explained in Data Mapping chapter.