1152-1619622711350-Unit 04 - Database Design and Development - Reworded - 2021

Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title BTEC HND in Computing
Assessor Internal Verifier

Unit 04: Database Design & Development
Unit(s)
Database Solution for Polly Pipe
Assignment title
Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match

those shown in the assignment brief? Y/N
Is the Pass/Merit/Distinction grade awarded

justified by the assessor’s comments on the Y/N
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 criteria? Y/N
• Identifying opportunities for Y/N
improved performance?
• Agreeing actions? Y/N
Does the assessment decision need
Y/N
amending?
Assessor signature Date
Internal Verifier signature Date

Programme Leader signature (if required)
Date
Confirm action completed

Remedial action taken
Give details:
Assessor signature Date
Internal Verifier
Date
signature
Name Subject Assignment NO.

S.A. Thushan Lakshitha Unit 04: Database Design & Development 01
(e005928) page. 1
Programme Leader
Date
signature (if required)

(e005928) page. 2
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Unit Title Unit 04: Database Design & Development
Assignment Number 1 Assessor

Date Received
Submission Date
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 & Distinction P1 M1 D1
Descripts
LO2 Develop a fully functional relational database system, based on an existing system design
Pass, Merit & Distinction P2 P3 M2 M3 D2
Descripts
LO3 Test the system against user and system requirements.

Descripts
LO4 Produce technical and user documentation.

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.

(e005928) page. 3
Assignment Feedback
Formative Feedback: Assessor to Student
Action Plan
Summative feedback
Feedback: Student to Assessor
Assessor Date
signature

(e005928) page. 4
Student Date
signature
Pearson Higher Nationals in

Computing
Assignment 01

(e005928) 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.
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.
(e005928) page. 6
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

(e005928) 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.
Student’s Signature: Date:

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

(e005928) page. 8
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Unit Number and Title Unit 4: Database Design & Development
Academic Year 2021/22
Unit Tutor
Assignment Title Data base system for Polly Pipe
Issue Date
Submission Date
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:

(e005928) page. 9
Assignment brief
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
Instillation Management Form
Activity 1
(e005928) page. 10
1.1. Identify the user and system requirements to design a database for the above scenario
Installation Installation Installation Customer Equipment Types of Staff Period of

ID Type Name and Required Staff
Address assignm
ent
234 Freshwater Oak Lee A. 2 air 1 x Carpenter From 1st
sun
Tropical House, 17 pumps 1 x Aquatics Septemb
Wroxton 200 gallons installer er 2012
Road, fish tank 1 x Electrician
Hertfordsh 1x
ire, H5 667 standard
thermostat
654 Freshwater Bayliss Sally 2 air 5x 1st June
Cold House, Dench pumps Carpenters 2005 –
Orange 200 gallons 1x 1st June
Street, fish tank Installation 2011
Kent, K7 Large Manager
988 Gravel Bag 1 x Aquatics
2x installer
standard 1 x Plumber
thermostat 3 x Labourers
s
767 Marine Eaglestone Perry 2 x 200 10 x From
Castle, Vanderru gallons fish Carpenters 30th June
Eaglestone ne tanks 2x 2012
, Kent 500 Wood Installation
panels Manager
1 x Aquatics
installer
1 x Plumber
3 x Labourers
943 Marine 23 Eric 2 air No staff required
Sackville Mackinto pumps
Street, sh 200 gallons
Wilts. W55 fish tank
1x
standard
thermostat
157 Freshwater Humbertso Perry 2 air 1 x Aquatics 1st
Tropical n Castle, Vanderru pumps installer Septemb
Kent, K8 ne 400 gallons er 2005
fish tank – 1st
3x Septemb
standard er 2012
thermostat
and design a relational database system using conceptual design (ER Model) by including

(e005928) page. 11
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

(e005928) page. 12
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.
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.

(e005928) page. 13
(e005928) page. 14
Grading Criteria Achie Feedback
ved
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
P2 Develop the database system with
evidence of user interface, output, and
data validations, and querying across
multiple tables.

(e005928) page. 15
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
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.

(e005928) page. 16
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.

(e005928) page. 17
Pearson Higher Nationals in
Computing
Assignment 01

(e005928) page. 18
Acknowledgment
I would like to express my special thanks of gratitude to my lecturer Mr. Chathuka

Mallikaarachchi who gave me the golden opportunity to do this wonderful project on the
topic of Discrete Mathematics. This also helped me in doing a lot of research and I came
to know about so many new things I am really thankful for them.
Secondly, I would also like to thank my parents and friends who helped me a lot in
finalizing this project within the limited time frame.
Thushan Lakshitha
(e005928)

(e005928) page. 19
Table of Contents
Acknowledgment ............................................................................................................... 19
Activity 1 ............................................................................................................................ 23
LO1 Use an appropriate design tool to design a relational database system for a
substantial problem. .......................................................................................................... 23
Activity 1.1 ......................................................................................................................... 23
1.1.1 Introduction .............................................................................................................. 23
1.1.2 The user and system requirements of Polly pipe ..................................................... 24
1.1.3 Explanation of Polly pipe’s ER Diagram .................................................................... 26
1.1.4 Er diagram for Polly Pipe........................................................................................... 26
1.1.5 Logical Schema .......................................................................................................... 27
1.1.6 Data normalization ................................................................................................... 27
1.1.7 Provided logical schema normalization .................................................................... 29
1.1.8 What is validation? ................................................................................................... 30
Activity 1.2 ......................................................................................................................... 32
1.2.1 Interface of Polly pipe ............................................................................................... 32
Activity 2 ............................................................................................................................ 40
LO2 Develop a fully functional relational database system, based on an existing system
design. ................................................................................................................................ 40
Activity 2.1 ......................................................................................................................... 40
2.1.1 What is SQL? ............................................................................................................. 40
Activity 2.2 ......................................................................................................................... 40
2.2.1 What is DDL Statements? ......................................................................................... 40
2.2.1.1 DDL ......................................................................................................................... 41
2.2.1.2 DML ........................................................................................................................ 42
2.2.2 Usage of DDL ............................................................................................................. 44
2.2.3 Polly pipe company system ...................................................................................... 47
2.2.4 Database security...................................................................................................... 52
2.2.5 SQL statements ......................................................................................................... 53
Activity 3 ............................................................................................................................ 59
LO3 Test the systems against user and system requirements .......................................... 59
Activity 3.1 ......................................................................................................................... 59
3.1.1 Test plan .................................................................................................................... 59
3.1.2 Test forms ................................................................................................................. 62
(e005928) page. 20
3.1.2 Test procedure .......................................................................................................... 65
............................................................................................................................................ 65
3.1.3 Database testing ....................................................................................................... 66
............................................................................................................................................ 66
Activity 4 ............................................................................................................................ 67
LO4 Produce technical and user documentation .............................................................. 67
Activity 4.1 ......................................................................................................................... 67
4.1.1 Technical and user documentation .......................................................................... 67
List of Tables
Table 1: Normalization (Author 2021) ............................................................................... 29
Table 2: Test case 01 .......................................................................................................... 59
Table 3: Test case 02 .......................................................................................................... 60
Table 4: Test case 03 .......................................................................................................... 61
Table 5: (Author 2021) ....................................................................................................... 65
Table 6: (Author 2021) ....................................................................................................... 66
Table 7: User guide (Author 2021) .................................................................................... 67
List of Figures
Figure 1: DBMS ................................................................................................................... 23
Figure 2: ER Diagram for Polly pipe (Author 2021) ............................................................ 26
Figure 3: logical schema for Polly Pipe (Author 2021): ...................................................... 27
Figure 4: (Author 2021) ...................................................................................................... 31
Figure 5: (Author 2021) ...................................................................................................... 31
Figure 6: (Author 2021) ...................................................................................................... 32
Figure 7: Logging form (Author 2021) .............................................................................. 33
Figure 8: Main form (Author 2021) .................................................................................... 34
Figure 9: Employee details form (Author 2021) ................................................................ 35
Figure 10: Customer details form (Author 2021)............................................................... 36
Figure 11: Installation details form (Author 2021) ........................................................... 37
Figure 12: Enuipment details form (Author 2021) ............................................................. 38
Figure 13: Payment form (Author 2021) ........................................................................... 39
Figure 14: (Author 2021) .................................................................................................... 45
Figure 15: (Author 2021) .................................................................................................... 46
Figure 16: (Author 2021) .................................................................................................... 46
Figure 17: Login form (Author 2021) ................................................................................. 47
Figure 18: Employee form (Author 2021) ......................................................................... 48
Figure 19: Customer details (Author 2021) ....................................................................... 49
(e005928) page. 21
Figure 20: Equipment form (Author 2021) ........................................................................ 50
Figure 21: Installation form (Author 2021) ....................................................................... 51
Figure 22: Payment form (Author 2021) ........................................................................... 52
Figure 23: Select form (Author 2021) ............................................................................... 54
Figure 24: Where form (Author 2021) .............................................................................. 55
Figure 25: Update statement (Author 2021) .................................................................... 56
Figure 26: Between statement (Author 2021) .................................................................. 56
Figure 27: In statement (Author 2021) ............................................................................. 57
Figure 28: Group by statement (Author 2021) ................................................................. 57
Figure 29: Order by statement (Author 2021) .................................................................. 58
Figure 30............................................................................................................................. 62
Figure 31............................................................................................................................. 63
Figure 32............................................................................................................................. 64

(e005928) page. 22
Activity 1
LO1 Use an appropriate design tool to design a relational database system for a
substantial problem.
Activity 1.1
What is database?
A database is a collection of information or data stored electronically in a computer

system. Such databases are managed by a database management system (DBMS).
Processing of data in a database is done by using rows and columns in tabular form to
make it easier to check the data. That way the data can be easily managed. Today, SQL
(structured query language) is the most used query for writing and querying data.
Figure 1: DBMS
1.1.1 Introduction
Polly pipe is a water sports provider and installer based in Braintree, England. Its
manual database system wants to design and implement a database that meets the data
requirements as computerized system. Therefore, this system was designed and
developed the solution for water sports provider and installer to meet their business
customers.
Polly pipe is maintaining their data in manual system. Manual system is a paper record.
In computerized system control the company’s data of maintainable assets through an

(e005928) page. 23
asset register, easy to control Customer’s request of several installations, but each
installation is tailor-made for a specific customer can include carpenters and masons as
well as water installers, use equipment such as aquariums, air pumps and thermostats
etc. Easy to control the issues and documentation of several installations.
Database design process is,
1. Requirement’s collection and analysis

2. Conceptual design
3. Logical design/ data model mapping
4. Physical design
1.1.2 The user and system requirements of Polly pipe
When defining requirements, two types of requirements are served different purposes.
When identify the user requirements of the above scenario. They are,
1. Functional requirements
2. Non – functional requirements
Functional requirements
All the tasks required to upgrade the database are called functional requirements.
Updating the data required to add to the system is one of the main requirements of the
user. The customer's database should be able to enter the customer's data from the Poly
Pipe company's database. Ability to enter information about employees, what duties
they are assigned, etc. Provide the equipment needed for an installation or order, what
type of equipment the organization needs, and the user needs to have information in the
system. (Polly Pipe system should ability to give customer details, employee details,
payments, installation, equipment details.) It should have creative interface.

(e005928) page. 24
Non – functional requirements
Non – functional requirements specify for not covered all the areas by functional
requirements. The details in system design were implement by functional requirements.
Various types of non – functional requirements are accessibility, audit, efficiency,
security, accuracy, availability, backup and restore, capacity, certification, compliance,
reliability, responsibility, virus guard, compatibility of software.
System requirements
System requirements are the building blocks developers use to develop the system.
System requirements are categorized as either functional or non – functional
requirements. Functional requirements differentiate something that a user needs to
perform their work very well. For example, in the above scenario system should be able
to provide the required information for customers several installations and handle daily
operations that is functional requirements.
1. Hardware requirements and Software requirements
8GB Ram, HDD, SSD, Frequency 3-3.5 GHZ and more, Network interface bandwidth
100Mbps, SSD for SQL 200Gb, Operating system – windows 10, Hard disk space 250GB+,
intel i7 dual core processor, Printer, Fax, scanner, Restore and backup options, Anti-virus
software.

(e005928) page. 25
1.1.3 Explanation of Polly pipe’s ER Diagram
In Polly pipe company’s customers when ordered installation it will be installation by

employees and customers pay payment. Company’s ER Diagram and Attributes are,
1. Customer - cus_id, cus_name, cus_address, cus_contact no:

2. Employee - emp_id, emp_name, emp_address, emp_contact no: emp_types, salary
3. Equipment – equi_id, equi_type, equi_name, equi_price, quantity
4. Installation – inst.id, inst. type, start job, end job, address
5. Payment - payment _id, paym_type, paym_date
Learner has identified some of the functional and non-functional requirements of the
system.
1.1.4 Er diagram for Polly Pipe
Figure 2: ER Diagram for Polly pipe (Author 2021)

(e005928) page. 26
Learner has identified the some main entities, attributes and relationships and have drawn
the ER diagram
1.1.5 Logical Schema
Figure 3: logical schema for Polly Pipe (Author 2021):
Learner has converted the ER diagram into a logical relational schema
1.1.6 Data normalization
Data normalization is the process of organizing data into a database. It also includes
creating tables and interacting with pre-designed rules to make it more flexible by
eliminating redundancy, data security and database incompatibility. Excess data storage
is a waste of disk space and can cause various maintenance problems. If different tables
have the same data, the data in each table must be changed. For example, if you intend
to change the customer's address, changing the customer desk data is sufficient.

(e005928) page. 27
"Incorrect dependence" means that when looking at a customer's desk for a customer's
address, it should not contain personal information about the employee's salary. They
should be at the employee desk.
There are several rules for normalizing a database.
First normalization form
Here, removing repetitive groups from individual tables, creating separate tables for
each dataset, and identifying data using a primary key. And not using the same desk to
store the same data.
For example, a company wants to store name and contact details of their employees.
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.
For example, suppose we want to store data on teachers who teach in a school and the
subjects they teach. There can be several rows for the same teacher at the table as one
teacher can teach more than one subject.
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.
For example, a recruitment table may include the name and address of a candidate's
university, but a complete list of universities is required to send a group mail. If the
information is stored on the job seeker's desk, there is no way to list the universities
where there are no candidates. What can be done here is to create a separate university
table and then attach it to the candidate desk. Although this is theoretical, there are
(e005928) page. 28
problems with its implementation. This is because in some cases this method is not
suitable for small tables. This is most appropriate for a frequently changing data party.
Fourth normal form
This is also known as the Boyce Code Normal Form (BCNF) and exists as the fifth
standard form, but in practice it is considered a coincidence. Ignoring these rules may
result in less than a complete database plan, but it does not affect performance.
For example, if think that there is a company that employs more than one employee, can
indicate that they are working in several departments of the organization.
1.1.7 Provided logical schema normalization
Table 1: Normalization (Author 2021)

(e005928) page. 29
Learner has simply explained the concept of normalization and have applied normalization
to the derived relational schema
1.1.8 What is validation?
Data validation is important in data processing, analysis, data verification and data
processing. It is important to verify any data before use. Making decisions based on
flawed data is risky. Therefore, any organization in the world has its own set of rules for
storing and maintaining its corporate data. Examples of data validation rules ,
 Data type (ex. integer, float or string)
 Range check (ex. A number between 10-50)
 Uniqueness (ex. Postal code)
 Consistent expressions (ex. Using one of St., Str, Street)
 No null values
Data validation
 Insert
 Update
 Delete
(What is Data Validation? How It Works and Why It's Important, 2021)

(e005928) page. 30
Insert Data
Figure 4: (Author 2021)
Update Data

(e005928) page. 31
Delete Data in database
Learner has just simply explained the validation mechanisms to validate data in the tables
with examples.
Activity 1.2
1.2.1 Interface of Polly pipe
Simple interface design to user for get main idea of system. It is can designed on
wireframe or any interface designing tool.
Polly pipe company has 6 interface forms that author created. They are,
• Login form
• Main form
• Employee form
• Customer form
• Installation form
• Equipment form
• Payment form

(e005928) page. 32
Login form
Polly Pipe company system main interface is Login form. It is design on simple
interface include username and password.
Figure 7: Logging form (Author 2021)

(e005928) page. 33
Main Form
Figure 8: Main form (Author 2021)

(e005928) page. 34
Employee details form
Figure 9: Employee details form (Author 2021)

(e005928) page. 35
Customer details form
Figure 10: Customer details form (Author 2021)

(e005928) page. 36
Installation details form
Figure 11: Installation details form (Author 2021)

(e005928) page. 37
Equipment details form
Figure 12: Enuipment details form (Author 2021)

(e005928) page. 38
Payment details form
Figure 13: Payment form (Author 2021)
Learner has designed sample interfaces to input and output data using an interface
designing tool.

(e005928) page. 39
Activity 2
LO2 Develop a fully functional relational database system, based on an existing

system design.
Activity 2.1
2.1.1 What is SQL?
SQL is a structured query language. It is a computer language for storing, manipulating,

and retrieving data stored on a relational database. A database is a table that includes rows
and columns. SQL mainly targeting understand and analyze of databases include data
tables. For a example, A company had a many data to be stored. Already Company has a
departments and gathered data on it . At that time company place a SQL for stored their
database.
Importance of SQL
1. SQL is a global language.

2. SQL is a open source language and that can be use easily to user or learner.
3. Mainly SQL have managed billions of data in world.
4. SQL even use on smart devices and use iOS and android.
5. Many global companies place sql at their demand.
Activity 2.2
2.2.1 What is DDL Statements?
SQL has 6 sublanguages.

• DDL – Data Definition Language.
• DML – Data Manipulation Language.
• DRL/DQL – Data Retrieval Language/Data Query Language
• TCL – Transaction Query Language.
• DCL – Data Control Language.
• SCL – Session Control Language.
(e005928) page. 40
2.2.1.1 DDL
DL can change commands automatically. It’s permanently saved in the database. DDL
does things like create tables and delete tables. DDL as a command,
• DROP
• ALTER
• CREATE
• TRUNCATE
Create used
Syntax
• CREATE TABLE TABLE_NAME (COLUMN_NAME DATATYPES[,….]);
Example
• CREATE TABLE CUSTOMER(Name VARCHAR2(50), ADDRES VARCHAR

2(100), DOB DATE);
Drop used
Syntax
• DROP TABLE table__name;
Example
• DROP TABLE PAYMENT;

(e005928) page. 41
Alter used
Syntax
• ALTER TABLE table _name ADD column__name COLUMN-definition;
Example
• ALTER TABLE CUS_DETAILS ADD(ADDRESS VARCHAR2(50));

• ALTER TABLE CUS_DETAILS MODIFY (NAME VARCHAR2(50));
Truncate used
Syntax
• TRUNCATE TABLE table_name;
Example
• TRUNCATE TABLE CUSTOMER;
2.2.1.2 DML
DML is used to modify databases. But DML cannot execute automatic commands like
DDL. Data can be reversed via DML. Here are under DML commands,
• INSERT
• UPDATE
• DELETE

(e005928) page. 42
Insert used
Syntax
1. INSERT INTO TABLE_NAME

2. VALUES (value1, value2, value3, .... valueN);
For example
1. INSERT INTO Employee (Address, Name) VALUES ("oak street", "sally

dench");
Update used
Syntax
• UPDATE table_name SET [column_name1= value1,...column_nameN = valueN]

[WHERE CONDITION]
For example
1. UPDATE Installation
2. SET Name = 'Marine'
3. WHERE Installation__Id = '767'
DELETE USED
Syntax
1. DELETE FROM table _name [WHERE condition];

(e005928) page. 43
For example
1. DELETE FROM Payment

2. WHERE PaymentID="22";
(SQL Commands: DDL, DML, DCL, TCL, DQL - javatpoint, 2021)
2.2.2 Usage of DDL
The key here is the ability to create tables and manage created tables using data definition
language. Create a new tables, structured and recorded stored create in table and also
delete structured data and stored on table in database and used to add new attributes in
database.
Below commands are Polly pipe database system usage:
Select Command

(e005928) page. 44
Update Command

(e005928) page. 45
Delete Command
The learner has provided overview about SQL

(e005928) page. 46
2.2.3 Polly pipe company system
Login form
Figure 17: Login form (Author 2021)

(e005928) page. 47
Employee details form
Figure 18: Employee form (Author 2021)

(e005928) page. 48
Customer details form
Figure 19: Customer details (Author 2021)

(e005928) page. 49
Equipment details form
Figure 20: Equipment form (Author 2021)

(e005928) page. 50
Installation details form
Figure 21: Installation form (Author 2021)

(e005928) page. 51
Payment details form
Figure 22: Payment form (Author 2021)
2.2.4 Database security
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
Types pf Database security mechanisms are,

• Access controls
• Views
• Data integrity

(e005928) page. 52
• 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.
2.2.5 SQL statements
Below are Select, where, update, Between, in, Group By, Order By statements.
‘Select’ SQL Statement

(e005928) page. 53
Figure 23: Select form (Author 2021)
‘Where’ statement

(e005928) page. 54
Figure 24: Where form (Author 2021)
‘Update’ statement

(e005928) page. 55
Figure 25: Update statement (Author 2021)
‘Between’ statement
Figure 26: Between statement (Author 2021)

(e005928) page. 56
‘in’ statement
Figure 27: In statement (Author 2021)
‘Group by’ statement
Figure 28: Group by statement (Author 2021)

(e005928) page. 57
‘Order by’ statement
Figure 29: Order by statement (Author 2021)
Learner has developed a relational database system according to the ER diagram using
DDL statements.but need to provide more source code.

(e005928) page. 58
Activity 3
LO3 Test the systems against user and system requirements
Activity 3.1
3.1.1 Test plan
Database Testing can check schemas, tables etc. of the database. Database system testing
is effectively and validate to ensure quality of the system.
Test case – 01
Test case – Enter incorrect username or password
Test name – Pamudi Manushika
Table 2: Test case 01

(e005928) page. 59
Test case – 02
Test case – Enter correct username and incorrect password
Test name – Thamasha thathsaranai

(e005928) page. 60
Test case – 03
Test case – Enter correct username and correct password
Test name – Maleesha sewwandi

(e005928) page. 61
3.1.2 Test forms
Test 01
Figure 30

(e005928) page. 62
Test 02
Figure 31

(e005928) page. 63
Test 03
Figure 32

(e005928) page. 64
3.1.2 Test procedure
Table 5: (Author 2021)

(e005928) page. 65
3.1.3 Database testing
Table 6: (Author 2021)
Learner has provided a suitable test plan and test cases to test the system against user
and system requirements.

(e005928) page. 66
Activity 4
LO4 Produce technical and user documentation
Activity 4.1
4.1.1 Technical and user documentation
User guide
Table 7: User guide (Author 2021)

(e005928) page. 67

(e005928) page. 68
Learner has prepared a user manual to assist the users of the system.

(e005928) page. 69
References
Oracle.com. 2021. What is a database?. [online] Available at:

https://www.oracle.com/database/what-is-database/ [Accessed 17 October 2021].
Phoenixnap.com. 2021. [online] Available at: https://phoenixnap.com/kb/wp-

content/uploads/2021/07/how-a-dbms-works.png [Accessed 17 October 2021].
Watt, A., 2021.

Chapter 12 Normalization. [online] Opentextbc.ca. Available at:
https://opentextbc.ca/dbdesign01/chapter/chapter-12-normalization/ [Accessed 1
October 2021].
Safe Software. 2021.

What is Data Validation? How It Works and Why It's Important. [online]
Available at: https://www.safe.com/what-is/data-validation/ [Accessed 14 October
2021].
www.javatpoint.com. 2021.
SQL Commands: DDL, DML, DCL, TCL, DQL - javatpoint. [online]
Available at: https://www.javatpoint.com/dbms-sql-command [Accessed 17 October
2021].

(e005928) page. 70
(e005928) page. 71

1152-1619622711350-Unit 04 - Database Design and Development - Reworded - 2021

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1152-1619622711350-Unit 04 - Database Design and Development - Reworded - 2021

Uploaded by

Copyright:

Available Formats

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

Programme title BTEC HND in Computing

Assessor Internal Verifier

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

Is the Pass/Merit/Distinction grade awarded

Assessor signature Date

Internal Verifier signature Date

Confirm action completed

Assessor signature Date

Name Subject Assignment NO.

Name Subject Assignment NO.

Unit Title Unit 04: Database Design & Development

Assignment Number 1 Assessor

LO3 Test the system against user and system requirements.

LO4 Produce technical and user documentation.

Grade: Assessor Signature: Date:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Name Subject Assignment NO.

Feedback: Student to Assessor

Name Subject Assignment NO.

Pearson Higher Nationals in

Name Subject Assignment NO.

Word Processing Rules

Name Subject Assignment NO.

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

Student’s Signature: Date:

Name Subject Assignment NO.

Unit Number and Title Unit 4: Database Design & Development

Academic Year 2021/22

Assignment Title Data base system for Polly Pipe

IV Name & Date

Name Subject Assignment NO.

Staff Management Record

Equipment Type Table

Instillation Management Form

Installation Installation Installation Customer Equipment Types of Staff Period of

Name Subject Assignment NO.

Name Subject Assignment NO.

Name Subject Assignment NO.

LO1 Use an appropriate design tool to

P1 Design a relational database system

D1 Evaluate the effectiveness of the design

LO2 Develop a fully functional relational

Name Subject Assignment NO.

M2 Implement a fully functional database

M3 Assess whether meaningful data has

LO3 Test the systems against user and

Name Subject Assignment NO.

P5 Produce technical and user

M5 Produce technical and user

D3 Evaluate the database in terms of

Name Subject Assignment NO.

Name Subject Assignment NO.

I would like to express my special thanks of gratitude to my lecturer Mr. Chathuka

Name Subject Assignment NO.

Name Subject Assignment NO.

A database is a collection of information or data stored electronically in a computer

In computerized system control the company’s data of maintainable assets through an

1. Requirement’s collection and analysis