Quantum Mechanics, Buddhism and Projects
by Rolf Goetz
Every once in a while I run into fellow requirements engineers who seem to ignore the fact that the holy project objectives trinity of Time, Budget, and Scope is all about interrelated, inseparable ideas. Why are they ignorant? After I heard about recent insights from quantum mechanics, an explaining theory formed in my head. I will add a little cognitive science and Buddhism to support my argument.
Conclusion: people might have a mental model too simple for covering the actual interrelation present.
| Attachment | Size |
|---|---|
| Quantum_Mechanics_Buddhism_and_Projects_for RQNG.pdf | 48.82 KB |
RE: quality?
Black Duck,
thanks for bringing these two important topics up.
It seems you're one of the rarely seen persons who believe that a poor quality function is not the desired function. I share the same belief.
But look at the average requirements specification document. There are too many cases in which 80% of it is function requirements, i. e. binary ones (ones that can be tested by answering a simple Yes-No question). When I say 80% I don't necessarily mean in numbers of requirements of course.
There should, however, be a percentage of scalar requirements at least as strong. These are the ones that need a scale to be tested. Qualities often belong in this category, as do time and budget. So yes, time and budget are simply requirements.
In this sense I wouldn't say that quality is a constraint per se.
To me, a constraint is a requirement that explicitly and intentionally tries to restrict a system or process (see the American Heritage Dictionary, and the Planguage Glossary). So constraints work differently in a spec, differenet from other requirements types.
Cheers!
Rolf