Value of Competence


If we know who the stakeholders are, when designing decision governance, then we need to know their interests, so that we can make sure these are met through the decision process.
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…
An argumentation framework [1] is a graph of nodes called arguments, and edges called attacks. If arguments are propositions, and “p1 attacks p2” reads “if you believe p1 then you shouldn’t believe p2”, then an argumentation framework looks like something you can use to represent the relationship between arguments and counterarguments in, say, a debate….
Being entitled to make decisions carries with it the responsibility for outcomes of actions that the decisions led to. Accountability can be implemented through decision governance by defining responsibilities for outcomes of decisions. The idea that decision responsibilities are the counterpart to decision rights is easy to understand. However, defining useful decision responsibilities involves finding…
Decision rights will be exercised, and decision obligations discharged only if there are incentives to do so. If you need to make a decision and bear the consequences, i.e., exercise decision rights and discharge obligations, the only reason to do so is if you see how it makes sense with regards to what you want….
What are the necessary and sufficient conditions for a proposition to be called a requirement? In Requirements Engineering research, a proposition is a requirement if and only if specific grammatical and/or communication conditions hold. I offer an alternative, that a proposition is a requirement if and only if specific contractual, economic, and engineering relationships hold….