Release date: 27th May 2013
1.1. UPDM 2.1 Support
1.2. Desired Effect Relationship Representation
1.3. Predefined Relationship Maps
1.4. Architectural Description as a Root Element
1.5. Blank EA Project
1.6. Redefinition of Inherited Information Flows
OMG UPDM 2.1 formal specification dtc/2012-10-0312-03 is supported with UPDM 2 Plugin version 17.0.4. UPDM projects created with earlier versions of the UPDM 2 Plugin are automatically migrated to support the OMG UPDM 2.1 specification.
The UPDM 2 Plugin version 17.0.4 introduces the ability to show an element’s states within the expanded structural compartment of an element. This capability enables to create a Desired Effects relation from a Desirer directly to the applicable Operational / Resource states in these simple ways:
- From the smart manipulator toolbar of the selected Desirer, choose the Desired Effect relationship and drag it to the appropriate Operational / Resource state
- Drag the chosen desirer and drop it onto the appropriate Operational / Resource state
The UPDM 2 Plugin version 17.0.4 includes eight predefined relation maps. These predefined relation maps collect and present the information from the model according to the chosen context and scope. Each such relation map has both predefined relation criteria and element types.
The eight predefined relation maps are:
- Capability Structural Map
- Capability Behavioral Map
- Implementation Map
- Operational Activity Implementation Map
- Operational Activity Map
- Organization Structure Map
- System Resource Map
- Variant Map
In UPDM 2 Plugin version 17.0.4, the initial, default Architectural Description appears as a member of the project’s root package, having moved from the AV-1 package in prior versions. The ability to create the additional Architectural Description and to store it in the AV-1 package retains.
A new Project Template, “Blank UPDM Project” is provided along with the traditional “UPDM Project” Template. The project created from the Blank UPDM Project can have all the capabilities of one created with the traditional UPDM Project Template—it simply lacks the Viewpoint Packages for each UPDM Viewpoint that the traditional template provides. With this “Blank UPDM Project” Template, the user who has the objective of modeling only a subset of all the available UPDM Viewpoints can begin their modeling without having to delete unnecessary packages provided by a template project.
The choices of Architectural Frameworks for the Blank UPDM Project Template are:
- DoDAF 2.0
- DoDAF 1.5
When modeling the various forms of exchanges that Operational and Systems elements inherit from generalizing elements, the user can now formally redefine these exchanges along with their information—such as Actual Measurements, Conveyed Items, and Documentation. The UPDM 2 Plugin version 17.0.4 properly creates the necessary redefine relationships in the model to record the intentional redefinition of inherited relationships.
On an Information Flow, when the same Exchange Item is conveyed several times, UPDM 2 Plugin version 17.0.4 displays only one instance of the name on the applicable connector when drawing diagrams. The ability to model multiple Information Flows between elements each with their own distinct or overlapping sets of Exchange Items retains.
To open the list of publicly available or your own issues those have been included into version 17.0.4 FR, click here.
Note: You will be required to login. Use the same login name and password as for www.nomagic.com.
You may find many more possible solutions for known issues at No Magic Community Forum that is regularly updated with new topics.