Graceful Object-Based Performance Evolution

Abstract

Object‐based design and development are thought to facilitate graceful evolution of functionality, and thus enhance the reusability of software components. They can also facilitate graceful performance evolution. The performance of a layered object‐based component can be made tunable to meet changing needs by permitting clients to ‘plug in’ appropriate implementations for its constituent components through generic parameters. If the components and their constituents are carefully designed, then performance tuning is possible without direct modification to the internal details of the participating components, thus significantly lowering the cost for performance evolution. The contribution of this paper is to software practice. It explains how software engineers can build performance‐tunable components using C++ templates. It includes empirical results confirming that tuning produces expected performance improvements with minimal code change. The results are especially significant because they are scalable to arbitrarily large and heavily layered software components and subsystems. © 1997 by John Wiley & Sons, Ltd.

Composition validation and subjectivity in GenVoca generators

“…1 are possible, the latter two showing that a component can be composed with itself. In general, the order in which components are composed can significantly affect the performance of the resulting system [4], [53].…”

Performance specification of software components

“…Designers of languages and developers of component libraries have considered alternative implementations providing performance trade-offs [2,12,13]. More sophisticated approaches that permit development of systems to allow parameterization and choice of implementation have been proposed [1,21]. However, in addressing the basic question of how to specify reusable component performance, almost all previous results defer to classical big-O analysis [3,10].…”

“…The parameterized nature of the notations also makes them suitable for specification of non-trivial, performanceparameterized components [1,21], though the resulting 6 To be exact, the displacement expressions for Stack initialization and finalization operations should account for any transitional displacement required Entry initialization and finalization procedures. So should procedure Pop, where a local variable is declared.…”

“…Clients will engineer new systems by choosing and assembling components that best fit their performance (time and space) requirements [1,17,21,22]. To facilitate meaningful selection from among competing alternatives, software components should include descriptions of performance behavior in addition to functional behavior.…”

Estimating Non-functional Properties of Component-based Software Based on Resource Consumption

“…In an earlier paper, Sreerama et al show how to implement componentbased software engineering in an object-oriented context, using C++ templates as building blocks for performance tuning [21]. In this approach, layered components can be "plugged" together without source-code modification, using different implementations for the same functionality that exhibit different performance behaviors.…”