Advertisement

Damokles — A database system for software engineering environments

  • Klaus R. Dittrich
  • Willi Gotthard
  • Peter C. Lockemann
Software Engineering Databases
Part of the Lecture Notes in Computer Science book series (LNCS, volume 244)

Abstract

Comprehensive software engineering environments consist of a large number of cooperating tools in order to support the various phases of some software life cycle. The cooperation depends largely on the availability of basic mechanisms that manage the large quantities of information involved in a consistent fashion. While database concepts are desirable for this purpose, current systems prove to be unsuitable.

This paper discusses some of the reasons, and lists the requirements that more appropriate solutions have to meet. One major requirement concerns a data model that should specifically be tailored to the software engineering world. The paper presents a new approach to data modelling currently under development. Some other system features as well as implementation aspects are also sketched. We conclude with some perspectives on how the construction of future software tools might be facilitated in the future by virtue of a common underlying database system.

Keywords

Data Model Database System Design Object Generic Object Object Type 
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.

5. References

  1. [Ada83]
    American National Standards Institute, Inc.: The Programming Language Ada Reference Manual. ANSI/MIL-STD-1815A-1983. Lecture Notes in Computer Science, Vol. 155, Springer, 1983.Google Scholar
  2. [Brod84]
    Brodie, M. L., J. Mylopoulos and J. W. Schmidt (eds.): On Conceptual Modelling, Springer, 1984.Google Scholar
  3. [Chen76]
    Chen, P. P.-S.: The Entity-Relationship Model — Toward a Unified View of Data. ACM Transactions on Database Systems, Vol. 1, No. 1, March 1976, pp. 9–36.CrossRefGoogle Scholar
  4. [Dada84]
    Dadam, P., V. Lum and H.-D. Werner: Integration of Time Versions into a Relational Database System. Proc. VLDB 10, 1984, pp. 509–522.Google Scholar
  5. [Date81]
    Date, C. J.: Introduction to Database Systems. 3rd edition. Addison-Wesley, 1981.Google Scholar
  6. [DeWi84]
    DeWitt, D. J. et al.: Implementation Techniques for Main Memory Database Systems. Technical Report, Electronic Research Laboratory, University of California, Berkeley, 1984.Google Scholar
  7. [Ditt85a]
    Dittrich, K. R. and R. A. Lorie: Version Support for Engineering Database Systems. Research Report RJ 4769 (50628) 7/18/85. IBM Research Laboratory, San Jose, CA 95193 (to appear in IEEE Trans. on Software Engineering).Google Scholar
  8. [Ditt85b]
    Dittrich, K. R., A. M. Kotz and J. A. Mülle: A Multilevel Approach to Design Database Systems and its Basic Mechanisms. Proc. IEEE COMPINT, Montreal, 1985, pp. 313–320.Google Scholar
  9. [Ditt85c]
    Dittrich, K. R., A. M. Kotz and J. A. Mülle: Complex Consistency Constraints in Design Databases. Technical Report No. 2, FZI Karlsruhe, 1985.Google Scholar
  10. [Habe82]
    Habermann, N. et al.: The Second Compendium of Gandalf Documentation. Department of Computer Science, Carnegie-Mellon University, Pittsburgh, May 1982.Google Scholar
  11. [Härd86]
    Härder, T. et al.: KUNICAD — Ein datenbankgestütztes geometrisches Modellierungssystem für Werkstücke. Universität Kaiserslautern, Bericht Nr. 22/86, Januar 1986.Google Scholar
  12. [Hask81]
    Haskin, R. L. and R. A. Lorie: On Extending the Functions of a Relational Database System. Proc. SIGMOD (ACM), June 1982, pp. 207–212.Google Scholar
  13. [Hend84]
    Henderson, P. (ed.): Proc. of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Engineering Environments. SIGPLAN Notices, Vol. 19, No. 5, May 1984.Google Scholar
  14. [ISO82]
    J. J. van Griethuysen (ed.): Concepts and Terminology for the Conceptual Schema and the Information Base. International Organization for Standardization, ISO/TC97/SC5/WG3, publication number ISO/TC97/SC5-N 695, 1982.Google Scholar
  15. [Katz85]
    Katz, R.: Information Management for Engineering Design. Springer, 1985.Google Scholar
  16. [Lint84]
    Linton, M. A.: Implementing Relational Views of Programs. In: [Hend84], pp. 132–140.Google Scholar
  17. [Klah85]
    Klahold, P., G. Schlageter, R. Unland and W. Wilkes: A Transaction Model Supporting Complex Applications in Integrated Information Systems. Proc. SIGMOD 1985, pp. 388–401.Google Scholar
  18. [Kim84]
    Kim, W., R. Lorie, D. McNabb and W. Plouffe: A Transaction Mechanism for Engineering Databases. Proc VLDB 10, 1984, pp. 355–362.Google Scholar
  19. [Lock85]
    Lockemann, P. C. et al.: Database Requirements of Engineering Applications — An Analysis. Proc. GI-Fachtagung ”Datenbanksysteme in Büro, Technik und Wissenschaft”, Karlsruhe, März 1985 (in German). Also available in English: Universität Karlsruhe, Fakultät für Informatik, Technical Report 12/85.Google Scholar
  20. [Nara85]
    Narayanaswamy, K., W. Scacchi and D. McLeod: Information Management Support for Evolving Software Systems. Technical Report USC TR 85-324, University of Southern California, Los Angeles, CA 90089-0782, March 1985.Google Scholar
  21. [Perl81]
    Perlis, A., F. Sayward and M. Shaw: Software Metrics: An Analysis and Evaluation. MIT Press, 1981.Google Scholar
  22. [Sidl80]
    Sidle, T. W.: Weaknesses of Commercial Database Management Systems in Engineering Applications. Proc. 17th Design Automation Conference, Minneapolis, June 1980, pp. 57–61.Google Scholar
  23. [Tich85]
    Tichy, W. F.: RCS — A System for Version Control. Software Practice and Experience, Vol. 15, No. 7, 1985, pp. 637–654.Google Scholar
  24. [Wirt82]
    Wirth, N.: Programming in Modula 2. Springer, 1982.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1987

Authors and Affiliations

  • Klaus R. Dittrich
    • 1
  • Willi Gotthard
    • 1
  • Peter C. Lockemann
    • 1
  1. 1.Forschungszentrum Informatik an der Universität KarlsruheKarlsruhe 1

Personalised recommendations