-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
first try of an ADR covering concerns and concepts
- Loading branch information
1 parent
0e89a48
commit c347166
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
22 changes: 22 additions & 0 deletions
22
documentation/decisions/009-crosscutting-concerns-and-concepts.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# 008: Architects are able to specify quality requirements | ||
|
||
## Status: Accepted | ||
|
||
## Context | ||
Within the FOUNDATION level working group we had long (aka _endless_) discussions about quality and quality requirements. | ||
Conclusion is: | ||
|
||
* Software architects shall be able to formulate precise quality requirements, i.e. as quality scenarios. | ||
* The shall not _invent_ these, but formulate in cooperation or collaboration with other stakeholders. | ||
|
||
## Rationale: | ||
|
||
* The ability to formulate such requirements in precise and practically usable ways is part of many CPSA-Advanced level certifications, therefore it *must* be taught and practiced within foundation level trainings. | ||
|
||
|
||
## Consequences: | ||
|
||
We discussed this topic within GitHub issues: | ||
|
||
* [#597](https://github.com/isaqb-org/curriculum-foundation/issues/597) proposed a somewhat weaker formulation (_know how to formulate scenarios..._). We decided to keep the existing "_are able to_". | ||
* In [#501](https://github.com/isaqb-org/curriculum-foundation/issues/501) we decided to elevate quality scenarios to R1. |