5-20100927 - Introduction to OO Program Design Software...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
Introduction to OO Program Design Software College of SCU Instructor: Shu Li Email: shuli@scu.edu.cn
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 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
Background image of page 2
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
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
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.
Background image of page 4
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.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
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
Background image of page 6
7 UML Diagrams Use case diagram ( o ) Class diagram ( o ) Behavior diagrams ( o ) Statechart diagram ( o ) Activity diagram ( o ) Interaction diagrams ( o ) Sequence diagram ( o ) Collaboration diagram ( o ) Implementation diagrams ( o ) Component diagram ( o ) Deployment diagram ( o )
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 Class Notation A class is represented by a rectangle with three compartments. The first compartment contains the name of the class; the second compartment describes the attributes of the class; and the third compartment describes the methods of the class.
Background image of page 8
9 UML Class Diagram NameClass -attribute1 : Type -attribute2 : Type +method1(param1 : Type, param2 : Type) : Type +method2(param1 : Type, param2 : Type) : Type name attribute method - private + public # protected
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 Employee Class This class contains three private attributes: name hourlyWage hourWorked It also contains the following public methods: Methods to access the values of the attributes:
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 51

5-20100927 - Introduction to OO Program Design Software...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online