More on UML

More on UML - MOREonUML Adaptedfrom:

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 MORE on UML Adapted from: Object-Oriented and Classical Software Engineering Chapter 16 Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach
Background image of page 1

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 12 - 2 Overview Overview Class diagrams Notes Use-case diagrams Stereotypes Interaction diagrams Statecharts Activity diagrams Packages Component diagrams Deployment diagrams
Background image of page 2
CUHK, Spring 2007 Software Engineering / 12 - 3 Unified Modeling Language (UML) Unified Modeling Language (UML) UML is now under the control of the  Object Management Group (OMG) Check for updates at the OMG Web site,  www.omg.org UML has become a world standard Every information technology professional today  needs to know UML
Background image of page 3

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 12 - 4 1. Class Diagrams 1. Class Diagrams A class diagram depicts  classes and their interrelationships Add as many (or as few) details as appropriate for the  current iteration and incrementation
Background image of page 4
CUHK, Spring 2007 Software Engineering / 12 - 5     Class Diagrams: Notation Class Diagrams: Notation Example:  bank account :  Bank Account Class bank account is an object, an instance of a class  Bank  Account Class The underlining denotes an object The colon denotes “an instance of”  The bold face and initial upper case letters in  Bank Account  Class  denote that this is a class UML allows a shorter notation when there is no  ambiguity, e.g., bank account
Background image of page 5

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 12 - 6 The UML notation for modeling the concept of  an arbitrary bank account is     :  Bank Account Class The colon means “an instance of,” so  Bank Account Class   means  “an instance of class  Bank Account  Class ” 
Background image of page 6
CUHK, Spring 2007 Software Engineering / 12 - 7 Class Diagrams: Visibility Prefixes Class Diagrams: Visibility Prefixes UML visibility prefixes (used for information hiding)  Prefix + indicates that an attribute or operation is  public Visible everywhere Prefix – denotes that the attribute or operation is  private Visible only in the class in which it is defined Prefix # denotes that the attribute or operation is  protected Visible either within the class in which it is defined or within  subclasses of that class
Background image of page 7

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 12 - 8 Example: Class diagram with visibility prefixes added Attribute accountBalance is visible only within the  Bank Account Class Operations deposit and withdraw are accessible from  anywhere within the software product
Background image of page 8
CUHK, Spring 2007 Software Engineering / 12 - 9 Aggregation Aggregation Example: “A car consists  of a chassis, an engine, 
Background image of page 9

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

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 12/28/2010 for the course CSC CSC2120 taught by Professor Xiacai during the Spring '07 term at CUHK.

Page1 / 45

More on UML - MOREonUML Adaptedfrom:

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

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