Abstract
In this chapter we describe various techniques for studying and representing the work of software engineers1 (SEs) and using the results to develop requirements for software engineering tools.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Bannon, L. (1994). Representing work in design. In L. Suchman (Ed.), Representations of Work: A Symposium. Monograph for proceedings of the 27th HICSS, January, Maui, Hawaii.
Bannon, L, and Bt dker, S. (1991). Beyond the interface: Encountering artifacts in use. In J. Carroll (Ed.), Designing Interaction: Psychology at the Human-Computer Interface. Cambridge University Press: New York.
Bendifallah, S., and Scacchi, W. (1987). Understanding software maintenance work, IEEE Transactions on Software Engineering, 13 (3), 311–323.
Blomberg, J., Suchman, L., and Trigg, R. (1996). Reflections on a work-oriented design project, Human Computer Interaction, 11, 237–265.
Boehm-Davis, D. Holt, R., and Schultz, A. (1992). The role of program structure in software maintenance, Int. Journal of Man Machine Studies, 36, 21–63.
Buhr, R.J.A (1998). Use case maps as architectural entities for complex systems,IEEE Trans. Software Engineering. 24(12) Dec., 1131–1155.
Buhr, R.J.A and Casselman, R.S. (1996). Use Case Maps for Object-Oriented SystemsPrentice-Hall, Englewood Cliffs, NJ.
Button, G., and Dourish, P. (1996). Technomethodology: Paradoxes and Possibilities, In Proc CHI ‘86; Human Factors in Computing Systems,Vancounver, 19–26..
Cook, T., and Campbell, D. (1979) Quasi-Experimentation: Design and Analysis Issues for Field Settings. Rand McNally: Chicago, IL.
Curtis, W (1986) By the way, did anyone study any real programmers? In E. Soloway and S. Iyengar (Eds.). In Proc. Empirical Studies of Programmers. Norwood, NJ, pp. 256–262.
Curtis, B., Krasner, H., and Iscoe, N. (1988). A field study of the software design process for large systems, Communications of the ACM,31(11), 1268–1287.
D’Astous, P., and Robillard, P. (2000). Protocol analysis in software engineering studies. Empirical Studies in Software Engineering, Khaled El-Eman and Janice Singer, eds., MIT Press.
Denzin, N.K and Lincoln, Y.S. (1994). Handbook of Qualitative Research, Sage Publications: Thousand Oaks, CA.
Glaser, B., and Strauss, A., (1967). The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine deGruyter: Hawthorne, NY.
Hutchins, E. (1994). Cognition in the Wild, MIT Press: Cambridge, MA.
Jordan, B., Goldman, R., and Sachs, P. (1995). Tools for the workplace, Communications of the ACM 38(9), 42.
Kraut, R., and Streeter, L. (1995). Coordination in software development, Communications of the ACM,38(3),69–81.
Kyng, M., and Mathiassen, L. (1997). Computers and Design in Context. MIT Press: Cambridge, MA.
Lethbridge, T.C. and Anquetil, N. (1997). Architecture of a source code exploration tool: A software engineering case study, University of Ottawa, Computer Science Technical report TR-97–07.72 Lethbridge and Singer
Lethbridge, T.C. and Herrera, F. (2000). Towards assessing the usefulness of the TkSee software exploration tool: a case study, Elsewhere in this book..
Lethbridge, T., Singer, J., Vinson, N., and Anquetil, N. (1997). An examination of software engineering work practices. In Proc. CASCON, Toronto, October: IBM, 209–223.
Lethbridge, T.C., Lyon, and S., Perry, P. (2000). The management of university-industry collaborations involving empirical studies of software engineering, In Empirical Studies in Software Engineering, Khaled El-Eman and Janice Singer, eds., MIT Press.
Litman, D., Pinto, J., Letovsky, S. and Soloway, E. (1996). Mental models and software maintenance. In Proc. Empirical Studies of Programmers: First Workshop.
Neuman, W., L. (1997). Social Research Methods: Qualitative and Quantitative Aproaches. Allyn and Bacon: Boston, MA.
Porter, A., and Votta L. (1998). Comparing detection methods for software requirements inspections: A replication using professional subjects, Empirical Software Engineering, 3, 355–379.
Pycock, J., Palfreyman, K., Allanson, J., and Button, G. (1998). Representing fieldwork and articulating requirements through VR, In. Proc CSCW, Seattle, 383–392.
Simonsen, J., and Kensing, F. (1997). Using ethnography in contextual design, Communications of the ACM, 40 (7), 82–88.
Singer, J., and Lethbridge, T. C. (1998a) Work practices as an alternative method to assist tool design in software engineering, International Workshop on Program Comprehension, Ischia, Italy, 173–179.
Singer, J., and Lethbridge, T.C. (1998). Studying work practices to assist tool design in software engineering. In 6th IEEE International Workshop on Program Comprehension,Italy, 173–179. A longer version appears as: University of Ottawa, Computer Science Technical Report TR-97–08.
Sanderson, P.M., Scott, J.J.P., Johnston, T., Mainzer, J., Watanabe, L. M. and James, J.M. (1994). MacSHAPA and the enterprise of exploratory sequential data analysis (ESDA). International Journal of Human-Computer Studies, 41 (5), 633–681.
Suchman, L. (1987). Plans and Situated Actions: The Problem of Human-Machine Communication. Cambridge University Press: New York.
Suchman, L. (Ed.) (1995). Representations of work, Special issue of the Communications of the ACM, 38(9), 33–68.
Walz, D., Elam, J., and Curtis, B. (1993). Inside a software design team: Knowledge acquisition, sharing, and integration, Communication of the ACM, 36(10), 63–77.
Editor information
Rights and permissions
Copyright information
© 2002 Springer Science+Business Media New York
About this chapter
Cite this chapter
Lethbridge, T., Singer, J. (2002). Studies of the Work Practices of Software Engineers. In: Erdogmus, H., Tanir, O. (eds) Advances in Software Engineering. Springer, New York, NY. https://doi.org/10.1007/978-0-387-21599-0_3
Download citation
DOI: https://doi.org/10.1007/978-0-387-21599-0_3
Publisher Name: Springer, New York, NY
Print ISBN: 978-1-4419-2878-8
Online ISBN: 978-0-387-21599-0
eBook Packages: Springer Book Archive