The purpose of this document is to document a specific quality attribute of a system, such that it can be consistently specified by a technical architect and discussed by the delivery team during implementation.
| Version | Issued | Comments |
|---|---|---|
| 0.1 | dd-MM-yyyy | … |
| Role | RACI |
|---|---|
| … | … |
| Review frequency | Next review due |
|---|---|
| ? | ? |
<Definition of the quality attribute.>
<Is this a runtime (e.g. performance) or development (e.g. modifiability) concern?>
<How is it specified. metrics? (E.g. "mean time to fix a defect" for modifiability).>
<Describe how this quality attribute relates to other quality attributes. Discuss any key conflicts or trade-offs that might need to be made.>
<Describe our standard approach to testing this quality attribute. This could be automated testing, expert review or somewhere in between.>
<Describe the relevant standards associated with the quality attribute.>
<Describe any legislation or regulation with which we are required to comply and how this compliance would typically be achieved.>
<Document the tactics / practices that allow each QA to be achieved (SAiP, p70). For example, indirection is a tactic to allow modifiability.>
<Provide any relevant appendices.>
<Provide any relevant references.>