ACM Home Page
Please provide us with feedback. Feedback
Analysing software requirements specifications for performance
Full text PdfPdf (213 KB)
Source Workshop on Software and Performance archive
Proceedings of the 3rd international workshop on Software and performance table of contents
Rome, Italy
SESSION: Performance analysis in the software lifecycle table of contents
Pages: 1 - 9  
Year of Publication: 2002
ISBN:1-58113-563-7
Authors
Dorin Petriu  Carleton University, Ottawa, Canada
Murray Woodside  Carleton University, Ottawa, Canada
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
SIGMETRICS: ACM Special Interest Group on Measurement and Evaluation
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 23,   Downloads (12 Months): 118,   Citation Count: 7
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/584369.584371
What is a DOI?

ABSTRACT

The earliest moment when performance issues can be addressed is the initial specification of a software system, during the formulation of the architecture, and well before the design stage. A common form of specification at this stage is a set of scenarios to be executed by the system, which embody the Use Cases, and identify the sequence of responsibilities to be carried out in different kinds of responses. On the basis that earlier analysis is better, a performance modeling capability has been installed in a scenario modeling tool for Use Case Maps that is part of a proposed standard for User Requirements Notation. Using examples, the paper shows how this kind of early analysis can address high-level performance questions, at a comparable level of abstraction to the specification. The imprecision of early knowledge, and the risk of ignoring some performance limitations, are key factors whose impact is addressed.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
 
4
R. J. A. Buhr and R. S. Casselman, High-Level Design of Object-Oriented and Real-Time Systems: A Unified Approach with Use Case Maps. Englewood Cliffs, New Jersey: Prentice Hall, 1995.
 
5
 
6
L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-Functional Requirements in Software Engineering. Boston: Kluwer, 2000.
 
7
G. Franks, S. Majumdar, J. Neilson, D. Petriu, J. Rolia, and M. Woodside, "Performance Analysis of Distributed Server Systems," in The Sixth International Conference on Software Quality (6ICSQ), Ottawa, Ontario, 1996, pp. 15-26.
 
8
G. Franks and M. Woodside, "Effectiveness of early replies in client-server systems," Proceedings of Performance 99, Performance Evaluation, vol. 36-37, pp. 165-183, August 1999.
 
9
 
10
 
11
 
12
D. Petriu and M. Woodside, "Incorporating Performance Analysis in the Early Stages of Software Development Using Generative Programming Principles," in Third Workshop on Generative Programming (ECOOP 2001 Workshop), Budapest, June 2001.
 
13
 
14
 
15
 
16
K. H. Siddiqui and C. M. Woodside, "Performance Aware Software Development (PASD) Using Resource Demand Budgets", submitted for publication, 2002.
 
17
 
18
 
19
C. U. Smith, L.G. Williams, "Performance Solutions", Addison-Wesley, 2001.
 
20
M. Woodside, "Layered Performance Modeling and Layered Queueing: Quick Tutorial," internal report, Carleton University, Ottawa, April 2001.
 
21
C. M. Woodside, "Software Resource Architecture", Int. Journal on Software Engineering and Knowledge Engineering (IJSEKE), vol. 11, no. 4 pp. 407-429, 2001.
22
 
23


Collaborative Colleagues:
Dorin Petriu: colleagues
Murray Woodside: colleagues

Peer to Peer - Readers of this Article have also read: