UML中如何描述系统的体系结构(三)



Theimplementation viewof a system encompasses the artifacts that are used to assemble and release the physical system. This view primarily addresses the configuration management of the system’s releases, made up of somewhat independent files that can be assembled in various ways to produce a running system. It is also concerned with the mapping from logical classes and components to physical artifacts. With the UML, the static aspects of this view are captured in artifact diagrams; the dynamic aspects of this view are captured in interaction diagrams, state diagrams, and activity diagrams.

Thedeployment view of a system encompasses the nodes that form the system’s hardware topology on which the system executes. This view primarily addresses the distribution, delivery, and installation of the parts that make up the physical system. With the UML, the static aspects of this view are captured in deployment diagrams; the dynamic aspects of this view are captured in interaction diagrams, state diagrams, and activity diagrams.

Each of these five views can stand alone so that different stakeholders can focus on the issues of the system’s architecture that most concern them. These five views also interact with one another: Nodes in the deployment view hold components in the implementation view that, in turn, represent the physical realization of classes, interfaces, collaborations, and active classes from the design and process views. The UML permits you to express each of these five views.

 

系统的实施视图包含的产品通常用于物理系统的集合和发布．这个视图主要定位系统发布的配置管理，由少量独立文件组成，这样就能以不同的方式组合从而产生一个可运行的系统．也可能涉及到从逻辑类和组件映射到物理产品．在UML中，实物图捕获的是该视图的静态一面;动态一面则是通过交互图，状态图和活动图捕获．

系统的部署视图包含那些运行了该系统的节点，并形成系统的硬件拓扑结构．这个视图主要定位分布，传送和组成物理系统的安装部分．在UML中，部署图捕获的是该视图的静态一面;动态一面则是通过交互图，状态图和活动图捕获．

这五个视图的每一个都可以单独成立，所以不同的利害关系人能致力于涉及到他们的系统体系结构的问题．这五个视图也相互作用：在部署视图里的节点保存的是实施视图中的那个组件．依此类推，表现类，接口，协作和活动类的物理实现来自设计和进程视图．UML允许建模者表达这五个视图的任何一个．