Main topics:
When is a requirements model incomplete? The answer depends on the requirements modeling language (RML) used to make the model. Therefore, when you choose an RML, you are also choosing its own definition of when a model is incomplete. The reason that conditions for model incompleteness are important, is that you cannot claim that you…
There is a simple condition, called “fitness improvement” that triggers (i.e., is both necessary and sufficient for) the change of a requirements model. The problem with it is that it is simple to define, but expensive to check when it verifies in practice. What is that condition, and why is checking it expensive? In discussing…
Let’s say that there was a requirements model M1, we made a change to it, and we call the changed model M2. What can be said about the relationship between the contents of M1 and M2? To make this simpler to discuss, suppose that we changed M1 by refining a requirement in it. To further…
In requirements modeling languages, refinement and decomposition show up as two relationships over requirements. Both terms are also, somewhat confusingly, used to refer to processes for changing the information in a requirements model. Although they have different origins, and appear in different modeling languages, they are actually not independent relationships. I will argue below that…
It requires paraconsistent reasoning and involves cognitive dissonance to think at the same time about requirements in the way promoted in mainstream requirements engineering, and then use the DevOps loop (and the broader model), a method that has been demonstrated to work (and I’ve seen it applied in a team I was part of in…
What could it mean that a “requirement evolves”? Is it the same to say that a requirement evolves and that it changes? How are requirements evolution and change related to updates of sets of requirements? The term “evolution” has rigorous definitions in biology. A textbook one is as follows (it is carried over from [1],…