Data Analysis and Design: Dominican College Database System

This report delves into the design and implementation of a relational database system for Dominican College. It explores various data models, database technologies, and normalization techniques. The report also covers the creation of user documentation, testing procedures, and the implementation of control mechanisms to ensure data integrity and security. The report provides a comprehensive overview of the database design process, from conceptualization to implementation and testing.

Data Analysis and Design

Table of Contents
Introduction......................................................................................................................................4
LO1 Understand data models and database technologies................................................................5
1.1 Critically compare different data models and schemas.........................................................5
1.2 Critically discuss the benefits and limitations of different database technologies................9
1.3 Analyse different approaches to database design................................................................11
LO2 Be able to design and implement relational database systems..............................................15
2.1 Design a relational database system to meet a given requirement......................................15
2NF (second normal form):.......................................................................................................17
2.2 Build a relational database system based on a prepared design..........................................19
2.3 Apply a range of database tools and techniques to enhance the user interface...................21
LO3 Be able to use manipulation and querying tools....................................................................22
3.1 Explain the benefits of using manipulation and query tools in a relational database system
...................................................................................................................................................22
3.2 Implement a query language into the relational database system........................................23
3.3 Critically evaluate how meaningful data has been extracted through the use of query tools
...................................................................................................................................................39
LO4 Be able to test and document relational database systems....................................................43
4.1 Critically review and test a relational database system.......................................................43
4.2 Create documentation to support the implementation and testing of a relational database
system........................................................................................................................................44
4.3 Create user documentation for a developed relational database system..............................47
4.4 Explain how verification and validation has been addressed..............................................52
4.5 Explain how control mechanisms have been used..............................................................53
Conclusion.................................................................................................................................55
References:................................................................................................................................56
Appendix........................................................................................................................................57
1

List of Figures
Figure 1 Network data model..........................................................................................................5
Figure 2 Hierarchical database model.............................................................................................6
Figure 3 Object-oriented database model........................................................................................6
Figure 4 Relational database model.................................................................................................7
Figure 5 Database schema with 3 layers..........................................................................................8
Figure 6 Relationship diagram.......................................................................................................15
Figure 7 ER diagram......................................................................................................................16
Figure 8 Design view of academic manager table.........................................................................19
Figure 9 Design view of admin table.............................................................................................19
Figure 10 Design view of course table..........................................................................................19
Figure 11 Design view of lecturer table........................................................................................19
Figure 12 Design view of student table.........................................................................................20
Figure 13 Design view of units table.............................................................................................20
Figure 14 Query 1 design view......................................................................................................23
Figure 15 Query 1 output view......................................................................................................23
Figure 16 Query 1 report view.......................................................................................................24
Figure 17 Query 2 design view......................................................................................................25
Figure 18 Query 2 output view......................................................................................................25
Figure 19 Query 2 report view.......................................................................................................26
Figure 20 Query 3 design view......................................................................................................27
Figure 21 Query 3 output view......................................................................................................27
Figure 22 Query 3 report view.......................................................................................................28
Figure 23 Query 4 design view......................................................................................................29
Figure 24 Query 4 output view......................................................................................................29
Figure 25 Query 4 report view.......................................................................................................30
Figure 26 Query 5 design view......................................................................................................31
Figure 27 Query 5 output view......................................................................................................31
Figure 28 Query 5 report view.......................................................................................................32
Figure 29 Query 6 design view......................................................................................................33
Figure 30 Query 6 output view......................................................................................................33
Figure 31 Query 6 report view.......................................................................................................34
Figure 32 Query 7 design view......................................................................................................35
Figure 33 Query 7 output view......................................................................................................35
Figure 34 Query 7 report view.......................................................................................................36
Figure 35 Query 8 design view......................................................................................................37
Figure 36 Query 8 output view......................................................................................................37
Figure 37 Query 8 report view.......................................................................................................38
Figure 38 SQL view of admin query.............................................................................................39
Figure 39 Output view of admin query..........................................................................................39
2

Figure 40 SQL view of academic manager query.........................................................................39
Figure 41 Output view of academic manager query......................................................................40
Figure 42 SQL view of college admin query.................................................................................40
Figure 43 Output view of college admin query.............................................................................41
Figure 44 SQL view of student query............................................................................................41
Figure 45 Output view of student query........................................................................................42
Figure 46 Test case 1.....................................................................................................................44
Figure 47 Test case 2.....................................................................................................................45
Figure 48 Test case 3.....................................................................................................................45
Figure 49 Test case 4.....................................................................................................................45
Figure 50 Test case 5.....................................................................................................................46
Figure 51 Academic manager form...............................................................................................47
Figure 52 Admin form...................................................................................................................47
Figure 53 Course form...................................................................................................................47
Figure 54 Lecturer form.................................................................................................................48
Figure 55 Student form..................................................................................................................48
Figure 56 Unit form.......................................................................................................................49
Figure 57 Academic manager form report.....................................................................................49
Figure 58 Admin form report........................................................................................................50
Figure 59 Course form report........................................................................................................50
Figure 60 Student form report.......................................................................................................51
Figure 61 Validation On lecturer phone no...................................................................................52
Figure 62 Control mechanism for admin table..............................................................................53
Figure 63 Control mechanism for admin table in course id..........................................................54
List of Tables
Table 1 Un normalized table..........................................................................................................12
Table 2 First NF form....................................................................................................................12
Table 3 Second (1) NF...................................................................................................................12
Table 4 Second(2) NF....................................................................................................................12
Table 5 Third (1) NF......................................................................................................................13
Table 6 Third (2) NF......................................................................................................................13
Table 7 Third (3) NF......................................................................................................................13
Table 8 First normal form table of database..................................................................................17
Table 9 Second normal form of database......................................................................................17
Table 10 Third normal form of database.......................................................................................18
Table 11 Feedback table by different users...................................................................................43
Table 12 Test cases table...............................................................................................................44
3

Introduction
Database design is the design process of the database and recognize the general basics of the
database system. For designing the database MS Access framework is used. The detailed
description of this report will generate for Dominican college database system. In this
assignment, the assignment is divided into four tasks. Different database technologies and
diverse methods for the creation of a database model are deliberated. In this, it will also contain
the information of normalization, verifications, and requirements of database and the
documentation for user which helps the operator to access and practise the database. It also
contains the detail of query language. In last part of the report the diverse test cases, test plans
and the user feedback are described.
4

LO1 Understand data models and database technologies
1.1 Critically compare different data models and schemas
Database management system: It is the software for a computer that can communicate with an
application, database, End-user for the analysis and for collecting data. Database management
system will allow database administrator to update, define, creation of database. Database will
contain information which can be managed by a database administrator. Different types of
database are network database, object-oriented, relational, hierarchical database.
Network database: This model contains a logical type of database. In this model, the connection
is contained among the nodes, their direction and the node cost. This type of database is
completed extremely because many-to-many relationship contains in between the nodes for the
one record that can be used by entire database.
Figure 1 Network data model
Source: (tutorial4begineer, 2018)
Advantages:
 It can be handled by several kinds of relationship.
 Data integrity and access flexibility are there in this.
Disadvantages:
 In this the complex system is present
 Complex to maintain the links.
Hierarchical database model: This model forms a tree-like structure which can be contained by
one to numerous type relationships. One parent is behaving as a root which is the top node. It is a
physical type of database which can be used for storing the information.
5

Advantages:
 Used for sharing the data.
 It offers a secure database.
Disadvantages:
 Some limitation is faced by the time of implementation of database.
 In-depth the hierarchical knowledge is required.
Figure 2 Hierarchical database model
Source: (tutorial4begineer, 2018)
Object-oriented database model: This kind of database can store the data in the form of
objects. The object-oriented languages like C++, JAVA, and others.
Figure 3 Object-oriented database model
Source: (tutorial4begineers, 2018)
6

Advantages:
 According to the need of user, the data type can be defined.
 It can save the method of data automated.
Disadvantages:
 Without the knowledge of OOPS, the user cannot use.
 It uses the poor reporting and querying tool.
Relational database: It can be widely used for data storage and processing. It stores the data in
table format where row defines the record and in a column, the attributes are defined.
Advantages:
 For database design, it can use a simple concept.
 For integration of data it can provide a communication in a effective manner.
Disadvantages:
Figure 4 Relational database model
Source: (Parker, 2009)
Database schema: It uses the three-layer structural design where individual level is vital on
behalf of the company. In table format, the data are stored and show the relations with the
different table present in database.
7

Figure 5 Database schema with 3 layers
Source: (LearnSoftwareDevelopment, 2009)
External level: In this, the different views for user are defined. It can use the physical data type
for the recognition of function in database. The feature is:
 SQL & MySQL are supported in the client query.
 The normalization process can be performed by a client or also by the user.
Internal level: It can be used for defining the database that can be used in an intelligent manner
so the developer and engineers which users can understand easily.
 All characteristic is explained.
 Elements & relationship are contained.
Conceptual level: In the user will use the concept of data model for the implementation. It has
some key feature that is:
 In this, the database connections and also the elements are not specified.
 The qualities are not defined in this.
8

1.2 Critically discuss the benefits and limitations of different database technologies
Database: It can be defined as a set of information, data, & records. It can be used for storing the
client-server and server information like documents, files, and also the records in a database. The
different type of database is explained here with their limitations & benefits are:
Multimedia Database: This can be highly used for storing multimedia information in a database
like images, videos.
Benefits:
 It will be user-friendly.
 This type of database can offer a large no. of styles for learning like auditory learning,
visual learning.
Imitations:
 Several types of compatibility issues are faced in this.
 For downloading the data, it can be depending on the web.
Cloud computing: It is the online type of database in which the data are stored on the internet.
Benefits
 The cost is low for the cloud software.
 Maintenance issue is not present.
Imitations:
 The speed is low with the comparison with the other type of database.
 The feature is limited in this type.
Relational database: It stores the data into the table format.
Benefits: It is flexible in use.
 Its implementation is also flexible and also very easy to understand.
Imitations: The design is poor in visual and also implementation poor.
 Hardware & software overhead is present in the relational database.
File-based database: In this, the files on the devices are accessed with the help of a database.
Benefits:
9

 It can use a simple concept.
 It can allow a sharing remotely.
Imitations:
 It is the database which is dependent on application database.
 The user view demonstration s difficult.
Data warehousing: This database can use a data reporting and also the data analyzing technique.
This stores the data in an annual or quarterly manner that can be used for the organizing and
report the data management.
Benefits:
 The data can be stored in a cleaner manner.
 The security can be provided for the data with the access.
Imitations:
 The database is expensive for using.
 This is a time consuming for implementing the data.
10

1.3 Analyse different approaches to database design
Database design approaches are described:
Top-Down approach:
This type is used globally for the designing the database. It can be developed by using the
scratch. The ER is the example of this type of approach because the complex outline of the
database is created.
Modelling the ER process:
It is the collection of entities. The relationships are also present in many entities in database
which allow developer to design the sketch in a very easy manner. It can be of 2 types the
concepts and the logical ER in concept the relationships with the entities are define and in the
logical the logical design of database is present.
Entity: It represents in a rectangular format where the database is in the table form.
Attribute: This can be represented in the oval that can be the property of the entity in the design.
It can be simple, derived, single value, multi-value, and composite attribute type.
Relationship: This represents the diamond symbol. This shows the relations between the entities
in a design.
Bottom-Up approach:
This is a common method of selection for the global schema description that can be used. This
converts the database in the form of local schema. This defines the connection and the element in
the database. The example of the bottom-up is normalization because it describes the relationship
of the database. (Burleson, 2018)
Normalization Process:
For removing the redundant data from the database the normalization process can be used. This
can be used to reduce the complexity so that throughput of accessing the data is improved. The
normalization process provides integrity and consistent data in the table of database.
Un-Normalization Process:
It has the set of rules which are:
 Table column will not contain the element in a left to right manner.
 Not containing the element in table in a top to down manner.
 Duplication data are not present in the rows.
11

Table 1 Un normalized table
1 NF: It forms the table in an atomic manner. The duplication is removed in this table.
Table 2 First NF form
2 NF: The table should present in 1 NF form and the partial dependency is removed in this.
Table 3 Second (1) NF
Table 4 Second(2) NF
12

3 NF: 3NF where table is already in 2 NF form and transitive dependency is removed.
Table 5 Third (1) NF
Table 6 Third (2) NF
Table 7 Third (3) NF
I have used the top-down approach for designing a database because it provides the security and
the implementation is also easy. And accessing the data in this is easy.
Data Dictionary:
Entity names Attributes Attributes data type Primary
key
Foreign key Description
Student_table  Sid
 Name
 Email
 Phone
 address
 number
 text
 text
 number
 text
 yes
 no
 no
 no
 no
 no
 no
 no
 no
 no
Student
details in
database
Units_table  uid
 name
 number
 text
 yes
 no
 no
 no
Units detail
in the
13

 cid
 year
 number
 number
 no
 no
 yes
 no
database
Course_table  cid
 name
 campus
 fees
 number
 text
 text
 currency
 yes
 no
 no
 no
 no
 no
 no
 no
Course
details in the
database
Lecturer_table  tid
 email
 name
 phone
 address
 number
 text
 text
 number
 text
 yes
 no
 no
 no
 no
 no
 no
 no
 no
 no
Lecturer
detail in the
database
Admin_table  sid
 cid
 course_ty
pe
 Number
 Number
 Text
 No
 No
 No
 Yes
 Yes
 No
Academic
manager_table
 Tid
 uid
 number
 number
 no
 no
 yes
 yes
Academic
manager
data are
saved in the
database
14

LO2 Be able to design and implement relational database systems
2.1 Design a relational database system to meet a given requirement
ERD diagram:
The ERD diagram represent the graphical representation in between the relationship of data
entities available in the database. It will also show the attributes which are related to that entity.
It can be represented in the two ways conceptual and the graphical diagram. Both the form
represents data into graphical way.
Entities: In this how entities in the database are linked to one another are defined. In nature, all
the entities are different in their form. It can be represented by the rectangular form of boxes.
Attributes: For a specific entity a specific set of properties are defined for the entity are called
attributes. This can be represented by the ovals.
Relationships: It will always exist in between the entities present in the database. It is either one
to one, or one to many, and also many to many types. It shows in the form of tilt square like a
diamond.
15

Figure 6 Relationship diagram
16

Figure 7 ER diagram
17

1NF (First normal form):
In this, the attributes in the table should be followed atomicity no duplicity is present. And also
check that the element should be in atomic form. This can be used to remove the dependency.
Table 8 First normal form table of database
Acad_manager Admin Couse
Tid Sid cid
Uid Student_Email Name
Lecturer_ Email Course_type Campus
Lecturer_phone Student_sid Fees
Lecturer_tid Student_phone Units_name
Lecturer_name Student_address Unit_year
Lecturer_address Student_Name Unit_cid
2NF (second normal form):
For the table should come under 2 NF form it should be pass through 1 NF properly and the
partial dependency are removed.
Table 9 Second normal form of database
Acad_manager Admin Couse
Tid Sid cid
Uid cid Name
Course_type Campus
Fees
Lecturer Student Unit_year
Tid Sid Unit_cid
Name Name unit_name
Email Email
Phone Address
Address Phone
3NF (Third normal form): For this normalization process the table should pass through 1NF &
2NF forms. In this form, the referential or transitivity are removed when reference column is not
dependent upon the primary key.
18

Table 10 Third normal form of database
Acad_manager Admin Couse
Tid Sid cid
Uid cid Name
Course_type Campus
Fees
Lecturer Student Units
Tid Sid Unit
Name Name Name
Email Email cid
Phone Address Year
Address Phone
19

2.2 Build a relational database system based on a prepared design
Design view of table:
Design view of tables means that the with attributes of table through his data types. In the table
all info of attributes are defined which are shown in the design view of tables:
Figure 8 Design view of academic manager table
Figure 9 Design view of admin table
Figure 10 Design view of course table
20

Figure 11 Design view of lecturer table
Figure 12 Design view of student table
Figure 13 Design view of units table
21

2.3 Apply a range of database tools and techniques to enhance the user interface
For enhancing the GUI of the database the MS Access is used that contains several components:
i.e. relationships, forms, tables, reports, macros, queries and modules.
MS Access feature is:
a) For each user, it is better.
b) By using MS Access, the files are easily export and import.
c) The templates which are present already can be used.
d) There is help feature in MS Access.
e) For the web, the database is easily created.
f) In PDF the report is easily created in MS Access.
g) The validation is used in the database for security.
h) For ribbon, it will show and hide the options.
i) It will allow user to eliminate and view the reports which are extra.
22

LO3 Be able to use manipulation and querying tools
3.1 Explain the benefits of using manipulation and query tools in a relational
database system
Data Manipulation:
In data manipulation, the data are altered by either select, delete, update, and insert in database.
This technique can be used to delete or insert data in the table. It can be used by the web server
that helps the owner of website to manage data that could take help of a relational type of
database.
Query language:
It can be used to retrieve the information from the database. By using this the records can
retrieve easily from the database and display
Aggregate function:
It is the type of function which the value in database can together group by using little condition
that produces one result by using the function. The different aggregate functions are:
 MIN (): displays minimum value from database.
 COUNT (): total no. row are displayed.
 MAX (): display maximum value from database.
 SUM (): addition of all data display.
 AVG (): The average of all data is displayed.
23

3.2 Implement a query language into the relational database system
Query1
College admin should view the course detail and units that are provided by the college will be
displayed.
Query 1 SQL view
Query 1 design view
Figure 14 Query 1 design view
Query 1 output view
Figure 15 Query 1 output view
24

Query 1 report view
Figure 16 Query 1 report view
Query2
Display those details of lectures who will teach the different unit types and students. So that
academic manager will view the details.
Query 2 SQL view
Query 2 design view
25

Figure 17 Query 2 design view
Query 2 output view
Figure 18 Query 2 output view
Query 2 report view
26

Figure 19 Query 2 report view
Query 3:
College admin should view a particular student who is taken a course with the unit and the
lecturer who teach them.
Query 3 SQL view
Query 3 design view
27

Figure 20 Query 3 design view
Query 3 output view
Figure 21 Query 3 output view
Query 3 report view
28

Figure 22 Query 3 report view
Query 4:
Student should be able to view the particular course taken and the fees of the course.
Query 4 SQL view
Query 4 design view
29

Figure 23 Query 4 design view
Query 4 output view
Figure 24 Query 4 output view
Query 4 report view
30

Figure 25 Query 4 report view
Query 5:
Academic manager should be able to list down student who are study the specific courses.
Query 5 SQL view
Query 5 design view
31

Figure 26 Query 5 design view
Query 5 output view
Figure 27 Query 5 output view
Query 5 report view
32

Figure 28 Query 5 report view
Query 6:
The lecturer should be able to list down the course detail in which what tutor teach the specific
course and
Query 6 SQL view
Query 6 design view
33

In which unit are displayed.
Figure 29 Query 6 design view
Query 6 output view
Figure 30 Query 6 output view
34

Query 6 report view
Figure 31 Query 6 report view
Query 7:
As per the request of lecturer the course which they study are shown with the unit and to whom
student should be displayed in the query.
Query 7 SQL view
SELECT couse.name AS COURSE, lecturer.name AS TUTOR, stud.name AS STUDENT,
units.name AS UNIT
FROM lecturer, stud, couse INNER JOIN units ON couse.cid = units.cid;
Query 7 design view
35

Figure 32 Query 7 design view
Query 7 output view
Figure 33 Query 7 output view
Query 7 report view
36

Figure 34 Query 7 report view
Query 8:
College admin should be able to assign a course to lecturer and which student study should be
displayed in that.
Query 8SQL view
Query 8 design view
37

Figure 35 Query 8 design view
Query 8 output view
Figure 36 Query 8 output view
38

Query 8 report view
Figure 37 Query 8 report view
39

3.3 Critically evaluate how meaningful data has been extracted through the use of
query tools
Query 1: In the below admin query the admin needs to list down the course detail and the unit
detail of all the available in database.
Figure 38 SQL view of admin query
Figure 39 Output view of admin query
Query 2: In the academic manager query below the needs to list down all the available courses in
which what unit it is and what lecturer teach that particular course from the database.
Figure 40 SQL view of academic manager query
40

Figure 41 Output view of academic manager query
Query 3: In the below query the college admin wants to show the particular student which learn
what subject what tutor teach them and what is the unit of each student the details and the query
are shown below.
Figure 42 SQL view of college admin query
41

Figure 43 Output view of college admin query
Query 4: In the below query the student needs to see that student which study the particular
course and what is the fees of each course so in this the student with the course and fees are
shown below.
Figure 44 SQL view of student query
42

Figure 45 Output view of student query
43

LO4 Be able to test and document relational database systems
4.1 Critically review and test a relational database system
The review from users of different types is taken to check the database. Feedback table is
generated for these users are:
Table 11 Feedback table by different users
Questionnaire User 1 User 2 User 3
Database usability? Simple Easy Hard
How often is database
use?
Always Regularly Not always
Are you referring the
database to others?
Yes Not with all No
Review on security of
database?
Security is high Secure Not much secure
Overall review of the
database (out of 10)
9.5 8.5 7
44

4.2 Create documentation to support the implementation and testing of a relational
database system
The database of Dominican college management system is tested with different test cases which
are described in this part:
Table 12 Test cases table
Sr. No. Test case Expected Result Actual Result
1. ID column value Display error Error shown.
2 The currency value
should contain a
numeric value
The error should
show if numeric
value is not there
Error shown.
3 In lecture phone the
value in numeric
If value is not
numeric then pop
up error box has
to appear.
Error shown.
4 The primary id key
value should not leave
blank.
If column is blank
error display
Error shown.
5 Inserted value should
be incorrect format.
Display error Error shown.
Figure 46 Test case 1
45

Figure 47 Test case 2
Figure 48 Test case 3
Figure 49 Test case 4
46

Figure 50 Test case 5
47

4.3 Create user documentation for a developed relational database system
It can be made so that user can take help from this. In the documentation, the user can guide
from this so it can know how the product & services are used. It can guide with proper assistance
and product guide that how to use the product.
Figure 51 Academic manager form
Figure 52 Admin form
Figure 53 Course form
48

Figure 54 Lecturer form
Figure 55 Student form
49

Figure 56 Unit form
Figure 57 Academic manager form report
50

Figure 58 Admin form report
Figure 59 Course form report
51

Figure 60 Student form report
52

4.4 Explain how verification and validation has been addressed
Verification:
For checking the inconsistency into the database it can be used if it found inconsistent then it
should be verified. It can also be used when the data transfer between different computer device
should take place.
Validation:
To check quality in data which is injected in database the validation is used. With the help of
these the consistency, correctness of data is checked. The rules are set in database and according
to the rule of validation, the injected data into database. And if the problem arises in this by the
condition then the data are not injected into database. (Woodward, 2008)
Figure 61 Validation On lecturer phone no.
In this the phone no. should not contain the text field in it should only contain the numeric value
if not then error is generated.
53

4.5 Explain how control mechanisms have been used
In the below admin table the sid which is student ID should have long integer field size. And in
admin table, there is no primary key so duplicate entries are allowed. It contains cid, sid and the
course_type.
Figure 62 Control mechanism for admin table
54

Figure 63 Control mechanism for admin table in course id
In the above diagram, the admin table the cid which is course id should have long int as field
size. It should contain the duplicate entries in table because it is not the primary key.
55

Conclusion
The database of Dominican college is generated in the MS Access. In this report the assignment
is discussed briefly of different models of database, technologies of database and also the
different approaches for developing the database by using the data models are discussed. This
also describes the data manipulation language techniques like inserting, deleting, updating, etc.
Query language and their tools are discussed. This also describes the requirements of user and
the documentation so that user will use database efficiently by using the report. The ERD
diagrams, normalizations tables, a conceptual diagram of database are discussed in this report.
The different test cases with the database and different queries are described in this assignment
report.
56

References:
 Burleson.D, (2018). Top-down vs. Bottom-Up Object Database Design . [online] Available
at: http://www.dba-oracle.com/t_object_top_down_bottom_up.htm [Accessed 19 May 2018].
 EDUCBA. (2016). 10 Powerful Features Of Microsoft Access | edu CBA. [online] Available
at: https://www.educba.com/10-powerful-features-of-microsoft-access/ [Accessed 19 May
2018].
 Guru99.com, (2018). [online] Available at: https://www.guru99.com/database-
normalization.html [Accessed 19 May 2018].
 Learn Software Development, (2009). DBMS Three-Schema Architecture and Data
Independence. [online] Available at: http://learnsoftwareprocesses.com/2009/08/05/dbms-
three-schema-architecture-and-data-independence/ [Accessed 19 May 2018].
 Parker, P. (2009). Relational Databases Homework Help, Relational Databases Online Help,
Relational Databases Tutor. [online] Urgent homework. Available at:
http://www.urgenthomework.com/relational-database-homework-help [Accessed 26 Mar.
2018].
 Relationaldbdesign.com, (2018). Three Schema Architecture | Database Life Cycle and
Relational Database Design. [online] Available at:
https://www.relationaldbdesign.com/relational-database-design/module3/schema-
architecture.php [Accessed 19 May 2018].
 Studytonight.com, (2018), 1NF, 2NF, 3NF and BCNF in Database Normalization |
Studytonight. [online] Available at: https://www.studytonight.com/dbms/database-
normalization.php [Accessed 19 May 2018].
 Tutorial4beginners.com, (2018). Types of Database Models. [online] Available at:
http://www.tutorial4beginners.com/dbms-types-of-database-models [Accessed 19 May
2018].
 Woodward, (2008). Data validation & verification – Greenspace Information for Greater
London. [online] Available at: http://www.gigl.org.uk/data-validation-verification/ [Accessed
19 May 2018].
57

Appendix
58