An object Versioning system to support collaborative design within a Concurrent Engineering context

Santoyridis, I.; Carnduff, T. W.; Gray, W. A.; Miles, John Christopher

doi:10.1007/3-540-63263-8_21

Cited by 11 publications

(5 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In Ergonomics, Leplat 1141 considers the collective activity as an activity in which a set of people work for a same goal, consult each actor, coordinate and cooperate. Many collaborative systems called CSCW were proposed in aim to help actors in their design activity [20], [lo]. These kinds of systems can be used to help to share knowledge during design process [ 121.…”

Section: About Collaborative Designmentioning

confidence: 99%

A model of the work - situation in order to improve traceability process in collaborative design

Belkadi¹,

Bonjour²,

Dulmet³

2005

Proceedings of the Ninth International Conference on Computer Supported Cooperative Work in Design, 2005.

View full text Add to dashboard Cite

The collective character of design activities requires the development of methods and tools in order fo control jhe design process and the collaborative activities. The workgroup is assimilated to a system composed of entities, which are in various interactions managed by a set of coordinatio~ and control mechanisms. We present here a model of the design situation in collaborative works using the notion of inter-related entities. We also propose also a cluss$cation of the di#erent interactions between theseentities. 73re perspectives of this work are to contribute to the improvement of support took for the collaborative design situation and knowledge capitalization.

show abstract

Section: About Collaborative Designmentioning

confidence: 99%

A model of the work - situation in order to improve traceability process in collaborative design

Belkadi¹,

Bonjour²,

Dulmet³

2005

Proceedings of the Ninth International Conference on Computer Supported Cooperative Work in Design, 2005.

View full text Add to dashboard Cite

show abstract

“…Most proposed configuration management systems are either superficial or otherwise unsatisfactory. Versions of different objects are bound together either statically (Krishnamurthy and Law, 1995;Andonoff et al, 1996;Ahmed and Navathe, 1991;Kafer and Schoning, 1992;Santoyridis et al, 1997) or dynamically to form a configuration. Dynamic references are resolved later by placing the versions that are to be combined together in the same layer (Katz, 1990), environment (Dittrich and Lorie, 1988), database version (DBV) (Cellary and Jomier, 1990) or assigning these versions to the same configuration identifier (Carnduff, 1993).…”

Section: Related Workmentioning

confidence: 99%

“…An object is said to be statically bound if it uses a direct reference to a specific version of its component objects (Ahmed and Navathe, 1991;Krishnamurthy and Law, 1995;Oussalah and Urtado, 1997;Andonoff et al, 1996;Santoyridis et al, 1997;Kafer and Schoning, 1992). On the other hand, if an object refers to the generic version of a constituent object instead of a specific version of that object then it is said to be dynamically bound (Kim et al, 1989(Kim et al, , 1991Sciore, 1994;Dittrich and Lorie, 1988;Carnduff, 1993;Katz, 1990).…”

Section: Introductionmentioning

confidence: 99%

“…To this end, one of the key issues required is an appropriate logical organisation of database support which facilitates the separation of private and shared work. Most of the systems in the literature that support collaborative design have adopted a hierarchical database architecture (Chou and Kim, 1986;Santoyridis et al, 1997;Katz, 1990;Kim et al, 1991;Loomis, 1992;Miles et al, 2000). The hierarchical structure comprises private workspaces, one for each individual designer, many project (or global) databases, one for each group (or assembly) and a single public database for the released design.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Configuration management in evolutionary engineering design using versioning and integrity constraints

Carnduff

Goonetillake²

2004

Advances in Engineering Software

View full text Add to dashboard Cite

“…Note that object versioning is an essential requirement in complex applications such as CAD, etc., where there is often a need to create new versions of an object from its existing single or multiple versions. Work has been carried out to provide versioning support for objects residing in object-oriented databases [2,3,[19][20][21][22][23]. However, these all concentrate on version modelling and workgroup support and tend to lose sight of the global pictureevolution.Our approach, in contrast to those above, views evolution as a process which affects the whole database and, therefore, concentrates on database evolution.…”

mentioning

confidence: 99%

A database evolution taxonomy for object-oriented databases

Rashid

Sawyer

2005

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

Like any other database application, object database applications are subject to evolution. Evolution, however, is a critical requirement in object-oriented databases as it is a fundamental characteristic of complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Object-oriented databases are inherently suited to supporting such applications. In this paper we present a database evolution taxonomy for object-oriented databases. We describe a conceptual database model and use it to define the taxonomy. We also present the various invariants and rules governing the various evolution operations. The execution sequence of rules is described. An implementation of the database model and the evolution taxonomy in the Semi-Autonomous Database Evolution System (SADES), is discussed. The implementation employs aspect-oriented programming techniques to provide a flexible means of transforming objects upon evolution, and implementing some application-specific evolution primitives. A case study compares the evolution taxonomy with existing evolution approaches. The comparison demonstrates that the taxonomy and its corresponding implementation in SADES provide improved coverage of the fundamental evolution operations to which an object database might be subjected. At the same time, erosion of the database structure is avoided by maintaining a coherent and comprehensible view of historical changes. A. RASHID AND P. SAWYER• to correct mistakes in the database design; • to add new features during incremental design; and • to reflect changes in the structure of the real-world artefacts modelled in the database. Therefore, like any other database application, object database applications are subject to evolution.However, evolution is a critical requirement in object-oriented databases because their inherent support for complex data types makes them highly suitable for supporting complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Due to the underlying rich data model (in contrast with conventional data-intensive record-processing applications), these applications require dynamic modifications to both the data residing within the database and the way the data has been modelled, i.e., both the objects residing within the database and the schema of the database are subject to change. Furthermore, there is a requirement to keep track of the change in case it needs to be reverted. Therefore, in addition to offering traditional database functionality such as persistence, transaction management, recovery and querying facilities, an objectoriented database management system needs to provide the ability to evolve dynamically, through various versions, both the objects and the class definitions (which form the database schema) in the database.An object database is, therefore, subject to three types of changes over its lifetime.• Class hierarchy modification: introduction of new classes, deletion of existing classes and modificatio...

show abstract

An object Versioning system to support collaborative design within a Concurrent Engineering context

Cited by 11 publications

References 8 publications

A model of the work - situation in order to improve traceability process in collaborative design

A model of the work - situation in order to improve traceability process in collaborative design

Configuration management in evolutionary engineering design using versioning and integrity constraints

A database evolution taxonomy for object-oriented databases

Contact Info

Product

Resources

About