INTERNATIONAL SCHOOL OF

MANAGEMENT AND TECHNOLOGY

FACULTY OF COMPUTING

ASSIGNMENT COVER SHEET

This form is to be completed by students submitting assignments of level 4 and level 5.
Students are required to complete all sections and attach to your assignment.

STUDENT DETAILS

STUDENT NAME Rama Bhattarai

STUDENT ID [email protected]

UNIT AND ASSIGNMENT DETAILS

UNIT TITLE Unit 4: Database Design & Development

UNIT NUMBER A/618/7400

United Limited IT Systems
ASSIGNMENT
TITLE
22/03/2023
ISSUE DATE DUE DATE 04/06/2023

ASSESSOR Prasanna Regmi

NAME

ESTIMATED 5505
WORD LENGTH

SUBMISSION

HAND IN DATE
DECLERATION AND ACKNOWLEDGEMENT
When submitting assignments, each student must sign a declaration confirming
that the work is their own.

Plagiarism and Collusion

Plagiarism: to use or pass off as one’s own, the writings or ideas of another
without acknowledging or crediting the source from which the ideas are taken.

Collusion: submitting an assignment, project or report completed by another

person and passing it off as one’s.

In accordance with the Academic Integrity and Plagiarism Policy:

I declare that:
this assignment is entirely my own work, except where I have included fully-
documented references to the work of others,
the material contained in this assignment has not previously been submitted for
any other subject at the University or any other educational institution, except as
otherwise permitted,
no part of this assignment or product has been submitted by me in another
(previous or current) assessment, except where appropriately referenced, and with prior
permission from the Lecturer / Tutor / Unit Coordinator for this unit.

I acknowledge that:
if required to do so, I will provide an electronic copy of this assignment to the
assessor;
the assessor of this assignment may, for the purpose of assessing this assignment:
reproduce this assignment and provide a copy to another member of academic
staff;
communicate a copy of this assignment to a plagiarism checking service such as
Plagiarism Check (which may then retain a copy of this assignment on its database for
the purpose of future plagiarism checking).

I am aware of and understand that any breaches to the Academic Code of Conduct
will be investigated and sanctioned in accordance with the College Policy.

SIGNATURE [email protected] DATE

Contents
List of Figures..................................................................................................................................1
List of Table.....................................................................................................................................1
List of abbreviation..........................................................................................................................2
Introduction......................................................................................................................................3
Database...........................................................................................................................................3
User Requirements...........................................................................................................................4
System Requirements......................................................................................................................4
Database Administration tools:........................................................................................................4
Relational Database management system........................................................................................4
Entity Relationship Diagram...........................................................................................................5
Normalization..................................................................................................................................6
Data Validation................................................................................................................................6
Output Design..................................................................................................................................7
Interface Diagram............................................................................................................................7
System Design.................................................................................................................................7
Entity Relationship Diagrams (ERDs).............................................................................................7
Schema Diagram............................................................................................................................10
Data Dictionary..............................................................................................................................11
Help Desk Table............................................................................................................................11
Caller Table...................................................................................................................................11
Department Table..........................................................................................................................12
Problem Table................................................................................................................................13
Specialist Table..............................................................................................................................13
Software Table...............................................................................................................................14
System Requirements....................................................................................................................14
Conclusion.....................................................................................................................................14
Introduction....................................................................................................................................15
Integrated Development Environment...........................................................................................15
User Interface (UI).........................................................................................................................15
Login page.....................................................................................................................................15
Home Page.....................................................................................................................................17
Caller Details.................................................................................................................................20
For Add......................................................................................................................................20
For View........................................................................................................................................22
For search button...........................................................................................................................23
Problem Details.............................................................................................................................24
For Add button...........................................................................................................................25
For Search Button..........................................................................................................................28
For View....................................................................................................................................29
Software.....................................................................................................................................29
For Add......................................................................................................................................29
For view.....................................................................................................................................32
For Search..................................................................................................................................33
For Print.....................................................................................................................................34
For Specialist.................................................................................................................................35
For Add......................................................................................................................................35
For view.....................................................................................................................................36
For Search..................................................................................................................................37
For print.....................................................................................................................................38
Implementing RDBMS into the query language...........................................................................38
Data Definition Language (DDL...............................................................................................38
Data Manipulation Language (DML)........................................................................................38
Data Control Language (DCL)..................................................................................................39
Caller Details.................................................................................................................................39
Create Table...............................................................................................................................39
Insert Values in Table................................................................................................................39
Update Data...............................................................................................................................40
Delete Data................................................................................................................................40
Problem Details.............................................................................................................................41
Create Table...............................................................................................................................41
Insert Values in Table................................................................................................................41
Update Data...............................................................................................................................41
Delete Data....................................................................................................................................42
Software Details.............................................................................................................................43
Create table................................................................................................................................43
Insert Values in Table................................................................................................................43
Update Data...............................................................................................................................43
Delete Data................................................................................................................................44
Specialist........................................................................................................................................45
Create table....................................................................................................................................45
Insert Values in table.................................................................................................................45
Update Data...............................................................................................................................45
Delete Data................................................................................................................................46
Testing...........................................................................................................................................47
Types of Testing............................................................................................................................47
Functional Testing.....................................................................................................................47
Unit Testing...............................................................................................................................47
Integration Testing.....................................................................................................................47
Stress Testing.............................................................................................................................48
White Box Testing.....................................................................................................................48
Black Box Testing.....................................................................................................................48
Black Box Testing in Login Form.................................................................................................49
White box Testing in Login Form.................................................................................................51
Technical Documentation..............................................................................................................52
Data Dictionary of my application................................................................................................52
ER Diagram of my application......................................................................................................55
Schema Diagram............................................................................................................................56
Algorithm of my application.........................................................................................................57
Conclusion.....................................................................................................................................71
References......................................................................................................................................72
Database

List of Figures
Figure 1 Database............................................................................................................................3
Figure 2 Data Validation.................................................................................................................7
Figure 3 ER Diagram.......................................................................................................................8
Figure 4 Schema Diagram.............................................................................................................10

List of Table
Table 1 Help Desk table................................................................................................................11
Table 2 Caller Table......................................................................................................................12
Table 3 Department Table.............................................................................................................12
Table 4 Problem Table...................................................................................................................13
Table 5 Specialist Table.................................................................................................................13
Table 6 Software Table..................................................................................................................14

Rama Bhattarai (1st Semester) 1

Database

List of abbreviation
ER diagram:

IDE:

Rama Bhattarai (1st Semester) 2

Database

Introduction
United Limited is a well-established real estate company that provides a wide extend of
proficient administrations, counting improvement of raw land, property administration,
brokerages, loaning, and other administrations. As the company proceeds to extend, it has
distinguished to build up an IT Helpdesk to handle equipment and computer program issues
concerning the IT frameworks. The Helpdesk will be responsible for logging and following
inquiries and guaranteeing that helpdesk pros are adequately resourced to illuminate issues in a
satisfactory time. The aim of this proposal is to create a completely useful plan of the social
database for the IT helpdesk framework, counting client framework necessities, ERDs,
normalization, data validation, output designs, and interface diagrams.

Database
A database is an organized collection of data that can be maintained, accessed, modified and
updated with the help of a database management system (DBMS). A DBMS allows users to
generate and control a database, and it facilitates users in performing operations like creating,
reading, updating, and deleting data within the database. It grants physical and logical
independence from data, controls and restricts access to the database, and offers varying
perspectives of the data to meet the needs of different users. Databases are classified according to
how data is stored and retrieved (Olawanle, 2023).

Figure 1 Database

Rama Bhattarai (1st Semester) 3

Database

User Requirements
 All employees should be able to operate easily with the IT helpdesk irrespective of their
technical skills.
 A centrally located database should be accessible through the system to maintain records
of client inquiries and their current condition.
 Users should be able to evaluate the guidance they received and provide feedback to the
system
 Any device, including desktops, laptops and cell phones, should be liable to access the
system.

System Requirements
System requirements are essential in software development, serving as a basis for designing,
developing, and deploying solutions. They give a clear idea of what the system should do and
which hardware, software, and networking infrastructure will be required to get it to work
properly. The IT helpdesk has set the various system requirements which comprises of following
components

Database Administration tools:

Database administration tools are software applications with a user-friendly graphical or web
interface that automate numerous database work such as searching for tables, altering data, and
performing other operations on a database that non-programmer may wish to accomplish. The
major purpose of these tools is to make it easier for people to interact with databases. MySQL
Workbench, SQL Server Management Studio and phpMyAdmin are a few examples. They let
users to construct new databases graphically, examine existing ones, track data logical linkages,
and manage user accounts. They also include a SQL editor, which lets users to develop and run
scripts while building, editing, and deleting tables and other database objects (Cooper, 2023).

Relational Database management system

A relational database management system (RDBMS) is a software system which facilitates the
user to create, define, maintain and management of relational databases. Data is stored in the
form of tables, and most commercial RDBMS options come with the option of using Structured
Query Language (SQL) to query and manage the database. It consists of tools and features that
allow users to interact with a relational database. RDBMS is widely used in the disciplines such

Rama Bhattarai (1st Semester) 4

Database

as manufacturing, finance, aviation, and human resources to assure data protection, consistency,
correctness, and integrity (Atzeni, 1993).

Entity Relationship Diagram

An Entity Relationship Diagram (ERD) is a visual representation, similar to a flowchart, of the
relationships and linkages between various entities, objects, or concepts within a system. ERDs
employ symbols like diamonds, rectangles, ovals, and connecting lines to show how entities,
relationships, and their properties are linked. ERDs are useful since they serve as a starting point
for developing a database and can aid in determining the needs of an organization's information
system. ERDs may be created using multiple models, such as a conceptual data model, and can
be used to establish an information system's conceptual data model (Li & Chen, 2009).

The components of ER diagram are

Entity

Entities are visualized using rectangles that are named after the entity set, they represent. It refers
to the unique object or data which could be physical existence or something with conceptual
existence (Li & Chen, 2009).

Attributes

The attributes are the characteristics or features of an entity. Ellipse are utilized for symbolizing
attributes. Each ellipse denotes one attribute and has a connection to its corresponding rectangle-
based object (Li & Chen, 2009).

Four different sorts of attributes in data model are

Key attribute - Key attributes are unique types of attributes that serve as an entity's primary key
and may be utilized to differentiate one entity from another in an entity collection. Key attributes
must store distinct, non-repeating values (Li & Chen, 2009).

Composite attribute - Two or more basic attributes combine to constitute composite attributes.
It is displayed as an ellipse, which is bound to other ellipses by another ellipse (Li & Chen,
2009).

Multivalued Attribute- A multivalued attribute is one that has more than one possible value.
An ER Diagram indicates it with double ovals. It is frequently used to hold details on the
connections between entities. As an example, the phone number property has multivalued
attribute. Hierarchical data can also be represented by multivalued characteristics (Li & Chen,
2009).

Rama Bhattarai (1st Semester) 5

 Database

Derived Attribute- They are calculated or determined based on other attributes and aren’t
physically stored as data values (Li & Chen, 2009).

Relationships

A link that exists between two or more tables permitting data to be accessed or altered between
the tables is database relationships. Diamond-shaped boxes signify relationships. Inside the
diamond-box is put the name of the connection. A line connects all of the entities (rectangles)
involved in a relationship.

The different relationships are given below

 One- to-one
 One-to-many
 Many-to-one
 Many-to-many

Normalization

Normalization is a database design technique that eliminates data redundancy and prevents
undesired features such as Insertion, Update, and Deletion Anomalies. The objective of
normalization is to break down large tables into smaller tables and link them by relationships.
This helps to reduce the amount of repeated data and ensure that the data is kept in an
appropriate order. Normalization rules are classified into following types (Javatpoint, 2021)

 First Normal Form(1NF)

 Second Normal Form(2NF)
 Third Normal Form(3NF)

Data Validation
The process of inspecting and verifying data before it is utilized is known as data validation. In
order to attain correct outcomes, every form of data handling operation, whether it is obtaining
data, evaluating it, or scheduling it for display, necessitates data validation. It could be tempting
to skip validation since it takes time. However, it is an indispensable phase to accomplish the
finest outcomes possible (Informatica, 2023).

Rama Bhattarai (1st Semester) 6

Figure 2 Data Validation

Database

Output Design
The process of defining the sort of outputs required and creating the requisite output controls and
prototype report layouts is referred to as output design. It is the most primary and basic source
of details for the user. It entails developing drawings, specifications, and production instructions
that specify all of the components, parts, and pieces that go into a product device (Informatica,
2023).

Interface Diagram
Interface diagrams are visualizations of the interaction between several components or systems.
The association of various system elements, such as the data flow between the database, the user
interface, and additional systems that could be connected with the helpdesk system, can also be
shown using interface diagrams. It can be used to upgrade the overall system design and enhance
its versability. In the context of IT help desk system, interface design can be used to portray the
relationship between the user and system requirements (interaction-design.org, 2016).

System Design
The system design for the IT help desk based on the Help Desk scenario is described below

Entity Relationship Diagrams (ERDs)

An Entity Relationship Diagram (ERD) is a visual representation, similar to a flowchart, of the
relationships and linkages between various entities, objects, or concepts within a system.

Based on the Help Desk scenario the ER diagram is shown below

Rama Bhattarai (1st Semester) 7

Database

Figure 3 ER Diagram

According to the system requirements I have designed the ER diagram which consists of various
entities such as Helpdesk, Client, Department, Problem, and Specialist.

The entity used and their attributes are

Helpdesk Entity- The attributes for the helpdesk includes HID, HName, Software/OS Computer
ID, ProblemID. HID is considered as the primary key which is the unique identifier. HName is
considered as the composite attribute which has the first name and last name. ProblemID is the
foreign key. Each helpdesk can handle multiple clients, departments and problems. So, it has the
1:M relationships with these entities

Caller Entity- The attributes for the client includes Caller ID, CName, Email, Caddress, Date of
Call, Phone number, Job title. Caller ID is considered as the primary key. Caller Name is the
composite attribute. Phone number is multivalued attributes.

Department Entity- The DepartmentID is the primary key and there is a one-to-many relationship
between the department and the specialists since a department can have multiple specialists
assigned to it.

Rama Bhattarai (1st Semester) 8

Database

Problem- It has problem type, problem details, complain name and complain number, Resolved
Date. Problem ID is considered as the primary key.

Specialist Entity – This entity contains characteristics such as the Specialist Id, Name, Workload,
Location and Contact Number.

Software Entity- This entity includes attributes like Software ID, Software Name, Version,
License and date of manufacture.

Rama Bhattarai (1st Semester) 9

Database

Schema Diagram

Figure 4 Schema Diagram

Rama Bhattarai (1st Semester) 10

Database

Data Dictionary
Data dictionaries contain and convey metadata regarding information stored within a database, a
system, or data utilized by applications. For a dataset, data dictionary serves as a reference
manual. A data dictionary's primary objective is to assist data teams comprehend the data assets.
Data administrators, analysts, and engineers implement a data dictionary to fully understand and
trust data assets (Singh, 2022).

A data dictionary providing a comprehensive overview of the characteristics of the Help Desk
database tables is available.

Help Desk Table

Table Name Field Name Data Type Field Size Constraint Description

Help Desk ID int Primary Key Help Desk Id

Help Desk Computer ID int Computer ID

Help Desk Operating varchar 30 Operating System

System of Help Desk

Help Desk Problem ID int Foreign Key Problem ID as

foreign key

Table 1 Help Desk table

Caller Table
Table Name Field Name Data Type Field Size Constraint Description

Caller ID int Primary Key Client ID

Rama Bhattarai (1st Semester) 11

Database

Caller Date of Call int date that the

client has
called
Caller Name Varchar 30 Name of the
client

Caller Email Varchar 30 email of the

client

Caller Phone int Phone

Number of
clients
Caller Job Title varchar 30

Caller Department int Foreign Key Department

Id ID as foreign
key

Table 2 Caller Table

Department Table
Table Name Field Name Data Type Field Size Constraint Description

Department ID Int Primary Key ID of the

department as
the unique
identifier
Department Name varchar 30 Name of the
department

Department Problem varchar 30 Foreign Key Problem

Type Type as
foreign key
Table 3 Department Table

Rama Bhattarai (1st Semester) 12

Database

Problem Table
Table Name Field Name Data Type Field Size Constraint Description

Problem ID Int Primary Key Problem ID

as the
primary key
Problem Problem type Varchar 30 Type of
Problem
which client
want to
addressed
Problem Complain Varchar 30 The name of
Name the complain

Problem Resolved The date

Date when the
problem
being
resolved
Problem Complain The numbers
Number of complain
being
addressed
Table 4 Problem Table

Specialist Table
Table Name Field Name Data Type Field Size Constraint Description
Specialist Specialist ID int Primary key ID of
specialist
Specialist Name varchar 30 Name of
Specialist

Specialist Address int Address of

specialist is
stored
Specialist Work Load int Work load of
specialist
Specialist Phone int Phone
Number Number is
stored
Table 5 Specialist Table

Rama Bhattarai (1st Semester) 13

Database

Software Table
Table Name Field Name Data Type Field Size Constraint Description

Software Software Id int Primary key ID is

considered as
the primary
key
Software Software varchar 30 Name of the
Name software used

Software License varchar 30 License of

the software
Software Version int The version
of software
used
Software Date of int Manufactured
manufacture date
Table 6 Software Table

System Requirements
I used XAMMP, Apache NetBeans 15 and SQL Server 2021 to bolster the performance of my
application. I wrote the basic framework and design with Java programming language. SQL was
used for the back-end of the application, dealing with data storage and access, while Apache
NetBeans used for the front-end, mainly focusing on the user interface. Both elements have a
significant role and are equally responsible for the success of my application.

Conclusion
Ultimately, we constructed a relational database system that satisfies the wants and requirements
of both the user and the system. The database is comprised of up of four interconnected tables
that were put together with by means of proper design tools and methodologies. The database
tables were designed to appropriately captivate the entities and relationships involved, and the
user requirements were carefully evaluated. During the design phase, system needs such as data
integrity, consistency, and performance were additionally taken into account.

Rama Bhattarai (1st Semester) 14

Database

Introduction
Our extensive database system has been developed to organize and address assistance and
guidance needs in an effective manner. This system strengthens productivity and generates an
effortless user experience with a user-friendly interface, data validation, secure architecture, and
extensive querying capabilities. Ticket administration, customer information storage, query
response, and data analysis are all part of it. Security safeguards sensitive data, while
maintainability provides long-term viability and flexibility. Using the Help Desk System, you
can streamline support operations, enhance response times, and maintain high customer
satisfaction. The query language is also implemented in relational database system.

Integrated Development Environment

Integrated development environments, commonly known as IDEs, provide a comprehensive set
of software development tools for developers and programmers. IDEs are designed to eliminate
any difficulties when creating applications for particular platforms. They are often used by teams
when developing new software, and are frequently referred to as GUI-based workbenches. This
is due to their aim of making the development of software easier by providing an integrated
environment that has all the necessary tools (Redhat, 2019).

I've been using Apache NetBeans as my IDE. It's really convenient to get started with, as it's easy
to use and works well with other tools. It has great features, like debugging, code completion,
integration, and support for multiple programming languages.

User Interface (UI)

User interface (UI) refers to any technique or approaches that are utilized when a product's
ultimate user interacts with or manages a product, piece of software, or hardware. A good user
interface should make communicating with the user and the product as straightforward, simple
and pleasurable as possible. User interface is intended to allow individuals to supervise machines
effectively and efficiently. In my case, I created a graphical user interface for my program. The
form includes Login Page, Home Page, Software, Caller, Problem Details and Specialist
(interaction-design.org, 2016).

Login page
In Login Page, if we enter incorrect credentials i.e., Username and Password then, we cannot
access the other page. We cannot enter inside the main page. Login will be successful if the
credentials you enter is correct. The data validations are also applied over here. I have shown the
login page and the code for the successful login below.

Rama Bhattarai (1st Semester) 15

Database

Rama Bhattarai (1st Semester) 16

Database

Home Page
I have included caller information, problem details, software, and specific data for the homepage
so that we can have access the relevant fields.

Rama Bhattarai (1st Semester) 17

Database

Rama Bhattarai (1st Semester) 18

Database

Rama Bhattarai (1st Semester) 19

Database

Caller Details
Initially the details must be added and you will see the data inserted successfully.

For Add

Rama Bhattarai (1st Semester) 20

Database

Rama Bhattarai (1st Semester) 21

Database

For View
The below provided information about the caller’s is provided when we click the view button.

Rama Bhattarai (1st Semester) 22

Database

For search button

We can type the numbers in the search box and view the results given below

Rama Bhattarai (1st Semester) 23

Database

Problem Details
Like the caller’s details it also contains the add, update and search button. The code is given
below:

Rama Bhattarai (1st Semester) 24

Database

For Add button

Rama Bhattarai (1st Semester) 25

Database

Rama Bhattarai (1st Semester) 26

Database

For print

Rama Bhattarai (1st Semester) 27

Database

For Search Button

We have to type the number in the search button to view the information

Rama Bhattarai (1st Semester) 28

Database

For View

Software
For Add

Rama Bhattarai (1st Semester) 29

Database

Rama Bhattarai (1st Semester) 30

Database

Rama Bhattarai (1st Semester) 31

Database

For view
We can view the details we inserted into the table

Rama Bhattarai (1st Semester) 32

Database

For Search
We can search by entering the numbers

Rama Bhattarai (1st Semester) 33

Database

For Print

Rama Bhattarai (1st Semester) 34

Database

For Specialist
For Add

Rama Bhattarai (1st Semester) 35

Database

For view

Rama Bhattarai (1st Semester) 36

Database

For Search

Rama Bhattarai (1st Semester) 37

Database

For print

Implementing RDBMS into the query language

Data Definition Language (DDL)

A data definition language (DDL) is a type of programming language that is used for developing
and modifying the arrangement of databases items. Views, schemas, tables, and indexes are
examples of such objects in a database. Data Definition Language outlines the fields and records
in a database table, defining primary key and field of the table. The commands of DDL includes
create, drop, alter and truncate (Scaler, 2022).

Data Manipulation Language (DML)

A DML (data manipulation language) is a computer programming language capable of enabling
users to insert (add), remove (delete), and modify (update) data in a database. A DML frequently

Rama Bhattarai (1st Semester) 38

Database

refers to a sublanguage of an overall database language, such as SQL, which incorporates several
of the language's operators. A DML (data manipulation language) is an association of
programming languages capable of providing guidelines for altering data in databases. The
commands include insert, update and delete (Scaler, 2022).

Data Control Language (DCL)

For entering the stored data, data control language (DCL) is being used. It is mostly used to
revoke and permit a user access to a database. This language lacks the rollback mechanism in the
database. The commands of DCL includes grant and revoke (Scaler, 2022).

Caller Details
Create Table

Insert Values in Table

Rama Bhattarai (1st Semester) 39

Database

Update Data

Delete Data

Rama Bhattarai (1st Semester) 40

Database

Problem Details
Create Table

Insert Values in Table

Update Data

Rama Bhattarai (1st Semester) 41

Database

Delete Data

Rama Bhattarai (1st Semester) 42

Database

Software Details
Create table

Insert Values in Table

Update Data

Rama Bhattarai (1st Semester) 43

Database

Delete Data

Rama Bhattarai (1st Semester) 44

Database

Specialist

Create table

Insert Values in table

Update Data

Rama Bhattarai (1st Semester) 45

Database

Delete Data

Rama Bhattarai (1st Semester) 46

Database

Testing
Testing is a method of assessing the performance of a software program to make sure that it
meets all the specified requirements and is free of any errors. The intention is to guarantee that
the end product is of top quality. Testing is a method of evaluating a software product or system
in order to assess its dependability, security, and performance. It involves assessing the
software's characteristics for any missing requirements, bugs, or errors so as to ascertain that it
fulfills the set conditions. The purpose of software testing is to locate errors, or missing
objectives in comparison to the actual requirements (Ibm, 2016).

Types of Testing
Functional Testing
Functional Testing is a sort of software testing that is performed to check if the functionality of a
software program, and to determine if the function continues to function in accordance to the
requirements. Each function is reviewed in functional testing by offering the value, estimating
the output, and then comparing the actual output to the expected value. Functional testing has
been described as black-box testing as a means of confirming that an application's or system's
functionality is operating as expected. It is done in order to verify that the software works
properly. The overall objective of functional testing is making sure that the key entry function,
which must be useful, including the flow of the screen GUI have all been performing correctly.
The error message occurs during functional testing so that the individual using it could simply
navigate through the application (Ibm, 2016).

Unit Testing
Unit testing involves checking every individual part or section of a software program. It is the
very initial step of functional testing. The main goal of unit testing is to evaluate the functionality
of the unit components. The main goal of unit testing is to validate that individual software
programs are working accurately. White box testing is regularly employed for unit testing and is
typically done by developers. Unit tests are normally automated and are aimed at verifying
particular components of code, such as a certain feature or procedure. Unit testing is done at the
most basic level of the software development process, in which single parts of the code are tested
separately. Unit testing promotes testers and developers become familiar with the foundation of
code, offering them to immediately update defect-causing code. Unit testing is helpful while
creating documentation (Ibm, 2016).

Integration Testing
Integration testing is the second step in the software testing process, following unit testing. Units
or different components of the software undergo evaluation collectively during this testing. The
integration testing is to detect defects through the interaction of integrated components or units.
This testing's primary job or goal is to verify the connections between the units/modules.
Integration testing involves inspecting multiple integrated systems in order to make sure that all

Rama Bhattarai (1st Semester) 47

Database

of them run successfully. Not only should the integration interfaces be examined, but the whole
integrated system needs to be reviewed considering into consideration the environment (Ibm,
2016).

Stress Testing
Stress testing is a significant component of performance testing in non-functional software
testing Stress testing is used to evaluate the reliability and robustness of software, beyond normal
operational boundaries. It is primarily intended for important software, although it may be
applied to any form of software application. Endurance testing, fatigue testing, and torture testing
are other names for it (Ibm, 2016).

White Box Testing

White box testing, also known as glass box, structural, clear box, open box, or transparent box
testing, is focused on the internal coding and infrastructure of a software. It involves checking
predefined inputs against expected and desired outputs. This type of testing requires
programming skills to design test cases and its primary goal is to ensure the flow of inputs and
outputs are secure. White box testing requires an examination of the internal structure of the
code. By understanding the internal workings of a product, tests can be conducted to make sure
that the internal operations are being executed as intended and that all of the internal components
have been properly tested (Ibm, 2016).

Black Box Testing

Black box testing involves examining a system with no previous understanding of its internal
functioning. A tester supplies the necessary inputs and observes the output the system generates.
This will allow you to identify how the system behaves to expected and unexpected actions by
users, including its reaction time, usability problems, and reliability issues. The tester selects a
function and inputs a value to check if it works correctly. If the output is accurate, the test team
will pass it, otherwise it will fail. After this, they report the outcome to the development team
and go on to examine the next function. If there are major problems after all the functions have
been tested, it is sent back to the development team to be remedied (Ibm, 2016).

Rama Bhattarai (1st Semester) 48

Database

Black Box Testing in Login Form

Login failed due to the invalid username and password

Login failed due to the blank in the password field

Rama Bhattarai (1st Semester) 49

Database

Login failed due to the blank in the username box

Rama Bhattarai (1st Semester) 50

Database

White box Testing in Login Form

Rama Bhattarai (1st Semester) 51

Database

Technical Documentation
Technical documentation may occur in numerous forms, but the primary objective is to provide
clarification on your product's features and functioning. Details regarding product roadmaps and
targets, the software layout, methodology for design, and scheduled applications are all
mentioned.

Data Dictionary of my application

Caller Table

Table Name Field Name Data Type Field Size Constraint Description

Caller ID int Primary Key Client ID

Caller Date of Call int date that the

client has
called
Caller Name Varchar 30 Name of the
client

Caller Email Varchar 30 email of the

client

Caller Phone int Phone

Number of
clients
Caller Job Title varchar 30

Caller Department int Foreign Key Department

Id ID as foreign
key

Rama Bhattarai (1st Semester) 52

Database

Department

Table Name Field Name Data Type Field Size Constraint Description

Department ID Int Primary Key ID of the

department as
the unique
identifier
Department Name varchar 30 Name of the
department

Department Problem varchar 30 Foreign Key Problem

Type Type as
foreign key

Problem

Table Name Field Name Data Type Field Size Constraint Description

Problem ID Int Primary Key Problem ID

as the
primary key
Problem Problem type Varchar 30 Type of
Problem
which client
want to
addressed
Problem Complain Varchar 30 The name of
Name the complain

Problem Resolved The date

Date when the
problem
being
resolved
Problem Complain The numbers
Number of complain
being
addressed

Rama Bhattarai (1st Semester) 53

Database

Specialist

Table Name Field Name Data Type Field Size Constraint Description
Specialist Specialist ID int Primary key ID of
specialist
Specialist Name varchar 30 Name of
Specialist

Specialist Address int Address of

specialist is
stored
Specialist Work Load int Work load of
specialist
Specialist Phone int Phone
Number Number is
stored

Software

Table Name Field Name Data Type Field Size Constraint Description

Software Software Id int Primary key ID is

considered as
the primary
key
Software Software varchar 30 Name of the
Name software used

Software License varchar 30 License of

the software
Software Version int The version
of software
used
Software Date of int Manufactured
manufacture date

Rama Bhattarai (1st Semester) 54

Database

ER Diagram of my application

Rama Bhattarai (1st Semester) 55

Database

Schema Diagram

Rama Bhattarai (1st Semester) 56

Database

Algorithm of my application
For Login Page

1. Start
2. Display the login page with input fields for username and password.
3. Accept the username and password entered by the user.
4. Validate the input fields to ensure they are not empty.
5. If the input fields are not empty, proceed to the next step.
6. Verify the username and password against the stored credentials in the database or any
other authentication mechanism.
7. If the credentials are valid, redirect the user to the main page or perform the desired
action.
8. If the credentials are invalid, display an error message.
9. End.

For Caller Details

1. Start
2. Declare the variables for name, doc, job title, email, CallerID, phone and department
3. Display an input field to capture the caller’s information
4. Accept the values
5. If all the input fields are valid, proceed to the next step
6. Insert the caller’s information
7. End

For Problem Details

1. Start
2. Declare the variables for problem_id, problem_name, description, problem_type
3. Display an input field to capture the problem’s information
4. Accept the values
5. If all the input fields are valid, proceed to the next step
6. Insert the problem’s information
7. End

For Software

1. Start
2. Declare the variables for software_id, software_name, version, license
3. Display an input field to capture the software’s information
4. Accept the values
5. If all the input fields are valid, proceed to the next step
6. Insert the software’s information

Rama Bhattarai (1st Semester) 57

Database

7. End
For Specialist

1. Start
2. Declare the variables for specialist _id, specialist_name and work_load
3. Display an input field to capture the specialist’s information
4. Accept the values
5. If all the input fields are valid, proceed to the next step
6. Insert the caller’s information
7. End

Flow Chart

Rama Bhattarai (1st Semester) 58

Database

User Documentation

User documentation provides your end user with the necessary information to understand and
use your product or service. It can help them learn the features and functions of your product, as
well as answer any questions they may have. User documentation can also serve as a reference
guide, helping customers quickly find solutions to common problems.

For login page

For home page

Rama Bhattarai (1st Semester) 59

Database

Rama Bhattarai (1st Semester) 60

Database

For Caller Details

For Add

Rama Bhattarai (1st Semester) 61

Database

Rama Bhattarai (1st Semester) 62

Database

For view

For search

Rama Bhattarai (1st Semester) 63

Database

For print

Rama Bhattarai (1st Semester) 64

Database

For Problem Details

For Add

For view

Rama Bhattarai (1st Semester) 65

Database

For search

Rama Bhattarai (1st Semester) 66

Database

For Software

For Add

For View

Rama Bhattarai (1st Semester) 67

Database

For Search

For print

Rama Bhattarai (1st Semester) 68

Database

Rama Bhattarai (1st Semester) 69

Database

For Specialist

For Add

Rama Bhattarai (1st Semester) 70

Database

For view

For Search

For Print

Rama Bhattarai (1st Semester) 71

Database

Conclusion
In conclusion, we were successful in developing technical and user documentation for the
database system. This documentation possesses all of the relevant facts and recommendations for
both technical personnel and end users. The technical documentation proposes an in-depth
explanation of the database system's architecture, structure, and implementation. This serves as
details concerning the database schema, table arrangements, linkages, constraints, and indexing
strategies. User documentation is designed to give end users clear instructions and assistance
when working with the database system. This includes user manuals, tutorials, and FAQs to help
users become familiar with the system's capabilities and features.

Rama Bhattarai (1st Semester) 72

Database

References
Atzeni, P. a. D. A. V., 1993. Relational database theory. 1 ed. s.l.:Benjamin-Cummings
Publishing Co., Inc..

Cooper, S., 2023. Comparitech.com. [Online]

Available at: https://www.comparitech.com/net-admin/database-management-tools-software/
[Accessed 06 05 2023].

Ibm, 2016. What is software testing?. [Online]

Available at: https://www.ibm.com/topics/software-testing
[Accessed 03 06 2023].

Informatica, 2023. What is Data Validation: Definition | Informatica. [Online]

Available at: https://www.informatica.com/services-and-training/glossary-of-terms/data-
validation-definition.html#:~:text=Data%20validation%20means%20checking%20the,a
%20form%20of%20data%20cleansing.
[Accessed 03 06 2023].

interaction-design.org, 2016. User Interface (UI) Design. [Online]

Available at: https://www.interaction-design.org/literature/topics/ui-design
[Accessed 03 06 2023].

Javatpoint, 2021. DBMS Normalization: 1NF, 2NF, 3NF and BCNF with Examples - javatpoint.
[Online]
Available at: https://www.javatpoint.com/dbms-normalization
[Accessed 03 06 2023].

Li, Q. & Chen, Y. L., 2009. Entity-relationship diagram. In: Springer, ed. Modeling and analysis
of enterprise and information systems. s.l.:Springer, pp. 125--139.

Olawanle, J., 2023. freeCodeCamp.org. [Online]

Available at: https://www.freecodecamp.org/news/what-is-sql-database-definition-for-beginners/
[Accessed 5 5 2023 ].

Redhat, 2019. What is an IDE?. [Online]

Available at: https://www.redhat.com/en/topics/middleware/what-is-ide
[Accessed 03 06 2023].

Scaler, 2022. What are DDL, DML, and DCL in SQL?. [Online]
Available at: https://www.scaler.com/topics/ddl-dml-dcl/
[Accessed 03 06 2023].

Rama Bhattarai (1st Semester) 73

Database

Singh, N., 2022. Data Dictionary in DBMS - Scaler Topics. [Online]

Available at: https://www.scaler.com/topics/data-dictionary-in-dbms/
[Accessed 03 06 2023].

Rama Bhattarai (1st Semester) 74