UAF11-11 |
Add a 3-way Resource Traceability Matrix as a standard view |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-48 |
ResourceInteractionKind should really be called ResourceExchangeKind. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-276 |
Improve quality of DMM diagrams |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-294 |
modify title and text for DMM diagram legend |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-86 |
Sv-Pr implementation should be BDD and Activity diagram and table |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-82 |
Mapping for UAF views to DoDAF/MODAF Views problem |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-99 |
Sc-Tx should be mapped to BDD |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-98 |
Implementation for Sv-Tr should be tabular. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-94 |
Pr-Ct mapping should include the OV-4 Actual as a potential mapping. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-93 |
Inconsistent naming for State Diagrams |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-87 |
Ov-Ct and Sv-Ct recommended implementation should both be BDD |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-106 |
OV-1a should not be mapped as Op-Sr and SmOV |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-105 |
OV-1b should be mapped to the SmOV |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-103 |
Sd mappings are wrong in Annex B: |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-102 |
Pj mappings are wrong in Annex B |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-110 |
The changes to KnownResource don’t make any sense to me. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-107 |
OV-1c and SV-7 are better fits for Pm-Me. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-124 |
Document inconsistency between EnterprisePhase and CapableElement |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-123 |
Document inconsistency between AssetRole and SecurityProperty |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-121 |
Inconsistency between text/figure for ResponsibleRoleKind |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-128 |
Inclusion of additional CapableElements |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-53 |
InformationElements and DataElements location and constraints. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-49 |
OperationalExchange.trustlevel should be called OperationalExchange.trustLevel |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-46 |
ResponsibleFor.ResponsibleRoleKind tag wrong. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-77 |
UAFP Inheritance from SysML issues. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-76 |
Operational agent should own operational operation. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-63 |
Figure 179 for ActualProjectMilestone error |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-59 |
SubjectOfSecurityConstraint doesn’t allow you to constrain any elements from the SecurityDomain |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-57 |
SecurityControlFamily has a constraint for annotedElement |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-73 |
CapabIlityProperty should be shown with Dependencies |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-70 |
Figure 260 for Security Processes issues. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-69 |
Should have an IBD version for the Operational Taxonomy view |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-300 |
Update DMM sections on UAF grid, Domain interelatiohips and descriptions |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-298 |
Update and add sections 1 through 6.4 from UAFP and move to UAF DMM document |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-80 |
Op-Cn should be mapped to OV-2 and OV-3 |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-15 |
Required Environment needs to be individual as opposed to type |
UAF 1.0b2
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-16 |
Security Property name change |
UAF 1.0b2
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-21 |
Add 3D representation of domain connectivity |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-20 |
Update UAF Grid |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-30 |
UAF is not considered DoDAF 2.02 compliant |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-25 |
NAF 4 conformance |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-7 |
Proof of DoDAF Conformance – Meta Model – DM2; LFL Issue #1 (11 September 2017). |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-43 |
Figure 53 for Achiever shows AchievedEffect twice. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-39 |
EnterpriseVision.statement should be derived or removed. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-36 |
Actual Enterprise Phase: Concern.systemConcern incorrect name. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-35 |
Multiplicity wrong for Actual Enterprise Phase: forecastPeriod tag |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-33 |
Constraints [c] and [d] for Implements.supplier should be merged |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-160 |
There should be a depiction for ServiceObjectFlow and ServiceControlFlow, |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-157 |
Multiple diagrams show inconsistencies between themselves |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-85 |
There is no example of an Op-Tr. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-84 |
Worked example should have all diagrams. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-83 |
Worked example structure needs changing |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-81 |
Inconsistency between example and specification |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-100 |
Sc-Pr example doesn’t match the specification. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-92 |
Pr-Sr should be OV-4 typical |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-89 |
There’s no example of the Sv-Rm view. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-104 |
Ar-Sr should be mapped to BDD. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-111 |
OwnsProcess should be shown on Figure 76. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-114 |
ServiceOperation should be shown on Figure 89. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-112 |
ProtocolImplementation should be shown on Figure 182. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-204 |
Operational Architecture cannot own Operational Port |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-148 |
2) The ServiceFunction diagram (Figure 96) is depicted different then the Operational Activity diagram Figure 78) and the Function diagram (Figure 132) |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-147 |
The UAFElement stereotype has multiple child stereotypes but none appear on the diagram. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-156 |
ActualOrganizationalResource (Figure 194) has no Metaclass |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-155 |
Text for ActualMilestoneKind refers to ActualMeasurements instead of ActualProjectMilestone |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-154 |
On Figure 186, there is no line between ActualOrganizationalResource and ActualProjectMilestone |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-153 |
ProjectRole (Figure 177) does not show as a child of ResourceRole (Figure125) |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-152 |
Inconsistent depiction of VisionStatement |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-150 |
CapabilityForTask is duplicated on the Capability diagram (Figure 40) |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-149 |
Diagram Consistency |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-118 |
Doc inconsistency between ActualOrganizationalResource & ActuralResponsibility |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-125 |
Dual inheritance for ActualService is confusing |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-122 |
Unclear relationship between ActualProject and ActualPropertySet |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-38 |
Figure 40 – Capability, shows CapabilityForTask twice |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-55 |
Figure 163 for Risk doesn’t show a specialization to Block |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-52 |
Figure 140 for DataModel doesn’t show an extension to a UML type. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-47 |
The ResourceRole.RoleKind tag should start with a lowercase letter. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-45 |
Figure103 for OrganizationalResource is missing some relationships. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-75 |
Figure 277 for Services Connectivity should show ServiceSpecificationRole |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-65 |
ActualService doesn’t need to directly inherit from ActualPropertySet |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-64 |
Figure 182 for Protocol should show the relationship to implementers. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-60 |
SubjectOfSecurityConstraint is specialized by Asset but not AssetRole |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-56 |
SecurityControl can't be a specialization of PropertySet and Requirement |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-74 |
Figure 277 for Services Connectivity should show provided/required interfaces |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-66 |
Figure 76 for OperationalActivity is missing OwnsProcess. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-95 |
Pr-Tx should not show structure, just generalizations. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-101 |
Tx and Sr views overlap. |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-108 |
The OwnsRiskInContext has the wrong constraint text |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-5 |
Make the relationship between the definition Statemachines (currently implicitly related to UML statemachines) and the definition of ResourceStateMachines more explicit for readers of the UAF. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-3 |
Make the relationship between UML composition and aggregation (for the information model) and the use of whole/part in the UAF more explicit for readers of the UAF specification document. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-23 |
Update descriptions for MetaData row of Grid |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-13 |
Constraint uses wrong name |
UAF 1.0b2
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-151 |
AchievedEffect is duplicated on the Achiever diagram (Figure 53) |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-117 |
Identify all MeasurableElements in a comprehensive list or table |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-116 |
Provided complete list of UAF PropertySets in table |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-44 |
Figure 88 for ServiceMethod inconsistent |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-41 |
Problem with Figure 214 for Strategic Roadmap |
UAF 1.0
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-40 |
Problems with Figure 49 |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-32 |
Constraint text for Figure 34 is incorrect. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-78 |
Energy should be restored to the UAF. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-62 |
ActualProject specialization wrong |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-72 |
Security Constraints inconsistency |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-71 |
Figure 262 shows an invalid relationship |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-68 |
Abstract stereotypes in the Elements list within Annex A |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-159 |
The diagram for OperationalObjectFlow does not show links to OperationalActivityAction |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-158 |
The diagram for FunctionObjectFlow does not show links to FunctionAction |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-79 |
Op-Tx should be IBD |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-97 |
Rs-Rm implementations should be matrix/tabular and BDD. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-91 |
Typo in the figure 235 text. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-90 |
Sv-Tr should be matrix/tabular and BDD. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-88 |
St-Rm should be mapped to an Object Diagram |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-109 |
XMI has ProjectActivityAction and CallBehaviourAction – shouldn’t include Activity. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-115 |
Problem with ServiceMessageHandler |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-113 |
ProvidesCompetence should also be an abstraction. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-2 |
Make the relationship between UML and the decomposition of Activity based elements more explicit for readers of the UAF specification document. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-1 |
Make the relationship between UML and BPMN for the representation the BPMN Start Event and End Event more explicit for readers of the UAF specification document. |
UAF 1.0
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-19 |
ResponsibleFor relationship from Actual Responsible Resource to Actual Project Milestone is missing in the Responsible For diagram |
UAF 1.0b2
|
UAF 1.1
|
Duplicate or Merged |
closed |
|
UAF11-18 |
Unified Architecture Framework (UAF), The Domain Metamodel document should not be marked as Appendix A for UAFP specification |
UAF 1.0b2
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-28 |
Enteprise Phase should not be a subtype of capable element |
UAF 1.0b2
|
UAF 1.1
|
Resolved |
closed |
|
UAF11-120 |
Missing Metaclass designation in documentation |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-119 |
No diagram representation exists for some model elements |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-127 |
Inconsistency between spec and implementation |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-129 |
Capabilty generalization should be Use Case |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-42 |
Figure 51 for EnduringTask is missing inheritance to SysML::Block |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-37 |
Actual Enterprise Phase: Concern.systemConcern should be 0..1 |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-34 |
Inconsistency with Constraint [e] for Implements.supplier |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-54 |
Problem with EnhancedSecurityControl inheritance |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-51 |
Inconsistency with SecurityProcess and ProjectActivity |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-50 |
Constraints for ResourceInteractionKind.ResourceEnergyFlow don’t make sense |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-61 |
Inconsistency with Project |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-58 |
Abstract stereotypes shouldn't have extensions. |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-12 |
conformsTo is missing |
UAF 1.0b1
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-96 |
OrganizationalResources should not be on a Rs-Tx |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-14 |
Ovierview picture (UAF Grid Overview) |
UAF 1.0b2
|
UAF 1.1
|
Closed; Out Of Scope |
closed |
|
UAF11-6 |
Provide Vendor Neutral exchange format of the UAF DMM |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-4 |
Add the element ResourceRoleKinds to the relevant diagrams in the UAF DMM |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-17 |
Actual Risk should be captured in Security Parameters rather than Security Constraints |
UAF 1.0b2
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-24 |
UAF compliance criteria for Toolvendors |
UAF 1.0
|
UAF 1.1
|
Closed; Out Of Scope |
closed |
|
UAF11-22 |
Add the UAF Metamodel on a page |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-31 |
Definition of FunctionAction is too tight |
UAF 1.0b2
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-29 |
Consumes relationship is facing wrong direction |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-27 |
Stereotypes for flowProperties |
UAF 1.0b2
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-26 |
Concpetual mapping between UAF DMM and Archimate elements |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-10 |
Interoperability and Interchange Testing; LFL Issue #4 (11 September 2017) |
UAF 1.0
|
UAF 1.1
|
Closed; Out Of Scope |
closed |
|
UAF11-9 |
Support Extensibility and Specialization of Architectures (Inheritance and Extension of Architectures; LFL Issue #3 (11 September 2017) |
UAF 1.0
|
UAF 1.1
|
Closed; No Change |
closed |
|
UAF11-8 |
Increase DoDAF Conformance – PES Implementation; LFL Issue #2 (11 September 2017). |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-67 |
The View definition in Annex A are missing stereotypes from the Elements list |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-296 |
Should SubjectOfForecast be an Asset instead of ResourcePerformer? |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-227 |
Achiever cannot be the same as Desirer |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|
UAF11-126 |
Inconsistency between spec and implementation |
UAF 1.0
|
UAF 1.1
|
Deferred |
closed |
|