The intent of the mapping between AADL and FACE can be unclear in places where the FACE Technical Standard describes source code (e.g., specifications that generate header files) and the AADL describes deployed code (e.g., a thread).
The annex should clearly differentiate these interpretations and state how they apply to the mapping.
For example, the boundaries of a UoP in FACE are not necessarily aligned directly with the boundaries of a UoP modeled in AADL as a thread group. The latter can have other software libraries linked to it that the former cannot.
The intent of the mapping between AADL and FACE can be unclear in places where the FACE Technical Standard describes source code (e.g., specifications that generate header files) and the AADL describes deployed code (e.g., a thread).
The annex should clearly differentiate these interpretations and state how they apply to the mapping.
For example, the boundaries of a UoP in FACE are not necessarily aligned directly with the boundaries of a UoP modeled in AADL as a thread group. The latter can have other software libraries linked to it that the former cannot.