Object-oriented analysis & design

Slides:



Advertisements
Similar presentations
7M701 1 Information Systems Modelling and Design with.
Advertisements

Unit 1: Java and Eclipse UML. Depending on the source, the acronym UML is said to stand for “unified modeling language” or “universal modeling language”.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Chap 1 UML vs Thinking in Objects! – Visual modeling Learning UML – Look at the book examples – Alan Holub’s UML reference card – Use library resources.
Chapter 1 Object Oriented Analysis and Design. UML, Patterns, and Object-Oriented Analysis and Design  The essential skills for the creation of well-designed,
Dictionary Illustration. The art of RECYCLING! Using everyday objects to create art Using everyday objects to create art What makes it art? What makes.
Unified Modeling Language
Object Oriented Analysis and Design
Domain model: visualizing concepts
Object Oriented Analysis and Design Chapter 1 Applying UML and Patterns -Craig Larman.
Introduction To System Analysis and design
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Introduction To System Analysis and Design
Object-Oriented Analysis and Design An Introduction.
An Introduction to Java Chapter 11 Object-Oriented Application Development: Part I.
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
Object-Oriented Analysis and Design Fall 2009.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
Copyright © Craig Larman All Rights Reserved The Domain Model.
An Introduction to the Unified Modeling Language
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
Design Model Lecture p6 T120B pavasario sem.
Introduction to OOAD and the UML
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
CS-112 Object Oriented Concepts Course Syllabus. Outline  Instructor and Prerequisites  What this course is  Learning outcomes  Degree program outcomes.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN Objectives Describe the book goals and scope Define OOA/D (Object-Oriented Analysis and Design) Illustrate.
Software Design. A well-known phenomenon You will learn…. –Thinking "object oriented“ –Define requirements and analyze the problem domain. –Design of.
Chapters 10, 11 SSD (Revision) SD DCD Exam Object-Oriented Design.
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
Introduction TH166 – Theories of Play Production Summer 2010 Lesson #2 – Script Analysis Introduction and Chapter 1 – The First Reading.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Copyright © 2012 Pearson Education, Inc. Chapter 13: Introduction to Classes.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
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.
Introduction to OOAD and UML
1 Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.
Chapter 0: Introduction
Sachin Malhotra Saurabh Choudhary
Object-Oriented Analysis and Design
Object-Oriented Techniques
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 5: Object Oriented Analysis and Design
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
Object-Oriented Modeling and Design
Objectives State the reasons for the complexity involved in the development of software Define the following terms Objects Classes Messages Methods Explain.
Introduction to UML Tutorial 1.
Business System Development
The Complete Guide to UML Diagram Types with Examples in Simple Words
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
Model-View-Controller
Chap 1 UML vs Thinking in Objects! Learning UML Visual modeling
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
SYS466 Domain Classes – Part 1.
Object Oriented Analysis and Design
2D1359 & 2D1360 : Object Oriented Modeling, Programming & Analysis
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
2.1 Introduction to Object-Oriented Programming
Appendix A Object-Oriented Analysis and Design
Appendix 3 Object-Oriented Analysis and Design
CSCI 360: Software Architecture & Design
Presentation transcript:

Object-oriented analysis & design 1. Introduction Object-oriented analysis & design

Objectives Compare analysis versus design Define object-oriented analysis & design Illustrate with a brief example

Applying UML & Patterns in OOA/D An object system design is good when it: Each object’s function is clear Object interactions are clear Functions correctly Is easy to modify (simple as possible?) Performs well.

Applying UML & Patterns in OOA/D UML stands for Unified Modeling Language. UML is only a notation used to: Explore an object design space Express/communicate a design

Applying UML & Patterns in OOA/D Assigning responsibilities to objects is fundamental to design. Such assignments benefit from principles & heuristics. The principles & heuristics depend on the object domain. Do the principles of assigning responsibilities to software objects apply to meatware objects? Should you use these principles to assign responsibilities to team members?

What Is Analysis & Design A resolution of anything, whether an object of the senses or of the intellect, into its constituent or original elements; an examination of the component parts of a subject, each separately, as the words which compose a sentence, the tones of a tune, or the simple propositions which enter into an argument. Synthesis Composition, or the putting of 2 or more things together, as in compounding medicines.

What Is Analysis & Design To draw preliminary outline or main features of; to sketch for a pattern or model; to delineate; to trace out; to draw. To create or produce, as a work of art; to form a plan or scheme of; to form in idea; to invent; to project; to lay out in the mind; as, a man designs an essay, a poem, a statue, or a cathedral.

What is Object-Oriented Analysis OOA A resolution of a system into its constituent objects or concepts. OOD To invent a model delineating the key objects of a system that satisfies a set of requirements.

What is Object-Oriented Analysis A key object or concept has representations Domain concept Visualization of concept Programming language representation Book title public class book { private String title; public Chapter getChapter(); }

What is Object-Oriented Analysis Object/concept representations Domain concept Visualization of concept Programming language representation Book title public class book { private String title; public Chapter getChapter(); }

An Example Mandelbrot Set Visualizer Define use cases 1. Visualize Mandelbrot Set: User selects a region to visualize. User sets visualization parameters. System displays selected region accordingly.

An Example Define a domain model MandelbrotSet region notifies Visualizer sets Region, parameters Controller Domain model indicates key concepts, associations, & attributes.

An Example Define Interaction Diagrams :Controller MandelbrotSet Visualizer setRegion() setRegion( Region) notify()

An Example Define Class Diagrams Visualizer Controller MandelbrotSet region: Region viewer: Viewer setRegion() setIterationLimit() Visualizer set: MandelBrotSet notify() Controller set: MandelBrotSet setRegion()