In NDBMS, all the associations are binary with cardinality ratio 1:m and represented by the set type (not a
mathematical set and also called as named set type) that connects two different record types that are associated. We
use set type in place of named set type whenever there is no confusion. Thus an association is implemented directly
as set type that implements one: many association in which record type corresponding to the class on cardinality one
is represented by the owner and record type corresponding to the class on cardinality many is represented as member
of the set type. In the input class diagram the association is represented by a connecting line & normally name is not
assigned. The name of the set type will be generated by the concatenation of first three letters of the owner name and
last three letters of member name. Thus at the semantic level 1: m association is mapped to set type directly with its
participating owner & member along with other constraints18. These mapping provides the host program the way
how to store the object in the database and to read/write the record objects from the database. The following table
(Table 1) summarizes the mapping techniques used in this paper.