Lecture 12 Additional UML models and notation Generalization and Aggregation

Lecture 12 Additional UML models and notation Generalization and Aggregation

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

View Full Document Right Arrow Icon
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W. Howden 1 01/08/11
Background image of page 1

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

View Full DocumentRight Arrow Icon
More UML Models Package introduced earlier in discussion of system architecture Activity Deployment Copyright W. Howden 2 01/08/11
Background image of page 2
Copyright W. Howden 3 Warning - UML Terminology Special definitions for: classifier, class, implementation class, interface, type, data type, operation and method Sometimes conforms to “normal” usage of the word and sometimes is a variation Not that important for our informal use of UML models 01/08/11
Background image of page 3

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 4 UML Diagrams Use Case Class Interaction Sequence Collaboration Package Activity Deployment State 01/08/11
Background image of page 4
Copyright W. Howden 5 UML Package Diagrams – Package Relationships Containment In addition to classes, a package may contain other packages Dependencies If one package is dependent on others, changes to their classes/packages may require changes to it also Generalization A “subtype” package must conform to the interface for the more general package. 01/08/11
Background image of page 5

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 6 Relationship Notation Containment, Dependency, Generalization . . Package5 Package6 Package3 Package7 Package8 Package9 01/08/11
Background image of page 6
Notation (Previous slide) Large super package contains packages 5 and 6 Large package depends on packages 3 and 7 Package 3 is a generalization of packages 8 and 9 Copyright W. Howden 7 01/08/11
Background image of page 7

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 8 DS Package Examples DS system package contains sub-packages for GUI, DL and DB packages Dependencies: e.g. changes to classes in DL package/subsystem may require changes to classes in GUI package/subsystem Generalization: e.g. DB package has a facade interface that can be implemented with different DB instances, including a mock DB for phase 1 01/08/11
Background image of page 8
Copyright W. Howden 9 UML Activity Diagrams Similar to (control) flow charts but includes parallelism Are functional, not OO models Parts of diagram (notation can vary) Activities (Oval), Flow edges, Synchronization bars (splitting and merging), Decision boxes (diamond - conditional branch) 01/08/11
Background image of page 9

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 10 01/08/11
Background image of page 10
Copyright W. Howden 11 DS Activity Diagram Example Describes what the system must do when the user asks for a date Use? Abstract functional design Parallelism in example: FrequentDatee Warning and DateeDataMessage have no temporal ordering 01/08/11
Background image of page 11

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

View Full DocumentRight Arrow Icon
Additional Notation Swimlanes Associates actions with different objects In our example, associates actions with user versus system Copyright W. Howden 12 01/08/11
Background image of page 12
Copyright W. Howden 13 01/08/11
Background image of page 13

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 14 Activity Diagram Applications Use case documentation Determining action sequences in designs Describing development process workflows Additional notation: Swimlanes: divide diagram into zones depending on actor responsible for action e.g. earlier DS example 01/08/11
Background image of page 14
Copyright W. Howden
Background image of page 15

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

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

This note was uploaded on 01/07/2011 for the course CSE 140 taught by Professor Rosing during the Fall '06 term at UCSD.

Page1 / 45

Lecture 12 Additional UML models and notation Generalization and Aggregation

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

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