Abstract

Performance Aware Software Development (PASD) as described here combines a software specification, a model, and resource demand budgets. The budgets are planning figures created by the designers and managers, from the requirements and their experience. The key elements of this approach are the planning of budgets for the resource demands of each of the parts and operations of the system, and a validation check (using the model) for the required performance. The paper starts from a Use Case Map (UCM) specification, but other specification languages such as UML could equally be used. Demand budgets are allocated to responsibilities and the entire budget is verified by a semi-automated performance analysis using Layered Queuing Network (LQN) models. The key step is to add "completions" to the software system design, representing those parts of the system not defined in the software specification (infrastructure such as middleware, the environment, and competing applications), which could impact the performance. Budget adjustments are indicated by bottleneck locations and the sensitivity of results.

Discussion

• Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.