Abstract
We describe how a study of the SEI's Capability Maturity Model led us to change the structure and content of a project-intensive introductory graduate course sequence in software engineering. A brief review of the Capability Model is followed by an assessment of our software process as it previously existed. We then present some of the changes that were introduced and how they seem to have benefited the students.
Preview
Unable to display preview. Download preview PDF.
References
Humphrey, Watts S. Managing the Software Process. Reading, Mass.: Addison-Wesley.
Olson, Dave. Exploiting Chaos: Cashing in on the Realities of Software Development. New York: Van Nostrand Reinhold.
Paulk, Mark C., et al. Capability Maturity Model for Software, Version 1.1, Software Engineering Institute, CMU/SEI-93-TR-24, February 1993.
Paulk, Mark C., et al. Key Practices of the Capability Maturity Model, Software Engineering Institute, CMU/SEI-93-TR-25, February 1993.
Pierce, Keith R. “Rethinking Academia's Conventional Wisdom,” IEEE Software 10(2), March 1993, 94–95, 99.
Tomayko, James E. Teaching a Project-Intensive Introduction to Software Engineering, Software Engineering Institute, CMU/SEI-87-TR-20.
Weinberg, Gerald M. Quality Software Management. New York: Dorset House.
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1993 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
McCarty, W.B., Plew, G.T. (1993). How mature is your software process?. In: Díaz-Herrera, J.L. (eds) Software Engineering Education. CSEE 1994. Lecture Notes in Computer Science, vol 750. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0017641
Download citation
DOI: https://doi.org/10.1007/BFb0017641
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-57461-3
Online ISBN: 978-3-540-48191-1
eBook Packages: Springer Book Archive