System Data Management: an inter-disciplinary collaboration architecture for systems engineering

This paper presents a novel approach to integrating systems engineering (SE) artifacts and methods with discipline-specific detailed design artifacts and processes, for the purpose of facilitating inter-disciplinary collaboration. In particular, it addresses the lifecycle management of complex products involving mechanical, electrical, electronics and software aspects, and being designed following a formal product development methodology. The primary motivation of the approach is to capture and maintain the traceability between the concrete artifacts stored in discipline-specific “repositories” and the abstract artifacts used to support system-level decisions as well as system integration. The proposed approach acknowledges the fundamental differences that exist between the various engineering disciplines and therefore favors a loose coupling based on a process-centric management of the artifacts traceability links. These considerations lead to an interdisciplinary collaboration and infrastructure pattern called “system data management” (SDM), with the role of enforcing the integrity of the inter-disciplinary traceability between artifacts. As a byproduct, this approach suggests a novel perspective on product data management (PDM) and software configuration management (SCM) integration that sharply contrasts with point-to-point integration solutions. The authors have implemented a prototype based on a service-oriented architecture (SOA) and existing PDM and SCM technologies.

By: José Gomes; Man-Mohan Singh; Mila Keren; Sai Zeng; Julia Rubin; Laurent Balmelli; Ioana Boier-Martin

Published in: RC23613 in 2005


This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.


Questions about this service can be mailed to .