-
Key: UAF13-26
-
Status: open
-
Source: Air Force Institute of Technology ( Steve Glazewski)
-
Summary:
(typo) Page 72, View Specifications::Resources::Roadmap::Resources Roadmap: Evolution has a Stakeholder named "Implements" and I think you mean "Implementers" as is used in other areas.
(typo) Page 83, View Specifications::Projects::Taxonomy::Project Taxonomy doesn't put the Stakeholders, Concerns, Definition, and Recommended Implementation on separate lines like every other View Specification does.Page 31, View Specifications::Operational::Connectivity::Operational Connectivity and Page 37, View Specifications::Operational::Constraints::Operational Constraints both have a Stakeholder named "Architects" whereas all other View Specifications specify one or several types of Architects. Are all other named types of Architects assumed?
In general, what are your definitions/assumptions for Business Architects versus Enterprise Architects versus IT Architects, all of which are used as Stakeholders in various View Specifications?
What are your definitions/assumptions for Solution Providers versus Implementers, both of which are used as Stakeholders?
What are your definitions/assumptions for Decision Makers versus Executives versus Owners Responsible for Operational Agents, all of which are used as Stakeholders in various View Specifications?Page 37, View Specifications::Operational::Constraints::Operational Constraints contains a Stakeholder called Program Sponsor. What is your definition for "Program" or that overall Stakeholder?
-
Reported: UAF 1.1 — Tue, 5 Apr 2022 18:59 GMT
-
Updated: Fri, 20 Dec 2024 14:57 GMT
UAF13 — Ambiguity regarding Stakeholder role expectations
- Key: UAF13-26
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF