Lecture: design for software (updated)

Updated: we will be visited by Art Swanson (LinkedIn, Quora) of local medical practice management software maker Allscripts. Allscripts is one of the leaders nationally in that field. Art will talk about their process for mobile development.

Next week I'll try to bring this design stuff home to our software world. We'll talk about design method, and about what design means for software. The two readings I'd like you to react to by Monday evening are:

• S. Kuhn. The software design studio: an exploration. 1998. IEEE Software, 15, 2, 65-71. 
• D. Kelley & B. Hartfield. The designer's stance. 1996. From T. Winograd, Bringing Design to Software, Addison Wesley. (This page his some annoying format problems that seem less annoying in Internet Explorer). 

Here are some more readings that you should look at if you have the time:

• Most of the Winograd book above is online, and well worth checking out. In particular, 
• See D. Schon & J. Bennet. Reflective conversation with materials, 
• And M. Schrage. Cultures of prototyping. 
• You can learn more about Shon's perspective in his paper, Design as a reflective conversation with the materials of a design situation. 1992. Knowledge-Based Systems, 5, 1, 3-14. 
• Kuhn elaborates in a slightly different context in her paper, Learning from the architecture studio: implications for project-based pedagogy. International J. Engineering Education, 17, 4-5.