The Experts below are selected from a list of 2586 Experts worldwide ranked by ideXlab platform

Klaus Pohl - One of the best experts on this subject based on the ideXlab platform.

  • documenting Application specific adaptations in software product line Engineering
    Conference on Advanced Information Systems Engineering, 2008
    Co-Authors: Gunter Halmans, Klaus Pohl, Ernst Sikora
    Abstract:

    Software product line Engineering distinguishes between two types of development processes: domain Engineering and Application Engineering. In domain Engineering software artefacts are developed for reuse. In Application Engineering domain artefacts are reused to create specific Applications. Application engineers often face the problem that individual customer needs cannot be satisfied completely by reusing domain artefacts and thus Application-specific adaptations are required. Either the domain artefacts or the Application artefacts need to be modified to incorporate the Application-specific adaptations. We consider the case that individual customer needs are realised by adapting the Application artefacts and propose a technique for maintaining traceability between the adapted Application artefacts and the domain artefacts. The traceable documentation of Application-specific adaptations is facilitated by an Application variability model (AVM) which records the differences between the domain artefacts and the Application artefacts of a particular Application. The approach is formalised using graph transformations.

  • CAiSE - Documenting Application-Specific Adaptations in Software Product Line Engineering
    Notes on Numerical Fluid Mechanics and Multidisciplinary Design, 2008
    Co-Authors: Gunter Halmans, Klaus Pohl, Ernst Sikora
    Abstract:

    Software product line Engineering distinguishes between two types of development processes: domain Engineering and Application Engineering. In domain Engineering software artefacts are developed for reuse. In Application Engineering domain artefacts are reused to create specific Applications. Application engineers often face the problem that individual customer needs cannot be satisfied completely by reusing domain artefacts and thus Application-specific adaptations are required. Either the domain artefacts or the Application artefacts need to be modified to incorporate the Application-specific adaptations. We consider the case that individual customer needs are realised by adapting the Application artefacts and propose a technique for maintaining traceability between the adapted Application artefacts and the domain artefacts. The traceable documentation of Application-specific adaptations is facilitated by an Application variability model (AVM) which records the differences between the domain artefacts and the Application artefacts of a particular Application. The approach is formalised using graph transformations.

  • integration testing in software product line Engineering a model based technique
    Fundamental Approaches to Software Engineering, 2007
    Co-Authors: Sacha Reis, Andreas Metzger, Klaus Pohl
    Abstract:

    The development process in software product line Engineering is divided into domain Engineering and Application Engineering. As a consequence of this division, tests should be performed in both processes. However, existing testing techniques for single systems cannot be applied during domain Engineering, because of the variability in the domain artifacts. Existing software product line test techniques only cover unit and system tests. Our contribution is a model-based, automated integration test technique that can be applied during domain Engineering. For generating integration test case scenarios, the technique abstracts from variability and assumes that placeholders are created for variability. The generated scenarios cover all interactions between the integrated components, which are specified in a test model. Additionally, the technique reduces the effort for creating placeholders by minimizing the number of placeholders needed to execute the integration test case scenarios. We have experimentally measured the performance of the technique and the potential reduction of placeholders.

  • software product line Engineering foundations principles and techniques
    2005
    Co-Authors: Klaus Pohl, Gnter Bckle, Frank Van Der Linden
    Abstract:

    Software product line Engineering has proven to be the methodology for developing a diversity of software products and software intensive systems at lower costs, in shorter time, and with higher quality. In this book, Pohl and his co-authors present a framework for software product line Engineering which they have developed based on their academic as well as industrial experience gained in projects over the last eight years. They do not only detail the technical aspect of the development, but also an integrated view of the business, organisation and process aspects are given. In addition, they explicitly point out the key differences of software product line Engineering compared to traditional single software system development, as the need for two distinct development processes for domain and Application Engineering respectively, or the need to define and manage variability.

J. Doerr - One of the best experts on this subject based on the ideXlab platform.

  • COMPSAC - The Role of Service Abstraction and Service Variability and Its Impact on Requirements Engineering for Service-Oriented Systems
    2008 32nd Annual IEEE International Computer Software and Applications Conference, 2008
    Co-Authors: S. Adam, J. Doerr
    Abstract:

    The service-oriented paradigm typically separates the development of systems into service Engineering and Application Engineering. In our opinion, these two disciplines cannot be completely separated, as otherwise, there is no assurance that services provided by service Engineering can actually be used by Application Engineering. In this paper, we describe service-oriented requirements Engineering (SORE) as an appropriate means for mediating between the two disciplines, and we identify the provision of service capabilities on the right level of abstraction and variability as the most crucial aspects SORE has to assure. For this purpose, we present the adoption of product line technology in service- oriented architecture and its closer alignment with business process management as a promising approach, and list related principles as well as challenges we plan to address in our ongoing research.

Jens Dietrich - One of the best experts on this subject based on the ideXlab platform.

  • Australian Software Engineering Conference - Non-Monotonic Model Completion in Web Application Engineering
    2010 21st Australian Software Engineering Conference, 2010
    Co-Authors: Jevon M. Wright, Jens Dietrich
    Abstract:

    Formal models are often used to verify systems and prove their correctness, and ensure that transformed models remain consistent to the original system. However, formal techniques can also be used to add reasoning in the Engineering of models, predicting the developers intentions. On a programming level, a similar approach has been used very successfully in several web Application frameworks. Promoting formal techniques to the web Application domain is useful as web Application developers increasingly need to abstract from a growing set of target platforms and technologies. We address this need and propose model completion, a formal framework to infer modelling elements. Model completion is a non-monotonic process and formalises the notion of the intended model, permitting the web Application developer to focus on Application design rather than scaffolding. Benchmarking an implementation of this process for a platform-independent web Application modelling language illustrates its significant potential to simplify model-driven development.

S. Adam - One of the best experts on this subject based on the ideXlab platform.

  • COMPSAC - The Role of Service Abstraction and Service Variability and Its Impact on Requirements Engineering for Service-Oriented Systems
    2008 32nd Annual IEEE International Computer Software and Applications Conference, 2008
    Co-Authors: S. Adam, J. Doerr
    Abstract:

    The service-oriented paradigm typically separates the development of systems into service Engineering and Application Engineering. In our opinion, these two disciplines cannot be completely separated, as otherwise, there is no assurance that services provided by service Engineering can actually be used by Application Engineering. In this paper, we describe service-oriented requirements Engineering (SORE) as an appropriate means for mediating between the two disciplines, and we identify the provision of service capabilities on the right level of abstraction and variability as the most crucial aspects SORE has to assure. For this purpose, we present the adoption of product line technology in service- oriented architecture and its closer alignment with business process management as a promising approach, and list related principles as well as challenges we plan to address in our ongoing research.

Sacha Reis - One of the best experts on this subject based on the ideXlab platform.

  • integration testing in software product line Engineering a model based technique
    Fundamental Approaches to Software Engineering, 2007
    Co-Authors: Sacha Reis, Andreas Metzger, Klaus Pohl
    Abstract:

    The development process in software product line Engineering is divided into domain Engineering and Application Engineering. As a consequence of this division, tests should be performed in both processes. However, existing testing techniques for single systems cannot be applied during domain Engineering, because of the variability in the domain artifacts. Existing software product line test techniques only cover unit and system tests. Our contribution is a model-based, automated integration test technique that can be applied during domain Engineering. For generating integration test case scenarios, the technique abstracts from variability and assumes that placeholders are created for variability. The generated scenarios cover all interactions between the integrated components, which are specified in a test model. Additionally, the technique reduces the effort for creating placeholders by minimizing the number of placeholders needed to execute the integration test case scenarios. We have experimentally measured the performance of the technique and the potential reduction of placeholders.