What life? What cycle?

ABSTRACT

The traditional system life cycle model does not portray the life of a system, nor is it a cycle. An alternative model is described that portrays the modification cycle of the system and the detailed activities of making a change. Implications are drawn for maintenance, development, and the education of software engineers.

REFERENCES

• 1: Ruven Brooks, Using a behavioral theory of program comprehension in software engineering, Proceedings of the 3rd international conference on Software engineering, p.196-201, May 10-12, 1978, Atlanta, Georgia, United States
• 2: Glass, R. L., and R. A. Noiseux, Software Maintenance Guidebook. Englewood Cliffs, New Jersey: Prentice-Hall, 1981.
• 3: Pentti Kerola , Peter Freeman, A comparison of lifecycle models, Proceedings of the 5th international conference on Software engineering, p.90-99, March 09-12, 1981, San Diego, California, United States
• 4: Bennett P. Lientz , E. Burton Swanson, Software Maintenance Management, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1980
• 5: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 6: D. L. Parnas, On the Design and Development of Program Families, IEEE Transactions on Software Engineering, v.2 n.1, p.1-9, January 1976 [doi>10.1109/TSE.1976.233797]
• 7: U.S. General Accounting Office. Federal Agencies' Maintenance of Computer Programs: Expensive and Undermanaged. U.S. General Accounting Office, AFMD-81-25, February 26, 1981.
• 8: Van Horn, E.C. "Software Must Evolve." In H. Freeman and P. M. Lewis, II (eds), Software Engineering. New York: Academic Press, 1980.