Abstract
As performance is a vital quality factor for systems, an important challenge during system development is to deal with performance requirements. For a credit card system, for example, a developer might consider performance requirements to “achieve good response time for sales authorization” and “achieve good space usage for storing customer information.” Being global in their nature and impact, performance requirements are an important class of non-functional requirements (NFRs). To be effective, systems should attain NFRs as well as functional requirements (e.g., requiring a credit card system to authorize sales). However, it is generally difficult to deal with performance requirements and other NFRs, as they can conflict and interact with each other and with the many implementation alternatives which have varying features and tradeoffs.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2000 Springer Science+Business Media New York
About this chapter
Cite this chapter
Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J. (2000). Performance Requirements. In: Non-Functional Requirements in Software Engineering. International Series in Software Engineering, vol 5. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-5269-7_8
Download citation
DOI: https://doi.org/10.1007/978-1-4615-5269-7_8
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4613-7403-9
Online ISBN: 978-1-4615-5269-7
eBook Packages: Springer Book Archive