3.

0– DESIGN DATA MODEL FOR THE SYSTEM

3.1 ENTITY RELATIONSHIP DIAGRM

Figure 13
3.1.1 ASSUMPTIONS OF THE ER DIAGRAM

• The department got as an entity by me. And there are

attributes named, DID (Department ID) and Dname
(Department Name). And also mentioned DID as primary key
because it is unique for each and every department.

• There are three categories of staff member such as executive,

secretary and meeting organizer. Each and every staff member
have attributes such as ENO, Gender, Age, Adress, Name and
contact. Marked name and adress as composite attribute due to
it consist No, Street & city in adress and Fname & Lname in
name. Also marked age as derived because it change every day.
As well as mentioned Contact number as multivalued because
there should have several numbers. And also mentioned ENO as
primary key

• In here, staff member mentioned as disjoint because

sometimes each member may be subclass of specialization. So it
should be executive, meeting organizer and secretary. ENO is
the unique for each entity. Qualitification, Experience and
Typing speed are the attributes for the specialization entities in
order.

• The executive has personal calendar, behave as an entity.

PCNO and planned vacation are its attributes and mentioned
PCNO as primary key.

• Secretary responsible and meeting organizer book a

conference hall act as entity for the meeting. Each conference
hall has CNO, Capacity and Stime (start time). CNO is
mentioned as primary key.

• Meeting organizer organize and secretary participate for the

Meeting, act as entity. MID, Day, Participant, Stime (start time),
 Etime (end time) are the attributes of Meeting. MID is
mentioned as primary key.

• Each and every personal calendar has an Entry. There are

attributes named, EID, Stime (start time), Etime (end time),
date, description, and venue. EID is mentioned as primary key.

• The conference room has room calendar which has attributes

RCNO, duration, and status. Here the attribute of status marked
as composite attribute because status can divided to available
status and unavailable status.
.

3.2 RELATIOANL SCHEMA FOR THE ER DIAGRM

STEP 01 – Mapping Strong Entities

Department (DID, Dname)

Employee (ENO, Fname, Lname, No, Street, City, Gender, Contact)

Conference_Room (CNO, Capacity, Facility)

Meeting (MID, Day, Participant, Stime, Etime)

Personal_Calender (PCNO, Planned_Vacation)

Entry (EID, Date, Description, Venue, Stime, Etime)

Room_Calender (RCNO, Duration, Available_Satatus, Unavailable_Sataus)

STEP 02 – Mapping Weak Entities

STEP 03 – Mapping Binary Relationships

I. Mapping 1:1 Relationships

Personal_Calender (PCNO, Planned_Vacation)

FK

Executive (ENO, Qualification, PCNO)K

 Conference_Room (CNO, Capacity, Facility)
FK

Room_Calender (RCNO, Duration, Available_Satatus, Unavailable_Sataus,

CNOK)

II. Mapping 1:M Relationships

Personal_Calender (PCNO, Planned_Vacation)

FK

Entry (EID, Date, Description, Venue, Stime, Etime, PCNO)K

FK

Meeting_Organizer (ENO, Experience, MIDK )

FK K
Executive (ENO, Qualification, PCNO)
FK

Meeting (MID, Day, Participant, Stime, Etime, ENO)K

FK

Conference_Room (CNO, Capacity, ENO)K

Secretary (ENO, Typing_Speed, CNO) FKK

Room_Facility (CNO, Facility)

III. Mapping M:N Relationships

Department (DID, Dname)

FK

Employee (ENO, Fname, Lname, No, Street, City, Gender, DID)K

Emp_Contact (ENO, Contact)

STEP 04 – Mapping Unary Relationships

STEP 05 – Mapping Complex Relationships

-
STEP 06 – Mapping Supertype / Subtype Relationships
FK

Employee (ENO, Fname, Lname, No, Street, City, Gender, DID)K

FK
 Executive (ENO, Qualification, PCNO)K

Secretary (ENO, Typing_Speed, CNO)FKK

FK

Meeting_Organizer (ENO, Experience, MID)K

STEP 07 – Mapping Categories

3.3 FINALIZED RELATIOANL SCHEMA FOR THE ER

DIAGRM

FK

Room_Calender (RCNO, Duration, Available_Satatus, Unavailable_Sataus, CNO)K

Personal_Calender (PCNO, Planned_Vacation)

FK

Entry (EID, Date, Description, Venue, Stime, Etime, PCNO)K

FK

Meeting (MID, Day, Participant, Stime, Etime, ENO)K

FK

Conference_Room (CNO, Capacity, ENO)K

Room_Facility (CNO, Facility)

Department (DID, Dname)

Emp_Contact (ENO, Contact)

FK

Employee (ENO, Fname, Lname, No, Street, City, Gender, DID)K

FK

Executive (ENO, Qualification, PCNO)K

FK

Secretary (ENO, Typing_Speed, CNO)K

FK

Meeting_Organizer (ENO, Experience, MID)K

 3.4 DATA DICTIONARY

Room_Calender
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 RCNO Room calendar Int 10 YES NO

number
2 Duration Time period of varchar 15 NO NO
meeting
3 Available Room varchar 20 NO NO
Status availability
4 Unavailable Room varchar 20 NO NO
Status unavailability
5 CNO Conference Int 10 NO YES
room number
Table 2

Personal Calendar
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 PCNO Personal Int 10 YES NO

calendar ID
 2 Planned Vacation details varchar 15 NO NO
Vacation
Table 3

Conference Room
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 CNO Conference Int 10 YES NO

room ID
2 Capacity Room capacity varchar 15 NO NO
3 ENO Employee Int 10 NO YES
number
Table 4

Entry
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 EID Entry number Int 10 YES NO

2 Date Date of the put Date 15 NO NO
entry
3 Description Meeting Char 20 NO NO
description
4 Venue The place of varchar 20 NO NO
meeting
5 Stime Start time of Time 10 NO NO
meeting
6 Etime End time of Time 10 NO NO
meeting
7 PCNO Personal Int 10 NO YES
calendar ID
Table 5

Meeting
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key
 1 MID Meeting Int 10 YES NO
number
2 Day Date of the Date 15 NO NO
meeting
3 Participant Participant varchar 20 NO NO
details
4 Stime Start time of Time 10 NO NO
meeting
5 Etime End time of Time 10 NO NO
meeting
6 ENO Employee Int 10 NO YES
number
Table 6

Room Facility
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 CNO Conference Int 10 YES NO

room number
2 Facility Facilities of varchar 15 NO NO
conference
room
Table 7

Department
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 DID Department Int 10 YES NO

number
2 Dname Department Char 15 NO NO
name
Table 8

Emp_Contact
 Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 ENO Employee Int 10 YES NO

number
2 Contact Contact number Int 10 NO NO
Table 9

Executive
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

nna1 ENO Employee Int 10 YES NO

number
2 Qualification Contact number char 25 NO NO
3 PCNO Personal Int 10 NO YES
calendar number
Table 10
Employee
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 ENO Employee Int 10 YES NO

number
2 Fname First name of Char 15 NO NO
employee
3 Lname Last name of Char 20 NO NO
employee
4 NO Residence Int 10 NO NO
number
5 Street Street name of varchar 15 NO NO
residence
6 City City of resident varchar 15 NO NO
7 Gender Sex of employee Char 10 NO NO

8 DID Department ID Int 10 NO YES

Table 11

Secretary
 Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 ENO Employee Int 10 YES NO

number
2 Typing speed Typing speed of varchar 25 NO NO
documents
3 CNO Conference Int 10 NO YES
room number
Table 12

Meeting Organizer
Serial Data Name Description Data No of Primary Foreign Key
No Type characters Key

1 ENO Employee Int 10 YES NO

number
2 Experience Experience of varchar 25 NO NO
organize
3 MID Meeting number Int 10 NO YES
Table 13