DOC PREVIEW
UT Dallas CS 6359 - Misc_ModelingWithUML

This preview shows page 1-2-3-24-25-26-27-49-50-51 out of 51 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 51 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1UML OverviewUML OverviewUML and OO MethodologiesUML and OO MethodologiesUML and OO MethodologiesUML ElementsUML Elements – Structural ThingsUML Elements – Structural ThingsUML Elements – Other ThingsUML Elements – RelationshipsUML Elements – RelationshipsUML Elements – DiagramsUML - Extension MechanismsUML - Extension MechanismsUML - Extension MechanismsUML - Extension MechanismsUML - Extension MechanismsUML and ‘4+1 Views’Class DiagramClass DiagramClass Diagram - ExamplesClass Diagram - ExamplesClass Diagram - ExamplesClass Diagram - ExamplesObject DiagramObject Diagrams - ExamplesObject Diagrams - ExamplesComponent DiagramComponent Diagrams - ExamplesComponent Diagrams - ExamplesComponent Diagrams - ExamplesPackage DiagramPackage Diagrams - ExamplesPackage Diagrams - ExamplesDeployment DiagramDeployment Diagrams - ArtifactsDeployment Diagrams - NodesDeployment Diagrams - ExamplesDeployment Diagrams - ExamplesUML - DiagramsState Machine DiagramState Machine Diagrams -ElementsState Machine Diagrams -ExamplesState Machine Diagrams -ExamplesSequence DiagramSequence DiagramsSequence Diagrams - ElementsUML - DiagramsQuestions and AnswersAssignmentCS/SE 6362-501 – Object-Oriented Analysis and Design (OOA/D)The Unified Modeling LanguageEbenezer Oladimeji, [email protected] Overview A general purpose visual modeling language for specifying, visualizing, constructing, and documenting the artifacts of software systems. Created by Object Management Group (OMG)Established as a standardLanguage Specification at www.uml.org UML has a direct relation with object oriented analysis and design (OOAD) Based on formal specificationsMeta-modelMeta-meta model ExtensibleUML Overview GoalsA picture is worth more than a thousand wordsdefine some general purpose modeling language which all modelers can useIt should be simple to understand and use by stakeholders:-business users, -common people,-Anybody- interested in understanding a systemEstablish a standardUML and OO Methodologies Fundamentals of Object-orientationObjects: an entity and the basic building blockClass: the blue print of an objectAbstraction: represents the behavior of a real world entityEncapsulation: mechanism of binding data together and hiding them from outside world.Inheritance: mechanism of making new classes from existing onePolymorphism: mechanism for classes to exists in different formsUML and OO Methodologies Purpose of OOADIdentifying the objects of a system.Identify their relationships.Make a design which can be converted to executables using OO languages OOAD Approach:OO Analysis  OO Design  OO implementation using OO languages OO enables automation, e.g.:Code generationModel checkingUML and OO Methodologies OOAD Phases:OO Analysis:-Main purpose is to identify objects and describe them properly-objects are to be identified with responsibilities-Responsibilities are the functions performed by the object-When each and every object performs its responsibilities, the purpose of the system is fulfilled.OO Design:-emphasis is given to the requirements and their fulfilment.-Focus is on solution domain-Levels–High-Level design (aka Architecture)–Detailed DesignOO Implementation:-Design is implemented using object oriented programming languages like Java, C++, etc.UML Elements ThingsThe most important building blocks in UML-Structural-Behavioral-Grouping-Annotational Relationships:Another most important building blocks in UML-Dependencies-Association-Generalization-Realization-Aggregation/Composition DiagramsStatic modelsDynamic models.UML Elements – Structural Things ClassAn abstract template for building objects Interface:defines a set of operations which specify the responsibility of a class Collaborationdefines a set of operations which specify the responsibility of a classUML Elements – Structural Things Use Caserepresents a set of actions performed by a system for a specific goal. Component:describes physical part of a system Nodea physical element that exists at run timeUML Elements – Other Things Interaction (behavioral thing)a behavior consisting of a group of messages exchanged among elements to accomplish a specific task. State machine (behavioral thing)a behavior consisting of a group of messages exchanged among elements to accomplish a specific task. Package (grouping thing)Package is the only one grouping thing; for gathering structural and behavioral things. Note (annotational thing)to capture remarks, descriptions, and commentsUML Elements – Relationships Dependencya relationship between two things in which change in one element also affects the other. Associationa set of links that connects UML elements also describes how many objects are taking part in that relationship.. Generalizationa relationship which connects a specialized element with a generalized element. basically describes inheritance relationship RealizationConnects two elements in which one describes some responsibility which is not implemented and the other one implements them. This relationship exists in case of interfacesUML Elements – RelationshipsMultiplicity IndicatorUML Elements – DiagramsWe will focus on diagrams for design modelsUML - Extension Mechanisms While UML is very well-defined, there are situations in which it needs to be customized to specific problem domains UML extension mechanisms are used for:-adding new model elements, -creating new properties, -and specifying new semantics 3 major extension MechanismStereotypesTagged valuesConstraintsUML - Extension Mechanisms StereotypesStereotypes are used to extend UML to create new model elements that can be used in specific domainsE.g. when modeling an elevator control system, we may need to represent some classes, states etc. as -«hardware»-«software»Stereotypes should always be applied in a consistent way«button»CancelButtonStereotypestateUML - Extension Mechanisms Tagged ValuesDefine additional properties for any kind of model elementsCan be defined for existing model elements and for stereotypesAre shown as a tag-value pair where the tag represent the property and the value represent the value of the property•Tagged values can be useful for adding properties about-code generation-version control-configuration management-authorship-etc.UML -


View Full Document

UT Dallas CS 6359 - Misc_ModelingWithUML

Documents in this Course
Lecture2

Lecture2

63 pages

Lecture3

Lecture3

49 pages

Lecture4

Lecture4

48 pages

Lecture5

Lecture5

47 pages

Lecture6

Lecture6

45 pages

Lecture7

Lecture7

63 pages

Lecture8

Lecture8

77 pages

Lecture9

Lecture9

48 pages

Lecture10

Lecture10

84 pages

Lecture11

Lecture11

45 pages

Lecture12

Lecture12

134 pages

Lecture13

Lecture13

62 pages

Lecture14

Lecture14

76 pages

Project

Project

2 pages

Chapter_1

Chapter_1

25 pages

Load more
Download Misc_ModelingWithUML
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 Misc_ModelingWithUML 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 Misc_ModelingWithUML 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?