Conference Room Booking System

TABLE-CONTENT
S.NO CONTENT PAGE NO

1. Introduction 2
2. Requirement Specification 6
3. Software Description 8
4. System Design 12
5. System Testing 15
6. ER Diagram 20
7. Form Layout 22
8. Table Structure 26
9. Source Code 28
10. Conclusion 41
11. Bibliography 43
1
INTRODUCTION
2
INTRODUCTION:
Web based meeting scheduler project is implemented in java platform using MYSQL database as
back end application. Main aim of this project is to develop an online application through which
users can easily communicate and schedule appointment for online meetings. This application is
designed for organizations where communication between employees, project leaders and clients
are important.
This application is implemented in eleven modules admin, login, user management, host
meeting, meeting room booking, view minutes, conference bridge call booking and cancelation
of meetings, view meetings and notifications.
The main objective of this project is to provide Conference Hall Booking and Check Date and
Check status of the Booking. The customers have to register themselves in order to Use the
service. Once a user have to select the date and check the available status. User has to check the
Booking status of the user if it accepted we can go to the Conference Hall.
3
ABOUT THE PROJECT:
Web based meeting scheduler project is implemented in java platform using MYSQL database as
back end application. Main aim of this project is to develop an online application through which
users can easily communicate and schedule appointment for online meetings. This application is
designed for organizations where communication between employees, project leaders and
client’s details are important.
This application is implemented in eleven modules admin, login, user management, host
meeting, meeting room booking, view minutes, conference bridge call booking and cancelation
of meetings, view meetings and notifications.
Admin:
Using this module user can manage meeting rooms, lock and unlock users account and arrange
meetings and host meetings.
Registration:
If you are the new user going to login into the application then you have to register first by
providing necessary details. After successful completion of sign up process, the user has to login
into the application by providing username and exact password.
Admin Login:
The Admin has to provide exact username and password which was provided at the time of
registration, if login success means it will take up to main page else it will remain in the login
page itself.
Login:
The user has to provide exact username and password which was provided at the time of
registration, if login success means it will take up to main page else it will remain in the login
page itself.
Check for Available Hall:

After registration user can apply for Conference Hall by selecting the date and the make payment
if they want to book the Conference Hall.
Book with Payment:

User Apply for the Booking in the Date and Conference hall and Check for the status of the
Booking.
4
User Management:
This module is for users to manage their account information like changing user name and
password and registering new users and other security features. Security is provided for user
passwords and if users miss three login failures account will be blocked.
Host Meeting:
Using this module user can arrange meeting schedules by taking basic details like data, time,
subject, agenda and comments. For every new meeting user is provided with unique id which
will be useful as reference. Using this meeting id booking rooms and other operations are inter-
linked. User will be provided with new screen for booking and bridge calls.
Meeting Room Bookings:

Using this module user can book room from meeting room. User is providing with available and
booking rooms details and user need to fill online form for online booking. Other module details
are explained in the project documentation which can be downloaded from below link.
Check Booking List:

After login Admin can get the user details. That will provide in-between services with
description.
Add New Conference Hall:

After login Admin can add new Conference Hall to the list So the user can select it from the
Applying Booking.
Maintain the details:

After successful authentication admin can view the registered user details, Employee details and
can make any update.
5
REQUIREMENT
SPECIFICTION
6
HARDWARE REQUIREMENTS:
1. Processor : Intel-AMD.
2. Processor speed : 1.5-GHz.
3. RAM : 2GB.
4. Monitor : LCD Monitor.
5. Hard Disk : 350GB.
6. Display Card : VGA.
7. Keyboard : Standard Keyboard.
8. Mouse : Optical Mouse.
SOFTWARE REQUIREMENTS:
1. Front end : HTML, CSS, ASP.NET, C#.
2. Back end : MYSQL.
3. Server : Browser.
4. Windows : Windows 7/8/10.
7
SOFTWARE DESCRIPTION
8
ABOUT THE FRONT END:
HTML
Hyper Text Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms a triad
of cornerstone technology for the world wide web. Web browsers receive Html documents from
a web server or from local storage and render them into multimedia web pages. Html describes
the structures of the web page semantically and originally included cues for the appearance of
the document.
Html elements are the building blocks of html pages with the Html constructs, Images and other
objects, such as interactive forms, may be embedded into the rendered pages. It provides a means
of interactive forms, may create structured documents by donating structural semantics for text
such as headings, paragraph, lines, links, quotes and other items. Html elements are delineated
by tags, written using angle brackets, Browser do not display Html tags, but use them to interrupt
the content of the page.
Html can embed the program written in scripting language such as JavaScript which affects the
behaviour of web pages. Inclusion of CSS defines the look and layout of the content. The world
wide web Consortium (W3C), maintains the Html and CSS standards, has the use of CSS over
explicit Presentational Html, since 1997.
CSS
Cascading style sheets (CSS) is a style sheet language used for describing the presentation of
the document written in markup language. Although the most often used to visualize the style of
the web page and user interfere written in HTML and XHTML, the language can be applied to
any xml document, including plain XML, SVG, XUL. And it is applicable to rendering in speech
or other media. Along with HTML and JavaScript user interfaces for web applications and user
interfaces for many mobile applications.
CSS is designed primarily to enable the separation of presentation and content, including
aspects such as the layout, colour, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specifications of presentation characteristics and
enable to reduce complexity and repetition in structural content.
9
ASP.NET
ASP.NET is an open-source server-side web application framework designed for web
development to produce dynamic web pages. It was developed by Microsoft to allow
programmers to build dynamic web sites, web applications and web services. It was first released
in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's
Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime
(CLR), allowing programmers to write ASP.NET code using any supported .NET language. The
ASP.NET SOAP extension framework allows ASP.NET components to process SOAP
messages. ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a
modular web framework, together with other frameworks like Entity Framework. The new
framework uses the new open-source .NET Compiler Platform (codename "Roslyn") and is cross
platform. ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages (a platform using
only Razor pages) have merged into a unified MVC 6.
C#:
C# is a general-purpose, modern and object-oriented programming language pronounced as “C
sharp”. It was developed by Microsoft led by Anders Hejlsberg and his team within the .Net
initiative and was approved by European Computer Manufacturers Association (ECMA) and
International Standards Organization (ISO). C# is among the languages for Common Language
Infrastructure and the current version of C# is version 7.2. C# is a lot similar to Java syntactically
and is easy for the users who have knowledge of C, C++ or Java. A bit about .Net
Framework.Net applications are multi-platform applications and framework can be used from
languages like C++, C#, Visual Basic, COBOL etc. It is designed in a manner so that other
languages can use it.
10
ABOUT THE BACK-END:
MYSQL
MySQL is an open source relational database management system (RDBMS). Its name is
combinations of “My”, the name of co-founder Michael Widenius's daughter, and "SQL", the
abbreviation for Structured Query Language. MySQL is free and open-source software under the
terms of the GNU General Public License, and is also available under a variety of proprietary
licenses. MySQL was owned and sponsored by the Swedish company MySQL AB, which was
bought by Sun Microsystems (now Oracle Corporation). In 2010, when Oracle acquired Sun,
Widenius forked the open-source MySQL project to create MariaDB.
MySQL is a component of the LAMP web application software stack (and others), which is an
acronym for Linux, Apache, MySQL, Perl/PHP/Python. MySQL is used by many database-
driven web applications, including Drupal, Joomla, php BB, and Word Press. MySQL is also
used by many popular websites, including Google.
MySQL is written in C and C++. Its SQL parser is written in yacc, but it uses a home
brewed lexical analyzer. MySQL works on many system platforms, including AIX, BSDi,
FreeBSD, HP-UX, eComStation, i5/OS, IRIX, Linux, macOS, Microsoft Windows, NetBSD,
Novell NetWare, OpenBSD, OpenSolaris, OS/2 Warp, QNX, Oracle, Solaris, Symbian,
SunOS, SCO Open Server, SCO UnixWare, Sanos and Tru64. A port of MySQL to
OpenVMS also exists. The MySQL server software itself and the client libraries use dual-
licensing distribution. They are offered under GPL version 2.
Support can be obtained from the official manual. Free support additionally is available in
different IRC channels and forums. Oracle offers paid support via its MySQL Enterprise
products. They differ in the scope of services and in price. Additionally, a number of third party
organizations exist to provide support and services, including MariaDB and Percona.
MySQL has received positive reviews, and reviewers noticed it "performs extremely well in the
average case" and that the "developer interfaces are there, and the documentation (not to mention
feedback in the real world via Web sites and the like) is very, very good". It has also been tested
to be a "fast, stable and true multi-user, multi-threaded sql database server.
MySQL has received positive reviews, and reviewers noticed it "performs extremely well in the
average case" and that the "developer interfaces are there, and the documentation (not to mention
feedback in the real world via Web sites and the like) is very, very good". It has also been tested
to be a "fast, stable and true multi-user, multi-threaded sql database server".
11
SYSTEM DESIGN
12
SYSTEM DESGIN:
System design is the process of designing the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system. System Analysis is the process that decomposes a system into its
component pieces for the purpose of defining how well those components interact to accomplish
the set requirements.
The purpose of the System Design process is to provide sufficient detailed data and information
about the system and its system elements to enable the implementation consistent with
architectural entities as defined in models and views of the system architecture.
PHYSICAL DESIGN:
The physical design is a kind of system design. It is a graphical illustration of the system,
representing external and internal entities of the system with to and fro data flow. An external
entity is an entity exterior to the system and internal entity is a entity inside the system where
both can convert the data. In fact, the physical design is related to the concrete input and output
of the system. This deals with how the input data is provided, how the input is processed, and
how the output is displayed. In other words, the physical design can be generally classified into
the following sub tasks:
1. User–Interface designing step.
2. Data designing step.
3. Process designing step.
User Interface Design:

This step concerns about how the user adds information to the system and also how the system
gives the information back to the user.
Data Design:
This step concerns about how the data is represented and how it is stored in the system .
Process Design:
This step concerns about how the data traverses through the system and how it is validated,
transformed, and secured as it run in and out of the system. Example: The physical design of a
personal computer. The input data is given through the “Keyboard”, the data is processed in the
“CPU”, and finally, the output is displayed through the “Monitor”.
13
LOGICAL DESIGN:
Logical database design is the process of determining the logical data structures needed to
support an organization's information resource. The logical design process helps you to
implement a database that satisfies the requirements of your business organization. Logical
design is critical to the implementation of a corporate database. If your logical design is
incomplete or has flaws, making changes to the means of data collection, storage, and protection
can be costly later on. By using a well-conceived preliminary design, you can easily implement
and test a database. A sound logical design therefore helps to ensure a successful
implementation.
INPUT DEGIGN:
Input facilities the entry of data into the computer system. Input design involves the selection of
the best strategy for getting data into the computer system at the right time and as accurately as
possible. This is because the most difficult aspect of input design in accuracy .The use of well-
defined documents can encourage users to record data accurately without omission. For example,
if a customer's telephone number is a needed input data, the sales order form should have a
specific line that is clearly labelled "customer telephone number". Having several lines labelled
"customer information" would be less effective. This is because sometimes only the name and
address would be filled in leaving out the telephone number.
OUTPUT DESIGN:
A Design Output is a drawing or specification or manufacturing instruction. Design Outputs
describe all the components, parts, and pieces that go into your medical device. Design Outputs
describe all assemblies and sub-assemblies of your product. Think of it like this. If you were
tasked with assembling a medical device from scratch, what documentation would you need to
do so? All this documentation that you would need Design Outputs.
CODE DESIGN:
Once the output requirements determined, the system designer can decide what to include in the
system and how to structure it and the requirements output can be produced. The output forms or
the screen used in the system are required for viewing and reporting the system.
14
SYSTEM TESTING
15
TESTING:
The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies and/or a finished product. It is the process of exercising
software with the intent of ensuring that the software system meets its requirements and user
expectations and does not fail in an unacceptable manner. There are various types of test. Each
test type addresses a specific testing requirement.
DEVELOPING METHODOLOGIES:
The test process is initiated by developing a comprehensive plan to test the general functionality
and special features on a variety of platform combinations. Strict quality control procedures are
used. The process verifies that the application meets the requirements specified in the system
requirements document and is bug free. The following are the considerations used to develop the
framework from developing the testing methodologies.
TYPES OF TESTING:
1. Unit Testing:
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program input produces valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.
2. Functional Testing:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.
Functional testing is centred on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures : interfacing systems or procedures must be invoked.
16
3. System Testing:
System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.
“The process of performing a variety of tests on a system to explore functionality or to

identify the problems” system testing is usually required before and after a system is put in
place. A series of systematic procedures are referred to while testing is being performed. These
procedures tell the tester how the system should perform and where common mistakes may be
found.
Testers usually try to "break the system" by entering data that may cause the system to
malfunction or return incorrect information. For example, a tester may put in a city in a search
engine designed to only accept states, to see how the system will respond to the incorrect input.
4. Performance Test:
The Performance test ensures that the output is produced within the time limits, and the time
taken by the system for compiling, giving response to the users and request being send to the
system for to retrieve the results. Performance testing is the process of determining the speed or
effectiveness of a computer, network, software program or device. This process can involve
quantitative tests done in a lab, such as measuring the response time or the number of MIPS
(millions of instructions per second) at which a system functions.
Qualitative attributes such as reliability, scalability and interoperability may also be evaluated.
Performance testing is often done in conjunction with stress testing. Performance testing can
verify that a system meets the specifications claimed by its manufacturer or vendor. The process
can compare two or more devices or programs in terms of parameters such as speed, data transfer
rate, bandwidth, throughput.
17
5. Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation
by the end user. It also ensures that the system meets the functional requirements. Acceptance
testing is a final stage of testing that is performed on a system prior to the system being delivered
to a live environment. Systems subjected to acceptance testing might include such deliverables as
a software system or a mechanical hardware system. Acceptance tests are generally performed as
"black box" tests. Black box testing means that the tester uses specified inputs into the system
and verifies that the resulting outputs are correct, without knowledge of the system's internal
workings.
User acceptance testing (UAT) is the term used when the acceptance tests are performed by the
person or persons who will be using the live system once it is delivered. If the system is being
built or developed by an external supplier, this is sometimes called customer acceptance testing
(CAT). The UAT or CAT acts as a final confirmation that the system is ready for go-live. A
successful acceptance test at this stage may be a contractual requirement prior to the system
being signed off by the client.
Acceptance testing for Data Synchronization:
 The Acknowledgements will be received by the Sender Node after the Packets are
received by the Destination Node.
 The Route add operation is done only when there is a Route request in need.
 The Status of Nodes information is done automatically in the Cache Updating process.
2. Integration Testing:
Software integration testing is the incremental integration testing of two or more integrated
software components on a single platform to produce failures caused by interface defects. The
task of the integration test is to check that components or software applications, e.g. components
in a software system or – one step up – software applications at the company level – interact
without error. Objective of Integration testing is to make sure that the interaction of two or more
components produces results that satisfy functional requirement. In integration testing, test cases
are developed with the express purpose of exercising the interface between the components.
Integration testing can also be treated as testing assumption of fellow programmer. During the
coding phase, lots of assumptions are made. Assumptions can be made for how you will receive
data from different components and how you have to pass data to different components.
18
3. Validation Testing:
This provides the final assurance that the software meets all functional, behavioural and
performance requirements. The software is completely assembled as a package. Validation
succeeds when the software functions in manner in which the user expects. Validation refers to
processor using software in an alive environment in order to find errors. During the course of
validating the system, failures may occur and sometimes the coding has to be changed according
to the requirement. Thus the feedback from the validation phase generally produces changes in
the software. Once the application was made free all at logical and interdict errors. Inputting
dummy data ensured that the software developed satisfied all the requirements of the user.
4. Output Testing:
 After performing the validation testing, the next step is output testing of the proposed
system since no system could be useful If It does not produce the required output
generated or considered into two ways; one is on screen and another is printed format.
 The output format on the screen is found to be correct as the format was designed in the
system design phase according to the user needs. For the hard copy also the output comes
out as the specified requirements by the user hence output testing does not result in any
correction in the system.
5. Build Plan Testing:

Any project can be divided into units that can be further performed for detailed processing. Then
a testing strategy for each of this unit is carried out. Unit testing helps to identity the possible
bugs in the individual component, so the component that has bugs can be identified and can be
rectified from errors.
19
ER DIAGRAM
20
ER DIAGRAM:
In software engineering, an entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modelling is a database modelling method, used to
produce a type of conceptual schema or semantic data model of a system, often a relational
database, and its requirements in a top-down fashion. Diagrams created by this process are called
entity-relationship diagrams, ER diagrams or ERDs.
An entity –relationship (ER) diagram is a specialized graphic that illustrates the relationship
between entities in a database. ER diagrams often use symbols to represent three different types
of information. Boxes are commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes.
21
FORM LAYOUT
22
Form-1:
User Login Form
RORM-2:
User Registration Form
23
FORM-3:
Logged User Form
FORM-4:
Admin Login Form
24
FORM-5:
Add Conference Hall Form
25
TABLE STRUCTURE
26
USER REGISTRATION TABLE:
HALL DETAILS TABLE:
BOOKING DETAILS TABLE:
27
SOURCE CODE
28
INDEX.C#:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
public partial class Registration : System.Web.UI.Page
{
SqlConnection con = new
SqlConnection(ConfigurationManager.ConnectionStrings["conn"].ConnectionString);
protected void Page_Load(object sender, EventArgs e)
{
txtuserid.Text = "USER-0" + ID();
txtuserid.ReadOnly = true;
}
public int ID()
{
con.Open();
int ID = 0;
SqlCommand cmd = new SqlCommand("select count (*) from userregister", con);
ID = Convert.ToInt32(cmd.ExecuteScalar()) + 1;
con.Close();
return ID;
}
protected void Button1_Click1(object sender, EventArgs e)
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into userregister
(userid,firstname,lastname,gender,dob,mobno,address,emailid,confirmpassword) values('" +
txtuserid.Text + "','" + TextBox1.Text + "','" + TextBox2.Text + "','" +
DropDownList1.SelectedValue + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" +
TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox9.Text + "') ", con);
cmd.ExecuteNonQuery();
con.Close();
TextBox1.Text = "";
TextBox2.Text = "";
DropDownList1.SelectedValue = "";
TextBox4.Text = "";
TextBox5.Text = "";
29
TextBox6.Text = "";
TextBox7.Text = "";
TextBox9.Text = "";
SqlDataAdapter da = new SqlDataAdapter("select * from userregister where userid='" +

txtuserid.Text + "'", con);
DataTable dt = new DataTable();
da.Fill(dt);
if (dt.Rows.Count > 0)
{
Session["userid"] = dt.Rows[0]["userid"].ToString();
ClientScript.RegisterStartupScript(Page.GetType(), "validation", "<script
language='javascript'>alert('Record Inserted
Successfully');window.location='Login.aspx';</script>");
}
}
protected void Button2_Click(object sender, EventArgs e)
{
Response.Redirect("Login.aspx");
}
}
USER REGISTER:
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Registration : System.Web.UI.Page
{
{
txtuserid.Text = "USER-0" + ID();
txtuserid.ReadOnly = true;
}
public int ID()
{
con.Open();
int ID = 0;
30
SqlCommand cmd = new SqlCommand("select count (*) from userregister", con);
con.Close();
return ID;
}
protected void Button1_Click1(object sender, EventArgs e)
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into userregister
(userid,firstname,lastname,gender,dob,mobno,address,emailid,confirmpassword) values('" +
txtuserid.Text + "','" + TextBox1.Text + "','" + TextBox2.Text + "','" +
DropDownList1.SelectedValue + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" +
TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox9.Text + "') ", con);
con.Close();
TextBox1.Text = "";
TextBox2.Text = "";
DropDownList1.SelectedValue = "";
TextBox4.Text = "";
TextBox5.Text = "";
TextBox6.Text = "";
TextBox7.Text = "";
TextBox9.Text = "";
SqlDataAdapter da = new SqlDataAdapter("select * from userregister where userid='" +

txtuserid.Text + "'", con);
da.Fill(dt);
{
Session["userid"] = dt.Rows[0]["userid"].ToString();
Successfully');window.location='Login.aspx';</script>");
}
}
{
Response.Redirect("Login.aspx");
}
}
UAER LOGIN:
31
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Login : System.Web.UI.Page

{
{
}
{
SqlDataAdapter da = new SqlDataAdapter("select * from userregister where userid= '" +
txtusername.Text + "'and confirmpassword= '" + txtpwd.Text + "'", con);
da.Fill(dt);
{
Session["userid"] = txtusername.Text;
//Response.Redirect("Logeduser.aspx");
language='javascript'>alert('LogedIn
Successfully');window.location='Logeduser.aspx';</script>");
}
else
{
language='javascript'>alert('UserID and password does not exist');</script>");
//Response.Write("UserID and password does not exist");
}
}
}
ADMIN LOGIN:
using System;
using System.Linq;
32
using System.Web;
public partial class Admin : System.Web.UI.Page

{
{
}
{
if (TextBox1.Text == "Admin" && TextBox2.Text == "Admin")
{
//Response.Write("<script>alert('Login Successful')</script>");
//Response.Redirect("Adminpage.aspx");
Successfully');window.location='Adminpage.aspx';</script>");
}
else
{
//Response.Write("<script>alert('Login Failed!')</script>");
language='javascript'>alert('Login Failed!');</script>");
}
}
}
ADMIN PAGE:
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Adminpage : System.Web.UI.Page

{
33
{
Panel1.Visible = true;
Panel3.Visible = false;
txthallid.Text = "Hall-0" + ID();
txthallid.ReadOnly = true;
}
public int ID()
{
con.Open();
int ID = 0;
SqlCommand cmd = new SqlCommand("select count (*) from halldetails", con);
con.Close();
return ID;
}
{
cleartextbox();
}
public void cleartextbox()
{
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
}
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into halldetails values('" + txthallid.Text +
"','" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text +
"') ", con);
int i = cmd.ExecuteNonQuery();
if (i > 0)
{
ClientScript.RegisterStartupScript(Page.GetType(), "Validation", "<script
language='javascript'>alert('Added Successfully..');</script>");
con.Close();
}
cleartextbox();
34
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
LinkButton link = sender as LinkButton;
string[] s = link.CommandArgument.ToString().Split(',');
string a = s[0];
con.Open();
SqlCommand cmd = new SqlCommand("delete from halldetails where hallid='" + a + "' ",
con);
con.Close();
ScriptManager.RegisterStartupScript(this, this.GetType(), "Message", "alert(' Deleted
Successfully');", true);
halldetails();
}
public void halldetails()
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from halldetails", con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
da.Fill(dt);
GridView1.DataSource = dt;
GridView1.DataBind();
con.Close();
}
{
halldetails();
}
{
}
{
language='javascript'>alert('LogedOut Successfully');window.location='Admin.aspx';</script>");
}
35
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from bookinghalldetails ", con);
da.Fill(dt);
{
GridView2.Visible = true;
//Session["date"] = TextBox1.Text.ToString();
con.Close();
}
}
}
LOGGED USER:
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Logeduser: System.Web.UI.Page
{
{
if (!this.IsPostBack)
{
}
Label1.Visible = false;
Label2.Visible = false;
36
Button6.Visible = false; ;
txtuserid.Text = Session["userid"].ToString();
TextBox1.Text = Session["name"].ToString();
//Session["userid"] = Label1.Text;
halllocation();
}
public void halllocation()
{
if (!this.IsPostBack)
{
con.Open();
SqlCommand cmd = new SqlCommand("select DISTINCT city from halldetails", con);
da.Fill(dt);
{
DropDownList1.DataSource = dt; //cmd.ExecuteReader();
DropDownList1.DataTextField = "city";
DropDownList1.DataValueField = "city";
DropDownList1.DataBind();
con.Close();
DropDownList1.Items.Insert(0, new ListItem("Select From", "0"));

}
}
}
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from bookinghalldetails where hallname
like '%" + DropDownList2.SelectedItem.Text + "%' and date like '%" + TextBox4.Text + "%'",
con);
da.Fill(dt);
{
Label1.Visible = true;
Button6.Visible = false;
}
else
{
Label2.Visible = true;
37
Button6.Visible = true;
}
//con.Open();
//SqlCommand cmd = new SqlCommand("select * from bookingdetails where city like '%"
+ DropDownList1.SelectedItem.Text + "%' and too like '%" +
DropDownList2.SelectedItem.Text + "%'", con);
//SqlDataAdapter da = new SqlDataAdapter(cmd);
//DataTable dt = new DataTable();
//da.Fill(dt);
//if (dt.Rows.Count > 0)
//{
// GridView1.Visible = true;
// GridView1.DataSource = dt;
// GridView1.DataBind();
// Session["date"] = TextBox1.Text.ToString();
// con.Close();
//}
}
protected void DropDownList2_SelectedIndexChanged(object sender, EventArgs e)
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from halldetails where hallname like '%"
+ DropDownList2.SelectedItem.Text + "%' ", con);
da.Fill(dt);
{
TextBox3.Text = dt.Rows[0]["totalseat"].ToString();
TextBox2.Text = dt.Rows[0]["price"].ToString();
con.Close();
}
}
{
language='javascript'>alert('LogedOut Successfully');window.location='Login.aspx';</script>");
}
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)
{
if (DropDownList1.SelectedItem.Text != "Select From")
38
{
con.Open();
SqlCommand cmdd = new SqlCommand("select hallname from halldetails where city
='" + DropDownList1.SelectedItem.Text + "'", con);
SqlDataAdapter daa = new SqlDataAdapter(cmdd);
DataTable dtt = new DataTable();
daa.Fill(dtt);
if (dtt.Rows.Count > 0)
{
DropDownList2.DataSource = dtt; //cmd.ExecuteReader();
DropDownList2.DataTextField = "hallname";
DropDownList2.DataValueField = "hallname";
DropDownList2.DataBind();
DropDownList2.Items.Insert(0, new ListItem("Select From", "0"));
con.Close();
}
}
}
{
Button6.Visible = true;
con.Open();
SqlCommand cmd = new SqlCommand("insert into bookinghalldetails

(hallname,date,userid) values('" + DropDownList2.SelectedItem.Text + "','" + TextBox4.Text +
"','" + txtuserid.Text + "') ", con);
con.Close();
language='javascript'>alert('Booked Successfully');</script>");
}
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from bookinghalldetails where userid like
'%" + txtuserid.Text + "%' ", con);
da.Fill(dt);
{
GridView1.Visible = true;
39
//Session["date"] = TextBox1.Text.ToString();
con.Close();
}
else
{
language='javascript'>alert('No Booking Avilable');</script>");
}
}
{
}
}
40
CONCLUSION
41
CONCLUSION:
The aim of this project “The Conference Room Booking System” allows people to book the
conference rooms across multiple departments or other resources. The goals of this project are to
reserve conference room seats for auditors and providing the response to user by sending the
notifications through SMS or mail. This includes shared calendar management, unlimited users,
remote device management etc. Booking is done on the bases of time or period. It is flexible
for repeating booking and this system supports multiple languages. The system is easy for
implementation and maintenance. It is cost effective project and can be used in many
organizations.
In future, certain changes can be incorporated as per the requirements of the
organizations implementing the system. Those are: Search of free conference rooms whether
they are available in particular city. The system can provide the users with the facility of booking
more than one hall at the same time and by using his/her same user_id. The registered users can
get the notification of newly built conference rooms in particular areas.
42
BIBILIOGRAPHY
43
BIBILIOGRAPHY:
 Windows programming : Charles Petzoid.
 ASP. NET Unleashed : Stephen Walther.
 Visual Basic .NET Black Book : Steven Holzer.
 Professional ASP. NET Web services : Alex Homer, Dave Sussman.
 SQL Server Essential Reference : Sharon Dooley.
44

Conference Room Booking System

Uploaded by

Document Information

Original Title

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

Conference Room Booking System

Uploaded by

Copyright:

Available Formats

TABLE-CONTENT

S.NO CONTENT PAGE NO

Check for Available Hall:

Book with Payment:

Meeting Room Bookings:

Check Booking List:

Add New Conference Hall:

Maintain the details:

User Interface Design:

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

“The process of performing a variety of tests on a system to explore functionality or to

5. Build Plan Testing:

HALL DETAILS TABLE:

BOOKING DETAILS TABLE:

SqlDataAdapter da = new SqlDataAdapter("select * from userregister where userid='" +

SqlDataAdapter da = new SqlDataAdapter("select * from userregister where userid='" +

public partial class Login : System.Web.UI.Page

public partial class Admin : System.Web.UI.Page

public partial class Adminpage : System.Web.UI.Page

DropDownList1.Items.Insert(0, new ListItem("Select From", "0"));

SqlCommand cmd = new SqlCommand("insert into bookinghalldetails

 Windows programming : Charles Petzoid.

 ASP. NET Unleashed : Stephen Walther.

 Visual Basic .NET Black Book : Steven Holzer.

 Professional ASP. NET Web services : Alex Homer, Dave Sussman.

 SQL Server Essential Reference : Sharon Dooley.

You might also like