Assignment Cover Sheet

1|Page Database and Development
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 Dhirendra Yadav
STUDENT ID
UNIT AND ASSIGNMENT DETAILS
UNIT TITLE Database management systems
UNIT NUMBER
ASSIGNMENT TITLE United Limited IT Systems
29/05/2023
ISSUE DATE 30/03/2023 DUE DATE
ASSESSOR NAME Rajat Shakya
ESTIMATED WORD 10,000

LENGTH
SUBMISSION
HAND IN DATE 2023/06/08
DECLERATION AND ACKNOWLEDGEMENT

When submitting assignments, each student must sign a declaration confirming that the work is their
own.
Dhirendra Yadav 2023 1

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:
1. I declare that:
a) this assignment is entirely my own work, except where I have included fully-documented
references to the work of others,
b) 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,
c) 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.
2. I acknowledge that:
a) if required to do so, I will provide an electronic copy of this assignment to the assessor;
b) the assessor of this assignment may, for the purpose of assessing this assignment:
I. reproduce this assignment and provide a copy to another member of academic staff;
II. 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 Dhirendra yadav DATE 2023/06/08

Table of Contents
Database Management Systems:......................................................................................................................7
Features of DBMS:....................................................................................................................................8
Characteristics of DBMS..........................................................................................................................8
Advantages of DBMS...............................................................................................................................8
Disadvantages of DBMS...........................................................................................................................8
Purpose.............................................................................................................................................................9
Entity:.............................................................................................................................................................10
Attributes:.......................................................................................................................................................10
SQL (Structured Query Language)................................................................................................................11
ERD................................................................................................................................................................12
Relational Database Schema.......................................................................................................................13
Data Dictionary..............................................................................................................................................14
Interface Requirement....................................................................................................................................15
User Interface..............................................................................................................................................15
Hardware Interfaces....................................................................................................................................15
Software Interfaces.....................................................................................................................................15
Targets of my application...............................................................................................................................16
My application justification:..........................................................................................................................16
Data Validation..............................................................................................................................................16
1.Information type check:...........................................................................................................................16
2.Code Check:.............................................................................................................................................16
3.Check the range:......................................................................................................................................16
Normalization:................................................................................................................................................17
First normal form (1NF).............................................................................................................................17
Second normal form (2NF)............................................................................................................................18
The tables now adhere to the Second normal form....................................................................................19
Third Normal form (3NF):..........................................................................................................................19
Insert, Update, Delete Statement....................................................................................................................20
Insert Statement..........................................................................................................................................21
Update Statement........................................................................................................................................21
Delete Statement.........................................................................................................................................22
Data validation, output designs and interface diagrams evaluating the reasons that the design will meet the
requirements...................................................................................................................................................23
1.Login Screen............................................................................................................................................23

1.1Flowchart:...........................................................................................................................................23
1.2Output Design:...................................................................................................................................23
1.3 Data Dictionary/validation:...............................................................................................................24
2.Admin Screen..........................................................................................................................................24
2.1Flowchart:...........................................................................................................................................24
2.2Output Design:...................................................................................................................................25
2.3Use case diagram/ Interface diagram:................................................................................................25
3.User screen...............................................................................................................................................26
3.1 flowchart:..........................................................................................................................................26
3.2 Output design:...................................................................................................................................26
3.3Use case diagram/ Interface diagram:................................................................................................27
4.Registration page.....................................................................................................................................27
4.1 Flowchart...........................................................................................................................................27
4.2output Design.....................................................................................................................................28
4.3 Data Dictionary.................................................................................................................................28
4.4 Interface Diagram..............................................................................................................................29
5.Complaint generator page........................................................................................................................29
5.1 Flowchart...........................................................................................................................................29
5.2output Design.....................................................................................................................................30
5.3 Data Dictionary.................................................................................................................................30
5.4 Interface Diagram..............................................................................................................................31
Evaluation of effectiveness of the given design (ERD and Logical design) in terms of the identified user
and system requirements................................................................................................................................31
Detectability and Verification Process...........................................................................................................32
Implementation of System Security...............................................................................................................32
Database Security.......................................................................................................................................32
Why is it important.....................................................................................................................................33
What Is a SQL Injection Attack?................................................................................................................33
What Can Attackers Do with a SQL Injection Attack?..............................................................................33
Preventing SQL Injection Attacks..............................................................................................................33
Database maintenance....................................................................................................................................34
1.Index Defragmentation:...........................................................................................................................34
Indexes in SQL databases function similarly to a library's Dewey Decimal system. Each table in your
Office Tools Professional database has at least one indexed field that we use to locate a particular value
(such as an Employee or a Work Code). When you ask SQL Server for something specific, like "All time

cards for employee "Joe Demo," an index saves a sorted and partitioned copy of that data in an extremely
fast portion of memory...............................................................................................................................34
2. Log File Maintenance...........................................................................................................................34
3. File/Data Compaction.............................................................................................................................34
4. Integrity Check.......................................................................................................................................34
Query a system of relational databases..........................................................................................................35
1.DDL (Data Definition Language) :..........................................................................................................35
2.DQL (Data Query Language):.................................................................................................................35
3.DML (Data Manipulation Language):.....................................................................................................35
4.DCL (Data Control Language):...............................................................................................................36
Data flow diagram..........................................................................................................................................36
Data Flow Diagram........................................................................................................................................37
1.login.........................................................................................................................................................38
1.1User-Interface:....................................................................................................................................38
1.2Inputs:.................................................................................................................................................39
1.3Outputs:..............................................................................................................................................39
1.4Data validation:..................................................................................................................................40
1.5Query:.................................................................................................................................................40
1.6Code:..................................................................................................................................................40
2:user interface:..........................................................................................................................................41
3.admin Interface........................................................................................................................................42
4.Problem Report........................................................................................................................................43
4.1Interface:.............................................................................................................................................43
4.2Inputs:.................................................................................................................................................43
4.3Outputs:..............................................................................................................................................44
4.4Data validation:..................................................................................................................................44
4.5Query:.................................................................................................................................................44
Code:.......................................................................................................................................................45
5.User Registration.....................................................................................................................................46
5.1 Interface:............................................................................................................................................46
5.2 Inputs:................................................................................................................................................46
5.3 Outputs:.............................................................................................................................................47
5.4Data validation:..................................................................................................................................47
5.5 Query:................................................................................................................................................47
6.Running problems....................................................................................................................................48

6.1 Interface:............................................................................................................................................48
6.2 Inputs:................................................................................................................................................48
6.3 Outputs:.............................................................................................................................................49
6.5 Query:................................................................................................................................................49
6.6 Code:.................................................................................................................................................50
7.Specialist..................................................................................................................................................52
7.1 Interface:............................................................................................................................................52
7.2 Outputs:.............................................................................................................................................52
7.4 Query:................................................................................................................................................53
8.Solved Problems interface.......................................................................................................................54
9.Problem Types interface.......................................................................................................................54
10.codes used in the project........................................................................................................................55
Testing...........................................................................................................................................................57
White Box Testing:.....................................................................................................................................57
Black Box Testing:.....................................................................................................................................57
Test case and Test plan................................................................................................................................58
Scenario:.....................................................................................................................................................58
Scope:.........................................................................................................................................................58
Conclusion:.................................................................................................................................................58
Test Plan:........................................................................................................................................................60
Test case Name: Registration of users and Problem Report.....................................................................60
System: Helpdesk Operating System.........................................................................................................60
Design By: Dhirendra Yadav.....................................................................................................................60
Designed Date:2023/06/03........................................................................................................................60
Description: Adding of Problems, updating it to specialist, Deleting Solved Problems...........................60
Test case Name: Equipment Details..........................................................................................................61
Designed Date:2023/06/03........................................................................................................................61
Test case Name: Installation Details.........................................................................................................62
Designed Date:2023/06/03........................................................................................................................62

Test Case Name: DDL statements............................................................................................................63

System: Help Desk Management System..................................................................................................63
Design Date: 2023/06/03...........................................................................................................................63
Description: Execute database tables and get following results................................................................63
Test Case Name: DDL statements............................................................................................................64
System: Help Desk Management System..................................................................................................64
Design Date: 2023/06/03...........................................................................................................................64
Description: Every DML Query’s execute and get these messages..........................................................64
Allocating Feedbacks On the design:.............................................................................................................65
effective, extreme and erroneous data in order to build an accurate Application:.........................................66
Database Connection:.....................................................................................................................................67
Fetching Records:...........................................................................................................................................68
Steps that I have used to make data designing...............................................................................................70
1.Name the entities in the data....................................................................................................................70
2.Define connections..................................................................................................................................70
3.Standardize the information.....................................................................................................................70
4.Establish a data model.............................................................................................................................70
5.Select a database management application..............................................................................................70
6.Outline the structure................................................................................................................................70
7.Fill out the database.................................................................................................................................70
8.Examine the database..............................................................................................................................70
Testing the system against user and system requirements.............................................................................71
Report:............................................................................................................................................................72
Introduction.................................................................................................................................................73
Technical Literature:................................................................................................................................73
User Instruction:.......................................................................................................................................73
system overview: technical and user documentation for a fully functional system...................................73
Models for Data:.......................................................................................................................................74
Diagrams of Data Flow:...........................................................................................................................74
Flowcharts:.................................................................................................................................................74
Evaluation of the Database Assessing the database in terms of the enhancements required to maintain the
system's effectiveness.....................................................................................................................................74
Evaluation:..................................................................................................................................................75

Recommendations:.........................................................................................................................................76
Future enhancements......................................................................................................................................76
FUTURE IMPROVEMENT..........................................................................................................................76
References......................................................................................................................................................77
Database Management Systems: (javaTpoint, n.d.)

The system software used to create and administer databases is referred to as a database management
system (DBMSWith the aid of a DBMS, end users may create, protect, read, update, and remove data from
a database. A software program is used to administer databases, or database management systems. As an
illustration, prominent commercial databases like MySQL, Oracle, etc. are utilized in a variety of
applications. A DBMS provides an interface to carry out a variety of tasks, including building databases,
putting data in them, updating data, creating tables in the databases, and many other things. It offers the
database security and safety. Additionally, it preserves data integrity when there are many users.
Features of DBMS:
o Data Definition: It is used to create, modify, and remove definitions that specify how data is
organized in a database.
o Data Updating: The real data in the database is added, changed, and deleted using this method.
o Data Retrieval: It is used to extract data from databases that programs may use in a number of
different ways.
o User Administration: It is used to preserve data security, deal with concurrency management,
register and monitor users, maintain data integrity, track performance, and restore data that has been
compromised by unexpected failure.
Characteristics of DBMS
 The information is managed and stored using a server-based digital repository.
 It can give a clear and logical overview of the data manipulation process.
 Automatic backup and recovery processes are included in DBMS.
 It has ACID characteristics that, in the event of failure, keep data in a good condition.
 It can simplify the intricate interrelationship between data.
 It supports the processing and modification of data.
 It is employed to provide data security.

 Depending on the user's needs, it can see the database from a variety of angles.
Advantages of DBMS
o Controls database redundancy: Because it keeps all the data in a single database file and the
recorded data is stored in the database, it is able to regulate data redundancy.
o Data sharing: In DBMS, numerous users may share the data with the organization's authorized
users.
o Easily Maintenance: Because the database system is centralized, it can be readily maintained.
o Reduce time: It cuts down on maintenance and development time.
o Backup: It offers backup and recovery subsystems that automatically produce backup copies of
data in the event of hardware or software failures and restore the data as necessary.
o multiple user interface: It offers several user interface kinds, such as graphical user interfaces and
application program interfaces.
Disadvantages of DBMS
o Cost of Hardware and Software: To execute DBMS software, a fast data processor and plenty of
memory are needed.
o Size: To execute them effectively, it needs a lot of RAM and storage space.
o Complexity: The database system adds more needs and complexity.
o Higher impact of failure: Database failure has a significant impact since, in the majority of
organizations, all of the data is saved in a single database. If the database is destroyed due to an
electrical outage or database corruption, the data may be permanently lost.
The following list of database types is provided:

 NoSQL databases: Any database that doesn't employ SQL as its primary data access language falls
under the umbrella term known as NoSQL.
 Cloud databases.
 Columnar databases.
 Wide column databases.
 Object-oriented databases.
 Key-value databases.
 Hierarchical databases.
 Document databases.
 The many DBMS types are illustrated below:

 Oracle RDBMS.
 Salesforce.

10 | P a g e Database and Development
 DevOps.
 Visual Studio Code.
 ESM Tools.
 PhpMyAdmin.
Purpose
Managing the whole real estate firm that specializes in residential, commercial, and industrial properties is the project's
aim. Additionally, it handles and manages resources that were previously handled and controlled by staff. The project's
aims are as follows:
• Automated manipulation of the goods.

• Buying undeveloped land, managing real estate, engaging brokers, obtaining financing, and using other
expert services like those provided by architects, attorneys, and interior designers.
• To keep track of many types of data.
• Regularly update all item details.
• Keeping security under control by providing a valid email address and password.
• Effective database management.
Entity:
Any readily recognizable real-world object, whether it be living or inanimate, qualifies as an entity. Each of
these objects stands apart from the others thanks to special traits or characteristics.
Some entity sets do not need to be detached. In order to complete this project, an ecommerce database was
created, with the product name and price serving as the table's entities.
Attributes:
Entities are represented by their attributes, which are their characteristics. Each characteristic has a value.
For instance, a student object may include attributes like name, class, and age.
A domain, or range, of values can be assigned to an attribute. For instance, a student's name cannot be a
number. It must be arranged alphabetically.
Some Attributes of my system listed below:
 Caller Table
o Caller_Id
o Date
o Name
o Address

o time
 TicketsTable
o Ticket_name
o Ticket_code
o Quantity
o Ticket_price
o Discount
 User
o Username
o User_id
o Password
SQL (Structured Query Language)

SQL is the name of the language that is used to connect to databases. For systems that control relational
databases, it acts as the default language. Despite the fact that the majority of database systems employ
SQL, they typically additionally include their own, platform-specific, proprietary extensions.
The following four groups make up the majority of these SQL commands:
Data definition language, data query language, data manipulation language, and data control language are
all examples of programming languages.

ERD
Entity-relationship modeling, a crucial database design approach, is crucial to the modeling of information
systems. E-Rmodels are effective at capturing the key semantics of a variety of circumstances, as is
commonly acknowledged. Like any other conceptual model, the restricted expressiveness of this one is a
necessary trade-off for its formality, simplicity, and broad applicability. In fact, one of the most important
steps in the modeling process is to eliminate data that is unnecessary or outside the scope of the application
at hand. As a result, the E-Rmodel is lauded for offering a definite line between generality and expressive
capability that permits explanation. The E-Rmodel is recognized for drawing a distinct line between
generality and expressive capacity, beyond which it is easy to foresee deteriorating results.
ERD of my proposed system is shown below:

The main aims of utilizing ER-diagram
 Database design: ER diagrams are used to depict and construct relational databases, both in terms of
the precise technology to be used (in a physical data model) and the logic and business rules (in a
logical data model). An ER diagram is frequently used as the first step in the requirements creation
process for a software engineering information systems project. It is also used to later simulate a
specific database or databases. A relational database has a relational table equivalent, if necessary.
 Database troubleshooting: When you draw the diagram, you should be able to pinpoint the
problems.
• Business process re-engineering (BPR): ER diagrams are useful for modeling a new database
architecture as well as for analyzing databases used in BPR.
• Education: Relational data is kept in databases for retrieval and instructional uses; as a result, ER
Diagrams may be utilized to assist in the planning of such data structures.
• study: ER diagrams can assist in creating databases that are helpful for data analysis since
structured data is a trendy issue for study.
Relational Database Schema

A database's relational structure serves as a guide for how data should be arranged. Programmers utilize
diagrams or other charts to understand how each table is organized, including the columns and types of
data they hold as well as how tables link. An additional choice is SQL code.
The database structure usually specifies the primary key columns in tables and the restrictions imposed on
them, such as the demand that each record have a unique value. To identify which segments in which tables
have references to information in distinct data sets, it typically uses crucial keys from other table records,
which makes column joining simpler.

I'll presently go over the means we ought to take before we start fostering any applications. In order to
demonstrate the relationships between attributes and tables or entities, an ERD diagram of the application
must first be created. Both developers and non-programmers need to have access to properties that provide
them with useful data. A database system used to collect company data is depicted graphically in an ER
diagram. To illustrate the five entities and features of my application, I created an ER diagram.
Data Dictionary
A database, information system, or research project's data components' names, definitions, and
characteristics are listed in a data dictionary. It clarifies comprehension, recognised implications, and
depiction as well as the implications and goals of information components in relation to a task.
Data dictionaries are useful for a variety of reasons. To put it simply, they are:
 Help keep data inconsistencies at bay throughout a project.

 Contribute to the creation of project-wide conventions.
 Ensure that multiple study team members consistently collect and use data.
 Facilitate data analysis;
 Ensure that data standards are adhered to. (library.ucmerced.edu, 2020)

Interface Requirement
An interface is a common boundary in computing that allows two distinct components of a computer
system to exchange information. Software, computer hardware, people, and even combinations of these can
be swapped. Although certain computer hardware components, like a touchscreen, may be able to send and
receive data through the interface, a mouse or microphone may only provide an interface for transmitting
data to a specific system.
User Interface
 Login Screen
 Admin Screen
 User screen
 Specialist Page
 Problem Types Page
 Equipment page
 Registration page
 Resolved problem page
 Running problem page
 Complaint generator page
 Complaint progress page
Hardware Interfaces
 Hard drive minimum of 2GB for servers
 P-III processor or an equivalent;
 512 MB of RAM;
 Windows with Apache already installed.
 Configuring clients
Software Interfaces
 Operating system: Windows 11
 CSharp (C#) is the language
 MYSQL is the database.
Interfaces for Communication Various methods, including email, a web browser, network server
communications protocols, electronic forms, and others, can all be utilized as interfaces for
communication. We can use the synchronization and encryption features of communication protocols like
HTTP and FTP to accomplish this.

Targets of my application
The essential objectives of an application are to fulfill clients and stick to framework prerequisites. The
main objectives of my application are:
• To populate a database with all relevant information.
• To develop applications that permit the administrator to view and update user database data.
My application justification:
A data set application called "Joined Country" has been developed by me in light of the aforementioned
circumstance. In order to better comprehend my software and all of its entities and characteristics, I created
an ER diagram, a schema diagram, and a data dictionary before creating my application. Among other
programs, I've worked with SQL Server and Microsoft Visual Studio.
Data Validation
Making ensuring that data is accurate and dependable is the process of data validation. It is implemented by
including a number of tests in a system or report to guarantee the logical integrity of the data input and
saved. When inputting data, automated systems essentially don't need any human input. For this reason, it
is essential to guarantee that the data used to create the framework is correct and in line with the core
quality criteria. It won't be useful if the data is entered incorrectly, and it might cause worse issues with
subsequent reports. There will be costs involved with cleaning, transforming, and storing unstructured data
even if it is provided in an appropriate manner.
The following are some types of data validation:
1. Data type confirmation: Data type confirmation ensures that the correct kind of data is input. One field
could only accept numeric input, for example. If this is the case, then any data that includes extra characters
—such as letters or special images—should be ignored by the framework.
2.Code Check: A code check verifies that a field was chosen from an acceptable range of options or that it
meets with established designing specifications. When a postal code is compared to a list of allowed codes,
it is simpler to establish if it is legitimate. Other criteria like country codes and NAICS industry codes may
also be considered using a similar methodology.
3.Check the range: The range will be tested to see if the input data falls inside a certain range. For instance,
geographic information frequently uses scope and longitude. A latitude number can be anywhere between -
90 and 90 degrees, whereas a longitude value can be anywhere between -180 and 180 degrees. Beyond this
point, qualities are deemed to be invalid.

Normalization:
Standardization is a data set plan system that prevents annoying characteristics like Inclusion, Update, and
Cancellation Oddities by reducing information duplication.
First normal form (1NF)
The first normal form rule is that a table's attribute (column) cannot have more than one value. Only atomic
values should be stored there. Let's imagine that a company has to keep track of the names and contact
information for each of its employees. It produces a table that seems as follows:
Because two employees, Jon and Lester, each had a unique mobile phone number, the company put the two
of them into the same field, as seen in the table above. The emp mobile values for employees are excluded
from 1NF since the criterion stipulates that "each attribute of a table must have atomic (single) values."
Lester and Jon object to this regulation.
Second normal form (2NF)

If both of the following are true, a table is said to be in 2NF:

The first ordinarily structured table arrangement is referred to as 1NF. The proper subset of applicant keys
in any table is not a requirement for any non-prime characteristic. The term "non-prime attributes" refers to
characteristics that are unconnected to any candidate keys. Consider a situation where a school wants to
keep track of the professors and the classes they teach. They produce the following varieties of tables: The
table might include different rows for each topic because the same teacher could teach numerous different
subjects.
Keys to Take into Account Include teacher_id and the non-prime subject attribute teacher_age, which is in
a single NF since each property has atomic values. This is not the case with 2NF, though, as the teacher id,
a valid subset of the candidate key, is the only variable on which the non-prime attribute teacher age
depends. As stated in the 2NF guideline, "no non-prime trait is reliant upon the right subset of any table
competitor key."
We may divide the table into two tables as follows to agree to 2NF: Information about the teacher in the
teacher_subject table:
The tables now adhere to the Second normal form.

Third Normal form (3NF):

If both of the following requirements are true, a table is said to be in third normal form (3NF). 2NF are
required for the table. A transitive functional reliance on any super key should no longer exist for non-
prime attributes. Known as a "non-prime attribute," an attribute is one that is not associated with any
candidate keys. 3NF may be stated as follows in another way: The super key for a table is the letter X if a
table is in 2NF and at least one of the preceding conditions is true for each utilitarian connection X->Y.
The crucial element of the table is An crucial trait for one of the candidate keys is referenced by the prime
feature.
We must divide this table into two tables to get rid of the transitive dependency in order to comply with
3NF:

Insert, Update, Delete Statement

Software development is made easier by an application called the Integrated Development Environment
(IDE). In general, an integrated development environment (IDE) is a graphical user interface-based
working environment made to assist a developer in developing software applications in an integrated
environment with all necessary tools. Debugging, copy control, and data structure review are all common
features that developers can use to quickly move things to other applications without changing them. As a
result, it reduces the amount of time spent learning languages and contributes to increased productivity by
providing the user interface (UI) for relevant components. An IDE upholds single or numerous dialects.
Insert Statement

Update Statement
Delete Statement

Data validation, output designs and interface diagrams evaluating the reasons that the design will meet the
requirements
1.Login Screen
1.1Flowchart:

1.2Output Design:
1.3 Data Dictionary/validation:

2.Admin Screen
2.1Flowchart:

2.2Output Design:
2.3Use case diagram/ Interface diagram:

3.User screen
3.1 flowchart:
3.2 Output design:

3.3Use case diagram/ Interface diagram:
4.Registration page
4.1 Flowchart

4.2output Design
4.3 Data Dictionary

4.4 Interface Diagram
5.Complaint generator page

5.1 Flowchart

5.2output Design
5.3 Data Dictionary

5.4 Interface Diagram
Evaluation of effectiveness of the given design (ERD and Logical design) in terms of the identified user
and system requirements.
A framework's success depends on how well it solves problems for customers. In the transport of
framework convenience based on customer needs that are settled in conjunction with their business goals,
customer responsibility is becoming a standard philosophy. The client network has no craving for holding
up expansive stretches to see new/overhauled system limits made functional. As a result, frameworks and
methods like "handy" improvement, for example, have gained a tremendous amount of acclaim. The
demonstration of the framework's capabilities during the framework's development is necessary for these
methods. Framework development partners demonstrate their progress during brief social events known as
"scrums," during which a practical picture ascent of the course of events of the provision of framework
limits that meet customer requirements is presented.

Detectability and Verification Process

A critical assessment of a development's capacity to meet system necessities revolves around
"conspicuousness." To ensure that the passed-on plan meets the operational requirement, traceability is
necessary. For instance, if a boat wants to reach a maximum speed of 32 packs, a set of requirements
should be attached to execution watch to justify the need for additional planning, development, and
maintenance to achieve that speed. The continuum of necessities age and detectable quality is maybe the
principal system in the plan, improvement, and game-plan of cutoff. Detectable quality is also the
establishment for the change strategy inside a task or program. Without the capacity to follow necessities
start to finish, the effect of changes can't be appropriately assessed. Additionally, change ought to be
evaluated in terms of its complete impact on various essentials and overall execution (see, for instance, the
Enterprise Engineering section of the SEG). A well-directed requirements measure should accompany this
bidirectional movement of requirements throughout a project or program. Utilizing open business devices
is appropriate for logically effective recognition, affirmation, and when all is said and done requirements of
the board.
Implementation of System Security

Database Security
The expression "information base security" alludes to a bunch of instruments, strategies, and techniques
for guaranteeing and keeping up with data set privacy, honesty, and accessibility. Since privacy is the
variable that is disregarded in most of information breaks, this article will focus on it.
The following must be protected and addressed by database security:
• The hardware of the physical or virtual database server; • The computer and/or network infrastructure
used to access the database; • The data in the database; • The database management system (DBMS); • Any
related applications;
Database security is a difficult and complicated task that encompasses all information security
technology and procedures. Additionally, it conflicts with database usability. As it becomes easier to
access and use, the database is more vulnerable to security risks; the information base turns out to be
more resistant to assaults as it turns out to be more challenging to access and utilize.
Why is it important
At risk is the following intellectual property: Your intellectual property, such as your trade secrets, original
works, and unpublished techniques, may be crucial to preserving the competitive edge of your sector.
Harm to mark notoriety: Clients or accomplices might be reluctant to obtain your items or administrations
(or work with you) on the off chance that they have no faith in you to safeguard their or their information.

Costs associated with correcting violations and informing customers: In addition to the cost of alerting
customers of the breach, a compromised business must also pay for forensic and investigation work, crisis
management, triage, and system repair.
What Is a SQL Injection Attack?
The language used most frequently for communicating with relational databases is called Structured
Query Language, or SQL. Databases are used to store user information like usernames and passwords in
applications and other computer languages. Data sets are also the most efficient and secure way to store a
variety of information, including private ledger data and public blog articles and comments.
SQL statements frequently make use of arguments to move data from users into a secure database or the
other way around. Assailants can use the spots where your application chats with a data set with a SQL
contention to get admittance to classified data and other got locales except if the qualities in these client
provided SQL contentions are gotten by disinfecting or arranged explanations.
What Can Attackers Do with a SQL Injection Attack?

At the time it connects to a database, SQLi attacks use code flaws.
When SQLi attacks succeed, attackers are able to:
• Access the front end of an app or website without a password.
• Get into secured databases and access, extract, and delete stored data.
• Open the door for additional attacks by modifying or creating their own database records.
(cheatsheetseries, 2021)
Database maintenance
The term "database maintenance" refers to a set of procedures that are all carried out with the intention of
improving your database. There are steps to boost performance, free up disk space, check for data issues,
look for hardware issues, update internal statistics, and do a variety of other trivial but crucial tasks.
Our Information base Upkeep program has four fundamental 'Classifications' of schedules:
 Defragmentation of the Index

 Maintenance of the Log Files
 Compression of Files and Data
 Authenticity Check
1.Index Defragmentation:
Like how indexes in SQL databases operate, the Dewey Decimal system at a library functions similarly.
Each table in your Office Tools Professional database has at least one indexed column, which we use to
find certain values (such an employee or a job code). For example, "All time cards for employee "Joe
Demo"" is an index that saves a sorted and partitioned copy of the data you request from SQL Server in a
very rapid region of memory.

2. Log File Maintenance

Every transaction that occurs inside a SQL data set is recorded in a "Log Document," a characteristic of
SQL data sets. A data collection can really be returned to the state it was in at any time using these log
entries. Therefore, in the event that something disastrous occurs to your database, whether unintentionally
or as a consequence of malicious intent, you will be able to restore your data to its previous state. The log
files thus need extra care because they are essential parts of the system.
3. File/Data Compaction
As you use it, your SQL database's file size changes. The file expands by a certain amount if more space is
needed. Data may also be kept everywhere there is enough memory because it is put into the database in
pieces. Unfortunately, data from one database may not always be kept close to data from other tables. The
data itself deviates from the indexes we previously mentioned. We do a "Data Compaction," which
reorganizes the file by gathering all associated data, to solve this issue. By doing this, the operator not only
puts relevant data together but also makes room in the file for future use.
4. Integrity Check
In the course of time, your database will undergo several changes. Tables will be modified, added, or
withdrawn, and data will also be added to and removed from the tables. There will be a schema change for
the entire database. The creation, reconstruction, removal, and reassembling of new indexes will all take
place. The size, number, and type of data columns will change. Over the duration of the database's
existence, several updates will be made. Any alteration, however little, has the potential to taint the
database. It is possible for files to include corrupted pages, references in the mapping to contain wrong
data, and tables to have inaccurate information. Small performance issues to major schema failure and data
loss are all possible outcomes of this sort of corruption. Instead, this is a situation where the Integrity
Check is helpful. (officetools, 2020)
Query a system of relational databases

1. DDL (Data Definition Language): DDL, or Information Definition Language, refers to the SQL
instructions that may be used to describe the data set pattern. It is used to create and modify the structure of
database objects in the database and exclusively deals with descriptions of database schemas.
• The construct command is used to construct the database or any of its objects, including tables, indexes,
functions, views, store procedures, and triggers.
• To delete data from the database, use the drop command.
• When modifying the database's structure, the word "ALTER" is utilized.
• Shorten is used to remove every record from a table, including every space used to distribute the records•
The COMMENT function adds comments to the data dictionary.
• The function RENAME allows you to change the name of a database item.

2. DQL (Data Query Language) commands can be used to get schema object data. The DQL's Order will
presumably return a connection that is in outline form based on the query that was provided to it.
Examples of DQL include:
To extract data from the data collection, use the SELECT command.
3.DML (Data Manipulation Language): The SQL orders that arrangement with controlling information in
a data set are named DML (Information Control Language), which covers most of SQL explanations.
Examples of DML include: • Inserting data into a table via the INSERT function.
A table's existing data can be updated using the UPDATE command.
• Records can be deleted from a table in a database using the DELETE option.
4. The rights, permissions, and other controls of the database system are addressed by the DCL commands
GRANT and REVOKE, for instance.
DCL instructions like the following:
Database access is made possible through GRANT.
• Obtain the admission honors for the customer that were given in accordance with the Award order.
TCL stands for Transaction Control Language. Manage database transactions with TCL commands.
TCL commands like the following:
• COMMIT: A transaction has been completed.
• ROLLBACK—reverses a transaction in the event of an error.
Utilize the SAVEPOINT command to set a save point during a transaction.
Set the transaction's characteristics using the SET TRANSACTION command. (geeksforgeeks, 2020)

Data flow diagram

A Data Flow Diagram (DFD) may be quite helpful for modeling and evaluating organizations or systems.
It offers a graphical depiction of the data flow across the system, from inputs to outputs. DFDs are widely
used to collect requirements for analysis and design reasons and may be developed at various abstraction
levels. Data Flows, Processes, Entities, and Data Stores make up the DFD's four main parts. DFDs may be
used to represent both manual and automated systems, and they can be created with varying levels of
consideration, such as detailed process-level graphs and substantial level setting outlines..
1 level data flow diagram

A level 1 data flow diagram, also known as a DFD, depicts how data generally moves through a system or
process. A high-level representation of the system's components, including external entities, data storage,
and data processing procedures, is provided. This realistic offers a theoretical portrayal of the framework
that features its most significant highlights while taking apart its intricacy.

Data Flow Diagram

Here is the data flow diagram of the application.

According to the Above-mentioned design, The User interface, Inputs, Outputs, Data validation and query
along with multiple tables is given below:
1.login
1.1User-Interface:
1.2Inputs:

1.3Outputs:
1.4Data validation:
1.5Query:

1.6Code:

2:user interface:
3.admin Interface

4.Problem Report
4.1Interface:
4.2Inputs:

4.3Outputs:
4.4Data validation:
4.5Query:

Code:

5.User Registration
5.1 Interface:
5.2 Inputs:

5.3 Outputs:
5.4Data validation:
5.5 Query:

6.Running problems
6.1 Interface:
6.2 Inputs:

6.3 Outputs:
6.4 Data validation:
6.5 Query:

6.6 Code:


7.Specialist
7.1 Interface:
7.2 Outputs:

7.3 Data validation:
7.4 Query:

8.Solved Problems interface
9.Problem Types interface

10.codes used in the project


Testing
I use a few different kinds of testing. These are the main ones:

White Box Testing:

White box testing, also known as "Glass box testing," is a type of test case design in which the control
structure of the procedural design serves as the driving force behind the test cases. Using white box testing
techniques, the system was put through the following tests:
a)All free pathways inside a module were practiced once. Our system validated each case structure to
ensure that the correct case was selected and carried out.
b) All logical judgments were examined to determine whether the values were true or false, and some flaws
in the code were fixed.
Black Box Testing:

Black box testing concentrates on the software's functional needs. This type of black box testing allows
software engineers to create a set of input circumstances that will thoroughly test all of a program's
functional requirements. Testing using black boxes differs from testing with white boxes because it is a
supplement that is more likely to find a different sort of problem than white box techniques.
Errors in the interface, data structure effectiveness, performance, and startup and termination errors
Test case and Test plan
Scenario:
Objective:
The goal of the testing is to assess the operation and usability of the complaint/helpdesk management
system when a user registers a complaint about a cracked smartphone screen.

Scope:
This plan incorporates assessing the activity of transferring photos, recording protests, the framework's
information stockpiling capacities, and various different elements of the grievance/helpdesk the board
framework.
Conclusion:
In order to ensure that the complaint/helpdesk management system satisfies the needs and expectations of
users when they file a complaint about a cracked smartphone screen, the goal of this test plan is to give a
thorough and in-depth technique for evaluation. The system must be thoroughly tested in order to identify
any problems and make sure that it satisfies the needs and expectations of users. Testing should be a part of
the product development life cycle since it guarantees that the framework fulfills both client and framework
requirements. To do this, it is necessary to build test cases, plans, and the relevant test data. A number of
problems were found and resolved to enhance the system's performance by comparing the system to both
user demands and the system itself. The testing procedure was effective in showing that the system
complied with the demands and was appropriate for its intended application.
Test Plan:
Test case Name: Registration of users and Problem Report.
System: Helpdesk Operating System.
Design By: Dhirendra Yadav
Designed Date:2023/06/03
Description: Adding of Problems, updating it to specialist, Deleting Solved Problems.
Step Action User System Response Pass/fail
Expected
Result
1. Adding Display Pass
Records Message

2. Update Display Pass

Records Message
3. Delete Display Pass

Records Message
Test case Name: Equipment Details.

Expected
Result
Records Message

Records Message

Records Message
Test case Name: Installation Details.

Expected
Result
Records Message

Records Message

Records Message
Test Case Name: DDL statements

System: Help Desk Management System
Design Date: 2023/06/03
Description: Execute database tables and get following results
1. Record Display DDL
Successfully Message Statements
2. Syntax Display
Errors Message

3. Object Display
Errors Error
Message
4. Data Type Display

Errors Error
Message
Test Case Name: DDL statements

System: Help Desk Management System
Design Date: 2023/06/03
Description: Every DML Query’s execute and get these messages.
Ste Action User System Response Pass/
p Expecte Fail
d Result
1. Insert Display Pass
record Messag
successfull e
y
2. Display Display Pass

Record Data
Successful
ly
3. Syntax Display Pass
errors Messag

4. Object Display Pass

Errors Errors
Messag
e
5. Column Display Pass

Errors Errors
Messag
e
6. Table Display Pass

Definition Errors
Don’t Messag
match e
Allocating Feedbacks On the design:
Comments:
…………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………
…………………………………………………………………………………….
Future recommendations:

…………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………
..
………………………………
……………………………….
Signature Date

effective, extreme and erroneous data in order to build an accurate Application:

A help desk operating system's effective data can be used to accurately depict how the system is being used
and potential issues. The system can then be enhanced and user support enhanced using this data.
Testing documentation can also benefit from extreme and incorrect data. You can ensure that the system is
capable of handling unforeseen circumstances by testing it with extreme data. By testing the framework
with mistaken information, you can recognize likely bugs and blunders.
Here are a few explicit instances of how viable information, outrageous information, and wrong
information can be utilized to further develop an assistance work area working framework:

• Accurate data: Effective data can be used to determine which help desk operating system features are
utilized most frequently. Then, you can use this information to put development efforts in order and make
sure the most important features are always available.
• Extensive data: The help desk operating system's limits can be tested with extreme data. You could, for
instance, attempt to search for a ticket using a very specific keyword or create a ticket with thousands of
attachments. By testing the framework with outrageous information, you can recognize likely issues and
ensure that the framework can deal with even the most requesting assignments.
• Inaccurate data: The help desk operating system can be used to find potential bugs and errors by using
incorrect data. You could, for instance, attempt to search for a ticket with a typo in the keyword or to create
a ticket with a subject line that is blank. You can identify potential issues and fix them before they cause
users any trouble by testing the system with incorrect data.
By gathering and utilizing successful information, outrageous information, and incorrect information, you
can assist with guaranteeing that your assistance work area working framework is generally modern and
prepared to help your clients.
To further enhance your help desk operating system, consider the following additional pointers for
gathering and utilizing data:
•Gather information from various sources. You can gather information from different sources, for example,
client overviews, ticket logs, and framework logs. You'll get a better idea of how the system is being used
and where potential issues might be.
• Conduct regular data analyses. In order to find patterns and trends in the data, you should analyze it on a
regular basis. This will assist you with recognizing regions where the framework can be moved along.
• Act on the basis of data analysis. You should take steps to make the system better once you have found
areas where it can be improved. This will assist in ensuring that your users' requirements are always met by
the system.
Database Connection:
To make a data set association in C# Windows Structure in a helpdesk working framework, we should
follow these means:
1. Make another Windows Structures project in Visual Studio.
2. To the System, add a reference. Data. Namespace for SqlClient
3. Create a control for a button in the form designer.
4. Double tap the button control to open the code supervisor.
private void button1_Click(object sender, EventArgs e) // Establish a connection string. "Data

Source=localhost;" in string connectionString Initial Catalog = helpdesk; True for Integrated Security;
Snippet of code: // Produce a SqlConnection object.

SqlConnection association = new SqlConnection(connectionString);
// Attempt to open the association.
Try using the connection. Open ();
// Work with the database in some way.
// Handle the exception with catch (Exception ex).
// Close the association.
connection. Close();
6. Start the program.
The code will attempt to connect to the database when you click the button. Assuming the association is
fruitful, you can play out any activities that you want to on the data set. You will be responsible for
handling an exception that is thrown if the connection fails.
Here are an extra things to remember while making a data set association in C# Windows Structure in a
helpdesk working framework:
• The connection string might need to be changed to point to the right database server and database.
• In order to allow the application's user account to connect to the database, you may need to modify the
database's security settings.
• When attempting to connect to the database, there may be additional exceptions that need to be handled.
Fetching Records:
In a C# Windows Form application, retrieve a record from a database:
Using System in C#;
using the System Windows. Forms;

using the System Data. SqlClient;
namespace Fetch Record

{
public halfway class Form1 : Form's public Form1() and InitializeComponent() functions;
Private void button1_Click(object sender, EventArgs e) // Create a brand-new SqlConnection object.
new SqlConnection("Data Source=localhost; Initial Catalog=MyDatabase; Integrated
Security=True") is the SqlConnection connection.
// Establish a connection.
connection. Open();
// Create a brand-new instance of SqlCommand.

new SqlCommand("SELECT * FROM Customers WHERE CustomerID = @CustomerID",
connection) = SqlCommand command
// Set the value of the parameter.

command. Parameters. "@CustomerID," textBox1.Text), addWithValue;
// Give the command a go.

reader = command in SQLDataReader. ExecuteReader();
// Examine the reader's results.

if the reader Read()) // Fill in the textboxes with the record information.
reader["CustomerName"] = textBox2.Text;
textBox3.Text = reader["CustomerAddress"];
reader["CustomerCity"] = textBox4.Text;
reader["CustomerState"] = textBox5.
reader["CustomerZipCode"]; textBox6.Text
else // In the event that no record was found, a message will be displayed.
MessageBox. "No record found for CustomerID" + textBox1.Text = show

// Resign yourself to the reader.

reader. Close();
// Disconnect from the network.

connection. Close();
}
}
}
This code will make another Windows Structure application with three textboxes, a button, and a mark.
The code will connect to a database and retrieve the record from the Customers table whose CustomerID
matches the value in the first textbox when the user clicks the button. The data will be displayed in the
other textboxes if a record is found. A message will be displayed in this case.
Steps that I have used to make data designing

The typical steps involved in data design are as follows:
1. Identify the following data entities: In order to do this, the data entities that must be stored must be
identified, and the system's needs must be examined.
2. After the data items have been discovered, the following step is to identify the links between them. This
entails determining if the two persons are in a one-to-one, one-to-many, or many-to-many connection.
3. Ensure the information is uniform: The process of normalization comprises breaking up large, difficult-
to-manage tables of data. Redundancy is decreased and data integrity is improved as a result.
4. Build a data model. A data model graphically depicts the relationships between the data's elements. This
will make sure that every piece of information is logged and structured logically and properly.
5. After the data model has been selected, the next step is to pick a database management system that can
store and manage the data effectively.
6. Describe the structure: The schema outlines the database's tables, columns, and relationships. To provide
effective data storage and retrieval, the schema must be carefully tuned.
7. Finish building the database: The description of the graphic is followed by the addition of data to the
data set. SQL queries are necessary for data entry, editing, and retrieval.
8.Examine the database: To guarantee that it is operating correctly and efficiently, the database has to be
extensively tested. This includes testing for security, functionality, and performance.
Testing the system against user and system requirements

Testing the system against user and system requirements is an important step in verifying that it complies
with the required functionality, performance, and security criteria. Use these procedures to check the
system against user and system requirements:

• Describe the test cases: The user requirements and system requirements should be utilized to define the
test cases. Testing of various types, including functional testing, performance testing, security testing, and
others, are instances of this. The test cases should cover every situation and edge case that could occur.
• When choosing test data, use samples that are typical of how the system will be used. The test data should
contain all potential situations and edge cases for the system. Real-world data, synthetic data, or a
combination of the two might be used for this.
•Put the experiments into action: Run the test cases using the specified test data. This might be
accomplished through human testing, automated testing, or a mix of the two. Keep a record of the results
for each test case.
• Analyze the test findings: Analyze the test results to determine whether the system is functioning as
intended and meeting the requirements. Recognize any flaws or problems that require attention.
• Enhance the procedure: Modify the system as necessary to better meet user and system demands. This
may entail modifying the framework engineering, altering the information base design, or modernizing the
user interface.
• To make sure that the framework has been enhanced and is fulfilling the ideal client and framework
requirements, retest it using the same experiments and test data.
Conclusion:
In conclusion, a comprehensive comprehension of the system design and data requirements is required for
the development of a relational database system that is fully functional. The cycle includes breaking down
the information substances, characterizing connections, normalizing the information, choosing a fitting data
set administration framework, characterizing the mapping, populating the data set, and completely testing
the framework for usefulness and proficiency. Data limitations, access needs, scalability, end-user
requirements, data quality, and continual development are all crucial factors to take into account.

Report:
A reflective report on
Effectiveness of Database
Dhirendra Yadav
Database Design and Development
Section ‘E’ 2023

Introduction
Technical and user documentation are essential to any software development efforts. Comprehensive
details of the system's architecture, data models, algorithms, and other technical characteristics may be
found in technical documentation. Due to this documentation, technical stakeholders now have a better
grasp of the system's design, implementation, and maintenance.
While user documentation provides instructions and guidance to end users who will interact with the
system. User guides, how-to articles, and other instructional materials are included in this documentation to
help people understand how the system works.
Effective technical and user documentation ensures the system's functionality and makes it easy for
developers, testers, and end users to understand. To ensure that the system is built and maintained
effectively, this documentation serves as a reference for developers and testers. Additionally, client
documentation aids users in making successful use of the framework, boosting user satisfaction and, more
generally, framework performance.
Technical Literature:
1.Learn about the architecture, design, and implementation of the system

2.Sort out the documentation to be not difficult to peruse and follow
3.Make use of flowcharts, diagrams, and other visuals to show how the system works.
4.Include instructions for configuring and setting up the system.
5.In the event of errors or problems, include steps for troubleshooting
6.Use language that is both clear and concise, avoiding technical jargon whenever possible.
7.Consider the crowd and their specialized information while composing the documentation
8.As the system changes over time, keep the documentation current.
User Instruction:
1.Include a brief introduction outlining the system's purpose and advantages
2.Clearly and concisely explain how to use the system
3.Make use of screenshots and other visuals to show how the system works.
4. Organize the documentation in a way that is logical and simple to follow.
5.Provide helpful hints and best practices for using the system.
6. Avoid using technical jargon and speak plainly whenever you can.

7.To assist users in comprehending technical concepts, provide a glossary of terms and definitions.
8. Include contact details if you need technical help or any other type of assistance.
Overview of the system: technical and user documentation

for a whole system
A retail company can use the technology to manage online orders. A database backend, an order processing
engine, and a web interface make up the system. The data set backend saves the request data, and
customers may place orders through the web interface. Bills are generated and orders are processed by the
order processing engine.
Diagrams of Data Flow: The way that data is exchanged between system components is depicted in
various data flow diagrams. Here are some instances of data flow diagrams:
The order processing engine, the database backend, and the web interface are all included in this high-level
system diagram, or setting chart.
• Data Flow Diagram, Level 1: In this diagram, the data flow from the web interface to the database
backend is depicted.
•Level 2 Information Stream Graph: This illustration depicts the information flow from the order
processing engine to the database backend.
Flowcharts:
The evolution of different system processes is shown in a number of flowcharts. Examples of flowcharts
include the following:
• Order Placement Schematic: This flowchart illustrates the steps necessary to place an order, such as
selecting goods, providing customer information, and submitting the order.
•Request Handling Flowchart: This flowchart shows the steps used to fulfill a request, including verifying
the installment, updating the inventory, and creating a receipt.
Evaluation of the Database Assessing the database in terms of the enhancements required to maintain the
system's effectiveness
Performance is just one crucial component to consider, along with how the information base is displayed.
If there are delays or issues with execution, are tasks and inquiries progressing effectively? The database
structure may need to be improved, indexing and caching may need to be improved, or hardware or
software components may need to be upgraded if the database is slow or having performance issues.
2. Security: The database's security is yet another essential component. Aside from being carried and stored
safely, are the proper access controls in place? Additional security measures like encryption, access
restrictions, or regular security audits can be required if security is a concern.
3. Data Integrity: A database's capacity to keep running effectively depends on the quality of its data. Does
the quality of the data appear to be affected by any duplicates or problems with missing data? To guarantee

that the data are accurate and consistent, it may be necessary to strengthen data validation or implement
data cleaning techniques.4. Scalability: As the database increases in size and complexity, it may become
increasingly important to upgrade the database architecture to support additional data and traffic. These
include data partitioning, the addition of more servers, and the acceleration of searches and procedures.
5.UI: Last but not least, the user interface and user experience of the database need to be taken into
account. Are customers able to easily access and handle the data, or are there still usability issues that need
to be addressed? The user interface (UI) and client experience may be further improved by focusing on the
overall efficacy and productivity of the knowledge base structure.
In conclusion, user and technical documentation must be assembled before software development and
deployment can begin. The software system's architecture, design, and implementation are all covered in
great detail in the technical documentation, whereas user documentation provides guidance on how to
interact with the system effectively. A system's usability and operation may be enhanced, support and
maintenance costs may be decreased, and users' effective and appropriate use of the system is ensured,
among other advantages, via high-quality technical and user documentation.
In general, producing technical and user documentation is crucial to the software development process.
Users may be happier and more willing to utilize the software system as a result, which can help maintain it
functional and user-friendly.
Evaluation:
Consider the following while assessing the queries and data gathered to provide useful management
information in a Windows form:
• The purpose of the searches and data extraction. What are you trying to achieve by obtaining this data?
What questions would you like to reply?
• The data's quality. Is the information true? Is it finished? Is it current?
• The data's significance. Are the data relevant to the queries' objectives?
• The data's accessibility. Is the information straightforward? Is it simple to use to respond to your
inquiries?
After evaluating the extracted queries and data, you can use them to generate useful management data in a
Windows format. You can do some of the following:
• Develop reports. The data can be used to create reports that simplify and summarize the information.
• Establish dashboards. Data can be visualized in the form of dashboards, which can be used to track
performance and spot trends.
• Set up alerts. You can create alerts with the data to be notified when particular conditions are met.
By utilizing the questions and information removed in a significant manner, you can assist chiefs with
pursuing better choices and work on the presentation of your association.
Here are a few extra ways to create significant administration data in a Windows structure:
•Utilize clear and brief names for all fields.

•Utilize proper information types for each field.

• Make the data easy to read by formatting it.
• To highlight important data, color code it.
• To show the data, use graphs and charts.
• Make use of sorting and filters to assist users in finding the data they require.
• Make use of the search feature to assist users in locating specific data points.
You can make Windows forms that are simple to use and give managers the information they need to make
better decisions by following these tips.
Recommendations:
Recommendations Make certain that the system has been developed and put into use in an efficient
manner. The capability and how it functions have been characterized for the director and the client who is
visiting, and this device is applied to the objective. During the observation, different advantages and issues
or restrictions tracked down in the test hardware. Machine safety is one topic restriction. The device is
programmed in such a straightforward manner that the menu can be managed by the simplest legal entity.
In any case, since you want to have numerous usernames to sign into the machine, in light of the fact that
the gadget can be utilized by numerous clients, every shopper actually needs somebody to call. Passwords
should be changed frequently to guard against unauthorized access. The password for this machine cannot
be changed; however, if the same password is used frequently, anyone can learn it. The fact that this
method no longer provides any useful equipment for producing difficult copies of output within the print
copy type is another obstacle or annoyance. This feature is not available on this machine. This machine will
not produce any backups if we also appear in the system. Human error or other technical issues could cause
the system to be disrupted. As a result, this could also be a problem with the device itself. Because this
single administrator login requires the most secure user name and password, which absolutely anyone can
analyze and keep, no intruder inside the device can reveal it. This could be a method of hacking.
Future enhancements
The primary goal is to make this system easier to use and to add more features, like advanced graphical
user interfaces, which will encourage interaction and make it easier to use the system effectively and
efficiently. The management system might gain a lot from having a new feature that lets users add new
fields and details. This will lessen in time utilization. An improvement ought to be finished in the approach
to embedding, refreshing and erasing the records in the Help Desk management System the board
framework. The graphical interfaces in the user documentation should be improved, as the user
documentation will provide a brief introduction to interaction. There will be more points in development if
I can make the system more appealing and user-friendly. In order to improve security, the Help Desk
management System management system's Administrator should have access to more options. Lastly, by
taking into account the database's security. In order to use a variety of control mechanisms to safeguard the
database from various threats, there needs to be a significant improvement.

FUTURE IMPROVEMENT
Solicitations should be coordinated in the business, and messages and warnings for fresh debuts and limits
should be conveyed to clients. A search engine that lets customers and customers search for specific
products in the store is essential. The store must also accept debit and credit cards. Customers and users
who do not speak English must have access to a variety of languages in order to deal without difficulty.
Control of Risk Many retail businesses use the Departmental store management (DSM) system to record all
important data at the user register. You've likely seen DSM Frameworks while recording at a help desk. At
the point when you look at, the scanner tags on the things you recorded were examined, problems were
determined utilizing its types and list information, description was recorded, and solved problem list were
refreshed. The Help Desk Management System can send daily sales summaries to its management or home
office via product or cash register, and all of these operations take place in real time. Numerous
organizations utilize DSM frameworks since they further develop consumer loyalty by permitting them to
follow and investigate information. so United Limited can minimize risk.
Video links:
https://youtu.be/UI8vunor1HI
https://youtu.be/UI8vunor1HI

References
cheatsheetseries. (2021). cheatsheetseries. Retrieved from cheatsheetseries.owasp:
https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html
geeksforgeeks. (2020). geeksforgeeks. Retrieved from www.geeksforgeeks.org:
https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/
javaTpoint. (n.d.). javaTpoint. Retrieved from https://www.javatpoint.com/dbms-tutorial
library.ucmerced.edu. (2020). library.ucmerced.edu. Retrieved from library.ucmerced.edu:
http://library.ucmerced.edu/data-dictionaries
officetools. (2020). officetools. Retrieved from www.officetools.com:
https://www.officetools.com/knowledgebase/database-maintenance-explained/

Assignment Cover Sheet

Uploaded by

Copyright:

Available Formats

Assignment Cover Sheet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Assignment Cover Sheet

Uploaded by

Copyright:

Available Formats

1|Page Database and Development

STUDENT NAME Dhirendra Yadav

UNIT AND ASSIGNMENT DETAILS

UNIT TITLE Database management systems

ASSIGNMENT TITLE United Limited IT Systems

ASSESSOR NAME Rajat Shakya

ESTIMATED WORD 10,000

HAND IN DATE 2023/06/08

DECLERATION AND ACKNOWLEDGEMENT

Dhirendra Yadav 2023 1

Plagiarism and Collusion

SIGNATURE Dhirendra yadav DATE 2023/06/08

Dhirendra Yadav 2023 2

Dhirendra Yadav 2023 3

Dhirendra Yadav 2023 4

Dhirendra Yadav 2023 5

Dhirendra Yadav 2023 6

Test Case Name: DDL statements............................................................................................................63

Dhirendra Yadav 2023 7

Database Management Systems: (javaTpoint, n.d.)

Dhirendra Yadav 2023 8

The following list of database types is provided:

 The many DBMS types are illustrated below:

Dhirendra Yadav 2023 9

• Automated manipulation of the goods.

Dhirendra Yadav 2023 10

SQL (Structured Query Language)

Dhirendra Yadav 2023 11

Dhirendra Yadav 2023 12

The main aims of utilizing ER-diagram

Relational Database Schema

Dhirendra Yadav 2023 13

 Help keep data inconsistencies at bay throughout a project.

Dhirendra Yadav 2023 14

Dhirendra Yadav 2023 15

• To populate a database with all relevant information.

The following are some types of data validation:

Dhirendra Yadav 2023 16

Second normal form (2NF)

Dhirendra Yadav 2023 17

The tables now adhere to the Second normal form.

Dhirendra Yadav 2023 18

Dhirendra Yadav 2023 19

Insert, Update, Delete Statement

Dhirendra Yadav 2023 20

Dhirendra Yadav 2023 21

Dhirendra Yadav 2023 22

1.3 Data Dictionary/validation:

Dhirendra Yadav 2023 23

Dhirendra Yadav 2023 24

2.3Use case diagram/ Interface diagram:

Dhirendra Yadav 2023 25

3.2 Output design:

Dhirendra Yadav 2023 26

3.3Use case diagram/ Interface diagram:

Dhirendra Yadav 2023 27

4.3 Data Dictionary

Dhirendra Yadav 2023 28

4.4 Interface Diagram

5.Complaint generator page