This Article 
 Bibliographic References 
 Add to: 
A Graph Model for Software Evolution
August 1990 (vol. 16 no. 8)
pp. 917-927

A graph model of software evolution is presented. The author seeks to formalize the objects and activities involved in software evolution in sufficient detail to enable automatic assistance for maintaining the consistency and integrity of an evolving software system. This includes automated support for propagating the consequences of a change to a software system. The evolution of large and complex software systems receives particular attention.

[1] IEEE Guide to Software Configuration Management, American National Standards Inst./IEEE. New York, Standard 1042-1987, 1988.
[2] V. Berzins, "On merging software extensions,"Acta Inform., vol. 23, no. 6, pp. 607-619, Nov. 1986.
[3] E. Borison, "A model of software manufacture," inAdvanced Programming Environments, R. Conradi, T. Didriksen, and D. Wanvik, Eds. New York: Springer-Verlag, 1986, pp. 197-220.
[4] D. Heimbigner and S. Krane, "A graph transform model for configuration management environments," inProc. ACM Software Eng. Notes/SIGPLAN Notices Software Engineering Symp. Practical-Software Development Environments, 1988, pp. 216-225.
[5] S. Horowitz, J. Prins, and T. Reps, "Integrating non-interfering versions of programs,"Trans. Program. Lang. Syst., vol. 11, no. 3, pp. 345-387, July 1989.
[6] G. Kaiser, P. Feiler, and S. Popovich, "Intelligent assistance for software development and maintenance,"IEEE Software, pp. 40-49, May 1988.
[7] G. Kaiser, "Modeling configurations as transactions," inProc. 2nd Int. Workshop Software Configuration Management, IEEE, Princeton, NJ, Oct. 1989, pp. 129-132.
[8] M. Ketabchi and V. Berzins, "Generalization per category: Theory and Application," inProc. Int. Conf. Information Systems, 1986; also Tech. Rep. 85-29, Dep. Comput. Sci., Univ. Minnesota.
[9] Luqi, "Software evolution via rapid prototyping,"Computer, vol. 22, no. 5, pp. 13-25, May 1989.
[10] R. Martin and W. Osborne,Guidance on Software Maintenance. Nat. Bureau Standards, U.S. Dep. Commerce, Dec. 1983.
[11] I. Mostov, Luqi, and K. Hefner, "A graph model of software maintenance," Dep. Comput. Sci., Naval Postgraduate School, Tech. Rep. NP552-90-014, Aug. 1989.
[12] K. Narayanaswamy and W. Scacchi, "Maintaining configurations of evolving software systems,"IEEE Trans. Software Eng., vol. SE- 13, no. 3, pp. 324-334, Mar. 1987.
[13] D. Perry, "The Inscape Environment," inProc. 11th Int. Conf. Software Engineering, IEEE, 1989, pp. 2-12.
[14] J. Walpole, G. Blair, J. Malik, and J. Nichol, "A unifying model for consistent distributed software development environments,"Software Eng. Notes (Proc. ACM Software Engineering Symp. Practical Software Development Environments), vol. 13, no. 5, pp. 183-190, Nov. 1988.

Index Terms:
graph model; software evolution; automatic assistance; consistency; integrity; evolving software system; automated support; complex software systems; automatic programming; data integrity; graph theory; software tools.
Luqi, "A Graph Model for Software Evolution," IEEE Transactions on Software Engineering, vol. 16, no. 8, pp. 917-927, Aug. 1990, doi:10.1109/32.57627
Usage of this product signifies your acceptance of the Terms of Use.