FEBRUARY 2007 (Vol. 40, No. 2) p. 4
0018-9162/07/$31.00 © 2007 IEEE
Published by the IEEE Computer Society
Published by the IEEE Computer Society
PDFs Require Adobe Acrobat
Challenges in Securing Networked J2ME Applications
André N. Klingsheim, Vebjørn Moen, and Kjell J. Hole
The fast-growing smart phone market is spurring development of new mobile software for everything from gaming to GPS navigation.
The most widespread development platform, the Java 2, Micro Edition, is available on nearly 80 percent of currently available smart phones. Experience gained during a commercial development project demonstrates how J2ME technologies, particularly security-related functionality, are implemented on real devices and provides insights into the problems researchers encounter during the development process.
Managing E-Mail Overload: Solutions and Future Challenges
David Schuff, Ozgur Turetken, John D'Arcy, and David Croson
E-mail management tools that economize on scarce cognitive resources at the expense of relatively cheap additional CPU power, disk capacity, or network bandwidth will ultimately prevail over those that pursue the opposite strategy. With proper application of automatic filtering, clustering, and new user interface metaphors, e-mail can once again become an effective knowledge-management tool rather than being a source of information overload.
Cryptography on a Speck of Dust
Jens-Peter Kaps, Gunnar Gaubatz, and Berk Sunar
Current wireless sensor nodes use simple, battery-powered general-purpose processors and provide secure communication using software-implemented cryptographic protocols. Next-generation sensor nodes will likely operate without batteries, harvesting energy instead from ambient sources.
To provide cryptographic functions for ubiquitous computing devices, designers must make power consumption their first priority. The challenge of future research is to find an algorithm that has at its core a simple, scalable primitive that could serve as a common element for secret and public-key functions.
Trust Management in Distributed Systems
Huaizhi Li and Mukesh Singhal
With the rapid development of network and communication technologies, new forms of distributed systems—such as peer-to-peer networks and mobile ad hoc networks—are emerging.
Trust is an important issue in these distributed systems. A flexible and general-purpose trust-management system can maintain current and consistent trustworthiness information for the different entities in a distributed system. Thus, trust management remains an active research area. Many interesting research issues are yet to be fully explored, including trust/reputation value storage.
Marking Technique to Isolate Boundary Router and Attacker
Vaarun Vijairaghavan, Darshak Shah, Pallavi Galgali, Amit Shah, Nikhil Shah, Venkatesh Srinivasan, and Lokesh Bhatia
Most research on denial-of-service attacks has focused on mitigating an attack's effects, which provides an effective stopgap measure but doesn't eliminate the problem or discourage attackers.
Internet Protocol traceback—which refers to any method for reliably determining a packet's origin on the Internet—is a significant step toward identifying—and thus stopping—attackers, but a method that operates independently of the attack would not require the attack to continue until the attacker can be traced back.
Adaptive QoS for Mobile Web Services through Cross-Layer Communication
Min Tian, Andreas Gramm, Hartmut Ritter, Jochen H. Schiller, and Thiemo Voigt
While clients seek reliable service performance whenever the need arises, service providers strive to achieve an optimal balance between user satisfaction and system utilization.
Given the ubiquity of mobile devices such as smart phones and PDAs, clients using these devices will likely generate a large share of all Web service requests in the future. However, mobile devices are resource-constrained in terms of CPU, memory, and battery lifetime. Compressing Web service interactions is therefore desirable.
How Accurately Do Engineers Predict Software Maintenance Tasks?
Numerous studies indicate that the distribution of time spent among adaptive, corrective, and perfective software maintenance varies widely. This variation is partly due to the fact that many activities are difficult to classify; for example, some organizations separate software reengineering from perfective maintenance. Even when these categories are reasonably well-defined, adaptive and perfective work are often used to hide corrective work.
The author presents a case study that confirms earlier research showing considerable overlap among perfective, corrective, and adaptive maintenance tasks in software development projects while also shedding light on how well programmers estimate both the type of maintenance necessary and the duration.