Title: Model Driven Integration: CMS-1 CS Case Study

Author(s): University of York

Publication Event: Software Systems Engineering Initiative [SSEI] - Released documents

Publication Date: 2011-05-04

Resource URL: https://scsc.uk/r1049.pdf

Abstract:

The complexity and scale of software that uses a mixture of software components from the supply chain (new code, third-party (COTS), legacy) leads to unpredictable system integration, one of the biggest risks in software-intensive, software-dependent projects. Modern projects use model driven engineering where models are created long before the source code. There is a potential benefit (risk reduction) by integrating models, so issues which might otherwise only become apparent at software integration are detected earlier (before any new code is written) and can be resolved when it is much cheaper to do so. The opportunity and value added lies in the provision of support for model driven integration where models are described using different platforms (e.g. industry partners using UML (Unified Modelling Language), MODAF (Ministry of Defence Architecture Framework) or Matlab Simulink are likely to have significant problem with this).