Related to and part of Issue FACE 11-2: Update standard to FACE 3.1

When FACE 3.0 transitioned to FACE 3.1 (with the newly-extracted UDDL v1.0 standard included for the FACE Data Model), multiple metamodel elements in the FACE Metamodel were renamed to remove the prefix IDL from their names. Some were also refactored in response to the removal of other unused or unnecessary FACE metamodel elements. Rename Platform package stereotypes that include "IDL" in their name to non-"IDL" names in accordance with the changes between FACE 3.0 and FACE 3.1 metamodels. In some cases, the renamed elements will also assume attributes and generalizations of their former "parent" elements. Honor that as well.

Note that renaming the corresponding stereotypes implies also updating any references to the renamed stereotypes, including in diagrams.

The FACE Profile 1.0 stereotypes affected and the target names for each are:
FACE_IDLArray -> FACE_Array
FACE_IDLBoundedString -> FACE_BoundedString
FACE_IDLCharacterArray -> FACE_CharArray
FACE_IDLComposition -> FACE_StructMember
FACE_IDLInteger -> FACE_Integer
FACE_IDLNumber -> FACE_Number
FACE_IDLPrimitive -> FACE_Primitive
FACE_IDLReal -> FACE_Real
FACE_IDLSequence -> FACE_Sequence
FACE_IDLStruct -> FACE_Struct
FACE_IDLType -> FACE_PlatformDataType
FACE_IDLUnsignedInteger -> FACE_UnsignedInteger

Related to and part of Issue FACE 11-2: Update standard to FACE 3.1

When FACE 3.0 transitioned to FACE 3.1 (with the newly-extracted UDDL v1.0 standard included for the FACE Data Model), multiple unused or unnecessary metamodel elements with the prefix IDL were removed from the FACE Metamodel. Remove the corresponding stereotypes from the FACE 3.1 standard.

Note that deleting the corresponding stereotypes implies also removing any references to the deleted stereotypes, including in diagrams.

Original Issue text, INCORRECT: metamodel elements deleted from the FACE 3.1 standard are:
IDLBoundedString
IDLCharacterArray
IDLUnboundedString

Corrected Issue:
Delete CharArray (will be replaced by renamed IDLCharacterArray)
Delete FACE_BoundedString (will be replaced by renamed FACE_IDLBoundedString)
Delete FACE_IDLUnboundedString

If it falls within the scope of the RTF, update the standard to reflect the changes between FACE 3.0 data architecture and the FACE 3.1 data architecture.

The v1.0 version of the FACE Profile specification has hard-coded figure numbers and absolute references for hyperlinks between stereotype detail descriptions. These references need to be changed so that, when an organizational change (move, delete, addition) occurs in the specification, figure numbers and hyperlinks can be updated automatically.

These hard-coded values originated in generation of content for the standard from a model into document using a template. The hyperlinks are pervasive in the section, with the intent of easing navigation to related stereotypes when using the standard.

According to notes from the FACE Profile for UAF 1.0 artifact set, the text of the Constraint specifications in the model used for the v1.0 XMI were newer than the ones used to generate the Constraint specifications in the printed document. The changes in the Constraint specifications may need to be addressed in an issue in the RTF to bring the printed specification and the machine-readable specification into alignment.

The bulk of the standard is UML only, with only a loose coupling between the UML and UAF elements. Because the strict connection to only the UAF specification artificially prevents use of the profile in UML and SysML models, separate the UML-only and UAF-specific portions of this specification into separate subsections, with conformance points to describe different language mappings.

This is likely to impact both the printed and machine-readable portions of the specification.

The standard specifies the information to be included in tabular analysis views to be included in implementations of the standard, but lacks examples. Provide examples of the expected views.

Add an informative paragraph with recommendations for use of the profile with SysML. Describe how the UML-based profile would apply in a SysML environment. Possibly implement as an informative annex to the printed standard.