Deciding what to design: closing a gap in software engineering education

  • Authors:
  • Mary Shaw;Jim Herbsleb;Ipek Ozkaya;Dave Root

  • Affiliations:
  • Institute for Software Research, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA;Institute for Software Research, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA;Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA;Institute for Software Research, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA

  • Venue:
  • ICSE'05 Proceedings of the 2005 international conference on Software Engineering Education in the Modern Age
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Software has jumped “out of the box” – it controls critical systems, pervades business and commerce, and infuses entertainment, communication, and other everyday activities. These applications are constrained not only by traditional capability and performance considerations but also by economic, business, market and policy issues and the context of intended use. The diver sity of applications requires adaptability in responding to client needs, and the diversity of clients and contexts requires the ability to discriminate among crite ria for success. As a result, software designers must also get out of their boxes: in addition to mastering classical software development skills, they must master the contextual issues that discriminate good solutions from merely competent ones. Current software engineering education, however, remains largely “in the box”: it neglects the rich fabric of issues that lie between the client's problem and actual software development. At Carnegie Mellon we address this major shortcoming by teaching students to understand both the capabilities required by the client and the constraints imposed by the client's context.