Difference between revisions of "Viewpoint Advocacy Groups"
Jump to navigation
Jump to search
Gigs Taggart (talk | contribs) (New page: (This is an early draft document, created for feedback purposes. It does not reflect a consensus recommendation, or statement of policy at this this.) Stakeholders in the Architecture ha...) |
Dzonatas Sol (talk | contribs) m (Viewpoint Advocacy Groups moved to Viewpoint Advocacy Task: serious, to keep focus of the right direction, keep in mind about COST, and avoid bureaucracy) |
(No difference)
|
Revision as of 15:04, 11 October 2007
(This is an early draft document, created for feedback purposes. It does not reflect a consensus recommendation, or statement of policy at this this.)
Stakeholders in the Architecture have various agendas, goals, and viewpoints. These views are critical to the design of the new grid. This proposal is to create subgroups with specific focus on particular requirements. The list of Viewpoint Advocacy Groups may grow and shrink during the course of this project. The idea here is to provide a framework to address specific concerns in a systematic way.
The goal of the core AWG is as follows:
- Integrate the requirements of each Viewpoint Advocacy Group.
- Negotiate and document conflicts between viewpoints.
- Document rationale for architectural decisions.
- Produce a coherent architecture.
- Integrate feedback from the various viewpoint advocacy groups.
The goal of each Viewpoint Advocacy Group is as follows:
- Document architectural views of the group.
- Document specific architectural requirements that stem from this view.
- Consider the architectural needs of specific likely implementations that fulfill the view's requirements.
- Operate in a way that allows for alternate implementations that satisfy the viewpoint.
- Work with the core AWG to document views and requirements that conflict or are inconsistent.
- Review the core AWGs work output to ensure that the view's requirements are met.
List of VA-Groups
- Lorem
- Ipsum