Abstract
The traditional options, purchasing an ERP or reengineering in-place applications, are not always available. Institutions find their buy versus (re)build alternatives spawn unacceptable ERP, staffing, software decrepitude, or future support costs. In this case study, the University of Washington describes its "middle road" of constructing, acquiring, reengineering, and developing applications.