Difference between revisions of "Viewpoint Advocacy Groups"
Jump to navigation
Jump to search
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) |
Dzonatas Sol (talk | contribs) (change to reflect view in a non-political organization) |
||
| Line 1: | Line 1: | ||
(This is an early draft document, created for feedback purposes. It does not reflect a consensus recommendation, or statement of policy at this this.) | (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 | 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 tasks to focus on specific requirements. The list of Viewpoint Advocacy Tasks 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 | The core goal of the AWG is as follows: | ||
* Integrate the requirements of each Viewpoint Advocacy Group. | * Integrate the requirements of each Viewpoint Advocacy Group. | ||
| Line 13: | Line 13: | ||
* Integrate feedback from the various viewpoint advocacy groups. | * Integrate feedback from the various viewpoint advocacy groups. | ||
From there we work with each Viewpoint Advocacy Task, as follows: | |||
* Document architectural views of the group. | * Document architectural views of the group. | ||
| Line 19: | Line 19: | ||
* Consider the architectural needs of specific likely implementations that fulfill the view's requirements. | * 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. | * Operate in a way that allows for alternate implementations that satisfy the viewpoint. | ||
* Work with the core | * Work with the core goals to document views and requirements that conflict or are inconsistent. | ||
* Review the core | * Review the core goals against the work output to ensure that the view's requirements are met. | ||
== List of VA-Groups == | == List of VA-Groups == | ||
Revision as of 15:08, 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 tasks to focus on specific requirements. The list of Viewpoint Advocacy Tasks 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 core goal of the 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.
From there we work with each Viewpoint Advocacy Task, 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 goals to document views and requirements that conflict or are inconsistent.
- Review the core goals against the work output to ensure that the view's requirements are met.
List of VA-Groups
- Lorem
- Ipsum