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

Ivica Crnkovic - One of the best experts on this subject based on the ideXlab platform.

  • a classification framework for software Component models
    IEEE Transactions on Software Engineering, 2011
    Co-Authors: Ivica Crnkovic, Severine Sentilles, Aneta Vulgarakis, Michel R V Chaudron
    Abstract:

    In the last decade, a large number of different software Component models have been developed, with different aims and using different principles and technologies. This has resulted in a number of models which have many similarities, but also principal differences, and in many cases unclear concepts. Component-Based Development has not succeeded in providing standard principles, as has, for example, object-oriented Development. In order to increase the understanding of the concepts and to differentiate Component models more easily, this paper identifies, discusses, and characterizes fundamental principles of Component models and provides a Component Model Classification Framework Based on these principles. Further, the paper classifies a large number of Component models using this framework.

  • a Component model for control intensive distributed embedded systems
    Component-Based Software Engineering, 2008
    Co-Authors: Severine Sentilles, Tomas Bures, Aneta Vulgarakis, Jan Carlson, Ivica Crnkovic
    Abstract:

    In this paper we focus on design of a class of distributed embedded systems that primarily perform real-time controlling tasks. We propose a two-layer Component model for design and Development of such embedded systems with the aim of using Component-Based Development for decreasing the complexity in design and providing a ground for analyzing them and predict their properties, such as resource consumption and timing behavior. The two-layer model is used to efficiently cope with different design paradigms on different abstraction levels. The model is illustrated by an example from the vehicular domain.

  • Component Based Development process and Component lifecycle
    International Conference on Software Engineering Advances, 2005
    Co-Authors: Ivica Crnkovic, Michel R V Chaudron, Stig Larsson
    Abstract:

    The process of Component- and Component-Based system Development differs in many significant ways from the "classical" Development process of software systems. The main difference is in the separation of the Development process of Components from the Development process of systems. This fact has a significant impact on the Development process. Since the Component-Based approach is a relatively young approach in software engineering, the main emphasis in the area has been in Development of technologies, while process modeling is still an unexplored area. This paper analyses the basic characteristics of the Component-Based approach and its impact on the Development process and lifecycle models. The generic lifecycle of Component-Based systems and the lifecycle of Components are discussed, and the different types of Development processes are discussed in detail: architecture-driven Component Development, productline Development and COTS-Based Development. Finally a short case study illustrates the principles and specifics of Component-Based processes.

  • Component-Based Development Process and Component Lifecycle
    Journal of Computing and Information Technology, 2005
    Co-Authors: Ivica Crnkovic, Stig Larsson, Michel R V Chaudron
    Abstract:

    In recent years Component-Based Development has become an established approach. Component-Based Software Engineering (CBSE) that deals with the entire lifecycle of Component-Based products has been focused on technologies related to design and implementation of software Components and systems built from software Components. The experience has shown that pure technologies alone are not enough. A CBSE approach requires certain changes in Development and life cycle processes. However, very few CBSE works, either research or practical, have addressed these topics. This paper describes principle differences of Component-Based and non- Component Based processes. Also we give an overview of a case study from a company that applies Component-Based approach.

  • saveccm a Component model for safety critical real time systems
    Proceedings. 30th Euromicro Conference 2004., 2004
    Co-Authors: Hans Hansson, Ivica Crnkovic, M Aakerholm, Martin Torngren
    Abstract:

    Component-Based Development has proven effective in many engineering domains, and several general Component technologies are available. Most of these are focused on providing an efficient software-engineering process. However for the majority of embedded systems, run-time efficiency and prediction of system behaviour are as important as process efficiency. This calls for specialized technologies. There is even a need for further specialized technologies adapted to different types of embedded systems, due to the heterogeneity of the domain and the close relation between the software and the often very application specific system. This work presents the SaveCCM Component model, intended for embedded control applications in vehicular systems. SaveCCM is a simple model in which flexibility is limited to facilitate analysis of real-time and dependability. We present and motivate the model, and provide examples of its use.

Magnus Larsson - One of the best experts on this subject based on the ideXlab platform.

  • building reliable Component Based software systems
    2002
    Co-Authors: Ivica Crnkovic, Magnus Larsson
    Abstract:

    Preface. Introduction. The Definition and Specification of Components. Software Architecture and Components. Developing Software Components. Using Software Components. Software Product Lines. Real-Time Software Components. Case Studies: Component-Based Development in Industrial Applications.

  • a case study demands on Component Based Development
    International Conference on Software Engineering, 2000
    Co-Authors: Ivica Crnkovic, Magnus Larsson
    Abstract:

    Building software systems with reusable Components brings many advantages. The Development becomes more efficient, the realibility of the products is enhanced, and the maintenance requirement is significantly reduced. Designing, developing and maintaining Components for reuse is, however, a very complex process which places high requirements not only for the Component functionality and flexibility, but also for the Development organization. In this paper we discuss the different levels of Component reuse, and certain aspects of Component Development, such as Component generality and efficiency, compatibility problems, the demands on Development environment, maintenance, etc. The evolution of requirements for products generates new requirements for Components, if Components are not enough general and mature. This dynamism determines the Component life cycle where the Component first reaches its stability and later degenerates in an asset that is difficult to use, difficult to adapt and maintain. When reaching this stage, the Component becomes an obstacle for efficient reuse and should be replaced. Questions related to use of standard and de-facto standard Components are addressed specifically. As an illustration of reuse issues, we present a successful implementation of a Component-Based system which is widely used for industrial process control.

Dirk Muthig - One of the best experts on this subject based on the ideXlab platform.

  • generic implementation of product line Components
    Lecture Notes in Computer Science, 2003
    Co-Authors: Dirk Muthig, Thomas Patzke
    Abstract:

    An argument pro Component-Based software Development is the idea of constructing software systems by assembling preexisting Components instead of redeveloping similar or identical functionality always from scratch. Unfortunately, integrating existing Components practically means adaptation and use rather than use only, which makes an ideal Component-Based Development hard to realize in practice. Product line engineering, however, tackles this problem by making Components as generic as needed for a particular product family and thus allows Component reuse. Such a Component covers variabilities and thus its implementation must consider variabilities as well. In this paper, we describe a process for implementing generic product line Components and give an overview of variability mechanisms at the implementation level, illustrated by a running example, a generic test Component.

  • Component Based product line engineering with uml
    2001
    Co-Authors: Colin Atkinson, Dirk Muthig, Christian Bunse, Joachim Bayer, Erik Kamsties, Oliver Laitenberger, Roland Laqua, Barbara Paech, Jurgen Wust, Jorg Zettel
    Abstract:

    Component-Based Development promises to revolutionize the way in which software is developed and maintained. However, contemporary Component technologies, such as COM+/.NET, EJB/J2EE and CORBA, only support Components in the final, implementation-oriented stages of Development, leaving the earlier stages of analysis and design to be organized in largely traditional, non-Component oriented ways. This book describes the KobrA method, which supports a model-driven, UML-Based representation of Components, and a product line approach to their Development and evolution. This enables the benefits of Component-Based Development to be realized throughout the software life-cycle, and allows the reusability of Components to be significantly enhanced.

  • Component Based product line Development the kobra approach
    Software Product Lines, 2000
    Co-Authors: Colin Atkinson, Joachim Bayer, Dirk Muthig
    Abstract:

    The product line and Component-Based approaches to software engineering both hold the potential to significantly increase the level of reuse in industrial software Development and maintenance. They also have complementary strengths, since they address the problem of reuse at opposite ends of the granularity spectrum; product line Development essentially supports “reuse in the large” while Component Based Development supports “reuse in the small.” This paper describes a method, Kobr A, that cleanly integrates the two paradigms into a systematic, unified approach to software Development and maintenance. Key synergies resulting from this integration include support for the rapid and flexible instantiation of system variants, and the provision of methodological support for Component-Based framework Development.

Sebastian Linz - One of the best experts on this subject based on the ideXlab platform.

  • Component-Based Development of Web-enabled eHome services
    Personal and Ubiquitous Computing, 2005
    Co-Authors: Michael Kirchhof, Sebastian Linz
    Abstract:

    In this paper we will take a look at the inside of connected homes, which build up complex IT systems. The building blocks of such systems are electronic devices, networks, and services , which empower the user to interact with his environment. Web-enabled eHome services offer functionality to the user by abstracting from devices and realize connectivity in three dimensions: (1) inner connectivity, (2) outer connectivity, and (3) integrative connectivity. Generations of Web-enabled eHome services have been developed Based on proprietary hard- and software. Today, an extensible and modular platform is required for forward-looking design and implementation of such services. We describe a new view on Component-Based Development of Web-enabled eHome services. While there is an adequate framework (open service gateway initiative) for the Development of state-of-the-art Web-enabled eHome services, there is no knowledge about the system and service structure and its architecture in detail. We propose an 3-layer system structure (called PowerArchitecture), which incorporates several established design ideas and show how this cookbook makes system architects’ and developers’ life easier.

  • Component Based Development of web enabled ehome services
    Lecture Notes in Computer Science, 2004
    Co-Authors: Michael Kirchhof, Sebastian Linz
    Abstract:

    The scope of Web-enabled eHome services covers both automated homes and automated industry facilities. Web-enabled eHome services provide a fully integrated view onto distributed systems comprising automated homes, back-end systems of providers, communication protocols, and services which make distribution aspects transparent. Future platforms should make the Development and deployment as easy as achievable. Access should be possible by the way of all communication devices (e.g. desktop computers, PDAs, mobile phones) and all communication networks. Also, all appliances, ubiquitous devices, and their networking protocols have to be supported. Generations of Web-enabled eHome services have been developed Based on proprietary hard- and software. Today, an extensible and modular platform is required for forward-looking design and implementation of such services. One of the main requirements is, that the developed system is maintenance-free and the system brings itself in an operable condition. For setup tasks, both the end-user and a remote operator should be able to execute necessary steps. It can be observed that services build up hierarchies. We propose a 3-layer system structure, which can be taken to account in system design. Software Components grouped by service layers can then be realized in order to implement concrete services. Based on the OSGi platform, we have developed sample services. Gained experience is used for verification of our assumptions. Summarizing, we propose a cookbook for convenient Development and deployment of services of the described nature.

Thomas Patzke - One of the best experts on this subject based on the ideXlab platform.

  • generic implementation of product line Components
    Lecture Notes in Computer Science, 2003
    Co-Authors: Dirk Muthig, Thomas Patzke
    Abstract:

    An argument pro Component-Based software Development is the idea of constructing software systems by assembling preexisting Components instead of redeveloping similar or identical functionality always from scratch. Unfortunately, integrating existing Components practically means adaptation and use rather than use only, which makes an ideal Component-Based Development hard to realize in practice. Product line engineering, however, tackles this problem by making Components as generic as needed for a particular product family and thus allows Component reuse. Such a Component covers variabilities and thus its implementation must consider variabilities as well. In this paper, we describe a process for implementing generic product line Components and give an overview of variability mechanisms at the implementation level, illustrated by a running example, a generic test Component.