×

A component-based software configuration management model and its supporting system. (English) Zbl 1057.68012

Summary: Software Configuration Management (SCM) is an important key technology in software development. Component-Based Software Development (CBSD) is an emerging paradigm in software development. However, to apply CBSD effectively in real world practice, supporting SCM in CBSD needs to be further investigated. In this paper, the objects that need to be managed in CBSD is analyzed and a component-based SCM model is presented. In this model, components, as the integral logical constituents in a system, are managed as the basic configuration items in SCM, and the relationships between/among components are defined and maintained. Based on this model, a configuration management system is implemented.

MSC:

68N01 General topics in the theory of software
Full Text: DOI

References:

[1] Burrows C, George G, Dart S. Configuration Management. Ovum Ltd., 1996.
[2] Rational Corporation, Clear Case Concepts Manual. Document Number 800-010043-000, January, 1998.
[3] McCabe & Associates Corporation, McCabe TRUEChange, Available WWW RL: http://www.mccabe.com/products/truechange.htm(2000)
[4] Merant Corporation, PVCS Product, Available WWW RL: http://www.merant.com/products/pvcs/(2000)
[5] Microsoft Corporation, Visual SourceSafe Technical Articles, Available WWW RL: http://msdn.microsoft.com/ssafe/technical/articles.asp(2000)
[6] Aoyama M. Component-based software engineering: Can it change the way of software development? InProceedings of the International Conference on Software Engineering, Volume II, April, 1998, pp.111–120.
[7] Christensen H B. Experiences with architectural software configuration management in Ragnarok. InProceedings of the Eighth International Symposium on System Configuration Management, Brussels, Belgium, July, 1998, pp.50–56.
[8] A van der Hoek, Heimbigner D, Wolf A L. System modeling resurrected. InProceedings of the Eighth International Symposium on System Configuration Management, Brussels, Belgium, July, 1998, pp.124–130.
[9] Leblang D B, McLean D G. Configuration management for large-scale software development efforts. InGTE Workshop on Software Engineering Environments for Programming in the Large, June, 1985, pp. 122–127.
[10] Estublier J. A configuration manager: The Adele data base of programs. InProceedings of the Workshop on Software Engineering Environments for Programming-in-the-Large, June, 1985, pp. 140–147.
[11] Sommerville I, Dean G. PCL: A language for modeling evolving, system architectures.Software Engineering Journal, 1996, 5(3): 111–121. · doi:10.1049/sej.1996.0015
[12] Berliner B. CVS II: Parallelizing software development. InProceedings of the Winter 1990 USENIX Conference, January 22–26, 1990, Washington, DC, USA (Berkeley, CA, USA, Jan. 1990), USENIX Association, Ed., USENIX, pp.341–352.
[13] MacDonald J, Hilfinger P N, Semenzato L. PRCS: The project revision control system. InProceedings of the Eighth International Symposium on System Configuration Management, Brussels, Belgium, July, 1998, pp.78–84.
[14] Podgurski A, Clarke L A. A formal model of program dependences and its implications for software testing, debugging and maintenance.IEEE Transactions on Software Engineering, Sept., 1990, 16(9): 965–979. · doi:10.1109/32.58784
[15] Moriconi M, Winkler T C. Approximate reasoning about the semantic effects of program changes.IEEE Transactions on Software Engineering, Sept., 1990, 16(9): 980–992. · doi:10.1109/32.58785
[16] Borison E. A Model of Software Manufacture. InAdvanced Programming Environments, Conradi R, Didriksen T, Wanvik D (eds.), New York: Springer-Verlag, 1986, pp. 197–200.
[17] Lu Qi. A graph model for software evolution.IEEE Transactions on Software Engineering, Aug., 1990, 16(8): 917–927. · doi:10.1109/32.57627
[18] Mei Hong, Zhang Lu, Yang Fuqing. A software configuration management model for supporting component-based software development.ACM SIGSOFT Software Engineering Notes (USA), 2001, 26(2). · Zbl 1057.68012
[19] Feiler P. Configuration management models in commercial environments. Technical Report CMU/SEI-91-TR-7, Software Engineering Institute, Pittsburgh, Pennsylvania, March, 1991.
[20] Conradi R, Westfechtel B. Version models for software configuration management.,ACM Computing Surveys, June, 1998, 30(2). · Zbl 1028.68927
[21] Rochkind M J. The source code control system.IEEE Trans. Software Engineering, Dec., 1975, 4(6): 364–370.
[22] Tichy W. RCS – A system for version control.Software Practice and Experience, 1985, 15(7): 637–654.
[23] Habermann N, Notkin D. Gandalf: Software development environments.IEEE Trans. Software Engineering 12, Dec., 1986, 12(11): 1117–1127.
[24] Wakeman L, Jowett J. PCTE – The Standard for Open Repositories. Prentice-Hall, Englewood Cliffs, NJ, 1993.
[25] Reichenberger C. VOODOO – A tool for orthogonal version management. InSoftware Configuration Management: Selected Papers SCM-4 and SCM-5 (Seattle, WA, April), Estublier J (ed.), LNCS 1005, Springer-Verlag, 1995, pp.61–79.
[26] MacKay S A. The state-of-the-art in concurrent, distributed configuration management. InSoftware Configuration Management: Selected papers SCM-4 and SCM-5 (Seattle, WA, April), Estublier J (ed.), LNCS 1005, Springer-Verlag, 1995, pp. 180–184.
This reference list is based on information provided by the publisher or from digital mathematics libraries. Its items are heuristically matched to zbMATH identifiers and may contain data conversion errors. In some cases that data have been complemented/enhanced by data from zbMATH Open. This attempts to reflect the references listed in the original paper as accurately as possible without claiming completeness or a perfect matching.