Introduction to OOAD
Introduction to OOAD
Introduction to OOAD with OO Basics - Unified Process – UML diagrams – Use Case –Case study – the
Next Gen POS system, Inception -Use case Modelling – Relating Use cases – include, extend and
generalization – When to use Use-cases
Class:
A class is a user defined blueprint or prototype from which objects are created.
It represents the set of properties or methods that are common to all objects of one type.
Encapsulation:
Encapsulation is the process of binding both attributes and methods together within a class.
Through encapsulation, the internal details of a class can be hidden from outside.
Polymorphism:
Polymorphism is originally a Greek word that means the ability to take multiple forms.
Inheritance:
Inheritance is the mechanism that permits new classes to be created out of existing classes by extending
and refining its capabilities. The existing classes are called the base classes/parent classes/super-classes,
and the new classes are called the derived classes/child classes/subclasses.
Types of Inheritance:
Association
The relationship between child and parent class is represented in aggregation relationship where
in child can exist independently of the parent.
It is weak association.
Composition:
The relationship between child and parent class is represented in composition relationship where
in child cannot exist independently of the parent.
It is strong association.
Generalization:
In the generalization process, the common characteristics of classes are combined to form a class
in a higher level of hierarchy, i.e., subclasses are combined to form a generalized super- class.
It represents an “is – a – kind – of” relationship.
Specialization: