In the framework of INCOSE’s strategic initiative, the Systems Engineering Vision 2020, one of the main areas of focus is model-based systems engineering. In keeping with this emphasis, the European Southern Observatory (ESO) is collaborating since 2007 with the German Chapter of INCOSE (GfSE) in the form of the “MBSE Challenge” team SE2.
The team’s task is to demonstrate solutions to challenging problems using MBSE. The Active Phasing Experiment (APE), a European Union Framework Program 6 project, was chosen as the subject of the SE2 Challenge Team. Many technical products in the telescope domain show an increasing integration of mechanics with electronics, information processing, and also optics, and can therefore be rightly considered as optomechatronic systems.
The SysML models were created by reverse engineering from existing documentation and from interviews with systems engineers.
The introductory presentation provides information on context, goals, and results of the Challenge team.
Our system case study is the Active Phasing Experiment technology demonstrator for the future European Extremely Large Telescope, which is a high-tech, interdisciplinary optomechatronical system in operation at the Paranal observatory.
The next generation of telescopes needs to collect significantly more light than current telescopes, therefore requiring larger reflecting surfaces that consist of many individual mirror segments. Due to different disturbances (such as vibrations, wind, and gravity), the segments must be actively controlled to provide a continuous mirror surface with a phasing error of only a few nanometers over the main mirror’s diameter of 42 m. The main challenge is to correctly detect the positioning errors of the segments via specific phasing sensors in order to create a continuous mirror surface.
APE was developed to evaluate those sensors, and was installed on one of the 8 m telescopes that constitutes part of the Very Large Telescope in Chile (VLT) for sky tests. For the installation at the telescope it had to comply with various mechanical, electrical, optical, and software interfaces. APE consists of about two hundred sensors and actuators such as wheels, translation stages, lenses, detectors, mirrors, light sources, an interferometer, and twelve computing nodes for control. Since APE had to be deployed in the test lab and in an already existing telescope, for each context it was necessary to model variants of function, interfaces, and structure. All of these characteristics made APE well suited to evaluate the potential of SysML in tackling similar issues.
|Date||Milestone||Status||Point of Contact|
|IW11||Cookbook and reference model, issue 1||Completed||Robert|
|IW11||Ontologies for modeling recipes||Completed||Robert|
|IW11||OCSMP white paper||Completed||Tim|
|IW11||MBSE modeling plugin||Completed||Michele|
|IW11||Model Based Document||Completed||Michele|
|2011-02-03||Requirements Modeling - getting textual requirements from models||Rudi|
|2010-12-16||Variant Modeling with SysML||Tim|
|2010-12-02||Model Based Document Generation||Michele|
|April 2009||Modeling Recipes and Challenges with SysML II||Robert|
|Nov 2008||Modeling Recipes and Challenges with SysML I||Robert|
|Robert Karban (lead)||ESOemail@example.com|
|Tim Weilkiens||oose GmbHfirstname.lastname@example.org|
|Berthil Muth||HOOD Groupemail@example.com|
|Christian Zingel||IPEK – Institut für Produktentwicklungfirstname.lastname@example.org|
SysML is a graphical language and defines a modeling elements with a notation, a formal syntax, and semantics. The SysML model is not merely a mental abstraction, but a collection of complex data structures that can be edited, augmented, queried, and reported on by means of a suitable tool, which is an indispensable pillar for MBSE. Like any language (formal or informal), it can be used in many different ways, including many wrong ways.
The main goals of the SE2 MBSE Challenge Team are to
SysML is a language and does not prescribe any methodology. For example, SysML allows to use the «allocate» relationship between nearly any model element. But where is this feature useful in a specific project? How can the relationship be determined from the model, e.g. for traceability? What are the consequences of having an «allocate» relationship between two elements? You do not find answers to these questions in the SysML specification.
SE2 did not define a MBSE methodology. The modeling work is based on different existing methodologies like SYSMOD, OOSEM, or Wymore´s MBSE theory. The Challenge Team has found some best practices and modeling guidelines to complement them but each project needs its own specific set of methods (see the Survey of Methodologies for more information). The results are supposed to be mostly method independent.
You find a complete version of the model and other material like presentations on our website: Telescope and Space Systems Modeling Challenge Teams.
The Cookbook addresses a variety of modeling areas, illustrated with real world examples.
The APE SysML Model provides the complete model navigable online in any web-browser.
From the SE2 Readings section you can download most given presentations and published papers related to MBSE and SysML by the SE2 Challenge team members.
In Downloads section you will find the complete model in MagicDraw´s mdzip format as well as the Open-Source MBSE Plugin for the modelling tool, which helps in querying the model, create automatically basic organizational structure, extracts model variants, and supports model based document generation based on DocBook.
SysML is a new language. This creates two inherent challenges: Is SysML sufficiently mature for real projects and is it accepted by a wide range of systems engineers? Especially the fact that SysML is based on UML sheds a special light on these challenges. Could a modeling language, which was initially defined for software development, be used to model systems and will systems engineers accept a language with origins in the software discipline? An overall result of our project is, that this question can be answered with yes.
The APE project is a pretty good challenge for SysML. It is complex, interdisciplinary without a special focus on software; it is a real system and no simplified coffee machine as often used as demonstration project. Although we found that SysML is practicable to model complex systems, we have found a list of SysML shortcomings.
The most significant ones are:
We will continue working on these topics.
This section contains information how the experiences of the Challenge team are applied to a new project, namely the Square Kilometer Array.
One example is the model of Level 1 Requirements:
This section contains information how the experiences of the Challenge team are applied to a new project, namely the telescope control system of the E-ELT.
The document is modeled in the same model as the system, using UML/SysML elements. A subset of the DocBook markup language is mapped to stereotypes, and applied to UML/SysML model elements, e.g. chapter to package, paragraph to comment. The MBSE plug-in which you can download from this site creates a DocBook file from the model. Note, that it is just a proof of concept with limitations. For example, only a limited number of DocBook elements are supported but sufficient to make reasonable use of it.
The plug-in can be downloaded here: MBSE Plugin.
The advantages are manifold
There are also disadvantages (which we hope will be solved by tool vendors in the future…)
This section will contain progress on Model Execution of SysML models.