KHAYRE HOTEL MANAGEMENT

SYSTEM
A Research Paper

Submitted for the partial fulfillment of the requirements for the award of the
Diploma in

Information Communication Technology (ICT)

Under the Guidance of Abdirisak Mohamed Abdilahi

Submitted By

Name

1) Ahmed Mohamed Hassan

2) Suhayb Ahmed Gahnug
3) Abdirahman Essa Mohamed

DEPARTMENT OF ICT
Tisqaad College

Sept – 2021

Page | I
 Tisqaad Computer Science College

CERTIFICATE
This is to certify that the project titled “Khayre Hotel” is a bona-fide work done by

Student Name

1) Ahmed Mohamed Hassan

2) Suhayb Ahmed Gahnug
3) Abdirahman Essa Mohamed

In partial fulfillment of the requirements for the award of Diploma. (ICT)

(Eng. Abdirisak Mohamed Abdilahi) (Eng. Abdirisak Mohamed Abdilahi)

Advisor Head of the Department

Page | II
 DECLARATION
We, Ahmed Mohamed Hassan, Apdirahman Essa Mohamed , Suhayb Ahmed Gahnug hereby declare
that this thesis is our original work and has not been presented for the award of any diploma in any
other college or university.

Suhayb Ahmed Gahnug Ahmed Mohamed Hassan

Signature……………………. Signature………….…….

Apdirahman Essa Mohamed

Signature…………………….

Date: ………………….

This thesis has been submitted with my approval as supervisor:

Abdirisak Mohamed Abdilahi,

ICT,

Tisqaad College, Hargeisa. Somaliland.

Signature………………………………………………..

Date: ………………………

Page | III
 ACKNOWLEDGEMEN

BISMILLAH , first thanks to Allah(SW) who allowed us to achieve this stage of life and make our
long dream came true, again special thanks goes to our parents whom their encouragement and
advice for our studying.

We are also here to express our gratitude to our advisor Eng. Abdirisak Mohamed Abdilahi for his
support, guidance and encouragement of our project.

This book would not have been possible without the help of many people whose comments and
suggestions significantly improved the end result of this project.

Finally, we wish to express our appreciation to all who has contributed whatever donations to this
paper including our family, friends and our honorable teachers.

Page | IV
Page | V
Contents
A Research Paper ...................................................................................................................................................I
Submitted for the partial fulfillment of the requirements for the award of the ......................................................I
Information Communication Technology (ICT)...............................................................................................I
Under the Guidance of Abdirisak Mohamed Abdilahi .......................................................................................I
DEPARTMENT OF ICT ....................................................................................................................................I
CERTIFICATE...................................................................................................................................................II
In partial fulfillment of the requirements for the award of Diploma. (ICT) .........................................................II
DECLARATION ...............................................................................................................................................III
ACKNOWLEDGEMEN .................................................................................................................................. IV
Contents ............................................................................................................................................................. VI
CHAPTER ONE .................................................................................................................................................1
INTRODUCTION ..........................................................................................................................................1
Background .........................................................................................................................................................1
Org Background .............................................................................................................................................1
1.1.2 Mission ........................................................................................................................................................2
Vision ...................................................................................................................................................................3
Org Structure ......................................................................................................................................................4
Problem Statement .............................................................................................................................................4
Proposed Solution ...............................................................................................................................................5
1.4 Project Goals and Objectives .......................................................................................................................5
1.4.1 Project goals ...........................................................................................................................................5
Project Objectives ...............................................................................................................................................6
1.5 Theoretical Background ...............................................................................................................................7
1.6 Project management .....................................................................................................................................8
1.6.1 Total Cost ...................................................................................................................................................8
1.6.2 Time Management ...................................................................................................................................10
Analysis ..............................................................................................................................................................11
2.0 Introduction.............................................................................................................................................11
2.1 Fact Finding ................................................................................................................................................11
2.2 Interviews ....................................................................................................................................................11
2.2 Requirement ................................................................................................................................................12
2.2.1 Functional .................................................................................................................................................13
2.2.2 Non-Functional.........................................................................................................................................13
2.3.1 System DFDs ............................................................................................................................................14
2.3.1 Context diagram ......................................................................................................................................15

Page | VI
2.3.2 Level zero diagram ..................................................................................................................................16
2.16 Low level diagrams ...................................................................................................................................17
............................................................................................................................................................................17
............................................................................................................................................................................17
Chapter Three ...................................................................................................................................................18
Project Design ...................................................................................................................................................18
3.0 Introduction.............................................................................................................................................18
3.1 Data Dictionary ...........................................................................................................................................18
3.1.1 Data item dictionary ................................................................................................................................19
3.1.2 Data structure dictionary ........................................................................................................................19
3.1.3 Data store dictionary ...............................................................................................................................20
3.1.4 Data flow dictionary ................................................................................................................................20
3.2 Data design ..................................................................................................................................................21
3.2.1 Entities and Attributes ............................................................................................................................21
3.2.2 Database design ........................................................................................................................................22
[Link] Database ER Diagram ..........................................................................................................................23
3.3 Interface & Screens Design ........................................................................................................................24
3.5 Control Design.............................................................................................................................................24
Chapter Four .....................................................................................................................................................25
Project Implementation ....................................................................................................................................25
4.0 Introduction: ...........................................................................................................................................25
4.1 Application Development ...........................................................................................................................25
4.1.1 Modules .....................................................................................................................................................25
4.1.2Refer to DFDs, process description, ERDs .............................................................................................37
4.2 User manual ................................................................................................................................................38
Chapter Five ......................................................................................................................................................39
Project Conclusion ............................................................................................................................................39
5.1 Future work: ...............................................................................................................................................39
The interfaces that will update is: ...................................................................................................................40
5.2 Conclusions: ................................................................................................................................................41
5.3 Reference .....................................................................................................................................................42

Page | VII
Page | II
 CHAPTER ONE

INTRODUCTION

1.0 Introduction

The project titled Hotel management system is Hotel management software for monstering transections

for library, the project “Hotel management system” is developed in C# which mainly focuses on basic

operations in Hotel like in a new Guest adding, Clients updating

Information, searching person information and members and facility to rent a room.

Hotel management system is Desktop application designed to windows operating system and to help

hotel users in our software.

This software is easy to use for beginners and advancers it features a familiar and well thought-out an

attractive user interface combine with strong searching Insertion and reporting capabilities The report

generation facility of Hotel system helps to get a good idea of which are the rooms rented by clients ,

makes employs possible to generate reports hard copy.

This software project is a hotel management software system with all the basic needs of a hotel as well

as some innovative features for managing a hotel. It consists of a large database of various rooms

available in the hotel. It also lists un-rented rooms.

The system keeps track of all the fees readily paid and also the fees that have been un-paid. The system

also handles room’s database. If the employee needs a report, he can copy the fees lo information of

the client. Renters usually tend to forget the date to pay the fees, so this system even calculates fine

depending on the expiry date. Thus this innovative hotel management system provides enhanced hotel

functionality for this modern world.

Background

Org Background

This Hotel opened in 2014 by the hands of a young entrepreneur.

Page | 1
He take the risks of opening this hotel.

He was an Engineer he had a construction company so that he thought that he would start a new

business.

He decided to build a building on the site of his former shop, which was located near Cartan dental

clinic, and he succeeded.

The construction cost nearly $ 500,000.

The hotel has been operational for almost 7 years now.

During this time, there have been a number of staff members.

His name is Mahoumed Ali Khayre.

1.1.2 Mission
At the moment we aim to extend the entire service of the Hotel management system to the general

modern services.

In Hargeisa We are committed to work efficiently, honestly, competently, with quality

Services . I am currently training all the staff of Khayre hotel to strengthen their knowledge related to

the clients basic and all needs of managing a hotel.

Page | 2
Vision
We Aspire, God willing to be the first Hotel in Somaliland as a whole and in the

Horn of Africa. We want our customers to add rewards that we encourage them.

Our vision for the future is to cover all Regions of Somaliland Communicate the services we

Provide.

Also we provide a good services to our clients so we can let them go with a smile in their faces

To come for us in the future.

There are also benefits from training the next generation the wee that they manage also work for a hotel

managing system.

We wish after 5 or 7 years to open our second and third branch in Hargeisa.

Page | 3
Org Structure

Manager

Cashier

Customer

Employee

Problem Statement

1. Manual work like books...

2. Loss of data.

3. Lost of the fees reports .

4. All Keys in the hotel are unknown or difficult to find.

5. It difficult to get clients information.

Page | 4
Proposed Solution
The solution proposed is to have a comprehensive rental project. To have the problem and the

solution of the paper and in order to succeed with this Project, the problem was too much help

from the voucher registration and contains everything that is rented first and ongoing use of paper

and lists of useless.

1. Software work.

2. Protect company data from loss.

3. The lost data is easily recovered. Such as accounts and fees.

4. All about to store the keys in the desk of the reception.

5. To make it easier to find clients information.

1.4 Project Goals and Objectives

1.4.1 Project goals

1. The first priority is to make the hotel management system a lot easier and simple. .

2. To get experience the way that we makes the Programs.

3. To keep up with Modern Technology which the world is now connecting with.

4. In the beginning it was a manual process that we had a lot of problems in.

5. To make the annual accounting of the hotel.

6. All tasks can be done automatically to enter data

7. Data accuracy

Page | 5
 8. No need store the data in the book.

9. Quicker reaction .

10. Information is getting very quickly.

11. No need book, paper and everything manual .

12. Every person can do it to record the data.

13. To help the hotel to done on its daily actions very easy.

14. To get more customer readers.

Project Objectives

# Our resolution that we made to this project include:

1. All accomplishments done automatically or database entry

2. Needed to store the data a computer

3. A user must be Needs in a technician

4. record must be saved database system

5. They need a hardware devices to facilitate the task

6. Powers that be must has a back up to get data

7. To make easier for work of hotel

8. To ensure reservations.

Page | 6
1.5 Theoretical Background
Comprehensive Hotel management system that deliver effective, safe, high-quality intervention to

those that need them, when and where needed, with minimum waste of resource, and with continuity

of insurance across levels of care, settings, and providers.

Our software has the facility to give a unique id for every client and stores the details of every employee

and the manager automatically.

RESOURCE REQUIREMENT:-

The Platforms that is running the project is:-

 Operating Systems:

Microsoft Windows 10

 Packages of the Application:

Microsoft Visual Studio 2019

Microsoft SQL server 2019

 The following lists are the minimum system requirements to run the project:

1. RAM (Random Access Memory) 8GB

2. CPU (Central Process Unit) requires a computer Pentium processor with a clock speed of at least

233 megahertz (MHz). Microsoft recommends a computer with a cori5 or faster processor

3. Available Hard Disk Space 500 GB of available hard-disk space

We use during making this program two programs those are Sal server and Microsoft C sharp those

Makes easier to make these projects and the advantage of these programs

Page | 7
1. The Sal server management system allows storing data and tables of the Projects

2. And C sharp helps us to build the structure and front end of the projects

We are determined to be an over program we want to do anything that will help business

Our hope to achieve and implement a system to make accurate long-time interrupted program Working.

1.6 Project management

Project nature and scope

 Protects company data.

 The lost data is easily recovered. Such as accounts, and All about the hotel as with the fees also.

 All un-rented rooms is highlighted

1.6.1 Total Cost

In this project, we did not face a lot of cost issues specially hardware cost because the hotel

Doesn’t have at all a lot of computing devices so we bought a simple things to use.

The total was $646.

Page | 8
 Hardware Type of Hardware Cost

Computer hp Computer $185

Laptop Hp Laptop $260

Ram 8GB $30

Mouse Wireless $6

Printer Hp printer $165

Page | 9
1.6.2 Time Management

Chapter Five

Chapter Four
Chapter Names:

Chapter Three

Chater Two

Chapter One

0 2 4 6 8 10 12 14
Time / Dates :

Page | 10
 Chapter Two

Analysis
2.0 Introduction
This chapter is about the fact that we have been in the process of making the system we interviewed

the authorities we received more information. Some of the part they will be it functional requirements

and Non-functional requirements by providing us with the services like software that will make us

the hotel also constraints on the function offered by the system.

Also includes the chapter as the System DFD's is covered Context diagram, Level zero diagram and

Low-level diagram describes the following descriptions.

2.1 Fact Finding

Fact Finding is process of collection of data and information based on techniques which contain

sampling of existing documents, research, observation, questionnaires, interviews, prototyping and

joint requirements planning. System analyst uses suitable fact-finding techniques to develop and

implement the current existing system. Collecting required facts are very important to apply tools in

System Development Life Cycle because tools cannot be used efficiently and effectively without

proper extracting from facts.

2.2 Interviews
There are most Asked Interview Questions for hotel with Answers:
Page | 11
 Interveiwer Question Owner Answer Duration

When was the In 2014 2 Minute

business established?
How many people did me and another person who 2 Minute
you start with? was an accountant for me.
How much money did We started with 500,000 2 Minute
you start with?
What kind of system The traditional way which we 3 Minute
do you work on ? use the book.
How Protect your There is no other way to 3 minutes
business data? protect our Business data
unless trust on the other
employees.
How much do you We need it in very important 2 minutes
need to works in a way.
computerized way?
How to protect When we found a full 6 minutes
business accounts? functioning program our
database will be protected.
How long does the It takes few days to calculate 5 minutes
accounting time take? the annual profit .

2.2 Requirement
This part we like to mention more information about software function requirement and non-

requirement we all of the world there are billions of software but every software has functional

requirement and non-function requirement.

We will perform bellow some information about requirement and we split it two main
Page | 12
parts, we hope you will know your functional requirement and non-functional requirement also you,

will know which one is your functional requirement and which one is not your non-functional

reqiurment.

2.2.1 Functional

The system we make has money buttons some of buttons has functional and other buttons has non-

functional.

Requirements have been demarcated based on their relevance to the user of the system, that is:

Save, Delete, Update, New.

The buttons have functional includes:

1. Save: it necessary because its importance the programs to support how to save the data, without

save the program do not save automatically so you have to use the save button as to save

the data.

2. Update: the button this can do the newly renovation the data it’s self because the program

is technological so they might add new thing and this help to continues with the revolution.

3. New: this help to create new thing and clear it the existence data in the textbox of you went

to create the new thing if may be in the notepad or other things.

4. Delete: you can support, how to erase data which you might not want to use later on or might

not necessary to use it for further.

2.2.2 Non-Functional.
We making complete system, this system have many buttons some of buttons are functional and

non-functional.

The different devices; who cannot be trained on the application functionalities. Hence non-functional

requirements such as usability and adaptability are as importance for the application as the function

Page | 13
requirement.

In this system, security, availability, adaptability and usability are recognized as the most importance

non-functional requirement and are discussed in details below.

1. Usability

2. Adaptability

3. Availability

4. Security

5. Speed

6. Volume

7. Reliability

8. Integrity

2.3.1 System DFDs

A data-flow diagram is a way of representing a flow of data through a process or a system. The DFD

also provides information about the outputs and inputs of each entity and the process itself. A data-

flow diagram has no control flow, there are no decision rules and no loops.

At this level, there is only one visible process node that represents the function of a complete system

in regards to how it interacts with external entities. Some of the benefits of a context diagrams are:-

1. Shows the overview of the boundaries of a system

2. No technical knowledge is required to understand with the simple notation

3. Simple to draw, amend and elaborate as its limited notation

Page | 14
2.3.1 Context diagram
The figure below shows as context data flow diagram that is drawn for a hotel ordering system. It

contains a process (shape) that represents the system to model, in this case, the “room ordering

system”.

it also shows the participants who will interact with the system, called the external entities. In this

example, reception, manager and customer are the entities who will interact with the system.

In between the process and the external entities, there are data flow (connector) that indicates the

Existence of information exchange between the entities and the system.

Cleint Stuff

0.1

Hotel
Mng sys

Rooms

Page | 15
2.3.2 Level zero diagram
The following diagram illustrates how can easily understand main concepts of the projects also he

Show the major process with which they inter-act, also he explain the major process are inter-related

By the data flow, and he shows the external entities, the major processes that comprise the overall

System the internal components of process zero.

Cleint employe

reuists

requists

respond

Respnds Hotel mnagment

system

Fee recorded

reported

fee

rooms
rented

Page | 16
2.16 Low level diagrams

Low-level design is a component-level design process that follows a step-by-step refinement process.

This process can be used for designing data structures, required software architecture. Lower level

are typically terms used to classify, describe and point to specific goals of a systematic operation,

though its uses also vary depending on the context - such as use in computer science versus business

administration. In general, high-level is used to describe operations that are more abstract in nature,

where overall goals and systemic features are typically more concerned with the wider, macro system

as a whole. Alternatively, a low-level description is one that describes more specific individual

components of a systematic operation, focusing on the details of rudimentary micro functions rather

than macro, complex processes. Low-level classification is typically more concerned with individual

components within the system and how they operate.

rooms

Cleints staff

Hotel
mnagment

system

controls

manager

Page | 17
 Chapter Three

Project Design
3.0 Introduction
This part we like to explain our project design this part is very important thing because we define

and explain our project data and entities also we mention hire database and relation between visual

basic studio and SQL server studio after that we hope to expand hire directions 30 of our project and

how to make relationship and how to make reject if [its unrelated tables try to inter data and how

to make successfully safe tables which can store all data without confuse.

3.1 Data Dictionary

A data dictionary is a collection of the descriptions of the data objects or items in a data model for the

benefit of programmers and others who need to refer to them. A first step in analysing a system

object with which users interact is to identify each object and its relationship to other object. This

process is called Data Modeling and result in a picture of the object relationship. After each data

object or item is given a descriptive name, its relationship is described (or it becomes part of some

structure that implicitly describes relationship), the type of the data (such as text or image or binary

value) is described, possible predefined values are listed, and a brief textual description is provided.

This collection can be organized for reference into a book called a data dictionary.

The data dictionary, Is a reference work of data about data (metadata), one that is compiled by the

System analyst to guide them through the analyse and design. It is where the system analyst goes to

Define or look up information about entities attributes and relationship on the ERD (Entity

Relationship Design) is the information you see in the data dictionary.

Important of the data dictionary: avoid duplications: always better communication between

Organizations who shares the same data base: makes maintains straight for word: it is valuable for

Their capacity to cross referencing data items. Enable one description of a data items to be stored and

Accessed by all individual so that definition for a data items is established and used.

Page | 18
Entity Attribute Type/Size Primary key
Client ID INT
Client Full name Varchar (50)
Client Age INT
Client Gender VARCHAR (50)
Client Tell INT
Client Address VARCHAR (50)
Entity Attribute Type/Size Primary key
Staff ID No Int
Staff Name Name Varchar (50)
Phone int varchar(50)

Address Address varchar(50)

Salary fee varchar(50)

3.1.1 Data item dictionary

Unit of data contained in a record, or a unit of data stored in a field that describing a particular

attribute (such as name, age, address) and requiring one or several bits, bytes, or words to represent

an entity.

The field cannot be changed after you save the DD item Within the DD, all DD items are referenced

by this four-byte data name. As they are used in database tables, a two-character prefix is added to

create unique data names in each table specification (DDS). If you are adding an error message,

this field must be left blank. The system assigns the error message number using next number.

3.1.2 Data structure dictionary

A dictionary is a general-purpose data structure for storing a group of objects. A dictionary has a set

of keys and each key has a single associated value. When presented with a key, the dictionary will

return the associated value. Which data structure can be used for efficiently building a word

dictionary and Spell Checker?

The answer depends upon the functionalists required in Spell Checker and availability of memory.

For example, following are few possibilities.

1. Hashing is one simple option for this. We can put all words in a hash table. Refer this paper which

compares hashing with self-balancing Binary Search Trees and Skip List, and shows that hashing
Page | 19
performs better. 2. Hashing doesn’t support operations like prefix search. Prefix search is something

where a user types a prefix and your dictionary shows all words starting with that prefix. Hashing

also doesn’t support efficient printing of all words in dictionary in alphabetical order and nearest

neighbor search.

HOTEL
Client
MNG Admin
SYS

3.1.3 Data store dictionary

A data store is a repository for persistently storing and managing collections of data which include

not just repositories like databases, but also simpler store types such as simple files, emails etc. A

database is a series of bytes that is managed by a database management system (DBMS). A file is a

series of bytes that is managed by a file system. Thus, any database or file is a series of bytes that,

once stored, is called a data store.

3.1.4 Data flow dictionary

In computers, the path of data from source document to data entry to processing to final reports. Data

changes format and sequence (within a file) as it moves from program to program. In

communications, the path taken by a message from origination to destination that includes all nodes

through which the data travels.

Page | 20
 clients
Managerr

Processor

Hotel management Staff

system

Data source

3.2 Data design

3.2.1 Entities and Attributes
An entity relationship diagram is a means of visualizing how the information a system produces is
related. There are five main components of an ERD:

Entities which are represented by rectangles. An entity is an object or concept about which you want to
store information.

Entity

A weak entity is an entity that must defined by a foreign key relationship with another entity as
Page | 21
it cannot be uniquely identified by its own attributes alone.

Entity

Actions, which are represented by diamond shapes, show how two entities share information in
the database.

Entity

3.2.2 Database design

A database is a collection of information that is organized so that it can easily be accessed, managed,

and updated. In one view, databases can be classified according to types of content bibliographic,

full-text, numeric, and images.A database is a list or a group of lists of objects organized to make the

list(s) and their values easy to create and manage. In the computer world, this suggests, rightly, that

the list(s) and (their) values are stored in a machine. As information becomes of high importance,

almost every company keeps some type of database, whether it includes its employees, its customers,

or the products it sells.

Database design is the process of producing a detailed data model of database. This data model

contains all the needed logical and physical design choices and physical storage parameters needed to

generate a design in a data definition language, which can then be used to create a database. A fully

attributed data model contains detailed attributes for each entity.

The term database design can be used to describe many different parts of the design of an overall

database system. Principally, and most correctly, it can be thought of as the logical design of the base

data structures used to store the data. In the relational model these are the tables and views. In an

object database the entities and relationships map directly to object classes and named relationships.

However, the term database design could also be used to apply to the overall process of designing,

Page | 22
not just the base data structures, but also the forms and queries used as part of the overall database

application within the database management system (DBMS).

The process of doing database design generally consists of a number of steps which will be carried

out by the database designer. Usually, the designer must:

1) Determine the data to be stored in the database.

2) Determine the relationships between the different data elements.

3) Superimpose a logical structure upon the data on the basis of these relationships.

[Link] Database ER Diagram

Page | 23
3.3 Interface & Screens Design

3.5 Control Design.

Clear Button
New

Save Button
Save

Update Update Button

Delete Button
Delete

Page | 24
 Chapter Four
Project Implementation
4.0 Introduction:
In this chapter we deliberate and express to the system and easily to see graphical design project.
Here, we shaping on the system and always users shall to see the design to evaluate.

4.1 Application Development

4.1.1 Modules
Modules connect C# and Sql database
Login from:
This form allows you to enter the project and needs you to enter username and password to enter
the project, if you type incorrect username or password you can enter the project so its security form
login Form code
When you passed the login form you will come and show main Form. Main form consists of all form in our system,
such as register customer, rooms, payment and etc
public partial class Form1 : Form

public Form1()
{
InitializeComponent();
}

private void guna2Button1_Click(object sender, EventArgs e)

{
[Link]();
SqlDataAdapter sda = new SqlDataAdapter("Select COUNT(*) FROM Staffs WHERE
StaffName='" + [Link] + "'and Password ='" + [Link] + "' ", Con);
DataTable dt = new DataTable();
[Link](dt);
if ([Link][0][0].ToString() == "1")
{
Dashboard mf = new Dashboard();
[Link]();
[Link]();
}
else
{
[Link]("Wrong Username Or Password");
}
[Link]();

private void guna2Button2_Click(object sender, EventArgs e)

{
[Link]();
Page | 25
.
Main Form

private void btnDashbord_Click(object sender, EventArgs e)

{
[Link] = "Dashboard";
[Link]();
Home Dashboard_vrb = new Home() { Dock = [Link], TopLevel = false,
TopMost = true };
Dashboard_vrb.FormBorderStyle = [Link];
[Link](Dashboard_vrb);
Dashboard_vrb.Show();

private void Staffbtn(object sender, EventArgs e)

{

[Link] = "Rooms";
[Link]();
Rooms Dashboard_vrb = new Rooms() { Dock = [Link], TopLevel =
false, TopMost = true };
Dashboard_vrb.FormBorderStyle = [Link];
[Link](Dashboard_vrb);
Dashboard_vrb.Show();

Page | 26
Clients

ADD

private void guna2Button4_Click(object sender, EventArgs e)

{
if ([Link] == [Link] || [Link] ==
[Link])
{

[Link]("please do not allowed blank space");

}
else
{

try
{
if ([Link] == [Link])
[Link]();
SqlCommand cmd = new SqlCommand("insert into Client values('" +
[Link] + "','" + [Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link]() + "')", Con);
[Link]();
[Link]();
[Link]("Client Added Successfull");
Page | 27
 DatadisplayClient();

}
catch (Exception ex)
{
[Link]([Link]);
}

}
displaydata();
cleardata();
}

UPDATE

private void updatebtn_Click(object sender, EventArgs e)

{
if ( [Link] == [Link])
{

[Link]("please do not allowed blank space");

}
else
{
DialogResult Remove = [Link]([Link], "Are you sure to
update ", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{

try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = @"Update Client Set ClientName = '" +
[Link] + "', ClientPhone = '" + [Link] + "',ClientAddress='" +
[Link] + "',ReservClients='" + [Link] + "' , Gender ='" +
[Link]() + "' where ClientID ='" + [Link] + "'
";
[Link]();
[Link]();
[Link]("Success updated ");

[Link]();

Page | 28
 }
catch (Exception ex)
{
[Link]([Link], "Error",
[Link], [Link]);
}
}
}
displaydata();
cleardata();

DELETE

private void deletebtn_Click(object sender, EventArgs e)

{
{

DialogResult Remove = [Link]([Link], "Are you sure

to delete", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{
try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = "Delete From Client Where ClientName = '"
+ [Link] + "'";
[Link]();
[Link]();

[Link]("delete successfully");
[Link]();

catch (Exception ex)

{
[Link]([Link], "Error",
[Link], [Link]);
}

}
}

Page | 29
 displaydata();
cleardata();
}

STAFF

ADD

private void staffAddbtn_Click(object sender, EventArgs e)

{
if ([Link] == [Link] || [Link] == [Link])
{

[Link]("please do not allowed blank space");

}
else
{

try
{
if ([Link] == [Link])
[Link]();
SqlCommand cmd = new SqlCommand("insert into Staffs values('" +
[Link] + "','" + [Link] + "','" + [Link] +

Page | 30
 "','"+[Link]+"','"+[Link]+"','" +
[Link]() + "','" + [Link] + "')", Con);
[Link]();
[Link]();
[Link]("Staff Added Successfull");

}
catch (Exception ex)
{
[Link]([Link]);
}

}
displaydata();
cleardata();

UPDATE

private void staffupdatebtn_Click(object sender, EventArgs e)

{
if ([Link] == [Link])
{

[Link]("please do not allowed blank space");

}
else
{
DialogResult Remove = [Link]([Link], "Are you sure to
update ", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{

try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = @"Update Staffs Set StaffName = '" +
[Link] + "', StaffPhone = '" + [Link] + "',StaffAddress =
'"+[Link]+"',Salary ='"+[Link]+"' , Gender= '" +
[Link]() +"' , Password = '" + [Link] + "'
where StaffID ='" + [Link] + "' ";
[Link]();
[Link]();
[Link]("Success updated ");

Page | 31
 [Link]();

}
catch (Exception ex)
{
[Link]([Link], "Error",
[Link], [Link]);
}
}
}
displaydata();
cleardata();
}

DELETE

private void staffdeletebtn_Click(object sender, EventArgs e)

{
{

DialogResult Remove = [Link]([Link], "Are you sure to

delete", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{
try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = "Delete From Staffs Where StaffID = '" +
[Link] + "'";
[Link]();
[Link]();

[Link]("delete successfully");
[Link]();

catch (Exception ex)

{
[Link]([Link], "Error",
[Link], [Link]);
}

}
}
displaydata();
Page | 32
 cleardata();
}

PAYMENTS

ADD

private void BookAddbtn_Click(object sender, EventArgs e)

{

if ([Link] == [Link] || [Link] == [Link])

{

[Link]("please do not allowed blank space");

}
else
{

try
{

if ([Link] == [Link])
[Link]();

Page | 33
 SqlCommand cmd = new SqlCommand("insert into Payment values('" +
[Link] + "','" + [Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" + [Link] +
"','" + [Link] + "')", Con);
[Link]();
[Link]();
[Link](" Payment Added Successfull");

}
catch (Exception ex)
{
[Link]([Link]);
}

}
displaydata();
cleardata();

UPDATE

private void payupdatebtn_Click(object sender, EventArgs e)

{
if ([Link] == [Link])
{

[Link]("please do not allowed blank space");

}
else
{
DialogResult Remove = [Link]([Link], "Are you sure to
update ", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{

try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = @"Update Payment Set PayID = '" +
[Link] + "',BookID ='" + [Link] + "',ClientName = '" +
[Link] + "', ClientAddress = '" + [Link] + "',Gender='" +
Page | 34
 [Link] + "' , RoomNo ='" + [Link] + "',RoomType ='" +
payroomtypetxt + "',RoomPrice = '" + [Link] + "',PaymentType='" +
[Link] + "' , Payment ='" + [Link] + "'";
[Link]();
[Link]();
[Link]("Success updated ");

[Link]();

}
catch (Exception ex)
{
[Link]([Link], "Error",
[Link], [Link]);
}
}
}
displaydata();
cleardata();
}

DELETE

private void paydeletebtn_Click(object sender, EventArgs e)

{

DialogResult Remove = [Link]([Link], "Are you sure to

delete", [Link], [Link]);
if (Remove == [Link])
{

}
if (Remove == [Link])
{
try
{
if ([Link] == [Link])
[Link]();
SqlCommand scmd = [Link]();
[Link] = [Link];
[Link] = "Delete From Payment Where PayID = '" +
[Link] + "'";
[Link]();
[Link]();

[Link]("Delete successfully");
[Link]();

catch (Exception ex)

Page | 35
 {
[Link]([Link], "Error",
[Link], [Link]);
}

}
}

displaydata();
cleardata();
}

PRINT

private void btnName_Click(object sender, EventArgs e)

{
using (ReportPayment st = new ReportPayment())
{
[Link]();
}
}

private void pictureBox1_Click(object sender, EventArgs e)

{
[Link]();
string myquery = "select * from Payment where PayID = '" +
[Link] + "' ";
SqlDataAdapter da = new SqlDataAdapter(myquery, Con);
SqlCommandBuilder cbuilder = new SqlCommandBuilder(da);
var ds = new DataSet();
[Link](ds);
[Link] = [Link][0];

[Link]();

Page | 36
4.1.2Refer to DFDs, process description, ERDs

Register information

MAIN OFFICE CLIENT

Regestration

Payment info

Every client has

ID

payments

Page | 37
4.2 User manual
The system will have user accounts for its users. The passwords will be encrypted. To protected

and will be kept for access to the system.

There is no such functionality in the system by which the user can register himself to the system.

This is because there are only five users in the system apart from the system administrator, so the

user accounts are created by the system administrator.

The system administrator can activate, deactivate, create, edit and delete user accounts, because

every once in a number of years the user 1 or the user 2 may be changed, but the user names for

them will be constant. The new user will have to do is to change the passwords for Him/herself

Page | 38
 Chapter Five
Project Conclusion

5.1 Future work:

We will be upgrading with new visions and design that better than this part Now we can’t able to

upgrading due to time and our techniques when we reach our hope We will produce new versions

that is the best this one this software will make more update in reality for all that reasons it made to

make an update placed and make advanced this software works only offline It may have not

attractiveness graphical interface that attractive with the user, for the future will update it and we

will add more additional interfaces that make the software more attractive,

39 | P a g e
The interfaces that will update is:
✓ Graphic interface

✓ Labels and their interfaces

✓ Controls and their interface structure

✓ Colors and user interfaces

The system of design it will be need to edit, remove and save more extra thing like:

✓ Camera

40 | P a g e
5.2 Conclusions:

The system has been developed using C# and SQL Server, the system was able to process and

update the database with more ease. It helped in developing a total integrated system.

This the project “Canadian Dental Management System” can be altered in accordance with the

future requirements of the organization. After we have completed the project we are sure the

problems in the existing system would Overcome. The “Canadian Dental Management System”

process made computerized to reduce human errors and to increase the efficiency. The main

focus of this project is to lessen human efforts. The maintenance of the records is made efficient,

as all the records are stored in the SQL SERVER database, through which data can be retrieved

easily. The navigation control is provided in all the forms to navigate through the large amount

of records. If the numbers of records are very large then user has to just type in the search string

and user gets the results immediately. The editing is also made simpler. The user has to just type

in the required field and press the update button to update the desired field.

41 | P a g e
5.3 Reference
Online collecting information’s
[Link]
[Link]
Some teachers of tisqaad

[Link]

[Link]

[Link] and some previous books of thesis books.

42 | P a g e