Table of Contents

Introduction of The Project........................................................................................ 1

Activity – 01 ............................................................................................................. 1
Data & Information ............................................................................................... 1
Database Management System ............................................................................. 1
Relational Database .......................................................................................... 1
Types of Relational Databases, ................................................................ 1
Types of Requirements ............................................................................ 2
User Requirements ........................................................................................ 2
Example of User Requirements ................................................................ 2
Types of User Requirements .................................................................... 2
Functional Requirements ........................................................................... 2
Example of Functional Requirements ....................................................... 3
Non-Functional Requirements .................................................................... 4
Examples of Non-Functional Requirements .............................................. 4
System Requirements .................................................................................... 5
Types of System Requirements ................................................................ 5
Examples of Hardware Requirements....................................................... 5
Examples of Software Requirements ........................................................ 5
Conceptual Design & Model............................................................................... 6
Entity ............................................................................................................ 6
Types of Entity ........................................................................................ 6
Strong Entity .............................................................................................. 6
Weak Entity................................................................................................ 6
Attributes ...................................................................................................... 7
Types of Attributes .................................................................................. 7
Relationship .................................................................................................. 8
Degree of Relationship ............................................................................ 8
Cardinality .................................................................................................... 8
Types of Cardinalities .............................................................................. 8
List of Entities & Attributes According to the Project .................................. 9

Page | I
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Relationships & Cardinalities According to the Project............................. 11
Entity Relationship Diagram ......................................................................... 12
Logical Schema ........................................................................................... 13
Normalization ............................................................................................. 14
Types of Normalization .......................................................................... 14
Un Normalization ..................................................................................... 14
1st Normalization ...................................................................................... 17
2nd Normalization ..................................................................................... 20
3rd Normalization ...................................................................................... 24

Page | II
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
List of Tables
Table 1 Un-Normalization Data ............................................................................................... 14
Table 2 1st Normalization: - Colonist ...................................................................................... 17
Table 3 1st Normalization: - Colonist Qualification ................................................................ 17
Table 4 1st Normalization: - Colonist Contact Number .......................................................... 17
Table 5 1st Normalization: - Dependent .................................................................................. 18
Table 6 1st Normalization: - E_Jet........................................................................................... 18
Table 7 1st Normalization: - Staff ............................................................................................ 18
Table 8 1st Normalization: - Pilot ............................................................................................ 18
Table 9 1st Normalization: - Pilot Jet Details .......................................................................... 19
Table 10 1st Normalization Pilot Qualification ....................................................................... 19
Table 11 1st Normalization: - Trip ........................................................................................... 19
Table 12 1st Normalization: - Trip Details .............................................................................. 19
Table 13 1st Normalization: - House ....................................................................................... 19
Table 14 1st Normalization: - Colonist House Details ............................................................ 20
Table 15 1st Normalization: - Job ............................................................................................ 20
Table 16 1st Normalization: -Colonist Job Details .................................................................. 20
Table 17 2nd Normalization: - Colonist................................................................................... 20
Table 18 2nd Normalization: - Colonist Qualification ............................................................ 21
Table 19 2nd Normalization: - Colonist Contact Number ....................................................... 21
Table 20 2nd Normalization: - Dependent ............................................................................... 21
Table 21 2nd Normalization; - E_Jet ....................................................................................... 21
Table 22 2nd Normalization: - Staff ........................................................................................ 22
Table 23 2nd Normalization: - Pilot......................................................................................... 22
Table 24 2nd Normalization: - Pilot Jet Details ....................................................................... 22
Table 25 2nd Normalization: - Pilot Qualification .................................................................. 22
Table 26 2nd Normalization: - Trip ......................................................................................... 23
Table 27 2nd Normalization: - Trip Details ............................................................................. 23
Table 28 2nd normalization: - House ....................................................................................... 23
Table 29 2nd Normalization: - Colonist House Details ........................................................... 23
Table 30 2nd Normalization; - Job........................................................................................... 23
Table 31 2nd Normalization: - Colonist Job Details ................................................................ 23
Table 32 3rd Normalization: - Colonist ................................................................................... 24
Table 33 3rd Normalization: - Colonist Qualification ............................................................. 24
Table 34 3rd Normalization: -Colonist Contact Number ......................................................... 24
Table 35 3rd Normalization: - Dependent ............................................................................... 25
Table 36 3rd Normalization: - E_Jet ........................................................................................ 25
Table 37 3rd Normalization: - Staff ......................................................................................... 25
Table 38 3rd Normalization; - Pilot ......................................................................................... 26
Table 39 3rd Normalization: - Pilot Jet Details ....................................................................... 26
Table 40 3rd Normalization: - Pilot Qualification ................................................................... 26
Table 41 3rd Normalization: - Trip .......................................................................................... 26
Table 42 3rd Normalization: - Trip Details .............................................................................. 26

Page | III
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Table 43 3rd Normalization: - House....................................................................................... 27
Table 44 3rd Normalization: - Colonist House Details ............................................................ 27
Table 45 3rd Normalization: - Job ........................................................................................... 27
Table 46 3rd Normalization: - Colonist Job Details ................................................................ 27

Page | IV
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Table of Figures
Figure I Entity ............................................................................................................................ 6
Figure II Strong Entity ............................................................................................................... 6
Figure III Weak Entity ............................................................................................................... 6
Figure IV Simple Attribute ........................................................................................................ 7
Figure V Composite Attributes .................................................................................................. 7
Figure VI Derived Attribute ....................................................................................................... 7
Figure VII Single-Value Attribute .............................................................................................. 8
Figure VIII Multi-Value Attribute .............................................................................................. 8
Figure IX Entity Relationship Diagram ................................................................................... 12
Figure X Logical Schema ........................................................................................................ 13

Page | V
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Introduction of The Project
o E-Space Solutions (Pvt. Ltd) is organizing a historic mission to colonize Mars in
2040. To support this project, the organization needs a solid Database Management
System (DBMS) to store and keep essential data. This system will ensure data
accuracy and consistency throughout the project's lifecycle, thus easing decision-
making and operational efficiency.

Activity – 01
Data & Information
o Data is made up of unorganized facts and numbers Because the letters and numbers
"C0001, C0002, C0003" are just data points, display them alone does not properly
express meaning. (David T. Bourgeois, 2014, pp. 39-40)

o Data that has been usefully arranged, contextualized, and processed is called
information. The raw data now has meaning and becomes information, for instance, if
you are informed that "C0001, C0002, and C0003" are the numbers of colonists
registered for the future Mars Colonization Project. We can comprehend and make
meaningful use of the facts thanks to information. (David T. Bourgeois, 2014)

Database Management System

o Data is an aggregation of information-producing facts and figures, and a database is a
collection of related data. Records of facts make up the majority of data. Data is used
in the production of fact-based information. If we have data on the colonists and
dependents living in the house, for example, we could calculate the average number
of colonists living with their families. To make data retrieval, change, and production
easier, and that's the use of a database management system that stores the data.
(Tutorials Point, n.d.)

Relational Database
o A relational database delivers a set of data rows in response to a query. A query
language most commonly the Structured Query Language (SQL) helps to create data
views. (Dancuk, Database Types Explained, 2021)

Types of Relational Databases,

• Centralized Database
o A centralized database stores and manages all its data centrally. A
network provides access to data. The data that has been stored can
be accessed by the end user via the network on the centralized
computer. (Dancuk, Database Types Explained, 2021)

• Distributed Database

Page | 1
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 o Information and Data are stored across several physical locations in
the distributed databases. The database may be spread across
multiple sites or locations and maintained on multiple CPUs at one
location. End users believe that the data is included in a single
database due to the connections that connect the disparate
databases. (Dancuk, Database Types Explained, 2021)

• Cloud Database
o A cloud database is a stand-alone database that is generated,
deployed, and accessed from the cloud. A cloud database provides all
of the functionality of a regular database while also allowing for cloud
computing flexibility. (Marijan, 2021)

Types of Requirements
o User Requirements

o System Requirements

User Requirements
o Prioritize user needs and expectations when developing a system and figure out what
the end users expect from the system and what they should obtain from the system.
(Catherine Courage, 2005, p. 3)

Example of User Requirements

o The Colonist, Dependent, Trip, E-Jet, Pilot, House, and Job data should be stored in
the database.

o To ensure easy identification of data in the table, assign each table a unique ID that
cannot be repeated.

o Create a trip details table that includes the trip, colonist, Pilot, and E-Jet details so that
pilots can easily check the trip details.

o Create a separate table for the colonists' and pilots' qualifications since they can have
multiple qualifications.

o Create a separate table for the colonists' contact information since they can have
multiple contact numbers.

Types of User Requirements

o Functional Requirements

o Non-Functional requirements

Functional Requirements
o Describe the system's services, response to inputs, and behavior in specific situations.
(UCSB Computer Science Department, 2023, p. 13)

Page | 2
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Example of Functional Requirements
• Colonist & Dependents
o Store the colonists' and dependents' data in the DBMS.

o Can search for the dependents' details with colonists unique_ID.

• E_Jet
o Record the details of E_Jet in DBMS.

o Can search for what kind of power source this has and can also
search for what kind of engine type it has.

o Assign Pilot to the E_Jet.

• Pilot
o Store the pilots' data in the DBMS.

o Can search for the pilot qualifications.

o He can check the data of the system according to the spacecraft trip
information with the passenger details.

• Trip
o Schedule and manage the trips including the departure, and arrival
dates.

o Assign E_Jet to the Trips.

• Houses
o Track house occupancy and capacity. (include and list which colonist
is staying there and if there is a dependent list them too.)

• Jobs
o Maintain a list of jobs available for the colonists.

o Assign the jobs to colonists based on their qualifications.

• Staff

• Data Entry Operators

o Input and update the colonists, dependents, pilots, trips, and
E_Jet details.
o Record the house allocation for colonists and dependents.
o Record the job assigns to colonists.
Page | 3
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 • System Administrator
o He has full data access (can view, update, and delete).
o Generate reports with the data.
o Can monitor and manage the colonists, dependents, trips, and
E_Jets.

• Colony Superintendent
o He can allocate houses to colonists and manage them.
o He can manage the jobs and generate the reports.
o He can monitor the colonists.

Non-Functional Requirements
o Non-functional Requirements describe the quality characteristics of a software
system. They evaluate the software system's Performance, Usability, Security,
Reliability, and other non-functional needs that are critical to the system's success.
(Batool, 2020, p. 116)

Examples of Non-Functional Requirements

• Performance
o Performance Nonfunctional requirements specify the system's
responsiveness and speed. They specify how quickly the system
should respond to the user queries and return the results. This can
include a variety of measures, such as response time, and resource
use. (E.g.: - with the search function the system should be able to
return colonists’ and Dependents’ information instantly.) (Das, 2024)

• Security

• Authentication & Authorization

o Implement robust user authentication and role-based access
control to restrict who can view, modify, and delete data. (E.g.: -
Only authorized personnel can input or modify data like Data Entry
Operator, and Administrator.) (Das, 2024)

• Encryption
o Sensitive data must be encrypted both at rest and in transit to
prevent unauthorized access. This ensures that even if data is
intercepted, it cannot be accessed without the appropriate
decryption keys. (To ensure that unauthorized people can't read the
data.) (Das, 2024)

Page | 4
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 • Usability
o Provide an easy-to-use interface for data entry and retrieval. (Provides
an easy-to-use data fill-in system, auto-fills in suggestions to ease the
data entry, and provides a search bar with filtering options.) (Das, 2024)

• Reliability
o Reliability NFRs assess the system's capacity to execute consistently
over time while avoiding critical failures. This covers error rates,
recovery times, and the system's capacity to operate in prescribed
settings without downtime. (Regular data backups to prevent data
loss, and Recovery mechanisms to restore data in case of system
failures or some data is deleted or overwritten.) (Das, 2024)

• Scalability
o Ability to handle an increasing number of records as the colonization
project grows. (When colonists and dependents are increasing in
numbers over a year.) (Das, 2024)

System Requirements
o Design and build a system that satisfies the users’ needs. This involves establishing
the technical and operational specifications necessary to support the functionality and
performance expected by the users. (UCSB Computer Science Department, 2023)

Types of System Requirements

o Hardware Requirements

o Software Requirements

Examples of Hardware Requirements

o RAM: - 32GB or more RAM.

o Storage: - 1TB or more SSD Storage.

o End Devices: - ASUS, Samsung, and ACER Monitors or Pc.

o High-speed network switches and routers. [E.g.: - Cisco or TP-link]

o Secure and reliable internet connection.

o Cables: - Ethernet Crossover Cable or Fiber Optic Cable.

Examples of Software Requirements

o Operating System: - Windows 11 or 10

o Database Management System: - Microsoft SQL Server.

Page | 5
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 o Backup Software: - A reliable backup solution that is compatible with the chosen
DBMS. [E.g.: - Veeam, Acronis]

o Monitoring Software: - Database and system-monitoring software. [E.g.: - Nagios,

Zabbix]

Conceptual Design & Model

o Conceptual design is an important step in the database design process. It focuses on
abstractly comprehending and expressing an organization's data requirements,
creating a high-level representation of the data and its relationships without getting
into the specifics of how that data will be physically implemented in a database
management system (DBMS). (Huawei Technologies Co., Ltd., 2022)

o A conceptual model is an abstract representation of the basic parts and interactions of

a system. It reduces complex reality into smaller, more manageable components,
which improves problem-solving. (Huawei Technologies Co., Ltd., 2022)

Entity
o An entity is a unique thing or concept that can be stored in a database. Entities can be
animate or inanimate (non-living) and have unique properties that define their
characteristics. (Tutorials Point, n.d.)

Figure I Entity

Types of Entity
o Strong Entity

o Weak Entity

Strong Entity
o A strong entity has not relied on any other entity. [E.g.: The Colonist is a strong entity,
and it has a primary key.] (OpenDSA, n.d.)

Figure II Strong Entity

Weak Entity
o A weak entity relies on a strong entity to ensure its existence. [E.g.: - The Dependent
entity relies on a Colonist entity, and it doesn’t have a primary key.] (OpenDSA, n.d.)

Figure III Weak Entity

Page | 6
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Attributes
o An attribute is a characteristic of an entity that helps define and describe it. Attributes
provide specific information about the entity that helps distinguish one entity from
another. (Tutorials Point, n.d.)

Types of Attributes
• Simple Attributes
o Simple attributes are atomic values, which cannot be divided further.
[E.g.: - A Colonist's Civil Status has an atomic value which cannot be
divided.] (Tutorials Point, n.d.)

Figure IV Simple Attribute

• Composite Attributes
o Composite attributes include more than one simple attribute. [E.g.: -
Colonists name.] (Tutorials Point, n.d.)

Figure V Composite Attributes

• Derived Attribute
o Derived attributes are the attributes that do not exist in the physical
database, but their values are derived from other attributes present in
the database. [E.g.: - Colonists age can be derived from the colonists
dob.] (Tutorials Point, n.d.)

Figure VI Derived Attribute

• Single Value Attribute

o Single-value attributes contain a single value. [E.g.: -
FamilyMembers_Count.] (Tutorials Point, n.d.)

Page | 7
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Figure VII Single-Value Attribute

• Multi Value Attribute

o Multi-value attributes may contain more than one value. [E.g.: -
Colonists Qualification.] (Tutorials Point, n.d.)

Figure VIII Multi-Value Attribute

Relationship
o According to the Tutorials Points website document relationships are associations
between entities. (Tutorials Point, n.d.)

Degree of Relationship
• Unary Relationship
o A unary relationship is a single entity type involved in the relationship
with itself. In other words, it occurs when entities of the same type are
related to each other. (GeeksforGeeks, 2023)

• Binary Relationship
o It describes the relationship between the two separate entities.
(GeeksforGeeks, 2023)

• Ternary Relationship
o A ternary relationship connects three entities at the same time.
(GeeksforGeeks, 2023)

• “n”ary Relationship
o An “n”ary relationship can associate n different types of entities at the
same time. (GeeksforGeeks, 2023)

Cardinality
o According to the Tutorials Points website document cardinality defines the number of
entities in one entity set, which can be associated with the number of entities of
another set via a relationship set. (Tutorials Point, n.d.)

Types of Cardinalities
• One – One Relationship

Page | 8
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 o According to the Tutorials Points website document one entity can be
associated with at most one entity and vice versa. (Tutorials Point,
n.d.)

• One-to-Many / Many-to-One
o According to the Tutorials Points website document one entity can be
associated with more than one entity however each instance of the
second entity is associated with only one instance of the first entity
and vice versa. (Tutorials Point, n.d.)

• Many-to-Many
o According to the Tutorials Points website document one entity can be
associated with more than one entity and vice versa. (Tutorials Point,
n.d.)

List of Entities & Attributes According to the Project

• Colonist
o MarsColonization_ID

o Colonist_Name

o Date_of_Birth

o Age

o Gender

o Civil_Status

o Earth_Address

o Family_Members_Count

o Contact_Number

o Qualification

• Dependent
o Dependent_ID

o Dependent_Name

o Date_of_Birth

o Age

o Relationship_to_Colonist

Page | 9
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 • Trip
o Trip_ID

o Departure_Date

o Arrival_Date

• E_Jet
o Jet_Unique_Code

o Engine_Type

o Power_Source

o Weight

o Jet_Made_Year

o Number_of_Passenger_Seats

• Pilot
o Pilot_ID

o Pilot_Name

o Space_Hours

o Designation

o Qualification

• House
o ColonyLot_Number

o Number-of-Rooms

o Square_Feet

• Job
o Job_ID

o Job_Title

o Start_Date

o End_Date

• Staff
o Staff_ID

Page | 10
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 o Staff_Name

o Staff_Designation

o User_Name

o Password

Relationships & Cardinalities According to the Project

• Colonist & Dependent
o One-to-Many (One colonist can have multiple dependents, and each
dependent belongs to one colonist)

• Colonists & Trip

o Many-to-One (Many colonists can take the same trip, but each trip is
taken by one colonist only, with no return trips)

• Colonist & Job

o Many-to-Many (One colonist can be assigned to multiple jobs, and
each job can be assigned to multiple colonists)

• Colonist & House

o Many-to-One (Multiple colonists can be allocated to the same house,
but each house is allocated to only one group of colonists)

• Trip & E_Jet

o Many-to-Many (One trip can use multiple jets, and one jet can be used
for multiple trips)

• E_Jet & Pilot

o Many-to-One (Multiple E_Jets can be assigned to a single pilot, but
each pilot is assigned to only one E_Jet.)

• Pilot & Staff

o One-to-One (Each pilot is associated with one staff member role, and
each staff member role includes only one pilot. This relationship
allows pilots to access trip details within the system.)

• Colonist & Staff

o Many-to-One (Multiple colonists can be managed by a single staff
member, and each staff member can handle the data for multiple
colonists.)

Page | 11
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 • Dependent & Staff
o Many-to-One (Multiple dependents can be managed by a single staff
member, and each staff member can oversee or provide assistance to
multiple dependents.)

• Job & Staff

o Many-to-One (Multiple jobs can be managed by a single staff member,
and each staff member can manage or oversee multiple jobs.)

• House & Staff

o Many-to-One (Multiple houses can be managed by a single staff
member, and each staff member can manage or oversee multiple
houses.)

• Trip & Staff

o Many-to-One (Multiple trips can be managed or overseen by a single
staff member, and each staff member can manage or oversee multiple
trips.)

• E_Jet & Staff

o Many-to-One (Multiple E_Jets can be managed or operated by a single
staff member, and each staff member can manage or operate multiple
E_Jets.)

Entity Relationship Diagram

o Nishadha defines the Entity Relationship Diagram as a visual representation of a
relational database's structure. (Nishadha, 2024)

Figure IX Entity Relationship Diagram

Page | 12
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Logical Schema
o According to the Greeks for Greeks website logical schema is a database blueprint
that focuses on the data's logical structures. It defines how data is arranged and how
different bits of data are connected but does not specify actual storage characteristics.
(Geeks for Geeks, 2024)

Figure X Logical Schema

Page | 13
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
Normalization
o Normalization, according to the Department of Computer Science at the University of
Cape Town, is a procedure that ensures data is formatted so that qualities are grouped
with the primary key, which gives unique identification. (Department of Computer
Science, University of Cape Town, n.d., p. 15)

Types of Normalization
o Un Normalization

o 1st Normalization

o 2nd Normalization

o 3rd Normalization

Un Normalization
o According to Milica Dancuk, an unnormalized table contains several values in a
single row. (Dancuk, What is Database Normalization?, 2021)
Table 1 Un-Normalization Data

Dependent Hous
Colonist Details Details Jet Staff Pilot Trip e Job
JID
MCID=C0001,Na CLN= =J0
me=JamesMicha HCLN 001
elAnderson,DOB PID=P000 TID=T0 0001, ,J_T
=1/20/1990,Gend DID=D0001,Nam JUC=J00 SID=S00 1,PName= 001,De Num_ itle
er=Male,Address e=(Laura Grace 01,Engin 01,SNa Raj,Space parture of_Ro =C
=(123 Oakwood Anderson,Ethan eType=N me=Noa Hours=(10 Date=6 oms= ons
Avenue, James Anderson, uclear h,Sdesig ,000 /22/20 4,Squ truc
Toronto,Ontario, Lucas Michael Engine,P ination= hours),Des 23,Arri areFe tion
ON M4B 1B3, Anderson), owerSour Data ignation=J valDate et=(2, ,CJ
Canada),CS=Sing DOB=(20-Jan- ce=Nucle Entry unior_Pilot =6/23/ 450 D=(
le,FamilyMember 1991, 21-Feb- ar,JetMa Operato ,PilotsJet=( 2023,Tr sq. J00
sCount=3,Qualifi 2015, 02-Mar- deYear=3 r,Userna J0001,J000 ip_Det ft),CH 01-
cation=(HND in 2016),Relationsh /20/2020 me=DE 3),PilotQu ails=(T D=(H C0
English, BEng, ip_to_Colonist=( ,Weight= O0001#, alification 0001- CLN0 001
MSc),ContN=777 Wife, 442.89 Passwor =(SPC,PPL C0001- 001- ,C0
676761, Son1&Son2),MCI Ton,NOP d=DE12 ,CPL),SID= P0001- C000 003
777767000 D=C0001 S=50 345 S0003 J0001) 1) )
MCID=C0002,Na DID=D0002,Nam JUC=J00 SID=S00 PID=P000 TID=T0 CLN= JID
me=SarahElizabe e=(Matthew 02,Engin 02,SNa 2,PName= 002,De HCLN =J0
thJhonson,DOB= James Johnson, eType=N me=Eth Kamel,Spa parture 0002, 002
3/21/1991,Gende Noah Benjamin uclear&H an,Sdesi ceHours=( Date=7 Num_ ,J_T
r=Female,Addres Johnson, ydro gination 15,000 /25/20 of_Ro itle
s=(456 Elm Alexander splitter =System hours),Des 23,Arri oms= =M
Street, Los Thomas Johnson, Engine,P Administ ignation=S valDate 4,Squ ech
Angeles,Californi Olivia Grace owerSour rator, enior_Pilot =7/26/ areFe ani
a,CA 90012, Johnson), ce=(Nucl Userna ,PilotsJet=( 2023,Tr et=(2, cal,

Page | 14
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 USA),CS=Married DOB=(01-Jan- ear,Hydr me=A00 J0001,J000 ip_Det 450 CJD
, 1991, 02-May- o),JetMa 00001#, 2),PilotQu ails=(T sq. =(J
FamilyMembersC 2015, 03-Jun- deYear=3 Passwor alification 0001- ft),CH 000
ount=4,Qualificat 2016, 13-Aug- /21/2020 d=A067 =(SPC, C0002, D=(H 2-
ion=(HND in 2017),Relationsh ,Weight= 891 PPL, CPL, C0003- CLN0 C0
English, BICT, MS ip_to_Colonist=( 450.75 RPC, CFI P0002- 002- 002
in Husband,Son1,S Ton,NOP ),SID=S00 J0002) C000 )
ICT),ContN=7576 on2,Daughter),M S=50 04 2)
76762, CID=C0002
752828510

MCID=C0003,Na JUC=J00 SID=(S0

me=DavidAnthon 03,Engin 003,S00 JID
yGarcia,DOB=1/2 eType=N 04),SNa CLN= =J0
0/1988,Gender= uclear&H me=(Raj HCLN 003
Male,Address=(7 ydro ,Kamel), 0003, ,J_T
89 Pine Street, splitter Sdesigin Num_ itle
Miami,Florida , FL Engine,P ation=Pil of_Ro =Po
33101, - owerSour ot,Usern - - oms= wer
USA),CS=Single,F ce=(Nucl ame=(P 4,Squ Ge
amilyMembersCo ear,Hydr 0000001 areFe ner
unt=0,Qualificati o),JetMa #,P0000 et=(2, atio
on=(HND in deYear=3 002#) 450 n,C
English, BEng, /22/2020 ,Passwo sq. JD=
MSc),ContNu=77 ,Weight= rd=(P06 ft),CH (J0
7676767, 450.75 7891,P0 D=(H 003
777767001 Ton,NOP 67892) CLN0 -
S=50 003- C0
C000 003
3) )
o To fit the table in the Word Document several headings have been shortened as seen
below: -

• In Colonist Details Column

o MCID – Mars_Colonization_ID

o Name – Colonist-Name

o DOB – Date_of_Birth

o Address – Earth_Address

o CS – Civil_Status

o Qualification – Colonists_Qualification

o ContNu – Contact_Number

• In Dependent Details Column

Page | 15
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 o DID – Dependent_ID

o Name – Dependent_Name

o DOB – Date_of_Birth

o MCID – Mars_Colonization_ID

• In Jet Column
o JUC – Jet_Unique_Code

o Weight – Jet_Weight

o NOPS – Number_of_Passengers_Seat

• In Staff Column
o SID – Staff_ID

o SName – Staff_Name

o Sdesignation – Staff_Designation

• In pilot Column
o PID – Pilot_ID

o PName – Pilot_Name

o PilotsJet – Pilot_Assigned_Jet_Details

• In Trip Column
o TID – Trip_ID

• In House Column
o CLN – Colony_Lot_Number

o Num_of_Rooms – Number_of_Rooms

o CHD – Colonist House Details

• In Job Column
o JID – Job_Id

o J_Title - Job title

o CJD – Colonist_Job_Details

Page | 16
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
1st Normalization
o According to Milica Dancuk, values in a single field must be atomic. All complex
elements in the table are rearranged into new rows or columns. (Dancuk, What is
Database Normalization?, 2021)
Table 2 1st Normalization: - Colonist

01. Colonist
Mid G Stre
MarsC Firs dle
Su Date en etNu Street Post Co Civi Family
oloniza tNa Narna _of_ de mbe Addre Sta alC un lSta Membe
tion_ID me meme Birth r r ss City te ode try tus rsCount
An Oakw
der 20- M ood On ON Ca
Jam Mich so Jan- al Avenu Toro tari M4B na Mar
C0001 es ael n 1990 e 123 e nto o 1B3 da ried 3
Fe
Jho 21- m Los Cal CA
Sar Eliza ns Mar- al Elm Ang ifor 900 US Mar
C0002 ah beth on 1991 e 456 Street eles nia 12 A ried 4
Ga 20- M Flo FL
Dav Anth rci Jan- al Pine Mia rid 331 US Sin
C0003 id ony a 1988 e 789 Street mi a 01 A gle 0

Table 3 1st Normalization: - Colonist Qualification

02. Colonist Qualification

CQ_ID Qualification MarsColonization_ID
CQ0001 HND in English C0001
CQ0002 BEng C0001
CQ0003 MSc C0001
CQ0004 HND in English C0002
CQ0005 BICT C0002
CQ0006 MS in ICT C0002
CQ0007 HND in English C0003
CQ0008 BEng C0003
CQ0009 MSc C0003

Table 4 1st Normalization: - Colonist Contact Number

03. ColonistCont_Num
CCN_ID Cont_Num MarsColonization_ID
CCN0001 (77) 767-6761 C0001
CCN0002 (77) 776-7000 C0001
CCN0003 (75) 767-6762 C0002
CCN0004 (75) 282-8510 C0002
CCN0005 (77) 767-6767 C0003
CCN0006 (77) 776-7001 C0003

Page | 17
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Table 5 1st Normalization: - Dependent

04. Dependent
Relationship_to_Coloni MarsColonization_I
D_ID D_Name DOB st D
D000 20-Jan-
1 Laura Grace Anderson 1991 Wife C0001
D000 21-Feb-
2 Ethan James Anderson 2015 1st Son C0001
D000
3 Lucas Michael Anderson 2-Mar-2016 2nd Son C0001
D000
4 Matthew James Johnson 1-Jan-1991 Husband C0002
D000
5 Noah Benjamin Johnson 2-May-2015 1st Son C0002
D000 Alexander Thomas
6 Johnson 3-Jun-2016 2nd Son C0002
D000 13-Aug-
7 Olivia Grace Johnson 2017 Daughter C0002

Table 6 1st Normalization: - E_Jet

05. E_Jet
JetUnique_C PowerSour JetMadeY Num_of_Passenger
ode EngineType ce ear Weight sSeats
20-Mar- 442.89
J0001 Nuclear Engine Nuclear 2024 Ton 50
Nuclear&Hydro splitter Nuclear, 21-Mar- 450.75
J0002 Engine Hydro 2024 Ton 50
Nuclear&Hydro splitter Nuclear, 22-Mar- 450.75
J0003 Engine Hydro 2024 Ton 50

Table 7 1st Normalization: - Staff

06. Staff
Staff_ID Staff_Name Staff_Designation User_Name Password
S0001 Noah Data Entry Operator DEO0001# DE12345
S0002 Ethan System Administrator A0000001# A067891
S0003 Raj Pilot P0000001# P067891
S0004 Kamel Pilot P0000002# P067892

Table 8 1st Normalization: - Pilot

07. Pilot
P_ID P_Name Space_Hours Designation Staff_ID
P0001 Raj 10,000 Hours Junior_Pilot S0003

Page | 18
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 P0002 Kamel 15,000 Hours Senior Pilot S0004

Table 9 1st Normalization: - Pilot Jet Details

08. PilotJet_Details
PJD_ID P_ID JetUnique_Code
PJD0001 P0001 J0001
PJD0002 P0001 J0003
PJD0003 P0002 J0001
PJD0004 P0002 J0002

Table 10 1st Normalization Pilot Qualification

09. PilotQualification
PQ_ID Qualification P_ID
PQD001 SPC P0001
PQD002 PPL P0001
PQD003 CPL P0001
PQD004 SPC P0002
PQD005 PPL P0002
PQD006 CPL P0002
PQD007 RPC P0002
PQD008 CFI P0002

Table 11 1st Normalization: - Trip

10. Trip
T_ID DepatureDate ArrivalDate
T0001 22-Jun-2023 23-Jun-2023
T0002 25-Jul-2023 26-Jul-2023

Table 12 1st Normalization: - Trip Details

11. Trip Details

TD_ID T_ID P_ID JetUnique_Code MarsColonization_ID
TD0001 T0001 P0001 J0001 C0001
TD0002 T0002 P0002 J0002 C0002
TD0003 T0002 P0002 J0002 C0003

Table 13 1st Normalization: - House

12. House
ColonyLot_Num Num_of_Rooms SquareFeet
CLN0001 4 2,450 sq. ft
CLN0002 4 2,450 sq. ft

Page | 19
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 CLN0003 4 2,450 sq. ft

Table 14 1st Normalization: - Colonist House Details

13. Colonist House Details

CHD_ID ColonyLot_Num MarsColonization_ID
CHD0001 CLN0001 C0001
CHD0002 CLN0002 C0002
CHD0003 CLN0003 C0003

Table 15 1st Normalization: - Job

14. Job
J_ID J_Title StartDate EndDate
J0001 Construction 23-Jun-2023 30-Sep-2024
J0002 Mechanical 24-Jun-2023 1-Oct-2024
J0003 Power Generation 25-Jun-2023 2-Oct-2024

Table 16 1st Normalization: -Colonist Job Details

15. ColonistJobDetails
CJD_ID J_ID MarsColonization_ID
CJD0001 J0001 C0001
CJD0002 J0001 C0003
CJD0003 J0002 C0002
CJD0004 J0003 C0003
2nd Normalization
o Milica Dancuk defines that every table in the database must depend on the primary
key if it has to consider a 2nd normalization. (Dancuk, What is Database
Normalization?, 2021)
Table 17 2nd Normalization: - Colonist

01. Colonist
Mid Su G Stre Civi Family
MarsCol Firs dle rn Date en etNu Stree Post Co lSt Membe
onizatio tNa Na am _of_ de mbe tAddr Sta alC un atu rsCoun
n_ID [PK] me me e Birth r r ess City te ode try s t
An 20- Oakw
Ja der Jan- M ood On ON Ca
me Mic so 199 al Avenu Toro tari M4B na Mar
C0001 s hael n 0 e 123 e nto o 1B3 da ried 3
21- Fe
Jho Mar- m Los Cal CA
Sar Eliza ns 199 al Elm Ang ifor 900 US Mar
C0002 ah beth on 1 e 456 Street eles nia 12 A ried 4

Page | 20
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 20-
Ga Jan- M Flo FL
Dav Anth rci 198 al Pine Mia rid 331 US Sin
C0003 id ony a 8 e 789 Street mi a 01 A gle 0

Table 18 2nd Normalization: - Colonist Qualification

02. ColonistQualification
CQ_ID [PK] Qualification
CQ0001 HND in English
CQ0002 BEng
CQ0003 MSc
CQ0004 HND in English
CQ0005 BICT
CQ0006 MS in ICT
CQ0007 HND in English
CQ0008 BEng
CQ0009 MSc

Table 19 2nd Normalization: - Colonist Contact Number

03. Colonistcont_Num
CCN_ID [PK] Cont_Num
CCN0001 (77) 767-6761
CCN0002 (77) 776-7000
CCN0003 (75) 767-6762
CCN0004 (75) 282-8510
CCN0005 (77) 767-6767
CCN0006 (77) 776-7001

Table 20 2nd Normalization: - Dependent

04. Dependent
D_ID [PK] D_Name DOB Relationship_to_Colonist
D0001 Laura Grace Anderson 20-Jan-1991 Wife
D0002 Ethan James Anderson 21-Feb-2015 1st Son
D0003 Lucas Michael Anderson 2-Mar-2016 2nd Son
D0004 Matthew James Johnson 1-Jan-1991 Husband
D0005 Noah Benjamin Johnson 2-May-2015 1st Son
D0006 Alexander Thomas Johnson 3-Jun-2016 2nd Son
D0007 Olivia Grace Johnson 13-Aug-2017 Daughter

Table 21 2nd Normalization; - E_Jet

05. E_Jet

Page | 21
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 JetUnique_Cod Power JetMade Num_of_Passenger
e [PK] EngineType Source Year Weight sSeats
20-Mar- 442.89
J0001 Nuclear Engine Nuclear 2024 Ton 50
Nuclear&Hydro Nuclear, 21-Mar- 450.75
J0002 splitter Engine Hydro 2024 Ton 50
Nuclear&Hydro Nuclear, 22-Mar- 450.75
J0003 splitter Engine Hydro 2024 Ton 50

Table 22 2nd Normalization: - Staff

06. Staff
Staff_ID [PK] Staff_Name Staff_Designation User_Name Password
S0001 Noah Data Entry Operator DEO0001# DE12345
S0002 Ethan System Administrator A0000001# A067891
S0003 Raj Pilot P0000001# P067891
S0004 Kamel Pilot P0000002# P067892

Table 23 2nd Normalization: - Pilot

07. Pilot
P_ID [PK] P_Name Space_Hours Designation
P0001 Raj 10,000 Hours Junior_Pilot
P0002 Kamel 15,000 Hours Senior Pilot

Table 24 2nd Normalization: - Pilot Jet Details

08. PilotJet_Details
PJD_ID[PK]
PJD0001
PJD0002
PJD0003
PJD0004

Table 25 2nd Normalization: - Pilot Qualification

09. PilotQualification
PQ_ID [PK] Qualification
PQD001 SPC
PQD002 PPL
PQD003 CPL
PQD004 SPC
PQD005 PPL
PQD006 CPL
PQD007 RPC
PQD008 CFI

Page | 22
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Table 26 2nd Normalization: - Trip

10. Trip
T_ID [PK] DepatureDate ArrivalDate
T0001 22-Jun-2023 23-Jun-2023
T0002 25-Jul-2023 26-Jul-2023

Table 27 2nd Normalization: - Trip Details

11. TripDetails
TD_ID [PK]
TD0001
TD0002
TD0003

Table 28 2nd normalization: - House

12. House
ColonyLot_Num [PK] Num_of_Rooms SquareFeet
CLN0001 4 2,450 sq. ft
CLN0002 4 2,450 sq. ft
CLN0003 4 2,450 sq. ft

Table 29 2nd Normalization: - Colonist House Details

13. Colonist House Details

CHD_ID [PK]
CHD0001
CHD0002
CHD0003

Table 30 2nd Normalization; - Job

14. Job
J_ID [PK] J_Title StartDate EndDate
J0001 Construction 23-Jun-2023 30-Sep-2024
J0002 Mechanical 24-Jun-2023 1-Oct-2024
J0003 Power Generation 25-Jun-2023 2-Oct-2024

Table 31 2nd Normalization: - Colonist Job Details

15. ColonistJobDetails
CJD_ID [PK]
CJD0001

Page | 23
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 CJD0002
CJD0003
CJD0004
3rd Normalization
o The 3rd Normalization is to ensure that the data in the table depends on the primary
key rather than any others means indirectly or transitively on another attribute.
(Department of Computer Science, University of Cape Town, n.d.)
Table 32 3rd Normalization: - Colonist

01. Colonist
Mid Su G Stre Civi Family
MarsCol Firs dle rn Date en etNu Stree Post Co lSt Membe
onizatio tNa Na am _of_ de mbe tAddr Sta alC un atu rsCoun
n_ID [PK] me me e Birth r r ess City te ode try s t
An 20- Oakw
Ja der Jan- M ood On ON Ca
me Mic so 199 al Avenu Toro tari M4B na Mar
C0001 s hael n 0 e 123 e nto o 1B3 da ried 3
21- Fe
Jho Mar- m Los Cal CA
Sar Eliza ns 199 al Elm Ang ifor 900 US Mar
C0002 ah beth on 1 e 456 Street eles nia 12 A ried 4
20-
Ga Jan- M Flo FL
Dav Anth rci 198 al Pine Mia rid 331 US Sin
C0003 id ony a 8 e 789 Street mi a 01 A gle 0

Table 33 3rd Normalization: - Colonist Qualification

02. Colonist Qualification

CQ_ID [PK] Qualification MarsColonization_ID [FK]
CQ0001 HND in English C0001
CQ0002 BEng C0001
CQ0003 MSc C0001
CQ0004 HND in English C0002
CQ0005 BICT C0002
CQ0006 MS in ICT C0002
CQ0007 HND in English C0003
CQ0008 BEng C0003
CQ0009 MSc C0003

Table 34 3rd Normalization: -Colonist Contact Number

03. ColonistCont_Num
CCN_ID [PK] Cont_Num MarsColonization_ID [FK]
CCN0001 (77) 767-6761 C0001
CCN0002 (77) 776-7000 C0001

Page | 24
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 CCN0003 (75) 767-6762 C0002
CCN0004 (75) 282-8510 C0002
CCN0005 (77) 767-6767 C0003
CCN0006 (77) 776-7001 C0003

Table 35 3rd Normalization: - Dependent

04. Dependent
Relationship_to_Colon MarsColonization_ID
D_ID D_Name DOB ist [FK]
D000 20-Jan-
1 Laura Grace Anderson 1991 Wife C0001
D000 21-Feb-
2 Ethan James Anderson 2015 1st Son C0001
D000
3 Lucas Michael Anderson 2-Mar-2016 2nd Son C0001
D000
4 Matthew James Johnson 1-Jan-1991 Husband C0002
D000 2-May-
5 Noah Benjamin Johnson 2015 1st Son C0002
D000 Alexander Thomas
6 Johnson 3-Jun-2016 2nd Son C0002
D000 13-Aug-
7 Olivia Grace Johnson 2017 Daughter C0002

Table 36 3rd Normalization: - E_Jet

05. E_Jet
JetUnique_Cod PowerSou JetMadeY Num_of_Passenger
e [PK] EngineType rce ear Weight sSeats
20-Mar- 442.89
J0001 Nuclear Engine Nuclear 2024 Ton 50
Nuclear&Hydro Nuclear, 21-Mar- 450.75
J0002 splitter Engine Hydro 2024 Ton 50
Nuclear&Hydro Nuclear, 22-Mar- 450.75
J0003 splitter Engine Hydro 2024 Ton 50

Table 37 3rd Normalization: - Staff

06. Staff
Staff_ID [PK] Staff_Designation Staff_Type User_Name Password
S0001 Noah Data Entry Operator DEO0001# DE12345
S0002 Ethan System Administrator A0000001# A067891
S0003 Raj Pilot P0000001# P067891
S0004 Kamel Pilot P0000002# P067892

Page | 25
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Table 38 3rd Normalization; - Pilot

07. Pilot
P_ID [PK] P_Name Space_Hours Desigination Staff_ID [FK]
P0001 Raj 10,000 Hours Junior_Pilot S0003
P0002 Kamel 15,000 Hours Senior Pilot S0004

Table 39 3rd Normalization: - Pilot Jet Details

08. PilotJet_Details
PJD_ID [PK] P_ID [FK] JetUnique_Code [FK]
PJD0001 P0001 J0001
PJD0002 P0001 J0003
PJD0003 P0002 J0001
PJD0004 P0002 J0002

Table 40 3rd Normalization: - Pilot Qualification

09. PilotQualification
PQ_ID [PK] Qualification P_ID [FK]
PQD001 SPC P0001
PQD002 PPL P0001
PQD003 CPL P0001
PQD004 SPC P0002
PQD005 PPL P0002
PQD006 CPL P0002
PQD007 RPC P0002
PQD008 CFI P0002

Table 41 3rd Normalization: - Trip

10. Trip
T_ID [PK] DepatureDate ArrivalDate
T0001 22-Jun-2023 23-Jun-2023
T0002 25-Jul-2023 26-Jul-2023

Table 42 3rd Normalization: - Trip Details

11. Trip Details

TD_ID [PK] T_ID [FK] P_ID [FK] JetUnique_Code [FK] MarsColonization_ID [FK]
TD0001 T0001 P0001 J0001 C0001
TD0002 T0002 P0002 J0002 C0002
TD0003 T0002 P0002 J0002 C0003

Page | 26
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
 Table 43 3rd Normalization: - House

12. House
ColonyLot_Num [PK] Num_of_Rooms SquareFeet
CLN0001 4 2,450 sq. ft
CLN0002 4 2,450 sq. ft
CLN0003 4 2,450 sq. ft

Table 44 3rd Normalization: - Colonist House Details

13. Colonist House Details

CHD_ID [PK] ColonyLot_Num [FK] MarsColonization_ID [FK]
CHD0001 CLN0001 C0001
CHD0002 CLN0002 C0002
CHD0003 CLN0003 C0003

Table 45 3rd Normalization: - Job

14. Job
J_ID [PK] J_Title StartDate EndDate
J0001 Construction 23-Jun-2023 30-Sep-2024
J0002 Mechanical 24-Jun-2023 1-Oct-2024
J0003 Power Generation 25-Jun-2023 2-Oct-2024

Table 46 3rd Normalization: - Colonist Job Details

15. ColonistJobDetails
CJD_ID [PK] J_ID [FK] MarsColonization_ID [FK]
CJD0001 J0001 C0001
CJD0002 J0001 C0003
CJD0003 J0002 C0002
CJD0004 J0003 C0003

Page | 27
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
References
Batool, I. (2020, August 31). Non-Functional Requirements as Constraints and Their
Values in Software Development: A Review. Retrieved from Journal of Software
Engineering & Intelligent Systems:
https://www.academia.edu/50351243/NON_FUNCTIONAL_REQUIREMENTS_AS
_CONSTRAINTS_AND_THEIR_VALUES_IN_SOFTWARE_DEVELOPMENT_A_REVIE
W

Catherine Courage, K. B. (2005). Understanding Your Users: A Practical Guide to User

Requirements Methods, Tools, and Techniques. San Francisco, CA: Morgan
Kaufmann Publishers (an imprint of Elsevier). Retrieved from
https://books.google.lk/books?hl=en&lr=&id=bZ__HjU20hEC&oi=fnd&pg=PR23&
dq=what+is+the+user+requirements&ots=Xk78eJZZg9&sig=iEOVeOlsyMMHTj9N
7p80p3-
Zdh4&redir_esc=y#v=onepage&q=what%20is%20the%20user%20requirements
&f=false

Dancuk, M. (2021, May 13). Database Types Explained. Retrieved from phoenix NAP
Web site: https://phoenixnap.com/kb/database-types

Dancuk, M. (2021, May 26). What is Database Normalization? Retrieved from phoenix
NAP Web site: https://phoenixnap.com/kb/database-normalization#ftoc-
heading-1

Das, S. (2024, Septemper 22). NFRs: What is Non Functional Requirements (Example &
Types). Retrieved from Browserstack Web site:
https://www.browserstack.com/guide/non-functional-requirements-
examples#:~:text=Non-
Functional%20Requirements%20%28NFRs%29%20are%20specifications%20th
at%20define%20how,operation%2C%20including%20performance%2C%20sec
urity%2C%20usability%2C%20reliability%2C

David T. Bourgeois. (2014). Information System for Business and Beyond. n.d.: The
Saylor Academy. Retrieved from
https://resources.saylor.org/wwwresources/archived/site/textbooks/Information
%20Systems%20for%20Business%20and%20Beyond.pdf#page=9&zoom=100,0
,76

Department of Computer Science, University of Cape Town. (n.d., n.d. n.d.). Chapter 8:
Data Normalization. Retrieved from University of Cape Town Web Site:
https://www.cs.uct.ac.za/mit_notes/database/pdfs/chp08.pdf

Geeks for Geeks. (2024, Septemer 19). Database Schemas. Retrieved from Geeks for
Geeks Web site: https://www.geeksforgeeks.org/database-schemas/

Page | VI
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01
GeeksforGeeks. (2023, November 6). Degree of Relations in DBMS. Retrieved from
GeeksforGeeks Web site: https://www.geeksforgeeks.org/degree-of-relations-in-
dbms/

Huawei Technologies Co., Ltd. (2022, October 22). Database Design Fundamentals.
Retrieved from Springer Web site:
https://link.springer.com/chapter/10.1007/978-981-19-3032-4_7#DOI

Marijan, B. (2021, May 20). 12 Best Coloud Databases. Retrieved from phoenix NAP Web
site: https://phoenixnap.com/kb/cloud-database

Nishadha. (2024, March 23). What is an Entity Relationship Diagram (ERD)? | An

Introduction to ER Diagram. Retrieved from Creately Web site:
https://creately.com/guides/er-diagrams-tutorial/

OpenDSA. (n.d., n.d. n.d.). ERD Basic Components. Retrieved from OpenDSA Web site:
https://opendsa-
server.cs.vt.edu/ODSA/Books/Database/html/ERDComponents.html#

Tutorials Point. (n.d., n.d. n.d.). DBMS - ER Model Basic Concepts. Retrieved from
Tutorials Point Web site:
https://www.tutorialspoint.com/dbms/er_model_basic_concepts.htm

Tutorials Point. (n.d., n.d. n.d.). DBMS - Overview. Retrieved from Tutorials Point Web
site: https://www.tutorialspoint.com/dbms/dbms_overview.htm

UCSB Computer Science Department. (2023, n.d. n.d.). CS189A Capstone: Lecture 4 -
Requirements Specification. Retrieved from UCSB Computer Science Web site:
https://sites.cs.ucsb.edu/~capstone/cs189a/l4.pdf

Page | VII
P. Kirushan Unit 04 – Database Design & Development Assignment No - 01