Difference between revisions of "Quality Assurance VAG"
| Line 21: | Line 21: | ||
= Use Cases = | = Use Cases = | ||
Use cases for this VAG are derived from normal software development practice. A few representative use cases will be provided, but the general requirement for QA is assumed not to require further justification. | |||
= Architectural Descriptions/Views used to express this viewpoint = | |||
This section identifies: | |||
# the general form or representation of [[Architecture_Working_Group_Glossary#Architectural descriptions and views (ADV)|ADV]]s required to express the viewpoint | |||
# the elements within such ADVs which will be used to express the viewpoint | |||
# how these elements within such ADVs map to the concerns of this viewpoint | |||
# the traceability to viewpoint concerns required for conformance with the viewpoint. | |||
None decided. | |||
= Tools employed by this VAG = | |||
* Normal wiki textual and graphic representations are expected to be sufficient for this VAG. | |||
* Programmed tools are expected to be developed for scalability testing and measurement. | |||
= Organization = | = Organization = | ||
| Line 46: | Line 61: | ||
* TBD | * TBD | ||
Revision as of 02:53, 22 October 2007
- This is an early draft so scope and focus are still fairly open. Please add comments to the Talk:Quality Assurance VAG if you have slightly different concerns so that we can try to converge on a common viewpoint. This discussion could also expose other similar VAGs that are needed in this area.
Purpose
The Quality Assurance Viewpoint Advocacy Group exists to assist with Software Quality Assurance within the architectural design group, both in terms of architectural project quality and also downstream design/implementation quality.
See the Architecture Working Group and the Viewpoint Advocacy Groups for more information.
Areas addressed by this viewpoint
Areas not addressed by this viewpoint
Source of Viewpoint
No existing sources for this viewpoint have (yet) been sought. This viewpoint is however highly reusable, and therefore existing sources are very likely to exist and should be investigated.
List of concerns in this viewpoint
Areas of concern central to this viewpoint include the following:
Use Cases
Use cases for this VAG are derived from normal software development practice. A few representative use cases will be provided, but the general requirement for QA is assumed not to require further justification.
Architectural Descriptions/Views used to express this viewpoint
This section identifies:
- the general form or representation of ADVs required to express the viewpoint
- the elements within such ADVs which will be used to express the viewpoint
- how these elements within such ADVs map to the concerns of this viewpoint
- the traceability to viewpoint concerns required for conformance with the viewpoint.
None decided.
Tools employed by this VAG
- Normal wiki textual and graphic representations are expected to be sufficient for this VAG.
- Programmed tools are expected to be developed for scalability testing and measurement.
Organization
Joining
Anyone with an interest in this Viewpoint is welcome to join. You should join the AW_Groupies group in Second Life.
In world meetings
We meet once a week in-world and more if people are available.
Also members are active on the wiki and in the SLDEV mailing list.
Meetings Schedule:
Meeting Agendas
- TBD
Chat Logs
- TBD
External Links
Members (Stakeholders)
Please note that the Quality Assurance VAG is a non-hierarchical VAG in every respect, without exception. Any tags supplied with names are purely informational. Stakeholder ordering is alphabetical.
- Morgaine Dinova 02:43, 18 October 2007 (PDT) - Founder, analyst