1986
DOI: 10.1145/6306.6307
|View full text |Cite
|
Sign up to set email alerts
|

Independent general principles for constructing responsive software systems

Abstract: Three general principles are presented that can be applied in early software life cycle stages for the definition of software requirements and designs with acceptable performance. They are genuine highlevel considerations for meeting responsiveness goals without sacrificing understandability and maintainability, and without increasing development time and cost. The principles are derived from the interrelationships of two performance models: a queueing network based on computer system model and an execution gr… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

1998
1998
2002
2002

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 16 publications
(6 citation statements)
references
References 14 publications
0
6
0
Order By: Relevance
“…We summarise some of the Systems Performance Engineering (SPE) principles [49,50] for building performance into large software systems and helping provide good responsiveness to users (the response time as seem by an end-user of the system). They include:…”
Section: Spe Principlesmentioning
confidence: 99%
See 1 more Smart Citation
“…We summarise some of the Systems Performance Engineering (SPE) principles [49,50] for building performance into large software systems and helping provide good responsiveness to users (the response time as seem by an end-user of the system). They include:…”
Section: Spe Principlesmentioning
confidence: 99%
“…Drawing on experience in implementing conceptual designs expressed in semantic data models, it catalogues knowledge of performance concepts and development techniques, which are further organised in a layered structure. It draws on Software Performance Engineering (SPE) principles for designing performance, including user-responsiveness, into systems [49,501. Catalogues are organised along several axes.…”
Section: Introductionmentioning
confidence: 99%
“…We are now looking at a hybrid approach that will allow us to smoothly and automatically shift from simulation and analytical models, and vice versa, over the course of the software lifecycle. Smith's [1986Smith's [ , 1990 work on software performance engineering is related to our modeling and analysis methods. Her work so far, however, has focused on sequential software systems.…”
Section: Related Workmentioning
confidence: 99%
“…Smith [SMIT90a] defines the following seven principles. A quantitative analysis of the performance results of three of them are in Smith [SMIT86b]. Both Smith [SMIT88a] and Smith [SMIT90a] give extensive explanations and examples for each principle.…”
Section: Early Lifecycle Performance Principlesmentioning
confidence: 99%