Author : Prof. Ashwini Gharde 1
Date of Publication :7th July 2015
Abstract: Software worth billions and trillions of dollars have gone waste in the past due to lack of proper techniques used for developing software resulting into software crisis. Historically , the processes of software development has played an important role in the software engineering. A number of life cycle models have been developed in last three decades. This paper is an attempt to identify attributes that are critical to software process model for a software project. The objective is to identify the project domain(area) and project type(scale).
Reference :
-
- Bryant, A. (2000), “Chinese Encyclopaedias and Balinese Cockfights – Lessons for Business Process Change and Knowledge Management,” In Knowledge Engineering and Knowledge Management.
- Lecture Notes in Artificial Intelligence #1937, R. Dieng and O. Corby, Eds., Springer Verlag.
- Bryant, A. (2001), “Metaphor, Myth and Mimicry: The Bases of Software Engineering,” Annals of Software Engineering 10, 273-292.
- Curtis, B., H. Krasner, V.Y. Shen, and N. Iscoe (1987), “On Building Software Process Models under the Lamppost,” In Proceedings of the 9th International Conference on Software Engineering, IEEE Computer Society Press, Monterey, CA., pp. 96- 103.
- Evans M.W. and J.J. Marciniak (1987), Software Quality Assurance and Management, WileyInterscience, New York.
- Fayad, M.E. (1997), “Software Development Process: the Necessary Evil?” Communications of the ACM. 40, 9,pp. 101-103
- Gilb, T. (1988), Principles of Software Engineering Management, Addison-Wesley, Reading, MA.
- Haase, V., R. Messmarz, G. Koch, H.J. Kugler and P. Decrinis (1994), “BOOTSTRAP Fine-Tuning Process Assessment,” IEEE Software 11, July, 25- 35
- Humphrey, W.S. (1988), “Characterizing the Software Process: A Maturity Framework,” IEEE Software 5, 2, March, 73-79.
- Humphrey, W.S. (1995), A Discipline for Software Engineering, SEI Series in Software Engineering, Addison- Wesley, Reading, MA
- Humphrey, W.S. and W.L. Sweet (1987), “A Method for Assessing the Software Engineering Capability of Contractors,” Technical Report CMU/SEI-87-TR-23, Software Engineering Institute, Pittsburgh, PA.