Abstract

To evaluate a software specification for its performance potential, it is necessary to supply additional information, not required for functional specification. Examples range from the execution cost of operations and details of deployment, up to missing subsystems and layers. The term “completions” is used here to include all such additions, including annotations, component insertions, environment infrastructure, deployment, communication patterns, design refinements and scenario or design transformations which correspond to a given deployment style. Completions are related to the purpose of evaluation, so they are tailored to describing the performance at a suitable level of detail. Completions for evaluating other attributes such as reliability or security are also possible. The paper describes how completions are added to a specification regardless of the language used (provided that it describes the system behaviour as well as its structure), and experience with completions in Use Case Maps.

Discussion

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

FormForVirtualLibrary edit

Title Performance-related Completions for Software Specifications
Authors Murray Woodside, Dorin Petriu, Khalid Siddiqui
Type Conference
Conference/Journal Title 24th International Conference on Software Engineering
Volume/Number
Editors
Publisher ACM
Month May
Year 2002
Pages 22-32
DOI http://doi.acm.org/10.1145/581339.581346
Keywords Performance prediction, software specification, generative design.
Topic attachments
I Attachment Action Size Date Who Comment
icse02.pdfpdf icse02.pdf manage 95 K 04 Nov 2005 - 18:09 JacquesSincennes  
Topic revision: r3 - 07 Nov 2009, HannaFarah
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback