UML中如何描述系统的体系结构(一).doc

ArchitectureVisualizing, specifying, constructing, and documenting a software-intensive system demands that the system be viewed from a number of perspectives. Different stakeholders - end users, analysts, developers, system integrators, testers, technical writers, and project managers - each bring different agendas to a project, and each looks at that system in different ways at different times over the projects life. A systems architecture is perhaps the most important artifact that can be used to manage these different viewpoints and thus control the iterative and incremental development of a system throughout its life cycle.Architecture is the set of significant decisions aboutn The organization of a software systemn The selection of the structural elements and their interfaces by which the system is composedn Their behavior, as specified in the collaborations among those elementsn The composition of these structural and behavioral elements into progressively larger subsystems.n The architectural style that guides this organization: the static and dynamic elements and their interfaces their collaborations, and their compositionSoftware architecture is not only concerned with structure and behavior but also with usage, functionality, performance, resilience, reuse, comprehensibility, economic and technology constraints and trade-offs, and aesthetic concerns.As Figure 2-23 illustrates, the architecture of a software-intensive system can best be described by five interlocking views. Each view is a projection into the organization and structure of the system, focused on a particular aspect of that system.体系结构具有可视性，描述性，结构性和文档性的软件集约型系统要求可以从多个角度观察该系统不同的权益关系人终端用户，分析人员，开发人员，系统集成人员，测试人员，文档工程师和项目经理每类人员都会将不同的议程带到项目组中，而且每类人员在项目的生命周期里，在不同的时间，用不同的方式看该系统系统的体系结构也许是最重要的产品，它通常能管理这些不同的视点，因此能在系统的整个生命周期里控制它的迭代和增量开发体系结构是一组关于如下方面的重要决策n 软件系统的组织n 结构元素和组成系统接口的选择n 在元素之间的交互行为n 结构的组成和行为元素加入到逐步扩大的子系统中n 指导本组织的体系结构风格：静态和动态元素和它们交互的接口，还有它们的组成软件结构不仅关系着结构和行为，还关