This investigation provides an empirical scaling of software engineering practices derived from the software process maturity model developed by the Software Engineering Institute of Carnegie Mellon University (Humphrey et al. [Humphrey, W. S., D. H. Kitson, T. C. Kasse. 1989. The state of software engineering practice: A preliminary report. Technical Report CMU/SEI-89-TR-1 ESD-TR-89-01, Carnegie-Mellon University, Software Engineering Institute, Pittsburgh, PA.]). An analysis of data collected in an extended software maintenance study has shown that the responses to Humphrey's key software practice items fit the Rasch psychometric model providing an alternative framework in which to understand the software development practices. The Rasch model analysis describes the likelihood of a practice deployment for any level of evolution and provides precise and meaningful measures.

No abstract

Results of a survey of the 1990 Software Maintenance Association Meeting and Conference attendees indicate a number of changes in software maintenance-related issues. Systems are ageing and growing in size. Software maintenance is separated from new systems development in more than half of the organizations. Over 45% of maintenance work is spent on functional enhancements. About three out of four organizations depend on specific individuals because no-one else can maintain particular systems and only 5% of organizations employ a formal method for determining when software should be rewritten. Responses describing major problems and preferred changes in DP organizations were classified into general categories and compared with previous similar studies. Trends show maturation of software maintenance toward a greater appreciation of maintenance and at least an intention of managers to improve the support of this activity.

No abstract

No abstract