Although object-oriented methods have been shown to help construct software systems that are easy to understand and modify, have a high potential for reuse, and are relatively quick and easy to implement, concern over performance of object-oriented systems represents a significant barrier to its adoption. Our experience has shown that it is possible to design objectoriented systems that have adequate performance and exhibit the other qualities, such as reusability, maintainability, and modifiability, that have made OOD so successful. However, doing this requires careful attention to performance goals throughout the life cycle. This paper describes the use of SPE.ED, a performance modeling tool that supports the SPE process, for early life cycle performance evaluation of object-oriented systems. The use of SPE.ED for performance engineering of object-oriented software is illustrated with a simple example. 1.0 Introduction Object-oriented development (OOD) methods have been shown to be...

Abstract not found

Many object-oriented systems fail to meet performance objectives when they are initially constructed. These performance failures result in damaged customer relations, lost productivity for users, lost revenue, cost overruns due to tuning or redesign, and missed market windows. Most performance failures are due to a lack of consideration of performance issues early in the development process. However, early consideration of performance in object-oriented systems is straightforward. The Use Case scenarios produced by developers during analysis and design serve as a starting point for performance analysis. This paper describes a systematic approach to the performance engineering of object-oriented systems based on Use Case scenarios. This approach is cost-effective and has a low impact on the software development process. A simple case study illustrates the process.

This paper describes a mechanism to enable users of performance modeling tools to transfer models among a set of tools. This paper describes the evolution and definition of a basic PMIF. It describes how tool developers can implement the PMIF and how the export and import would work for users. A simple example illustrates the format. The paper describes how to extend the PMIF to add new features to the basic format. It ends with the current status of the PMIF, what we have learned, some suggestions for sets of extensions, and current work in progress. 1.0 Introduction A performance model interchange format (PMIF) is a common representation for system performance model data that can be used to move models among modeling tools. A user of several tools that support the format can create a model in one tool, and later move the model to other tools for further work. For example, an analyst might create a model of a server platform conduct several studies, then move the model to a tool bet...

This paper presents a languagebased framework for Software Performance Engineering in C/S environments. The language allows for the specification of objects such as clients, servers, DB tables, networks, and transactions. A specification of a C/S system in this language compiles into an analytic model used to predict the performance of the new system