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.
- Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.
| Title || Analysing Software Requirements Specifications for Performance |
| Authors || Dorin Petriu and Murray Woodside |
| Type || Conference |
| Conference/Journal Title || WOSP 2002: Third International Workshop on Software and Performance |
| Volume/Number || |
| Editors || |
| Publisher || ACM |
| Month || July |
| Year || 2002 |
| Pages || |
| DOI || http://doi.acm.org/10.1145/584369.584371 |
| Keywords || specifications, performance, Use Case Maps, completion, non-functional requirements |