Message Sequence Chart MSC speci cations have found their way into many software engineering methodologies and CASE tools, in particular to represent early life-cycle requirements and high-level design speci cations. In this paper we analyze iterating and branching MSC speci cations with respect to their software architectural content. We present algorithms for the automated synthesis of Real-Time Object-Oriented M o deling ROOM models from MSC speci cations and discuss their implementation in the Mesa toolset. 1 Introduction Message Sequence Charts MSCs have been adopted within several software engineering methodologies and tools. MSCs are suitable to express early life-cycle requirements and high-level object designs. In 2 we argue that due to their focused expressiveness MSCs are not a full life-cycle notation. Instead, MSCs should be a front-end to full life-cycle methods and tools. The development o f the Mesa toolset 2 is based on this idea. Initially, designers will describe sets of scenarios, and compose them to form an iterating and branching model of the system behavior. This model will be analyzed for syntactic sanity a s w ell as semantic consistency using an approach outlined in 2 . The crucial step is then to translate the high-level MSC model into an architectural model supporting the design of the implementation.Motivation for our work stems from the fact that the manual translation from an MSC speci cation into a full life-cycle modeling language like Real-Time Object-Oriented Modeling ROOM 5 will be an error-prone and time-consuming task. To increase reliability and e ciency of this transformation we will present algorithms that will automate this translation. The two main groups that could bene t from the suggested approach are are those who intend to design their system using the synthesized ROOM models as well as those who are mainly interested in executable architectural models.2 Related Work ITU-T Recommendation Z.120 3 speci es two major syntactical objects as components of the MSC notation: basic MSCs bMSCs and High-Level MSCs HMSCs. A bMSC essentially consists of a set of processes called instances in Z.120 that run in parallel and exchange messages in a one-to-one, asynchronous fashion. The graph of an HMSC provides for operators to connect bMSCs to describe their parallel, sequential, iterating, and non-deterministic execution. We will call the collection of an HMSC graph and the referenced bMSCs an MSC speci cation. For an example see Figure 1.Real-Time Object Oriented Modeling ROOM 5 is a graphical notation which relies on two main building blocks: 1 the description of a system's structure as expressed through nested actor structures and 2 the dynamic behavior of the structural components de ned by hierarchical communicating extended nite state machines called ROOMcharts, a v ariant of Statecharts. 1 h a ve recently argued for the use of ROOM as an Architecture Description Language ADL. The ObjecTime Developer 1 toolset is an industrial-strength CASE tool implementing the ROOM method...

Abstract. The software architecture of distributed systems is about to change due to new requirements of modern mobile devices. New network techniques, like ad-hoc radio communication or peer-to-peer networks allow mobile devices to sense their environment and to interact with other devices dynamically. This paper presents a cutting-edge way to describe objects and their interaction, also called context, as well as the possibility to configure such interaction scenarios. A lookup mechanism collects information about the environment and a rolebased classification is responsible for identifying possible interaction partners. Furthermore the configuration of scenario behavior with context rules is introduced. Finally a comparison with already existing context frameworks is given and a practical emergency scenario configuration is shown.

No abstract

Applications for mobile devices, especially mobile phones, are rarely used today -apart from games. They neither take the special features of each device into account nor the individuality of the user who has commonly a much closer emotional relationship to his mobile phone than to many other technical devices. Really useful and successful mobile applications can thus be presumably only those that address these deficits. In this paper we present a novel approach for solving these problems by personalizing Java based mobile applications. The concept centres on a powerful and flexible XML information model that can easily be utilized for adding personalized data and features to an application. The information is weaved into the code by a pre-processor prior to compilation. We also present an example of its usage and discuss some of the consequences.