CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 The Unified Modeling Language is a visual language used to create models of programs.

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to.
Stereotypes Stereotypes provide the capability to create a new kind of modeling element. –They can be used to classify or mark modeling elements. –A type.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
CS 340 UML Class Diagrams. A model is an abstraction of a system, specifying the modeled system from a certain viewpoint and at a certain level of abstraction.
UML Class and Sequence Diagrams Violet Slides adapted from Marty Stepp, CSE 403, Winter 2012 CSE 403 Spring 2012 Anton Osobov.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
UML – Class Diagrams.
7M701 1 Class Diagram advanced concepts. 7M701 2 Characteristics of Object Oriented Design (OOD) objectData and operations (functions) are combined 
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Chapter 7: System models
Unified Modeling Language
The Unified Modeling Language (UML) Class Diagrams.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
An Introduction to Java Chapter 11 Object-Oriented Application Development: Part I.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
Chapter 7 System models.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Chapter Two The UML – Unified Modeling Language Ku-Yaw Chang Assistant Professor, Department of Computer Science and Information.
Domain Modeling Part2: Domain Class Diagram Chapter 4 pp part 2 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
An Introduction to the Unified Modeling Language
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
CS 325: Software Engineering January 27, 2015 Domain Modeling Application Domains UML Class Diagrams.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Lab 5 CPIT 250 System Analysis and Design.
CSE 219 Computer Science III UML. UML Diagrams UML - Unified Modeling Language UML diagrams are used to design object-oriented software systems –represent.
UML Part 1: Class Diagrams. Introduction UML stands for Unified Modeling Language. It represents a unification of the concepts and notations presented.
Class diagrams Terézia Mézešová.
Copyright © 2012 Pearson Education, Inc. Chapter 13: Introduction to Classes.
Chapter 3: Introducing the UML
Object Modeling THETOPPERSWAY.COM. Object Modelling Technique(OMT)  Building a model of an application domain and then adding implementation.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
COP 3330 Notes 4/13. Today’s Topics UML Class Diagrams.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
 Class and Diagram  Representation of Class Name Attributes Operations  Visibility of Attributes and Operations.
Data Modeling Using the Entity- Relationship (ER) Model
Appendix 3 Object-Oriented Analysis and Design
Unified Modeling Language Tutorial
DATA REQIREMENT ANALYSIS
Object-Oriented Analysis and Design
Review for Midterm, Fall 2009
Unified Modeling Language
University of Central Florida COP 3330 Object Oriented Programming
Abstract descriptions of systems whose requirements are being analysed
Business System Development
Domain Class Diagram Chapter 4 Part 2 pp
Software Engineering Lecture #11.
Chapter 20 Object-Oriented Analysis and Design
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
CS 8532: Advanced Software Engineering
Class Diagram.
CIS 375 Bruce R. Maxim UM-Dearborn
2.1 Introduction to Object-Oriented Programming
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Appendix 3 Object-Oriented Analysis and Design
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
Presentation transcript:

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 The Unified Modeling Language is a visual language used to create models of programs. UML has several different diagrams. Each diagram shows the relationship among different sets of entities, depending upon the purpose of the diagram. Use Case (Analysis Phase) involve entities interacting with the system Interaction Diagrams (Looking at Objects Interactions) Shows how specific objects interact with each other Class Diagrams (Design Phase) detail the relationships between classes State Diagrams (Looking at Objects Behaviors) Detail the different states an object may be in as well as the transitions between states Deployment Phase (Deployment Phase) How different modules will be deployed.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 Class Diagram – describes classes and shows the relationships between them. When one class is a “kind of” another class; the is-a relationship When there are associations between two classes –One class “contains” another class: the has-a relationship Composition: the contained item is part of the containing item (an engine in a car) Composition: the contained item is part of the containing item (an engine in a car) Aggregation: the contained item is part of a collection of items (airplanes in an airport) Aggregation: the contained item is part of a collection of items (airplanes in an airport) –One class “uses” another class: the uses-a relationship –One class “creates” another class

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 A rectangle represents a class. Three aspects to the rectangle/class are: –The name of the class –The data members of the class –The methods of the class The following three figures show just a class defined, a class with a public method, and a class with a private attribute and a public method respectfully.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 A rectangle represents a class with it’s name at the top. The next section of the rectangle lists the attributes in the class. Each attribute contains: –A scope identifier (Public (+), private (-), protected (#). –The name of the attribute –A colon –The data type of the attribute The final section of the rectangle lists the methods of the class. Each method contains: –A scope identifier (Public (+), private (-), protected (#). –The name of the method –The parameters, if they exist, for the method. –A return value for the function, if it exists.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 UML Notation for Relationships You can use UML to notate which accessibility you want each member to have. The most common follow, A aggregates B, A is composed of B, B is derived from A, and A depends on B respectively.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 UML Notation for Relationships You can use UML to notate which accessibility you want each member to have. The most common follow, A aggregates B, A is composed of B, B is derived from A, and A depends on B respectively.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 Class diagram, showing the is-a relationship of the most basic example of our case study. Note there are no attributes or methods, just the relationships between classes.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 Class diagram, showing the has relationship between an airport and aircraft as well as an is-a relationship between a Jet/Helicopter and the Aircraft.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 Technically, the Aircraft is an abstract class. In UML this is shown by writing the name of the class in italics.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 No markup language is perfect, so UML gives you the ability to add notes to your diagram.

CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 UML will also allow you to show cardinality. Here 1 car has 4 or 5 tires. In addition, it shows that a car is dependent upon a gas station.