Category list

References and additional resources

[Beck00] Beck, Kent, Extreme Programming Explained , Addison-Wesley, 2000.

[Khan97] Khan, Badrul H., Web-Based Instruction , Educational Technology Publications (1997).

[Jonssen86] Jonssen, D., Hypertext Principles for Text and Course Design, Educational Psychologist 21(4), (1986): pp. 269 “292.

[Minsky85] Minsky, Marvin, The Society of Mind, Simon and Schuster, 1985.

[Petroski03] Petroski, Henry, Small Things Considered , Knopf, 2003.

The Alertbox: http://www.useit.com.

Center for Research in Electronic Commerce: http://crec.bus.utexas.edu/.

Shapiro, Carl, and Varian, Hal. R., Information Rules , Harvard Business School Press, 1998.

Lawrence, E.; Corbitt, B.; Tidwell, A.; Fisher, J.; and Lawrence, J. R., Internet Commerce ”Digital Modes for Business , John Wiley & Sons, 1998.

Dodgson, M., Organizational Learning: A Review of Some Literature, Organization Studies 14(3), (1993): pp. 375 “394.

Drucker, Peter Ferdinand, Managing for the Future , Truman Talley Books, 1992.

Lakoff, George, and Johnson, Mark, Metaphors We Live By , University of Chicago Press, 1980.

Wallace, Patricia, The Internet in the Workplace , Cambridge, UK, 2004.

Part V: Software Engineering Education

Chapter List

Chapter 16: Case Studies in Software Engineering
Chapter 17: Students Summary Projects and Presentations
Chapter 18: Remarks about Software Engineering Education
Chapter 19: Additional Information on Resources Used in This Book

Chapter 16: Case Studies in Software Engineering

Introduction

This chapter contains 16 case studies from the software development field. The particular cases were chosen to illustrate some of the human aspects of software engineering problems. Each case study consists of a set of background questions designed to focus the reader s attention on the point(s) of the case study, narrative, and further questions to apply knowledge gained . The cases are of three types: the first group illustrates software management problems, the second group contains one case for each process of the paradigm of software engineering described in Chapter 8, The History of Software Engineering, and the third group focuses on several problems involved with software design, architecture, and testing.

Objectives

Readers will become familiar with information managers usually have, and its effect on the process of software development.
Readers will observe the steps of the software development paradigm by analyzing case studies.
Readers will gain tools to apply to software design, architecture, and testing problems.

Study Questions

Before reading the case studies, and based on what you have read so far in this book, what, in your opinion, would be the most common theme of the management narratives? The life cycle stories? The design cases?

Relevance for Software Engineering

Since each aspect of the case studies pertains to some problem in software engineering and its solution, relevance is evident; we chose the cases based on utility. One of the most accelerated ways to illustrate such points is the use of case studies [Linn and Clancy92]. Table 16.1 presents the structure of the chapter.

Table 16.1: The Case Studies Presented in This Chapter
Software Management	Software Development Paradigm	General Principles
Case 1: Overtime	Case 5: Specifying	Case 9: The Recycling Principle
Case 2: Schedule	Case 6: Designing	Case 10: Multiple Representations
Case 3: Getting New Business	Case 7: Coding	Case 11: Alternative Tasks
Case 4: Discovering Information	Case 8: Testing	Case 12: Reflection Case 13: Fingerprints Case 14: Divide and Conquer Case 15: Persecution Complex Case 16: Literacy