Topics Covered Today Unit 1. 2 Designing Classes 1. 2. 1 UML Class diagrams 1.2.2 Relationships between Classes 1.2.3 Common Class structures 1.2.4 UML with eclipse
2 Topics Covered Today • Unit 1.2 Designing Classes – 1.2.1 UML Class Diagrams – 1.2.2 Relationships Between Classes – 1.2.3 Common Class Structures – 1.2.4 UML with Eclipse
UML Introduction Programming is like building a house. An architect creates a design, and a builder uses appropriate tools to carry out the design The builder does not proceed without a blueprint from the architect Software developers also need a blueprint to create complex systems The UML is a toolbox of graphical notations used to produce the blueprint a graphical l depiction of the software design UML, Unified modeling language
3 UML Introduction • Programming is like building a house. An architect creates a design, and a builder uses appropriate tools to carry out the design. The builder does not proceed without a blueprint from the architect. • Software developers also need a blueprint to create complex systems. • The UML is a toolbox of graphical notations used to produce the blueprint -- a graphical depiction of the software design • UML, Unified Modeling Language
Unified Modelling Language (UML) A graph ohio cal language for Visualising Specifying Constructin g Documenting Object-oriented software systems ·OMG( Object management Group国际对象管理 组织) is responsible for UML standard
4 Unified Modelling Language (UML) • A graphical language for – Visualising – Specifying – Constructing – Documenting • Object-oriented software systems • OMG (Object Management Group国际对象管理 组织) is responsible for UML standard
UML UML is not a method it does not outline a procedure for designing software; It is a modeling language that captures the design graphically Whatever process you use you can use uml to record the results of your anal ysis and design decisions
5 UML • UML is not a method. It does not outline a procedure for designing software; it is a modeling language that captures the design graphically. • Whatever process you use, you can use UML to record the results of your analysis and design decisions
UML The main reason to use uml notation is communication To discuss design with someone both need to understand the modeling language, not the process used to come up with the design Human language is imprecise Code is too detailed
6 UML • The main reason to use UML notation is communication. – To discuss design with someone, both need to understand the modeling language, not the process used to come up with the design. – Human language is imprecise – Code is too detailed