In the domain of embedded software systems the increasing complexity of the functionality as well as the increase in variations caused by product lines requires a modular design process, separating function-based and component-based design. As a consequence, functional integration becomes a central task in the development process, to avoid unforeseen interaction. While currently functional integration often is delayed to module integration, leading to a late detection of interactions, here we suggest a methodical approach to the early integration of functions to construct a logical component-oriented architecture. 1

In this paper we introduce the concept of service-based modeling and integrate the modeling techniques into existing development processes. We focus on services in the different phases of the modeling and introduce appropriate models as well as suitable notations. A small example from the automotive domain is used throughout the paper to illustrate the approach.

Telecommunication operators provide services and enable customers to compose their own packages of services. While designing a service-oriented system, deciding whether a service interaction is desired or harmful is a subjective choice which depends on the requirements expressed by the user with respect to the service integration. In this paper, we define both a formalism and a methodology which, respectively, allows us to automatically analyze a class of interactions based on specification consistency, and implements the previous analysis. For the latter (i.e. the methodology), we take advantage of both specifier expertise and formal methods. Hence, adding a new service on a system consists in a static design step providing a consistent specification and thus aiming at reinforcing the specification quality, taking into account the expert choices. Service requirements are expressed by means of an axiomatic formalism which includes variables, invariant properties and state transition rules (str). The interaction analysis is based on algorithms which check specification consistency. Each detected interaction is then avoided thanks to an expert choice correcting the anomaly.

Services as a basic notion are helpful in two respects: on the one hand, services are used to structure the specification of a system easing understand and reasoning about the system; on the other hand, services can also be used as design principle of the implementation architecture. This paper presents an approach for developing software systems using services as the central development concept. A concrete case study, namely the development of a control unit for an automotive seat adjustment system, clarifies the proposed service-based development process.

Service-based systems engineering is a recent paradigm that has proven useful for the development of multifunctional systems, whose functions may be used in different contexts and have strong interrelations and dependencies between each other. Integrated into a service-oriented development process, we present an approach for tool supported design of services and execution scenarios describing their interaction, using the tool AUTOFOCUS. It includes the application of simulation, verification of typical requirements for service-based systems using model checking, and code generation. We report on our experience with this approach by means of a case study from the automotive domain, a fairly new field of application for service-based systems engineering. 1.

Embedded software systems are increasingly constructed using interacting functionalities, leading to the development of networks of communicating software components distributed over connected processors. At the same time, the growing complexitiy of the functionality as well as the increase in variations caused by product lines requires a modular development process. As repeatedly witnessed, e.g., in embedded automotive applications, without a suitable notion of interface specifications, integration faults are often only detected after deployment. Here, timed interface specifications can be used to simplify a modular development process, including mechanic checks for consistent modular composition.

Abstract not found