University of Central Florida Fall 2014 COP 4331 Recitation 2 Unified Modeling Language Class amp Sequence Diagrams Each class is divided into three components Class Diagram Each class is divided into three components ID: 381949
Download Presentation The PPT/PDF document "Department of Electrical Engineering and..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Department of Electrical Engineering and Computer ScienceUniversity of Central FloridaFall 2014
COP 4331 Recitation
#2Slide2
Unified Modeling LanguageClass & Sequence DiagramsSlide3
Each class is divided into three components:Class DiagramSlide4
Each class is divided into three components:Class Diagram
Class NameSlide5
Each class is divided into three components:Class Diagram
Class Name
AttributesSlide6
Each class is divided into three components:Class Diagram
Class Name
Attributes
Attributes can be:
+ Public
- Private
# ProtectedSlide7
Each class is divided into three components:Class Diagram
Class Name
Attributes
OperationsSlide8
Class Diagram example:Slide9
Class Diagram example:
PatronSlide10
Class Diagram example:
Patron
#
ID_Number
: integer
+Name : String
- Fines : doubleSlide11
Class Diagram example:
Patron
#
ID_Number
: integer
+Name : String
- Fines : double
checkFines
()
payFines
()Slide12
Class diagrams also contain information regarding the relationship between themAssociationDependencyGeneralization
Class DiagramSlide13
Association: A link indicating that two classes need to communicate with one anotherClass Diagram
Student
ProfessorSlide14
Association: A link indicating that two classes need to communicate with one anotherMultiplicity: Every professor has 1 or more studentsClass Diagram
Student
Professor
[1…*]Slide15
Association: A link indicating that two classes need to communicate with one anotherMultiplicity: Every professor has 1 or more studentsRole Names: Students learn from ProfessorsClass Diagram
Student
Professor
learns from
teaches Slide16
Aggregation: “has a” association. Each part exists outside of the wholeShown by using an empty diamondClass Diagram
Car
Wheel
EngineSlide17
Composition: demonstrates strong ownership, the part cannot exist without the whole and vice versaShown by using a filled diamondClass Diagram
Person
Arm
LegSlide18
Dependency relationship: Is a semantic relationship between classes because the functionality of one depends on the otherClass Diagram
Calendar
addEvent
(p: Party)
PartySlide19
Generalization: connection between a subclass and a superclassClass Diagram
People
Student
ProfessorSlide20
Sequence diagrams emphasis the time ordering of messagesSequence DiagramSlide21
Sequence diagrams emphasis the time ordering of messagesObjects create the “object life line”Sequence DiagramSlide22
Messages are shown by a horizontal line between life linesMay include a conditionSequence Diagram
Customer
Bank
withdraw moneySlide23
A return message is a response from the objectSequence Diagram
Customer
Bank
withdraw money
moneySlide24
The end of an object life line is demonstrated by an XSequence Diagram
BankSlide25
Shari Lawrence Pfleeger and Joanne M. Atlee, "Software Engineering: Theory and Practice", 4th Edition, Prentice Hall, 2010.Prepared/modified byKia Manoochehri
kiam@knights.ucf.edu
Gurkan
Solmaz
gsolmaz@knights.ucf.edu
References