Ruzan DDD Final Assignment - 082903

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

INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title BTEC HND in Computing

Miss.Ishani
Assessor Internal Verifier
Unit 04: Database Design & Development
Unit(s)
Database Solution for Polly Pipe
Assignment title
Mohamed Ramzy Mohamed Ruzan
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
Programme Leader
Date
signature (if required)
Mohamed Ruzan Unit 04- Database Design &Development 1

Higher Nationals - Summative Assignment Feedback Form
Student Name/ID Mohamed Ruzan /KAN00130309
Unit Title Unit 04: Database Design & Development
Assignment Number 1 Assessor Miss.Ishani

15.10.2022 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.

Assignment Feedback
Formative Feedback: Assessor to Student
Given answers are good enough.

One diagram is not included. Other answers are ok.
Action Plan
I have included the diagram that was missed.
Summative feedback
Feedback: Student to Assessor
ishani@esoft.lk 15.10.1022
Assessor Date
signature
E161001@esoft.academy 15.10.2022
Student Date
signature

Pearson Higher Nationals in
Computing
Unit 04: Database Design & Development
Assignment 01

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.
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

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.
E161001@esoft.academy 15.10.2022
Student’s Signature: Date:
(Provide E-mail ID) (Provide Submission Date)

Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number Mohamed Ruzan /KAN00130309
Unit Number and Title Unit 4: Database Design & Development
Academic Year 2021/22
Unit Tutor Miss.Ishani
Assignment Title Data base system for Polly Pipe
Issue Date 06.07.2022
Submission Date 15.10.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:

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
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

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 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.

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
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
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.

Content
Activity 1.1………………………………………………………………………..……19
What are the requirements …………………………………………………………..…19
ER Diagram…………………………………………………………………………..…20
Figure 1 ER Diagram……………………………………………………………….…..21
Relational schema for above ER Diagram…………………………………………..….22
Data validation……………………………………………………………………….…22
Normalization………………………………………………………………………..….22
Activity 1.2……………………………………………………………………………..25
Interface of Polly Pipe……………………………………………………………….…25
Figure 2 sign up……………………………………………………………………..….25
Figure 3 Register…………………………………………………………………….….25
Figure 4 Menu……………………………………………………………………….….26
Figure 5 Customer……………….………………………………………………….…..26
Figure 6 Staff.………………………………………………………………………..….27
Figure 7 Installation………………………………………………………………….….27
Figure 8 Equipment………………………………………………………………….….28
Figure 9 Facility….…………………………………………………………………..….28
Figure 10 Payment….………………………………………………………………..….29
Evaluation of the logical diagrams mentioned above…………………………….….….29
Activity 2.2………………………………………………………………………..….….31
DDL………………………………………………………………………………..….…31
Polly pipe database system……………………………………………………..…….….32
Figure 11 create database………………………………………………………….…..…32
Figure 12 create customer table……………………………………………………….....33
Figure 13 create facility table……………………………………………………….…....33
Figure 14 create staff table………………………………………………………….…....34
Figure 15 create payment table……………………………………………………….….34
Figure 16 create installation table…………………………………………………….….35
Figure 17 create equipment table…………………………………………………….…...35
About the IDE………………………………………………………………………….…36
The constrains utilized to create this database are……………………………………..…36
Activity 2.2…………………………………………………………………………….….37
DML……………………………………………………………………………………....37
Figure 18 create statement………………………………………………………………...37
Figure 19 insert statement………………………………………………………………...38
Figure 20 select statement………………………………………………………………...38
Figure 21 update statement……………………………………………………………….39
Figure 23 IN statement……………………………………………………………………40
Figure 24 between statement……………………………………………………………...40
Figure 25 delete statement………………………………………………………………...41
Figure 27 where statement………………………………………………………………...42
Figure order by statement…………………………………………………………………42

Activity 3.1……………………………………………………………………………..…...43
Software testing………………………………………………………………………..……43
Test plan………………………………………………………………………………..…...44
Test cases……………………………………………………………………………….…...45
Test ID 101………………………………………………………….….……46
Test ID 102………………………………………………………….….……46
Test ID 103……………………………………………………….…….……47
Test ID 104………………………………………………………………..…47
Test data evaluation for effective testing…………………………………………………....48
Activity 3.2……………………………………………………………………………….….50
Some of the feedbacks for my system…………………………………………………….…50
Figure 29………………………………………………………………………………….….50
Figure 30………………………………………………………………………………….….51
Figure 31……………………………………………………………………………….…….52
Figure 32……………………………………………………………………………….…….53
Figure 33………………………………………………………………………………….….54
Summary of suggestion improvement………………………………………………….……55
Figure 34………………………………………………………………………………….….55
Figure 35………………………………………………………………………………….….55
Figure 36………………………………………………………………………………….….55
Activity 4………………………………………………………………………………….…56
Documentation…………………………………………………………………………….…56
User guidelines…………………………………………………………………………….…57
Figure 37 Login interface…………………………………………………………….………57
Figure 38 Registration interface.……….………………………………………………….…58
Figure 39 Main menu interface………………………………………………………………59
Figure 40 Customer interface…………………………………….….……………….………60
Figure 41 Staff interface…………...…………………………………………………………61
Figure 42 Installation interface………………………………………………………….……62
Figure 43 Equipment interface………………………………………………………….……63
Figure 44 Facility interface…………….……………………………………………….……64
Figure 45 Payment interface…………………………………………………………….……65
UML Diagram…………………………………………………………………………….….66
Figure 46 use case diagram……………………………………………………………….….66
Figure 47 class diagram………………………………………………………………………67
Figure 48 activity diagram…...…………...…...………………………………………….….68
Suggested future improvement and recommendations for an effective system……………...69
Figure 49 Gantt chart…………………………………………………………………………70

Acknowledgement
In order to complete my assignment, I needed to enlist the assistance and counsel of some
highly respected individuals, for whom I am eternally grateful.
As completing this assignment gave me a lot of pleasure, I'd like to thank Ms. Ishani,
Course Instructor at Esoft Metro Campus, for providing me with good guidelines for this
assignment through numerous consultations and feedback.
I'd also like to thank everyone who has helped me with this assignment, both directly and
indirectly.
Many people, particularly my batch mates, provided insightful comments and suggestions
on my system, which inspired me to improve the quality of the assignment.
Thank You!!!

Activity 1.1
What are Requirements?

A requirement is a specification of a need or want. Set of requirements are used to
capture the information needed to design, build and test a process, a service, product or a
system.
There are 2 main requirements
User requirements
User requirements, or user needs, are description of what a user must do with the
system, such as what activities a user must be able to perform. Narrative text is usually used
to document user requirements in a user requirements document (URD).
The example of user requirements:
• In customer table, the user can accept orders and enter like Customer name and
installation ID.
• In the employee table, the user can access information on the staffs working, staffs on
leave using records staff_id and staff name in the relation
• In the equipment table, the user updates the equipment used by employees in that
way, if any shortage, or loss in equipment, the record can be recalled.
System requirements
system requirements are the configuration that a system must have in order for a
hardware or software application to run smoothly and efficiently. System requirements are
classified as:
according to the system we are implementing, these meet the system requirement as:
1. Software requirements
Software requirement is a functional or non-functional need to be
implemented in the system.

2. Hardware requirements
The hardware requirements are the requirements of a hardware devices.
Followings are the Hardware & Software requirements that were used in this
assignment
Hardware Specification Software specification
Intel(R) Core(TM) i5-3230M CPU @ 2.6GHz OPERATING SYSTEM – Windows10 pro

2.60 GHz
GRAPHICS CARD – Ge-Force GTX 560
2GB
MEMORY – DDR3 8GB .NET FRAMEWORK – Ver 4.8
HDD – SAMSUNG HD502HM ATA Device MS SQL – version 2019
NETWORKING – 802.11n USB Wireless MS OFFICE PACK – version 2019

LAN Card
ER Diagram (Entity Relationship Diagram)
ER Diagram stands for Entity relationship diagram, also known as ERD is a diagram
that displays the relationship of entity sets stored in a database. In other words, ER diagrams
help to explain the logical structure of database.
Why use ER Diagrams?
• Helps to describe entities, attributes, relationships.

• Helps to define terms related to entity relationship modelling.
• ER diagrams can be used by database designers as a blueprint for implementing data
in specific software applications.
• Provides a preview of how all your tables should connect, what fields are going to be
on each table.
• ERD allows you to communicate with the logical structure of the database to users.

ER DIAGRAM
Figure 1 ER diagram

Relational schema for the above ER diagram,
Entities Attributes
Installation Ins_id, Ins_type, Ins_name, Ins_address, Cus_id
Staff Staff_id, Staff_name, Staff_period, F_id
Customer Cus_id, Cus_name

Equipment Eq_id, Eq_type, Eq_name, Quantity, F_id, Staff_id
Facility F_id, F_type
Payment P_id, P_date, P_name
Data validation
It is an automatic computer check to ensure that the data entered is logical and
appropriate. It does check the accuracy of data.
Length check, format check, check digit, lookup table range check, presence check,
spell check
Normalization
Normalization is a database design technique that reduces data redundancy
and eliminates undesirable characteristics like insertion, update and deletion
anomalies.
Normalization of a data model consists of several steps. These steps are called
normalization rules.
0 Normal Form: not normalized

If a table contains repeating attributes, it is not normalized.
1 Normal Form: no repeating groups

If a relation contain composite or multivalued attribute, it violates first normal
form or a relation is in 1NF if it does not contain any composite or multivalued
attribute.

2 Normal Form: eliminate redundant data
To be in second normal form, a relation must be in first normal form and
relation must not contain any partial dependency.
3 Normal Form: eliminate transitive dependency

A relation is in third normal form, if there is no transitive dependency for non-
prime attributes as well as it is in 2NF.
Tables for the respective ER Diagram given above
The Customer table

Customer
Cus_id Cus_name
C1 Lee A.sun
C2 Sally Dench
For the request relationship. As this is a relationship between Installation and

Customer, both of the table’s foreign keys must be included in this table.
Request
Installation name & Address Ins_id Cus_id
Oak House, 17 Wroxton Road, 234 C1
Hertfordshire, H5 667
Bayliss House, Orange Street, Kent, K7 654 C2
988
The Installation table

Installation
Ins_id Ins_type
234 Freshwater Tropical
654 Freshwater Cold
Both the Installation and Customer tables are already in normalized form.

Employee table is also initially in normalized form.
Employee
Staff_Id Staff_name Start End Facility_id
SHA2 Freddy Davies 1/9/2012 111
SHA23 Satpal Singh 1/6/2005 1/6/2011 112
Facility table is also in normalized form.
Facility
Id F_Type
111 Aquatic installing
112 Plumbing
The equipment table is un normalized form. This table can be divided into 2.
Equipment
Eq_type Eq_name Quantity F_id Staff_Id
Air pumps Standard, Super 2 111 SHA2
Tanks 200 gallons fish 1 111 SHA2
tank
Thermostats Standard 1 112 SHA23
Equipment table is converted to 1st normal form to avoid multivalued attribute.

Variant
Eq_name Equip_type
Standard Air pumps
Super Air pumps
Equipment
Quantity F_Id Staff_Id Eq_type
2 111 SHA2 Air pumps
1 111 SHA2 Air pumps
1 112 SHA23 Thermostat

Activity 1.2
Interface of Polly Pipe
Figure 2
Figure 3

Figure 4
Figure 5

Figure 6
Figure 7

Figure 8
Figure 9

Figure 10
Evaluation of the Logical diagrams mentioned above:
As per the request of Polly Pipe waters port provider’s data requirements, I
have designed the ER-diagram which is the structure of the database as show in
page18. I have obtained 6 entities from the scenario (Staff, Customer, Equipment,
Facility, Payment, Installation). The ER diagram that I have is fully designed in
consideration to avoid the anomalies that are major problems. I only used Microsoft
word to design the entire ER model, as word is more familiar and user friendly to use.
All the interface were design using Microsoft Visual Studio and Database in
Microsoft server management studios.
So, when considering graphical interfaces that is connecting to the respective

database, I have given a signup form (figure1). This will be initial interface to appear
on screen when the system is on. A new user can get registered by filling the required
details in the registration form(figure2). But an existing user can enter the username

and password and access to the menu interface. This security system is a benefit to
avoid unauthorized access to the system. This interface and logical setup can be
modified for a more user friendly interface with added features such as a biometric
fingerprint scanner system that scans user data and saves it in the respective database
and later recall when fingerprint is given.
In Figure3 I designed separated slot for each field (Customer, Staff, Installation,
Equipment, Facility, Payment) I have provided the facility to the user to preview the
respective forms by clicking the right button. This categorized way makes the system
more convenient for the user to use.
The customer entity has two attributes; customer_id and Customer_name: as
shown in figure4. I have added some features such as ‘add button to insert a new
customer to the table, ‘update’ to update customer informations, ‘save’ button to save
the changes made by updating informations, ‘delete’ button to delete customer detail
from the table and ‘back’ button to return to the previous interface.
Staff interface (Figure 5) has staff_id, staff_name, staff_period with a foreign

key facility_id from facility table is placed to form a relationship. The same features
added in (figure 4) customer entity can be seen in this form too to make it more user
friendly
The figure 6 shows installation interface. It has Installation_id,

installation_name, installation_type, installation_address with a foreign key staff_id
from staff table is placed to from a relationship. The same features added in (figure 4)
customer entity can be seen in this form too to make it more user friendly.
Equipment interface (figure 7) has equipment_id, equipment_name,

equipment_type, quantity with a foreign key facility_id from facility table is placed to
form a relationship and a foreign key staff_id from staff table is placed to from a
relationship. The same features added in (figure 4) customer entity can be seen in this
form too to make it more user friendly.

The figur8 shows facility interface. It has facility_id and facility_type. Facility
type in the table is what the staff or employees do. Eg: plumbing, installing etc.
The payment interface (figure 9) has payment_id, payment_name,

payment_date. The same features added in all entities can be seen in this form too to
make it more user friendly.
So, I have designed the interfaces and logical diagrams as minimal but to
cover the requirements of the company and we can upgrade this system from tip to toe
by combining this simple setup with other programs.
Activity 2.1
Data Definition Language (DDL)
A data definition language is a computer language used to create and modify

the structure of database object in a database. These database objects include tables
,schemas, views, indexes, etc.
This term is also known as data description language in some contexts, as it

describes the fields and records in a database table. Create, Update, Rename,
Drop, etc.

Polly Pipe database system
➢ Create Database
Figure 11

➢ Create customer table
Figure 12
➢ Create facility table
Figure 13

➢ Create staff table
Figure 14
➢ Create payment table
Figure 15

➢ Create installation table
Figure 16
➢ Create equipment table
Figure 17

About the IDE
Created by Microsoft, Visual Studio is an integrated development environment that

is used to develop computer programs for windows.
Visual studio can also be used foe developing web sites, web applications and web
services. It uses Microsoft software development platforms such as windows APL,
windows form, Windows Store, Windows presentation foundation and Microsoft
Silverlight,
Including a code editor that support Intelligence, Visual studio is written in C++ and
C# and offers as an integrated debugger that works both as a source debugger and a
machine level debugger.
The constraints utilized to create this database are,
• Unique key constraint

By using this constraint, I was able to forbid duplicate values in one or more
columns within the prepared table.
• Primary key constraint

This constraint was used to define relationship between the table.
• Not null constraint

By this constraint, I was able to prevent null values from being entered into the
columns within the table
• Foreign key
This constraint is used in this database to define the relationship between and within
the table.

Activity 2.2
Data Manipulation Language (DML)
DML which deals with data manipulation and includes most common SQL statements
such SELECT, INSERT, UPDATE, DELETE, etc and it is used to store, modify,
retrieve, delete and update data in a database.
➢ CREATE Statement
Figure 18

➢ INSERT
Figure 19
➢ SELECT
Figure 20

➢ UPDATE
Figure 21
Figure 22

➢ IN
Figure 23
➢ BETWEEN
Figure 24

➢ DELETE
Figure 26
Figure 25

➢ WHERE
Figure 27
➢ ORDER BY
Figure 28

Activity 3.1
Software Testing
Software testing is a process of analysing an application’s functionally as per the

customer necessity.
We must do several sorts of software testing in order to make sure that our software
is stable and bug-free because testing is the only process that can make an
application bug-free.
Types of software testing
1. Unit Testing
It is the initial level of testing, which is typically performed by developers. In unit
testing, a module or component is tested in isolation. Its advantage is that defects in
a module can be easily identified at an early stage, lowering the overall cost of bug-
fixing.
2. Integration Testing
It is the second level of testing, and it involves testing a group of related modules as
an integrating component. It seeks to identify interface issues between modules. This
comes in four varieties: big-bang, bottom-up, top-down and hybrid.
3. System Testing
It is the third level of testing, and it involves testing the entire integrated application
as a whole. Its goal is to determine whether the application meets its business
requirements.

4. Acceptance Testing
It is the final and most important level of testing, upon completion of which the
application is released to production. There are two kinds of testing: alpha testing
and beta testing.
Testing methods
1. Black Box Testing: only interacting with the system’s graphical user interface
allows for black box testing.
2. White Box Testing: the system’s syntax will be tested, as well as unit and
integrating testing. Knowledge of programming is required.
3. Gray Box Testing: a combination of black box and white box testing.
Test Plan
Essentially, the Polly Pipe system is a functional and implementable system. The
logistic relational model, the ER Diagram, as shown above, initially formed this.
For any personnel, the system is extremely simple and easy to understand. Polly
Pipe’s main database contains table for the entities (Customer, Payment, Installation,
facility, Equipment, staff) as well as column names for the tables.
Assumption
▪ Customer can request a specific service for multiple addresses.
▪ Users can access the system with the proper company authentication.
▪ In an installation, customer can order more than two types of staff.
▪ Customer can only place installation orders for equipment with no personnel
involve.

Recourses
Software – Microsoft visual studio, Microsoft SQL server.
Objective
Testing the system with basic functionalities for analysis and evaluation.
Features to be tested
System with database connected interfaces
Login, insert, update, delete, save, add and submit
Test Cases
Test ID - 100 Date – 2022.08.02
Test function Login

Steps to test Insert username | Insert password | Click on login
Pre-def function Execute the login interface codes.
Post-def function The interface will be change to main menu.
Expected outcome Display menu interface
Actual outcome
Tester Ruzan

Test ID - 102 Date – 2022.08.31
Test function Insert customer details
Steps to test Insert customer ID and name | Click on insert
Pre-def function Insert customer ID along with customer name.
Post-def function We can see new customer details adding the record
Expected outcome Displays a message box after adding the new customer details to
the tables inside.
Actual outcome
Tester Ruzan
Test ID - 101 Date – 2022.08.18

Test function Delete
Steps to test Select a record from primary key field or type in | Click on delete
Pre-def function Select the ID or primary key in a field
Post-def function The previously selected record will be deleted if given ‘Yes’
Expected outcome Displays a message box after delete required record from table
Actual outcome
Tester Ruzan

Test ID - 103 Date – 2022.09.03
Test function Update
Steps to test Fill the necessary fields | Click on update
Pre-def function Type in the required field text boxes that has to be updated.
Post-def function The field we wanted to update with details will be changed.
Expected outcome Displays a message box after details have been updated in the
database table.
Actual outcome
Tester Ruzan
Test ID - 104 Date – 2022.09.10

Test function Submit
Steps to test Fill the all necessary fields | Click on submit
Pre-def function Type in the required field text boxes that has to be submitted.
Post-def function The field we wanted will be submitted to another interface.
Expected outcome Displays a message box after fields have been in the database
table.
Actual outcome
Tester Ruzan

Test data evaluation for effective testing
I have given five of my system tested cases for demonstration

The login screen is the first step to login to the system in Test case 1 (Test ID
100), so it is the key interface that also performs user authentication. Because the
company eventually required a better system, this interface is required in the given
system. After clicking the ‘login’ button, the system recognizes the user with the
provided credentials, and the interface is redirected to the main menu, where there
are a number of buttons that lead to the respective interfaces as labelled on them.
The buttons are customer, installation, staff, facility, equipment and payment. The
main menu can direct the user to any interface he requires with a single click.
The “Delete” button can also be thought of as a maintenance feature button, as

described in Test ID 101. A user can delete any record by selecting it form a combo
box or typing it into the box and clicking the delete button. If there was duplicate
data in the tables linked to the interfaces, the user could easily remove it. When the
delete button is pressed, a warning message appears to remind the user to reconsider
his decision. As a result, we can avoid losing valuable data that the user will
unintentionally delete.
The insert command and insert button, which are typical of some of my
interface designs, are included in Test ID 102. We eventually want to add the items
to the tables inside Polly Pipe’s database whenever we want to add a new client, a
new product, or a new service that helps with that the business needs. To store the
entered data, each insert button creates new entries in the corresponding tables. You
can see the combo box field will include the data you supplied it after the message
box says “Record added”.
As mentioned in Test ID 103, the “Update” button I also a key feature in managing
records and changes across the database’s tables. This van be used to make changes
to specific fields of data or records. Some of my interfaces have an update button,
particularly those with tables that collect and store data or information. Once you’ve
entered the items to be updated in the field rows, clicking the “update” button will

change the data that needs to be changed, and old data will be replaced with the new
ones, with the message “Update complete” indicating that the update was successful.
The “Submit” button is described in Test ID 104. This relates to the insert as
well. However, this future differs slightly from the insert button in that hen submit is
clicked, the data in the fields is redirected to another table that temporarily stores or
shifts the submitted information, which can then be printed if necessary.
I’ve described some of the main aspects of my database that were mentioned
in the above test cases, which will aid in testing the system’s effectiveness.

ACTIVITY 3.2
Some of the feedbacks for my system
Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Summary of suggestion improvement
Figure 34
Figure 35
Figure 36

ACTIVTY 4
Documentation
Project documentation is the process of recording the key project details and
producing the documents that are required to implement it successfully.
Users
Only the management crew of the company can login to the system and do necessary
changes, especially a user group with access permissions.
Access Requirements
A username along with a password has been assigned to a group of specific

personals for security purpose of the system. Management crew has the ability to
change credentials when needed.

User Guidelines
Login Interface
Figure 37
1
5
2 3 4
1. Enter username
2. Enter password
3. If username & password is known, click Login” else,
4. Click “Sign Up” for registration

Registration Interface
Figure 38
3 5 4 2
1. Enter fist name
2. Enter last name
3. Enter contact number
4. Enter email address
5. Click on register for new sign up

Main menu
1 3 4 2
5
6
Figure 39 1. Click Customer (Redirects to customer interface)
2. Click Staff (redirects to staff interface)
3. Click Installation (Redirects to installation interface)
4. Click Equipment (Redirects to equipment interface)
5. Click Facility (Redirects to facility interface)
6. Click Payment (Redirects to payment interface)

Customer Interface
1 Figure 40
4 2 3
5 6 7
8
1. Enter Customer ID
2. Enter Customer name
3. Enter facility ID
4. Click “back” to go previous interface
5. Click “Add” to add details
6. Click “Delete” to erase a record, select the record first
7. Click “Update” to change a previously entered record
8. Click “Save” to save your entered records

Staff Interface
Figure 41
1
5 2 6 4 7 3 8
9
1. Enter Staff ID
2. Enter Staff name
3. Enter Staff period
4. Enter Facility ID

Installation Interface

Figure 42
6 1 7 3 8 5 4 9 2
10
1. Enter Installation ID
2. Enter Installation name
3. Enter Installation type
4. Enter Installation address
5. Enter Customer ID

Equipment Interface
Figure 43
6
7 1
8 2 4 9 5 3 10 11
1. Enter equipment ID
2. Enter Equipment name
3. Enter Equipment type
5. Enter Staff ID
6. Enter Quantity

Facility Interface
Figure 44
3
2 4 5 1 6 7
2. Enter Facility type

Payment Interface
Figure 45
4 1 5 8
2 3 9 6 7
1. Enter Payment ID
2. Enter Payment name
3. Enter Payment date
9. Click “Submit” to approve your selection to move on with the procedure

UML Diagram (Unified Modeling Language)
Use case diagram
Figure 46

Class Diagram
Figure 47

Activity Diagram
Figure 48

Suggested future improvement and recommendations for an effective system
For further improvement and future improvement of the database management

system that was created for the Polly Pipe water sport provider, many changes can be
made to the system, starting from a much more user-friendly interface to an advanced
online- based dynamic system.
The system that I modified to meet the needs of the company is a basic
functional system that is only for use within the company’s margins. We can design
the entire system to be online and usable by customers. When it comes to customers,
they are frequently looking for the simplest way to complete tasks. So, we can have a
website designed separately by the company and configure things accordingly. We
can connect the improved Polly pipe database to the website, create and identification
and authentication mechanism and grant customers credentials access to the website
to place orders. As a results, customers can save time by not having to go to the
company’s premises to place orders, and the company will have more online
reputations to improve their profit percentages. Although the interface shown above is
clearly not user-friendly, when it comes to the interaction and implementation of a
good system, these things must be polished and made more user-friendly, which
should include a variety of features in order to provide a much more efficient and
reliable user experience.
Furthermore, as the company’s system backend is improved, we will be able

to have a more secure authentication method for logging into the Polly Pipe system,
divided into user groups with access permissions.
As the system is brought online, a set of dedicated servers should be
networked to the computers on the inside, because the system must be dynamic and
fast online in order to provide prompt responses to customers.

Gantt chart of my assignment progress
Figure 49


Ruzan DDD Final Assignment - 082903

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

Ruzan DDD Final Assignment - 082903

Uploaded by

Copyright:

Available Formats

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

Programme title BTEC HND in Computing

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

Mohamed Ruzan Unit 04- Database Design &Development 1

Unit Title Unit 04: Database Design & Development

Assignment Number 1 Assessor Miss.Ishani

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:

Mohamed Ruzan Unit 04- Database Design &Development 2

Given answers are good enough.

Feedback: Student to Assessor

Mohamed Ruzan Unit 04- Database Design &Development 3

Mohamed Ruzan Unit 04- Database Design &Development 4

Word Processing Rules

Mohamed Ruzan Unit 04- Database Design &Development 5

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

Mohamed Ruzan Unit 04- Database Design &Development 6

Unit Number and Title Unit 4: Database Design & Development

Academic Year 2021/22

Unit Tutor Miss.Ishani

Assignment Title Data base system for Polly Pipe

Issue Date 06.07.2022

Submission Date 15.10.2022

IV Name & Date

Mohamed Ruzan Unit 04- Database Design &Development 7

Staff Management Record

Equipment Type Table

Mohamed Ruzan Unit 04- Database Design &Development 8

Installation Installation Installation Customer Equipment Types of Staff Period of

Mohamed Ruzan Unit 04- Database Design &Development 9

Mohamed Ruzan Unit 04- Database Design &Development 10

Mohamed Ruzan Unit 04- Database Design &Development 11

LO1 Use an appropriate design tool to design a relational

P1 Design a relational database system using appropriate

D1 Evaluate the effectiveness of the design in relation to

Mohamed Ruzan Unit 04- Database Design &Development 12

P2 Develop the database system with evidence of user

P3 Implement a query language into the relational database

M2 Implement a fully functional database system that

M3 Assess whether meaningful data has been extracted

Mohamed Ruzan Unit 04- Database Design &Development 13

P4 Test the system against user and system requirements.

M4 Assess the effectiveness of the testing, including an

P5 Produce technical and user documentation.

M5 Produce technical and user documentation for a fully

D3 Evaluate the database in terms of improvements

Mohamed Ruzan Unit 04- Database Design &Development 14

Mohamed Ruzan Unit 04- Database Design &Development 15

Mohamed Ruzan Unit 04- Database Design &Development 16

Mohamed Ruzan Unit 04- Database Design &Development 17

What are Requirements?

There are 2 main requirements