最新UML介绍+实战完美版课件.ppt

1、UML介绍+实战 应用设计所应用设计所2019.11.23About learning UML stuff What is a model?Why do we model?When do we model?How to use UML?What is a model?A model is a simplification of reality.Why do we model?We cannot comprehend such a system in its entirety.We build models so that we can better understand the system

2、we are developing.Through modeling,we achieve four aims:Models help us to visualize a system as it is or as we want it to be.Models permit us to specify the structure or behavior of a system.Models give us a template that guides us in constructing a system.Models document the decisions we have made.

3、The larger and more complex the system to be,the more important modeling becomes.The Principles of Modeling Choose your models well.Every model may be expressed at different levels of precision.The best models are connected to reality.No single model or view is sufficient.When do we model?The sooner

4、 the better,and keep modeling in developing.Object-Oriented Modeling&Algorithmic ModelingWhat is the structure of a good object-oriented architecture?Visualizing,specifying,constructing,and documenting object-oriented systems is exactly the purpose of the Unified Modeling Language.Building Blocks of

5、 the UML Things(Structural things,Behavioral things,Grouping things,Annotational things)Relationships(Dependency,Association,Generalization,Realization)Diagrams(Structural Diagrams,Behavioral Diagrams)Things Structural things(Class,interface,collaboration,use case,active class,component,artifact,nod

6、e)Behavioral things(Interaction,state machine,activity)Grouping things(Package)Annotational thingsRelationships Dependency Association Generalization RealizationStructural Diagrams&Behavioral DiagramsUML Structural Diagrams Class diagram(Classes,interfaces,and collaborations)Component diagram(Compon

7、ents)Composite structure diagram(Internal structure)Object diagram(Objects)Artifact diagram(Artifacts)Deployment diagram(Nodes)UML Behavioral Diagrams Use case diagram(Organizes the behaviors of the system)Sequence diagram(Focuses on the time ordering of messages)Communication diagram(Focuses on the

8、 structural organization of objects that send and receive messages)State diagram(Focuses on the changing state of a system driven by events)Activity diagram(Focuses on the flow of control from activity to activity)Class diagramRealization(实现实现)Aggregation(聚合聚合)Class diagramGeneralization(泛化泛化)Associ

9、ation(关联关联)Composition(组合组合)Dependency(依赖依赖)Class diagrams commonly contain:Class Interface Dependency,generalization,realization and association relationshipsClassOperationAttributeClass name“+”is public“-”is private“#”is protectedIf the class is abstract class,the class name will be in italics.Int

10、erfaceAbstract OperationInterface namepublic interface IFly void fly();InterfaceInterface nameRealization Operationpublic interface ILanguage void speak();Generalizationpublic class Bird extends AnimalRealizationpublic class WideGoose implements IFlyDependencypublic abstract class Animal public Meta

11、bolism(Oxygen oxygen,Water water)Associationpublic class Penguin extends Birdprivate Climate climate;Aggregationpublic class WideGooseAggregateprivate WideGoose arrayWideGoose;.has a.(weak)Compositionpublic class Birdprivate Wing wing;public Bird()wing=new Wing();.has a.(strong)The same lifecycle.Ob

12、ject diagramObject diagram对象对象链链属性值属性值匿名对象匿名对象At a point in timeUse case diagramUse case diagramActor(参与者参与者)Relationships(关系关系)Subject(主题主题)Use case(用例用例)Use case diagrams commonly contain:Subject Use cases Actors Dependency,generalization,and association relationshipsWhat is a use case?A use case

13、is a description of a set of sequences of actions,including variants,that a system performs to yield an observable result of value to an actor.Actor&Use case&SubjectNameActorUse caseLogin SystemSubjectInteraction diagramSequence diagramLife line(生命线生命线)Execute specification(执行规约执行规约)objects(对象对象)Asy

14、nchronous message(异步消息异步消息)Return message(返回消息返回消息)TimeSynchronous message(同步消息同步消息)Communication diagram链链对象对象序号序号消息消息路径约束路径约束Interaction diagrams commonly contain:Roles or objects Communications or links MessagesState diagramState diagramInitial state(初始状态初始状态)Simple state(简单状态简单状态)Events(事件事件)Tra

15、nsitions(转移转移)State diagramTCPIP状态变迁图状态变迁图Transitions(转移转移)State diagrams commonly contain:Simple states and composite states Transitions,trigers,and constraintState diagramAction(动作动作)Activity diagramActivity diagrams commonly contain:Actions Activity nodes Flows Object valuesActivity diagramAndroi

16、d Activity LifecycleComponent diagramComponent diagram需接口需接口供接口供接口构件构件依赖依赖使用使用接口声明接口声明实现实现Component diagram需接口需接口供接口供接口端口端口构件声明构件声明端口名端口名接口名接口名Artifact diagramArtifact diagram制品制品依赖依赖Artifact diagramModeling Executables and LibrariesModeling Tables,Files,and DocumentsModeling Source CodeDeployment d

17、iagramDeployment diagramHow to use UML?Forward Engineering&Reverse EngineeringDesign UMLImplementsForward EngineeringReverse EngineeringWe usually write code like this.Poor DesignSimple Factory Design Pattern Better designed,but not the best.Factory Method Design Pattern Best DesignUse UML,let codes become better!UML ToolsIBM Rational RoseMicrosoft VisioVisual Paradigm for UML (VP-UML)ArgoUMLUML Reference BookUML用户指南大象-Thinking in UML UML和模式应用大话设计模式Thank U!