Higher Nationals

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Program title BTEC HND in computing

Assessor Internal Verifier

Unit 04: database design and development

Unit(s)
Database solution for Polly pipe
Assignment title

A.M. Ranidu Chandima

Student’s name

List which assessment criteria the Pass Merit Distinction

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’s work?
Has the work been assessed accurately?
Y/N
Is the feedback to the student:
Give details:
• Constructive?
• Linked to relevant assessment criteria? Y/N
• Identifying opportunities for improved Y/N
performance? Y/N
• Agreeing actions?
Y/N
Does the assessment decision need amend?
Y/N

Assessor signature Date

Internal Verifier signature Date

Program Leader signature (if required)

Date
Confirm action completed
Remedial action is taken
Give details:
Internal verification of assessment decisions – BTEC (RFQ)

A.M. Ranidu Chandima database and development Unit 04

 Higher Nationals - Summative
Assignment Feedback Form
Student Name/ID

Unit Title Unit 04: Database and development

Assignment Number 1 Assessor

11/09/2022 Date Received 1st 11/09/2022

Submission Date submission
Date Received 2nd
Re-submission Date submission
Assessor Feedback:
LO1 Demonstrate a range of interpersonal and transferable communication skills to a target audience

Pass, Merit & Distinction P1 P2 M1 D1

Descriptions

LO2 Apply critical reasoning and thinking to a range of problem-solving scenarios

Pass, Merit & Distinction P3 P4 M2 M3 D2

Descriptions

LO3 Discuss the importance and dynamics of working within a team and the impact of the team working
in different environments
Pass, Merit & Distinction P5 P6 M4 D3
Descriptions

LO4 Examine the need for Continuing Professional Development (CPD) and its role within the workplace
and higher-level learning
Pass, Merit & Distinction P7 P8 M5 D4
Descriptions

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Page:02

A.M. Ranidu Chandima database and development Unit 04

Assignment Feedback
Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor Date
signature

Student signature Date

A.M. Ranidu Chandima database and development Unit 04

 Pearson Higher Nationals in
Computing
Unit 04: Database Design and
development

Assignment:01

A.M. Ranidu Chandima database and development Unit 04

 General Guidelines

1. A Cover page or title page – You should always attach a title page to your assignment. Use the
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 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. egg: Figures, tables of comparison, etc. Adding text boxes in the body
except for the before-mentioned compulsory information will result in the rejection of your
work.
2. Carefully check the hand-in date and the instructions are 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 FERAL. 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 the
HARVARD referencing system to avoid plagiarism. You must provide both in-text citations and a
reference list.

A.M. Ranidu Chandima database and development Unit 04

 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

Pearson Higher Nationals in

Computing
Unit 04: Database Design and
development

Assignment:01

A.M. Ranidu Chandima

HND BATCH 47

A.M. Ranidu Chandima database and development Unit 04

Table of Content
Figure numbers .................................................................................................................... 7
Activity 1 .............................................................................................................................. 9

Activity 1.1 ..................................................................................................................... 10

1.1.1 Introduction .................................................................................................. 10

1.1.2 The user and system requirements of Polly pipe ......................................... 11

Functional requirements ............................................................................................. 11

Non-functional requirements ....................................................................... ............ 12

System requirements .................................................................................................. 12

1.1.3 Explanation of Polly pipe’s ER Diagram .......................................................... 13

1.1.4 Er diagram for Polly Pipe ...................................................................................... 14

1.1.5 Logical Schema ..................................................................................................... 15

1.1.6 Data normalization ................................................................................................ 16

(Watt, 2022) ................................................................................................................. 17

1.1.7 Provided logical schema normalization ................................................................ 18

Figure numbers

Figure 1 DBMS .................................................................................................................. 10

Figure 2 ER Diagram for Polly pipe (Author 2022) .......................................................... 14

Figure 3 logical schema for Polly Pipe (Author 2022) ...................................................... 15

Figure 4 (Author 2022) ...................................................................................................... 20

Figure 5 (Author 2022) ...................................................................................................... 20

A.M. Ranidu Chandima database and development Unit 04

Figure 6(Author 2022) ....................................................................................................... 21

Figure 7 Main form (2022 Author) ................................................................................... 23

Figure 8 Login form (2022 Author) .................................................................................... 24

Figure 9 Customer form (Author 2022) ........................................................................... 25

Figure 10 Installation form (Author 2022) ........................................................................ 26

Figure 11 Employee form (Author 2022) ............................................................................ 27

A.M. Ranidu Chandima database and development Unit 04

Activity 1.1

Definition of database

A database could be a computerized system that creates it easy to go look, select, and store

information. A database is sometimes controlled by a direction system (DBMS). Together, the
information and the DBMS, together with the applications that are related to them, are named a
database system, often shortened to only a database. Data within the foremost common forms
of databases operative today is often modeled in rows and columns during a series of tables to
create processing and data querying efficiency. the info can then be easily accessed, managed,
modified, updated, controlled, and arranged.

Figure 1 DBMS

Source:

A.M. Ranidu Chandima database and development Unit 04

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 of a computerized system. Therefore, this system was designed and
developed as a solution for water sports providers and installers to meet their business
customers. Polly pipe is maintaining its data in the manual system.
A manual system is a paper record.

(Space left intentionally)

A.M. Ranidu Chandima database and development Unit 04

1.1.2 The user and system requirements of Polly pipe

Definition of Requirements

Requirement simply means a thing that is needed or wanted. Requirement engineering is

the process of defining requirement, establishing, and documenting it properly, and keeping the
standard of requirements of a customer from a system, and therefore the limitations under which
it operates and is developed. it is the primary activity of software engineering. Requirements are
needed to satisfy whether deliberately, product, or process of software When explaining
requirements there are two main styles of requirements are served different purposes. When
identifying the user requirements of the above scenario. They are,

1. Functional requirements
2. Non – functional requirements

Functional Requirements

Functional requirements are mandatory which suggests it is compulsory and needed to be

fulfilled. they typically describe and define features of the outcome of computer code and
easily focus on what the tip product does. These are the wants that a system should accomplish
or do like calculations, data manipulations, etc. it is extremely easy to search out functional
requirements and capture them in use cases. A system should provide a press release of service
which describes how the system reacts to inputs provided and may be clear and the way a system
reacts during a particular situation. Functional requirements are a form of requirements that
depends upon the variety of software as different software incorporates different functional
requirements and systems on which software is employed because it heavily affects the functions
of software and users to satisfy their requirements. The functional requirement of users is high-
level abstract statements.

Non-Functional Requirements

Non-functional requirements do not seem to be mandatory which implies that they are not

compulsory to be fulfilled. The non-functional requirements define system properties and system

A.M. Ranidu Chandima database and development Unit 04

performance. Different properties of a system are there which may be Reliability, latent period,
maintainability, availability, and storage requirements. It simply focuses on how the tip product
works and it is not extremely easy and hard to search out non-functional requirements and
captured them as a top-quality attribute. Testing includes performance, stress, security testing,
etc. Non-functional requirements are more disapproved and if the non-functional
requirements are not fulfilled then the complete system is of no use.

System Requirements

System requirements are the configuration that a system must have so as for a hardware or
software application to run smoothly and efficiently. Failure to satisfy these requirements may
result in installation problems or performance problems. the previous may prevent a tool or
application from getting installed, whereas the latter may cause a product to malfunction or
perform below expectation or maybe to hold or crash.

1.1.3 Explanation of Polly pipe’s ER Diagram

A.M. Ranidu Chandima database and development Unit 04

In Polly pipe company’s customers when ordered installation it will be installed by employees
and customers pay the payment. The 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, payment_type, payment_date

A.M. Ranidu Chandima database and development Unit 04

1.1.4 Er Diagram for Polypipe

Figure 2 ER Diagram for Polly pipe

Source: Author’s work
Relationship missing
Add multivalued attributes

A.M. Ranidu Chandima database and development Unit 04

1.1.5 Logical Schema

Emp. id Name Emp. type Contact No: Address Salary

Employee

Cus.id Name Contact No: Address Ins.id

Customer

Equip.id Name Price Type Quantity

Equipment

Ins.Id Start Job End Job Ins.type Equip.id Emp.id

Installation

Payment.id Payment. Type Payment. Date Cus.id

Payment

Figure 3. Logical Schema (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

1.1.6 Data Normalization

What is Normalization?

Normalization is the process of organizing a database to scale back redundancy and improve data

integrity. Normalization also simplifies the database design, so it achieves the optimal structure
composed of atomic elements. Also observed as database normalization or data normalization,
normalization is a vital part of electronic database design because it helps with the speed,
accuracy, and efficiency of the database. By normalizing a database, you arrange the info into
tables and columns. You make sure that each table contains only related data. If data is
not related, you create a replacement table for that data.

Why do we need Normalization?

The main reason for normalizing the relations is to get rid of these anomalies. Failure to
eliminate anomalies ends up in data redundancy and may cause data integrity and other
problems because the database grows. Normalization consists of a series of guidelines that helps
to guide you in creating an honest database structure.

First Normalization Form(1NF)

To achieve the first normal form for a database, you would like to create sure that no table
contains multiple columns that you simply could use to urge identical information. Each table
should be organized into rows, and every row should have a primary key that distinguishes it as
unique. the first secret is usually one column, but sometimes over one column may
be combined to form one primary key.

Second Normalization Form(2NF)

The second normal form (2NF) is the second step in normalizing a database. 2NF builds on the
primary normal form (1NF). Normalization is the process of organizing data in a database in the
order that it meets two basic requirements: there is no redundancy of information (all data is
stored in mere one place).

A.M. Ranidu Chandima database and development Unit 04

 Third Normalization form(2NF)

We need to get rid of such dependencies by going to the Third Normal Form (3NF). A
relation is within the third normal form if there is no transitive dependency for non-prime
attributes additionally because it is within the second normal form

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 gaggle mail. If the
information is stored on the work seeker's desk, there are no thanks to listing the schools
where there are not any candidates. What will be done here is to form a separate
university. table and so attach it to the candidate desk. Although this is often theoretical,
there are problems with its implementation. this is often because in some cases this
method is not suitable for little tables. this is often most proper for a frequently changing
data party.

Forth Normalization Form

The fourth normal form (4NF) may be a level of database normalization where there are not
any non-trivial multivalued dependencies apart from a candidate key.

It builds on the primary three normal forms (1NF, 2NF, and 3NF) and therefore the Boyce-Codd
Normal Form (BCNF). It states that, additionally to a database meeting the necessities of BCNF,
it must not contain quite one multivalued dependency. This is also known as the Boyce Code
Normal Form (BCNF)

A.M. Ranidu Chandima database and development Unit 04

1.1.7 Provided logical schema normalization

employee

ID Name Type

xSHA1 Dave Clark Plumber

SHA8 John Smith Installation Manager

SHA2 Freddy Davies Aquatics installer

SHA11 McCloud Aquatics installer

SHA23 Satpal Singh Plumber

SHA66 Winston Kodogo Aquatics installer

SHA55 Alison Smith Bricklayer

Table 1 Normalization (Author 2022)

Employee

ID Name

SHA1 Plumber

SHA8 Installation Manager

SHA2 Aquatics installer

SHA11 Aquatics installer

SHA23 Plumber

SHA66 Aquatics installer

SHA55 Brick layer

Table 2 Normalization (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

1.1.8 Definition for Data Validation

Data validation is an important part of any data handling task whether you are within
the field collecting information, analyzing data, or preparing to present data to
stakeholders. If data is not accurate from the beginning, your results will not be accurate
either. That is why it is necessary to verify and validate data before it is used.

While data validation may be a critical step in any data workflow, it is often skipped. it is

going to seem as if data validation may be a step that slows down your pace of labor,
however, it is essential because it will facilitate you create the simplest results
possible. nowadays data validation is often a far quicker process than you might have
thought. With data integration platforms that will incorporate and automate validation
processes, validation may be an important ingredient to your workflow instead of a
further step.

Examples of data validation rules,

 Data type (ex. integer, float, or string)
 Range check (ex. A number between 10-5 0)
 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? 202

A.M. Ranidu Chandima database and development Unit 04

Activity 1.2

1.2.1 Interface of Polypipe System

Simple interface design for the user for getting the main idea of a system. It can design on a
wireframe or any interface designing tool.

Polly pipe company has six interface forms that the author created. They are,

 Main form
 Login Form
 Employee form
 Customer form
 Installation form
 Equipment form
 Payment form

(Space left Intentionally)

A.M. Ranidu Chandima database and development Unit 04

Main form
This is the main Interface Form of Polypipe Company. Simply this is the Main form

Figure 7 Main Form (Author 2022)

Login Form
It is designed with a simple interface including username and password.
Figure 8 Login Form (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

Customer Form

Figure 9 Customer Form (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

Installation Form
Figure 10 Installation Form (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

Employee Form

Figure 11 Employee Form (author 2022)

A.M. Ranidu Chandima database and development Unit 04

Equipment Form

Figure 12 equipment Form (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

Payment Form

Figure 13 Payment Form (Author 2022)

A.M. Ranidu Chandima database and development Unit 04

Activity 2

Activity 2.1.1 Definition for SQL

SQL is a Structured search language, which could be a programing language for storing,
manipulating, and retrieving data stored in a computer database.

SQL is the standard language for online database Systems. All the electronic information

service Management Systems (RDMS) like MySQL, MS Access, Oracle, Sybase, Informix,
Postgres, and SQL Server use SQL as their standard database language.

It,s using different dialects, such as,

MS SQL Server using T-SQL,

Oracle using PL/SQL,
MS Access version of SQL is named JET SQL (native format) etc.….

Importance Of SQL

SQL is so important because it's a typical language for working with databases. this

suggests that irrespective of what kind of database you're using, it'll likely have an SQL
interface that you simply can use to speak with it.

Using a standard language also ensures that everybody who uses a database is going to

be using the identical commands to try and do so, which makes it easier for developers to
make applications that employment with multiple databases.

Additionally, SQL is intended for managing data, which makes it a robust tool for organizing
and processing large amounts of data. and at last, because SQL could be a standard language,
anyone who knows the way to use it can easily edit code written by some other person, making
collaboration much simpler.

A.M. Ranidu Chandima database and development Unit 04

2.2.1 Statement for DDL
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.

2.2.1.1.DDL

DDL is the brief name of information Definition Language, which deals with database

schemas and descriptions, of how the info should reside within the database

 CREATE
 ALTER
 DROP
 TRUNCATE
 COMMENT
 RENAME

A.M. Ranidu Chandima database and development Unit 04

  Create use

Syntax

• CREATE TABLE TABLE_NAME (COLUMN_NAME DATATYPES [….]).

Example

• CREATE TABLE CUSTOMER (Name VARCHAR2(50), ADDRESS VARCHAR

2(100), DATE), DOB

 Drop used
Syntax

• DROP TABLE table__name,

Example

• DROP TABLE PAYMENT.

 Alter used
Syntax

ALTER TABLE table _name column__name25 COLUMN-definition.

Example
• ALTER TABLE CUS_DETAILS ADD (ADDRESS VARCHAR2(50)).
• ALTER TABLE CUS_DETAILS MODIFY (NAME VARCHAR2(50)).

A.M. Ranidu Chandima database and development Unit 04

  Truncate used

1. TRUNCATE TABLE table_ name.

Example:

• TRUNCATE TABLE CUSTOMER.

2.2.1.2 DML

A data manipulation language (DML) could be a family of computer languages including

commands permitting users to control data in an exceeding database. This manipulation
involves inserting data into database tables, retrieving existing data, deleting, retrieving
existing data, deleting data from existing tables, and modifying existing data. Data
manipulation language is usually incorporated in SQL databases

 INSERT
 UPDATE
 DELETE

 Insert Used

Syntax

1. INSERT INTO TABLE_NAME

2.VALUES (value1, value 2, value 3, value N).

For Example:

INSERT INTO Employee (Address, Name) VALUES

A.M. Ranidu Chandima database and development Unit 04

  Update Used

Syntax

 UPDATE table_name SET [column_name1= value1, column_nameN = valueN]

[WHERE CONDITION]

For example:

1. UPDATE Installation
2. SET Name = 'Ranidu'
3. WHERE Installation_ID = '779'

 Delete Used

Syntax

 DELETE FROM table _name [WHERE condition].

For example:

1. DELETE FROM Payment

2. WHERE Payment_ID ="23”.

(SQL Commands: DDL, DML, DCL, TCL, DQL - javatpoint, 2022)

A.M. Ranidu Chandima database and development Unit 04

A.M. Ranidu Chandima database and development Unit 04