An Evolution Process For Service-Oriented Systems

Evolution of service-oriented systems is quite a new research area, which becomesmore and more important as engineering challenges move from enablingservice-orientation onto the maintenance and evolution of already developedservice-oriented systems. However, the development of suitable evolution processesand methodologies is still an open research problem. The evolution processpresented in this paper has been designed to address the evolution of serviceorientedsystems, which are technically built out of a set of service compositions.The presented process comprises phases and tasks compliant with ISO 20000.The underlying model of service-oriented system consisting of business processesand corresponding service composition models has also been presented. A traceabilitymodel and tools supporting change impact analysis have also beenprovisioned for. Preliminary industrial validation indicates that the evolutionprocess should be easy to adapt by the industry

Modelling architectural decisions under changing requirements

Abstract-One of the approaches for documenting software architecture is to treat it as a set of architectural design decisions. Such decisions are always made in the context of requirements that must be fulfilled and in the context of decisions that were made before. Currently, models for representing architectural decisions are mainly concentrated on showing the decision making process of the initial architectural design. However, decisions that have been made in such a process may need to be changed during further evolution and maintenance of the software architecture, typically in response to the new or changed requirements. A graphical modelling notation for documenting architectural decisions (Maps of Architectural Decisions) has been developed by our team. In this paper, it is presented how this notation could be used to model architectural decisions under changing requirements. It is proposed how one decision change could be effectively propagated through the rest of the architectural decision model and how a rigorous and toolsupported process of updating such models could be organized

Variable structure robot control systems: The RAPP approach

International audienceThis paper presents a method of designing variable structure control systems for robots. As the on-board robot computational resources are limited, but in some cases the demands imposed on the robot by the user are virtually limitless, the solution is to produce a variable structure system. The task dependent part has to be exchanged, however the task governs the activities of the robot. Thus not only exchange of some task-dependent modules is required, but also supervisory responsibilities have to be switched. Such control systems are necessary in the case of robot companions, where the owner of the robot may demand from it to provide many services.

Towards Precise Architectural Decision Models

Abstract. One of the modern approaches for documenting software architecture is to show the architectural design decisions that led an architect to the final form of software architecture. However, decisions that have been made in such a process may need to be changed during further evolution and maintenance of the software architecture. The main reasons for these changes are new or changed requirements. In our team we have developed a graphical modelling notation for documenting architectural decisions, called Maps of Architectural Decisions, that can support the process of making changes in the software architecture. In this work we define a formal background for the controlled process of making changes in architectural decision models that are documented using that notation