STUDENT ASSESSMENT SUBMISSION AND DECLARATION

When submitting evidence for assessment, each student must sign a declaration confirming that
the work is their own.

Student name: Assessor name:

Jonathan Mottley

Issue date: Submission date: Submitted on:

Friday 20th December 2019 Thursday 9th April 2020 Thursday 9th April 2020

Programme:

BTEC HND in Computing and Systems Development

Unit: Unit4 – Database Design & Development

Assignment number and title: Assignment 1 Part 2 & 3

Plagiarism
Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs and students
who break the rules, however innocently, may be penalised. It is your responsibility to ensure
that you understand correct referencing practices. As a university level student, you are
expected to use appropriate references throughout and keep carefully detailed notes of all your
sources of materials for material you have used in your work, including any material
downloaded from the Internet. Please consult the relevant unit lecturer or your course tutor if
you need any further advice.

Student Declaration
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the
consequences of plagiarism. I understand that making a false declaration is a form of
malpractice.

Student signature: Date: 09/04/2020

Table of Contents
Introduction...................................................................................................................................4
Effectiveness of Testing & Choice of Test Data............................................................................6
User Document..............................................................................................................................7
Forms & Tables.............................................................................................................................9
Query Design, Queries & Reports...............................................................................................17
Technical Documentation............................................................................................................25
System Requirements – Hardware...............................................................................................25
System Requirements – Software................................................................................................25
Query Language..........................................................................................................................26
Security and Maintenance............................................................................................................26
References...................................................................................................................................28

Figure 1:Relational Diagram..................................................................................................................4

Figure 2: Company Table.......................................................................................................................5
Figure 3: Project Status Table................................................................................................................5
Figure 4: Main Database Lobby Page.....................................................................................................7
Figure 5: Add New Branch Form............................................................................................................9
Figure 6: Edit Branch Information Form................................................................................................9
Figure 7: Branch Table...........................................................................................................................9
Figure 8: Add New Client Form............................................................................................................10
Figure 9: Edit Client Information Form................................................................................................10
Figure 10: Client Table.........................................................................................................................10
Figure 11: Add New Country Form......................................................................................................11
Figure 12: Edit Country Information Table..........................................................................................11
Figure 13: Country Table.....................................................................................................................12
Figure 14: Add New Development Team Form....................................................................................13
Figure 15: Edit Development Team Form............................................................................................13
Figure 16: Development Team Table...................................................................................................13
Figure 17: Add New Employee Form...................................................................................................14
Figure 18: Edit Employee Information Form........................................................................................14
Figure 19: Employee Table..................................................................................................................14
Figure 20: Add New Project Form........................................................................................................15
Figure 21: Edit Project Information Form............................................................................................15
Figure 22: Project Table.......................................................................................................................15
Figure 23: New Project Type Form......................................................................................................16
Figure 24: Edit Project Type Form.......................................................................................................16
Figure 25: Project Type Table..............................................................................................................16
Figure 26: Branch to Client Design View..............................................................................................18
Figure 27: Branch to Client Query........................................................................................................18
Figure 28: Branch Report.....................................................................................................................18
Figure 29: Project Name & Type Design View Query...........................................................................19
Figure 30: Project Name &Type Query................................................................................................19
Figure 31: Project Name & Type Report..............................................................................................19
Figure 32: Project Design View Query.................................................................................................20
Figure 33: Project Query......................................................................................................................20
Figure 34: Project Report.....................................................................................................................20
Figure 35: Employee Design View Query.............................................................................................21
Figure 36: Employee Query.................................................................................................................21
Figure 37: Employee Report................................................................................................................21
Figure 38: Dev Team to Project Design View Query............................................................................22
Figure 39: Dev Team to Project Query.................................................................................................22
Figure 40: Dev Team to Project Report................................................................................................22
Figure 41: Country to Branch Design View Query................................................................................23
Figure 42: Country to Branch Query....................................................................................................23
Figure 43: Country to Branch Report...................................................................................................23
Figure 44: Client Design View Query...................................................................................................24
Figure 45: Client Query........................................................................................................................24
Figure 46: Client Report.......................................................................................................................24
Introduction

The ITConsultancy Company Database has been demoed on Thursday 9 th April 2020
at 6:30pm. It showed most of the features that would be associated with the use of the
database. The reason for this development is to meet the company’s requirement of being
able to fully monitor all their clients and their respected projects. With the implementation of
this database, it wouldn’t be limited to just monitoring projects and clients but also all aspects
of the company from development team straight to the branch and its respected countries.

From the initial planning of this database, it was stated that 8 tables would house all
the necessary data for this database. However, upon further planning it showed the need for a
nineth table. This being the project status table. This table consisted of all the phases of a
project. The image below represents a relational diagram that would depict the relationship
between each table for the database. The data types that are associated with this relational
diagram would be Integer, Varchar & Date. These data types were explained in Part 1 of the
previous document.

Figure 1:Relational Diagram

The information below would illustrate all the Tables, Forms, Queries in Design
View, Queries and Reports. In this database, as mentioned above it consists of 9 tables.
However, the two tables with the names Project Status Table and Company Table doesn’t
require a form to add information since they are fixed tables.
 In database, a table would be used to store all information that is inputted into fields
on a form which would then store the information accordingly to how the relationship
between all the tables are created.

A form is a G.U.I. that would be used to input information on tables. These forms can
be created through the use of a wizard or from a blank form. Each form can be personalised
to suit the requirements of the users.

Queries in Design View is when the developer would create a query that would be
unique to the user. What this means is that the data that would be gathered from the query
would be unique to the user based on their requirements.

Queries are the end product of the queries that are in design view. Which would then
give the user a view of the compiled data that they requested initially.

A Report is a formatted illustration of a query which contain personalised data which

can be used for decision-making.

Figure 2: Company Table

This table is created initially with the sole purpose of being the main linking table.
Information wouldn’t be written to it due to a form not being created to add information. This
table has 4 data types. These being 1 int and 3 var.

Figure 3: Project Status Table

This table was created to show the status of a project. Initially, it was left out and
upon further into the development, it was brought to the developers’ attention that a project
status table was required to link a status to a respected project. This table has 2 data types.
These being 1 int and 1 var.
Effectiveness of Testing & Choice of Test Data
A test report is documentation that would contain a summary of all test activities and the final
testing results and an assessment. The table below would illustrate what was done during the
testing phase.
Functions Descriptions
Add New Client Check for new Client Entry
Edit/ Delete Client Check if client info was edited
or deleted
Add New Project Check for new Project Entry
Edit/ Delete Project Check if Project info was
edited or deleted
Add New Branch Check for new Branch Entry
Edit/ Delete Branch Check if Branch info was
edited or deleted
Add New Country Check for new Country Entry
Edit/ Delete Country Check if Country info was
edited or deleted
Creating various The ability to create a query in
Queries design view
Generating Query Generating a report from a
Reports previous query that was
designed
Data Validation The ability to use a drop-down
menu as well as date
Referential Integrity The ability not have duplicate
entry
Pass/ Fail Test Data
Pass Added the new client Star Fox
to the database
Pass Edit the recently entered
client’s information
Pass Add the new project qwerty123
Pass Delete the recently added
project from the database
Pass Added a new branch call
Zimbabwe Br
Pass Edited the Branch Information
Pass Added a new country called
Zimbabwe
Pass Deleted the newly added
country record
Pass Create a query on all the
projects in the Implementation
Phase
Pass Generate the formatted report
on the query previously carried
out
Pass All forms that required pre-set
data in certain fields were
configured to suit
Pass The application of Unique to
the necessary fields in
PHPMyAdmin made sure there
wasn’t any duplicate entries on
the desired fields.
User Document

The image below illustrates the main user/ lobby page. What the user would be
greeted to would be a main screen with the date and time of the system that it’s currently
being used on as well as 7 tabs that would be connected to each respected table.

Figure 4: Main Database Lobby Page

The images below go in the following order from an Add Form, Edit Form and a Table that
would show how all information would link to each respected table. All steps on how to Add,
Edit & Delete a record are applicable to all the following forms.

 How to Add a New Record

Step 1: To add a new record of any sort, the user would firstly have to click on the desired
form tab on the main database lobby page.

Step 2: Click on the “Add” button to perform the adding process/

Step 3: Fill in all empty fields with the necessary information then click “save”

 How to Edit a Record

Step 1: To edit records information, the user would have to first click on the desired form tab
on the main database lobby page

Step 2: Click on the “Edit” button to perform the editing process

Step 3: Edit the necessary information on the desire fields and the click “save”

 How to Delete a Record

Step 1: Follow steps 1 & 2 on how to edit a record

Step 2: Select the desired record that you want to delete and the click the “delete” button.

Once these steps are performed properly, please look at the desired table and click the
“refresh all” button to ensure the changes that you have made were applied
Forms & Tables

Figure 5: Add New Branch Form

Figure 6: Edit Branch Information Form

Figure 7: Branch Table

Figure 8: Add New Client Form

Figure 9: Edit Client Information Form

Figure 10: Client Table

Figure 11: Add New Country Form

Figure 12: Edit Country Information Table

Figure 13: Country Table
Figure 14: Add New Development Team Form

Figure 15: Edit Development Team Form

Figure 16: Development Team Table

Figure 17: Add New Employee Form

Figure 18: Edit Employee Information Form

Figure 19: Employee Table

Figure 20: Add New Project Form

Figure 21: Edit Project Information Form

Figure 22: Project Table

Figure 23: New Project Type Form

Figure 24: Edit Project Type Form

Figure 25: Project Type Table

Query Design, Queries & Reports

The following images below shows Queries in Design View, Queries and Reports from the
generated queries. The following steps would illustrate how a user should create, generate a
query and create a Report.

 How to create a Query in Design View

Step 1: Click “create”

Step 2: Click “Query Design”

Step 3: Select desire tables for the query

Step 4: Click the dropdown menu on “field” & select the desire fields from the desire tables

Step 5 (Optional): Enter information for the query in the “criteria” area

Step 6: Save the query to desired name

Step 7: Click “Run” on the top left corner

 How to create a Query Report

Step 1: Click “Create”

Step 2: Highlight the desired query that was previous created from design view

Step 3: Click “Reports”

Step 4: Format report to user desire

Step 5: Save Report with desired name

Once the query is generated, if there are any special criteria inserted the user would click
“refresh all” while the query is open to get the most updated data from the query report.
Figure 26: Branch to Client Design View

Figure 27: Branch to Client Query

Figure 28: Branch Report

Figure 29: Project Name & Type Design View Query

Figure 30: Project Name &Type Query

Figure 31: Project Name & Type Report

Figure 32: Project Design View Query

Figure 33: Project Query

Figure 34: Project Report

Figure 35: Employee Design View Query

Figure 36: Employee Query

Figure 37: Employee Report

Figure 38: Dev Team to Project Design View Query

Figure 39: Dev Team to Project Query

Figure 40: Dev Team to Project Report

Figure 41: Country to Branch Design View Query

Figure 42: Country to Branch Query

Figure 43: Country to Branch Report

Figure 44: Client Design View Query

Figure 45: Client Query

Figure 46: Client Report

Technical Documentation
This type of documentation is used to help all groups to better explain the functionality, the
creation and the architecture of the respected product.

System Requirements – Hardware

The use of a Dell R340 PowerEdge Rack Server would be needed for this endeavour. The
specifications required for this server would be as follows: -

Processor – minimum (Intel i3 9100 processor up to 4 cores per processor)

RAM – Up to 64GBs memory

Memory Type – UDIMM

Memory Slots – 4

Power Supplies – 350W Platinum, 550W Platinum (Hot plug supplies with full redundancy
option)

Storage – up to 8 x 2.5” Hot Plug SATA(SSD), 4 x 3.5” Hot Plug SATA(SSD)

Network Options - 2 x 1GbE LOM

Front Ports - 1 x Dedicated iDRAC direct micro-USB, 1 x USB 2.0 

Rear Ports - 1 x Serial, 2 x USB 3.0, 1 x VGA 

Internal Ports - 1 x USB 3.0, Slots PCie, 2 x PCIe Gen3 slots

System Requirements – Software

As identified in the initial document the following software would need to be applied to the
server to properly function.

WAMP – Windows, Apache, MySQL and PHP is what it stands for. This software is used for
web development as well as database development. Once the software is installed, it uses a
web browser interface to connect to PHPMyAdmin. The version that would be used this
database would be 3.2.2.2 4bit.

Microsoft Access - is a management tool that would store data referencing, data analysis and
data reporting. A minimum of Microsoft Access 2016 should be used
SQL Server Studio Management – is used to manage analysis services objects such as
performing back-ups and processing objects.

MySQL Workbench – is the visual tool that database developers utilise. It provides data
modelling and comprehensive administrative tools. The version that would be used would be
8.0.18.

Query Language
SQL Query Language – is a database language that would be used to develop, maintain and
retrieve relational database. This language is case insensitive however, the practise of using
all capitals for key words such as CREATE, SELECT, UPDATE, etc should be implemented
throughout with the use of defined things such as table names, column names, etc. in
lowercase letters.

Security and Maintenance

With this database the use of database security and database maintenance were factors
to be considered. Database security is a crucial topic when it comes to database. It is basically
any type of security that would be used to protect the database from any potential
compromises.

During development it was already stated that there would be 3 methods of security which
would be used throughout.

 Software/ Hardware – various types of software and hardware would be utilised to

prevent malicious acts towards the database through the use of viruses or even
hacking.
 Physical – this would be the use of company personnel who would monitor and
control the database. With this method type, it would allow the user to identify any
potential compromises and/or weaknesses.
 User Accounts – with this method of security, features such as restriction of access
through the use of passwords would limit or even block users who aren’t supposed to
have access to the database.

Database Maintenance would only be catered to after the database is developed and
functional. Once the database is live the use of a software called SQL Server Management
Studio would be integrated into the database which would monitor and control 4 factors of
the database every 14 days. These factors would be: -

 Index Defragmentation – is where SQL Server Management Studio would defrag all
the indexes of the database and reorganise or rebuild an index or one partition. Once
this has been carried out, it would improve disk space and the performance of SQL
Server.
 Log File Maintenance – is where the database would keep a journal or record of all
activities that have been transpired on the database.
 File & Data Compaction – is the removal of redundant information from files or data.
 Integrity Checker – checks the single or multiple databases for the allocation as well
as the structural integrity of all objects.

These 4 factors can run independently or concurrent on the desire database.

References

2019. [online] Available at: <https://www.dell.com/en-

us/work/shop/povw/poweredge-r340/techspecs/techspecs> [Accessed 10 April
2020].
Docs.microsoft.com. 2019. SQL Server Management Studio (SSMS) - SQL Server
Management Studio (SSMS). [online] Available at:
<https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-
ssms?view=sql-server-ver15> [Accessed 10 April 2020].