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
L.Anuhas Nethmina
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

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

L.Anuhas Nethmina DDD 00125406

Programme Leader
signature (if required) Date

L.Anuhas Nethmina DDD 00125406

Higher Nationals - Summative Assignment Feedback Form
Student Name/ID L.Anuhas Nethmina Liyanage
Unit Title Unit 04: Database Design & Development

Assignment Number 1 Assessor

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

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

L.Anuhas Nethmina DDD 00125406

 Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor Date
signature
E149603@esoft.academ 19/10/2022
Student y Date
signature

L.Anuhas Nethmina DDD 00125406

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

L.Anuhas Nethmina DDD 00125406

 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

L.Anuhas Nethmina DDD 00125406

 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.

E149603@esoft.academy
19/10/2022
Student’s Signature: Date:
(Provide E-mail ID) (Provide Submission Date)

L.Anuhas Nethmina DDD 00125406

Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number L.Anuhas Nethmina
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:

L.Anuhas Nethmina DDD 00125406

 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

L.Anuhas Nethmina DDD 00125406

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

L.Anuhas Nethmina DDD 00125406

 (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

L.Anuhas Nethmina DDD 00125406

 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.

L.Anuhas Nethmina DDD 00125406

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.

L.Anuhas Nethmina DDD 00125406

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

L.Anuhas Nethmina DDD 00125406

 1.1.1. There are two types of requirements. they are...........................................................16
1.1.2. Following are the user requirements and system requirements of the poly pipe
system 16
1.1.3. Figure-ERD...................................................................................................................17
1.1.4. Figure Relational database...........................................................................................18
1.1.5. Normalization..............................................................................................................19
1.2....................................................................................................................................................22
1.2.1. .Login form...................................................................................................................22
1.2.2. Staff details..................................................................................................................22
1.2.3. Installation details........................................................................................................23
1.2.4. Customer detals...........................................................................................................23
1.2.5. Facility details..............................................................................................................24
1.2.6. Equipment details........................................................................................................24
2...........................................................................................................................................................25
2.1. Data Definition Language (DDL): What is it?........................................................................25
2.1.1. Creating a database.....................................................................................................25
2.1.2. Creating a staff table....................................................................................................26
2.1.3. Creating a equipment table.........................................................................................26
2.1.4. Creating a facility table................................................................................................27
2.1.5. Creating a installation table.........................................................................................27
2.1.6. Creating a customer table............................................................................................28
Adding foreign keys.........................................................................................................................28
2.1.7. Figure-Adding foreign keys for staff table....................................................................28
2.1.8. Figure -Adding foreign keys for Facility table...............................................................29
2.1.9. Figure -Adding foreign keys for Equipment table.........................................................29
2.1.10. Figure Adding foreign keys for Installation table.........................................................30
2.2. Visual Studio 2022-IDE.........................................................................................................31
2.3. What Is DML........................................................................................................................33
2.3.1. Select Statement..........................................................................................................34
2.3.2. Where Statement........................................................................................................34
2.3.3. Update Statement........................................................................................................35
3.......................................................................................................................................................36
3.1. Feedback form.....................................................................................................................36
Feedbacks....................................................................................................................................37

L.Anuhas Nethmina DDD 00125406

 3.2. Test cases.............................................................................................................................38
4...........................................................................................................................................................42
4.1. System introduction.............................................................................................................42
4.2. Usecase Diagram.................................................................................................................42
4.3. Class diagram.......................................................................................................................43
4.4. Activity diagram...................................................................................................................44
4.5. User manual.........................................................................................................................45
Bibliography.........................................................................................................................................46

L.Anuhas Nethmina DDD 00125406

1.

1.1.1. There are two types of requirements. they are

1.1.1.1. system requirements

 System Requirements means the minimum requirements that need to run the
software smoothly. Examples of the system requirements are Computer,
 Operating system, Ram, Minimum free storage space, processor, Graphic card,
etc…..

1.1.1.2. user requirements

 User requirements are features that users expect from the software product to
fulfill their needs. Some of the common user requirements are maintaining a
database without any data loss, maintaining system efficiency and accuracy of the
data, etc….

1.1.2. Following are the user requirements and system requirements of the poly
pipe system

1.1.2.1. User requirements

 Maintain data accuracy

 to get all details about types of equipment, staff management table, and
Instillation Management Form
 easily access databases and find specific data
 view, update, and delete data easily
 efficiently
 secure data

1.1.2.2. system requirements

 Computer
 Operating system
 processor
 RAM
 Free storage
 Trained employee

L.Anuhas Nethmina DDD 00125406

 1.1.3. Figure-ERD

L.Anuhas Nethmina DDD 00125406

 1.1.4. Figure Relational database

L.Anuhas Nethmina DDD 00125406

 1.1.5. Normalization
Normalization is the process of organizing a database to reduce redundancy and
improve data integrity.
Normalization also simplifies the database design so that it achieves the optimal structure
composed of atomic elements (i.e. elements that cannot be broken down into smaller parts).
Also referred to as database normalization or data normalization, normalization is an
important part of relational database design, as it helps with the speed, accuracy, and
efficiency of the database.
By normalizing a database, you arrange the data into tables and columns.  You ensure that
each table contains only related data. If data is not directly related, you create a new table
for that data.
For example, if you have a “Customers” table, you’d normally create a separate table for the
products they can order (you could call this table “Products”). You’d create another table
for customers’ orders (perhaps called “Orders”). And if each order could contain multiple
items, you’d typically create yet another table to store each order item (perhaps called
“OrderItems”). All these tables would be linked by their primary key, which allows you to
find related data across all these tables (such as all orders by a given customer). (what-is-
normalization)

1.1.5.1. Benefits of Normalization

 There are many benefits of normalizing a database. Here are some of the key benefits:
 Minimizes data redundancy (duplicate data).
 Minimizes null values.
 Results in a more compact database (due to less data redundancy/null values).
 Minimizes/avoids data modification issues.
 Simplifies queries.
 The database structure is cleaner and easier to understand. You can learn a lot about a relational
database just by looking at its schema.
 You can extend the database without necessarily impacting the existing data.
 Searching, sorting, and creating indexes can be faster, since tables are narrower, and more rows fit
on a data page. (what-is-normalization)

L.Anuhas Nethmina DDD 00125406

 1.1.5.2. First Normal Form (1NF)
Multi-valued attributes, composite attributes, and their combinations are not allowed in
the first normal form. It states that a table's attribute cannot have more than one value. It
can only include characteristics with a single value.

1.1.5.3. Second Normal Form (2NF)

If a relation satisfies the following two conditions, it is in the second normal form:
-It is in first normal form.

It don't have any non-prime attribute that is functionally dependent on any proper subset
of any candidate key of the relation.

L.Anuhas Nethmina DDD 00125406

 1.1.5.4. Third Normal Form (3NF)
Data duplication is reduced with 3NF. Additionally, it is employed to ensure data
integrity.

A relation will be in 3NF if it is in 2NF and not contain any transitive partial dependency.

L.Anuhas Nethmina DDD 00125406

 1.2.

1.2.1. .Login form

1.2.2. Staff details

L.Anuhas Nethmina DDD 00125406

 1.2.3. Installation details

1.2.4. Customer detals

L.Anuhas Nethmina DDD 00125406

 1.2.5. Facility details

1.2.6. Equipment details

L.Anuhas Nethmina DDD 00125406

2.

2.1. Data Definition Language (DDL): What is it?

Using predefined commands and a particular syntax, Data Definition Language (DDL) is
used to construct and modify the structure of items in a database. Tables, sequences,
locations, aliases, schemas, and indexes are some of these database objects.

An explanation of Data Definition Language

DDL is a standardized language with commands to define the various objects, structures,
and storage groups (stogroups) in a database. Database objects like tables, indexes, and
stogroups can be created, modified, or deleted using DDL statements. DDL can also be used
to refer to any language that describes data in a general way.
SQL statements for creating and deleting databases, aliases, locations, indexes, tables, and
sequences are included in DDL. Additionally, it contains commands to modify these objects
and add or remove particular restrictions on tables, such as the following:
 UNIQUE
 PRIMARY
 FOREIGN KEY
 CHECK

An executed DDL statement has an immediate impact on the database.

Since its statements can also be used to describe, remark on, and apply labels to database
objects, DDL is occasionally referred to as the "Data Description Language."

2.1.1. Creating a database

L.Anuhas Nethmina DDD 00125406

 2.1.2. Creating a staff table

L.Anuhas Nethmina DDD 00125406

 2.1.3. Creating a equipment table

L.Anuhas Nethmina DDD 00125406

 2.1.4. Creating a facility table

2.1.5. Creating a installation table

L.Anuhas Nethmina DDD 00125406

 2.1.6. Creating a customer table

Adding foreign keys

2.1.7. Figure-Adding foreign keys for staff table

L.Anuhas Nethmina DDD 00125406

 2.1.8. Figure -Adding foreign keys for Facility table

2.1.9. Figure -Adding foreign keys for Equipment table

L.Anuhas Nethmina DDD 00125406

 2.1.10. Figure Adding foreign keys for Installation table

L.Anuhas Nethmina DDD 00125406

 2.2. Visual Studio 2022-IDE
Visual Studio 2022 is the best Visual Studio ever. Our first 64-bit IDE makes it easier to
work with even bigger projects and more complex workloads. The stuff you do every day
—like typing code and switching branches—feels more fluid and more responsive. And
out-of-memory errors? They’re about to be a distant memory.

Type less, code more

IntelliCode is a powerful set of automatic code completion tools that understand your
code context: variable names, functions, and the type of code you’re writing. This makes
IntelliCode able to complete up to a whole line at once, helping you code more
accurately and confidently.

 In the visual studio we can create the software graphically it is very easier than
coding
 We can design software graphically using this toolbox

L.Anuhas Nethmina DDD 00125406

  In visual studio ide, we can debug the software and can see how the software works
using this debug option

 This error list is the most valuable tool in visual studio. We can find what is the
errors in our code using this tool.

L.Anuhas Nethmina DDD 00125406

 2.3. What Is DML
Data Manipulation Language or DML is a subset of operations used to insert, delete, and
update data in a database. A DML is often a sublanguage of a more extensive language like
SQL; DML comprises some of the operators in the language. Selecting read-only data is
closely related and is sometimes also considered a component of a DML, as some users can
perform both read and write selection.
A popular data manipulation language is Structured Query Language or SQL, used to
retrieve and manipulate data in a relational database. With SQL, you can perform operations
on the database and also use it to create a database. SQL uses specific commands like
Create, Drop, Insert, etc., to carry out the required tasks.
DML is an abbreviation for Data Manipulation Language. Represents a collection of
programming languages explicitly used to make changes to the database, such as:
 CRUD operations to create, read, update and delete data.
 Using INSERT, SELECT, UPDATE, and DELETE commands.
 DML commands are often part of a more extensive database language, for example,
SQL (structured query language). These DMLs can have a specific syntax to handle
data in that language.

DML has two main classifications which are procedural and non-procedural programming,
which is also called declarative programming. The SQL dealing with the manipulation of
data present in the database belongs to the DML or Data Manipulation Language, including
most of the SQL statements. (satoricyber.com/dml-data-manipulation-language, 2022)

L.Anuhas Nethmina DDD 00125406

 2.3.1. Select Statement
 It is used to restrict the records from a table

2.3.2. Where Statement

 It is used to add a condition or filter records

L.Anuhas Nethmina DDD 00125406

 2.3.3. Update Statement
 It is used to modify the records which are already added to a table

Before update

After Update

L.Anuhas Nethmina DDD 00125406

3.

3.1. Feedback form

L.Anuhas Nethmina DDD 00125406

Feedbacks

L.Anuhas Nethmina DDD 00125406

Test Case 001
Test Name Login
Actions Insert Username and password
Pre-Def Function Register
Post-Def Search Details
Function
Expected Output Access Database
Actual Output Access Database
Tester Name Anuhas
Tested Date 2022/9/20

3.2. Test cases

Test Case 002
Test Name Login
Actions Inserting Data into the table
Pre-Def Function Login
Post-Def Function Search Details, update details, delete records
Expected Output Insert data into the database

Actual Output Insert data into the database

Tester Name Anuhas

Tested Date 2022/9/20

L.Anuhas Nethmina DDD 00125406

Test Case 003
Test Name Update
Actions Update data in the table
Pre-Def Function Insert data
Post-Def Delete data
Function
Expected Output Update data in the database

Actual Output Update data in the database

Tester Name Anuhas
Tested Daate 2022/9/20

L.Anuhas Nethmina DDD 00125406

Test Case 004
Test Name Delete
Actions Delete data in the table
Pre-Def Function Insert data, update data
Post-Def Search Details, update details
Function
Expected Output Delete records from the database
Actual Output Delete records from the database
Tester Name Anuhas
Tested Daate 2022/9/20

L.Anuhas Nethmina DDD 00125406

Test Case 005
Test Name View
Actions view data in the table
Pre-Def Insert data, update data, delete
Functions
Post Def Search Details, update details, delete
Functions
Expected Output View records from the database
Actual Output View records from the database
Tester Name Anuhas
Tested Date 2022/9/20

4.

4.1. System introduction

The poly pipe system is a data management system that manages all the details in the poly
pipe company

L.Anuhas Nethmina DDD 00125406

 Following are the records that manage in the poly pipe system
 Customer records
 Staff details
 Installation details
 Facility details
 Equipment details

Insert, Update, Delete, and View are the main functions of that system

4.2. Usecase Diagram

4.3. Class
diagram

L.Anuhas Nethmina DDD 00125406

L.Anuhas Nethmina DDD 00125406
 4.4. Activity diagram

4.5. User manual

L.Anuhas Nethmina DDD 00125406

This is the login form for the poly pipe system. First, you need to provide user name and
password and log in

After that you can see forms like following, you need to fill that forms





After filling them you can add data to the database using the insert button
 If you want to update data, you can update data using the update button
 If you want to delete data you can delete it by using the delete button
 If you want to view records you can view them by view button

Suggestions for the system

L.Anuhas Nethmina DDD 00125406

  We can develop this system by applying online payment system and notifications
service.
 And we can dverlop GUI

Bibliography
satoricyber.com/dml-data-manipulation-language. (2022). Retrieved from
https://satoricyber.com: https://satoricyber.com/glossary/dml-data-manipulation-
language/
what-is-normalization. (n.d.). Retrieved from https://database.guide:
https://database.guide/what-is-normalization/

L.Anuhas Nethmina DDD 00125406