ASSIGNMENT#1

OBJECT ORIENTED ANALYSIS & DESIGN

Roll Number: BSEM-F17-175

Submitted to: Sir Saleem Zubair
 ➢ Overlapping and incomplete Subclasses:
This variation is the default in both UML and in concept modeling. In this variation, an instance can be a
member of the superclass and / or any number of subclasses. In this sense, the classification of instances
is “incomplete”—sometimes there is a specific subclass, and sometimes there is not.

For example, the diagram below shows four instances. One is an instance of “Manufacturer”, one is an
instance of “Windshield Manufacturer”, one is an instance of “Car Manufacturer”, and one is an instance
of both “Windshield Manufacturer” and “Car Manufacturer”.

In both standard UML and in concept modeling, incomplete and overlapping subclasses are shown
with either no notation, or with the notation {incomplete, overlapping} near the generalization arrow.
 ➢ Disjoint and Complete Subclasses:
This variation means that an instance can only be classified by one of the subclasses. The instance cannot
be classified as only the superclass, and it cannot be classified by two subclasses at the same time.

For example, in the subsequent diagram, two instances are shown. One is an instance of “Windshield
Manufacturer”, and one is an instance of “Car Manufacturer”. There can be no instance of “Manufacturer”
that is not also an instance of one of the subclasses, and there can be no instance that is classified as both
a “Windshield Manufacturer” and a “Car Manufacturer” at the same time.

The diagram below shows an example of disjoint and complete subclasses in standard UML notation. The
diagram shows that “Steering Wheel Manufacturer”, “Car Manufacturer”, and “Windshield
Manufacturer” are all subclasses of “Manufacturer”. In addition, the standard UML {complete, disjoint}
notation declares that the subclasses are complete and disjoint.