Object Oriented Design And Programing

Object Oriented Design (OOD)in software industry

Available at www.elfuchs.com

Emmanuel FUCHS

Why OOD ?

Design for changesProcedural Oriented Design (POD) VS Object Oriented Design (OOD)Procedural Oriented DesignObject Oriented DesignDesign Pattern

OOD in software industryDesign for changes

Sources of ChangeDesigning and programming in future tense

Procedural Oriented Design (POD) VS Object Oriented Design (OOD)Procedural Oriented Design

Design The Problem StatementConsequence of Problem Statement changeState and Procedure Dichotomy

Object Oriented DesignIntegrate State and ProcedureDesign A Solution StatementNo Consequence of Problem Statement change

GOF Design PatternFactoryState pattern

Changes Request : flexible solution

Productive programmerInitial Request

1 Day After

Unproductive programmer

1 Week After

Productive programmerEvolution

RequestInitial Request

1 Day After

1 Week After

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later

1 Day After

Productive programmer

Evolution Request

Initial Request

1 Day After

1 Week After

Few Weeks Later

1 Day After

Unproductive programmerEvolution

1 Day After

1 Week After

Few Weeks Later

Productive programmer

1 Day After

Changes Sources During Development

Requirements :Customers Discover What they Really Want During or at the End of Developments

TechnologyPerformances Are Increasing With Time

SkillWe Learn and Understand the Problem and We Discover the Right Solution on the Job

Short Term PoliticNo Comments

program in the future tense.

Initial Request

1 Day After

Present tenseprogramming Short term

Medium to long term1 Week After

Future tenseprogramming

program in the future tense.

Initial Request Evolution Request

1 Week After

Few Weeks Later

1 Day After

Present tenseprogramming

1 Day After

Future tenseprogramming

Object VS Procedural

ProceduralThe code solution “structure” is the problem “structure”.When problems “changes” the code structure changes.

ObjectThe solution is based on integration and collaboration of independent entities (component).An entity is a code subset.Integration and Collaboration are managed by tools (compiler).When the problems “changes” the collaboration scheme changes not entity’s code.

User Input

Operation:

A: Addition

B: Subtraction

C: Division

E: Multiplication

Enter a choice =>

User Input

Operation: Addition

A: First Integer

B: Second Integer

Enter a choice =>

Procedural Programming

Proc A1()

Proc a ()

CH = 1

Proc b ()

CH = 2

Proc c ()

CH = 3

CharacterInput CH

Proc A2() Proc A3()

Procedure A ()

CH = A

Proc d ()

CH = 1

Proc e ()

CH = 2

Proc f ()

CH = 3

CharacterInput CH

Procedure B ()

CH = B

Proc g ()

CH = 1

Proc h ()

CH = 2

CharacterInput CH

Procedure C()

CH = C

CharacterImput CH

Hierarchical Programming

Tapez un nom iciTapez un titre de fonction ici

User Input : Operation in R and C

Operation:

A: Real

B: Complex

Enter a choice =>

User Input

Operation: Complex Addition

A: First Number real part

B: First Number imaginary part

C: Second Number real part

D: Second Number imaginary part

Enter a choice =>

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later

1 Day After

Hierarchical, Structural Programming, “Top Down”

Reuse of Real operations for Complex Operations

Procedures

Spaghetti Plate

State and Procedure dichotomy

State Procedures

Spaghetti Plate

Object Paradigm

GOF definition for object: A run-time entity that packages both data and the procedures that operate on that data.

ObjectObject

OperationOperation

Attribute Interfaces

GoF stand for Gang of Four. It refers to the famous books of Vlisside and Co. Design Patterns: Elements of Reusable Object-Oriented Software.

Object Paradigm

GOF definition for object: A run-time entity that packages both data and the procedures that operate on that data.

UML class

ObjectObjectName

Attribute

OperationOperationOperationOperation

OperationOperation

Attribute InterfacesUML: Unified Modelling Language

Object analogy

A driver doesn't care of engine's internal working.He only knows the interface

Implementation Interface

Object analogy

Polymorphism

Interface

(specification) Implementation

(body)

Object Interface

UML class

Attribute

Object Interface

Client

Object Interface and Implementation

Attribute

UML class

Object Interface

Client

Interface Implementation

Object Interface and Implementation

Attribute

UML class

Object Interface

Client

Interface Implementation

Object collaboration

OOD hides the problem space

With OOD likely to change aspects are encapsulated and hidden to other objects.

How and What are separated

The problem : What

The solution : How

The problem is in the User Input

Colour

A: Black,B: Brown,C: Red, D: Orange,E: Yellow,F: Green, G: Blue,

Enter a colour =>

Replace case and enum by object .

enum Color {

Black,Brown,Red, Orange,Yellow,Green,Blue,

structural switch

static void printsColor(int Value) {

switch(Value) {

case Black : processing 1

case Brown:processing 2

case Red:processing 3

case Orange:processing 4

case Yellow:processing 5

case Green:processing 6

case Blue:processing 7

structural switch

static void flightUpdate(intstatus) {

switch(status) {

case NIL_EXIT_STATE: processing 1

case FLIGHT_ACTIVATION_PROPOSAL:processing 2

case FLIGHT_ACTIVATION_ALARM:processing 3

case FLIGHT_ACTIVATION_CONFIRMED:processing 4

case HANDOVER_TRANSFERED,processing 5

case COORDINATION_TERMINATED,processing 6

case UNKNOWN_EXIT_STATEprocessing 7

static void flightUpdate(int status) {

switch(status) {

case NIL_EXIT_STATE : processing 1

switch(status) {

} } Software

Module BSoftwareModule A Software

Module D

switch(status) {

SoftwareModule C

SoftwareModule E

The problem space and the solution space.

If the switch value reflects the problem for example user inputs.

When the user request new case you have to change everywhere you use the switch value.

Example 3: The problem is in the User Input

Colour

A: Black,B: Brown,C: Red, D: Orange,E: Yellow,F: Green, G: Blue,H: NewColor,

Enter a colour =>

Replace case and enum by object .

enum Color {

Black,Brown,Red, Orange,Yellow,Green,Blue,NewColor,

structural switchstatic void printsColor(int Value) {

switch(Value) {

case Black : processing 1

case Brown:processing 2

case Red:processing 3

case Orange:processing 4

case Yellow:processing 5

case Green:processing 6

case Blue:processing 7

case NewColor,processing 7

structural switch

switch(status) {

SoftwareModule A

SoftwareModule B

SoftwareModule C

SoftwareModule D

SoftwareModule E

Changes

structural switch

switch(status) {

SoftwareModule A

SoftwareModule B

SoftwareModule C

SoftwareModule D

SoftwareModule ESpaghetti Plate

Changes

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later ?

1 Day After

The object solution

Polymorphism

Print()Color

+print()

Client

Polymorphism

+print()

No Changes

Print()Client

+ print()

Polymorphism

+print()

+ print()

No Changes

Print()Client

+ print()

Polymorphism

+print()

+ print()

No Changes

Print()Client

+ print()

Polymorphism

+print()

+ print()

No Changes

Print()Client

+ print()

newColor

+ print()

Object Polymorphism

Code example

Polymorphism

Print()Color

+print()

Client

Polymorphism

+print()

Print()Client

+ print()

Code of the Black object print() operation

class Black extends Color

public void print()

System.out.println( " Black "); }

Polymorphism

+print()

+ print()

Print()Client

+ print()

Code of the Brown object print() operation

class Brown extends Color

public void print()

System.out.println( " Brown "); }

Polymorphism

+print()

+ print()

Print()Client

+ print()

Code of the Red object print() operation

class Red extends Color

public void print()

System.out.println( " Red "); }

Code of the Blue object print() operation

class Blue extends Color

public void print()

System.out.println( " Blue "); }

Polymorphism

+print()

+ print()

Print()Client

+ print()

Polymorphism

+print()

+ print()

No Changes

Print()Client

+ print()

newColor

+ print()

Code of the Blue object print() operation

class NewColor extends Color

public void print()

System.out.println( " NewColor "); }

GoF stand for Gang of Four. It refers to the pattern seminal book of John Vlissides, Erich Gamma, Richard Helm, Ralph Johnson:

Title: Design Patterns: Elements of Reusable Object-Oriented Software.

GOF: The book cover

Design Pattern GOF Definition

A design pattern systematically names, motivates, and explains ageneral design that addresses a recurring design problem inobject-oriented systems. It describes the problem, the solution, when to apply the solution, and its consequences. It also gives implementation hints and examples. The solution is a general arrangement of objects and classes that solve the problem. The solution is customized and implemented to solve the problem in a particular context.

Why Design Pattern ?

Because we want to use polymorphism to manage the changesBut it is very difficult to find the object class lattice which leads to polymorphismDesign pattern Language is a catalogue of object class lattices which handle a certain problem with polymorphism.

What to Expect from Design Patterns

A Common Design VocabularyA Documentation and Learning AidAn Adjunct to Existing MethodsA Target for Refactoring

Anti pattern are also useful.

Design Pattern Catalogue

Creational PatternsAbstract Factory Builder Factory Method Prototype Singleton

Structural PatternsAdapter Bridge Composite Decorator Facade Flyweight Proxy

Behavioral PatternsChain of Responsibility Command Interpreter Memento Iterator Mediator Observer State Strategy Template Method Visitor

Design Pattern Map

What to Expect from Design Patterns

A Common Design VocabularyA Documentation and Learning AidAn Adjunct to Existing MethodsA Target for Refactoring

Anti pattern are also useful.

The GOF Abstract Factory Design Pattern

*GoF stand for Gang of Four. It refers to the famous books of John Vlissides, Erich Gamma, Richard Helm, Ralph Johnson. Design Patterns: Elements of Reusable Object-Oriented Software.

Factory Pattern

+print()

Print()

+ print()

UNKNOWN_EXIT_STATE

+ print()

ColorFactory

+ create()

Client

+ print()

Factory Pattern

The switch is now hidden in the object state factory.

The factory returns a new object of the right derived class by using a switch case on the state integer code.

The client always sees the root class object type Color.

Each state object know how to manage client invocation in its case.

Factory pseudo code

static color create(int Color) {

switch(Color) {

case Black : return color = new black();break;

case Brown:return color = new brown();break;

case Red:return color = new red();break;

case Orange : return color = new Orange();break;

case Yellow: return color = new Yellow();break;

case Green : return color = new Green();break;

case Blue : return color = new Blue();

New Object

Dynamic Polymorphism

Static polymorphism (Factory)State machine

Pattern State creates one object for each state and uses polymorphism to enable transparent client invocation.

Dynamic Polymorphism

State Pattern (from the GoF)

State model transformation

ColorRequest()

Client

State diagram

Request()

Black OrangeRequest()

Request()

Request()Red

structural switch

static void printsState(int state) {

switch(state) {

case Black :

System.out.println( “Black"); break;

case Brown :

System.out.println( “Brown"); break;

case Red :

System.out.println( “Red"); break;

case Orange :

System.out.println( “Orange"); break;

structural switch

static void printsState(int state) {

switch(state) {

case Black :

System.out.println( “Black"); break;

case Brown :

System.out.println( “Brown"); break;

case Red :

System.out.println( “Red"); break;

case Orange :

System.out.println( “Orange"); break;

Spaghetti Plate

ColorRequest()

Client

ContextRequest()

Client

HelloContextRequest()

OrangeHandle()

ColorHandle()

BrownHandle()

Client

BlackHandle()

HelloContextRequest()

OrangeHandle()

BlackHandle()

ColorHandle()

BrownHandle()

Context

Concrete state

Client

Polymorphism and state patterns

If we have an object which state can change during its lifetime and we have to perform different operations according to the object state we use the pattern state.

pattern State avoids switch even if the state of the object is changing

pattern State creates one object for each state and uses polymorphism to enable transparent client invocation.

Objective

State pattern avoid structural switchNo enumeration in Java

An enumeration may be managed as a state machine.

Next step

Model Driven DevelopmentCode generation

Second order polynomial

The problem1° requirements change2° requirements changeProcedural solutionInitial requirements1° requirements change2° requirements changeObject SolutionPolynomial FactoryInitial requirements1° requirements change2° requirements change

Object Oriented Design (OOD)in software industry

The second order polynomial example

Emmanuel FUCHS

Second order polynomial equation

02 =++ cbxax

Second order polynomial equation roots:

aacbbx

242 −±−

Second order polynomial discriminant :

acb 42 −=∆

First iteration : find roots in R

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later

1 Day After

Second iteration : find roots in C

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later

1 Day After

Third iteration : Checks Roots Interval

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later ?

1 Day After

Procedural solutionStart

Input coefficients a,b,c

Computes discriminantDelta = b * b – 4 * a * c

Computes single root

< 0> 0 DiscriminantSign

Computes roots

print roots print root print no roots

Source code

delta = (b*b) - (4*a*c); // discrimant computation

if (delta < 0.0) { System.out.println (" No roots");

else if (delta > 0.0) { System.out.println (" Two roots :"); System.out.println (" x1 = " + (-b + Math.sqrt(delta))/ (2.0 * a)); System.out.println (" x2 = " + (-b - Math.sqrt(delta))/ (2.0 * a));

else { System.out.println (“ Single root: "); System.out.println (" x = " + (-b / (2.0 * a)));

Procedural solutionStart

Computes single root

< 0> 0 DiscriminantSign

Computes roots

print roots print root print no roots

Procedural solution Complex roots

DiscriminantSign

Computes double rootComputes roots

print roots print root print roots

Computes Complex roots

Source code

Source code first modification

System.out.println (" Complex roots"); System.out.println (" x1 real part = " + (-b / (2.0*a))); System.out.println (" x2 imaginary part = " + (-b - Math.sqrt(-delta))/ (2.0*a)+ "i"); System.out.println (" x2 real part = " + (-b / (2.0*a))); System.out.println (" x2 imaginary part= " + (-b - Math.sqrt(-delta))/ (2.0*a)+ "i");

Functional evolution : Checks Roots Interval

Checks Roots Interval : procedural solution

< 0> 0

( /X1/ <= X & X <= /X2/ )

Return True Return False

DiscriminatSign

= 0Computes root case 1 Computes roots case 2 2

TX == X1

Return True Return False Return False

Initial Request

1 Day After

1 Week After

1 Day After

1 Week After

Few Weeks Later ?

1 Day After

Source Code

static boolean isInBetweenRoots(double x,double a,double b, double c) {

double delta, x1, x2; delta = (b*b) - (4*a*c);

if (delta < 0.0)

return false;

else if (delta > 0.0) {

System.out.print("delta > 0"); x1 = (-b + Math.sqrt(delta))/ (2.0*a); x2 = (-b - Math.sqrt(delta))/ (2.0*a); return (Math.abs(x1) <= Math.abs(x)) && (Math.abs(x) <= Math.abs(x2));

else { x1 = -b / (2.0 * a); return (x == x1);

First Object Model : Domain Model

Second OrderPolynomial

Single RootSecond Order

Polynomial

Two RootsSecond Order

Polynomial

No RootSecond Order

Polynomial

First Object Model : Domain Model

Second OrderPolynomial Discriminant

Polynomial

No RootSecond Order

Polynomial

First Design Model with operation

computeRoots()

Double aDouble bDouble c

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Design Model Creation without Factory

computeRoots()create()

PolynomialcomputeRoots()

No RootSecond Order

Domain Model

Discriminant

Domain Model: Polynomial FactorySecond Order

Polynomial

Factory

Discriminant

create

Domain Model: Polynomial FactorySecond Order

Polynomial

Factory

Discriminant

First Design Model with operation

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Discriminant

class Discriminant {

private double delta;

public Discriminant (double a, double b, double c) {

delta = (b * b) - (4.0 * a * c);

public double value () {

return delta; }

Factory: Initial Requirements

static Polynome create( double a, double b, double c) {

Discriminant theDiscriminant = new Discriminant(a,b,c); double delta = theDiscriminant.value();Polynome polynome;

if (delta == 0.0) {

return polynome = new SingleRootPolynome(a,b,c,theDiscriminant) ; } else if (delta > 0.0) {

return polynome = new TwoRootsPolynome(a,b,c,theDiscriminant) ; } else {

return polynome = new NoRootPolynome(a,b,c,theDiscriminant); }

Factory 1° Requirements Change

static Polynome create( double a, double b, double c) {

Discriminant theDiscriminant = new Discriminant(a,b,c); double delta = theDiscriminant.value(); Polynome polynome;

if (delta == 0.0) {

return polynome = new SingleRootPolynome(a,b,c,theDiscriminant) ; } else if (delta > 0.0) {

return polynome = new TwoRootsPolynome(a,b,c,theDiscriminant) ; } else {

return polynome = new ComplexRootsPolynome(a,b,c,theDiscriminant); }

Design Model with operation

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Computes root : Single Root Polynomial

void computesRoots() {

System.out.println (" Single root: ");

System.out.println (" x = " + (-b / (2.0*a)));

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Computes root : Two Roots Polynomial

System.out.println (" Two roots :");

System.out.println (" x1 = " + (-b + Math.sqrt(discriminant.value()))/ (2.0*a));

System.out.println (" x2 = " + (-b - Math.sqrt(discriminant.value()))/ (2.0*a));

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Computes root : No Root Polynomial

System.out.println (" No roots");

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

No RootSecond Order

Polynomial

computeRoots()

Discriminant

Polynomial

computeRoots()

Polynomial

computeRoots()

Complex RootsSecond Order

Polynomial

computeRoots()

Computes root : Complex Roots Polynomial

System.out.println (" Complex roots");

System.out.println (" x1 real part = " + (-b / (2.0*a)));

System.out.println (" x1 imaginary part = “

+ (-b + Math.sqrt(-discriminant.value()))/ (2.0*a)+ "i");

System.out.println (" x2 real part = " + (-b / (2.0*a)));

System.out.println (" x2 imaginary part = “

+ (-b - Math.sqrt(-discriminant.value()))/ (2.0*a)+ "i");

Design Model

computeRoots()isInBetweenRoots()

isInBetweenRoots()

No RootSecond Order

isInBetweenRoots()

Bracket the parameter : single root

boolean isInBetweenRoots(double x) {

return (x == x1);

Design Model

isInBetweenRoots()

No RootSecond Order

isInBetweenRoots()

Bracket the parameter : Two roots

return (Math.abs(x1) <= Math.abs(x)) && (Math.abs(x) <= Math.abs(x2));

Design Model

isInBetweenRoots()

No RootSecond Order

isInBetweenRoots()

Bracket the parameter : no roots

return false;

That’s it !!!

Thank You For Your Attention

Questions are welcomeContacts :

emmanuel.fuchs@elfuchs.com

www.elfuchs.com

Object Oriented Design And Programing

Technology

Transcript of Object Oriented Design And Programing

The Object-Oriented Paradigmkena/classes/5448/f12/lectures/02-oo... · The Object-Oriented Paradigm ... • Discuss important concepts of object-oriented programming ... • Object-Oriented

Object Oriented Programming and Object Oriented Design

Object Oriented Analysis & Design. Outline Object Oriented Concepts and principals Object Oriented Analysis Object Oriented Design.

CSE 1201 Object Oriented Programming Object Oriented Design.

mysarkarinaukri.com€¦ · Unit 4: Programming and Object Oriented Programming Object Oriented Paradigm: Structured vs object oriented development, elements of object oriented programming,

object oriented programing lecture 1

Object-oriented Modeling of Object Oriented Concepts

Object-Oriented Databases Object Oriented Databases - ODBMS.org

Object Oriented Software Design - I - Object Oriented Design

Object-oriented Programming with PHP · Object-oriented Programming with PHP [2 ] Object-oriented programming Object-oriented programming is a popular programming paradigm where concepts

Object-Oriented Analysis (OOA) Object-Oriented Analysisdigital.cs.usu.edu/~xqi/Teaching/CS2450F08/Notes/Ch12.OOA.pdf · 1 1 Object-Oriented Analysis Xiaojun Qi 2 Object-Oriented Analysis

Developing Object-Oriented PHP. PHP-Object Oriented Programming2 Object-Oriented Programming Object-oriented programming (OOP) refers to the creation.

Object-Oriented Programing in Java

12. Object-oriented Design - Aalborg Universitetkom.aau.dk/~dimon/old-control/teaching/Object-oriented-design.pdf · 2 Object-oriented Design ©Ian Sommerville 2000 Object-oriented

Module 3 Object Oriented Data Models Object Oriented notations

Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week04.

THE PIPE - WJCSpipedesign.co.kr/Foxpro_pdf/WJCS.pdf · 2008-01-18 · WJCS PROGRAMING TOOL WJCS(Welding Joint Control System)은 객체지향 프로그래밍(OOP, Object Oriented

Principles of object oriented programing

Modul Praktikum - stiki-indonesia.ac.idstiki-indonesia.ac.id/wp-content/uploads/2019/03/modul/MODUL_TI/Modul... · Modul Praktikum Object Oriented Programing Java 6 Gambar 1.3 Create

ASPECT ORIENTED PROGRAMING(aop)