1. Initial Situation

The paradigm of subject-orientation and the modelling language PASS are not mainstream process modelling methods, but deliver several advantages in comparison to the classic input-output process thinking (which makes it worthwhile to convert different subject-oriented models into standardized subject-oriented models). In the past, the Metasonic S-BPM Suite was a cornerstone in the research domain of subject-orientation. However, it is not being maintained anymore, yet companies do still have their valuable knowledge saved in process models built with the Metasonic Suite.

During those last years, the SO-research-community-driven development of an OWL Standard for the Subject-Oriented Parallel Activity Specification Schema (PASS) modeling language provided the foundations for a standardization format for process models built in PASS. Yet models created with Metasonic are not compatible with that standard, and converting processes modelled in another subject-oriented language into the OWL-Standard for PASS helps in understanding the usability and scope of PASS in comparison to other modelling languages.

2. Research Goal/Research Questions

 The general goal of this thesis is to develop a converter software that can transform models from Metasonic to the PASS Model OWL-Exchange Standard.

This requires understanding what differences lie between those two model-file formats and why or why not it is possible to convert (certain concepts) between them.

In detail, this requires: …

• To understand the subject-oriented paradigm and PASS to show the advantages and disadvantages of it.
• The existing community OWL/RDF bases exchange standard, the underlying technologies
• To understand how the underlying modelling format of the Metasonic Suite and possible dialects of the PASS language are different in comparison to standard and what the advantages and disadvantages of that are.

Open questions are:

•  How can process models built with the Metasonic Suite be converted to the PASS Model OWL-Exchange Standard?
• Are there certain concepts within the Metasonic PASS models that cannot be converted to PASS standard models, and why?
  • What advantages do those non-convertible concepts offer, and why does standard PASS not offer them?
• Is a converter a better solution than modelling the processes directly in the new standard/modelling language?
• What are the differences/advantages and disadvantages of standard PASS, viewing it directly compared to the Metasonic Suite format?

3. Planned Method/Planned structure

The planned steps are to understand the subject-oriented paradigm, process models built in the Metasonic Suite by analyzing relevant literature, documentations, and studying examples as well as the suite itself

To develop the converter software engineering methods, such as requirement (including choice of language – ideal target is C#) analysis, documentation (e.g., with UML diagrams), and iterative development, will be applied. To assess and review the converter.