Model-driven Service Engineering with SoaML

Elvesæter, Brian; Carrez, Cyril; Mohagheghi, Parastoo; Berre, Arne-Jørgen; Johnsen, Svein G.; Solberg, Arnor

doi:10.1007/978-3-7091-0415-6_2

Cited by 21 publications

(26 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are four stages: A) Preliminaries: This stage uses the SModel to create the base PModel using PUMA, and creates the SModel/PModel mapping table. Pattern application begins at step (4), where the designer selects a candidate pattern for its own reasons (e.g. maintainability).…”

Section: Process Overviewmentioning

confidence: 99%

“…This paper describes (A) -(C) but does not address the implementation of the transformation in step (D). The SOA SModel is captured in UML with the OMG profiles SoaML (Service Oriented Architecture Modeling Language) [4] and MARTE (Modeling and Analysis of Real-Time and Embedded Systems) [5] for performance information. The Role Based Modeling Language (RBML) [6] is used to formally define each SOA design pattern in terms of first, the set of SModel elements that represent the problem addressed by the pattern and second, those that constitute the solution.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Exploring SOA Pattern Performance using Coupled Transformations and Performance Models

Mani

Petriu

Woodside

2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Service Oriented Architecture (SOA) patterns can be applied to improve different qualities of SOA designs. The performance impact of a pattern (improvement or degradation) may affect its use, so we assess its impact by automatically generated performance models for the original design and for each candidate pattern and pattern variation. This paper proposes a technique to incrementally propagate the changes from the software to the performance model. The technique formally records the refactoring of the design model when applying a pattern, and uses this record to generate a coupled transformation of the performance model. The SOA design is modeled in UML extended with two profiles, SoaML and MARTE; the patterns are specified using Role Based Modeling and the performance model is expressed in Layered Queuing Networks. Application of the process, and pattern performance exploration, is demonstrated on a case study.

show abstract

Section: Process Overviewmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Exploring SOA Pattern Performance using Coupled Transformations and Performance Models

Mani

Petriu

Woodside

2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…The MDSE methodology based on MDA guides solution architects in how to specify services that are aligned with the business process models (Elvesaeter, B., 2011). In our model-driven approach shown in Figure 7, the Business Architecture is first built as a Computation Independent Model (CIM), the computational and implementation details of the system are hidden at this level of description.…”

Section: Outline Of the Approachmentioning

confidence: 99%

“…The BAM further describes the services architecture of the business community and the service contracts between the business entities participating in the community as illustrated in the SoaML diagrams. The Business Process Modeling Notation (BPMN) is often used to describe business processes while mapping rules between BPMN and SoaML frequently appear in articles on MDSE (Elvesaeter, B., 2011). Note that we decided to use the activity diagram at this level in contrast with BPMN.…”

Section: Business Architecture Designmentioning

confidence: 99%

Model-Driven Design and Validation of Service Oriented Architecture Based on Devs Simulation Framework

Hu¹,

Huang²,

Wu³

et al. 2014

STSC

View full text Add to dashboard Cite

It is very important to validate functional requirements and evaluate non-functional requirements in earlier design phase of a Service Oriented Architecture (SOA) by executable modeling methodology. To make SOA executable, basically, most of the proposed approaches can be divided into two categories: formalism-based ones and modeldriven ones, which both have the advantages and limitations. In this paper, we take advantage of both formalismbased and model-driven methodologies to specify a unified model-driven design and validation approach to SOA. This approach bridges generic service design and universal simulation paradigm with formal bases and practical implementation. To achieve this goal, we first extend the DEVS modeling language (DEVSML) to support nondeterministic state transition and enhance its capability to describe complex behavior of systems. Then we provide an automated transformation process using Extended DEVSML as a model transformation intermediary to bring together Model Driven Service Engineering (MDSE) with Service oriented architecture Modeling Language (SoaML) and Modeling & Simulation (M&S) methodology based on Discrete Event System Specification (DEVS). To demonstrate the applicability of this approach, we introduce an aircraft docking process in an airport scenario as the case study.

show abstract

“…Although this is very promising, it does not allow specifying the architecture of the overall system which violates the criterion of enabling the user to carry out a complete system specification. Another methodology using SoaML introduced in [13] closely follows the processes defined in the Model-driven architecture (MDA) approach published by the Object Management Group. Tool support is granted by the modeling tool "Modelio".…”

Section: Development Of Service-oriented Applicationsmentioning

confidence: 99%

Developing self-adaptive automotive systems

Wagner

Meroth

Zöbel

2013

Des Autom Embed Syst

View full text Add to dashboard Cite

Future Driving Assistance Systems (DAS) will have to react to changes within the system at runtime. This might be the case in Car-to-X systems where the availability of communication partners changes dynamically. Another example are systems like DAS for truck and trailer combinations where a trailer might be disconnected and replaced by another one several times a day. State-of-the-art DAS are not capable of handling these runtime changes. In our approach we make usage of the principles of Service-orientation to generate self-adaptive DAS on architectural level. But this technical approach requires the definition of a development process that fits into the practices within the automotive industry. This paper introduces SOMA4DDAS, a model-based development process based on the UML profile SoaML. SOMA4DDAS describes a tri-phase procedure to transfer an idea for a DAS into a detailed specification of the application and the Services involved. These phases are integrated into the "core process for system and software development" (CPSSD), a standard process within the automotive industry. The paper illustrates the benefits of this approach by developing a truck and trailer DAS consisting of 13 different Services.

show abstract

Model-driven Service Engineering with SoaML

Cited by 21 publications

References 4 publications

Exploring SOA Pattern Performance using Coupled Transformations and Performance Models

Exploring SOA Pattern Performance using Coupled Transformations and Performance Models

Model-Driven Design and Validation of Service Oriented Architecture Based on Devs Simulation Framework

Developing self-adaptive automotive systems

Contact Info

Product

Resources

About