Decisions not requirements: decision-centered engineering of computer-based systems

Recognizing the stated aims of the engineering of computer-based systems (ECBS) discipline namely the design, development deployment, and analysis of complex systems whose behavior is, to a substantial degree, determined or controlled by computers, the proposal is that the term [and the associated process] of “requirements” be replaced with “decisions” and a decision process. Requirements, by definition, mandate a flow that originates with the senior and are directed unilaterally to the junior: “I require this of you.” The decision process is exactly the opposite in both flow and participation. Rather than unilateral direction to the junior that is originated by the senior, decisions are choices by the senior resulting from united consideration with the junior of the latter´s nominated set of alternatives. “I select the following as a result of our mutual consideration of the options and associated assessments and recommendations you have provided.”