Skip to main content

Object Oriented Design: Relationship Types

Inheritance

Inheritance relationship defines a parent child relationship in which child is said to be type of parent. Child inherits common actions and attributes from parent. Inheritance relationship allows rich abstractions to reduce code repetition and to increase code reuse.
Consider the Passenger and StudentPassenger objects. StudentPassenger object is of type Passenger. StudentPassenger inherits all actions and attributes of Passenger. Additionally a StudentPassenger has a pass card and pays less than a normal Passenger. It is phrased as StudentPassenger is a Passenger.

Association

Association is a relationship in which one object uses another object to achieve some task. They don’t own each other and  their lifecycle is independent of each other.  
Consider the relationship between bus and bus station. They don’t own each other and they exists regardless of each other. It is phrased as Bus uses a Bus Stop to pick passengers.

Aggregation

Aggregation is like association, lifecycle of objects does not depend on each other. But unlike association, in aggregation relationship one object owns the other.
Consider the relationship between passenger and bus. A Bus and a passenger exist independent of each other but a passenger may belong to a bus. It is phrased as Bus has a passenger.

Composition

Composition relationship means that lifecycle of objects depend each other and one side of relationship is owned by other side.
Consider the relationship between a bus and engine. Lifecycle of bus and engine strongly depends on each other and engine belongs to bus. It is phrased as Bus owns an Engine.

Over All Picture

Diagram 1 depicts UML diagram of the related objects.


Below is the example code listing for defined relationships.

class Bus{
 Engine engine;
 List<Passenger> passengers;
 
 Bus(){
  // Bus owns an engine and engine's lifecycle depends on Bus object
  engine = new Engine();
 }
 
 void pickPassengers(BusStop busStop){}
}

class BusStop{
 List<Passenger> passengers;
 
 List<Passenger> getPassengers(){};
 void addPassenger(Passenger passenger){};
}

class Passenger{
 double payFee(){}
}
class StudentPassenger{
 Pass pass;
 double payFee(){}//overridden to pay less
}

class Pass{}
class Engine{}

class Main{
 
 public static void main(String[] args){
  
  Bus bus = new Bus();// not owned by BusStop, lifecycle does not depend on BusStop
  BusStop busStop = new BusStop();// not owned by Bus, lifecycle does not depend on Bus
  
  Passenger passenger1 = new Passenger();// lifecycle does not depend on BusStop or Bus
  Passenger passenger2 = new StudentPassenger(); // lifecycle does not depend on BusStop or Bus
  // StudentPassenger is also a passenger.
  
  busStop.addPassenger(passenger1); // busStop has a passenger
  busStop.addPassenger(passenger2); // busStop has a passenger
  
  bus.pickPassengers(busStop); // bus uses bus stop to pick passengers 
  // now Bus has passengers
  
 }
 
}

Comments

Popular posts from this blog

Obfuscating Spring Boot Projects Using Maven Proguard Plugin

Introduction Obfuscation is the act of reorganizing bytecode such that it becomes hard to decompile. Many developers rely on obfuscation to save their sensitive code from undesired eyes. Publishing jars without obfuscation may hinder competitiveness because rivals may take advantage of easily decompilable nature of java binaries. Objective Spring Boot applications make use of public interfaces, annotations which makes applications harder to obfuscate. Additionally, maven Spring Boot plugin creates a fat jar which contains all dependent jars. It is not viable to obfuscate the whole fat jar. Thus obfuscating Spring Boot applications is different than obfuscating regular java applications and requires a suitable strategy. Audience Those who use Spring Boot and Maven and wish to obfuscate their application using Proguard are the target audience for this article. Sample Application As the sample application, I will use elastic search synch application from my G...

Hadoop Installation Document - Standalone Mode

This document shows my experience on following apache document titled “Hadoop:Setting up a Single Node Cluster”[1] which is for Hadoop version 3.0.0-Alpha2 [2]. A. Prepare the guest environment Install VirtualBox. Create a virtual 64 bit Linux machine. Name it “ubuntul_hadoop_master”. Give it 500MB memory. Create a VMDK disc which is dynamically allocated up to 30GB. In network settings in first tab you should see Adapter 1 enabled and attached to “NAT”. In second table enable adapter 2 and attach to “Host Only Adaptor”. First adapter is required for internet connection. Second one is required for letting outside connect to a guest service. In storage settings, attach a Linux iso file to IDE channel. Use any distribution you like. Because of small installation size, I choose minimal Ubuntu iso [1]. In package selection menu, I only left standard packages selected.  Login to system.  Setup JDK. $ sudo apt-get install openjdk-8-jdk Install ssh and pdsh, if...

Java Thread States

Java Threads may have 6 states: new , runnable , terminated , blocked , waiting , timed_waiting . When a thread is created it is in new state. When start method of thread is called it enters runnable state. Runnable state has two inner states: ready and running . If thread is eligible for execution it is said to be ready, if it is executing it is in running state. Remember calling start method on a already started thread will raise IllegalThreadStateException. When thread finishes its execution it enters into terminated state. When a thread is trying to access a resource, a synchronized statement for example, and it is not available, lock of the object is already acquired for example, it is blocked and said to be in blocked state. When lock is released an thread has chance to acquire lock it goes back to runnable state. When a thread calls join or wait method it enters into waiting state. When joined thread finishes or for wait method notify/notifyAll metho...