However, it remains open how to store data on project level that enable flexible and efficient data access from different disciplines in different environments and enable backtracking to previous versions in case of defects and/or human errors. Project-level concepts enable the mapping of engineering data coming from different disciplines. Individual stakeholders apply various tools and related data storage approaches that (a) might hinder seamless interoperability and (b) include limited capability to support data versioning. Large systems engineering projects involve the cooperation of various stakeholders from different engineering disciplines. Last this work provides several perspectives when they are associated to predictive and reactive design activities. C++ implementation of structural and semantic comparison uses tools of automatic generation of source code. Besides, extraction of information is carried out without any model mapping. Designed system does not depend on any data persistence tool. Semantic analysis makes the system very flexible : partial extract of information, definition of semantic equivalences and tolerance on numerical values. From a configuration based on a structural helper (only a few lines of XML code), the software engineer automatically generates a library of structural comparison, adapted to the application data model. This generic approach guarantees some robustness for future evolutions of DMUC. This analysis is done at the meta-model level (EXPRESS language) instead of a specific data model (IFC, IFC-BRIDGE). We consider also the meaning of used concepts (semantic comparison). To do so, this thesis focuses on tracking changes within a DMUC during design process, thanks to comparison of structured information (structural information). Before that, we show that existing tools cannot be directly adapted to AEC sector. This work aims to propose mechanisms to aid DMUC synchronization. Therefore involved processes need to be specifically analysed. Civil design seems however different from design of manufactured products, because of : multiplicity and heterogeneity of actors, creation of a unique product. Concerning AEC sector Digital Mock-Up for Construction (DMUC) refers to the adaptation of previous technology to this industrial field. The results proved the accuracy and efficiency of our proposed approach.ĭigital Mock-Up (DMU) is a digital, centralized and structured representation of all productions from project actors. We performed a controlled experiment using open source eclipse modeling framework and compare our approach with an open source tool Eclipse Modeling Framework (EMF) Compare. Merge cases are used along with the comparison result in order to perform conflict resolution and merge operation. To differentiate between conflicted and non-conflicted cases, we have defined different merge cases, and established a merge policy based on merge cases. Our approach follows a 3-way model merge process, where a base and its derived versions are used for comparison. We represent models at finegrained level as graph structures, which is an intermediate representation based on graph theory. The goal of this paper is to develop a configuration management solution for model merging and conflict resolution that overcomes the challenges faced by traditional SCM systems for model-based development. New challenges of model mappings, differencing, merging, and conflict detection arise when applying file-based solution to model-driven software. File-based SCM systems consider software artifacts as a set of text files, while today’s software development is model-driven and models are the main artifacts produced in the early phases of software development process. Traditional SCM systems are file-based SCM systems, which are not adequate for performing software configuration management activities. combining of two or more versions) and so on. Controlling software artifacts evolution requires many activities to be carried out such as, construction and creation of versions, computation of mappings and differences between versions, merging (i.e. Software Configuration Management (SCM) aims to provide a controlling mechanism for the evolution of software artifacts created during software development process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |