Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title HND IN COMPUTING

Ms. Dulashi Athauda

Assessor Internal Verifier
Unit 04: Database Design & Development
Unit(s)
Data base system for the Smart Movers Transport Company
Assignment title
J.M.G.M JAYAMAHA
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 Y/N
improved 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
Programme Leader
signature (if required) Date
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID J.M.G.M JAYAMAHA GAM/A 015254

Unit 04: Database Design & Development

Unit Title
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 M3 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 signature Date

Student signature Date

Pearson Higher Nationals in

Computing
Unit 04: Database Design & Development
Assignment 01
General Guidelines

1. A cover page or title page should be attached to your assignment. Use page 1 of this
assignment brief as your cover page and make sure all details are accurately filled.
2. The entire assignment brief should be attached as the first section of your assignment.
3. The assignment should be prepared using a word processing software.
4. The assignment should be printed single sided in an A4 sized paper.
5. Allow 1” margin on top, bottom and right sides of the paper and 1.25” on the left side (for
binding).

Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Set line spacing to 1.5. Justify all paragraphs.
3. Ensure that all headings are consistent in terms of size and font style.
4. Use footer function on the word processor to insert your name, unit, assignment no, and
page number on each page. This is useful if individual sheets get detached from the
submission.
5. Use the spell check and grammar check function of the word processing application to
review the use of language on your assignment.
Important Points:

1. Carefully check carefully the hand in date and the instructions given with the assignment.
Late submissions will not be accepted.
2. Ensure that sufficient time is spent to complete the assignment by the due date.
3. Do not wait till the last minute to print or bind the assignment. Such excuses will not be
accepted for late submissions.
4. You must be responsible for efficient management of your time.
5. 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.
6. Failure to achieve at least a PASS grade will result in a REFERRAL grade.
7. Non-submission of work without valid reasons will lead to an automatic REFERRAL. You will
then be asked to complete an alternative assignment.
8. If you use other people’s work or ideas in your assignment, it must be properly referenced,
using the HARVARD referencing system, in your text or any bibliography. Otherwise, you’ll
be found guilty of committing plagiarism.
9. If you are caught plagiarising, your grade will be reduced to a REFERRAL or at worst, you
could be excluded 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 Edexcel 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: 01/07/2020

(Provide E-mail ID) (Provide Submission Date)
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number J.M.G.M Jayamaha GAM/A 015254
Unit Number and Title Unit 4: Database Design & Development

Academic Year 2020/21

Unit Tutor Ms. Dulashi Athauda
Assignment Title Data base system for the Smart Movers Transport
Company

Issue Date

Submission Date

IV Name & Date

Submission format

Part 1: The submission is in the form of an individual written report. This should be 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 the Harvard referencing system. Please also
provide a bibliography using the Harvard referencing system. The recommended word
limit is 2,000–2,500 words, although you will not be penalised for exceeding the total word
limit.
Part 2: The submission is 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 is 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:
*Please note that assignment guidance is for reference only and should be more
specific in detail to meet customized needs.
Assignment brief
Case study
You are employed as a Database Developer for a large IT development company.
The company has been approached by a transport company called Smart
Movers which has grown to a level where need to have an automated system to
handle day today operational activities to meet customer demands. You are
given the job to design and develop a database solution for Smart Movers to
meet their business requirements.
The company transports chemical products from one location to another on
behalf of registered customers. Customers are of three types namely Catogory1,
2 and 3. Each customer is given a unique customer number and his or her details
have to be recorded in the system.
Each transport operation is called a job, which involves picking up one or more
loads of the products from a customer requested start location and delivers it to
a customer requested destination. A unique number is given for each job and for
each load when they are created.
A Load is transported using a particular transport unit, which consists of a lorry,
a driver, assistant, and a container (for carrying the product) A container is fixed
to a trailer so it needs to be coupled to a lorry at the start of a Job. (Single
container can transport only one chemical product due to safety requirements)
Payments for a job depends on customer type, product type (No Risk, High risk)
and the load type (small, medium and large). Transport operations are run from
9 regional depots. Jobs are allocated to individual depots to service. Depots
hold, manage and maintain their own transport units which are permanently
allocated to them to service Jobs. Normally transport units are held at the base
Depot they belong.
The final system should be able to provide the required information for
management decision making and to handle daily operations efficiently and
effectively.
Activity 1

1) Design and produce a comprehensive database design document for the above
scenario and it should cover the below mentioned points.

• User and system requirements

• Complete normalized (up to 3rd normal form) ER Diagram
• Complete Logical database design.
• Validations that used to validate data in the tables
• Simple interfaces to input and output data to the tables
• Critical evaluation and access the effectiveness of the user and system
requirements with the database design

Activity 2

2) Develop a comprehensive database system based on the database design

document which is provided under Activity 1

• Implement the database according to the provided ER diagram and use DDL
statements.
• Implement a GUI based system to view, insert, update, delete data in the tables.
• Implement validation methods explained in the Activity 1.
• Implement join queries display the details payment with the job details and the
customer details
• Implement and access DML (select, update, delete) by giving meaningful
examples
from the developed database
• Explain and implement the security mechanisms in the developed database (EX:
- User groups, access permissions).
• Explain and implement the below mentioned SQL statements from the
developed
database by giving meaningful examples.
• (Group by, Order by, Having, Between, Where)

Activity 3

3) Test the developed database system which has created in the Activity 2.
• Create a test plan to test the system against user and system requirements.
• Create test cases to test the developed database.
• Explain and access how the selected test data can be used improve the
effectiveness of testing.
• Get independent feedback and evaluate the effectiveness on the developed
database solution from the non-technical users and some developers.

Activity 4

4) Produce a technical documentation for the developed database system that

contains a user guide, UML diagrams (Use case diagram, class diagram, flow
charts, DFD level 0 and 1) and evaluate the database suggesting future
enhancements to be
implemented to ensure continuous effectiveness of the system
Grading Criteria Achie Feedback
ved

LO1 Use an appropriate

design tool to design a
relational database system
for a substantial problem

P1 Design a relational
database system using
appropriate design tools and
techniques, containing at
least four interrelated tables,
with clear statements of user
and system requirements.
M1 Produce a comprehensive
design for a fully functional
system that includes interface
and output designs, data
validations and data
normalization.

D1 Assess 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 Assess any future

improvements that may be
required to ensure the
continued effectiveness of
the database system.
Acknowledgement

In preparation for the Database Assignment of the first semester, I would like to thank our
lecturer Miss Dulashi Athauda who was very helpful for us to complete this task in time. In
addition, I would like to thank all my friends and family members who helped me
accomplish this target in no time. I gained a vast knowledge about database development
through this module and through the online tutorials from the internet. I am very grateful to
have this assignment done in time and I thank our lecturer; Miss Dulashi immensely and
ESOFT Metro Campus for laying out a good online educational platform to study even
during these pandemic times.
Acknowledgement..............................................................................................................................17
Activity 1.............................................................................................................................................20
Definition of a Database..................................................................................................................20
User and System Requirements......................................................................................................22
User Requirements.....................................................................................................................22
System Requirements.................................................................................................................24
ER Diagram and Data normalization................................................................................................26
Complete Normalized ER Diagram..............................................................................................26
Data Normalization.....................................................................................................................27
Primary Key.................................................................................................................................31
Cardinality...................................................................................................................................31
Relationship................................................................................................................................31
Entity Relationship Diagram (ERD) of the Smart Movers above:.................................................32
Customer_ ID..............................................................................................................................32
Product _ID.................................................................................................................................32
Load _ID......................................................................................................................................32
Payment_ ID................................................................................................................................32
Validations that used to validate data in the tables........................................................................33
Domain integrity.........................................................................................................................33
Entity integrity.............................................................................................................................34
Referential integrity....................................................................................................................34
Simple interfaces to input and output data to the tables...............................................................35
Critical evaluation and access the effectiveness of the user and system requirements with the
database design..............................................................................................................................36
Activity 2.............................................................................................................................................37
Implement the database according to the provided ER diagram and use DDL...............................37
Statements......................................................................................................................................37
2.2 Implement a GUI based system to view,insert,update,delete data in the tables......................39
Implement validation methods explained in the Activity 1.............................................................41
Data Validation............................................................................................................................41
Implement join queries display the details payment with the job details and the customer details.
........................................................................................................................................................43
 SQL Join.........................................................................................43
2.5 Implement and access DML
(select,update,delete) by giving meaningful examples from the developed database...................44
Data Manipulation Language (DML)............................................................................................44
2.6 Explain and implement the security mechanisms in the developed database (EX: - User groups,
access permissions).........................................................................................................................48
Security Mechanism Used In a Database....................................................................................48
Importance of these security Mechanisms.................................................................................49
Explain and implement the below mentioned SQL statements from the developed database by
giving meaningful examples. (Group by,Order by,Having,Between,Where)...................................51
Group by Statement....................................................................................................................51
Order by Statement....................................................................................................................51
Having Statement........................................................................................................................52
Between Statement....................................................................................................................52
Where Statement........................................................................................................................53
Implement the Above mentioned SQL statements from the developed database by giving
meaningful examples..................................................................................................................53
Activity 3.............................................................................................................................................55
3.1/2Create a test plan to test the system against user and system requirements........................55
Test Cases....................................................................................................................................55
Test Plan for Smart Movers.........................................................................................................56
3.3 Explain and access how the selected test data can be used improve the effectiveness of
testing.............................................................................................................................................57
Effectiveness of the Testing Explanation.....................................................................................57
3.4 Get independent feedback and evaluate the effectiveness on the developed database solution
from the non-technical users and some developers.......................................................................58
Effectiveness of the Database Solution.......................................................................................59
Activity 4.............................................................................................................................................61
4) Produce a technical documentation for the developed database system that contains a user
guide, UML diagrams (Use case diagram, class diagram, flow charts, DFD level 0 and 1) and
evaluate the database suggesting future enhancements to be implemented to ensure continuous
effectiveness of the system.............................................................................................................61
Future Improvements.................................................................................................................68
Activity 1

Definition of a Database

“A database is an organized collection of structured information, or data, typically stored

electronically in a computer system. A database is usually controlled by a database
management system (DBMS). Together, the data and the DBMS, along with the applications
that are associated with them, are referred to as a database system, often shortened to just
database.

Data within the most common types of databases in operation today is typically modeled in
rows and columns in a series of tables to make processing and data querying efficient. The
data can then be easily accessed, managed, modified, updated, controlled, and organized.
Most databases use structured query language (SQL) for writing and querying data.”

(Anon., 2020)

At the present day, we use various kinds of programs and tools to create databases such as,

 MY SQL

 Microsoft SQL Server

 Oracle RDBMS

 Improvado

 Knack

 MS Access
Features of a Good Database

 Minimal Data Redundancy – Integrated data into a single, logical structure where
duplicated data is minimum as possible.

 Data Consistency – Data is consistent throughout the whole database such that a
single update could easily update the total database.

 Data Shareable – Database is created to share the data and information among users
who have different levels of authorized access.
 Data Independence – No dependency among the data in the database.

 High data security – Different levels of access for the users as a guest, administrator
for updating and protecting the data.

Advantages of a Database

 High data security

 Higher data integrity

 Data consistency

Disadvantages of a Database

 Complexity and size

 Cost of DBMS and additional hardware costs

 Performance issues and problems

 High impact of a failure

Components of a Database System

1. Hardware

2. Software

a) General-purpose database management software

b) Application Software

3. People

a) Users

b) Practitioners

4. Data

User and System Requirements

User Requirements

User requirement is the requirement of the user when using the database system. User
requirement is a document, which is used in projects that tells us about the expected outcome
of the user while using the software. User requirement can be the user document or the user
manual, which is mainly, documented targeting the customers.

Documentation for Users

All programs or collections of programs comprising a composite system should have a
manual. This document follows more or less the same path as that of the operating instruction
except that the user will not normally be as concerned with the equipment technicalities as
will the operator.
The user’s manual should cover:

I. Detailed description of the function performed by the program;

II. The means by which the user supplies data to the program to be processed, covering
format and the content of the data together with any restrictions on values included,
and so on (Anon., 2020)

User Requirements for Smart Movers Company

 The accountable manager should be able to create a new job according to the specific
criteria like product type, customer type and the load type relating to the customer’s
satisfaction within a few seconds.

 The software; the DBMS created for the Smart Movers should store all the details as
per each customer enrolled for their specific jobs.

 The front desk officer should be able to register new customers easily and handle all
the transactions details and payment details easily without any delaying the customers
so that we can provide a good service to our customers.

 There should not be any major hidden bugs and errors in the system as per the
agreement.
 A proper training should be provided to the IT team of Smart Movers as per the
agreement.
System Requirements

System requirements are all of the requirements at the system level that describe the

functions which the system as a whole should fulfill to satisfy the stakeholder needs and
requirements, and are expressed in an appropriate combination of textual statements, views,
and non-functional requirements; the latter expressing the levels of safety, security,
reliability, etc., that will be necessary. (Alan Faisandier, 2020)

System Requirements for Smart Movers Company

System requirement is a document that describes the features and the functions of the system,
which is designed for Smart Movers.

Classification of System Requirements

Several classifications of system requirements are possible, depending on the requirements
definition methods and/or the architecture and design methods being applied. System
requirement is being divided into two parts,

a) Functional Requirement- Features and characteristics of the system

 Single container can transport only one chemical product due to safety requirements

 A Load is transported using a particular transport unit, which consists of a lorry, a

driver, assistant, and a container

 Customers are of three types namely Catogory1, 2 and 3, each customer is given a
unique customer number and his or her details have to be recorded in the system
 Payments for a job depends on customer type, product type (No Risk, High risk) and
the load type (small, medium and large)

 Transport operations are run from 9 regional depots

 Jobs are allocated to individual depots to service. Depots hold, manage and maintain
their own transport units which are permanently allocated to them to service Jobs

 The final system should be able to provide the required information for management
decision making and to handle daily operations efficiently and effectively

b) Non- Functional Requirement- Specifies the quality attribute of a software system.

 Security-The software should have a very high security in terms of data

security, secure against external hacking and cyber attacks

 Scalability-Accuracy of data input to the system and accuracy of payment

details

 Data integrity- Data has to be consistent throughout the system that via a
single update we can completely

 Reliability

 Maintainability

 Usability
Conceptual Design
An entity relational model or conceptual model, also called an entity-relational (ER) diagram
is a design representation of entities and their relationships to each other, ER model is used to
create relational database. In addition, they show how the different parts of a data model link
to each other.

ER Diagram and Data normalization

Complete Normalized ER Diagram

Data Normalization

Database normalization is a process used to organize a database into tables and columns.
Data Normalization should meet two basic requirements:

1. There is no redundancy of data (all data is stored in only one place, there should not be
duplicates available in the database anymore)

2. Data dependencies are logical (all the related data items in the database are stored
together)

Data Normalization is important because of many reasons, since there is no redundancy of

data the processes such as updating, deleting, insertion of new data to the table can be done
very easily.
 Structured database

No Anomalies No redundancy

Insertion Consistency of Data

Updating

Deleting

There are three main types of normalization.

1NF
2NF
3NF
BCNF
Partial dependency:

Non-key attribute is functionally depends on just a part of the key attribute. To achieve 2NF
the partial dependency of the table has to be removed.

Transitive dependency:

Non-key attribute is functionally depending on another non-key attribute.

Full dependency:

Non-key attribute depends on the whole primary key.

First Normal Form (1NF)

A relation is in 1NF, if it does not contain repeating groups or multivalued attributes. This
can be achieved by making every tuple/row unique.

E.g.: - 1st NF Customer (CusNo, Name, JobID, JobTitle)

(PaymentID, Name, Age, Cusno*)

We have to remove multivalued attribute or repeating groups when coming from zero
normalization form into first Normalization form.

This can be separate in to two ways.

By separating table into two tables

By filling the empty cells with the relevant data

Second Normalization Form (2NF)
Second Normal Form (2NF) is based on the concept of full functional dependency. Second
Normal Form applies to relations with composite keys, that is, relations with a primary key
composed of two or more attributes. A relation with a single-attribute primary key is
automatically in at least 2NF. A relation that is not in 2NF may suffer from the update
anomalies. (Upadhyay, 2019)

E.g.: - 2nd NF Customer (CusNo, Name, JobID, JobtTitle)

Job (JobID, JobName)

Third Normalization Form (3NF)

A relation is in third normal form, if there is no transitive dependency for non-prime
attributes as well as it is in second normal form. (Upadhyay, 2019)

Primary Key
A Primary Key is helps to uniquely identify the each row or record in Database. Primary Key
is contain the unique value. The Primary Key cannot have NULL values. Always one table
have only one Primary Key.

Cardinality
Cardinality is the context of database and this is refer to the singularity of the data values
contained in a column. The large columns contains percentage is totally unique value and it
means the column contains large. Low cardinality means that the column has lot of repeat in
data range.
Relationship
Database relationship is the context of database and it is exists between two relational
database table. The one table has a foreign key that is reference the primary key of the other
table. Relationship allows to the relational database to split and store the data in different
tables. An entity set is a collection of same entity, these entities are have attribute that is
define properties by major entities, attributes and viewing the relationship between tables.

Entity Relationship Diagram (ERD) of the Smart Movers above:

Customer Job
Customer ID Job ID
Customer ID Transport _Unit ID
Mobile Number Deport ID
DOB Job ID
Customer Name Pickup _Location ID
Address Product _ID
Customer type Customer ID

Payment
Depot Payment Id
Depot ID Customer_ ID
Transport_ Unit ID Product _ID
Deport ID Load _ID
Name Payment_ ID
Address
 Tel No
Product Location
Product ID
Load ID
Price
Quantity
No Risk Transport Unit
High Risk
Risk ID Transport ID
Transport Name
Depot ID
Load ID
Load

Load ID
Load ID
Pro _ID
Transport
Start Location

Validations that used to validate data in the tables

Data validation means checking the accuracy and quality of source data before using,
importing or processing the data. Different types of validation techniques can be performed
depending on objectives. Data validation is also known as Input Validation.

The relational data model/conceptual model includes several types of constraints. The major
types of integrity constraints used are:

 Domain integrity

 Entity integrity

 Referential integrity
Domain integrity

Domain integrity specifies that the columns in a relational database have to be declared upon
a defined domain. All of the values that appears in a column must be taken from the same
domain. A domain is a finite valid set of values that may be assigned to an attribute.

Domain integrity can be maintained by the use of:

 User defined domain types
 Not null
 Unique
 Default value
 Check clause

Entity integrity

The entity integrity technique is designed to assure that every relation has a Primary key. The
entity integrity assures that the primary key is not null and the values for the primary key are
valid all the time.

Referential integrity

A referential integrity constraint is a rule that maintains consistency among the rows of two
relations. In the relational data model, associations between tables are defined with foreign
keys. The rule is that if there is a foreign key in one relation, either each foreign key must
match a primary key value in referred relation or the foreign key value must be null.

Referential Integrity Rule in DBMS is based on Primary and Foreign Key. The Rule defines
that a foreign key have a matching primary key. Reference from a table to another table
 should be valid. To allow join, the
referential integrity rule states that the Primary Key and Foreign Key
have same data types. (Meador, 2018).

Simple interfaces to input and output data to the tables

A User Login Interface

 Critical evaluation and access the effectiveness of the user and system requirements
with the database design

Database quality depends greatly on the accuracy of the need specification and therefore the
greatest effort should specialize in improving the first stages of the database life cycle.
Conceptual data models form the idea of all later design work and determine what
information are often represented by a database. Therefore, its quality features a significant
impact on the standard of the database, which ultimately implemented. Ultimately, the user
requirements and the system requirements have to be fulfilled in the final database design
such that the database design is aligned with the technical requirements asked by the Smart
Movers Company.
Activity 2

Implement the database according to the provided ER diagram and use DDL
Statements

Definition for Data Definition language (DDL)

DDL in SQL

Data definition Language (DDL) is a standard for commands that define the different
structures in a database. DDL statements create, modify, and remove database objects such as
tables, indexes and users. Common DDL statement are CREATE, ALTER, AND DROP
(Rouse, 2019).

According to the scenario, smart movers there are seven types of table should be added in the
designed database. These tables can be created in SQL DDL statement in MS SQL

 Customer
 Transport Unit
 Payment
 Load
 Products
 Job
 Depot
2.2 Implement a GUI based system to view,insert,update,delete data in the tables.
 Implement validation methods explained in the Activity 1.

Data Validation.

Data validation means checking the accuracy and quality of source data before using,
importing or processing the data. Different types of validation techniques can be performed
depending on objectives. Data validation is also known as Input Validation.

Data validation is an essential part of any data handling task whether you’re in the field
collecting information, analyzing data, or preparing to present your data to stakeholders. If
your data isn’t accurate from the start, your results definitely won’t be accurate either. That’s
why it’s necessary to verify and validate your data before it is used.

While data validation is a critical step in any data workflow, it’s often skipped over. It may
seem as if data validation is a step that slows down your pace of work, however, it is
essential because it will help you create the best results possible. These days data validation
can be a much quicker process than you might’ve thought. With data integration platforms
that can incorporate and automate validation processes, validation can be treated as an
essential ingredient to your workflow rather than an additional step (Anon., 2021)
Validation
Method of Data Validation Examples
type

The last one or two digits in a code are

Check digit used to check the other digits are Bar code readers in supermarkets use check digits
correct

Format A National Insurance number is in the form LL 99

Checks the data is in the right format
check 99 99 L where L is any letter and 9 is any number

Checks the data isn't too short or too

Length check A password which needs to be six letters long
long

Lookup table Looks up acceptable values in a table There are only seven possible days of the week

Presence Checks that data has been entered into

In most databases a key field cannot be left blank
check a field

Checks that a value falls within the Number of hours worked must be less than 50
Range check
specified range and more than 0

Spell check Looks up words in a dictionary When word processing

 Implement join queries display the details payment with the job details and the
customer details.

SQL Join

A SQL Join statement is used to combine data or rows from two or more tables based on a
common field between them.

Join Query can be divided into 4 types:

 Inner Join- The inner join selects all rows from both the tables as long as the
condition satisfies.

 Left Join- This join returns all the rows of the table on the left side of the join . Left
join is also known as left outer join.

 Right Join- Right Join is similar to Left Join. This join returns all the rows of the table
on the right side of the join. Right Join is also known as Right outer Join.

 Full outer Join- Full Join creates the result-set by combining result of both left and
right joins. The result-set will be a combination of both the tables.

 
 2.5 Implement and access DML (select,update,delete) by giving meaningful
examples from the developed database.

Data Manipulation Language (DML)

DML statements are SQL statements that manipulate data. DML stands for Data
Manipulation Language. The SQL statements that are in the DML class are INSERT,
UPDATE and DELETE. Some people also lump the SELECT statement in the DML
classification (Rouse, 2006).
The data manipulation language is that the programing language when using data inserting,
deleting, and modifying in database. DML is use as a sublanguage in mainly database
language like SQL operating language.

The different DML statements are:

 Select

 Insert

 Update

 Delete

SELECT – The select query is employed to pick the database. This Selected command
commonly utilized in SQL. This enables users to database the extract information for an
operation or retrieve information from specified columns or from all of the columns in the table.

Syntax:

SELECT `Customer_id`, `Customer_name`, `Customer_address`, `DOB`, `Mobile no`,

`Customer_type` FROM `customers` WHERE 1
INSERT- this is often wont to INSERT new data to the database this statement is employed
as an INSERT INTO. There are two ways within the data insert.

Syntax:
INSERT INTO TABLE_NAME
[(col1, col2, col3,...colN)]
VALUES (value1, value2, value3,...valueN);
col1, col2,...colN

UPDATE – The UPDATE statement in SQL is used to update the data of an existing table in
database. We can update single columns as well as multiple columns using UPDATE
statement as per our requirement
Syntax:

UPDATE table_name

SET column1=value, column2=value2,...

WHERE some_column=some_value

DELETE – this is often wont to delete the info into the database. We will use the WHERE
clause with the Delete query. This question deletes the chosen rows because otherwise all
records are deleted into the database.

Syntax:

DELETE FROM table_name [WHERE condition];

 2.6 Explain and implement the security mechanisms in the developed database (EX:
- User groups, access permissions).

Security Mechanism Used In a Database

Database security is protection of an invaluable organizational resource against unauthorized

reading, changing or erasing of data. In a database, there should be more security because all
the important data are stored in the system so it should be more secured and the third party or
some hackers should not be able to take the stored data from the database. If there is no
proper security mechanism, it might affect the future of companies.

Database security must do strictly. This is often to stay the entire info safe within the
database. There is a regulation in database demand the quality from any business with online
components.
The database security is analysis implemented includes with:

 Restrict unauthorized access in use by implementing strong access and data internal
control.

 The testing capacity of a database makes sure it does not crash with the service attack
in user overload.

 Physical security of database servers and backups equipment’s.

 Review the system for any known or unknown awareness a mapping or decide to
reduce them.

Importance of these security Mechanisms

Database security is important to any organization because of the value of data in the
database.

 The database security helps to dam the firewall attacks, prevent malware viral, data
corruption, and every one sort of data spread in end-point devices.

 This prevents data loss through the corruption file or programming errors within the
system.

 Make sure that any quite damage can prevent the loss of knowledge on the server.
 Restrict data loss through the corruption of programmed errors.

 Company’s block attacks, including ransom ware and breached firewalls, which
keeps sensitive information’s safe.
 Explain and implement the below mentioned SQL statements from the developed
database by giving meaningful examples. (Group by,Order
by,Having,Between,Where)

Group by Statement

Group by is one of the most frequently used SQL clauses. It allows you to collapse a field
into its distinct values. This clause is most often used with aggregations to show one value
per grouped field or combination of fields.

SELECT column_name(s)

FROM table_name

WHERE condition

GROUP BY column_name(s)

ORDER BY column_name(s);

Order by Statement

The ORDER BY statement in sql is used to sort the fetched data in either ascending or
descending according to one or more columns. Order the result set of a query by the specified
column list and, optionally, limit the rows returned to a specified range.

SELECT column1, column2,

FROM table_ name

ORDER BY column1, column2, ASC|DESC;

Having Statement

The HAVING clause was added to SQL because the WHERE keyword could not be used
with aggregate functions.

SELECT column_name(s)

FROM table_name

WHERE condition

GROUP BY column_name(s)

HAVING condition

ORDER BY column_name(s);

Between Statement

The SQL BETWEEN condition allows you to easily test if an expression is within a range of
values (inclusive) .The BETWEEN operator selects values within a given range. The values
can be numbers, text, or dates. The BETWEEN operator is inclusive: begin and end values
are included.

SELECT column_name(s)

FROM table_name

WHERE column_name BETWEEN value1 AND value2;

Where Statement

The WHERE clause is used to filter records. The WHERE clause is used to extract only
those records that fulfill a specified condition.

SELECT column1, column2,

FROM table_name

WHERE condition;

Implement the Above mentioned SQL statements from the developed database by
giving meaningful examples.
Activity 3
3.1/2Create a test plan to test the system against user and system requirements.

Test Cases.

Component to Purpose of the Which test to Test data Expected

Use test use outcome

Insert data to Get the Insert data Name =Gihan Successfully

customer table information inserted
about the
customer
Test Plan for Smart Movers.

According to the smart mover’s database, a test plan document that outlines the planning for
test process. It contains guideline for the test process such as approach, testing tasks,
environment needs, resources requirement, schedule and constraints. And it describes the
scope of testing, testing technique to be used, resources required for testing and the schedule
of intended test activities. The scope helps identifying test items and the features to be tested.
A test plan also contain details of who will perform a given task.

INTRODUCTION- This test plan describes the testing approach and overall framework
which will drive the testing of the Smart Movers 1.0 – The document introduces:
Test Strategy: rules the test are going to be supported, including the givens of the project
(e.g.: start/end dates, objectives, assumptions); description of the method to line up a
legitimate test (e.g.: entry/exit criteria, creation of test cases, specific tasks to perform,
scheduling, data strategy).

Execution Strategy: describes how the test are going to be performed and process to spot and
report defects, and to repair and implement fixes.

Test Management: process to handle the logistics of the test and every one the events that
come up during execution (e.g.: communications, escalation procedures, risk, and mitigation,
team roster)

Overview of Project- Smart Movers is a powerful tool that allows corporate employees to
view relevant information such as payments and enter payment information without the
hassle of an Internet-enabled computer.

3.3 Explain and access how the selected test data can be used improve the
effectiveness of testing.

Effectiveness of the Testing Explanation.

Accurate and up-to-date data guarantee the success of a business. It prevents many
miscommunications and misleading decisions and situations. Therefore, SmartMovers needs
modifiable software and databases to regulate customer, transportation and payment details.
It provides the need to select test cases as described above to assess whether the database is
capable of providing return results. To be an effective database, it must be designed to be
simple to
 Maintain and store external knowledge. In
order to deal with customer information that is becoming obsolete,
there must be a process to systematically verify or update individual information. Therefore,
monitoring the database from time to time, it is very important to maintain it so far, and the
above tests have given me the opportunity to see the power of trying for it. Also, testing
allows you to check for flaws in the database, correct them, and prevent future use.
Information security is violated when more people access information. Therefore, enhancing
security is essential if data and access and access are restricted.

3.4 Get independent feedback and evaluate the effectiveness on the developed
database solution from the non-technical users and some developers.
80% of the respondents agreed that software offered useful feedback once they got wrong in
working with the software.

50% of the respondents agreed that software used scoring and from that 80% believes that it
is sensible and it encourages the learner.

65% of the respondents agreed that it's easy to navigate through the program and most of the
people 90% agreed that software is straightforward to start out and 80% said interface is
straightforward to know.

Only 40% of the respondents agreed that the icons won’t to assist navigation clear and
intelligible therefore it should be improved by reorganizing the icons during a more
understandable way.

Only a half the respondents agreed that it always clear to the learner which point s/he reached
within the program and thus users should be more informed and made conscious of what to
try to once they reach the assistance needed.

Effectiveness of the Database Solution.

To evaluate the effectiveness of the software feedback forms should be arranged as a

questionnaire to gather the small print from users to return into the suggestions to enhance
the software.

Feedback forms include the employee's name, department, and position, and are measured
according to the following principles: A questionnaire was distributed by 5 developers and 5
non-technical users, and feedback was distributed as follows.

 80% of the respondents agreed that software offered useful feedback once they got
wrong in working with the software.
 60% of the respondents agreed that it's easy to navigate through the program and
most of the people 90% agreed that software is straightforward to start out and 80%
said interface is straightforward to know.

 Only 40% of the respondents agreed that the icons won’t to assist navigation clear
and intelligible therefore it should be improved by reorganizing the icons during a
more understandable way.

 Only a half the respondents agreed that it always clear to the learner which point s/he
reached within the program and thus users should be more informed and made
conscious of what to try to once they reach the assistance needed.
Activity 4
4) Produce a technical documentation for the developed database system that
contains a user guide, UML diagrams (Use case diagram, class diagram, flow charts,
DFD level 0 and 1) and evaluate the database suggesting future enhancements to be
implemented to ensure continuous effectiveness of the system.

User’ guide and technical documentation for the support and maintenance of the software
User guide for the support and maintenance of the software by the fellow it staff.

Purpose of the system

The purpose of the system database that is to say it analyses the component of the system and
their inter-relationships, which enables us to understand the structure and behaviors of the
SmartMovers database system. And also to manage day to day transportation process of the
SmartMovers organization.

Simply to document the system and confirm that is has certain required features, such as a
security, privacy, system evidential sufficiency etc. To understand the system so that one can
design critical tests to confirm that the system functioning perfectly. A full system analysis
takes into account the whole system of SmartMovers database and includes looking at future
consideration.
Data Flow
 System features/functionalities

 One container must only transport one product at a time due to safety requirements

 Unique number must be given for each job and load when they are created

 Input the details of the customer dividing into their category 1,2 & 3

 Transport unit, assistant, lorry, driver and container details must be inputted into the
system

 Input customer type

Product type (lower, high, risk)

Load type (small, medium, large) to decided payments
 Input details about the transport operations from 9 regional depots

 Input the depots details to the depots table (E.g. DID, location, address)

 Input unique number to load and job when they created (E.g. loads and job tables)

Hardware and software requirements

Recommended Operating Systems

o Windows: 7 or newer
 o MAC: OS X v 10.7 or higher

o Linux: Ubuntu

o Processor: Minimum 2 GHz; Recommended 2GHz or more

o Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)

o Hard Drive: Minimum 128 GB; Recommended 256 GB or more

o Memory (RAM): Minimum 2 GB; Recommended 4 GB or above

o Some classes require a camera and microphone

Technical documentation for the support and maintenance of the software

System features/functionalities
Performance, security and user ability

 Security should be very high and effective

 Accuracy of payment and details

 System requirements and speed

 Reports should be created according to the system on time and should update all those
on time (e.g. customer details, transactions etc.)
Hardware and software requirements
Recommended Operating Systems

 Windows: 7 or newer

 MAC: OS X v10.7 or higher

 Linux: Ubuntu

Processor: Minimum 2 GHz; Recommended 4GHz or more

Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)

Hard Drive: Minimum 128 GB; Recommended 256 GB or more

Memory (RAM): Minimum 2 GB; Recommended 4 GB or above

Some classes require a camera and microphone

UML Diagrams
Use Case Diagram to Smart Movers Database System
Class Diagram for Smart Movers Database System
Future Improvements

The logistics management and transportation companies are finding the categories for
themselves by becoming reliable within the delivery of products and services. Especially the
smart movers are the products transport service. They need to deliver the foreseeable and
safe manner and offer transparency in their delivery process. They need to estimate the
impact of their transport vehicles, crew, and facilities available. Although Smart movers got
to improve their database system and software consistent with the changes in customers need
by their account convenience to raised customer relationship between business and therefore
the customer.
In predictive analytics are the sort used with data warehouse solution today to optimize the
vehicle routing, crew, and goods. Like directly fundamental to supply rock bottom possible
cost of transport to the customer, will maintaining limit? Smart movers must implement the
collect all the info of consumers to realize the advantage of cost-saving database and
software.
The vehicle divers risk analysis supported sensor or data will improve the security of the
drive and
Minimize warranty costs by avoiding potential cost recall. That’s the rationale Smart Movers
must adjust the software in risk analysis data facts.

References
Alan Faisandier, G. R. T. R. A. A. S., 2020. System Requirements. [Online]
Available at: sebokwiki.org/wiki/System_Requirements

Anon., 2020. Database Design And Development. s.l.:ESOFT METRO CAMPUS.

Anon., 2020. What is a Database?. [Online]

Available at: oracle.com/database/what-is-database/

Anon., 2021. What is Data Validation?. [Online]

Available at: https://www.safe.com/what-is/data-validation/

Meador, D., 2018. Referential Integrity Rule in RDBMS. [Online]

Available at: https://www.tutorialspoint.com/Referential-Integrity-Rule-in-RDBMS

Patrick, J. J., n.d. fandatabasemanagemendom. [Online]

Available at: https://t.fandatabasemanagemendom.com/wiki/Data_Validation

Upadhyay, M., 2019. Second Normal Form. [Online]

Available at: https://www.geeksforgeeks.org/second-normal-form-2nf/