Unfriendly COTS integration - instrumentation and interfaces for improved plugability
ABSTRACT It is becoming increasingly desirable to incorporate commercial-off-the-shelf (COTS) tools as software components into larger software systems. Due to their large user base, COTS tools tend to be cheap, reasonably reliable, and functionally powerful. Reusing them as components has the benefit of significantly reducing development cost and effort. Despite these advantages, developers encounter major obstacles in integrating most COTS tools because these tools have been constructed as stand-alone applications and make assumptions about their environment that do not hold when used as part of larger software systems. Most significantly, while they frequently contain programmatic interfaces that allow other components to obtain services from them on a direct call basis, they almost always lack the notification and data synchronicity facilities required for active integration. The authors present an integration framework for adding these notification and data synchronization facilities to COTS tools so that they can be integrated as active software components into larger systems. We illustrate our integration framework through tool suites we constructed around Mathworks' Matlab/Stateflow and Rational's Rose (two widely-used, large COTS tools). Our experience to date is that it is indeed possible to transform standalone COTS tools into software components.
Conference Proceeding: A Software Architecture for Cross-Layer Wireless Network Adaptations[show abstract] [hide abstract]
ABSTRACT: Conventional data networks are based on layered architectures. The introduction of wireless networks has created a need to violate this layering discipline to create cross- layer designs or adaptations. Ad-hoc implementations of such cross-layer adaptations reduce the level of modularity and abstraction in the network's implementation, giving rise to a significant increase in complexity. We present a taxonomy of possible cross-layer adaptations that is then used to derive an architecture for their implementation that significantly preserves the networks structure. We present implementation results that validate this architecture in the context of a real wireless network implementation.Software Architecture, 2008. WICSA 2008. Seventh Working IEEE/IFIP Conference on; 03/2008
Conference Proceeding: Architecture differencing for self management.Proceedings of the 1st ACM SIGSOFT Workshop on Self-Managed Systems, WOSS 2004, Newport Beach, California, USA, October 31 - November 1, 2004; 01/2004
Article: Chapter 5 - The Tools Perspective on Software Reverse Engineering: Requirements, Construction, and Evaluation[show abstract] [hide abstract]
ABSTRACT: Software reverse engineering is a subdiscipline of software engineering, striving to provide support for the comprehension of software systems by creating suitable representations of the system in another form or higher level of abstraction. In order to be effective, reverse engineering needs tool support, which provides functionality to extract low-level facts from the systems, to analyze and generate knowledge about the systems, and to visualize that knowledge so that reverse engineers are able to comprehend the aspects of the system that they are interested in effectively.This chapter explores the issue of building tools for reverse engineering. Since tools are an important part of conducting research in reverse engineering, it is worthwhile to reflect upon the state of tool building with the goal to advance upon it—and thus to advance reverse engineering research as a whole. We tackle this goal by looking at the issue of tools through a set of lenses. The purpose of each lens is to focus on a critical topic for tool building by surveying the current state-of-the-art and identifying challenges that need to be addressed.In this chapter we discuss three lenses, namely (1) requirements for reverse engineering tools, (2) construction of reverse engineering tools, and (3) evaluation of reverse engineering tools. The first lens identifies a number of generic quality attributes that reverse engineering tools should strive to meet. The second lens approaches tools from the observation that since tool building is a key activity in research, it should be conducted in an effective and rather predictable manner. The third lens looks at the role that tools play in supporting the evaluation of reverse engineering research. While each lens looks at the topic from a different perspective, taken together they provide a holistic picture of tool building in the reverse engineering domain.Advances in Computers.