【正文】 IT行業(yè)絕大部分（ 7080%）的軟件設(shè)計(jì)（包括數(shù)據(jù)庫(kù)設(shè)計(jì)）可以采用OO方法，目前國(guó)外流行的趨勢(shì)也是這樣，剩下的少部分有特定需求的可能還會(huì)用傳統(tǒng)方法。 ActorUse Case 用例 ? The specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system. ? A use case is a coherent unit of functionality provided by a system, a subsystem, or a class as manifested by sequences of messages exchanged among the system and one or more outside interactors (called actors) together with actions performed by the system. Use CaseBusiness Use Case/Actor Business ActorBusiness UseCaseBusiness System ? 例子 登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登includeincludeinclude課程登記系統(tǒng) 登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登登Use Case依賴關(guān)系 ? Association – The participation of an actor in a use case, . instances of the actor and instances of the use case municate with each other. This is the only relationship between actors and use cases. ? Extend – An extend relationship from use case A to use case B indicates that an instance of use case B may be extended (subject to specific conditions specified in the extension) by the behavior specified by A. The behavior is inserted at the location defined by the extension point in B which is referenced by the extend relationship. Use Case依賴關(guān)系 ? Generalization – A generalization from use case A to use case B indicates that A is a specialization of B. ? Include – An include relationship from use case A to use case B indicates that an instance of the use case A will also include the behavior as specified by B. The behavior is included at the location which defined in A. 登登登登登登登登登登登登 登登登登 登登登登登登登登登登includeincludeincludeextend產(chǎn)品定購(gòu)管理 Actor Generalization 登登登登登登登登登登登登登登登Sequence Diagram A diagram that shows object interactions arranged in time sequence. In particular, it shows the objects participating in the interaction and the sequence of messages exchanged. Unlike a collaboration diagram, a sequence diagram includes time sequences but does not include object relationships. A sequence diagram can exist in a generic form (describes all possible scenarios) and in an instance form (describes one actual scenario). Sequence diagrams and collaboration diagrams express similar information, but show it in different ways. 序列圖元素 Joe : CustomerBanking Screen : AccountFormUse Case描述 ? 簡(jiǎn)述： This use case allows a Student to register for course offering in the current semester. The Student can also update or delete course selections if changes are made within the add/drop period at the beginning of the semester. The Course Catalog System provides a list of all the course offerings for the current semester. 登登登登事件流 Basic Flow: This use case start when a Student wishes to register for course offerings, or to change his/her existing course schedule. 1. The system requests that the Student specify the function he/she would like to perform (either Create a Schedule, Update a Schedule, or Delete a Schedule). 2. Once the Student provides the requested information, one of the subflows is executed. If the Registrar selected “Create a Schedule”, the Create a Schedule subflow is executed. (Update a Schedule, Delete a Schedule) Create a Schedule 1. The system retrieves a list of available course offerings from the Course Catalog System and displays the list to the Student. 2. The Student selects 4 primary course offerings and 2 alternate course offerings from the list of available offerings. 3. Once the student has made his/her selections, the system creates a schedule for the Student containing the selected course offerings. 4. The Submit Schedule subflow is executed. 類的劃分 ? 邊界類 ? 控制類 ? 實(shí)體類 Control EntityActor Boundary : 登登 : 登登登登 : 登登登登登登登 : 登登登登 : 登登登登登登登登登登登登登登登登登登登登登登4登登登登2登登登登登登登登登登登登登登登登登登登4登登選課 理解 Use Case和 Actor 1） Use Case絕不是錦上添花的東西，一方面它可以促進(jìn)與用戶溝通，理解正確的需求，另一方面它可以劃分系統(tǒng)與外部實(shí)體的界限，是系統(tǒng)設(shè)計(jì)的起點(diǎn)，而最終應(yīng)該落實(shí)到類和實(shí)現(xiàn)代碼上。 ? 可溯關(guān)系 是兩個(gè)元素或元素集合之間的概念連接，用于描述位于不同語義層或多種視點(diǎn)下的同一個(gè)概念。 子程序 ? 不含類聲明。 evolve into associated design elements which are modeled in the Design Model. ? Business Object Model ? Design Model Business Object Model ? contains a set of interacting workers and business entity (domain) classes which collaborate to enact the business processes. In some cases, only the business entity classes are documented. The business entity classes as a whole are sometimes referred to as a 39。 ,哪些對(duì)象的命名可用中文 ?如 Sequence圖中的 Message命名是否不能用中文 ? 業(yè)務(wù)模型、抽象類，不影響代碼生成的圖形元素均可以。 VB語言的模型中， VB Form如何在模型中實(shí)現(xiàn) ? ? Order Visual Interface現(xiàn)？ ? A stereotype is, in effect, a new class of modeling element that is introduced at modeling time. It represents a subclass of an existing modeling element with the same form (attributes and relationships) but with a different intent. Generally a stereotype represents a usage distinction. ? A stereotyped element may have additional constraints on it from the base class. It may also have required tagged values that add information needed by elements with the stereotype. It is expected that code generators and other tools will treat stereotyped elements specially. ? Stereotypes represent one of the builtin extensibility mechanisms of UML. 自定義 stereotype ? Stereotypes allow you to provide additional distinctions in your model that are not explicitly supported by the UML metamodel. Stereotypes extend the basic modeling elements to create new elements. This makes it easier to add information about modeling elements that may be specific to a project or process. ? A diagram icon (.wmf, .emf) ? A small diagram toolbar icon (.bmp) ? A large diagram toolbar icon