Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.

Slides:



Advertisements
Similar presentations
COMET Approach for UML Overview
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Unified Modeling Language
Introduction To System Analysis and Design
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
CS 501: Software Engineering Fall 2000 Lecture 11 Object-Oriented Design I.
Lecturer: Dr. AJ Bieszczad Chapter 66-1 Object-Oriented analysis and design Special nature of OO development Use cases Design with UML OO system design.
Unified Modeling Language 7/12/2015B.Ramamurthy1 The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson, and Jim Rumbaugh.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 16 Object Oriented Design I.
OO Design Notations Original version by B.Rogers/M.Utting.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Slide 1 UML Review Chapter 2: Introduction to Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version 2.0 Alan Dennis,
Unified Modeling Language, Version 2.0
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Object Oriented Programming Lecture 9: OO Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
1 UML Distilled 3e by Martin Fowler Chapter 1 Introduction to UML.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
1 Introduction to UML. 2 What is UML? UML is an acronym for Unified Modeling Language. Unified –Combines the best from existing object- oriented software.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Chapter 7 The Object-Oriented Approach to Requirements.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Software Engineering Lecture 8 Object-Oriented Analysis.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
MADALINA CROITORU Software Engineering week 4 Practical Madalina Croitoru IUT Montpellier.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
Object Oriented Analysis and Design Introduction to Rational Rose.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Basic Characteristics of Object-Oriented Systems
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
CompSci 280 S Introduction to Software Development
Introduction to UML.
UML(Unified Modeling Language)
Object-Oriented Analysis and Design
Introduction to the Unified Modeling Language
Systems Analysis and Design With UML 2
Unified Modeling Language
Introduction to Unified Modeling Language (UML)
Systems Analysis and Design With UML 2
University of Central Florida COP 3330 Object Oriented Programming
Introduction to Object Oriented Analysis, Design and Unified Modeling Language (UML) Shanika Karunasekera.
IMPORTANT NOTICE TO STUDENTS:
Unified Modeling Language
Introduction to UML.
Introduction to the Unified Modeling Language
Use Cases & Use Case Diagrams
Introduction to the Unified Modeling Language
Software Design Lecture : 15.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case

Object Oriented Modeling Analysis and design (A/D) using object oriented (O-O) concept Most popular O-O A/D model is Unified Modeling Language (UML)

UML UML provides a standard set of tools/diagrams to document the analysis and design of a software system It helps in effective communication between developer team and business persons on a project

UML History The software engineers worked independently to develop a O-O model –Grady Booch: Booth diagram –Ivan Jacobson : Jacobson diagram –James Rumbaugh: Rumbaugh diagram UML is developed in collaboration to unify their methods

Use case modeling and UML UML is fundamentally based on use case modeling Use case –Defines what a system does (i.e. system requirement) not how. –Divides system functionalities into behaviours that are important to user UML –Analyze use case & defines system objects and interactions

Use case: In Detail Use case model in consist of 2 elements: –Actor: role of user of the system –Use case: describes sequence of transactions in the system in response to an event

UML elements

Things Structure things –Class –Interface –Collaboration –Use case –Active class (controller) –component Behavioral things –Interaction –State machine –Annotation things Grouping things –Package Annotation things –Notes

Structure Thing: Class Defines common attributes & behavior of objects/things Rental Car Size Color Model Rentout() Checkin() Service()

Structure Thing: Interface The behavior of a class of a system that is noticeable from outside the class PC Serial port External device

Structure Thing: Collaboration Some classes collaborate to each other to do a common job Part1 Engine Several engine Parts works together to run The engine

Structure Thing: Use case Describes a series of actions that demonstrate behavior of the system and its interaction with action

Structure Thing: Active class Initiate and control independent activity server client

Structure Thing: Component Provides services and interfaces Example: COM, JAVA Bean, text box

Behavior things: Interaction Message sent between a set of objects within the system to perform a specific task drivercar message

Behavior things: State machine Series of states of an object customer After LoginBefore Login

Grouping things: Package Things can be groups into package

Annotation things: Notes Note about things