A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Plans and situated actions: the problem of human-machine communication
Plans and situated actions: the problem of human-machine communication
A scientific methodology for MIS case studies
MIS Quarterly
Communications of the ACM - Special issue on analysis and modeling in software development
The sciences of the artificial (3rd ed.)
The sciences of the artificial (3rd ed.)
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
A science of design for software-intensive systems
Communications of the ACM - Interactive immersion in 3D graphics
Information Systems Research
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Human Problem Solving
Design and natural science research on information technology
Decision Support Systems
Validating instruments in MIS research
MIS Quarterly
Design science in information systems research
MIS Quarterly
A plea for lean software process models
Proceedings of the 2011 International Conference on Software and Systems Process
Report on the first SEMAT workshop on general theory of software engineering (GTSE 2012)
ACM SIGSOFT Software Engineering Notes
A classification of argument types for product aesthetics
Proceedings of the 9th ACM Conference on Creativity & Cognition
| Hi-index | 0.00 |
This paper explores an ongoing conflict concerning the nature of software design This conflict manifests itself as antagonism between managers and developers, debates about agile vs plan-driven methodologies and aspiring developers' dissatisfaction with their courses One side views design as a plan-driven information processing task involving rational decision-making (the Reason-Centric Perspective), while the other views design as an improvised, creative task involving naturalized decision-making (Action-Centric Perspective) Each perspective includes an epistemology, theory of human action and a software design process theory (an explanation of how software is created in practice) This paper reports the results of an exploratory questionnaire study that comparatively and empirically evaluated the two process theories Results clearly favor the Action-Centric process theory: the Sensemaking-Coevolution-Implementation Framework.