The symbiosis between an enterprise architecture and service-oriented architecture results in so-called service-oriented enterprise architecture and brings up new problems for service-oriented enterprise systems engin...
详细信息
The symbiosis between an enterprise architecture and service-oriented architecture results in so-called service-oriented enterprise architecture and brings up new problems for service-oriented enterprise systems engineering. One of the most important is a business service quality definition, specification and evaluation. The paper proposes a formal model of enterprise business service quality evaluation framework to encompass and balance all the viewpoints and perspectives on an enterprise business service quality.
The ModelJoin language offers the definition of views that combine information from heterogeneous models. These views are currently realised by unidirectional transformations. Thus, updates to the views are not transl...
详细信息
ISBN:
(纸本)9783319420646;9783319420639
The ModelJoin language offers the definition of views that combine information from heterogeneous models. These views are currently realised by unidirectional transformations. Thus, updates to the views are not translated back to the models. In this paper, we study the view-update problem for ModelJoin view definitions. We propose translation strategies for view updates, and show that generated model constraints can be used to decide whether updated views can be translated. We provide a transformation for deriving a set of OCL constraints to check for translatability. For untranslatable cases that can be made translatable with minor fixes to the view, we provide algorithms for automatic fixes. The constraints are evaluated in two case study examples. The evaluation shows the applicability of the translation strategies, and the algorithms for automatically checking and restoring the translatability. Most of the consistent update sequences could be translated, and all inconsistent updates could be identified.
In the traditional software development cycle, requirements gathering is considered the most critical phase. Getting the requirements right first time has become a dogma in software engineering because the correction ...
详细信息
In the traditional software development cycle, requirements gathering is considered the most critical phase. Getting the requirements right first time has become a dogma in software engineering because the correction of erroneous or incomplete requirements in later software development phases becomes overly expensive. For product-service systems (PSS), this dogma and standard requirements engineering (RE) approaches are not appropriate because classical RE is considered concluded, once a product service is delivered. For PSS it is impossible to foresee all future context conditions and customization needs customers may come up with after product deployment. In addition, the services supporting a complex hardware-software product depend on the individual product configuration a customer requires. For example, when a standard laser machine is equipped with one or more special sensors, new services may be needed that depend on sensor data from these new sources combined with other data generated by the standard machine configuration. Thus, we claim that RE needs to be extended to the deployment phase of a product and an agile approach is required to cope with emerging hardware and software requirements as a PSS is marketed. In this paper, a novel view-based model-driven engineering approach is proposed that enables collaborative product-service design and customization and copes with evolving, incomplete and unforeseen requirements. A prototype has been implemented as a Proof-of-Concept (PoC) and is currently validated on four industrial pilot cases as part of the H2020 project ICP4Life. (C) 2017 The Authors. Published by Elsevier B.V.
In the traditional software development cycle, requirements gathering is considered the most critical phase. Getting the requirements right first time has become a dogma in software engineering because the correction ...
详细信息
In the traditional software development cycle, requirements gathering is considered the most critical phase. Getting the requirements right first time has become a dogma in software engineering because the correction of erroneous or incomplete requirements in later software development phases becomes overly expensive. For product-service systems (PSS), this dogma and standard requirements engineering (RE) approaches are not appropriate because classical RE is considered concluded, once a product service is delivered. For PSS it is impossible to foresee all future context conditions and customization needs customers may come up with after product deployment. In addition, the services supporting a complex hardware-software product depend on the individual product configuration a customer requires. For example, when a standard laser machine is equipped with one or more special sensors, new services may be needed that depend on sensor data from these new sources combined with other data generated by the standard machine configuration. Thus, we claim that RE needs to be extended to the deployment phase of a product and an agile approach is required to cope with emerging hardware and software requirements as a PSS is marketed. In this paper, a novel view-based model-driven engineering approach is proposed that enables collaborative product-service design and customization and copes with evolving, incomplete and unforeseen requirements. A prototype has been implemented as a Proof-of-Concept (PoC) and is currently validated on four industrial pilot cases as part of the H2020 project ICP4Life.
暂无评论