Abstract
Requirements are fundamental to any engineered system. They capture the key stakeholder functional needs, constraints on the operation of the system, and often form a basis for contracting, testing and acceptance [1, 2]. Architecture captures the structuring of software solutions, incorporating not just functional properties of a system but design rationale, multi-layer abstractions and architectural knowledge [3, 4]. One can not exist without the other. Requirements need to be realized in a software system, described in essence by appropriate software architectures. Architecture must deliver on specified functional and non-functional requirements in order for the software system to be at all useful.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: Proceedings of the conference on the future of software engineering (ICSE). ACM, New York, pp 35–46
Berenbach B, Paulish DJ, Kazmeier J, Daniel P, Rudorfer A (2009) Software systems requirements engineering: in practice. McGraw-Hill Osborne Media, New York
Garlan D, Perry DE (1995) Introduction to the special issue on software architecture. IEEE T Software Eng 21(4):269–274
Kruchten P, Lago P, van Vliet H (2006) Building up and reasoning about architectural knowledge. In: Hofmeister C (ed) QoSA-quality of software architecture. Springer, Vasteras, pp 43–58
Harker SDP, Eason KD, Dobson JE (1993) The change and evolution of requirements as a challenge to the practice of software engineering. In: Proceedings of the IEEE international symposium on requirements engineering. San Diego, pp 266–272
Stark GE, Oman P, Skillicorn A, Ameele A (1999) An examination of the effects of requirements changes on software maintenance releases. J Softw Maint-Res Pr 11(5):293–309
Gotel OCZ, Finkelstein ACW (1994) An analysis of the requirements traceability problem. In: IEEE international symposium on requirements engineering (RE). Colorado Springs, pp 94–101
Lago P, Muccini H, van Vliet H (2009) A scoped approach to traceability management. J Syst Softw 82(1):168–182
Hayes JH, Dekhtyar A, Sundaram SK (2006) Advancing candidate link generation for requirements tracing: the study of methods. IEEE Trans Software Eng 32(1):4–19
Mendonça N, Kramer J (2001) An approach for recovering distributed system architectures. Autom Softw Eng 8(3–4):311–354
Jakobac V, Medvidovic N, Egyed A (2005) Separating architectural concerns to ease program understanding. SIGSOFT Softw Eng Notes 30(4):1–5
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Grundy, J., Lago, P., Avgeriou, P., Hall, J., Mistrík, I. (2011). Theoretical Underpinnings and Reviews. 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_2
Download citation
DOI: https://doi.org/10.1007/978-3-642-21001-3_2
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)