G.-C. Roman, G. P. Picco, and A. L. Murphy. Software engineering for mobility: A roadmap. The Future of Software Engineerin,, pages 241--258, 2000.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....is a non solution, as it completely relies on application designers for the solution of most of the non functional requirements middleware should provide, starting from scalability. On the other hand, recently, some middleware specifically targeting the needs of mobile computing have been devised [59]; assumptions such as scarce resources, and fluctuating connectivity have been made in order to reach lightweight solutions. Some of the approaches however target only one of the mobility aspects: for instance, many location aware systems have been implemented to allow application to use location ....

G.-C. Roman, A. L. Murphy, and G. P. Picco. Software Engineering for Mobility: A Roadmap. In The Future of Software Engineering - 22 Int. Conf. on Software Engineering (ICSE2000), pages 243--258. ACM Press, May 2000.

....[17] On the other hand, the same separation of concerns allows for components to be replaced, upgraded, monitored or regulated without interfering with the logic that dictates how their behaviour needs to be coordinated. Recently, mobility has become an additional factor of complexity (see [20], 21] for surveys of this topic) In a mobile computing system, components may move across a network of locations, thus changing the environment in which computations need to be performed, which may require their adaptation or replacement. On the other hand, the properties of the network itself ....

G.-C.Roman, G.P.Picco, A.L.Murphy, "Software Engineering for Mobility: A Roadmap," in A. Finkelstein (ed), Future of Software Engineering, 22nd International Conference on Software Engineering, 241-258, June 2000

....systems could constitute a breaking point between traditional paradigms and the MAS approaches for complex systems software engineering. 2.2. Mobile computing Mobile computing studies computational systems, where software components can change execution environment during their life cycle [RPM00]. Similarly to MAS, mobile code components interact together to achieve some specific goals. Mobile code community has already identified the central role played by the coordination media to perform controlled and safe components interactions [CLZ97, CLZ98] Thus, several coordination media ....

G.-C. Roman, G. P. Picco, and A. L. Murphy. Software engineering for mobility: A roadmap. The Future of Software Engineerin,, pages 241--258, 2000.

..... Physical mobility. Mobile devices such as palmtop, cellular phones, etc. accessing the Internet and or interacting with each other in the context of mobile adhoc network (MANETs) will be more and more present in application scenarios, and they will have to be properly handled and modeled [PicMR00]. To limit complexity of application design and development, suitable models and infrastructures are needed to handle mobility in a natural and uniform way. 2 A promising approach to uniformly deal with all the above kinds of mobility is to model application components, as well as physical ....

G. P. Picco, A. M. Murphy, G. -C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

....draw some conclusions summarizing our experience and discussing future developments. 2 Background In this section we provide some background on mobility, Siena and Charmy. 2. 1 Mobility As some authors describe it, mobility is a total meltdown of the stability assumed by distributed systems [15]. In fact the network structure may be mutable, nodes may come and go, processes may move between nodes, and programs may evolve and change structure. From the software engineering perspective, mobility is de ned as the study of systems in which computational components may change location, in a ....

G.-C. Roman, G. P. Picco, and A. L. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, The Future of Software Engineering, pages 241-258. ACM Press, 2000. Invited contribution.

....to application design. Moreover, we have shown how a programmable coordination infrastructure can implement the abstractions of the framework and can lead to easy to program and easy to maintain mobile agent applications. We are currently developing a formal model of organizational contexts [3,17]. In addition, we are investigating a possible integration of our model within standard middleware technologies like CORBA and Jini [6] Acknowledgments: Work supported by the Italian MURST in the Framework of the Project MUSIQUE . ....

G. P. Picco, A. M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

....The mobile agent paradigm provides a number of advantages with respect to the traditional client server paradigm. The ability to relocate the components of an application supports service customization, optimized access to distributed resources, and deployment in a mobile networking environment [25]. On the other hand, the ability to move and execute code fragments has serious security implications [8, 5, 15] In particular, the recent worm attacks [4, 6] showed that malicious mobile software is tolerant to eradication and allows one to perform distributed denial of service attacks. The ....

Gruia-Catalin Roman, Gian Pietro Picco, and Amy L. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, The Future of Software Engineering, pages 241-258. ACM Press, 2000.

....and can rely on them for both acquiring contextual information and carry on complex coordination activities in an adaptive way. Several examples in different scenarios show the effectiveness of such an approach. 1. Introduction The emergence of distributed computing scenarios such as mobile [Bro98, PicMR00], peer to peer [RowD01, Rat01] and pervasive computing [Est02, Wei02] calls for novel approaches to support and facilitate the development and execution of distributed applications. In particular: i) In all the above scenarios, the activities of software components are often contextual, i.e. ....

G. P. Picco, A.M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

.... to another during their execution, changing the structure of the software system executing in that context [Whi97, CabLZ02] This requires not only the ability of components to learn about their new context , but also the ability to organize and control component interactions in the context [PicMR00]. Such concepts are exacerbated in mobile ad hoc networking, where interactions must be made fruitful and somehow controllable despite the lack of any intrinsic structure and the dynamics of connectivity [Bro98] Similar considerations apply to Internet based and open distributed computing. There, ....

.... computer based systems interacting with each other [GusF01] or distributed sensor nets [IntGE00] The integration in complex distributed applications and systems of (software running on) mobile devices of any type can be tackled only by modeling them in terms of autonomous software components [PicMR00]. Internet based distributed applications are typically made up of autonomous processes, possibly executing on different nodes, and cooperating with each other, a choice driven by conceptual simplicity and by decentralized management rather than by the actual need of autonomous concurrent ....

[Article contains additional citation context not shown here]

G. P. Picco, A.M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

.... each other in the context of complex distributed applications, e.g. to support our cooperative activities [Mts2002] to monitor and control our environments [Bor02] and to improve our interactions with the physical world [MamLZ02] Also, since most of the embeddings will be intrinsically mobile [PicMR00], as a car or a human, distributed software processes and components (from now on, we adopt the term agents to generically indicate the active components of a distributed application) will have to effectively interact with each other and effectively orchestrate their activities despite the ....

G. P. Picco, A.M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

....The focus of this project is to investigate how to provide process support for mobile work using different kinds of equipment (ranging from a small mobile phone, or PDA to laptop desktop PCs) An initial goal of the project is to find characteristics that can define and describe mobile work. In [5], mobility is divided into physical and logical mobility. This classification is at a very coarse level, and was not very useful for classifying mobile work. From a more practical point of view, mobile work can be classified into hardware mobility, software mobility and combined mobility [7] ....

G-C. Roman, G.P. Picco, and A.L. Murphy. Software Engineering for Mobility: A Roadmap. In The future of Software Engineering (ed. by A. Finkelstein), ACM Press, p.243-258, 2000.

....a great deal of interest from both industry and academia. In particular, the mobile agent paradigm has been used successfully to design applications ranging from distributed information retrieval [9] to network management [2] to wireless based services for dynamically reconfigured network links [15]. Although the mobile agent paradigm provides a number of advantages with respect to the traditional client server paradigm, some fundamental issues must be addressed for this new approach to be universally accepted. In particular, security and verification issues cause major concerns among ....

G.-C. Roman, G. P. Picco, and A. L. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, The Future of Software Engineering, pages 241-- 258. ACM Press, 2000.

.... the software processes running on them) connecting to the Internet from dynamically changing access points and interacting with its resources can be perceived, from the viewpoint of the fixed network infrastructure, in terms of autonomous and mobile software agents, and can be modeled as that [PicMR00, Sat01]. 2.2 From Global to Local Coordination The design and development of Internet applications based on mobile agents whatever the specific type of mobility discourage the generalized adoption of those coordination models such as peer topeer message passing, client server, distributed shared ....

.... [GluTM99, CabLZ01] of CORBA based interoperability [BelM01] as well as of agent interoperability [FIPA, Acities] In addition, a more general and formal notion of context dependent coordination, possibly defined by exploiting and extending already defined formal models for mobile systems [CarG00, PicMR00], is needed. Acknowledgements: Work supported by the NOKIA Research Center Boston and by the Italian MURST within the project MUSIQUE . ....

G. P. Picco, A.M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

....level the abstractions of the framework, can lead to the development of easy to program and easy to maintain mobile agent applications. In the future, we intend to develop a formal model of organizational contexts, possibly by exploiting already defined models for mobility and mobile agents [3, 8]. In addition, we intend to better investigate a possible integration of our model within standard middleware technologies like CORBA and Jini. Acknowledgements Work supported by Italian Ministry for University and Science and Technology Research (MURST) within the project MUSIQUE: ....

G. P. Picco, A. M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

.... move from one context to another during their execution [Whi97] Of course, more than in other application areas, this requires the capability of components to acquire knowledge dynamically about the context in which they execute, and the capability to control component interaction in a context [PicMR00]. 2.3 Local Control The flow of control concept has always been one of the key aspects of computer science and software engineering, at all levels, from the hardware level up to the high level design of applications. However, when software systems and components live and interact in an open ....

....applications, including applications for wearable systems, the very nature of wireless connections forces locality in interactions. Since wireless communication has limited range, a mobile computing component can directly interact at a given time only with a limited portion of the world [PicMR00]. Fig. 1. The Scenario of Modern Software Systems 2.5 A General Model Summarizing, software systems can be more and more assimilated to the general scheme of Figure 1. Software systems (dashed ellipses) are made up of autonomous components (black circles) interacting locally with each other ....

G. P. Picco, A.M. Murphy, G.-C. Roman, "Software Engineering for Mobility: A Roadmap", in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp. 241-258, 2000.

....artifacts. We are currently applying X ray to assess distributed system evolution from a runtime architecture perspective. We also plant to investigate how the approach can be extended so as to support extraction of distributed runtime abstractions involving both physical and logical mobility[10]. ....

G.-C. Roman, G. P. Picco, and A. Murphy, "Software engineering for mobility: A road map", In A. Finkelstein, editor, The Future of Software Engineering, ACM Press, June 2000, pp. 241-258.

....mobile devices and application designers aim to build applications that are portable and interoperable across device types. The resolution of distribution and the provision of high level interaction primitives, such as remote procedure calls or tuple spaces are also important in a mobile setting [19]. While middleware for fixed distributed systems is largely based on the notion of transparency [1] it is less appropriate in a dynamic and constrained setting, such as mobile computing [2] It is largely agreed that di#erent forms of middleware are needed for this scenario. In [4] we have ....

G.-C. Roman, A. L. Murphy, and G. P. Picco. Software Engineering for Mobility: A Roadmap. In The Future of Software Engineering - 22 nd Int. Conf. on Software Engineering (ICSE

....from time to time, due to changes in the business structure, or to adapt to the preferences of the user. In the former case, dynamicity must be dealt at an even finer time scale, since mobility defines a fluid system configuration where interactions among components may become only transient [16]. In these scenarios, assumptions about the existence of a single point of control, persistency, or authorization are often ine#cient, impractical, or simply not applicable. More and more, the developer loses global control over the components belonging to the system, since they are autonomously ....

G-C. Roman, G.P. Picco, and A.L. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, The Future of Software Engineering, pages 241--258. ACM Press, 2000.

....and ad hoc networks. The potentially very large number of independent computing units, a decoupled computing style, frequent disconnections, continuous position changes, and the location dependent nature of the behavior and communication patterns present designers with unprecedented challenges [21]. While formal methods may not be ready yet to deliver complete practical systems, the complexity of the undertaking clearly can benefit enormously from the rigor associated with a precise design process, even if employed only in the design of the most critical aspects of the system. Our first ....

G.-C. Roman, G. Picco, and A. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, Future of Software Engineering, pages 241--258. 22 Intl. Conf. on Soft. Eng., ACM Press, 2000.

....and ad hoc networks. The potentially very large number of independent computing units, a decoupled computing style, frequent disconnections, continuous position changes, and the location dependent nature of the behavior and communication patterns present designers with unprecedented challenges [21]. While formal methods may not be ready yet to deliver complete practical systems, the complexity of the 1 undertaking clearly can benefit enormously from the rigor associated with a precise design process, even if employed only in the design of the most critical aspects of the system. Our first ....

G.-C. Roman, G. Picco, and A. Murphy. Software Engineering for Mobility: A Roadmap. In A. Finkelstein, editor, Future of Software Engineering, pages 241--258. 22  Intl. Conf. on Soft. Eng., ACM Press, 2000.

No context found.

G.-C. Roman, G. P. Picco, and A. L. Murphy. Software engineering for mobility: A roadmap. The Future of Software Engineerin,, pages 241--258, 2000.

No context found.

G.-C. Roman, A. L. Murphy, and G. P. Picco. Software Engineering for Mobility: A Roadmap. In The Future of Software Engineering - 22 Int. Conf. on Software Engineering (ICSE2000.

No context found.

Gruia-Catalin Roman, Amy L. Murphy and Gian Pietro Picco. Software Engineering for Mobility: a roadmap. In this volume.

No context found.

G. P. Picco, A.M. Murphy, G.-C. Roman, Software Engineering for Mobility: A Roadmap, in The Future of Software Engineering, A. Finkelstein (Ed.), ACM Press, pp 241-258, 2000.

No context found.

A.L. Murphy G-C. Roman, G.P. Picco. Software Engineering for Mobility: A Roadmap. In The future of Software Engineering (ed. by A. Finkelstein), ACM Press, p.243-258, 2000.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC