02291: System Integration Introduction to UML Hubert Baumeister - - PowerPoint PPT Presentation
02291: System Integration Introduction to UML Hubert Baumeister huba@dtu.dk DTU Compute Technical University of Denmark Spring 2020 What is the UML? Unified Modelling Language (UML) Family of graphical notations for describing aspects
◮ ”A picture is more than a thousand words”
◮ managed by the Object Management Group
◮ http://www.uml.org
◮ Objects became main stream ◮ OO methods and graphical notations ◮ Grady Booch, Peter Coad, Ivar Jacobson, Jim Odell, Jim
◮ Grady Booch, Ivar Jacobson and Jim Rumbaugh at
◮ First version of the UML (UML 0.8)
◮ The Object Management Group (OMG) ◮ Driven by tool vendors! ◮ Tool interoperability!
◮ UML 2.0 ISO standard
◮ a set of graphical notations ◮ and a single metamodel
{pre: bor.canBorrow() post: dueDate = Date.today + 3 weeks and bor.books->containing(self) } {body: books->size <= 5 and books->forAll(b | not(b.overdue))} <<interface>> LibraryInterface scanLibraryCard() checkOut scanBook() checkIn ... {inv: overdue iff dueDate <> null and today > dueDate} Book
dueDate register() deregister() checkout() checkin() Borrower canBorrow() Library scan library card() check out scan book() check in ... 0..5 * user *
Classifier Class Operation Classifier StructuralFeature Association + isDerived : Boolean = false Classifier Relationship ValueSpecification Type Property + isDerived : Boolean = false + isReadOnly : Boolean = false {redefines isReadOnly} + isDerivedUnion : Boolean = false + /default : String [0..1] + aggregation : AggregationKind = none + /isComposite : Boolean + isID : Boolean = false «enumeration» AggregationKind none shared composite * + class * + /superClass {subsets classifier} {redefines general} 0..1 + class * + ownedOperation {subsets featuringClassifier, subsets redefinitionContext, subsets namespace} {ordered, subsets feature, subsets redefinableElement, subsets ownedMember} 0..1 + class * + nestedClassifier {subsets namespace, subsets redefinitionContext} {ordered, subsets ownedMember, subsets redefinableElement} 0..1 + association * + navigableOwnedEnd {subsets owningAssociation} {subsets ownedEnd} 0..1 + owningAssociation * + ownedEnd {subsets association, subsets featuringClassifier, subsets namespace, subsets redefinitionContext} {ordered, subsets memberEnd, subsets feature, subsets ownedMember, subsets redefinableElement} 0..1 + association 2..* + memberEnd {subsets memberNamespace} {ordered, subsets member} 0..1 + owningProperty 0..1 + defaultValue {subsets owner} {subsets ownedElement} * + association 1..* + /endType {subsets relationship} {ordered, readOnly, subsets relatedElement} 0..1 + class * + ownedAttribute {subsets classifier, subsets namespace} {ordered, subsets attribute, subsets ownedMember} * * + subsettedProperty 0..1 0..1 + /opposite * + property * + redefinedProperty {subsets redefinableElement} {subsets redefinedElement} {pre: bor.canBorrow() post: dueDate = Date.today + 3 weeks and bor.books->containing(self) } {body: books->size <= 5 and books->forAll(b | not(b.overdue))} <<interface>> LibraryInterface scanLibraryCard() checkOut scanBook() checkIn ... {inv: overdue iff dueDate <> null and today > dueDate} Book
dueDate register() deregister() checkout() checkin() Borrower canBorrow() Library scan library card() check out scan book() check in ... 0..5 * user *
◮ e.g. class, association, . . .
◮ e.g. the concept of a class is mapped to rectangle with
◮ Basically UML class diagrams
◮ XMI (XML Metadata Interchange)
◮ Meaning of class? ◮ Execution of activity diagrams and state machines
◮ Left open in the standard ◮ Tool vendors choose meaning
◮ Informal use
◮ Forward Engineering: e.g. create class stubs
◮ Executable UML ◮ Problems ◮ How to describe the behaviour?
◮ lightweight (UML profile) ◮ heavy weight
◮ Class Diagram ◮ Class, features, and relationships ◮ Object Diagram ◮ Example configuration of instances ◮ Package Diagram ◮ Hierarchical structure for models ◮ Component Diagram ◮ Structure and connections of components ◮ Deployment Diagram ◮ Deployment of artifacts to nodes ◮ Composite Structure Diagram ◮ Runtime decomposition of a class
◮ Use-Case Diagram ◮ How users interact with a system ◮ Activity Diagram ◮ Procedural and parallel behaviour ◮ State Machine Diagram ◮ How events change an object over its life ◮ Interaction Diagram ◮ Sequence Diagram: Interaction between objects; emphasis
◮ Communication Diagram (formerly called collaboration
◮ Interaction Overview Diagram: Mix of sequence and activity
◮ Timing Diagram: Interaction between objects; emphasis on
User LibrarySystem borrow book return book search for book
user ok user ok can borrow? ... ... book scanned User scanned Idle checkOut/return [not cb] / return "book can't be borrowed" scanBook(l) [cb] / b.checkOut(); return "ok" / cb := bor.canBorrow() [users->contains(l)]/return true [not users->contains(l)] / return err-msg scanLibraryCard (l)
sd: borrow book success scan library card(bor) true checkOut() scan book(b) canBorrow() isOverdue() false loop true checkout(bor) true true loop User Library bor:Borrower [b in bor.books] b1:Book b2:Book
sd: borrow book success scan library card(bor) true checkOut() scan book(b) canBorrow() loop true true loop User Library
user ok user ok can borrow? ... ... book scanned User scanned Idle checkOut/return [not cb] / return "book can't be borrowed" scanBook(l) [cb] / b.checkOut(); return "ok" / cb := bor.canBorrow() [users->contains(l)]/return true [not users->contains(l)] / return err-msg scanLibraryCard (l) sd: borrow book success scan library card(bor) true checkOut() scan book(b) canBorrow() isOverdue() false loop true checkout(bor) true true loop User Library bor:Borrower [b in bor.books] b1:Book b2:Book