Gambit: An Interactive Database Design Tool for Data Structures, Integrity Constraints, and Transactions

• Published in: IEEE transactions on software engineering Vol. SE-11; no. 7; pp. 574 - 583
• Main Authors: Braegger, R.P., Dudler, A.M., Rebsamen, J., Zehnder, C.A.
• Format: Journal Article
• Language: English
• Published: New York, NY IEEE 01.07.1985; Institute of Electrical and Electronics Engineers; IEEE Computer Society
• Subjects: Applied sciences; Computer languages; Computer science; control theory; systems; Data modules; Data structures; Database design; database programming language; Database systems; Design; Engineering; entity relationship model; Exact sciences and technology; Feedback; Information systems. Data bases; integrity constraints; Memory organisation. Data processing; Methods; Programming languages; propagation path concept; Prototypes; Relational databases; Satellite broadcasting; Semantics; Software; Testing; Transaction databases; User interface; User interfaces; Programming language; Database; System design
• ISSN: 0098-5589; 1939-3520
• DOI: 10.1109/TSE.1985.232501

The design of a database is a rather complex and dynamic process that requires comprehensive knowledge and experience. There exist many manual design tools and techniques, but the step from a schema to an implementation is still a delicate subject. The interactive database design tool Gambit supports the whole process in an optimal way. It is based on an extended relational-entity relationship model. The designer is assisted in outlining and describing data structures and consistency preserving update transactions. The constraints are formulated using the database programming language Modula/R which is based upon first-order predicate calculus. The update transactions are generated automatically as Modula/R programs and include all defined integrity constraints. They are collected in so-called data modules that represent the only interface to the database apart from read operations. The prototype facility of Gambit allows the designer to test the design of the database. The results can be used as feedback leading to an improvement of the conceptual schema and the transactions.