FORDHAM CSLU 3598 - chap10 MORE ON UML

Unformatted text preview:

Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30Slide 31Slide 32Slide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40Slide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Slide 48Slide 49Slide 50Slide 51Slide 52Slide 53Slide 54Slide 55Slide 56Slide 57Slide 58Slide 59Slide 60Slide 61Slide 62Slide 63Slide 64Slide 65Slide 66Slide 67Slide 68Slide 69Slide 70Slide 71Slide 72Slide 73Slide 74Slide 75Slide 76Slide 77Slide 10A.1Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction toObject-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004Stephen R. [email protected] 10A.2Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CHAPTER 10 — Unit AMORE ON UMLSlide 10A.3Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter OverviewUML Is Not a MethodologyClass DiagramsNotesUse-Case DiagramsStereotypesInteraction DiagramsStatechartsActivity DiagramsPackagesComponent DiagramsSlide 10A.4Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter Overview (contd)Deployment DiagramsReview of UML DiagramsUML and IterationSlide 10A.5Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. The Current Version of UMLLike all modern computer languages, UML is constantly changing–When this book was written, the latest version of UML was Version 1.4–By now some aspects of UML may have changedUML is now under the control of the Object Management Group (OMG)–Check for updates at the OMG Web site, www.omg.orgSlide 10A.6Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. UML Is Not a MethodologyUML is an acronym for Unified Modeling Language–UML is therefore a languageA language is simply a tool for expressing ideasSlide 10A.7Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. UML Is Not a MethodologyUML is a notation, not a methodology–It can be used in conjunction with any methodologyUML is not merely a notation, it is the notationUML has become a world standard–Every information technology professional today needs to know UMLSlide 10A.8Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. UML Is Not a Methodology (contd)The title of this chapter is “More on UML” –Surely it should be “All of UML”?The manual for Version 1.4 of UML is nearly 600 pages long–Complete coverage is not possibleSurely every information technology professional must know every aspect of UML?Slide 10A.9Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. UML Is Not a Methodology (contd)UML is a languageThe English language has over 100,000 words–We can manage fine with just a subsetThe small subset of UML presented in Chapters 3 through 9 is adequate for the purposes of this bookThe larger subset of UML presented in this chapter is adequate for the systems analysis and design of most information systemsSlide 10A.10Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. UML Is Not a Methodology (contd)UML can be used for modeling all kinds of software–This book is on systems analysis and design, not the full life cycle –This book is on information systems, not other types of softwareThose features of UML most appropriate for the systems analysis and design of information systems are included in this bookSlide 10A.11Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class DiagramsA class diagram depicts classes and their interrelationshipsHere is the simplest possible class diagramSlide 10A.12Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams (contd)Class diagram showing more details of Bank Account ClassAdd as many (or as few) details as appropriate for the current iteration and incrementationSlide 10A.13Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams: Notation (contd)Freedom of notation extends to objects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 classSlide 10A.14Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams: Notation (contd)UML allows a shorter notation when there is no ambiguity–bank accountSlide 10A.15Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams: Notation (contd)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” This notation has been widely used in the interaction diagrams of Chapters 6 and 7Slide 10A.16Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams: Visibility Prefixes (contd)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 classSlide 10A.17Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Class Diagrams: Visibility Prefixes (contd)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 information systemSlide 10A.18Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. AggregationExample: “A car consists of a chassis, an engine, wheels, and seats”Slide 10A.19Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Aggregation (contd)The open diamonds denote aggregation–Aggregation


View Full Document
Download chap10 MORE ON UML
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view chap10 MORE ON UML and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view chap10 MORE ON UML 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?