The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January/February (2012 vol.29)
pp: 28-33
Alex Baker , Visitrend
Andre van der Hoek , University of California, Irvine
Harold Ossher , IBM Research
Marian Petre , The Open University
ABSTRACT
This special issue sets an agenda for research into early software design, and this introduction outlines drivers and issues for that agenda. It argues that looking at software from a design perspective, understanding software as a designed artifact, and considering how design reaches into the whole software life cycle can bring significant benefits both to our understanding of what works in software design and to our approach to tools and practices. The special issue presents outputs from an NSF-funded workshop on 'Studying Professional Software Design' held in 2010 at UC Irvine in which participants analyzed the same professional design sessions from different analytic perspectives. The workshop dialogues provide an example of what's critically needed to drive this research agenda: empirically grounded dialogues between research and practitioners.
INDEX TERMS
design, software design, studying professional software design
CITATION
Alex Baker, Andre van der Hoek, Harold Ossher, Marian Petre, "Guest Editors' Introduction: Studying Professional Software Design", IEEE Software, vol.29, no. 1, pp. 28-33, January/February 2012, doi:10.1109/MS.2011.155
REFERENCES
1. B. Boehm, Software Engineering: Barry Boehm's Lifetime Contributions to Software Development, Management, and Research, Wiley/IEEE CS, 2007.
2. F.P. Brooks Jr., The Design of Design: Essays from a Computer Scientist, Addison-Wesley/Pearson Education, 2010.
3. T. Winograd, Bringing Design to Software, ACM Press, 1996.
4. N. Cross, Designerly Ways of Knowing, Springer, 2007.
5. R. Guindon, H. Krasner, and B. Curtis, Breakdowns and Processes during the Early Activities of Software Design by Professionals, Empirical Studies of Programmers: Second Workshop, Ablex Publishing, 1987.
6. B. Curtis et al., "A Field Study of the Software Design Process for Large Systems," Comm. ACM, vol. 31, no. 11, 1988, pp. 1268–1287.
7. M. Cherubini et al., "Let's Go to the Whiteboard: How and Why Software Developers Use Drawings," Proc. CHI 2007, ACM Press, 2007, pp. 557–566.
8. U. Dekel and J.D. Herbsleb, "Notation and Representation in Collaborative Object-Oriented Design: An Observational Study," SIG-PLAN Notices, vol. 42, no. 10, 2007, pp. 261–280.
9. R. Jeffries et al., "The Processes Involved in Designing Software," Cognitive Skills and Their Acquisition, J.R. Anderson ed., Erlbaum, 1981, pp. 225–283.
10. M. Petre, "Insights from Expert Software Design Practice," Proc. European Software Eng. Conf./Foundations of Software Eng. (ESEC/FSE), ACM, 2009, pp. 233–242.
11. A. Baker, and A. van der Hoek, "Ideas, Subjects, and Cycles as Lenses for Understanding the Software Design Process," Design Studies, vol. 31, no. 6, 2010, pp. 590–613.
12. S. Sonnetag, "Expertise in Professional Software Design," J. Applied Psychology, vol. 83, no. 5, 1998, pp. 703–715.
13. W. Visser, "Designers' Activities Examined at Three Levels: Organization, Strategies and Problem-Solving Processes," Knowledge-Based Systems, vol. 5, no. 1, 1992, pp. 92–104.
14. L.J. Ball and T.C. Ormerod, "Structured and Opportunistic Processing in Design: A Critical Discussion," Int'l J. Human-Computer Studies, vol. 43, 1995, pp. 131–151.
15. C. Zannier, M. Chiasson, and F. Maurer, "A Model of Design Decision Making Based on Empirical Results of Interviews with Software Designers," Information and Software Technology, vol. 49, no. 6, 2007, pp. 637–653.
39 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool