The OOD Process Design as a Logical Continuation of Analysis.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Advertisements

Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
Chapter 7 – Object-Oriented Design
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
The Problem Domain Component (PDC) [Coad/Yourdon]
Chapter 1 Object Oriented Analysis and Design. UML, Patterns, and Object-Oriented Analysis and Design  The essential skills for the creation of well-designed,
Chapter 1 Object-Oriented System Development
Introduction To System Analysis and Design
The OOD Process - III The Data Management Component (DMC) [Coad/Yourdon]
7M701 1 Software Engineering Object-oriented Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 12 )
Component-Level Design
1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.
The OOD Process - II The Human Interaction Component (HIC) [Coad/Yourdon]
Object Oriented Design OOD. OOD characteristics - I conceptual compatibility with OOA notational consistency with OOA clean traceability of OOA results.
Object Oriented Analysis OOA. OOA Deliverables Static Object model –one single diagram Scenarios –set of diagrams Object Dictionary –one set of comprehensive.
Software Engineering I Object-Oriented Design
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
The Task Management Component (TMC) [Coad/Yourdon]
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
1 Object-Oriented Software Engineering CIS 375 Bruce R. Maxim UM-Dearborn.
Object-Oriented Analysis and Design
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.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
Introduction To System Analysis and Design
Chapter 7 IS630. Project Design  Technical Design & Specification Network and System Architecture & Design Software System Architecture & Design  Database.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Systems Analysis and Design in a Changing World, 3rd Edition
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
© 2005 Prentice Hall9-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Lecture 1: Introduction to Software Engineering WXGE6103 Software Engineering Process and Practice Object-oriented Design.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
ARCHITECTURAL DESIGN. Why is Architecture Important? Representations of software architecture are an enabler for communication between all parties (stakeholders)
CS 8532: Advanced Software Engineering Dr. Hisham Haddad Overview of Object-Oriented Design Highlights of OOD Concepts, Components, and Process.
Software Engineering Zhang Shuang
Dale Roberts Object Oriented Programming using Java - Introduction Dale Roberts, Lecturer Computer Science, IUPUI Department.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
Introduction to OOAD and the UML
Advanced Object-Oriented Design Patterns and Architectures Part One COEN396A John Xiao
UML (Unified Modeling Language)
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
Object-Oriented Systems. Goals Object-Oriented Methodologies – The Rumbaugh et al. OMT – The Booch methodology – Jacobson's methodologies.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
07 - OODCSC4071 OOA/OOD/OOP Example example OODCSC4072 Requirements See eg/req.htmleg/req.html Want a program to help a software company plan new.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Unit - 3 OBJECT ORIENTED DESIGN PROCESS AND AXIOMS
Instructor: Dr. Hany H. Ammar
UNIT 1.
Chapter 7 – Object-Oriented Design
SSA(D) vs OOAD M. Pickard CSC 513.
The Object Oriented Approach to Design
Object-Oriented Design
Unified Modeling Language
Object-Oriented Design
Object oriented analysis and design
OBJECT ORIENTED ANALYSIS AND DESIGN
The OOA OBJECT DICTIONARY
Chapter 22 Object-Oriented Systems Analysis and Design and UML
From Use Cases to Implementation
Presentation transcript:

The OOD Process Design as a Logical Continuation of Analysis

Object-Oriented Design “Steps” of the Process? OOD OOA Model OOD Model OOA Process

The Levels of the OOD Process - High-Level Design (1) extend the OOA Model [Coad/Yourdon] –think in terms of OO model components –OOA results are the basic component problem domain component –include other components in the model include human interface (HIC) task management (TMC) data management (DMC) ==> acknowledge that we develop a computer- based system around/with the analysis results

The Levels of the OOD Process - High-Level Design (2) structure your approach decide on a general system architecture –organize the objects into a well specified system structures –organize and extend scenarios according to generally applicable patterns –reuse existing patterns generic templates generic architectures and frameworks

The Levels of the OOD Process - Detailed Design refine and map the OOA Model to the infrastructure –detailed algorithms and datastructures –implementation of OO structures –implementation of states and transitions –optimization –maximize reuse –exception handling –etc.

The OO Co-Design Process Matrix of Domain Components and Levels TMCHICPDCDMC high-level Design detailed Design Miniworld extend refine & map

Object Oriented Design means to navigate the domain/level matrix with the purpose to develop all model components on both levels in a meaningful sequence.

OOD Deliverables - I extended Static Objectmodel –Coad & Yourdon: Problem Domain Component (PDC) Human Interaction Component (HIC) Task Management Component (TMC) Data Management Component (DMC) on the level of high-level design basically “another analysis step” on the level of detailed design connect to existing class hierarchy,...

OOD Deliverables - II completed & extended Scenarios –extend old scenarios accross domains reflect the chosen architecture’s dynamics build links between domain components –add new scenarios to accomodate internal organisation e.g. data backup, rollback, load/save on the level of high-level design extended and new scenario diagrams (& dictionary) on the level of detailed design complete all details in dictionary diagrams only if necessary (optimization,...)

Scenarios TMCHICPDCDMC high-level Design detailed Design extend refine & map

OOD Deliverables - III Object Dictionary –document & specify the added domain components very much like during analysis: objects, structures,... ==> for high-level design –map and refine existing specifications translate structures, STDs,... map to existing patterns and objects document optimizations ==> for detailed design

As in OOA it holds for OOD: Static Model and Scenarios are documented as graphical Views of the more complete Object Dictionary.

The complete OOAD Specification The “schoolbook scenario” TMCHICPDCDMC high-level Design detailed Design Miniworld Dictionary Scenarios Static Model Dictionary Scenarios Static Model