作者: 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.