Chapter 2 Unified Modeling Language UML Introduction

Chapter 2 Unified Modeling Language UML Introduction

1. Unified modeling language UML is an Object Management Group published in the icon software design language published in 1997. For a software system, the UML language has an important function, visualization function, description function, construction function, construction Document function.

2. MUML includes structural diagrams and behavior patterns. Structured diagrams include 1. Class Diagram 2. Component Diagram 4. Deployment Diagram Diagram (Deployment Diagram) behavior The map includes 1. Activity Diagram 2. Activity Diagram 4. Sequence Diagram 5. Collaboration Diagram 3. Most commonly used Class diagram, state diagram, and timing chart.

Chapter III Software Properties and Creditability

1. Design principles There are those entities of the Open-Closed PrinciPle, and the implementation of the extension is open, and the modification is turned off. * The following principles are implemented - closed means.

Liskov Substitution PrinciPle Any base class, the subclass can appear. * Because the subclass contains all the contents of the parent class, that is, the parent class is a subset of subclasses.

Dependency Inversion Princi Dep Dendency Inversion Princi Relatives Don't rely on implementation. * Interface programming is fully compliant. If a class has an abstract class or interface, then you should try to reference his abstraction or interface. < > 1.If appropriate interface types exist, parameters, return values, variables, and fields should all be declared using interface types.2.If you get into the habit of using interfaces as types, your program will be much more Flexible.3.it is entirely approprise.3.it is entirely appropriate to refer to an Object by a class rather Than an interface if no appropriate interface exists.

Interface Isolation Principle (Interface SegRegation Princi)

It should be provided to the client to provide a small number of individual interfaces, not to provide large total interfaces. Composition / aggregation PrinciPle should try to use synthetic / aggregation, rather than inheritance reaches the purpose of taking. * << Effective Java >> Item 14: Favor Composition over Inheritance.unlike Method Invocation, Inheritance Breaks Encapsulation.

Dimit France (Law of Demeter)

A software entity should interact with other entities as possible.

Oh, it's so tired. At 12:40 ..