Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title BTEC Higher National Diploma in Computing

Assessor Internal
Verifier
Unit(s) Unit 04: Database Design & Development

Assignment title Database Solution for Polly Pipe

G.Ishanka Anuruddha Nandasiri

Student’s name

List which assessment Pass Merit Distinction

criteria the Assessor has
awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded
match those shown in the Y/N
assignment brief?
Is the Pass/Merit/Distinction grade
awarded justified by the assessor’s
Y/N
comments on the student work?

Has the work been assessed

Y/N
accurately?
Is the feedback to the student:
Give details:
• Constructive? Y/N
• Linked to relevant assessment Y/N
criteria? Y/N
• Identifying opportunities for
improved performance? Y/N
• Agreeing actions?
Does the assessment decision need
Y/N
amending?
Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if
Date

Ishanka Anuruddha | Database Design and Development | Page 1

 required)

Confirm action completed

Remedial action
taken
Give details:
Assessor signature Date

Internal
Date
Verifier
signature
Programme
Date
Leader signature
(if required)

Ishanka Anuruddha | Database Design and Development | Page 2

Higher Nationals - Summative Assignment Feedback Form

Student Name/ID G.Ishanka Anuruddha Nandasiri (0012805)

Unit Title Unit 04: Database Design & Development

Assignment 1 Assessor
Number
Date
Submission Date
Received 1st
submission
Date Received 2nd
Re-submission Date
submission
Assessor Feedback:
LO1 Use an appropriate design tool to design a relational database system for a
substantial problem
Pass, Merit & P1 M1 D1
Distinction Descripts

LO2 Develop a fully functional relational database system, based on an existing system
design
Pass, Merit & P2 P3 M2 M3
Distinction Descripts D2

LO3 Test the system against user and system requirements.

Pass, Merit & P4 M4 D2
Distinction Descripts

LO4 Produce technical and user documentation.

Pass, Merit & P5 M5 D3
Distinction Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once internal and
external moderation has taken place and grades decisions have been agreed at the assessment
board.

Ishanka Anuruddha | Database Design and Development | Page 3

Assignment Feedback

Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Ishanka Anuruddha | Database Design and Development | Page 4

Feedback: Student to Assessor

Assessor Date
signature

Student signature Date

Pearson Higher Nationals in

Computing

Unit 04: Database Design & Development

Assignment 01

Ishanka Anuruddha | Database Design and Development | Page 5

General Guidelines

1. A Cover page or title page – You should always attach a title page to your
assignment. Use previous page as your cover sheet and make sure all the details are
accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.

Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.

Ishanka Anuruddha | Database Design and Development | Page 6

 4. Use footer function in the word processor to insert Your Name, Subject,
Assignment No, and Page Number on each page. This is useful if individual sheets
become detached for any reason.
5. Use word processing application spell check and grammar check function to help
editing your assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the
compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in
the body except for the before mentioned compulsory information will result in
rejection of your work.
2. Carefully check the hand in date and the instructions given in the assignment. Late
submissions will not be accepted.
3. Ensure that you give yourself enough time to complete the assignment by the due
date.
4. Excuses of any nature will not be accepted for failure to hand in the work on time.
5. You must take responsibility for managing your own time effectively.
6. If you are unable to hand in your assignment on time and have valid reasons such as
illness, you may apply (in writing) for an extension.
7. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
8. Non-submission of work without valid reasons will lead to an automatic RE
FERRAL. You will then be asked to complete an alternative assignment.
9. If you use other people’s work or ideas in your assignment, reference them properly
using HARVARD referencing system to avoid plagiarism. You have to provide both
in-text citation and a reference list.
10. If you are proven to be guilty of plagiarism or any academic misconduct, your grade
could be reduced to A REFERRAL or at worst you could be expelled from the course

Ishanka Anuruddha | Database Design and Development | Page 7

Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to
present it as my own without attributing the sources in the correct form. I further understand
what it means to copy another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.

2. I understand the plagiarism and copying policy of Edexcel UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any of
the assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will
be my own, and where I have made use of another’s work, I will attribute the source
in the correct way.
5. I acknowledge that the attachment of this document signed or not, constitutes a
binding agreement between myself and Pearson, UK.
6. I understand that my assignment will not be considered as submitted if this document
is not attached to the assignment.

[email protected]

Student’s Signature: Date:20/08/2022

(Provide E-mail ID) (Provide Submission Date)

Ishanka Anuruddha | Database Design and Development | Page 8

Higher National Diploma in Computing

Assignment Brief

Student Name /ID Number G.Ishanka Anuruddha Nandasiri (0012805)

Unit Number and Title Unit 4: Database Design & Development

Academic Year 2022/23

Unit Tutor

Assignment Title Data base system for Polly Pipe

Issue Date

Submission Date 20/08/2022

IV Name & Date

Submission format

Part 1: The submission should be in the form of an individual written report written in a concise,
formal business style using single spacing and font size 12. You are required to make use of
headings, paragraphs and subsections as appropriate, and all work must be supported with
research and referenced using Harvard referencing system. Please also provide in-text citation
and bibliography using Harvard referencing system. The recommended word limit is 3,000–
3,500 words, although you will not be penalised for exceeding the total word limit.
Part 2: The submission should be in the form of a fully functional relational database system
demonstrated to the Tutor; and an individual written report (please see details in Part 1 above).
Part 3: The submission should be in the form of a witness statement of the testing completed by
the Tutor; technical documentation; and a written report (please see details in Part 1 above).
Unit Learning Outcomes:

LO1 Use an appropriate design tool to design a relational database system for a substantial
problem.
LO2 Develop a fully functional relational database system, based on an existing system
design.
LO3 Test the system against user and system requirements.
LO4 Produce technical and user documentation.
Assignment Brief and Guidance:

Ishanka Anuruddha | Database Design and Development | Page 9

 Assignment brief

Installation Installatio Installatio Custome Equipment Types of Period

ID n Type n Name r Staff of Staff
and Required assignm
Address ent

Polly Pipe is a water sports provider and installer based in Braintree, England. They need you
to design and implement a database that meets the data requirements. These necessities are
defined in this scenario and below are samples of the paper records that the Polly Pipe
preserves.

Polly Pipe is focused in placing aquariums at business customers. Customers can request
several installations, but each installation is tailor-made for a specific customer. Facilities are
classified by type. One or more employees are assigned to each facility. Because these
facilities are often very large, they can include carpenters and masons as well as water
installers. The facilities use equipment such as aquariums, air pumps and thermostats. There
can be multiple computers in a facility.

Below are examples of paper records that Polly Pipe currently maintains.

Staff Management Record

Staff Number Name Type
SHA1 Dave Clark Plumber
SHA8 John Smith Installation Manager
SHA2 Freddy Davies Aquatics installer
SHA11 McCloud Aquatics installer
SHA23 Satpal Singh Plumber
SHA66 Winstn Kodogo Aquatics installer
SHA55 Alison Smith Brick Layer

Equipment Type Table

Type Equipment
Tanks 20 gallon tank, 50 gallon tank, 100
gallon tank, 200 gallon tank
Thermostats Standard, Super
Air Pumps Standard, Super
Filters Air driven, Undergravel

Ishanka Anuruddha | Database Design and Development | Page 10

 234 Freshwate Oak Lee A. 2 air 1 x Carpenter From
r Tropical House, 17 sun pumps 1 x Aquatics 1st
Wroxton 200 installer Septemb
Road, gallons 1x er 2012
Hertfordsh fish tank Electrician
ire, H5 1x
667 standard
thermostat
654 Freshwate Bayliss Sally 2 air 5x 1st June
r Cold House, Dench pumps Carpenters 2005 –
Orange 200 1x 1st June
Street, gallons Installation 2011
Kent, K7 fish tank Manager
988 Large 1 x Aquatics
Gravel installer
Bag 1 x Plumber
2x 3 x Labourers
standard
thermostat
s
767 Marine Eaglestone Perry 2 x 200 10 x From
Castle, Vanderru gallons Carpenters 30th
Eaglestone ne fish tanks 2x June
, Kent 500 Wood Installation 2012
panels Manager
1 x Aquatics
installer
1 x Plumber
3 x Labourers
943 Marine 23 Eric 2 air No staff required
Sackville Mackint pumps
Street, osh 200
Wilts. gallons
W55 fish tank
1x
standard
thermostat
157 Freshwate Humberts Perry 2 air 1 x Aquatics 1st
r Tropical on Castle, Vanderru pumps installer Septemb
Kent, K8 ne 400 er 2005
gallons – 1st
fish tank Septemb
3x er 2012
standard
thermostat
Instillation Management Form

Ishanka Anuruddha | Database Design and Development | Page 11

 Activity 1
1.1.Identify the user and system requirements to design a database for the above scenario
and design a relational database system using conceptual design (ER Model) by
including identifiers (primary Key) of entities and cardinalities, participations of
relationships. Convert the ER Model into logical database design using relational
database model including primary keys foreign keys and referential Integrities. It should
contain at least five interrelated tables. Check whether the provided logical design is
normalised. If not, normalize the database by removing the anomalies.

(Note:-It is allowed to have your own assumptions and related attributes within the scope
of the case study given)

1.2. Design set of simple interfaces to input and output for the above scenario using
Wireframe or any interface-designing tool. Evaluate the effectiveness of the given design
(ERD and Logical design) in terms of the identified user and system requirements .

Activity 2
Activity 2.1
a. Develop a relational database system according to the ER diagram you have created
(Use SQL DDL statements). Provide evidence of the use of a suitable IDE to create
a simple interface to insert, update and delete data in the database. Implement proper
security mechanisms in the developed database.
Evaluate the database solution developed and its effectiveness with relevant to the
user and system requirements identified, system security mechanisms (EX: -User
groups, access permissions) and the maintenance of the database.
Activity 2.2
a. Explain the usage of DML with below mentioned queries by giving at least one
single example per each case from the developed database. Assess the usage of the
below SQL statements with the examples from the developed database to prove that
the data extracted through them are meaningful and relevant to the given scenario.
Select/ Where / Update / Between / In / Group by / Order by / Having

Activity 3
Activity 3.1
Provide a suitable test plan to test the system against user and system requirements. provide
relevant test cases for the database you have implemented. Assess how the selected test data
Ishanka Anuruddha | Database Design and Development | Page 12
 can be used to improve the effectiveness of testing.
Note:- Learner needs to give expected results in a tabular format and screenshots of the
actual results with the conclusion

Activity 3.2
Get independent feedback on your database solution from the non-technical users and some
developers (use surveys, questioners, interviews or any other feedback collecting method)
and make recommendations and suggestions for improvements in a separate
conclusion/recommendations section.

Activity 4

Produce a technical documentation and a user guide for the developed database system.
Suitable diagrams diagrams (Use case diagram, class diagram, flow charts, DFD level 0 and
1) should be included in the technical documentation to show data movement in the system.
Assess the developed database by suggesting future enhancements to ensure the
effectiveness of the system.

Ishanka Anuruddha | Database Design and Development | Page 13

 Grading Criteria Achieved Feedback

LO1 Use an appropriate design tool to design a relational

database system for a substantial problem

P1 Design a relational database system using appropriate

design tools and techniques, containing at least four
interrelated tables, with clear statements of user and system
requirements.
M1 Produce a comprehensive design for a fully functional
system that includes interface and output designs, data
validations and data normalization.

D1 Evaluate the effectiveness of the design in relation to

user and system requirements.

LO2 Develop a fully functional relational database system,

based on an existing system design

Ishanka Anuruddha | Database Design and Development | Page 14

 P2 Develop the database system with evidence of user
interface, output, and data validations, and querying across
multiple tables.

P3 Implement a query language into the relational database

system

M2 Implement a fully functional database system that

includes system security and database maintenance.

M3 Assess whether meaningful data has been extracted

using query tools to produce appropriate management
information.

LO3 Test the systems against user and system requirements

Ishanka Anuruddha | Database Design and Development | Page 15

 P4 Test the system against user and system requirements.

M4 Assess the effectiveness of the testing, including an

explanation of the choice of test data used.
LO2 & LO3
D2 Evaluate the effectiveness of the database solution in
relation to user and system requirements, and suggest
improvements.
LO4 Produce technical and user documentation

P5 Produce technical and user documentation.

M5 Produce technical and user documentation for a fully

functional system, including diagrams showing movement
of data through the system, and flowcharts describing how
the system works.

D3 Evaluate the database in terms of improvements needed

to ensure the continued effectiveness of the system.

Ishanka Anuruddha | Database Design and Development | Page 16

Table of Contents
Acknowledgement ................................................................................................................................ 19
Activity 1 .............................................................................................................................................. 20
1.1 For the above scenario, identify the user and system requirements for designing a database .... 20
1.1.1 User and System requirements ............................................................................................. 21
1.1.2. Entity Relationship (ER) diagram ....................................................................................... 22
1.1.3 Design a relational database system using conceptual design (ER Model) by including
identifiers (primary Key) of entities and cardinalities, participations of relationships ................. 24
1.1.4. Using the relational database model, converting the ER model into a logical database
design, including primary keys, foreign keys, and referential integrity. ..................................... 25
1.1.5. Check whether the provided logical design is normalized. If not, normalize the database by
removing the anomalies. ............................................................................................................... 26
1.1.6 Normalization: ..................................................................................................................... 27
1.2 Design set of simple interfaces to input and output for the above scenario using Wireframe or
any interface-designing tool. Evaluate the effectiveness of the given design (ERD and Logical
design) in terms of the identified user and system requirements. ..................................................... 31
1.3 Evaluate the effectiveness of the given design (ERD and Logical design) in terms of the
identified user and system requirements........................................................................................... 36
Activity 2 .............................................................................................................................................. 37
2.1 According to the ER diagram created above, the relational database system designed for Polly
Pipe Company using SQL. ............................................................................................................... 37
2.2 Creates a simple interface to insert, update and delete data in the database ............................... 40
2.3 Implement proper security mechanisms in the developed database ........................................... 44
2.4 Evaluate the database solution developed and its effectiveness with relevant to the user and
system requirements identified, system security mechanisms.......................................................... 45
Activity 3 .............................................................................................................................................. 45
3.1 Provide a suitable test plan to test the system against user and system requirements. provide
relevant test cases for the database you have implemented. Assess how the selected test data can be
used to improve the effectiveness of testing. .................................................................................... 46
3.2 Get independent feedback on your database solution from the nontechnical users and some
developers (use surveys, questioners, interviews or any other feedback collecting method) and
make recommendations and suggestions for improvements in a separate
conclusion/recommendations section. .............................................................................................. 47
Activity 4 .............................................................................................................................................. 53
4.1 Produce a technical documentation and a user guide for the developed database system.......... 53
4.2 Technical Specification Requirements for Manage the Database .............................................. 55

Ishanka Anuruddha | Database Design and Development | Page 17

 4.3 Suitable diagrams (Use case diagram, class diagram, flow charts, DFD level 0 and 1) should be
included in the technical documentation to show data movement in the system. ............................ 56

List of Tables

Table 1 - Customer Details 1 ................................................................................................................. 28

Table 2 -Customer Detail 2 ................................................................................................................... 28
Table 3 - Customer Details 3 ................................................................................................................. 29
Table 4 - Installation Details 1 ............................................................................................................... 29
Table 5 - Customer Details 4 ................................................................................................................. 30
Table 6 - Customer address and contact .............................................................................................. 30
Table 7 - Installation Details 2 ............................................................................................................... 30
Table 8 -Wireframes ............................................................................................................................. 31
Table 9 - Class diagram ......................................................................................................................... 56
Table 10 - user diagram ........................................................................................................................ 57

List of Images

Figure 1 - Database ............................................................................................................................... 20

Figure 2 - Entity Relationship Diagrams Crow's foot model ................................................................. 23
Figure 3 - ER Diagram ............................................................................................................................ 24
Figure 4 - logical database design ......................................................................................................... 26
Figure 5 - Normal Forms ....................................................................................................................... 27
Figure 5 - Normal Forms ...................................................................................................................... 60
Figure 6 - Entity Relationship Diagrams Crow's foot model: ............................................................... 60

Ishanka Anuruddha | Database Design and Development | Page 18

Acknowledgement

I would like to thank all who supported me in completing my 1st assignment of Database
Design & Development assignment. I’m really happy about my friends because they always
encouraged me until I finished my project. I am sincerely grateful to them for sharing their
knowledge and giving their comments on several issues related to this assignment. Also, I
would like to give my special thanks to my friend Sandaruwan Rathnayake. He used to point
out any mistake when he is seen.

I take this opportunity to express my sincere gratitude to Mr.Eranga for his support and
guidance throughout this assignment. Also, his kindness and friendliness with the students
were a great help to us. Finally, I would like to extend my deep gratitude towards my mother
and my sister for their support in carrying out this work successfully.

Thank all,

Ishanka Anuruddha.

Ishanka Anuruddha | Database Design and Development | Page 19

Activity 1

1.1 For the above scenario, identify the user and system requirements for designing a
database

What is database?

A database is an organized collection of structured information or data that is usually

stored electronically in an information system. A database is generally managed
through a database management system (DBMS). Together, the data and the DBMS,
along with associated applications, are called a database system, often abbreviated
into a database.

Data stored within the most common databases is typically modelled in lines and
columns for efficient processing and data querying. Storing data in this way allows
for its easy access, management, modification, updating, and control. Most databases
use structured query language (SQL) to look at data stored in rows and columns to
avoid the querying issues confronted with a sequence of data.

Figure 1 - Database

Ishanka Anuruddha | Database Design and Development | Page 20

1.1.1 User and System requirements

User requirements:

User requirements are statements, in a natural language plus diagrams, of what services
the system is expected to provide to system users and the constraints under which it
must operate. The user requirements may vary form broad statements of the system
features required, precise description of the system functionality.

Polly Pipe is a company based in Braintree, England that provides and installs water
sports equipment. It is necessary to develop and implement an electronic database to
accommodate their needs. Polly Pipe emphasizes corporate positioning here. Customers
can order single or multiple installations per facility type. Employees or staff are
assigned to each facility. Because these buildings are frequently very large, plumbers are
also masons and carpenters. Air pumps, thermostats, and aquariums are used in
facilities.

System requirements:

System Requirements are those that developers use to build the system. Those are
requirements that require a much deeper vision of the system. The requirements of the
system may be classified as,

1. Functional requirements
2. Non – functional requirements

Functional requirements

All tasks necessary for the database upgrade are called functional requirements.
Updating the data required for addition to the system is a key requirement for users.
The client database must be able to enter the client data from Poly Pipe Company
Database. Ability to enter information on staff and tasks. they are assigned, etc.
Provide the equipment required for an installation or control, the type of equipment
that the organization needs, and the user needs information.

Non – functional requirements

Nonfunctional requirements are different kinds of predictions for a system or

software. They are disruptive to the design and implementation of systems and
software. Nonfunctional requirements include forecaster, availability, reliability,
integrity, traceability, testability, maintainability and accountability.

Ishanka Anuruddha | Database Design and Development | Page 21

1.1.2. Entity Relationship (ER) diagram

Entity relationship diagrams (ERD):

ERDs display relationships between items in a database, such as persons, things, and
concepts. The ER diagram depicts a database's logical structure by identifying
entities, their properties, and their relationships. The Common ERD Symbols are as
follows:

Entity

Attribute

Multivalued Attribute

Derived Attribute

Relationship

Associative Entity

Ishanka Anuruddha | Database Design and Development | Page 22

 Cardinality:

A Cardinality strategy relates to how many instances of one entity are associated with
one instance of another entity when connecting databases and ERDs. In terms of
cardinality, there are three types:

Chen Model

 One to One - 1 : 1

 One to Many – 1 : M

 Many to Many – M : N

Crow’s Foot Model

Figure 2 - Entity Relationship Diagrams Crow's foot model

Ishanka Anuruddha | Database Design and Development | Page 23

1.1.3 Design a relational database system using conceptual design (ER Model) by including identifiers (primary Key) of entities and
cardinalities, participations of relationships

Figure 3 - ER Diagram

Ishanka Anuruddha | Database Design and Development | Page 24

1.1.4. Using the relational database model, converting the ER model into a logical
database design, including primary keys, foreign keys, and referential integrity.

facility (facility_id, type)

staff ( staff_no, name, facility_id*)

equipment_type(equipment_type_id, name)

equipment(equipment_id, name, value, equipment_type_id*)

facility( facility_id, name)

equipment( equipment_id, name, value, facility_id*)

installation_type( installation_type_id, name)

installation( installation_id, from,to, installation_type_id*)

Customer(customer_id, f_name, address, contact)

installation (installation_id, from, to, customer_id*)

Staff( staff_No, name)

installation( installation_id, from, to)

installation_has_staff( id, installation_id*,staff_No*)

installation( installation_id,from,to)

equipment( equipment_id, name, value)

installation_has_equipment( id, installation_id*,equipment_id*)

Ishanka Anuruddha | Database Design and Development | Page 25

1.1.5. Check whether the provided logical design is normalized. If not, normalize the
database by removing the anomalies.

Figure 4 - logical database design

Ishanka Anuruddha | Database Design and Development | Page 26

1.1.6 Normalization:

Multiple related tables are organized into a single table to minimize data entry. Using
normalization, you can reduce data redundancy and remove unwanted characteristics such as
inserting, updating and deleting anomalies. In normalization rules, large tables are divided
into smaller ones, and these smaller ones are connected by relationships. In SQL,
normalization aims to remove redundant data (duplicates) and ensure accurate data storage

There are a few steps involved in normalizing databases,

First Normal Form - 1NF

Second Normal Form - 2NF
Third Normal Form - 3NF
Boyce Codd Normal Form - BCNF

Figure 5 - Normal Forms

Ishanka Anuruddha | Database Design and Development | Page 27

According to the Pipe Company, here are some details of a few selected customers and
installations. Without any normalization in the database, all the information is stored in one
table as below.
Table 1 - Customer Details 1

Customer Details
Name Address Contact Installation Type
Lee A.sun Oak House, 17 Wroxton Road, 071-0000001 Freshwater Tropical
Hertfordsh ire, H5 667 077-0000001
Sally Dench Bayliss House, Orange Street, 071-0000002 Freshwater Cold
Kent, K7 988
Perry Eaglestone Castle, Eaglestone , 077-0000003 Marine
Vanderrune Kent
Eric Mackintosh 23 Sackville Street, Wilts. W55 077-0000004 Marine

Perry Humbertso n Castle, Kent, K8 077-0000003 Freshwater Tropical

Vanderrune

1NF (First Normal Form):

 Each cell to be single valued

 Entries in a column are same type
 Rows uniquely identified

Let’s see the result after the first normal form

Table 2 -Customer Detail 2

Customer Details
Customer Name Address Contact Installation
ID Type
C01 Lee A.sun Oak House, 17 Wroxton 071-0000001 Freshwater
Road, Hertfordsh ire, H5 667 Tropical
C01 Lee A.sun Oak House, 17 Wroxton 077-0000001 Freshwater
Road, Hertfordsh ire, H5 667 Tropical
C02 Sally Dench Bayliss House, Orange Street, 071-0000002 Freshwater
Kent, K7 988 Cold
C03 Perry Eaglestone Castle, Eaglestone 077-0000003 Marine
Vanderrune , Kent
C03 Perry Humbertso n Castle, Kent, K8 077-0000003 Freshwater
Vanderrune Tropical
C04 Eric 23 Sackville Street, Wilts. 077-0000004 Marine
Mackintosh W55

Ishanka Anuruddha | Database Design and Development | Page 28

2NF (Second Normal Form):

Use separate tables for values that apply to multiple reports. Connect tables with a

Foreign key and do not rest on a table key other than the corresponding desk key.

 Each cell to be single valued.

 Entries in the column are same type.
 Rows uniquely identified.
 All attributes depend on the key.

According to the last point, Name, Address and Contact depend on the Customer ID but
Installation Types are not depending on the Customer ID. So, we can fix it like that.

Table 3 - Customer Details 3

Customer Details
Customer Name Address Contact
ID
C01 Lee A.sun Oak House, 17 Wroxton 071-0000001
Road, Hertfordsh ire, H5 667
C01 Lee A.sun Oak House, 17 Wroxton 077-0000001
Road, Hertfordsh ire, H5 667
C02 Sally Dench Bayliss House, Orange Street, 071-0000002
Kent, K7 988
C03 Perry Eaglestone Castle, Eaglestone 077-0000003
Vanderrune , Kent
C03 Perry Humbertso n Castle, Kent, K8 077-0000003
Vanderrune
C04 Eric 23 Sackville Street, Wilts. 077-0000004
Mackintosh W55

Table 4 - Installation Details 1

Installation Details
Installation ID Installation Type
I01 Freshwater Tropical
I01 Freshwater Tropical
I02 Freshwater Cold
I03 Marine
I01 Freshwater Tropical
I03 Marine

Now all attributes depend on the key.

Ishanka Anuruddha | Database Design and Development | Page 29

3NF (Third Normal Form):

In any case, if the contents of a group of fields apply to more than one report in a table,

Such areas can be listed separately.

 Each cell to be single valued.

 Entries in the column are same type.
 Rows uniquely identified.
 All attributes depend on the key.
 All attributes determined only by the key
Table 5 - Customer Details 4

Customer Details
Customer Name
ID
C01 Lee A.sun
C02 Sally Dench
C03 Perry Vanderrune
C04 Eric Mackintosh

Table 6 - Customer address and contact

Customer Address & Contact

Customer Address Contact
ID
C01 Oak House, 17 Wroxton Road, Hertfordsh ire, H5 667 071-0000001
C01 Oak House, 17 Wroxton Road, Hertfordsh ire, H5 667 077-0000001
C02 Bayliss House, Orange Street, Kent, K7 988 071-0000002
C03 Eaglestone Castle, Eaglestone , Kent 077-0000003
C03 Humbertso n Castle, Kent, K8 077-0000003
C04 23 Sackville Street, Wilts. W55 077-0000004

Table 7 - Installation Details 2

Installation Details
Installation Installation Type
ID
I01 Freshwater Tropical
I02 Freshwater Cold
I03 Marine

Ishanka Anuruddha | Database Design and Development | Page 30

1.2 Design set of simple interfaces to input and output for the above scenario using
Wireframe or any interface-designing tool. Evaluate the effectiveness of the given design
(ERD and Logical design) in terms of the identified user and system requirements.

To design a simple interface we need a suitable flat form for that, I decided to use Wireframe.

Wireframe:

Wireframes show which interface parts are important pages on a web page. In the interaction
design process, it is crucial. A wireframe is used to present a visual overview of a page before
starting the creative process to get stakeholder and project team approval. Before adding
visual design and content, wireframes are used to build the basic structure of a page.

Table 8 -Wireframes

Ishanka Anuruddha | Database Design and Development | Page 31

  Interface of Login Page

 Interface of Main Menu

Ishanka Anuruddha | Database Design and Development | Page 32

  Interface of Staff Management

 Interface of Facility Details

Ishanka Anuruddha | Database Design and Development | Page 33

  Interface of Customer Details

 Interface of Installation Details

Ishanka Anuruddha | Database Design and Development | Page 34

  Interface of Installation Type Details

 Interface of Equipment Types

Ishanka Anuruddha | Database Design and Development | Page 35

  Interface of Equipment Details

1.3 Evaluate the effectiveness of the given design (ERD and Logical design) in terms of
the identified user and system requirements

Before we can construct and design a database system, we must thoroughly understand both
user and system requirements. The system's efficiency is affected by this factor. A
framework's success depends on how well it addresses the issues of its users. Understanding
user and system demands is crucial to building a better, more efficient system. In order to
completely meet their needs, we aim to do so through our system.

Our system must meet eight main user requirements. A user's login, menu, adding staff,
adding equipment types, adding equipment and managing equipment, adding customers,
adding facilities, and managing installations are the software modules.

These processes are performed through nine interfaces. To meet these desires in Polly Pipe
Company, a database need to be created. A difficult concept of this gadget can be taken
through first developing an ER plan to go well with every requirement. There, all the desires
are studied and separate entities are constructed for them. Then, by way of designing the
attributes associated to them, the components wanted for an entire machine can be identified.

Then a logical database is created to fit them. There you can recognize the primary keys,
visitor keys, etc. contained in the system. It is additionally viable to apprehend the
relationships between every entity in the system.

Ishanka Anuruddha | Database Design and Development | Page 36

Activity 2

2.1 According to the ER diagram created above, the relational database system designed
for Polly Pipe Company using SQL.

Staff Management table:

Customer Details Table:

Ishanka Anuruddha | Database Design and Development | Page 37

Facility Table:

Equipment table:

Ishanka Anuruddha | Database Design and Development | Page 38

Equipment type table:

Installation Table:

Ishanka Anuruddha | Database Design and Development | Page 39

Installation Type Table:

2.2 Creates a simple interface to insert, update and delete data in the database

The term Integrated Development Environment (IDE) refers to a tool used for software
development. GUIs (Graphical User Interfaces) are IDEs, also known as Integrated
Development Environments (IDEs). These systems enable programmers to integrate many
parts of the development process.

Developers can easily transfer code to new applications by using debugging, copy control,
and data structure review capabilities. By providing user interfaces (UIs) for pertinent
components, it increases productivity and reduces language learning time. IDEs support a
single language or a number of languages.

Ishanka Anuruddha | Database Design and Development | Page 40

INSERT Statement:

Ishanka Anuruddha | Database Design and Development | Page 41

UPDATE Statement:

Ishanka Anuruddha | Database Design and Development | Page 42

DELETE Statement:

Ishanka Anuruddha | Database Design and Development | Page 43

2.3 Implement proper security mechanisms in the developed database

Database security can protect confidentiality, integrity and availability of data. Database

Security is secure database from threats. Database security threats in following situation,

• Theft fraudulent

• Confidentiality loss

• Data privacy loss

• Integrity loss

• Data availability loss

Type’s PF Database security mechanisms are,

• Access controls

• Views

• Data integrity

• Encryption of data

Access control:

Access control can protect database on unauthorized access.

Data encryption:

Encryption give protection on sensitive data communicate on public networks.

Ishanka Anuruddha | Database Design and Development | Page 44

2.4 Evaluate the database solution developed and its effectiveness with relevant to the
user and system requirements identified, system security mechanisms

Database design was influenced by user and system requirements identified during system
design. Users' requirements describe what the system must do, while system requirements
describe what the system must do. The database solution created is made in a way that is easy
and practical for users to understand.

According to security measures, the database is built with a standard level of security. The
database is protected from unauthorized access by certain restrictions.

Maintaining an objective database improvement system is essential. The system developed

here checks whether the game is running properly. Additional database maintenance tasks
include checking for problems, looking for evidence of system damage, deleting duplicate
files, searching records, and looking for anomalies. By completing all these facilities and
creating the system, the efficiency of this mine will increase.

Activity 3

Test Plan

A trial plan is a technical writing piece that describes an orderly strategy for. Evaluating a
particular system, such as a machine, piece of software, or gadget.

The test plan involves a thorough understanding of the workflow and operations.of the
system and details how each will be assessed to see if the system works the same.designed to
detect flaws, and to establish its real constraints.

Ishanka Anuruddha | Database Design and Development | Page 45

3.1 Provide a suitable test plan to test the system against user and system requirements.
provide relevant test cases for the database you have implemented. Assess how the
selected test data can be used to improve the effectiveness of testing.

Test Plan:

Login page Test Test Date: 18/08/2022

Testing Process: Input Valid User Name, Password
Purpose of Testing: When enter correct user name and Password display "Login
successful!" message box and load "Menu Page". If not display
"Login not Successful!"
Test Data:

Output: Correct login: User Name - admin

Password - admin@123

Output: Incorrect login : User Name - admin

Password - 12345

Ishanka Anuruddha | Database Design and Development | Page 46

In this way, this process is entered for all data tables in database.

3.2 Get independent feedback on your database solution from the nontechnical users
and some developers (use surveys, questioners, interviews or any other feedback
collecting method) and make recommendations and suggestions for improvements in a
separate conclusion/recommendations section.

Ishanka Anuruddha | Database Design and Development | Page 47

Ishanka Anuruddha | Database Design and Development | Page 48
Ishanka Anuruddha | Database Design and Development | Page 49
Feedback Summary:

Ishanka Anuruddha | Database Design and Development | Page 50

Ishanka Anuruddha | Database Design and Development | Page 51
Ishanka Anuruddha | Database Design and Development | Page 52
Activity 4

4.1 Produce a technical documentation and a user guide for the developed database
system.

Welcome to all the Polly Pipe system!

Let’s see how you can easily use the system step by step

Step 1: Here is the logging page to the Polly Pipe Database system

If you need to leave from the system, To Continue the Process, Click the
please click here Loin Button

Step 2: After you logging in to the system correctly, the Menu form will be display.

Ishanka Anuruddha | Database Design and Development | Page 53

Step 3: Then you can select any option you need to know and click the button you want to
enter. The required page by operating the Buttons (Staff Management, Facility...) in the Menu
form.

If you click customer details, it will display like here,

To find the Entered data

To delete data, use this

You can edit or update data by

clicking here

By the clicking this you can add new To Erase data

records to the customer details table

Go back to Main Menu

According to this type you can use every form in the menu and it eligible to add data, update
data, Delete, Clear and Search.

Ishanka Anuruddha | Database Design and Development | Page 54

4.2 Technical Specification Requirements for Manage the Database

1. Software Requirements

2. Hardware Requirements

Software Requirements Hardware Requirements

 Microsoft SQL Server application  Minimum e requirements of the

Processor - x64 Processor: AMD
 Microsoft Visual Studio Opteron, AMD Athlon 64, Intel
Xeon with Intel EM64T support,
Intel Pentium IV with EM64T
support

 Processor Speed
x86 Processor: 1.0 GHz
x64 Processor: 1.4 GHz
Recommended: 2.0 GHz or faster

 Memory Express Editions: 512 MB

All other editions: 1 GB

Ishanka Anuruddha | Database Design and Development | Page 55

4.3 Suitable diagrams (Use case diagram, class diagram, flow charts, DFD level 0 and 1)
should be included in the technical documentation to show data movement in the
system.

Class Diagram:

Table 9 - Class diagram

Ishanka Anuruddha | Database Design and Development | Page 56

Use Case Diagrams :

Table 10 - user diagram

Flow Chart:

For Login Page

Ishanka Anuruddha | Database Design and Development | Page 57

 For Data Update

Add Data

Ishanka Anuruddha | Database Design and Development | Page 58

 Delete Data

Add Data

4.4 Assess the developed database by suggesting future enhancements to ensure the
effectiveness of the system.

Develop the system as a user-friendly mobile application, and then the user can easily
download and install the app on his/her smart device. According to that, the company can
share the details easily and update data day by day with the help of users. no need to bear an
additional cost to the system.

Creating security measures like two factor authentication in consideration of the damage that
can be caused to the system due to cyber-attack and carelessness of other external users.

Since there may be a legal problem in storing people's personal information, therefore during
the system's installation, the user should be informed about it and establish a plan to confirm
that he has no objection to storing his personal information.

Ishanka Anuruddha | Database Design and Development | Page 59

References:

What is database (2022/12/08) [online] www.oracle.com:

https://www.oracle.com/database/what-is-database/

Richard Peterson (2019). What is Normalization? 1NF, 2NF, 3NF & BCNF with Examples.
[online] Guru99.com. Available at: https://www.guru99.com/database- normalization.html.

Richard Peterson (2019). What is Normalization? 1NF, 2NF, 3NF & BCNF with Examples.
[online] Guru99.com. Available at: https://www.guru99.com/database- normalization.html.

Smartdraw (2019). Entity Relationship Diagram (ERD) - What is an ER Diagram? [online]

Smartdraw.com. Available at: https://www.smartdraw.com/entity- relationship-diagram/

Figure 6 - Normal Forms:

https://medium.com/@yg17381/normalization-in-dbms-297269fe7e9f

Figure 7 - Entity Relationship Diagrams Crow's foot model:

https://dev.to/helenanders26/entity-relationship-diagrams-explained-by-sonic-the-hedgehog-

Ishanka Anuruddha | Database Design and Development | Page 60