Interpretation, interaction and reality construction in software engineering: An explanatory model

The incorporation of social issues in software engineering is limited. Still, during the last 20 years the social element inherent in software development has been addressed in a number of publications that identified a lack of common concepts, models, and theories for discussing software development from this point of view. It has been suggested that we need to take interpretative and constructive views more seriously if we are to incorporate the social element in software engineering. Up till now we have lacked papers presenting 'simple' models explaining why. This article presents a model that helps us better to understand interpretation, interaction and reality construction from a natural language perspective. The concepts and categories following with the model provide a new frame of reference useful in software engineering research, teaching, and methods development.

[1]  Peter Naur,et al.  Computing: A Human Activity , 1991 .

[2]  Philip Kraft,et al.  Software Practice Is Social Practice , 2002, Social Thinking - Software Practice.

[3]  Christiane Floyd,et al.  Software Development and Reality Construction , 1992 .

[4]  Christiane Floyd,et al.  Outline of a Paradigm Change in Software Engineering , 1993 .

[5]  Gerhard Schmidt,et al.  STEPS to Software Development with Users , 1989, ESEC.

[6]  Peter Naur,et al.  Programming as theory building , 1985 .

[7]  Alfonso Fuggetta,et al.  Software process: a roadmap , 2000, ICSE '00.

[8]  Kari Rönkkö,et al.  Making Methods Work in Software Engineering: Method Deployment - as a Social Achievement , 2005 .

[9]  Ivan Aaen,et al.  Software Process Improvement: Blueprints versus Recipes , 2003, IEEE Softw..

[10]  Meir M. Lehman.  Programs, life cycles, and laws of software evolution , 1980 .

[11]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[12]  Yvonne Dittrich,et al.  Social Thinking - Software Practice , 2002, Social Thinking - Software Practice.

[13]  Kari Smolander,et al.  Four metaphors of architecture in software organizations: finding out the meaning of architecture in practice , 2002, Proceedings International Symposium on Empirical Software Engineering.

[14]  Yvonne Dittrich,et al.  When Plans do not Work Out: How Plans are Used in Software Development Projects , 2005, Computer Supported Cooperative Work (CSCW).

[15]  Tom DeMarco,et al.  Peopleware: Productive Projects and Teams , 1987 .

[16]  S. Bruyn,et al.  Studies in Ethnomethodology. By Harold Garfinkel. Englewood Cliffs, New Jersey: Prentice-Hall, 1967. 288 pp. $6.95 , 1968 .

[17]  Urs Andelfinger,et al.  On the Intertwining of Social and Technical Factors in Software Development Projects , 2002, Social Thinking - Software Practice.

[18]  S. L. Star,et al.  Social science, technical systems, and cooperative work: beyond the great divide , 1999 .

[19]  Wes Sharrock,et al.  Project work: The organisation of collaborative design and development in software engineering , 1996, Computer Supported Cooperative Work (CSCW).

[20]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[21]  Lars Mathiassen,et al.  Reflective Systems Development , 1998, Scand. J. Inf. Syst..

[22]  R. Gordon.  Ethnomethodology , 1976 .

[23]  Tom DeMarco,et al.  Peopleware (2nd ed.): productive projects and teams , 1999 .

[24]  Keith W. Miller,et al.  Agile software development: human values and culture , 2005, IEEE Technology and Society Magazine.

[25]  M.M. Lehman,et al.  Programs, life cycles, and laws of software evolution , 1980, Proceedings of the IEEE.

[26]  Jr. Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[27]  L. Wittgenstein.  Philosophical investigations = Philosophische Untersuchungen , 1958 .

[28]  Joseph A. Goguen,et al.  Requirements engineering: social and technical issues , 1994 .

[29]  Sara Eriksén,et al.  Localizing Self on the Internet: Designing for "Genius Loci" in a Global Context , 2002, Social Thinking - Software Practice.

[30]  David D. McDonald,et al.  Programs , 1984, CL.

[31]  P. Kidwell,et al.  The mythical man-month: Essays on software engineering , 1996, IEEE Annals of the History of Computing.

[32]  Elihu M. Gerson,et al.  Analyzing due process in the workplace , 1986, COCS '86.

[33]  Watts S. Humphrey,et al.  Managing Technical People: Innovation, Teamwork, and the Software Process , 1996 .

[34]  David Lorge Parnas,et al.  A Rational Design Process: How and Why to Fake It , 1985, TAPSOFT, Vol.2.

[35]  Wes Sharrock,et al.  Occasioned practices in the work of software engineers , 1994 .