-
Some links in the glossary seem to be outdated/broken e.g.
http://iso25000.com/index.php/en/iso-25000-standards/iso-25010%7CISO in the Usability Quality Attribute term description
A systematic c…
-
The OPERATIONS section should rather focus on traits that support the evolution - no matter whether Build-for-replacement or Build-and-evolve - of a business services. The curriculum should explain th…
-
These suggestions only work if the question is rewritten as suggested in #42
"Which TWO statements about the principle „Don’t repeat yourself” (DRY) are correct?
In other words: It should be avoide…
-
We want our LGs to be "good" (explained in our [readme](https://github.com/isaqb-org/curriculum-foundation#what-constitutes-good-learning-goals)
Therefore we should be able to add one or several re…
-
from an iSAQB internal slack channel, asked by @michaelpog:
>I see that SOLID principles were entirely removed. In other words even the mention of the term SOLID was removed and instead just the Op…
-
In all chapters, we should delete the text “[previously LG...]” text. I would rather have this documented as part of the change history that we publish.
By the way, in LG 01-03 in the English versi…
-
I know we've talked about this ad nauseum, but I'm going to give it one last try... :-)
I would like to change the "clarify and scrutinize requirements and constraints, and refine them if necessar…
-
IMPORTANT - PLEASE READ!!
As @rhoadesre asked in a private E-mail: How do we decide?
I'd like to make our "process" explicit in an ADR, so others can understand how we come to conclusions or dec…
-
"Gesamtverantwortung der Projektleitung" is currently translated as "overall responsibilities of project management", which rather means "die allgemeinen Aufgaben des Projektmanagements"
IMO "overa…
-
for a first version some definitions could be included in the curriculum itself.