Abstract
This book describes current understanding and use of the relationship between software requirements and software architectures.
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 subscriptionsNotes
- 1.
We note that context and requirements may change independently; as they define the problem that should be solved, we refer to problem volatility as indicative of these changes.
- 2.
The precise details of this relationship between complexity and lines of code have been subject to many debates over the years; we do not replay them here.
- 3.
See [3] for an intriguing reconstruction of that first program, together with a transcript of the notes accompanying its design.
- 4.
Their rise has also been coincident with a waning in the popularity of high-level programming languages; always wary of cum hoc ergo propter hoc.
- 5.
J. Lyons and Co. A UK food manufacturer in the mid 20th century.
- 6.
Modally, the projects were in the €10–20 million range.
References
Ferreira S, Collofello J, Shunk D, Mackulak G (2009) Understanding the effects of requirements volatility in software engineering by using analytical modeling and software process simulation. J Syst Softw 82(10):1568–1577, SI: YAU
Schaller R (1997) Moore’s law: past, present and future. IEEE Spectrum 34(6):52–59
Tootill G (1998) The original original program. Resurrection: the computer conservation society, no. 20. ISSN 0958–7403
Enticknap N (1998) Computing’s golden jubilee. Resurrection: the computer conservation society, no. 20. ISSN 0958–7403
Perry DE, Wolf AL (1992) Foundations for the study of software architecture. ACM SIGSOFT Software Eng Notes 17(4):40–52
Shaw M, Garlan D (1996) Software architecture: perspectives on an emerging discipline. Prentice Hall, Englewood Cliffs
Bass L, Clements P, Kazman R (2003) Software architecture in practice, 2nd edn. Addison-Wesley Longman, Boston
Royce W (1970) Managing the development of large software systems. Proc IEEE WESCON 26:1–9
Cheng B, Atlee J (2007) Research directions in requirements engineering. In: Proceedings of FoSE 2007: future of software engineering. Washington, DC, pp 285–303
Bird P (1994) LEO: the first business computer. Hasler, Workingham
Grant RM (2003) Cases in contemporary strategy analysis. Blackwell, USA/UK/Australia/Germany. ISBN 1405111801
Turski WM (1986) And no philosophers’ stone, either. Information processing 86:1077–1080
McManus J, Wood-Harper T (2008) A study in project failure. Tech rep, Chartered Institute of IT. Last accessed 27 March 2011
Acknowledgments
The first author wishes to thank Lucia Rapanotti for her careful reading and detailed critique of this chapter.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Hall, J.G., Grundy, J., Mistrik, I., Lago, P., Avgeriou, P. (2011). Introduction: Relating Requirements and Architectures. In: Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrík, I. (eds) Relating Software Requirements and Architectures. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21001-3_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-21001-3_1
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-21000-6
Online ISBN: 978-3-642-21001-3
eBook Packages: Computer ScienceComputer Science (R0)