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
Y/N
• Identifying opportunities for
improved performance?
Y/N
• Agreeing actions?
Does the assessment decision need Y/N
amending?

Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if required)
Date
Confirm action completed
Remedial action taken
Give details:

Assessor signature Date

Internal Verifier
signature Date
Programme Leader
signature (if required) Date
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.

Pass, Merit & Distinction P4 M4 D2
Descripts

LO4 Produce technical and user documentation.

Pass, Merit & Distinction P5 M5 D3
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

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor Date
signature

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.

Student’s Signature: Date:

(Provide E-mail ID) (Provide Submission Date)
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:
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
Installation ID Installation
Installation Customer Equipment Types of Staff Period of
Type Name and Required Staff
Address assignment
234 Freshwater Oak House, Lee A. sun 2 air pumps 1 x Carpenter From 1st
Tropical 17 Wroxton 200 gallons 1 x Aquatics September
Road, fish tank installer 2012
Hertfordshire 1 x standard 1 x Electrician
, H5 667 thermostat
654 Freshwater Bayliss Sally Dench 2 air pumps 5 x Carpenters 1st June
Cold House, 200 gallons 1 x Installation 2005 – 1st
Orange fish tank Manager June 2011
Street, Kent, Large Gravel 1 x Aquatics
K7 988 Bag installer
2 x standard 1 x Plumber
thermostats 3 x Labourers
767 Marine Eaglestone Perry 2 x 200 10 x Carpenters From 30th
Castle, Vanderrune gallons fish 2 x Installation June 2012
Eaglestone, tanks Manager
Kent 500 Wood 1 x Aquatics
panels installer
1 x Plumber
3 x Labourers
943 Marine 23 Sackville Eric 2 air pumps No staff required
Street, Wilts. Mackintosh 200 gallons
W55 fish tank
1 x standard
thermostat
157 Freshwater Humbertson Perry 2 air pumps 1 x Aquatics 1st
Tropical Castle, Kent, Vanderrune 400 gallons installer September
K8 fish tank 2005 – 1st
3 x standard September
thermostat 2012

Instillation Management Form

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.
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title BTEC HND in Computing
Assessor Internal
Verifier
Unit(s) Unit 04: Database Design & Development
Assignment title Database Solution for Polly Pipe
Student’s name
List which assessment Pas s Merit Distinction
criteria the Assessor has
awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded
match those shown in the assignment Y/N
brief?
Is the Pass/Merit/Distinction grade
awarded Y/N
justified by the assessor’s comments on
the
student work?
Has the work been assessed accurately? Y/N

Is the feedback to the student:

Give details:
• Constructive? Y/ N
• Linked to relevant assessment criteria? Y/ N
• Identifying opportunities for improved Y/ N
performance?
• Agreeing actions? Y/N

Does the assessment decision need

amending? Y/N
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
signature (if required) Date
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID
Unit Title Unit 04: Database Design & Development
Assignment Number 1 Assessor
Date
Submission Date Received 1st
submission
Re-submission Date Date Received 2nd
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
systemdesign Pass, Merit & Distinction P2 P3 M2 M3 D2
Descripts
LO3 Test the system against user and system requirements. Pass, Merit & Distinction P4
M4
D2 Descripts

LO4 Produce technical and user documentation. Pass, Merit & Distinction P5 M5
D3 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

Action Plan

Summative feedback

Feedback: Student to Assessor

Assesso r signatur e Date

Student signatur e Date
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 sideprinting.
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 NewRoman.
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 ontime.
5. You must take responsibility for managing your own timeeffectively.
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 thecourse
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)
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:
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 House, Lee A. sun
2 air 1 x Carpenter From 1st
Tropical 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 Humbertson Perry 2 air pumps 1 x Aquatics 1st
Tropical Castle, Kent, Vanderrun 400 gallons installer Septembe
K8 e fish tank r 2005 –
3 x standard 1st
thermostat Septembe
r 2012
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.

M.A.M.Akram database Design and Development P a g e | 12

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.
Contents
Activity 1............................................................................................................................................7

1.1. Designing a Relational Database System.............................................................................8

1.1.1. The User and the System Requirements of the Polly Pipe System..............................8

1.1.2. Designing the ER Diagram...........................................................................................9

1.1.3. Designing the Relational Database Model.................................................................12

1.2. Designing a Fully Functional System................................................................................15

1.2.1. Normalization.............................................................................................................15

1.2.2. Interfaces of the Polly Pipe System............................................................................18

1.2.3. Validation Mechanisms..............................................................................................23

1.3. ERD vs User and System Requirements............................................................................24

Activity 2..........................................................................................................................................25

2.1. Developing The Database System.....................................................................................25

2.1.1. SQL DDL Statements of the Polly Pipe System........................................................25

2.1.2. Evidence of Insert, Update and Delete Queries of the System in Visual Studio........28

2.1.3. Implementation of Validation Methods......................................................................33

2.1.4. Example for Join Query..............................................................................................34

2.2. Implementing Query Language into the Relational Database System..............................35

2.2.1. Usage of DML............................................................................................................35

2.3. System Security and Database Maintenance.....................................................................36

2.3.1. Security Mechanisms..................................................................................................36

2.4. Meaningful extraction of data............................................................................................42

2.4.1. Usage of SQL Statement............................................................................................42

Activity 3..........................................................................................................................................44

3.1. Testing................................................................................................................................44
 3.1.1. Test plan......................................................................................................................44

3.1.2. Test Plan of Polly Pipe System...................................................................................46

3.1.3. Test cases....................................................................................................................48

3.2.................................................................................................................................................50

3.2.1. Effectiveness of Testing.............................................................................................50

3.3. Evaluating the Effectiveness of the Database Solution.....................................................51

3.3.1. Evaluation from the Feedbacks..................................................................................51

Activity 4..........................................................................................................................................54

4.1. Technical and User Documentation...................................................................................54

4.1.1. User Guide..................................................................................................................54

4.1.2. Technical Guide..........................................................................................................56

4.2. Technical Documentation for A Fully Functional System................................................57

4.2.1. Diagrams.....................................................................................................................57

4.3 Ensuring Continued Effectiveness of Database System....................................................60

4.3.1. Future improvements..................................................................................................60

Self-Criticism...................................................................................................................................61

References........................................................................................................................................63

Gantt Chart.....................................................................................................................................64
Figure 1 ER Model...................................................................................................................................................... 24
Figure 2 ER Logical Diagram....................................................................................................................................... 25
Figure 3...................................................................................................................................................................... 34
Figure 4 Equipment Type........................................................................................................................................... 35
Figure 5 Customer Table............................................................................................................................................ 36
Figure 6 Installation Management......................................................................................................................... 37
Figure 7 Equipment Usage Table................................................................................................................................38
Figure 8 Staff Required............................................................................................................................................... 39
Figure 9 SQL DDL statements 01................................................................................................................................ 41
Figure 10 SQL DDL statements 02.............................................................................................................................. 42
Figure 11 Select.......................................................................................................................................................... 43
Figure 12 Where......................................................................................................................................................... 44
Figure 13 Update........................................................................................................................................................ 45
Figure 14 Between..................................................................................................................................................... 46
Figure 15 In................................................................................................................................................................. 47
Figure 16 Group by..................................................................................................................................................... 48
Figure 17 Order by..................................................................................................................................................... 49
Figure 18 Having......................................................................................................................................................... 50
Figure 19 feedback Form 01....................................................................................................................................... 53
Figure 20 feedback Form 02....................................................................................................................................... 54
Figure 21 feedback Form 03....................................................................................................................................... 55
Figure 22 1.1 Login and Home....................................................................................................................................56
Figure 23 Home.......................................................................................................................................................... 58
Figure 23 Home.......................................................................................................................................................... 58
Figure 24 Insert record.............................................................................................................................................. 59
Figure 24 Insert record.............................................................................................................................................. 59
Figure 25 Update record............................................................................................................................................ 60
Figure 25 Update record............................................................................................................................................ 60
Figure 26 1.3 Delete record.................................................................................................................................... 61
Figure 27: Installation Interface................................................................................................................................. 61
Figure 28: PAYMENT _UNIT InterfaceFigure 27: Installation Interface.......................................................................61
Figure 28: PAYMENT _UNIT Interface........................................................................................................................ 62
Figure 29: Installation Type InterfaceFigure 28: PAYMENT _UNIT Interface..............................................................62
Figure 29: Installation Type Interface.........................................................................................................................62
Figure 29: Installation Type Interface.........................................................................................................................62
Figure 30 Payment..................................................................................................................................................... 63
Figure 27: Installation InterfaceFigure 30 Payment................................................................................................... 63
Figure 31 Equipment.................................................................................................................................................. 63
Figure 31 Equipment.................................................................................................................................................. 63
Figure 32 Employee installation................................................................................................................................. 63
Figure 32 Employee installation................................................................................................................................. 63
Figure 33 Class Diagram............................................................................................................................................. 66
Figure 33 Class Diagram............................................................................................................................................. 66
Figure 34 Use Case Diagram....................................................................................................................................... 67
Figure 34 Use Case Diagram....................................................................................................................................... 67
Figure 35 DFD (0) LEVEL DIAGRAM.............................................................................................................................70
Figure 35 DFD (0) LEVEL DIAGRAM.............................................................................................................................70
Figure 36 DFD (1) LEVEL DIAGRAM.............................................................................................................................71
Figure 36 DFD (1) LEVEL DIAGRAM.............................................................................................................................71
Figure 37 Flow Charts................................................................................................................................................ 72
Figure 37 Flow Charts................................................................................................................................................ 72
Figure 38 Insert.......................................................................................................................................................... 73
Figure 38 Insert.......................................................................................................................................................... 73
Figure 39 Update........................................................................................................................................................ 74
Figure 39 Update........................................................................................................................................................ 74
Figure 40 Delete......................................................................................................................................................... 75
Figure 40 Delete......................................................................................................................................................... 75
Activity 01
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 normalized. If not, normalize the database by removing the anomalies.

1.1 User requirements

Polly Pipe, situated in Braintree, England, may be a water sports provider and installation.
They must design and implement a database that satisfies the information needs. These
requirements are stated in this scenario, and examples of the paper records preserved by the
Polly Pipe are shown below. Polly Pipe focuses on placing aquariums with business clients.
Customers can request many installations, but each one is customized for a specific
consumer. Types of facilities are categorized. Every facility has one or more staff assigned to
it. Because these facilities are sometimes rather large, carpenters and masons will be
employed as well as water installers. Aquariums, air pumps, and thermostats are used in the
facility. During a facility, there are frequently many PCs. (Work of the author) Specifications
for the system the developers employ system requirements to construct the system. These are
the needs that necessitate a considerably more in- depth understanding of the system. The
following are the different types of system requirements:

1) Functional requirements

2) Nonfunctional requirements
1 Functional requirements

Functionality requirements define what the system developer must include in the system in
order to create the needed system, i.e., they are required for the system to function.

3 Nonfunctional requirements
They are also called qualities of a system. Non-functional requirements define all the
remaining requirements that are not included in functional requirements. There are many
types of non-functional requirements. There are two types mainly:

Execution qualities: - security and usability, which are observable at run time. Evolution
qualities: - testability, maintainability, extensibility and scalability, which are embodied in
the static structure of the software system.
 1.2 System Requirement Specification

This is the System Requirement Specification of the Polly Pipe system that is to be designed.
This will provide a summary of the system and why it is built.

1) The Purpose

The purpose of this SRS is to provide a clear notion of what the system should be and what
its requirements should be to the software developer who will construct the system for Polly
Pipe. It was created for Polly Pipe's basic staff to make their manual labor, which comprises
paper-based activities, easier. The only thing left to accomplish after the software is to
appropriately update the master database so that the computerized system can assist staff
with their daily office tasks.

2) The Scope

The program assists Polly Pipe's paper-based operations team in keeping track of equipment
and other data up to date, as well as doing their jobs efficiently and properly, without
consciously or accidentally misplacing orders, causing customers to wait longer for their
purchases. (Technical goal, 2021)
 1.3 Design a relational database system using conceptual design (ER Model) by
including identifiers (primary Key) of entities and cardinalities, participations
of relationships

Figure 1 ER Model
1.4 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.

Figure 2 ER Logical Diagram

 1.5 Check whether the provided logical design is normalized. If not, normalize the
database by removing the anomalies.
1) Database Normalization

The process of organizing data into tables in such a way that the results of accessing the
database are always explicit and as intended is known as database normalization. A
relational database has them built in. This has the side consequence of duplicating data
within the database, resulting in the establishment of a new database. A database is made up
of a few key components. They are as follows:

i. Key

ii. Primary Key

iii. Composite Key

iv. Foreign key

v. Transitive Functional dependency

2) Key

A key is a value used to uniquely identify a record in a table. It might be a single column or a
collection of columns. Non-key columns are those in a table that do not specifically identify
a record.

3) composite key

Composite key can be defined as a primary key composed of multiple columns used to
identify a record specifically.
 4) Foreign key

Foreign key can be defined as a column of data in one table that connects to the primary key
data in the original table acting as a bridge.

5) Transitive Functional dependency

The term "transitive dependency" refers to an indirect relationship between table data that
leads to functional dependency. Any transitive dependency must be removed in order to
meet the Third Normal Form (3NF) normalization standard.
Examples of Database Normalization

There are a few methods of Database Normalization. They are:

i. First Normal Form

ii. Second Normal Form

iii. Third Normal Form

iv. Boyce Codd Normal Form (or 3.5 Normal Form)

v. Fifth Normal Form

vi. Sixth Normal Form

But the most widely used forms of Normalization are

i. First Normal Form

ii. Second Normal Form

iii. Third Normal Form

For example, in a rent a car database without any normalization, all information is stored in
one table as shown below.
 Table 1 First Normal Form

Name Phone Number Vehicle No Vehicle Type Payment Type

Akram 0757563815 EX 0085 Car Cheque

Niranjan 0775933454 AB 5524 Van Cash

Waseem 0775273214 DBU 4771 Bike Cash

1NF (First Normal Form)

Each table cell should contain a single value. Each record needs to be unique.
 Table 2 Table 2 Second Normal Form

Name Phone Number Vehicle No Vehicle Type

Akram 0757563815 EX 0085 Car

Niranjan 0775933454 AB 5524 Van

Waseem 0775273214 DBU 4771 Bike

2NF (Second Normal Form) Rule 1- Be in 1NF

Rule 2- Single Column Primary Key
It is clear that we can't move forward to make our simple database in 2nd Normalization
form unless we partition the table above.

Table 3 Second Normal Form

Customer ID Name Phone Number

01 Akram 0757563815
02 Niranjan 0775933454
03 Waseem 0775273214

I have divided my 1NF table into two Tables viz. Table 1 and Table2. Table 1 contains
customer information. Table 2 contains information on this specific database. We have
introduced a new column called Customer ID which is the primary key for table 1. Records
can be uniquely identified in Table 1 using Customer ID.
3NF (Third Normal Form) Rule 1- Be in 2NF
Rule 2- Has no transitive functional dependencies
To move our 2NF table into 3NF, we again need to divide our table.
Table 4 Table 3 Third Normal Form

Customer ID Vehicle No
01 EX 0085
02 AB 5524
03 DBU 4771

Table 5 Table 4 Third Normal Form

Customer ID Name Phone Number Payment Type

01 Akram 0757563815 Cheque
02 Niranjan 0775933454 Cash
03 Waseem 0775273214 Cash
1.1 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.

RDD (relational database design) is a database design that organizes information and data into tables with rows
and columns. Relational databases are manipulated using the Structured Query Language (SQL). A relational
database is built in four stages, each of which involves modeling the data into a series of related tables. The stages
are as follows:

a. Define relations/attributes
b. Define primary keys
c. Define relationships
d. Normalization

The process of normalization involves removing duplication from a relation or group of relations. Anomalies in
insertion, deletion, and updation can be caused by relation redundancy. As a result, it aids in reducing relational
redundancy. Normal forms are used in database tables to eliminate or decrease redundancy.

a) Normalization is the process of organizing the data in the database.

b) Normalization is used to minimize the redundancy from a relation or set of relations.
It is also used to eliminate the undesirable characteristics like Insertion, Update and Deletion Anomalies.
c) Normalization divides the larger table into the smaller table and links them using relationship.
d) The normal form is used to reduce redundancy from the database table.

Normalization is a database design approach that avoids undesired characteristics such as Insertion, Update, and
Deletion Anomalies by reducing data redundancy. Normalization rules break huge tables into smaller tables and
use relationships to connect them. The goal of SQL normalization is to reduce duplicate (repetitive) data and
ensure logical data storage.
With the introduction of the First Normal Form, the architect of the relational model, Edgar Codd, presented the
idea of data normalization, which he continued to enhance with the Second and Third Normal Forms. Later, he
collaborated with Raymond F. Boyce to establish the Boyce-Codd Normal Form theory.
 1. Management

Figure 3
2. Equipment Type

Figure 4 Equipment Type

 3. Customer Table

Figure 5 Customer Table

 4. Installation Management

Figure 6Installation Management

5. Equipment Usage Table

Figure 7 Equipment Usage Table

6. Staff Required

Figure 8 Staff Required

Attributes in relational databases are the defining qualities or properties that define all objects belonging to a
specific category and are applied to all cells in a column.

The rows, on the other hand, are referred to as tuples, and they contain data sets that have been applied to a single
entity in order to uniquely identify each item. As a result, attributes are the features that assist characterize the
unique properties of each individual tuple.

Consider a table in a relational database to be the electronic equivalent of a spreadsheet. A spreadsheet attribute is
merely one non-null cell or the intersection of a column and a row.

It only saves one piece of information about the item represented by the table where the attribute is stored. The
tuple may be an Invoice entity, for example. An invoice's properties are Price, Number, Date, and Paid/Unpaid.

There are various sorts of attributes accessible, in addition to the self-explanatory simple or single-valued
attributes.

A composite characteristic is one that is made up of many simple attributes. An employee entity's Address
attribute, for example, could include the characteristics Street, City, Postal code, and Country.

A multivalued attribute is one that allows for several descriptions to be specified. An employee object, for
example, may contain multiple Email ID properties in the same cell.

An ID, key, letter, or number that uniquely identifies that item is referred to as a key attribute or primary attribute.
It could, for instance, be the invoice number (e.g., the individual ID of that invoice). A table with a single key
characteristic is referred to as a strong entity. If a table is generated from other tables, it may have more than one
key attribute.

Derived characteristics are derived from other qualities, either directly or through specialized formula outcomes,
as the name implies. For instance, the Employee's Age attribute may be calculated from the Date of Birth
element. In other cases, a formula may be used to calculate the VAT of a certain payment, so that whenever the
cell with the attribute Payment is filled, the cell with the derived attribute VAT calculates its value automatically.
 Activity 02

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

Figure 9 SQL DDL statements 01

Figure 10 SQL DDL statements 02
 2.2 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

1. Select

Figure 11 Select
2. Where

Figure 12 Where
3. Update

Figure 13 Update
4. Between

Figure 14 Between
 5. In

Figure 15 In
6. Group by

Figure 16 Group by
7. Order by

Figure 17 Order by
8. Having

Figure 18 Having
Activity 03

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.

Table 5 User_Manage Test Plan

Test Case Name: User_Manage

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description: Insert, Update, Select

Table 6 Staff_Management Test Plan

Test Case Name: Staff_Management

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description Insert, Update, Select

Table 7 Customer_Manage Test Plan

Test Case Name: Customer_Manage

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description: Insert, Update, Select
Table 8 Equipment _Manage Test Plan

Test Case Name: Equipment _Manage

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description: Insert, Update, Select

Table 8 Installation _Management Test Plan

Test Case Name: Installation _Management

System: Polly Pipe management system
Design By: M.A.M.Akram
Design Date: 20/8/2021
Description: Insert, Update, Select

Table 9 Equipment_Usage_Manage Test Plan

Test Case Name: Equipment_Usage_Manage

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description: Insert, Update, Select

Table 10 Staff_Required_Manage Test Plan

Test Case Name: Staff_Required_Manage

System: Polly Pipe management system
Design By: M.A.M. Akram
Design Date: 20/8/2021
Description: Insert, Update, Select
Table 11 User_Manage test

Test Test Case Test Data Expected Actual Result Status

ID Result
User_ID:1 Data should
1 Inserting User_Name:Akram be
User_Manage Bod:1999-04-17 saved in the 
Address:73/6, moor User_Mana ge
street, Trincomalee
phone_no: 0775933454
password:12345

User_name:Karish an Data should

2 Update Address:3m kata be 
User_Manage updated in the
User_Mana ge

User_ID: User_Name: Data should

3 Select Bod: Address: be
User_Manage phone_no: password: Selected in the 
User_Mana ge
 Staff_ID:3 Data should
4 Inserting Staff_Name:Waze em be
Staff_Manage Address:trincomal ee saved in the 
ment phone_Number:07 Staff_Man
75933454 agement
Staff_NIC:199910
810026

Staff_Name:rathee Data should

5 Update shan Address:kinniya be 
Staff_Manage updated in the
ment Staff_Man
agement

Staff_ID: Staff_Name: Data should

6 Select Address: be
Staff_Manage phone_Number: Selected in the 
ment Staff_NIC: Staff_Man
agement

Table 12 Staff_Management test

 Customer_ID:3 Data should
7 Inserting customer_name: be
customer_Ma Wazeem saved in the 
nage NIC:199910810026 customer_
[Address]: Manage
Trincomalee
Installation_ID: 234
Staff_ID: SHA1

customer_name:ra Data should

8 Update theeshan [Address]: be 
customer_Ma kinniya updated in the
nage customer_
Manage

Customer_ID: Data should

9 Select customer_name: NIC: be
customer_Ma [Address]: Selected in the 
nage Installation_ID: customer_
Staff_ID: Manage

Table 13 Customer_Manage test

 Customer_ID:3 Data should
10 Inserting customer_name: be
Equipment_ Wazeem saved in the 
Manage NIC:199910810026 Equipment
[Address]: _Manage
Trincomalee
Installation_ID: 234
Staff_ID: SHA1

customer_name:ra Data should

11 Update theeshan [Address]: be 
Equipment_ kinniya updated in the
Manage Equipment
_Manage

Customer_ID: Data should

12 Select customer_name: NIC: be
Equipment_ [Address]: Selected in the 
Manage Installation_ID: Equipment
Staff_ID: _Manage

Table 14 Equipment _Manage test

 Installation_ID:5 Data should
13 Inserting Installation_type: be
Installation_ Freshwater Tropical saved in the 
Management Staff_ID: SHA67 Installation
Period_of_staff_as _Managem
signment: No staff ent
required

Installation_type: Data should

14 Update Freshwater Tropical be 
Installation_ Period_of_staff_as updated in the
Management signment: 1st april Installation
2015 – 1st _Managem
June 2021 ent

Installation_ID: Data should

15 Select Installation_type: be
Installation_ Staff_ID: Selected in the 
Management Period_of_staff_as Installation
signment: _Managem
ent

Table 15 Installation _Management test

 EU_ID:6 Data should
16 Inserting Equipment_Name: 2 be
Equipment_U air pumps saved in the 
sage_Manage 200 gallons Equipment
fish tank _Usage_Ma
Installation_ID: 456 nage
Staff_ID: SHA67

Data should
17 Update Equipment_Name: 2 be 
Equipment_U air pumps, 200 gallons updated in the
sage_Manage tank Equipment
_Usage_Ma
nage

EU_ID: Data should

18 Select Equipment_Name: be
Equipment_U Installation_ID: Selected in the 
sage_Manage Staff_ID: Equipment
_Usage_Ma
nage

Table 16 Equipment_Usage_Manage Test

 Staff_Required_ID Data should
19 Inserting :6 be
Staff_Require Types_of_Staff_Re saved in the 
d_Manage quired:1xCarpente Staff_Requ
r,1xAquatics ired_Mana ge
installer,1xElectric ian
Installation_ID: 456
Staff_ID: SHA67

Data should
20 Update Types_of_Staff_Re be 
Staff_Require quired:1xCarpente updated in the
d_Manage r,1xAquatics installer Staff_Requ
ired_Mana ge

Staff_Required_ID Data should

21 Select : be
Staff_Require Types_of_Staff_Re Selected in the 
d_Manage quired: Staff_Requ
Installation_ID: ired_Mana ge
Staff_ID:

Table 17 Staff_Required_Manage Test

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.

Figure 19 feedback Form 01

Figure 20 feedback Form 02
Figure 21 feedback Form 03
Activity 04

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.

4.1 Prepare a simple users’ guide and a technical documentation for the support and maintenance of
the software.

1. User documentation

1.1 Login and Home

The development of user documentation is left until the end of the test documentation phase. If they are created in
advance, some parts of the system may change due to a failure detection. The user documentation is provided to
the user who provides a general description of the use of the system. Paper-based user documents are usually in
the form of a brochure or file.
The Poly Pipe Service start up with login form. In this form shows userID and password textboxes. If you login
the system must input correct userID and password.

Figure 22 1.1 Login and Home

Figure 23 1.1 Login and Home

Figure 24 HomeFigure 25 1.1 Login and Home

Figure 26 1.1 Login and Home

After login the system next form is main menu. In this form click the option.

Figure 27 Home

Figure
By 28 Homean option in main menu next form is into selecting option. There are two tabs that first details and
selecting
second report. In the details tab have add button, search button, update button, delete button and also main menu
Figure 29 Insert recordFigure 30 Home
and logout buttons.

Figure 31 Home
Fill the textboxes with data then click the Save button to insert new data in database.

Figure 32 Insert record

Figure 33 Insert record

Figure 34 Update recordFigure 35 Insert record

Figure 36 Insert record

 1.2 Update record

After search a record update the data and click the update button to change the data in database.

Figure 37 Update record

Figure 38 Update record

Figure 39 1.3 Delete recordFigure 40 Update record

Figure 41 Update record

 1.3 Delete record

After search a record click the delete the button to delete all data in this record.

Figure 42 1.3 Delete record

Figure 43 1.3 Delete record

Figure 44 EquipmentFigure 45 1.3 Delete record

Figure 46 1.3 Delete record

Figure 47: Installation Interface

Figure 48: PAYMENT _UNIT InterfaceFigure 49: Installation Interface

Figure 50: PAYMENT _UNIT Interface

Figure 51: Installation Type InterfaceFigure 52: PAYMENT _UNIT

PAYMENT UNIT GUI

Figure 56: PAYMENT _UNIT Interface

Figure 57: Installation Type InterfaceFigure 58: PAYMENT _UNIT Interface

Figure 59: Installation Type Interface

Figure 60: Installation Type InterfaceFigure 61: PAYMENT _UNIT Interface

Figure 62: Installation Type InterfaceFigure 63: PAYMENT _UNIT Interface

Figure 64: Installation Type Interface

Figure 65: Installation Type Interface

Figure 66 1.1 Login and HomeFigure 67: Installation Type Interface

Figure 68: Installation Type Interface

 EMPLOYEE _INSTALLATION GUI

Figure 69 Payment

Figure 70: Installation InterfaceFigure 71 Payment

Figure 72: Installation Interface

Figure 73: PAYMENT _UNIT InterfaceFigure 74: Installation

InterfaceFigure 75 Payment

Figure 76: Installation InterfaceFigure 77 Payment

Figure 78 Employee installation

Figure 79 Employee installation

Figure 80 PaymentFigure 81 Employee installation

Figure 82 Employee installation

Figure 83 Equipment

Figure 84 Equipment

Figure 85 Class DiagramFigure 86 Equipment

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

2.1 Technical documentation

Table 18 technician documentation

Item Specification Quantity Have to purchase or Available

Hardware

RAM 4 GB
01 Available
Hard Disk 8 GB
01 Available
Processor Intel i5 or Ryzen 5
01 Available
Software

Operating system Windows 10 or

Windows 11 01 Available
Visual Studio Ultimate
2019 01 Available
Sql Server
2008 R2 01 Available
 2.2 Diagrams

Class Diagram

Figure 88 Class Diagram

Figure 89 Class Diagram

Figure 90 Use Case DiagramFigure 91 Class Diagram

Figure 92 Class Diagram

Use Case Diagram

UML diagrams are used to sort and evaluate a variety of systems. They enable you to visualize the various styles
of roles in a system and how those roles interact with it. As previously stated, use case diagrams are used to
gather a system's usage demand. Depending on your needs, you'll be able to apply that information in a variety of
ways.
The system is used to draw a parallelogram outlining the scope of the utilization instance. When it comes to
visualizing large systems, this ex-gratia portion is really useful.
 Figure 93 Use Case Diagram

Figure 94 Use Case Diagram

Figure 95 DFD (0) LEVEL DIAGRAMFigure 96 Use Case Diagram

Figure 97 Use Case Diagram

A static diagram could be a class diagram. It represents AN application's static read. The category diagram is used
not only for visualizing, describing, and documenting many parts of a system, but also for writing usable code for
the code application.

The qualities and actions of a category, as well as the system's constraints, are depicted in a class diagram.
Because they're the only UML diagrams that can be mapped directly with object-oriented languages, category
diagrams are widely used in the modeling of object-oriented systems.
The information in a flow chart diagram should be represented in the order in which water travels through the
facility from the point of entry to the site or building, to the outlets and note all connecting water lines, flushing
points and direction of flow.
Information flow diagrams, also referred to as DFDs, are used to illustrate the movement of data in a corporate
data system diagrammatically. DFD refers to the procedures that occur during the transfer of data from the input
to the file storage and report generating stages of a system. There are two types of information flow diagrams:
logical and physical. The logical information flow chart depicts the flow of data through a system in order to
ensure the efficiency of a firm. The physical information flow chart depicts how the logical information flow is
implemented. The functions, or processes, that capture, manipulate, store, and distribute information between a
system and its environment, as well as between pieces of a system, are represented by the DFD diagrammatically.
DFD (0) LEVEL DIAGRAM

Figure 98 DFD (0) LEVEL DIAGRAM

Figure 99 DFD (0) LEVEL DIAGRAM

Figure 100 DFD (1) LEVEL DIAGRAMFigure 101 DFD (0) LEVEL DIAGRAM

Figure 102 DFD (0) LEVEL DIAGRAM

DFD (1) LEVEL DIAGRAM

Figure 103 DFD (1) LEVEL DIAGRAM

Figure 104 DFD (1) LEVEL DIAGRAM

Figure 105 Flow ChartsFigure 106 DFD (1) LEVEL DIAGRAM

Figure 107 DFD (1) LEVEL DIAGRAM

 2.3 Flow Charts

Login

Figure 108 Flow Charts

Figure 109 Flow Charts

Figure 110 InsertFigure 111 Flow Charts

Figure 112 Flow Charts

Insert

Figure 113 Insert

Figure 114 Insert

Figure 115 UpdateFigure 116 Insert

Figure 117 Insert

Update

Figure 118 Update

Figure 119 Update

Figure 120 DeleteFigure 121 Update

Figure 122 Update

Delete

Figure 123 Delete

Figure 124 Delete

Figure 125 Delete

Figure 126 Delete

4.2 Suggest the future improvements that may be required to ensure the continued effectiveness of the
database system.

Future improvements for poly pipe services system

The info system for poly pipe services is intended to help within the day-after- day procedures of the Company.
it's designed to change all manual operations to laptop base system. this technique must be improved in future to
develop the system. such are few concepts here.

The last item on the list of vital information security measures is to possess regular security checks associated
data backups. For a sudden attack or data breach, it is terribly helpful for a company to make a copy your data. to
possess a sure-fire business, you want to maintain the habit of mechanically or manually backing up data every
week or each day.

In addition, the info should be protected by up-to-date computer code and effective antivirus tools. However, to
realize this, you wish a progressive and economical IT service. make sure to rent somebody with the talents to try
to the work properly.

In examining operations and processes to mitigate cyber-attacks, a very important step is to arrange a listing of
security measures and data security policy. this kind of arrange of a company might facilitate considerably in
essential things and response times to incidents. because of the policies, you'll react instantly to avoid the intense
impacts of a cyber-attack.
Another main object that we've to contemplate is security of the database, since we have given 2 varieties of
access to the system organism users and admin, however within the future, there'll be some high-level users that
require some rights from the admin, then we have to form middle sort access to those high- level users in between
the admin and commonplace user.

As in the case of management and access rights, worker access is often simply known, and you've got to seek out
who in your organization might are violated. it's important to recollect that a policy and method arrange is barely
valid for your last review. Technology, trade rules and best practices are perpetually evolving. somebody ought to
have this political process and guide and continuously trying for new ways to update to take care of its relevance.
References

What is Data Manipulation? 2021. What is Data Manipulation? [ONLINE] Available at:
https://www.computerhope.com/jargon/d/datamani.htm. [Accessed 1 May 2022].

Looker. 2021. What is Database Security? Definition, Types & Importance | Looker [ONLINE] Available at:
https://looker.com/definitions/database-security. [Accessed 1 May 2022].

SQL ORDER BY Clause. 2021. SQL ORDER BY Clause. [ONLINE] Available at: http://beginner-sql-
tutorial.com/sql-order-by-clause.htm. [Accessed May04 2022].

IT Pro. 2021. Certifiably SQL: Data Constraints and Integrity | IT Pro. [ONLINE]Available at:
http://www.itprotoday.com/microsoft-sql- server/certifiably-sql-data-constraints-andintegrity.
[Accessed 5 May 2022

Techopedia. 2021. What is a Not Null Constraint? - Definition from Techopedia. [ONLINE] Available at:
https://www.techopedia.com/definition/27370/not-null- constraint. [Accessed 6 May 2022].

Techopedia. 2021. What is an Integrated Development Environment (IDE)? – Definition from Techopedia.
[ONLINE] Available at: https://www.techopedia.com/definition/26860/integrated-development-
environment-ide. [Accessed 6 May 2022].

SQL - ORDER BY Clause - Tutorials point. 2021. SQL - ORDER BY Clause - Tutorials point. [ONLINE]
Available at: https://www.tutorialspoint.com/sql/sql- order- by.htm. [Accessed 06 06 May 2022].

SQL - WHERE Clause - Tutorials point. 2021. SQL - WHERE Clause - Tutorials point. [ONLINE] Available at:
https://www.tutorialspoint.com/sql/sql-where- clause.htm. [Accessed 06 May 2022].