Holistic Cross-Domain Cooperation for Mechatronic Product Development (Comet)
Duration: 01.04.2007 - 31.12.2009
Functionality of mechatronic systems is based on the tight interaction of several subsystems out of different domains. Thereby, each domain uses different methods, models and tools during the engineering process. Currently the overall development process is dominated by one single domain (in most cases the mechanic domain). The mechanic structure is then enriched by electric, electronic and information processing modules.
This state of practice approach barely considers the fact, that changes within one domain may have significant effects within other domains. Thus, changes made on one module will lead to time-consuming revision of effected modules, whereas not all effects of the change are known a priori.
In order to address this issue, an overall system engineering approach is needed. This includes an overall requirements- and process management with a systematic use of collaborative methods and tools. That way a synchronized cross-domain product development can be established.
The aim of this project is to provide new processes, methods and tools in order to establish a systematic, cross-domain system engineering of mechatronic products. All domains manage their requirements within a net of requirements, which may be interacting with each other. These requirements are connected with product properties using a function-oriented approach. This cross-domain net (consisting of requirements and product properties) forms an integrated and solid basis for the development of mechanic, electric, electronic and embedded software.
- Methods for cross-domain requirements engineering
- Methods for cross-domain requirements change tracking
- Engineering change management (ECM)
- Cooperation platform
- Recommendation for a nominal E/E development process
- Engineering objects and processes for later implementation within an E/E-PDM
Based on the outputs of this project, a better matching between virtual models and real components is possible during every step within the engineering process. This leads to more accurate prediction of the product behaviour and quality. Moreover, a higher stage of maturity can be established earlier within the development process.