Unit 04 Database-Assignment Holistic

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

INTERNAL VERIFICATION – ASSESSMENT DECISIONS
Programme title
Assessor Internal Verifier

Unit 04: Database Design & Development
Unit(s)
Data base system for the SmartMovers Transport Company
Assignment title
Student’s name
List which assessment criteria Pass Merit Distinction
the Assessor has awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded match

those shown in the assignment brief? Y/N
Is the Pass/Merit/Distinction grade awarded

justified by the assessor’s comments on the Y/N
student work?
Has the work been assessed
Y/N
accurately?
Is the feedback to the student:
Give details:
• Constructive? Y/N
• Linked to relevant assessment criteria? Y/N
• Identifying opportunities for Y/N
improved performance?
• Agreeing actions? Y/N
Does the assessment decision need
Y/N
amending?
Assessor signature Date
Internal Verifier signature Date

Programme Leader signature (if required)
Date
Confirm action completed

Remedial action taken
Give details:
Assessor signature Date
Internal Verifier
Date
signature
Programme Leader
Date
signature (if required)
Higher Nationals - Summative Assignment Feedback Form

Student Name/ID
Unit Title Unit 04: Database Design & Development
Assignment Number 1 Assessor

Date Received
Submission Date
1st submission
Date Received 2nd
Re-submission Date
submission
Assessor Feedback:
LO1 Use an appropriate design tool to design a relational database system for a substantial problem
Pass, Merit & Distinction P1 M1 D1
Descripts
LO2 Develop a fully functional relational database system, based on an existing system design
Pass, Merit & Distinction P2 P3 M3 M3 D2
Descripts
LO3 Test the system against user and system requirements.

Descripts
LO4 Produce technical and user documentation.

Descripts
Grade: Assessor Signature: Date:
Resubmission Feedback:
Grade: Assessor Signature: Date:
Internal Verifier’s Comments:
Signature & Date:
* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.
Assignment Feedback
Formative Feedback: Assessor to Student
Action Plan
Summative feedback
Feedback: Student to Assessor

Date
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.
Page 5 of 102
Ahammed Asjath Database Assessment Unit 03
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.
Page 6 of 102
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:

(Provide E-mail ID) (Provide Submission Date)
Page 7 of 102
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number
Unit Number and Title Unit 4: Database Design & Development
Academic Year 2017/18
Unit Tutor
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.
Page 8 of 102
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
SmartMovers 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
SmartMovers 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.
Page 9 of 102
The final system should be able to provide the required information for
management decision making and to handle daily operations efficiently and
effectively.
Activity 01
Activity 1.1
a. Identify the user and system requirements to design a database for the
above scenario.
b. Identify entities and attributes of the given scenario and design a
relational database system using conceptual design (ER Model) by
including identifiers (primary Key) of entities and cardinalities,
participations of relationships.
c. 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.
Note:-It is allowed to have your own assumptions and related attributes
within the scope of the case study given.
Activity 1.2
a. Explain data normalization with examples. Check whether the provided
logical design in task 1.1 is normalised. If not, normalize the database by
removing the anomalies.
b. Design set of simple interfaces to input and output for the above
scenario using Wireframe or any interface-designing tool.
c. Explain the validation mechanisms to validate data in the tables with
examples.
Activity 1.3
a. Check whether the given design (ERD and Logical design) is representing
the identified user and system requirements to access the effectiveness
of the design.
Page 10 of 102
Activity 2
Activity 2.1
Develop the database system with evidence of user interface, output and data
validations, and querying across multiple tables.
a. Develop a relational database system according to the ER diagram you
have created (Use SQL DDL statements).
b. Provide evidence of the use of a suitable IDE to create a simple interface
to insert, update and delete data in the database
c. Implement the validation methods explained in task 1.2-part c.
d. Display the details payment with the job details and the customer
details using Join queries
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.
Select
Update
Delete
Note: - The queries you have selected should be meaningful and relevant to
the given scenario.
Activity 2.3
a. Explain how security mechanisms have been used and the importance
of these mechanisms for the security of the database. Implement
proper security mechanisms (EX: -User groups, access permissions) in
the developed database.
Page 11 of 102
Activity 2.4
a. Explain the usage of the below SQL statements with the examples from
the developed database
Group by
Order by
Having
Between
Where
Activity 3
Activity 3.1
a. Provide a suitable test plan to test the system against user and system
requirements
b. Provide relevant test cases for the database you have implemented
Note:- Learner needs to give expected results in a tabular format and
screenshots of the actual results with the conclusion
Activity 3.2
a. Explain how the selected test data in task 3.1 b) can be used improve
the effectiveness of testing.
Activity 3.3
a. Get independent feedback on your database solution from the non-
technical users and some developers (use surveys, questioners,
interviews or any other feedback collecting method) and make
recommendations and suggestions for improvements in a separate
conclusion/recommendations section.
Page 12 of 102
Activity 4
Activity 4.1
a. Prepare a simple users’ guide and a technical documentation for the
support and maintenance of the software.
Activity 4.2
a. Your technical documentation should include some of the UML
diagrams (Use case diagram Class diagram, etc.), flow charts for the
important functionalities, context level DFD and the Level 1 DFD
Activity 4.3
a. Suggest the future improvements that may be required to ensure the
continued effectiveness of the database system.
Page 13 of 102
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 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
Page 14 of 102
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.
Page 15 of 102
Acknowledgement
Acknowledgement is not only a formal, so far additionally an obligation to every one of the
persons who have helped in the finishing procedure of the venture. One of the most wonderful
angles in meeting the important and critical data and assembling it is the chance to thank every
one of the persons who effectively add to it
First of all, I Would Thank our ESOFT Manager Mr. V. Niruban, Senior Lecturer of ESOFT
Metro Campus and Mr. Piragan ESOFT Metro Campus who gave the specialized way and
consistent management all the same his busy timetable
Finally, I would like to thank ESOFT Metro Campus and its decent showing board for giving
important information and help all through the HND Computing and Systems Improvement
program. I am additionally grateful to my family mostly to my parents, for supporting also,
promising me to finish this project effectively.
Page 16 of 102
Page 17 of 102
Page 18 of 102
Table of Contents
Acknowledgement ............................................................................................................................... 16
List of Figures...................................................................................................................................... 21
List of Tables ....................................................................................................................................... 23
Introduction ......................................................................................................................................... 24
Activity 01 ............................................................................................................................................ 25
Activity 1.1 ....................................................................................................................................... 25
A Requirement Analysis ............................................................................................................. 25
ER Diagram for Smart Movers ................................................................................................. 27
Logical Schema for Smart Movers ............................................................................................ 31
Activity 1.2 ....................................................................................................................................... 32
Data normalization ..................................................................................................................... 32
Purpose of the Data Normalization ........................................................................................... 32
Process of Normalization ............................................................................................................ 32
Design set of simple interfaces to input and output for the above scenario using Wireframe
or any interface-designing tool................................................................................................... 36
Explain the validation mechanisms to validate data in the tables with examples. ................ 43
Activity 1.3 ....................................................................................................................................... 45
Check whether the given design (ERD and Logical design) is representing the identified
user and system requirements to access the effectiveness of the design. ................................ 45
Activity 02 ............................................................................................................................................ 47
Activity 2.1 ....................................................................................................................................... 47
Develop a relational database system according to the ER diagram you have created (Use
SQL DDL statements)................................................................................................................. 47
Provide evidence of the use of a suitable IDE to create a simple interface to insert, update
and delete data in the database .................................................................................................. 53
Implement the validation methods explained in task 1.2-part c. ............................................ 60
Display the details payment with the job details and the customer details using Join queries
...................................................................................................................................................... 62
Activity 2.2 ....................................................................................................................................... 63
Explain the usage of DML with below mentioned queries by giving at least one single
example per each case from the developed database. .............................................................. 63
Activity 2.3 ....................................................................................................................................... 66
Explain how security mechanisms have been used and the importance of these mechanisms
for the security of the database. Implement proper security mechanisms (EX: -User groups,
access permissions) in the developed database. ........................................................................ 66
Activity 2.4 ....................................................................................................................................... 69
Page 19 of 102
Explain the usage of the below SQL statements with the examples from the developed
database ....................................................................................................................................... 69
Activity 03 ............................................................................................................................................ 72
Activity 3.1 ....................................................................................................................................... 72
Provide a suitable test plan to test the system against user and system requirements. ........ 72
Provide relevant test cases for the database you have implemented ...................................... 76
Activity 3.2 ....................................................................................................................................... 84
Explain how the selected test data in task 3.1 b) can be used improve the effectiveness of
testing. .......................................................................................................................................... 84
Activity 3.3 ....................................................................................................................................... 85
Get independent feedback on your database solution from the non-technical users and
some developers (use surveys, questioners, interviews or any other feedback collecting
method) and make recommendations and suggestions for improvements in a separate
conclusion/recommendations section. ....................................................................................... 85
Recommendations and suggestions for improvements in a separate conclusion /
recommendations section. .......................................................................................................... 87
Activity 04 ............................................................................................................................................ 88
Activity 4.1 ....................................................................................................................................... 88
Prepare a simple users’ guide and a technical documentation for the support and
maintenance of the software....................................................................................................... 88
Activity 4.2 ....................................................................................................................................... 95
Your technical documentation should include some of the UML diagrams (Use case
diagram Class diagram, etc.), flow charts for the important functionalities, context level
DFD and the Level 1 DFD. ......................................................................................................... 95
Activity 4.3 ....................................................................................................................................... 98
Suggest the future improvements that may be required to ensure the continued
effectiveness of the database system. ......................................................................................... 98
Self-Criticism ....................................................................................................................................... 99
Conclusion ......................................................................................................................................... 100
References .......................................................................................................................................... 101
Page 20 of 102
List of Figures
Figure 1 ER Diagram for Smart Movers .......................................................................................... 27
Figure 2 Logical Schema .................................................................................................................... 31
Figure 3 Process of Normalization .................................................................................................... 32
Figure 4 User Login ............................................................................................................................ 36
Figure 5 Main Menu ........................................................................................................................... 37
Figure 6 Customer Form .................................................................................................................... 37
Figure 7 Load Form ............................................................................................................................ 38
Figure 8 Product Form ....................................................................................................................... 38
Figure 9 Payment Form...................................................................................................................... 39
Figure 10 Job Form ............................................................................................................................ 39
Figure 11 Employee Form .................................................................................................................. 40
Figure 12 Employee Form .................................................................................................................. 40
Figure 13 Depot Form ........................................................................................................................ 41
Figure 14 Lorry Form ........................................................................................................................ 41
Figure 15 Container Form ................................................................................................................. 42
Figure 16 Trailer Form ...................................................................................................................... 42
Figure 17 Job Interface Design .......................................................................................................... 45
Figure 18 Product Interface ............................................................................................................... 46
Figure 19 Database on Databases ...................................................................................................... 52
Figure 20 Database Create query ...................................................................................................... 52
Figure 21 User Interface using Visual Studio IDE........................................................................... 55
Figure 22 Before Data Add on Data Table ....................................................................................... 56
Figure 23 Insert Function Interface .................................................................................................. 56
Figure 24 After Data Save on Data Table ......................................................................................... 57
Figure 25 Before Delete Data row on Data Table ............................................................................ 57
Figure 26 Want to Delete Data Row .................................................................................................. 58
Figure 27 Delete Data Interface ......................................................................................................... 58
Figure 28 Before Update Cus_Id=6 ................................................................................................... 59
Figure 29 After Data Update.............................................................................................................. 59
Figure 30 Data Has Been Changed.................................................................................................... 60
Figure 31 Range Validation Method Example ................................................................................. 60
Figure 32 Finding Data Validation error ......................................................................................... 61
Figure 33 Finding Field Validation ................................................................................................... 61
Figure 34 Select Query ....................................................................................................................... 64
Figure 35 Update Query ..................................................................................................................... 64
Figure 36 Delete Query ....................................................................................................................... 65
Figure 37 Login Interface Form ........................................................................................................ 67
Figure 38 Username Password gone Wrong..................................................................................... 68
Figure 39 Username and Password is Correct ................................................................................. 68
Figure 40 Group by Query ................................................................................................................. 69
Figure 41 Order by Query ................................................................................................................. 70
Figure 42 Having Query ..................................................................................................................... 70
Figure 43 Between Query ................................................................................................................... 71
Figure 44 Where Query ...................................................................................................................... 71
Figure 45 Test Plan for Smart Movers.............................................................................................. 72
Figure 46 Test Case No1 ..................................................................................................................... 76
Page 21 of 102
Figure 51 Test Case No 6 .................................................................................................................... 81
Figure 57 User Manual for Smart Mover ......................................................................................... 88
Figure 58 Instruction Login Page ...................................................................................................... 91
Figure 59 Username or Password gone Wrong ................................................................................ 91
Figure 60 Username and Password is Correct ................................................................................. 92
Figure 61 Main Menu for This System ............................................................................................. 93
Figure 62 Customer Form in This System ........................................................................................ 93
Figure 63 Software Hardware Requirements................................................................................... 95
Figure 64 Use Case Diagram .............................................................................................................. 96
Figure 65 Flow Chart.......................................................................................................................... 97
Page 22 of 102
List of Tables
Table 1 Smart Movers Software and Hardware Requirement ....................................................... 26
Table 2 Attributes ............................................................................................................................... 29
Table 3 Primary Key .......................................................................................................................... 29
Table 4 Foreign Key............................................................................................................................ 30
Table 5 1NF ......................................................................................................................................... 33
Table 6 Test Caste Template .............................................................................................................. 74
Table 7 Test Case Interface ............................................................................................................... 75
Table 8 Test Case No1 ........................................................................................................................ 76
Table 9 Test Case No 2 ....................................................................................................................... 77
Table 10 Test Case No 3 ..................................................................................................................... 78
Page 23 of 102
Introduction
The company has been advanced by a transport company called Smart Movers. 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. and also Product Type have 2 type it
“High Risk ” “Low Risk”.
And Myself I Decided To use Software for this Assignment Database System is Microsoft
SQL Server 2012 for Create Database and Visual Studio 2012 for Create Interfaces and
System.
I Have Some Knowledge about Database and Visual Studio So with Help of My Friends who
are Behind me and Lectures Who are support us to do this Assessment.
Page 24 of 102
Activity 01
Activity 1.1
A Requirement Analysis
This is where every software project starts. Requirements serve many purposes for a software
development project. For starters, requirements define what the software is supposed to do.
The software requirements serve as the basis for all the future design, coding, and testing that
will be done on the project. Typically, requirements start out as high-level general statements
about the software's functionality as perceived by the users of the software. Requirements are
further defined through performance, look and feel, and other criteria. Each top-level
requirement is assigned to one or more subsystems within an application. Subsystem-level
requirements are further refined and allocated to individual modules. As this process points
out, requirements definition is not just a process that takes place at the start of a development
project, but an ongoing process. This is especially true when a spiral development model is
used. The ability to manage the definition and tracking of requirements is a key process area
required of level 2 organizations by the SW-CMM. (Kern, 2001)
Smart Movers Provides Four Types Requirements

1. User Requirement
2. System Requirement
3. Software Requirement
4. Hardware Requirement
Smart Movers User Requirement

1. Customer records store in Database
2. Customer needs to Deliver Product, Delivery Details must be stored
3. Employee records Details
4. Transport Details
5. Payment Details
Smart Movers System Requirement

1. Customer reports (week, daily, month wise)
2. Customer must add in a job. Job have added products details, customer table, product
table and job table must in database
3. Transport unit are employees, every transport unit have driver, assistant, lorry,
container, trailer, so transport unit, employee, container, trailer tables must in database.
Page 25 of 102
Smart Movers Software and Hardware Requirement
Table 1 Smart Movers Software and Hardware Requirement
Software Requirement Hardware Requirement

MS SQL Server 2012 Hard Drive Disk(500 GB) and RAM(2GB)
Operating System: Windows 10 Printer(Canon)
Visual Studio 2012 Bar Code Reader
Drivers Keyboard & Mouse (Wireless)
Ice Cream PDF Reader Internet Router (Dialog)
Page 26 of 102
ER Diagram for Smart Movers
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is an object, a component of data. An entity set is a collection of similar
entities. These entities can have attributes that define its properties. By defining the entities,
their attributes, and showing the relationships between them, an ER diagram illustrates the
logical structure of databases. ER diagrams are used to sketch out the design of a database.
(Anon., 2019)
Figure 1 ER Diagram for Smart Movers
Page 27 of 102
Entity
An entity is any object in the system that we want to model and store Data about. Entities are
usually recognizable concepts, either concrete or abstract, such as person, places, things, or
events which have relevance to the database. Some specific examples of entities are Employee,
Student, Lecturer. An entity is analogous to a table in the relational model. (Anon., 2007)
Entity are Two Types
1. Strong Entity
2. Weak Entity
According to the ER Diagram:
• Customer
• Product
• Load
• Payment
• Job
• Employee
• Transport Unit
• Depot
• Lorry
• Container
• Trailer
Attributes
An attribute is an item of Data which is stored about an entity. For example, the entity 'lecturer'
could have attributes such as staff id, surname, forename, date of birth, telephone number, etc.
An attribute can only appear in one entity, unless it is the key attribute in another entity. In a
traditional filing system, an attribute equates to a field in a record. (Anon., 2007)
Types of Attributes
1. Simple Attributes: Simple attributes are atomic values, which cannot be divided
further.
2. Composite Attributes: Composite attributes are made of more than one simple
attribute.
3. Single-Value Attributes: Single-value attributes contain single value.
4. Multi-Value Attributes: Multi-value attributes may contain more than one values.
5. Derived Attributes: other attributes present in the database.
Page 28 of 102
According to the ER Diagram:
Table 2 Attributes
Entity Attributes
Customer Cus_ID,Cus_Name,Tel_No,Cus_Address,F_Name,L_Name
Product P_ID,P_Name,P_Type
Load L_ID,L_Type
Payment Py_ID,Py_Type,Py_Date
Job J_ID,Start_Location,Delivery_Location
Employee E_ID,E_Name,E_Telno,E_Type
Transport Unit Driver_ID,Assistant_ID,Tr_ID
Depot D_ID,D_Location,Depot_Address
Lorry L_ID,L_Lic,L_Unit
Container C_ID,C_Type
Trailer T_ID,T_Type
Primary Key
A primary key is a field in a table which uniquely identifies each row/record in a database
table. Primary keys must contain unique values. A primary key column cannot have NULL
values. A table can have only one primary key, which may consist of single or multiple fields.
When multiple fields are used as a primary key, they are called a composite key. (Anon., n.d.)
Entity Primary Key

Customer Cus_ID
Product P_ID
Load L_ID
Payment Py_ID
Job J_ID
Employee E_ID
Transport Unit Tr_ID
Depot D_ID
Lorry L_ID
Container C_ID
Trailer T_ID
Table 3 Primary Key
Page 29 of 102
Foreign Key
A foreign key is a key used to link two tables together. This is sometimes also called as a
referencing key. A Foreign Key is a column or a combination of columns whose values match
a Primary Key in a different table (Anon., n.d.)
Table 4 Foreign Key
Entity Foreign Key

Customer
Product Cus_ID, L_ID
Load
Payment Cus_ID , P_ID , Tr_ID , J_ID
Job Cus_ID , P_ID , Tr_ID , L_ID , D_ID ,E_ID
Employee
Transport Unit
Depot
Lorry C_ID , T_ID
Container
Trailer
Degrees of Relationships (Cardinality)

1. 1 to 1 (1:1)
2. 1 to Many (1:M)
3. Many to Many (M:M)
According to the ER Diagram 1 to 1 (Relationship)

• One Load has One Payment
• One Lorry Connects One Container
• One Container attach One Trailer
According to the ER Diagram 1 to M (Relationship)

• One Customer Sent Many Products
• One Transport Unit Have Many Depots
• One Depot have Many Lorry’s
According to the ER Diagram M to M (Relationship)

• Many Products Assign Many Loads
• Many Customers creates Many Jobs
Page 30 of 102
Logical Schema for Smart Movers
A logical schema is a design-centric database structure built to meet your business
requirements. It is a model that exists on a white board or in a diagramming tool. It is like the
architect's drawings of your database. (Anon., 2014)
Figure 2 Logical Schema
Page 31 of 102
Activity 1.2
Data normalization
Normalization is the way toward reorganizing Data in a database with the goal that it meets
two fundamental fundamentals: There is no excess of Data (all Data is put away in just one
spot) and Data conditions are smart (every related datum thing are put away together).
Normalization is significant for some reasons, however mostly on the grounds that it enables
databases to inhabit as scanty circle room as could be allowed, bringing about expanded
execution. Normalization is else called Data Normalization.
Purpose of the Data Normalization

The main purpose of normalization is to minimize the redundancy and remove Insert, Update
and Delete Anomaly. It divides larger tables to smaller tables and links them using
relationships. Data redundancy happens when the same piece of data is held in two separate
places.
Process of Normalization
Figure 3 Process of Normalization
Page 32 of 102
First Normal Form (1NF)
The first normal form (1NF) sets the fundamental rules for database normalization and relates
to a single table within a relational database system. Normalization follows three basic steps,
each building on the last. The first of these is the first normal form.
The first normal form states that:

• Every column in the table must be unique
• Separate tables must be created for each set of related data
• Each table must be identified with a unique column or concatenated columns called the
primary key
• No rows may be duplicated
• No columns may be duplicated
• No row or column intersections contain a null value
• No row or column intersections contain multivalued fields
According to the Logical Schema
Table 5 1NF
Customer Cus_ID
Product P_ID
Load L_ID
Payment Py_ID
Job J_ID
Employee E_ID
Transport Unit T_ID
Depot D_ID
Lorry L_ID
Container C_ID
Trailer T_ID
Page 33 of 102
Second Normal Form (2NF)
Second normal form (2NF) is the second step in normalizing a database. 2NF builds on the first
normal form (1NF).
Normalization is the process of organizing data in a database so that it meets two basic
requirements:
• There is no redundancy of data (all data is stored in only one place).

• Data dependencies are logical (all related data items are stored together).
A 1NF table is in 2NF form if and only if all of its non-prime attributes are functionally
dependent on the whole of every candidate key.
Customer (Cus_ID , Cus_Name , Tel_No , Cus_Address)
Later 2NF:
Customer Name (Cus_Name , Cus_Fname , Cus_Lname)
Customer (Cus_ID , Cus_Name)
Page 34 of 102
Third Normal Form (3NF)
Third normal form (3NF) is the third step in normalizing a database and it builds on the first
and second normal forms, 1NF and 2NF. 3NF states that all column reference in referenced
data that are not dependent on the primary key should be removed. Another way of putting this
is that only foreign key columns should be used to reference another table, and no other
columns from the parent table should exist in the referenced table
Page 35 of 102
Design set of simple interfaces to input and output for the above scenario using
Wireframe or any interface-designing tool.
There some Interface Design Using Wireframe
Figure 4 User Login
Page 36 of 102
Figure 5 Main Menu
Figure 6 Customer Form
Page 37 of 102
Figure 8 Product Form
Figure 7 Load Form
Page 38 of 102
Figure 9 Payment Form
Figure 10 Job Form
Page 39 of 102
Figure 11 Employee Form
Figure 12 Employee Form
Page 40 of 102
Figure 13 Depot Form
Figure 14 Lorry Form
Page 41 of 102
Figure 15 Container Form
Figure 16 Trailer Form
Page 42 of 102
Explain the validation mechanisms to validate data in the tables with examples.
Data validation is a process that ensures the delivery of clean and clear data to the programs,
applications and services using it. It checks for the integrity and validity of data that is being
inputted to different software and its components. Data validation ensures that the data
complies with the requirements and quality benchmarks.
Data validation is also known as input validation
Validation methods
Range Validation
This is generally used when working with data which contains numbers, currency, or date and
time values
According to the Scenario All Telephone Numbers Fields on Data Type with Range of 0-10.
Data Type Validation
This is a way to confirm that the correct data type is inputted.
Data Type in Customer Table:
Cus_Id int ,
Cus_Name Varchar ,
Cus_Telno Numeric
Data Type in Payment Table:
Py_Id int ,
Py_Type varchar ,
Py_Date Date
Page 43 of 102
Field Validation
You can select validation options to ensure that data is entered into a field correctly. When
validation options are selected, FileMaker Pro displays a message if you enter data incorrectly.
Customer Table: Customer Name
Payment Table: Payment Type
Employee Table: Employee Name
Page 44 of 102
Activity 1.3
Check whether the given design (ERD and Logical design) is representing the identified
user and system requirements to access the effectiveness of the design.
The database is designed according to the user and system requirements. To accomplish these
requirements writer designed some interfaces for each function. The database is designed
according to the user and system requirements. To accomplish these requirements Developer
designed some interfaces for each function.
Figure 17 Job Interface Design
By Using This Interface User Can insert Job Details for the Database. There are some interfaces
also there ex. Product, Payment, Customer and etc.
Nonfunctional requirements also include for the design of the database. There is a login
interfaces for keep a good security. It is also a user requirement. This system is easy to maintain
an easy to use. User main requirement is to use the system very easy and Secure. This system
design according to the system and user requirements. This design characterize all the
requirement according to the scenario. Visual studio 2012 software and SQL server 2012
software helped to create this system.
Page 45 of 102
Ex: user wants to update Customer Table. Then Administrator created update function in
Customer interface. Therefore, this requirement represented by this interface.
Users wants to know about the products in the company. Then Administrator created a Product
interface for it. Therefore, this design represent user and system requirements.
Figure 18 Product Interface
Page 46 of 102
Activity 02
Activity 2.1
Develop a relational database system according to the ER diagram you have created
(Use SQL DDL statements).
Create Database SMART_MOVER_DB
Use SAMART_MOVER_DB
Create Table Customer_Tbl
( Cus_Id int Identity,
Cus_Fname Varchar (100) not null,
Cus_Lname varchar (100)not null,
Cus_Telno Numeric (10)not null,
Cus_Address Varchar (250)not null,
Cus_Type Varchar (5)not null,
Constraint C_pk Primary Key (Cus_Id),
constraint chk_Cus check (Cus_Type in ('C1','C2','C3'))
);
Create Table Product_Tbl
P_Id int Identity,
P_Name Varchar (100) not null,
P_Type Varchar (15) not null,
Cus_Id int,
L_Id int,
Constraint p_pk Primary Key (P_ID),
Constraint Chk_P Check (P_Type in ('High Risk','Low Risk')),
Constraint cus_fk foreign key(Cus_Id)
references Customer_Tbl(Cus_Id) on delete cascade,
Constraint load_fk foreign key(L_Id)
Page 47 of 102
references Load_Tbl(L_Id) on delete cascade,
);
Create Table Load_Tbl
L_Id int Identity,
L_Type Varchar (20) not null,
Constraint L_pk Primary Key (L_Id),
Constraint Chk_L Check (L_Type in ('Small','Medium','Large'))
);
Create Table Payment_Tbl
Py_Id int Identity,
Py_Type Varchar (100) not null,
Py_Date Varchar (30) not null,
Cus_Id int,
P_Id int,
T_Id int,
J_Id int,
Constraint Py_pk Primary Key (Py_Id),
Constraint Chk_Py check (Py_Type in ('Cheque','Cash')),
Constraint cst_fk foreign key(Cus_Id)
Constraint pmt_fk foreign key(P_Id)
references Product_Tbl (P_Id) on delete cascade,
Constraint pmt_fk foreign key(T_Id)
references Product_Tbl (T_Id) on delete cascade,
Page 48 of 102
Constraint jul_fk foreign key(J_Id)
references Product_Tbl (J_Id )on delete cascade,
);
Create Table TransportUnit_Tbl
Tr_Id int Identity,
Driver_ID int,
Assistant_Id int,
Constraint T_pk Primary Key (Tr_Id)
);
Create Table Depot_Tbl
D_Id int Identity,
D_Location Varchar (250),
Depot_Address Varchar (250),
Constraint D_pk Primary Key (D_Id)
);
Create Table Employee_Tbl
E_Id int Identity,
E_Name Varchar (100),
E_Telno Numeric (10),
E_Type Varchar (50),
Constraint E_pk Primary key (E_Id),
Constraint Chk_E Check (E_Type in ('Manager','Driver','Assistant'))
);
Create Table Job_Tbl
Page 49 of 102
(
J_Id int Identity,
Start_Location Varchar (100) not null,
Delivery_Location Varchar (100) not null,
Cus_Id int,
P_Id int,
Tr_Id int,
L_Id int,
D_Id int,
E_Id int,
Constraint J_pk Primary Key (J_Id),
Constraint cs_fk foreign key(Cus_Id)
Constraint pro_fk foreign key(P_Id)
references Product_Tbl(P_Id),
Constraint Tr_fk foreign key(Tr_Id)
references TransportUnit_Tbl(Tr_Id),
Constraint L_fk foreign key(L_Id)
references Load_Tbl(L_Id),
Constraint D_fk foreign key(D_Id)
references Depot_Tbl(D_Id) on delete cascade,
Constraint E_fk foreign key(E_Id)
references Employee_Tbl(E_Id) on delete cascade,
);
Page 50 of 102
Create table Lorry_Tbl
( Lr_Id int Identity,
Lr_Lic Varchar (100),
L_Unit Varchar (100),
Cus_Id int,
Tr_Id int,
Constraint Lorry_pk Primary Key (Lr_Id),
Constraint cos_lorry_fk foreign key(Cus_Id)
Constraint trans_fk foreign key(Tr_Id)
references TransportUnit_Tbl(Tr_Id) on delete cascade,
);
Create Table Container_Tbl
( Con_Id Int Identity,
Con_Type Varchar (25),
Constraint Con_pk Primary Key (Con_Id),
Constraint chk_C Check (Con_Type in ('Small','Medium','Large'))
);
Create Table Trailer_Tbl
( T_Id Int Identity,
T_Type Varchar (250),
Constraint Trail_pk Primary Key (T_Id),
Constraint chk_T Check (T_Type in ('Small','Medium','Large'))
);
Page 51 of 102
Figure 20 Database Create query
Database Created
Figure 19 Database on Databases
Page 52 of 102
Provide evidence of the use of a suitable IDE to create a simple interface to insert,
update and delete data in the database
Integrated Development Environment (IDE)

An Integrated Development Environment (IDE) is an application that facilitates application
development. In general, an IDE is a graphical user interface (GUI)-based workbench designed
to aid a developer in building software applications with an integrated environment combined
with all the required tools at hand. Most common features, such as debugging, version control
and data structure browsing, help a developer quickly execute actions without switching to
other applications. Thus, it helps maximize productivity by providing similar user interfaces
(UI) for related components and reduces the time taken to learn the language. An IDE supports
single or multiple languages.
Advantages of Integrated Development Environment (IDE)
1. Less time and effort: The entire purpose of an IDE is to make developing faster and
easier. Its tools and features are supposed to help you organize resources, prevent
mistakes, and provide shortcuts.
2. Enforce project or company standards: Simply by working in the same
development environment, a group of programmers will adhere to a standard way of
doing things. Standards can be further enforced if the IDE offers predefined
templates, or if code libraries are shared between different team members/teams
working on the same project.
3. Project management: This can be twofold. First, many IDEs have documentation
tools that either automate the entry of developer comments, or may actually force
developers to write comments in different areas. Second, simply by having a visual
presentation of resources, it should be a lot easier to know how an application is laid
out as opposed to traversing the file system for arcane files in the file system
Page 53 of 102
Disadvantages of Integrated Development Environment (IDE)
1. Learning curve: IDEs are complicated tools. Maximizing their benefit will
require time and patience.
2. A sophisticated IDE may not be a good tool for beginning programmers:
If you throw the learning curve of an IDE on top of learning how to program,
it can be quite frustrating. Further, features and shortcuts for experienced
programmers often hide crucial but mundane details of a language. Details
should not be overlooked when learning a new language. Using an IDE may
hamper the learning of a new language.
3. Will not fix bad code, practices, or design: You still need to be proficient and
meticulous. An IDE will not eliminate efficiency or performance problems in
your application. IDEs are like paintbrushes. Whether you create a Van Gogh
or a Velvet Elvis is dictated by your skill and decisions
Page 54 of 102
Visual Studio
Is this IDE Software. Which me using to create Interfaces and System for above Scenario. In
Visual Studio have so many Versions. I Used for This Interfaces Visual Studio 2012. This is
the Interface Which I Create Using Visual Studio IDE
Figure 21 User Interface using Visual Studio IDE
Page 55 of 102
Insert Function
This Picture was before Add Data row on Data Table
Figure 22 Before Data Add on Data Table
After Data Save on Data Table
Figure 23 Insert Function Interface
Page 56 of 102
Figure 24 After Data Save on Data Table
Delete Function
This Picture was before Delete Data row on Data Table
Figure 25 Before Delete Data row on Data Table
Page 57 of 102
The user wants to delete the data which Cus_Id =5.
Figure 26 Want to Delete Data Row
After Delete Data on Data Table
Figure 27 Delete Data Interface
Page 58 of 102
Update Function
The user wants to update the Cus_Telno which the data row Cus_Id =6
Figure 28 Before Update Cus_Id=6
After Update Data on Data table
Figure 29 After Data Update
Page 59 of 102
Figure 30 Data Has Been Changed
Implement the validation methods explained in task 1.2-part c.
Range Validation
This validation method is used to check the field range. It means Cus_Telno data type is
numeric (10). This field only can enter 10 characters.
This is The Range Validation Method Example:
Figure 31 Range Validation Method Example
Page 60 of 102
Data Type Validation
Each field takes a data type. It will be only can enter numbers, characters or together.
I Used to Find Data Type Validation the Cus_Id is field data type is int. So, it cannot enter
characters and it only allocate numbers. After entering a character for that field, the system
shows an error message.
Figure 32 Finding Data Validation error
Field Validation
The Customer Address field is empty and an error message will show when inserting data.
Developer used field validation for this system. If a field is empty, then an error message will
display. It is easy to the users to identify the error. Then users can avoid from errors.
Figure 33 Finding Field Validation
Page 61 of 102
Display the details payment with the job details and the customer details using Join
queries
SELECT Payment_Tbl.*, Customer_Tbl.*, Job_Tbl.* FROM Payment_Tbl INNER JOIN

Customer_Tbl ON Payment_Tbl.Cus_Id = Customer_Tbl.Cus_Id INNER JOIN Job_Tbl ON
Payment_Tbl.J_Id = Job_Tbl.J_Id AND Customer_Tbl.Cus_Id = Job_Tbl.Cus_Id
Page 62 of 102
Activity 2.2
Explain the usage of DML with below mentioned queries by giving at least one single
example per each case from the developed database.
DML is short name of Data Manipulation Language which deals with data manipulation and
includes most common SQL statements such SELECT, INSERT, UPDATE, DELETE, etc.,
and it is used to store, modify, retrieve, delete and update data in a database. (w3schools, n.d.)
• SELECT - retrieve data from a database
• INSERT - insert data into a table
• UPDATE - updates existing data within a table
• DELETE - Delete all records from a database table
Page 63 of 102
Select Query
Select * From <table_name>
Select * From Customer_Tbl
Figure 34 Select Query
Update Query
UPDATE table_name
SET column=value
WHERE someColumn=someValue
UPDATE Customer_Tbl
SET Cus_Lname='Hasmi'
WHERE Cus_Id=4
Figure 35 Update Query
Page 64 of 102
Delete Query
DELETE FROM tableName

WHERE someColumn = someValue
DELETE FROM Customer_Tbl

WHERE Cus_Id = 4
Figure 36 Delete Query
Page 65 of 102
Activity 2.3
Explain how security mechanisms have been used and the importance of these
mechanisms for the security of the database. Implement proper security mechanisms
(EX: -User groups, access permissions) in the developed database.
Database Security
Database security refers to the collective measures used to protect and secure a database or
database management software from illegitimate use and malicious threats and attacks. It is a
broad term that includes a multitude of processes, tools and methodologies that ensure security
within a database environment. (techopedia, n.d.)
Security plan
• Identify the user community.
• Gather the database information.
• Determine the types of user account (i.e. associate database objects and user
roles).
• Undertake a threat analysis.
• Establish DBA Developer ties and procedures.
• Establish policies for managing (creating, deleting, auditing) user accounts.
• Determine the user tracking policy.
• Establish the user identification method.
• Define security incidents and reporting procedure.
• Assess the sensitivity of specific data objects.
• Establish standards and enforcement procedures (as well as back-up and
recovery plans, of course).
Page 66 of 102
Developer has tool the system with security mechanism above mention. There are some
samples in below:
Login Interface Form
Figure 37 Login Interface Form
User can easily enter system using this login interface form. anybody can’t access this login
those who have username and Password. This Type of Login Very Secure
Page 67 of 102
If User name and Password is gone wrong or not filled System will Show Error Message
Figure 38 Username Password gone Wrong
If Username and Password Is Correct. System Will Show Login Successful
Figure 39 Username and Password is Correct
Page 68 of 102
Activity 2.4
Explain the usage of the below SQL statements with the examples from the developed
database
Group by
Order by
Having
Between
Where
Group by
SELECT count (Cus_Id), Cus_Type FROM Customer_Tbl GROUP BY Cus_Type
Figure 40 Group by Query
Page 69 of 102
Order By
SELECT * FROM Customer_Tbl ORDER BY Cus_Lname Asc;
Figure 41 Order by Query
Having
SELECT count (Cus_Id) , Cus_Id FROM Customer_Tbl Group by Cus_Id HAVING count
(Cus_Id)<=5 ;
Figure 42 Having Query
Page 70 of 102
Between
SELECT * FROM Customer_Tbl WHERE Cus_Id BETWEEN 2 AND 8 ;
Figure 43 Between Query
Where
SELECT * FROM Customer_Tbl WHERE Cus_Id=3
Figure 44 Where Query
Page 71 of 102
Activity 03
Activity 3.1
Provide a suitable test plan to test the system against user and system requirements.
Figure 45 Test Plan for Smart Movers
Page 72 of 102
Test Plan Contents
1. Introduction
2. Testing Objectives
3. Testing Scope
4. Test caste Template
5. Testing Procedure
Page 73 of 102
Introduction
Smart Movers is a transport company which deliver chemical products. They store their data
manually. They wanted a computerized system to do easy their works. Smart Mover System
Have Mote Data in System
Ex: Customer_Tbl , Product_Tbl , Payment_Tbl
Then They Create Database for Smart Mover with Using MS SQL 2012 and They Create
Interfaces of System with Using Visual Studio 2012 C# Programming Language . Then
Developer Create Insert , Update and Delete System for Interfaces. Then Developer has used
a Test Plan to Test the System.
Test Objective
Main object is to show all the functions perform perfectly. To confirm user and system
requirements involvement to the database. To find errors and make best answers for it. To
improve the value of the system. To improve manageability and performance. To check all the
calculation complete well and properly.
Testing Scope
The database is created to store “Smart Movers” company data. It has many functions, such as
record customers, employee registering, increase products and etc. Developer created many
test cases for database testing. Developer check actual result and await result for the test cases
and compare the result and confirm a conclusion.
Test caste Template
Table 6 Test Caste Template
Test outcome
Test case Input data Expected result Actual result
(Pass/Fail)
Page 74 of 102
Testing Procedure
Table 7 Test Case Interface
Test case no Description
01 Login when entering valid username and password
02 Login when entering invalid username and password
03 Insert details
04 Update details
05 Delete details
06 Insert a record to the database using SQL Query.
07 Update a record to the database using SQL Query.
08 Delete a record to the database using SQL Query.
Page 75 of 102
Provide relevant test cases for the database you have implemented
Test Login
Test Case No 1 : Login when entering valid username and password
Table 8 Test Case No1
Test outcome
(Did/Didn’t)
Tester has Username: Display a Displayed a Did
entering valid User “Login “Login
username and Successful” Successful”
password Password:
User123
Actual Result
Figure 46 Test Case No1
Page 76 of 102
Test Case No 2: Login when entering invalid username and password
Table 9 Test Case No 2
Test outcome
(Did/Didn’t)
Test Has Username: Display a Displayed a Did
entering invalid Admin “Please Check “Please Check
username and Username or Username or
Password:
password Password” Password”
Admin123
Actual Result
Page 77 of 102
Test Case No 3: Insert details
Test outcome
(Did/Didn’t)
Test Has Cus_Id:11 Display a Displayed a Did
entering Cus_Fname: Mohamed “Customer “Customer
data row for Details Save Details Save
Cus_Lname: Safnee
the customer Successfully” Successfully”
Cus_Telno: 0779427929
table
Cus_Address:Kattankudi
Cus_Type:C2
Actual Result
Page 78 of 102
Test Case No 4: Update details
Test outcome
(Did/Didn’t)
Test Has Cus_Fname: Ahamed Display a Displayed a Did
entering Cus_Telno: 0774545625 “Customer “Customer
updated data Updated Updated
row in the Successfully” Successfully”
customer
table. Tester
update
category 2 to
category 4.
Actual Result
Page 79 of 102
Test Case No 5: Delete details
Test outcome
(Did/Didn’t)
Test Has Delete Row Display a Displayed a Did
entering Cus_Id: 9 “Deleted “Deleted
delete a data Successfully” Successfully”
row in the
customer
table.
Actual Result
Page 80 of 102
Test Case No 6: Insert a record to the database using SQL Query.
Test outcome
(Did/Didn’t)
Test Has Cus_Id:11 Display a “1 Displayed a Did
entering Cus_Fname: Mohamed row(s) “1 row(s)
Insert a affected” affected”
Cus_Lname: Shiraz
record to the Cus_Telno: 0774521212
Customer
table using Cus_Address:Kattankudi
SQL Query. Cus_Type:C1
Figure 52 Test Case No 6
Page 81 of 102
Test Case No 7: Update a record to the database using SQL Query.

Test outcome
(Did/Didn’t)
Test Has Cus_Fname: Mohamed Display a “1 Displayed a Did
entering Cus_Lname: Shiraz row(s) “1 row(1)
Update a affected” affected”
Cus_Telno: 0774521212
record to the Cus_Address: Kalmunai
Customer
table using Cus_Type:C1
SQL Query.
Page 82 of 102
Test Case No 8: Delete a record to the database using SQL Query.

Test outcome
(Did/Didn’t)
Test Has Cus_Id = 13 Display a “1 Displayed a Did
entering row(s) “1 row(1)
Delete a affected” affected”
record to the
Customer
table using
SQL Query.
Page 83 of 102
Activity 3.2
Explain how the selected test data in task 3.1 b) can be used improve the effectiveness of
testing.
Can be considered as how viably testing is done or objective is talented that meets the client
requirement. In SDLC (Software advancement Life Cycle), we have fundamentals social affair
stage where SRS (Software Requirements Specification) and FRD (Functional Requirements
Document) are arranged and reliant on on that development group starts assembling the product
application, concurrently experiments are cut out of SRS and FRD records by the testing group.
Test capability starts directly toward the start of the improvement and performance of
experiments and after progression is finished to check the quantity of failures. Defects can be
large or unacceptable. Large failures are required to be fixed in the application or item and
invalid ones should be closed or overlooked. In this way, numerically it is determined as a level
of various genuine defects fixed in programming application divided by the collective of an
all-out number of failures filled and a complete number of defects got away.
Page 84 of 102
Activity 3.3
Get independent feedback on your database solution from the non-technical users and
some developers (use surveys, questioners, interviews or any other feedback collecting
method) and make recommendations and suggestions for improvements in a separate
conclusion/recommendations section.
Figure 57 supervisor Feedback
Page 85 of 102
Figure 58 Peer Friend Feedback
Page 86 of 102
Recommendations and suggestions for improvements in a separate conclusion /
recommendations section.
According to the feedback summary there are some references for this system. Manageability
is not satisfied of this software. Therefore developer have to develop it. To increase
Manageability developer have to reduce mouse clicks. It have to easy to install an update.
Graphical User Interface should be developed according to user’s feedbacks. Graphical User
Interface should have easy to use. Developer can encode the password for tool the security.
System functionalities have to divide for advantaged. This can help to improve effectiveness
of the system. The developer can well-arranged the system for users which have attraction.
Considering these references Developer can tool the system. Then the users can have a
superiority system.
Page 87 of 102
Activity 04
Activity 4.1
Prepare a simple users’ guide and a technical documentation for the support and
maintenance of the software.
Figure 59 User Manual for Smart Mover
Page 88 of 102
Content for User Manual
• Introduction
o User manual
o Purpose of User manual
o Database system
• Instructions for user
• Conclusion
Page 89 of 102
Introduction
User Manual
It is technical document future to give help to people using a particular system. It helps to
people to understand a software application. It contains simple language format and simple
sentences. This simple language format helps to users to understand it. User can get a clear idea
about the system by using user manual. User manual include all the details to execute the
system step by step.
Purpose of the Database System.
Main purpose of the user manual is to deliver strong information for users. How to implement
the system step by step.
Database System
This is a transport system for Smart movers Company. The main process is to transport
products for the customers. Customer stand registered for the system. Other register tasks are
Payment, Product , Load Etc. All the records are store in the transport database. Developer can
edit Data on Database.
Page 90 of 102
Instruction for Users
Figure 60 Instruction Login Page
If the user already have an account then they can enter the username and password. After
entering it click the login button. Then move into next interface.
If User Have Account they can’t access this System
If Username or Password gone Wrong System will Display:
Figure 61 Username or Password gone Wrong
Page 91 of 102
If Username and Password is Correct System Will Display:
Figure 62 Username and Password is Correct
Page 92 of 102
This Main Menu for This System:
Figure 63 Main Menu for This System
This interface. User can select one from them. If the user want to get a product then have to
select by product. If the user want to edit customer details the have to click “Customer”. For
each selection there is an interface.
Figure 64 Customer Form in This System
Page 93 of 102
Conclusion
From this user manual users can execute the system well. Users can
Login into This System
Edit Customer Details
View Customer Details
Buy product
This user manual guide users for done these works.
Page 94 of 102
Activity 4.2
Your technical documentation should include some of the UML diagrams (Use case
diagram Class diagram, etc.), flow charts for the important functionalities, context level
DFD and the Level 1 DFD.
Software and Hardware Requirements.
Figure 65 Software Hardware Requirements
Page 95 of 102
Use Case Diagram
Figure 66 Use Case Diagram
Page 96 of 102
Flow Chart
Figure 67 Flow Chart
Page 97 of 102
Activity 4.3
Suggest the future improvements that may be required to ensure the continued
effectiveness of the database system.
Future Improvement’s on the system.

The Developer use testing method for maintain the system. Developer test the system by two
weeks. Developer checked the data insert correctly to the database, update functions are
working and the Graphical User Interface performance. Check all the calculation are working
correctly month by month. Database system for any company is the base. Information,
company documents, important certificates, communications and what not is done on
computers. The entire company depends upon the IT department to maintain the systems of the
company. There is a cloud storage system. Therefore the Developer can develop the system to
web base system. If something happens to the database then data in the cloud are safe. Then
system develop to automatic backup. If the system not work today, then it can work with
yesterday back up data.
Page 98 of 102
Self-Criticism
I was clever to complete the assignments on my personal because of the fear and attention
towards the subject. There were some issues that pretentious my completion of the assignment,
some were the strengths and some were weakness.
Strengths:
1.Can Start Assignments on Time
2 Can Manage My Own Task at Deadlines
3. Get Some Ideas from Friends and Lectures
4. Get Good Experience in Visual Studio and Database SQL Server
5. Get Some Knowledge in Creating System and Database
Weakness:
1. In Time Management
2. Misunderstandings in Some Difficult Task
At the start I beaten to do my assignments and faced some problems after friends the help of
the said strengths finally I was bright to complete my assignment on time. The strengths helped
me to do the Creating System and Databases successfully and to improve Software . I learnt to
dose my own limits for finishing each task and to finish the final assignment as well. Now I
have a good knowledge on doing assignments. I’m self-confident that I have better my
professional skills and can-do other Creating System and Databases better than this in future.
Page 99 of 102
Conclusion
I’m really glad of implementing project. Because while this project was being implemented,
we got a lot of skills which we hadn’t gotten before. This project developed our skills, such as
Creating System and Creating Databases knowledge about Software, talks ability to others
without hesitation and nervous, critical thinking, collaboration and negation skill. We were
lack of knowledge regarding many things. It also taught a lot. We have an idea also to
implement this project in several schools who needs. Finally, we would also be thankful for t
hose lecturers and people who helped us to complete this project successfully.
Page 100 of 102

References
Anon., 2007. mysqa. [Online]
Available at: http://www.mysqa.info/e-learning/MDBS01CD/page_07.htm
[Accessed 29 October 2019].
Anon., 2014. Stack Exchange. [Online]

Available at: https://dba.stackexchange.com/questions/59780/what-is-the-difference-between-
logical-schema-and-physical-schema
Anon., 2019. Smartdraw. [Online]

Available at: https://www.smartdraw.com/entity-relationship-diagram/
Anon., n.d. Tutorialspoint. [Online]

Available at: https://www.tutorialspoint.com/sql/sql-primary-key.htm
Kern, M. H. a. H., 2001. The Software Life Cycle. [Online]

Available at: http://www.informit.com/articles/article.aspx?p=24016&seqNum=3
techopedia, n.d. techopedia. [Online]

Available at: https://www.techopedia.com/definition/29841/database-security
[Accessed 06 November 2019].
w3schools, n.d. w3schools. [Online]

Available at: https://www.w3schools.in/mysql/ddl-dml-dcl/
[Accessed 6 November 2019].
Page 101 of 102

Page 102 of 102

Unit 04 Database-Assignment Holistic

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 04 Database-Assignment Holistic

Uploaded by

Copyright:

Available Formats

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

Assessor Internal Verifier

INTERNAL VERIFIER CHECKLIST

Do the assessment criteria awarded match

Is the Pass/Merit/Distinction grade awarded

Assessor signature Date

Internal Verifier signature Date

Confirm action completed

Assessor signature Date

Higher Nationals - Summative Assignment Feedback Form

Unit Title Unit 04: Database Design & Development

Assignment Number 1 Assessor

LO3 Test the system against user and system requirements.

LO4 Produce technical and user documentation.

Grade: Assessor Signature: Date:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Formative Feedback: Assessor to Student

Feedback: Student to Assessor

Pearson Higher Nationals in

Word Processing Rules

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

Student’s Signature: Date:

Unit Number and Title Unit 4: Database Design & Development

Academic Year 2017/18

IV Name & Date

Assignment Brief and Guidance:

LO1 Use an appropriate design tool to design a relational

P1 Design a relational database system using appropriate

D1 Assess the effectiveness of the design in relation to user

LO2 Develop a fully functional relational database system,

P2 Develop the database system with evidence of user

P3 Implement a query language into the relational database

M3 Assess whether meaningful data has been extracted

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

P5 Produce technical and user documentation.

M5 Produce technical and user documentation for a fully

D3 Assess any future improvements that may be required

Smart Movers Provides Four Types Requirements

Smart Movers User Requirement

Smart Movers System Requirement

Table 1 Smart Movers Software and Hardware Requirement

Software Requirement Hardware Requirement

Figure 1 ER Diagram for Smart Movers

Entity are Two Types

According to the ER Diagram:

Entity Primary Key

Table 4 Foreign Key

Entity Foreign Key

Degrees of Relationships (Cardinality)

According to the ER Diagram 1 to 1 (Relationship)

According to the ER Diagram 1 to M (Relationship)

According to the ER Diagram M to M (Relationship)

Figure 2 Logical Schema

Purpose of the Data Normalization

Figure 3 Process of Normalization

The first normal form states that:

According to the Logical Schema

• There is no redundancy of data (all data is stored in only one place).

Customer (Cus_ID , Cus_Name , Tel_No , Cus_Address)