Copyright © 2004 Published by Elsevier B.V.
Software performance models from system scenarios
Received 12 June 2003;
References and further reading may be available for this article. To view references and further reading you must purchase this article.
Abstract
The earliest definition of a software system may be in the form of Use Cases, which may be elaborated as scenarios. In this work, performance models are created from scenarios, to permit the earliest possible analysis of potential performance issues. Suitable forms of scenario models include Unified Modeling Language (UML) Activity or Sequence Diagrams (SD), and Use Case Maps (UCM) from the User Requirements Notation (URN) standard. They capture the causal flow of intended execution, and the operations, activities or responsibilities which may be allocated to components, with their expected resource demands. The Scenario to Performance (S2P) algorithm described here automatically transforms scenario models into performance models, and the LQNGenerator tool implements S2P to convert UCM scenario models into layered queueing performance models. S2P can, in principle, also be applied to other scenario models, including Message Sequence Charts, UML Activity Graphs (or Collaboration Diagrams, or Sequence Diagrams).
Keywords: Software performance; Scenarios; Software quality; Software evaluation; Use Case Maps; UML; Layered Queueing Networks
Article Outline
- 1. Introduction
- 2. Models for scenarios and performance
- 2.1. Use Case Maps
- 2.2. Layered Queueing Networks
- 2.2.1. Notation
- 3. Generating a layered performance model
- 3.1. Identifying blocking interactions
- 3.2. Correspondences between UCMs and LQNs
- 3.3. Correspondences of path structure in LQN
- 4. Algorithm for Scenario to Performance model transformation
- 4.1. Message Stack (MStack)
- 4.2. S2P Algorithm
- 5. Examples
- 5.1. Ticket Reservation System
- 5.2. POTS
- 5.2.1. POTS Path Traversal
- 5.2.2. POTS Performance Analysis Results
- 6. Obtaining Performance Models from UML Sequence Diagrams
- 7. Conclusions
- Acknowledgements
- References
- Vitae







E-mail Article
Add to my Quick Links

Cited By in Scopus (2)






