Software configuration management and engineering data management: Differences and similarities

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


Engineering data management and software configuration management have been evolving fairly independently. On the other hand, it has been observed earlier that many parallels exist [10]. In this paper, we examine the similarities of and differences between EDM and SCM. Many concepts are similar, but there are some differences concerning the objects to be managed. As a consequence, some sophisticated fear tures of modern SCM systems are not applicable in the EDM domain because they are based on assumptions which do not hold there (objects represented as text files, tools operating towards the file system). Some suggestions for further work on version models and on the architecture of version support systems are outlined.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    M. Atkinson, F. BanÇilhon, D. DeWitt, K. Dittrich, D. Maier, and S. Zdonik. The object-oriented database system manifesto. In Proc. DOOD'89, Kyoto, Japan, pages 40–57, Dec. 1989.Google Scholar
  2. 2.
    F. BanÇilhon, C. Delobel, and P. Kannelakis, editors. Building an Object-Oriented Database System: The Story of O 2. Morgan Kaufmann, 1992.Google Scholar
  3. 3.
    M. Brielmann, E. Kupitz, D. Mallon, et al. A Common Data Schema for Tool Integration. In Proceedings CAD'92, pages 127–140. Springer Verlag, 1992.Google Scholar
  4. 4.
    H.-J. Bullinger and J. Warschat, editors. Concurrent Simultaneous Engineering Systems. Springer-Verlag, 1996.Google Scholar
  5. 5.
    W. Cellary and G. Jomier. Consistency of Versions in Object-Oriented Databases. In BanÇilhon et al. [2], pages 447–462.Google Scholar
  6. 6.
    E. E. Chang, D. Gedye, and R. H. Katz. The Design and Implementation of a Version Server for Computer-Aided Design Data. Software — Practice and Experience, 19(3): 199–222, Mar. 1989.Google Scholar
  7. 7.
    R. Conradi, editor. Software Configuration Management: Proceedings from SCM7 Workshop, Boston, USA, 18–19 May 1997. Springer Verlag LNCS 1235, 234 p.Google Scholar
  8. 8.
    R. Conradi and B. Westfechtel. Towards a Uniform Version Model for Software Configuration Management. In Conradi [7], pages 1–17.Google Scholar
  9. 9.
    R. Conradi and B. Westfechtel. Version Models for Software Configuration Management, 59 p. ACM Computing Surveys, 1998. (Accepted August 1997).Google Scholar
  10. 10.
    S. A. Dart. Parallels in Computer-Aided Design Frameworks and Software Development Environments Efforts. IFIP Transactions A, 16:175–189, 1992.Google Scholar
  11. 11.
    T. Didriksen, A. Lie, and R. Conradi. IDL as a Data Description Language for a Programming Environment Database. ACM SIGPLAN Notices, pages 71–78, Nov. 1987. (Special issue on IDL, ed. C. Robert Morgan).Google Scholar
  12. 12.
    Electronic Industries Associates, Engineering Department, Arlington, VA. CDIF CASE Data Interchange Format EIA/IS-106/107.Google Scholar
  13. 13.
    J. Estublier and R. Casallas. The Adele Software Configuration Manager. In Tichy [41]., pages 2–11.Google Scholar
  14. 14.
    S. I. Feldman. Make — a Program for Maintaining Computer Programs. Software — Practice and Experience, 9(3):255–265, Mar. 1979.MATHGoogle Scholar
  15. 15.
    G. Fowler, D. Korn, and H. Rao. n-DFS: The Multiple Dimensional File System. In Tichy [41], pages 135–154.Google Scholar
  16. 16.
    A. Fuggetta. A Classification of CASE Technology. IEEE Computer, pages 25–38, Dec. 1993.Google Scholar
  17. 17.
    I. P. Goldstein and D. G. Bobrow. A Layered Approach to Software Design. Technical Report CSL-80-5, XEROX PARC, Palo Alto, California, 1980.Google Scholar
  18. 18.
    A. N. Habermann and D. Notkin. Gandalf: Software Development Environments. IEEE Trans. on Software Engineering, SE-12(12):1117–1127, Dec. 1986. (Special issue on GANDALF).Google Scholar
  19. 19.
    S. B. Harris. Business Strategy and the Role of Engineering Product Data Management: A Literature Review and Summary of the Emerging Research Questions. Proceedings of the Institution of Mechanical Engineers, Part B (Journal of Engineering Manufacture), 210(B3):207–220, 1996.Google Scholar
  20. 20.
    P. B. Henderson, editor. Proc. 1st ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments (Pittsburgh), Apr. 1984. In ACM SIGPLAN Notices 19(5), May 1984.Google Scholar
  21. 21.
    ISO. ISO 10303: Product Data Representation and Exchange (the STEP Standard).Google Scholar
  22. 22.
    W. Käfer and H. Schöning. Mapping a Version Model to a Complex-Object Data Model. In Proceedings 8th International Conference on Data Engineering, pages 348–357, Tempe, Arizona, 1992. IEEE Computer Society Press.Google Scholar
  23. 23.
    R. H. Katz. Toward a Unified Framework for Version Modeling in Engineering Databases. ACM Computing Surveys, 22(4):375–408, Dec. 1990.CrossRefGoogle Scholar
  24. 24.
    B. W. Lampson and E. E. Schmidt. Practical Use of a Polymorphic Applicative Language. In Proc. 10th ACM SIGACT/SIGPLAN Symposium on Principles of Programming Languages, pages 237–255, Austin, Texas, USA, Jan. 1983.Google Scholar
  25. 25.
    D. Leblang. The CM Challenge: Configuration Management that Works. In Tichy [41], pages 1–38.Google Scholar
  26. 26.
    D. B. Leblang and R. P. Chase, Jr. Computer-aided Software Engineering in a Distributed Workstation Environment. In Henderson [20], pages 104–112. In ACM SIGPLAN Notices 19(5), May 1984.Google Scholar
  27. 27.
    A. Lie, R. Conradi, T. Didriksen, E. Kaxlsson, S. O. Hallsteinsen, and P. Holager. Change Oriented Versioning. In C. Ghezzi and J. A. McDermid, editors, Proceedings of the 2nd European Software Engineering Conference, LNCS 387, pages 191–202, Coventry, UK, Sept. 1989. Springer Verlag.Google Scholar
  28. 28.
    Y.-J. Lin and S. P. Reiss. Configuration Management with Logical Structures. In Proc. of the 18th International Conference on Software Engineering, pages 298–307, Berlin, Mar. 1996. IEEE Computer Society Press.Google Scholar
  29. 29.
    K. G. McIntosh. Engineering Data Management — A Guide to Successful Implementation. McGraw-Hill, Maidenhead, England, 1995.Google Scholar
  30. 30.
    J. Micallef and G. Clemm. The Asgard System: Activity-Based Configuration Management. In I. Sommerville, editor, Software Configuration Management: ICSE'96 SCM-6 Workshop, LNCS 1167, pages 175–186, Berlin, Germany, Mar. 1996. Springer-Verlag.Google Scholar
  31. 31.
    B. Munch. HiCOV: Managing the Version Space. In I. Sommerville, editor, Software Configuration Management: ICSE'96 SCM-6 Workshop, LNCS 1167, pages 110–126, Berlin, Germany, Mar. 1996. Springer-Verlag.Google Scholar
  32. 32.
    B. P. Munch, R. Conradi, J.-O. Larsen, M. N. Nguyen, and P. H. Westby. Integrated Product and Process Management in EPOS. Journal of Integrated CAE, 1995. (Special issue on Integrated Product and Process Modeling), 30 p.Google Scholar
  33. 33.
    M. Nagl, editor. Building Tightly-Integrated Software Development Environments: The IPSEN Approach. LNCS 1170, 709 p. Springer Verlag, Berlin, 1996.Google Scholar
  34. 34.
    P. Naur and B. Randell, editors. Software Engineering — Proc. NATO Conference in Garmisch-Partenkirchen, 1968. NATO Science Committee, Scientific Affairs Division, NATO, Brussels, Jan. 1969.Google Scholar
  35. 35.
    C. Reichenberger. Concepts and Techniques for Software Version Control. Software — Concepts and Tools, 15(3):97–104, July 1994.Google Scholar
  36. 36.
    M. J. Rochkind. The Source Code Control System. IEEE Trans. on Software Engineering, SE-1(4):364–370, 1975.Google Scholar
  37. 37.
    E. Sciore. Version and Configuration Management in an Object-Oriented Data Model. VLDB Journal, 3(1):77–106, Jan. 1994.CrossRefGoogle Scholar
  38. 38.
    R. Snodgrass. The IDL Description Language: Definition and Use. Computer Science Press, Rockville, MD 20850, USA, 1989.Google Scholar
  39. 39.
    W. F. Tichy. RCS — A System for Version Control. Software — Practice and Experience, 15(7):637–654, 1985.Google Scholar
  40. 40.
    W. F. Tichy. Tools for Software Configuration Management. In J. F. H. Winkler, editor, Proceedings of the International Workshop on Software Version and Configuration Control, pages 1–20, Grassau, Germany, 1988. Teubner Verlag.Google Scholar
  41. 41.
    W. F. Tichy, editor. Configuration Management, volume 2 of Trends in Software. John Wiley and Sons, New York, 1994.Google Scholar
  42. 42.
    B. Westfechtel. A Graph-Based System for Managing Configurations of Engineering Design Documents. International Journal of Software Engineering and Knowledge Engineering, 6(4):549–583, Dec. 1996.CrossRefGoogle Scholar
  43. 43.
    B. Westfechtel. Integrated Product and Process Management for Engineering Design Applications. Integrated Computer-Aided Engineering, 3(1):20–35, Jan. 1996.Google Scholar
  44. 44.
    A. Zeller and G. Snelting. Unified Versioning through Feature Logic. ACM Transactions on Software Engineering and Methodology, 6(4):397–440, Oct. 1997.CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1998

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