【正文】 將來 Rose也可以在模型中加入代碼。 Rose系列工具進行軟件開發(fā)的全過程。實體類是客觀存在的，所以在需求階段的靜態(tài)結(jié)構(gòu)中，主要是指實體類（即業(yè)務(wù)對象）和重要的邊界類、控制類（但一般是抽象類）。 Class圖是否是同時生成并交互修改 ? 1）嚴(yán)格地說，一上來就畫靜態(tài)結(jié)構(gòu)（類圖）不對，靜態(tài)結(jié)構(gòu)是為動態(tài)模型完成的功能服務(wù)的，所以應(yīng)該先有需求階段的順序圖（動態(tài)模型），后有靜態(tài)模型，這是因果關(guān)系。 可參考 Rose RUP Framework。 this is what is meant by the highlevel anization of subsystems. The other lowerlevel layers are in focus during architectural design, refer to the activity Architectural Design for more information. Layer package ? A package should be used in cases where a set of classes and/or other packages need to be grouped together for model anization purposes. Though the contents of the package can have public visibility, which makes them visible to model elements outside the containing package, packages are primarily just grouping mechanisms. ? If a set of classes is to be encapsulated and can be hidden behind a welldefined interface, a subsystem is a more appropriate container. Layer subsystem ? A subsystem should be used in cases where a set of classes and/or other packages need to be encapsulated within a container and hidden behind a set of welldefined interfaces. By convention, none of the contents of subsystem are visible except the interfaces of the subsystem. This allows subsystems to be easily replaced, and the implementations changed, provided the interfaces remain unchanged. It offers a degree of encapsulation greater than that of the package. ? If a set of classes is merely to be grouped together, but public visibility of classes is still desirable, a package is a more appropriate container. Subsystem設(shè)計步驟 ? Distribute Subsystem behavior to Subsystem Elements ? Document Subsystem Elements ? Describe Subsystem Dependencies ? Checkpoints Class設(shè)計步驟 ? Create Initial Design Classes ? Identify Persistent Classes ? Define Operations ? Define Class Visibility ? Define Methods ? Define States ? Define Attributes ? Define Dependencies ? Define Associations ? Define Generalizations ? Resolve Use Case Collisions ? Handle NonFunctional Requirements in General ? Checkpoints Process View ? Process view diagram illustrates the position of processes and threads, and the mapping of classes onto those processes and threads. Process NameprocessThread NamethreadUse Case設(shè)計步驟 ? Describe Interactions Between Design Objects ? Simplify Interaction Diagrams Using Subsystems (optional) ? Describe PersistenceRelated Description ? Refine the Flow of Events Description ? Unify Classes and Subsystems ? Checkpoints Use Case Realizations package ? In this Package we will describe Use Case Realizations as stereotyped use cases. ? A usecase realization describes how a particular use case is realized within the design model, in terms of collaborating objects. ? A realize dependency is used between the Use Case Realization and the Use Case in the usecase model that is realized. Use Case Name(from Use Case Name)UseCase Nameusecase realizationrealizeUse Case Realization ? Participating classes diagram ? realize dependicies ? Sequence Diagram basic type, other flow type Component View ? Implementation Model is a collection of ponents, and the implementation subsystems that contain them. An architectural view that describes one or several system configurations。s implementation. They define the objects, which in turn are abstractions of the objects in the system39。domain model39。 二、 RUP建模過程與步驟 系統(tǒng)分析、設(shè)計工作流 Use Case分析步驟 ? Supplement the UseCase Description ? For each usecase realization – Find Classes from UseCase Behavior – Distribute UseCase Behavior to Classes ? For each resulting analysis class – Describe Responsibilities – Describe Attributes and Associations – Qualify Analysis Mechanisms ? Unify Analysis Classes ? Checkpoints [舉例 ] Use Case View ? Business Object Model（可選） describing the business ? Use Case Model for the system a model of the behavior of a system which supports the business processes. Use Case Model ? The UseCase Model is traceable to (and derives from) the Business Model. The system (as described in the Use Case Model) provides behavior that supports the business. Use Case package ? Use Case package All Use Cases in the system are contained in this package. This is done strictly as a way to anize the model and make it easier to understand. Use Cases are often documented in a separate text file, use the Rational Unified Process template or use the use case template in Rational Requsite Pro. The Use Case Realizations that correspond to these use cases are created in the Design Model.. Use Case package ? Included Use Cases package contains mon use cases which are textually included in one or more other use cases. They are anized in this package to promote greater reuse. ? Architecturally Significant Use Cases diagram contains all architecturally significant use cases. Annotations may be added to the diagram to explain why particular use cases are architecturally significant. Actor Package ? Actor package All Actors in the system are contained in this package. This is both as a way to anize the model, making it easier to understand, and to provide a way to manage the actors in a single configuration item. Logical View ? Analysis Model (optional) contains a set of Analysis Classes, which describe an abstract realization of the use cases of the system。 ? 直接連接，如 RS232。 the connection type and bandwidth, the manufacturer, model, memory, and disks of a machine, or the kind and size of a device. ? Processes Processes denote the root of a main program from a ponent diagram or the name of an active objec