Advertisement

Software Architecture and Software Configuration Management

  • Bernhard Westfechtel
  • Reidar Conradi
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2649)

Abstract

This paper examines the relations between software architecture and software configuration management. These disciplines overlap because they are both concerned with the structure of a software system being described in terms of components and relationships. On the other hand, they differ with respect to their focus — specific support for programming-in-the-large, versus general support for the management of evolving software objects throughout the whole life cycle. Several problems and alternatives concerning the integration of both disciplines are discussed.

Keywords

Software Architecture Version Control Case Tool Architecture Description Language Software Object 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Garlan, D., Shaw, M.: An introduction to software architecture. In Ambriola, V., Tortora, G., eds.: Advances in Software Engineering and Knowledge Engineering. Volume 2. World Scientific, Singapore (1993) 1–39Google Scholar
  2. 2.
    Garlan, D., Paulisch, F., Tichy, W.: Summary of the Dagstuhl workshop on software architecture. ACM Software Engineering Notes 20 (1995) 63–83CrossRefGoogle Scholar
  3. 3.
    Software Engineering Institute Pittsburgh, Pennsylvania: How Do You Define Software Architecture? (2003) http://www.sei.cmu.edu/architecture/definitions.html.
  4. 4.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison Wesley, Reading, Massachusetts (1998)Google Scholar
  5. 5.
    Prieto-Diaz, R., Neighbors, J.: Module interconnection languages. The Journal of Systems and Software 6 (1986) 307–334CrossRefGoogle Scholar
  6. 6.
    Vestal, S.: A cursory overview and comparison of four architecture description languages. Technical report, Honeywell Systems and Research Center (1993)Google Scholar
  7. 7.
    Medvidovic, N., Taylor, R.: A classification and comparison framework for software architecture description languages. IEEE Transactions on Software Engineering 26 (2000) 70–93CrossRefGoogle Scholar
  8. 8.
    Tichy, W.F.: Tools for software configuration management. In Winkler, J.F.H., ed.: Proceedings of the International Workshop on Software Version and Configuration Control, Grassau, Germany, Teubner Verlag (1988) 1–20Google Scholar
  9. 9.
    IEEE New York, New York: IEEE Standard for Software Configuration Management Plans: ANSI/IEEE Std 828-1983. (1983)Google Scholar
  10. 10.
    Dart, S.: Concepts in configuration management systems. In Feiler, P.H., ed.: Proceedings of the 3rd International Workshop on Software Configuration Management, Trondheim, Norway, ACM Press (1991) 1–18Google Scholar
  11. 11.
    Conradi, R., Westfechtel, B.: Version models for software configuration management. ACM Computing Surveys 30 (1998) 232–282CrossRefGoogle Scholar
  12. 12.
    Tichy, W.F.: Software development control based on module interconnection. In: Proceedings of the IEEE 4th International Conference on Software Engineering, Pittsburgh, Pennsylvania, IEEE Computer Society Press (1979) 29–41Google Scholar
  13. 13.
    Estublier, J.: A configuration manager: The Adele data base of programs. In: Proceedings of the Workshop on Software Engineering Environments for Programming-in-the-Large, Harwichport, Massachusetts (1985) 140–147Google Scholar
  14. 14.
    Marzullo, K., Wiebe, D.: Jasmine: A software system modelling facility. In: Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments. ACM SIGPLAN Notices 22-1, Palo Alto, California (1986) 121–130Google Scholar
  15. 15.
    Tryggeseth, E., Gulla, B., Conradi, R.: Modelling systems with variability using the PROTEUS configuration language. [34] 216–240Google Scholar
  16. 16.
    Leblang, D.B., McLean, G.D.: Configuration management for large-scale software development efforts. In: Proceedings of the Workshop on Software Engineering Environments for Programming-in-the-Large, Harwichport, Massachusetts (1985) 122–127Google Scholar
  17. 17.
    Burrows, C.: Ovum Evaluates: Configuration Management. Ovum Limited, London, UK. (2002) http://www.ovum.com.Google Scholar
  18. 18.
    Feldman, S.I.: Make — A program for maintaining computer programs. Software Practice and Experience 9 (1979) 255–265zbMATHCrossRefGoogle Scholar
  19. 19.
    Rochkind, M.J.: The source code control system. Transactions on Software Engineering 1 (1975) 364–370Google Scholar
  20. 20.
    Tichy, W.F.: RCS — A system for version control. Software Practice and Experience 15 (1985) 637–654CrossRefGoogle Scholar
  21. 21.
    Leblang, D.: The CM challenge: Configuration management that works. [35] 1–38Google Scholar
  22. 22.
    Cagan, M.: Untangling configuration management. [34] 35–52Google Scholar
  23. 23.
    Estublier, J., Casallas, R.: Three dimensional versioning. [34] 118–135Google Scholar
  24. 24.
    Boggs, W., Boggs, M.: UML with Rational Rose 2002. Sybex, Alameda, California (2002)Google Scholar
  25. 25.
    White, B.A.: Software Configuration Management Strategies and Rational ClearCase. Object Technology Series. Addison-Wesley, Reading, Massachusetts (2000)Google Scholar
  26. 26.
    Rational Software Corporation Cupertino, California: Using Rational Rose and Rational ClearCase in a Team Environment. (2002) http://www.rational.com.
  27. 27.
    Estublier, J., Casallas, R.: The Adele configuration manager. [35] 99–134Google Scholar
  28. 28.
    Allen, R., Garlan, D.: A formal basis for architectural connection. ACM Transactions on Software Engineering and Methodology 6 (1997) 213–249CrossRefGoogle Scholar
  29. 29.
    Luckham, D.C., Kenney, J.J., Augustin, L.M., Vera, J., Bryan, D., Mann, W.: Specification and analysis of system architecture using Rapide. IEEE Transactions on Software Engineering 21 (1995) 336–354CrossRefGoogle Scholar
  30. 30.
    van der Hoek, A., Heimbigner, D., Wolf, A.L.: Software architecture, configuration management, and configurable distributed systems: A menage a trois. Technical Report CU-CS-849-98, University of Boulder, Colorado (1998)Google Scholar
  31. 31.
    van der Hoek, A., Heimbigner, D., Wolf, A.L.: Capturing architectural configurability: Variants, options, and evolution. Technical Report CU-CS-895-99, University of Boulder, Colorado (1999)Google Scholar
  32. 32.
    van der Hoek, A., Mikic-Rakic, M., Roshandel, R., Medvidovic, N.: Taming architectural evolution. In: Proceedings of the Joint 8th European Software Engineering Conference and the 9th ACM SIGSOFT Symposium on Fundamentals of Software Engineering. ACM Software Engineering Notes 26-5, Vienna, Austria, ACM Press (2001) 1–10CrossRefGoogle Scholar
  33. 33.
    Westfechtel, B., Conradi, R.: Software architecture and software configuration management. In van der Hoek, A., ed.: 10th International Workshop on Software Configuration Management: New Practices, New Challenges, and New Boundaries (SCM 10), Toronto, Canada (2001) 19–26Google Scholar
  34. 34.
    Estublier, J., ed.: Software Configuration Management: Selected Papers SCM-4 and SCM-5. LNCS 1005, Seattle, Washington, Springer-Verlag (1995)Google Scholar
  35. 35.
    Tichy, W.F., ed.: Configuration Management. Volume 2 of Trends in Software. John Wiley & Sons, New York, New York (1994)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Bernhard Westfechtel
    • 1
  • Reidar Conradi
    • 2
  1. 1.Lehrstuhl für Informatik IIIRWTH AachenAachen
  2. 2.Norwegian University of Science and Technology (NTNU)TrondheimNorway

Personalised recommendations