A Graph-Based System for Managing Configurations of Engineering Design Documents

Abstract

Due to increasing complexity of hardware and software systems, configuration management has been receiving more and more attention in nearly all engineering domains (e.g. electrical, mechanical, and software engineering). This observation has driven us to develop a domain-independent and adaptable configuration management model (called CoMa) for managing systems of engineering design documents. The CoMa model integrates composition hierarchies, dependencies, and versions into a coherent framework based on a sparse set of essential configuration management concepts. In order to give a clear and comprehensible specification, the CoMa model is defined in a high-level, multi-paradigm specification language (PROGRES) which combines concepts from various disciplines (database systems, knowledge-based systems, graph rewriting systems, programming languages). Finally, we also present an implementation which conforms to the formal specification and provides graphical, structure-oriented tools offering a bunch of sophisticated commands and operating in a heterogeneous environment.

Version models for software configuration management

“…To ensure safe retrieval of previously constructed versions, versions can be made immutable. In many systems, all versions are made immutable when they are checked into the object base [Rochkind 1975]; in others, explicit operations are provided to freeze mutable versions [Westfechtel 1996]. Furthermore, immutability may be enforced selectively (e.g., by distinguishing between mutable and immutable attributes [Estublier and Casallas 1995]).…”

“…Thus the version model is represented by a schema whose underlying data model is not aware of versioning. This solution has been adopted, for example, by PCTE [Oquendo et al 1989] and CoMa [Westfechtel 1996], which are based on an EER and a graph data model, respectively. Its main advantage is that the data model is kept simple and potentially application-specific extensions are avoided (a widely accepted uniform version model does not yet exist).…”

“…CoMa [Westfechtel 1994[Westfechtel , 1996] manages configurations of engineering design documents and has been applied to both software engineering and mechanical engineering. The CoMa model integrates composition hierarchies, dependencies, and versions into a coherent framework based on a small set of concepts.…”

Faculty Fellowship in Support of Tolerating Intrusions through Secure System Reconfiguration

“…13c. The other systems are CME [25], Gradient [4], CoMa [51], and ScmEngine [10]. CME extends RCE [26], itself a programmatic interface to RCS [47], with collection management.…”

Ein graphbasiertes Managementsystem für dynamische Entwicklungsprozesse

“…optionale und Mengenknoten, Attributbedingungen und negative Anwendbarkeitsbedingungen). Ferner lassen sich Graphersetzungsregeln mit Hilfe von Kontrollstrukturen zu komplexen Graphtransformationen zusammensetzen.Zur Illustration des Spezifikationsansatzes werden im Folgenden Ausschnitte aus der Spezifikation des Aktivitäten-modells beschrieben; auf das Produkt-und Resourcenmodell gehen wir aus Platzgründen nicht ein (s. dazu[67,43,42]). Wir beschränken uns auf die Spezifikation des generischen Modells; auf spezifische Modelle gehen wir in Abschnitt 5 ein.…”