Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS

Programme title BTEC HND in Computing

Assessor Internal
Verifier
Unit 04: Database Design & Development
Unit(s)
Database Solution for Quiet Attic Films
Assignment title
Student’s name
List which assessment Pass Merit Distinction
criteria the Assessor has
awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria awarded
match those shown in the Y/N
assignment brief?
Is the Pass/Merit/Distinction grade
awarded justified by the assessor’s Y/N
comments on the 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 Y/N
criteria? Y/N
• Identifying opportunities for
improved performance? Y/N
• Agreeing actions?
Does the assessment decision need
Y/N
amending?
Assessor signature Date

Internal Verifier signature Date

Programme Leader signature (if
Date
required)

Confirm action completed

Remedial action
taken
Give details:
Assessor signature Date
Internal
Date
Verifier
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
Submission Date
Received 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 & P1 M1 D1
Distinction Descripts

LO2 Develop a fully functional relational database system, based on an existing system
design
Pass, Merit & P2 P3 M2 M3 D2
Distinction Descripts

LO3 Test the system against user and system requirements.

Pass, Merit & P4 M4 D2
Distinction Descripts

LO4 Produce technical and user documentation.

Pass, Merit & P5 M5 D3
Distinction Descripts

Grade: Assessor Signature: Date:

Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once
internal and external moderation has taken place and grades decisions have been
agreed at the assessment board.
Assignment Feedback
Formative Feedback: Assessor to Student

Action Plan

Summative feedback

Feedback: Student to Assessor

Assessor Date
signature

Student Date
signature
Pearson Higher Nationals in
Computing
Unit 04: Database Design & Development
Assignment 01
General Guidelines

1. A Cover page or title page – You should always attach a title page to your
assignment. Use previous page as your cover sheet and make sure all the details
are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.

Word Processing Rules

1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject,
Assignment No, and Page Number on each page. This is useful if individual sheets
become detached for any reason.
5. Use word processing application spell check and grammar check function to help
editing your assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts in the assignments, except for
the compulsory information. eg: Figures, tables of comparison etc. Adding text
boxes in the body except for the before mentioned compulsory information will
result in rejection of your work.
2. Carefully check the hand in date and the instructions given in the assignment. Late
submissions will not be accepted.
3. Ensure that you give yourself enough time to complete the assignment by the due
date.
4. Excuses of any nature will not be accepted for failure to hand in the work on time.
5. You must take responsibility for managing your own time effectively.
6. If you are unable to hand in your assignment on time and have valid reasons such
as illness, you may apply (in writing) for an extension.
7. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
8. Non-submission of work without valid reasons will lead to an automatic RE
FERRAL. You will then be asked to complete an alternative assignment.
9. If you use other people’s work or ideas in your assignment, reference them
properly using HARVARD referencing system to avoid plagiarism. You have to
provide both in-text citation and a reference list.
10. If you are proven to be guilty of plagiarism or any academic misconduct, your
grade could be reduced to A REFERRAL or at worst you could be expelled from
the course
Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and
to present it as my own without attributing the sources in the correct form. I further
understand what it means to copy another’s work.

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

2. I understand the plagiarism and copying policy of Edexcel UK.
3. I know what the consequences will be if I plagiarise or copy another’s work in any
of the assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program,
will be my own, and where I have made use of another’s work, I will attribute the
source in the correct way.
5. I acknowledge that the attachment of this document signed or not, constitutes a
binding agreement between myself and Pearson, UK.
6. I understand that my assignment will not be considered as submitted if this
document is not attached to the assignment.

Student’s Signature: Date:

(Provide E-mail ID) (Provide Submission Date)
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number

Unit Number and Title Unit 4: Database Design & Development

Academic Year 2022/23

Unit Tutor

Assignment Title Data base system for Quiet Attic Films

Issue Date 09/01/2023

Submission Date 05/03/2023
IV Name & Date

Submission format

Part 1: The submission should be in the form of an individual written report written in a concise,
formal business style using single spacing and font size 12. You are required to make use of
headings, paragraphs and subsections as appropriate, and all work must be supported with
research and referenced using Harvard referencing system. Please also provide in-text citation
and bibliography using Harvard referencing system. The recommended word limit is 3,000–
3,500 words, although you will not be penalised for exceeding the total word limit.
Part 2: The submission should be in the form of a fully functional relational database system
demonstrated to the Tutor; and an individual written report (please see details in Part 1 above).
Part 3: The submission should be in the form of a witness statement of the testing completed
by the Tutor; technical documentation; and a written report (please see details in Part 1
above).
Unit Learning Outcomes:

LO1 Use an appropriate design tool to design a relational database system for a substantial
problem.
LO2 Develop a fully functional relational database system, based on an existing system design.
LO3 Test the system against user and system requirements.
LO4 Produce technical and user documentation.
Assignment Brief and Guidance:
Assignment brief
Quiet Attic Films is a film production company based in London, England who specialize in
making short information films and advertisements for television. They want you to design
and implement a database that meets the requirements for their data. These requirements are
specified in this scenario and the examples of paper documents kept by the company shown
below.
Quiet Attic Films organize their data around the concept of a ‘production’. A production is
specified as being for a particular client; but note that a client might have more than one
production at any time. A production will take place at one or more locations. A production
will also use a number of, what are called, properties, which might be anything from an
actual property like a building, to costumes or small items of any sort. It is important to keep
a record of which properties are required at which location.
There should also be a record kept of the staff types that are assigned to productions
Activity 1
Identify the user and system requirements to design a database for the above scenario and
design a relational database system using conceptual design (ER Model) by including
identifiers (primary Key) of entities and cardinalities, participations of relationships. Convert
the ER Model into logical database design using relational database model including primary
keys foreign keys and referential Integrities.
It should contain at least five interrelated tables. Check whether the provided logical design
is normalised. If not, normalize the database by removing the anomalies.
(Note:-It is allowed to have your own assumptions and related attributes within the scope
of the case study given)
Design set of simple interfaces to input and output for the above scenario using Wireframe
or any interface-designing tool. Evaluate the effectiveness of the given design (ERD and
Logical design) in terms of the identified user and system requirements.
Activity 2
Develop a relational database system according to the ER diagram you have created (Use
SQL DDL statements). Provide evidence of the use of a suitable IDE to create a simple
interface to insert, update and delete data in the database. Implement proper security
mechanisms in the developed database and evaluate the database solution developed in
terms of its effectiveness with relevance to the user and system requirements identified,
system security mechanisms (EX: -User groups, access permissions) and the maintenance of
the database. Suggest improvements for any identified problems.

Assess the usage of the below SQL statements with the examples from the developed
database to prove that the data extracted through them are meaningful and relevant to the
given scenario.
Select/ Where / Update / Between / In / Group by / Order by / Having

Activity 3

3.1 Provide a suitable test plan to test the system against user and system requirements.
provide relevant test cases for the database you have implemented. Assess how the
selected test data can be used to improve the effectiveness of testing.
Note:- Learner needs to give expected results in a tabular format and screenshots of the
actual results with the conclusion

3.2 Get independent feedback on your database solution from the non-technical users and
some developers (use surveys, questioners, interviews or any other feedback collecting
method) and make a separate conclusion from the feedbacks.
Activity 4

Produce technical and user documentation for a fully functional system, including data flow
diagrams showing movement of data through the system, and flowcharts describing how
the system works. Evaluate the developed database by suggesting future enhancements to
ensure the effectiveness of the system.
Grading Criteria Achieved Feedback

LO1 Use an appropriate design tool to design a relational

database system for a substantial problem.

P1 Design a relational database system using appropriate

design tools and techniques, containing at least four
interrelated tables, with clear statements of user and system
requirements.
M1 Produce a comprehensive design for a fully-functional
system, which includes interface and output designs, data
validations and data normalization.
D1 Evaluate the effectiveness of the design in relation to user
and system requirements.
LO2 Develop a fully-functional relational database
system, based on an existing system design
P2 Develop the database system with evidence of user
interface, output and data validations, and querying across
multiple tables.

P3 Implement a query language into the relational database

system

.
M2 Implement a fullyfunctional database system, which
includes system security and database maintenance.

M3 Assess whether meaningful data has been extracted

through the use of 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.
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 data flow diagrams and
flowcharts, describing how the system works.

D3 Evaluate the database in terms of improvements needed

to ensure the continued effectiveness of the system.
Unit 04: Database Design & Development

Database Solution for Quiet Attic Films

 Content

1.0 Database .................................................................................................................... 1

1.0.1Relational databases. .................................................................................................... 1
1.0.2 Non-relational database........................................................................................... 2
1.0.3 Object Oriented database ................................................................................... 3
1.1 Components of a Database ............................................................................................. 4
1.2 Database Management System (DBMS) ....................................................................... 5
1.3 Database Models ....................................................................................................... 6
1.3.1 Types of Database Models ................................................................................ 6
1.4 Database Design........................................................................................................ 8
1.4.1 Conceptual Design ............................................................................................. 8
1.4.2 Logical Design ........................................................................................................ 9
1.4.3 Normalization........................................................................................................ 10
1.4.4 Physical Design ..................................................................................................... 14
1.4.5 User Requirement ................................................................................................. 14
1.4.6 System Requirement ............................................................................................. 14
1.5 Interface design for quiet attic films ............................ Error! Bookmark not defined.
2.0 Data Validation ............................................................................................................ 15
2.1 Data Definition Language (DDL) ................................................................................ 17
2.2 Developing a relational database system using SQL DDL statements according to the
ER diagram ........................................................................................................................ 17
2.3 Security Mechanisms ................................................................................................... 21
2.3.1 Database Security .................................................................................................. 21
2.4 Database Maintenance ................................................................................................. 23
2.5 Usage of SQL statements ............................................................................................. 24
3.0 Test plan for quiet attic films .................................................................................. 29
4.0 Technical and user documentation for quiet attic films database system .................... 29
References .......................................................................................................................... 32

ii | P a g e
 Table of Figures

Figure 1(Hierarchical model) ............................................................................................... 6

Figure 2 (Network Model) ................................................................................................... 7
Figure 3 (ER Model) ............................................................................................................ 7
Figure 4 (Relational Model) ................................................................................................. 8
Figure 5 (ER Diagram for quiet attic films) ......................................................................... 9
Figure 6 (Logical Diagram for Quiet Attic Films) ............................................................. 10
Figure 7 (1NF) ................................................................................................................... 11
Figure 8 (Before 2NF)........................................................................................................ 12
Figure 9 (After 2NF) .......................................................................................................... 12
Figure 10 (Before 3NF)...................................................................................................... 13
Figure 11 (After 3NF) ........................................................................................................ 13
Figure 12 (Login Page) ...................................................... Error! Bookmark not defined.
Figure 13 (Main Menu) ...................................................... Error! Bookmark not defined.
Figure 14 (Production Page) .............................................. Error! Bookmark not defined.
Figure 15 (Client Page) ...................................................... Error! Bookmark not defined.
Figure 16 (Location Page).................................................. Error! Bookmark not defined.
Figure 17 (Property Page) .................................................. Error! Bookmark not defined.
Figure 18 (Staff Page) ........................................................ Error! Bookmark not defined.
Figure 19 (Employee Page)................................................ Error! Bookmark not defined.
Figure 20 (Test ID 1.1 Result) ........................................... Error! Bookmark not defined.
Figure 21 (Test ID 1.2 Result) ........................................... Error! Bookmark not defined.
Figure 22 (Test ID 1.3 Result) ........................................... Error! Bookmark not defined.
Figure 23 Main Menu ........................................................ Error! Bookmark not defined.
Figure 24 Insert data to client table in data base through GUI ......... Error! Bookmark not
defined.
Figure 25 Appearance of the client table in database after insert data successfully ...Error!
Bookmark not defined.
Figure 26 Update data in client table in data base through GUI ....... Error! Bookmark not
defined.
Figure 27 Appearance of the client table in database after update data successfully .Error!
Bookmark not defined.
Figure 28 Delete data in client table in data base through GUI ........ Error! Bookmark not
defined.
Figure 29 Appearance of the client table in database after delete data successfully ..Error!
Bookmark not defined.

iii | P a g e
iv | P a g e
1.0 Database
A database is a structured collection of information that has been arranged and is often
kept electronically in a computer system. A database management system often
manages a database (DBMS).
The term "database system," which is frequently shortened to "database," refers to the
combination of the data, the DBMS, and the applications that are connected to it.
(oracle, 2023)
There are 3 different types of databases based. They are,
1. Relational database.
2. Non-relational database (No SQL)
3. Object Oriented database.

1.0.1Relational databases.
Data points that are connected to one another are stored and accessible in a relational
database, which is a form of database. The relational model, an easy-to-understand
method of representing data in tables, is the foundation of relational databases. Each
table row in a relational database is a record with a distinct ID known as the key. It is
simple to determine the associations between data points because the table's columns
carry the properties of the data and each record typically has a value for each property.
(oracle, 2023)
Advantages of Relational Database
Simple Model
The simplest approach is a relational database system because it doesn't need intricate
structure or querying procedures. It doesn't involve lengthy architectural procedures like
the definition or structuring of hierarchical databases. Since the structure is
straightforward, it can be handled with straightforward SQL queries without the need for
complicated query architecture. (Pedamkar, 2023)
Data Accuracy
With the help of the primary key and foreign key principles, many tables in a relational
database system can be connected to one another. The data is no longer repeated as a
result. There is no possibility of data duplication. As a result, relational databases have
more data accuracy than other database systems. (Pedamkar, 2023)

1|Page
Easy Access to Data
In contrast to other types of databases, which can only be accessed by going via a tree or
a hierarchical model, the Relational Database System does not have a pattern or
pathway for accessing the data. Any table in the relational database can be queried by
anyone with access to the data. One can combine all or any number of related tables
using join queries and conditional statements to retrieve the needed data. The user can
easily recover the necessary data as a result of modifying the output data depending on
the values from any column, across any number of columns. It enables selection of the
desired columns to be included in the result so that only pertinent data will be shown.
(Pedamkar, 2023)
Flexibility
Due to its flexible structure that can adapt to the continuously changing requirements, a
Relational Database system has the capacity to level up and extend for long ranges. This
makes it easier to update and delete data as needed and to handle the growing volume of
data that is coming in. This architecture allows for modifications to be made to a
database's setup as well, and these changes can be easily implemented without causing
the database's data or other components to crash. (Pedamkar, 2023)
Data Integrity
A fundamental aspect of the Relational Database system is data integrity. All of the Data
in the database is contained inside appropriate arrangements thanks to solid Data entries
and legitimacy validations, and the data required for establishing the associations is
there. The database's tables' relational stability helps prevent the records from being
incomplete, isolated, or unrelated. Data integrity aids in making sure of the relational
database's other key properties like Ease of use, precision, and stability of the data.
(Pedamkar, 2023)

1.0.2 Non-relational database

In contrast to conventional relational databases, non-relational databases (commonly
referred to as NoSQL databases) store their data in a non-tabular format. Non-relational
databases, on the other hand, might be built using data structures like documents.
Despite carrying a variety of different sorts of information in various formats, a
document can be extremely thorough. Non-relational databases are far more flexible

2|Page
than relational databases due to their capacity to process and organize numerous types of
information concurrently. (mongodb, 2023)
Benefits of a non-relational database
Massive dataset organization
Non-relational databases can easily query huge datasets in the era of Big Data, in
addition to storing vast amounts of data. Non-relational databases have a number of
advantages, including scale and speed. (mongodb, 2023)
Flexible database expansion
Data is dynamic. A non-relational database can incorporate new data as it is gathered,
augmenting the existing database with new levels of granularity even if it does not suit
the data types of the previously obtained data. (mongodb, 2023)
Multiple data structures
Users' information is currently collected in a variety of ways, including through the
usage of numbers, strings, photos, videos, and message histories. A database must be
able to store these numerous information forms, comprehend their connections, and
execute in-depth queries. Non-relational databases can combine many information kinds
in one document regardless of the format in which the information is stored. (mongodb,
2023)
Built for the cloud
An enormous non-relational database is possible. They also require a hosting
environment that can develop and expand with them because they sometimes have the
potential to grow tremendously. Non-relational databases thrive in the cloud due to its
built-in scalability. (mongodb, 2023)

1.0.3 Object Oriented database.

A database that adheres to object-oriented programming principles is known as an

object-oriented database (OOP). Data is arranged and stored as objects in object-
oriented databases, which are self-contained entities that include both data and the
actions or methods that can be used on that data. This makes it possible to organize and
depict complicated data structures and interactions in an effective way. (databasetown,
2023)

3|Page
Advantages of Object-Oriented Databases
Efficient representation of complex data structures
The ability to effectively express and handle intricate data structures and relationships is
one of the key benefits of object-oriented databases. Applications that require the
integration of many data types and sources, such as multimedia data or data from several
sources, will find this to be especially helpful. (databasetown, 2023)
Improved code reuse and modularity
Inheritance and flexibility, which facilitate effective reuse of code and data structures,
are supported by object-oriented databases. This enhances the database's versatility and
maintainability and makes it easier to design and handle complicated data structures.
(databasetown, 2023)
Support for data integration
Since they permit the depiction of complex data structures and relationships, object-
oriented databases are well suited for applications that call for the integration of various
data kinds and sources. (databasetown, 2023)
Flexibility and adaptability
As object-oriented databases are so versatile and adaptive, they can quickly
accommodate changes in data structures and specifications. Applications that need to
quickly react to shifting business needs and requirements will find this to be especially
helpful. (databasetown, 2023)
Improved performance
Since they are designed to efficiently represent and manipulate complex data structures
and relationships, object-oriented databases may perform better than traditional database
models. (databasetown, 2023)

1.1 Components of a Database

There have five main components in a database. Those are,
1. Hardware
Hardware describes the tangible, electronic components that serve as an
interface between computers and actual systems, such as hard drives and
computers. (Taylor, 2023)

4|Page
2. Software
Software, which refers to a collection of programs used to administer and
control databases, also comprises the operating system, network software,
applications used to access databases, and database software. (Taylor, 2023)
3. Data
To make it more relevant, data must be structured and processed from basic
facts and information. The use of data within a company can be centralized,
documented, controlled, and coordinated using database dictionaries. A
database is a collection of data about a database. (Taylor, 2023)
4. Procedures
The term "procedures" refers to the instructions used in a database
management system and includes everything from setup and installation
instructions to login and logout instructions, administration of day-to-day
operations, data backup instructions, and report generation instructions.
(Taylor, 2023)
5. Database Access Language
A database's data can be accessed, updated, and deleted using commands
written in database access language. Before sending commands to the database
for execution, users can write them using Database Access Language. Users
can create new databases, tables, insert data, and delete data by using the
language. (Taylor, 2023)

1.2 Database Management System (DBMS)

In data analysis, the phrase "database management system" (DBMS) is well-known. It
describes a group of applications that give users access to databases and the ability to
alter, maintain, report, and link data. Data redundancy, regulated data sharing, and data
integrity issues are frequently addressed with DBMSs. DBMS is only software and not
an information system. (Taylor, 2023)

5|Page
1.3 Database Models
A database model displays the relationships and restrictions that control how data can be
stored and used, as well as the logical structure of a database. Specific database models
are created based on the principles and guidelines of the larger data model that the
designers choose to use. The majority of data models have a corresponding database
diagram. (lucidchart., 2023)

1.3.1 Types of Database Models

There have many kinds of data model, some of them as follow,

Hierarchical Model
This database type arranges information into a structure like a tree, with a single root to
which all other information is connected. The hierarchy grows like a tree by adding
child nodes to the parent nodes as it progresses from the Root data. A child node in this
architecture will have just one parent node. Therefor it called one to many relationship
has in this model. (studytonight, 2023)

Figure 1(Hierarchical model)

Network Model
An expansion of the hierarchical model is this. This architecture allows for several
parent nodes, which allows for a more graph-like organization of the data.
When more relationships are created in this database model, data becomes more tied to
one another. Also, since the data is more connected, obtaining it is also simple and
quick. The mapping of many-to-many data relationships uses this database model. Prior
to the introduction of the Relational Model, this was the most popular database model.
(studytonight, 2023)

6|Page
Figure 2 (Network Model)
Entity-relationship Model
Relationships are established in this database model by classifying the object of interest
as an entity and its properties as attributes. Relationships are used to connect various
entities. E-R models are designed to illustrate relationships in a way that is
understandable to a variety of stakeholders. This approach is useful for creating
databases that can later be converted into relational mode tables. (studytonight, 2023)

Figure 3 (ER Model)

Relational Model
The database is presented by the relational model (RM) as a set of relations. A relation
is nothing more than a values table. Each row in the table is a collection of relevant data
values. These table rows represent an actual person, place, thing, or relationship. To
determine the significance of the values in each row, the table name and column names
are useful. The information is displayed as a collection of relations. Tables are used to

7|Page
hold data in the relational model. .however, how the data are logically arranged is
unrelated to how the data are physically stored. (Peterson, 2022)

Figure 4 (Relational Model)

1.4 Database Design

A general definition of database design is a group of activities or procedures that
improve the planning, creation, implementation, and maintenance of an enterprise data
management system. A good database design improves data consistency while lowering
maintenance costs. It also has a significant impact on cost-effective measures in terms of
disk storage. Consequently, creating a database requires an innovative idea. Following
the limitations, the designer should choose how the pieces relate to one another and
what type of data has to be stored. (javatpoint., 2023)
Steps in database design as follow,
1. Conceptual design
2. Logical Design
3. Normalization
4. Physical Design

1.4.1 Conceptual Design

The database design process begins with conceptual design. At this level, creating a
database that is not dependent on database software or physical specifications is the
aim. A conceptual data model that details the key data entities, attributes, relationships,

8|Page
 and constraints of a certain problem domain is the process' output. This work has a
descriptive, narrative form. (THIRU, 2023)
Entity Relationship Diagrams are the mostly use conceptual design model now a days.
Database design team of quiet attic films use following entity relationship diagram as
the first step of designing database.

Figure 5 (ER Diagram for quiet attic films)

1.4.2 Logical Design

The second level of database design is logical design. Entities, relationships, and multi-
valued attributes are mapped into a logical schema through the logical design process.
Designing an enterprise-wide database based on a certain data model is the logical
design objective. (Elgabry, 2016)
Database design team of quiet attic films use following logical design diagram as the
second step of designing database.

9|Page
Figure 6 (Logical Diagram for Quiet Attic Films)

1.4.3 Normalization
Data organization in a database is done by normalization. This involves building tables
and linking those tables together in accordance with principles to protect the data and
increase the database's adaptability by removing redundancy and inconsistent reliance.
(microsoft, 2022)
Database design team of quiet attic films use Normalization as the third step of
designing database.

There is a list of Normal Forms in normalization. They are,

- 1NF (First Normal Form)

- 2NF (Second Normal Form)

- 3NF (Third Normal Form)

10 | P a g e
 - BCNF (Boyce-Codd Normal Form)

- 4NF (Fourth Normal Form)

- 5NF (Fifth Normal Form)

- 6NF (Sixth Normal Form)

1NF (First Normal Form)
Below rules need to be fulfil when come to first normal form

- Each table cell should contain a single value.

- Each record needs to be unique.
- A column should contain values that are of same type

Below table show how properties table in quiet attic films database appears after convert
it to the first normal form.

Figure 7 (1NF)

2NF (Second Normal Form)

Below rules need to be fulfil when come to second normal form
- Table should be in first normal form
- Not have any partial dependencies

11 | P a g e
Below table show how employee table in quiet attic films database appears when
convert it to the second normal form.

Figure 8 (Before 2NF)

Figure 9 (After 2NF)

12 | P a g e
3NF (Third Normal Form)
Below rules need to be fulfil when come to third normal form
- Table should be in second normal form
- Must not have transitive function dependencies on the primary key
Below table show how Production table in quiet attic films database appears when
convert it to the third normal form.

Figure 10 (Before 3NF)

Figure 11 (After 3NF)

13 | P a g e
1.4.4 Physical Design

The final step of database design is the physical design. The process of converting a data
model into the physical data structure of a specific database management system is
known as physical database design (DBMS). In order to complete Physical Design, it is
typically necessary to expand a business model into a fully attributed model (FAM),
which is then converted into a physical design model. (Banister, 2021)
Common characteristics of a physical data Design
- Outlines the information needs of a specific project or application.
- Includes a list of all tables and columns.
- Foreign keys are used to identify relationships between tables in this document.
- The physical data model could differ from the logical data model due to physical
factors.

1.4.5 User Requirement

User requirements, also known as user needs, outline what the user accomplishes with
the system, including the tasks they must be able to carry out. In a User Requirements
Document (URD), narrative material is typically used to describe user requirements.
The user typically approves user requirements, which are the main source of information
for formulating system requirements. Identifying what the user genuinely wants a
software product to achieve is a crucial and challenging phase in its creation. This is due
to the fact that the user frequently struggles to fully express their requirements and
desires, and that the information they do supply may also be unreliable, erroneous, or
contradictory. The business analyst is in charge of fully comprehending what the
consumer wants. Because of this, user needs and system requirements are typically
treated differently. In order to ensure that the requirements meet certain quality
standards, the business analyst thoroughly examines user requirements before carefully
creating and documenting a set of high-quality system requirements.

1.4.6 System Requirement

The components of the system that developers utilize to construct it are called system
requirements. These are the standard "must" clauses that specify what the system "shall
do." Functional requirements and supplementary requirements are the two categories of
system requirements. An item that a user must have in order to complete their task is

14 | P a g e
 specified by a functional requirement. An example of a functional requirement would be
for a system to be able to enter and print cost estimates. All the additional needs that are
not covered by the functional requirements are specified in the supplemental or non-
functional requirements. Who wants to be referred to as nonfunctional? I much prefer
the term "supplemental requirements" instead. Quality of service requirements are
another name for supplementary requirements. The system design includes a thorough
plan for putting functional requirements into practice.

2.0 Data Validation

Data quality and accuracy are ensured through a procedure known as data validation. In
order to assure the logical consistency of input and stored data, it is implemented by
including a number of checks in a system or report.
Data is entered into automated systems with little to no human oversight. As a result, it's
critical to make sure that the data entering the system is accurate and up to par in terms of
quality. If the data is not recorded correctly, it will be of little use and may lead to more
serious downstream reporting concerns. Even correctly entered unstructured data will
result in associated expenditures for cleaning, converting, and storing. (Taylor, 2023)

Types of Data Validation

Validating data comes in many different forms. To guarantee that the data is accurate
before being stored in the database, the majority of data validation methods will carry
out one or more of these tests. Data validation checks of common types include:

1. Data Type Check

The right data type of the entered data is verified by a data type check. A field, for
instance, might only accept numerical information. If so, the system should reject any
data that includes additional characters, such as letters or special symbols. (Taylor,
2023)

2. Code Check

A code check verifies that a field is chosen from an acceptable list of values or that it
adheres to specific formatting guidelines. For instance, comparing a postal code to a list

15 | P a g e
of legitimate codes makes it simpler to confirm if it is valid. Other elements like country
codes and NAICS industry codes can be used in the same way. (Taylor, 2023)

3.Range Check

The results of a range check will show whether the input data falls inside a particular
range. Latitude and longitude, for instance, are frequently employed in geographic data.
The range for a latitude value is from -90 to 90, while the range for a longitude value is
from -180 to 180. Outside of this range, any values are invalid. (Taylor, 2023)

4. Format Check

Several data kinds adhere to a predetermined format. Date columns with a set format,
such as "YYYY-MM-DD" or "DD-MM-YYYY," are a frequent use case. Maintaining
consistency over time and across data is made easier by a data validation process that
makes sure dates are formatted correctly. (Taylor, 2023)

5. Consistency Check

A logical check called a consistency check verifies that the data was entered in a way
that is logically consistent. (Taylor, 2023)

6. Uniqueness Check

Certain information, like IDs or email addresses, is by definition unique. These fields in
a database should presumably all have unique entries. A uniqueness check makes sure
that an item is not added to a database more than once. (Taylor, 2023)

Evaluation of the effectiveness of the ERD and Logical design in terms of the
identified user and system requirements

The ERD and the logical design should be an output that is properly normalized for a
database to be accurate and effective. The ERD and logical design of the database
should be based on user and system requirements for it to be effective and helpful.
Hence, user and system needs are fully responsible for the effectiveness of ERD and

16 | P a g e
logical design. Developing the design in accordance with the user and system
requirements satisfies the client, making it a custom creation that works for queit attic
films. While the efficacy of the database is increased by the custom design, the
produced database's accuracy and performance are also improved. The database's
security is also improved. Consequently, in order to develop an efficient and effective
database, the ERD and logical design must be created with user and system needs that
are realistic.

2.1 Data Definition Language (DDL)

Defines "Data Definition Language." A language called a DDL is used to specify data
structures and change data. For instance, tables in a database can be added, removed, or
modified using DDL commands. DDLs are regarded as a subset of SQL, or Structured
Query Language, which is utilized in database applications. However a DDL may also
specify different kinds of data, like XML. The syntax for describing data in a data
definition language is predetermined. The CREATE command is used to create a new
table, For example, to build a new table using SQL syntax, the CREATE command is
used, followed by parameters for the table name and column definitions. Each column's
name and related data type can also be specified in the DDL. The ALTER command can
be used to change a table after it has been created. The DROP command can be used to
eliminate a table if it is no longer required.

2.2 Developing a relational database system using SQL DDL

statements according to the ER diagram

Creating and call the Database

17 | P a g e
 Create a table for Production

Create a table for Client

18 | P a g e
Create a table for Location

Create a table for Property

19 | P a g e
Create a table for Staff

Create a table for employee

20 | P a g e
2.3 Security Mechanisms

2.3.1 Database Security

Database security refers to the assortment of measures taken to build and protect the
confidentiality, integrity, and availability of databases.
Database security must safeguard and take care of the following:
- Data stored in the database.
- The database management system (DBMS)
- Applications related to it.
- The underlying hardware, the physical database server, and/or the virtual database
server.
- The database accessing computer and/or network infrastructure.

21 | P a g e
Including all parts of information security technology and practices, database security is
a challenging task. Also, it fundamentally interferes with databases' usefulness. The ease
of access and use affects a database's security; the easier it is to use and access, the more
susceptible it is to security issues. (IBM, 2022).
Importance of database security.
By definition, a data breach occurs when the confidentiality of data in a database is
violated. The effect of a data breach on your company's bottom line will differ
depending on a range of results or factors:
Intellectual property that has been compromised
The ability to protect intellectual property, such as trade secrets, inventions, and
proprietary processes, may be necessary to sustain a competitive advantage in the market.
If that intellectual property is stolen or compromised, maintaining competitive advantages
may be difficult or impossible.
Penalties or fines for failing to comply
Failure to comply with global laws like the Sarbannes-Oxley Act (SAO) or Payment Card
Industry Data Security Standard (PCI DSS), industry-specific laws like HIPAA, or
regional laws like Europe's General Data Protection Regulation (GDPR) can have
catastrophic financial repercussions, with fines in the worst cases exceeding several
million dollars per violation.
Repair and customer notification expenses
In addition to the expense of telling customers about the breach, a breached firm must also
pay for forensic and investigation operations, crisis management, triage, repair of the
compromised systems, and other costs. (IBM, 2022).
Database security and threats
Data security must come first in every database system. It is extremely important in
distributed systems because of the huge number of users, fragmented and replicated data,
numerous sites, and dispersed control.
Availability loss
Loss of availability is the inability of authorized users to access database items.
Integrity loss
When the database is subjected to unacceptable operations, whether on purpose or
accidentally, integrity loss occurs. This might happen whenever new data is created,
updated, deleted, or added. Decisions are thus made using flawed data.

22 | P a g e
Confidentiality loss
When private information is mistakenly or accidentally revealed, confidentiality is lost.
There could be unethical behavior, threats to national security, and a deterioration in
public confidence. (tutorialspoint, 2022).
Measures of control
The following categories provide a broad division of the control measures:
Access Control
Access control includes the security components of a database management system that
prevent unauthorized access. After logged in, a user can only access the database using
verified user accounts. Each user account has a password to protect it.
Flow control
Distributed systems heavily rely on data transfer both inside and between nodes. Flow
control prevents the transfer of data, preventing unwanted parties from gaining access to
it. A flow policy lists the possible channels through which information may be
transmitted. It also specifies several levels of security for both data and transactions.
Data Encryption
When sensitive information needs to be communicated over a public network, it is
necessary to encrypt the data. Even if the unauthorised agent were to gain access to the
material, the format prevents him from understanding it. (tutorialspoint, 2022).

2.4 Database Maintenance

A group of actions are conducted as part of database maintenance to ensure that a

database operates properly. Database management systems like Oracle and SQL Server
require frequent updates to remain abreast of new security threats and technological
advancements.
Backups, data export/import operations, index reviews, object autoruns or removals, and
other database maintenance processes are a few examples of database maintenance
actions.
While database backups are well acknowledged, database maintenance is less well-
known. Your data is kept secure by a number of database maintenance operations.
One kind of database task is data exporting and importing. This is crucial because it
makes it possible for you to fix issues that have damaged your systems, such as data

23 | P a g e
corruption or hardware failures. You can use it to backup or transfer some of your
database to a different system. (Odogwu, 2023).
Database maintenance consist of four routines. They are,
1. Index defragmentation
Each table in your Office Tools Professional database contains at least one indexed
column. Indexes are used to store a sorted and partitioned version of that data in a
very short area of memory. The performance of a query can be increased by up to
1,000 times with a well-designed (and well-maintained) index..
2. Log file maintenance
Log files are important system components that require special maintenance as well.
A database can be restored to any previous point in time using these log files. Log
files automatically grow as new data is added to your database.
3. File Data Compaction
When you use your database, its file size grows and shrinks. Every time the file
needs extra space, a certain amount is added to it. As information is entered into the
database, it is saved in any location that has enough memory for that chunk (as a
chunk). Similar to the indexes we previously covered, the data itself is broken up.
4. Integrity Check
The Integrity Check, which can discover and correct the majority of corruption it
encounters, thoroughly examines the whole database. When a corruption is
discovered or rectified, WorkSpace immediately notifies the user of the details,
severity, and steps taken. Our data specialists have successfully recovered data that
was previously thought to be completely unrecoverable (Officetools, 2021).

2.5 Usage of SQL statements

SELECT
The SELECT statement is used to select records from the table, with or without a
condition.

24 | P a g e
WHERE
WHERE statement is used to extract only those records that fulfil a specified condition.

25 | P a g e
UPDATE
The UPDATE statement is used to update existing values in a table, which is based on
some condition

BETWEEN
The BETWEEN operator selects values within a given range. The values can be numbers,
text, or dates.

26 | P a g e
IN
The IN operator allows you to specify multiple values in a WHERE clause. The IN
operator is a shorthand for multiple OR conditions.

GROUP BY
The GROUP BY statement is often used with aggregate functions (COUNT(), MAX(),
MIN(), SUM(), AVG()) to group the result-set by one or more columns.

27 | P a g e
ORDER BY
ORDER BY statement is need to sort your SQL result in database tables. We can use
ascending (ASC) and descending (DESC) for order records.

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

28 | P a g e
3.0 Test plan for quiet attic films
1. Log in to the quiet attic films system.
2. Insert new data into tables.
3. Update existing data in tables.
4. Delete existing data from tables.

4.0 Technical and user documentation for quiet attic films database
system

Technical Documentation
System Requirements:
- Processor: Minimum 1.4 GHz 64-bit processor. Recommended 2.0 GHz or faster
multi-core processor.
- Memory: Minimum of 2 GB RAM. Recommended 8 GB RAM or more.
- Hard Disk Space: Minimum of 6 GB of available hard disk space. Recommended
10 GB or more.
- Operating System: Windows 11, Windows 10, Windows 8.1
Overview:
- To store data, the desktop application is created with the.NET Framework and
SQL Server. The presentation layer, business layer, and data access layer are all
components of the application's three-tier design.
System Architecture:
- Presentation Layer: Windows Forms
- Business Layer: C#
- Data Access Layer: MS SQL Server
- Database schema: normalized schema with tables for production, client, staff,
location, employee, property
User Documentation
Installation Steps:
- Run the installation file and follow the on-screen instructions.
- Choose the installation directory.
- Select the components to install.
- Set the security options.

29 | P a g e
- Review and accept the license agreement.
- Complete the installation process.

Getting Started:
- To get started, open the desktop application and enter user name and password
provide by admin and login to the application. You will be taken to the main menu
after successful login. There you can access various features and functions of the
application.
Navigation:
You can use the following various sections of the desktop application:
I. Main Menu:
After successfully logging to the system, you directly move to the main
menu. In there you can choose various sections such as production, client,
staff, location, employee, property.
II. Production
When click the production button in the main menu you can access to the
production form, in there you can insert, update and delete all production
details related to quiet attic films.
III. Client
When click the client button in the main menu you can access to the client
form, in there you can insert, update and delete all client details related to
quiet attic films.
IV. Staff
When click the staff button in the main menu you can access to the staff
form, in there you can insert, update and delete all staff details related to
quiet attic films.
V. Location

30 | P a g e
 When click the location button in the main menu you can access to the
location form, in there you can insert, update and delete all location details
related to quiet attic films.
VI. Employee
When click the employee button in the main menu you can access to the
employee form, in there you can insert, update and delete all employee
details related to quiet attic films.

VII. Property
When click the property button in the main menu you can access to the
property form, in there you can insert, update and delete all property details
related to quiet attic films.

31 | P a g e
References
Banister, R., 2021. Physical Database Design. [Online]
Available at: https://sesamesoftware.com/white-papers/physical-database-
design/#:~:text=Physical%20database%20design%20is%20the,database%20manageme
nt%20system%20(DBMS).
[Accessed 04 03 2023].
databasetown, 2023. databasetown. [Online]
Available at: https://databasetown.com/object-oriented-database/
[Accessed 03 03 2023].
Elgabry, O., 2016. Database — Design: Logical Design. [Online]
Available at: https://medium.com/omarelgabrys-blog/database-modeling-logical-design-
part-6-af029e93cc1f
[Accessed 04 03 2023].
IBM, 2022. IBM. [Online]
Available at: https://www.ibm.com/cloud/learn/database-security
[Accessed 05 03 2023].
IBM, 2022. IBM. [Online]
Available at: https://www.ibm.com/cloud/learn/database-security
[Accessed 05 03 2023].
javatpoint., 2023. javatpoint.. [Online]
Available at: https://www.javatpoint.com/database-design
[Accessed 04 03 2023].
lucidchart., 2023. lucidchart.. [Online]
Available at: https://www.lucidchart.com/pages/database-diagram/database-models
[Accessed 03 03 2023].
microsoft, 2022. Description of the database normalization basics. [Online]
Available at: https://learn.microsoft.com/en-us/office/troubleshoot/access/database-
normalization-description
[Accessed 04 03 2023].
mongodb, 2023. mongodb. [Online]
Available at: https://www.mongodb.com/databases/non-relational
[Accessed 03 03 2023].

32 | P a g e
Odogwu, C., 2023. makeuseof. [Online]
Available at: https://www.makeuseof.com/what-is-database-maintenance/
[Accessed 05 03 2023].
Officetools, 2021. Officetools. [Online]
Available at: https://www.officetools.com/knowledgebase/database-maintenance-
explained/
[Accessed 05 03 2023].
oracle, 2023. oracle. [Online]
Available at: https://www.oracle.com/database/what-is-database/
[Accessed 03 03 2023].
oracle, 2023. oracle. [Online]
Available at: https://www.oracle.com/database/what-is-a-relational-database/
[Accessed 03 03 2023].
Pedamkar, P., 2023. Relational Database Advantages. [Online]
Available at: https://www.educba.com/relational-database-advantages/
[Accessed 03 03 2023].
Peterson, R., 2022. Relational Data Model in DBMS | Database Concepts & Example.
[Online]
Available at: https://www.guru99.com/relational-data-model-dbms.html
[Accessed 03 03 2023].
studytonight, 2023. DBMS Database Models. [Online]
Available at: https://www.studytonight.com/dbms/database-model.php
[Accessed 03 03 2023].
Taylor, S., 2023. Data Validation. [Online]
Available at: https://corporatefinanceinstitute.com/resources/data-science/data-
validation/
[Accessed 04 03 2023].
Taylor, S., 2023. Database. [Online]
Available at: https://corporatefinanceinstitute.com/resources/data-science/database/
[Accessed 03 03 2023].
THIRU, 2023. Conceptual Design in Database Design Process. [Online]
Available at: http://www.myreadingroom.co.in/notes-and-studymaterial/65-dbms/507-
conceptual-design.html
[Accessed 04 03 2023].
tutorialspoint, 2022. tutorialspoint. [Online]
Available at:
https://www.tutorialspoint.com/distributed_dbms/distributed_dbms_database_security_c
ryptography.htm
[Accessed 05 03 2023].

33 | P a g e
34 | P a g e