How Software Architecture can Frame, Constrain and Inspire System Requirements

作者: Eoin Woods , Nick Rozanski

DOI: 10.1007/978-3-642-21001-3_19

关键词:

摘要: Historically a system’s requirements and its architectural design have been viewed as having simple relationship where the drove architecture was designed in order to meet requirements. In contrast, our experience is that much more dynamic can be achieved between these key activities within system lifecycle, allows constrain an achievable set of possibilities, frame making their implications clearer, inspire new from capabilities architecture. this article, we describe relationship, illustrate it with case study drawn present some lessons learned believe will valuable for other software architects.

参考文章(16)
James Robertson, Suzanne Robertson, Mastering the Requirements Process (2nd Edition) Addison-Wesley Professional. ,(2006)
James Robertson, Suzanne Robertson, Mastering the requirements process ACM Press/Addison-Wesley Publishing Co.. ,(1999)
Axel van Lamsweerde, Emmanuel Letier, From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering International Workshop on Radical Innovations of Software and Systems Engineering in the Future. pp. 325- 340 ,(2004) , 10.1007/978-3-540-24626-8_23
Rick Kazman, Len Bass, Paul Clements, Software Architecture in Practice ,(1997)
C. Shekaran, D. Garlan, M. Jackson, N.R. Mead, C. Potts, H.B. Reubenstein, The role of software architecture in requirements engineering international conference on requirements engineering. pp. 239- 245 ,(1994) , 10.1109/ICRE.1994.292379
Paul Clements, David Garlan, Reed Little, Robert Nord, Judith Stafford, None, Documenting Software Architectures: Views and Beyond ,(2002)