Abstract
THE SYN tools used throughout this monograph measure (for components) and predict (for systems) two behaviors: output (usually called ‘functional behavior’) and run time (an example of a contrasting ‘non-functional behavior’). As described in Chapter 14, the tools actually process as ‘run time’ an arbitrary secondary output from components and systems. The ‘non-functional’ behavior could be any property of interest, so long as there is a way to measure it at the component level and then to combine its component values into system values. For run time, measurement is straightforward using operating-system services and the series combination operator is addition, although concurrency introduces a bit of complication (Chapter 11). Throughout this chapter, run time continues to stand in for an arbitrary non-functional property. Reliability, which can be treated in much the same way as run time, is not at all straightforward and has its own Chapter 12.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
Hamlet, D. (2010). Functional vs. Non-functional Properties. In: Composing Software Components. Springer, Boston, MA. https://doi.org/10.1007/978-1-4419-7148-7_20
Download citation
DOI: https://doi.org/10.1007/978-1-4419-7148-7_20
Published:
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4419-7147-0
Online ISBN: 978-1-4419-7148-7
eBook Packages: Computer ScienceComputer Science (R0)