loading...
Decisions not requirements: decision-centered engineering of computer-based systems
Monterey, CA March 24-March 28
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ECBS.1997.5819261997 Workshop on Engineering of Compu ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
R. Evans, ERI Inc., USA
Sooyong Park, ERI Inc., USA
H. Alberts, ERI Inc., USA
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.".
Index Terms:
systems analysis; decision-centered engineering; computer-based systems; development deployment
Citation:
R. Evans, Sooyong Park, H. Alberts, "Decisions not requirements: decision-centered engineering of computer-based systems," ecbs, pp.435, 1997 Workshop on Engineering of Computer-Based Systems (ECBS '97), 1997
Usage of this product signifies your acceptance of the Terms of Use.


Suggestions