Final (1).pdf

TITLE OF THE PROJECT - COUNSELING BOOKING
MANAGEMENT SYSTEM
NAME – KRISHAN KUMAR
PROGRAME CODE - BACHELOR OF COMPUTER
ENROLLMENT NUMBER - 191808813
REGIONAL CENTER CODE - RC-39, NOIDA
COURSE CODE - BCSP-060
MOBILE NUMBER - 9068094705
EMAIL ID – nnkrishna714@gmail.com

INDIRA GANDHI NATIONAL OPEN
UNIVERSITY
Counseling Booking Management System
BY
Krishna Kumar
Enrollment number –191808813
Submitted to the school of Computer and Information sciences, IGNOU
In partial fulfillment of the requirement
For the award of the degree
Master of Computer Application (MCA)
INDIRA GANDHI NATIONAL OPEN UNIVERSITY
MAIDAN GARHI
NEW DELHI -110068

Manmohan Shakya
+ 91 80108 44344, + 91 8800 242 399 | manmohan.s2013@gmail.com
manmohan.shakya@icloud.com | k.manmohan (skype)
CTC: 9.3 LPA, Expected CTC: Negotiable | Official Notice Period: 60 days
Career Objective
Getting an opportunity to work for the organization where my skill & Knowledge can be utilized at
maximum and at the same time I can get an opportunity for career enhancement and professional
growth in this field.
Summary
- 9+ Years of experience in developing enterprise level Web/Windows based applications using
Microsoft .NET Technologies
- 3+ Years of experience in developing hybrid mobile apps using Flutter, Ionic, and Angular 2+.
Job Responsibilities
- Application Design and Coding: Develops program logic for new applications or analyzes and
modifies logic in existing applications based on the technical design and coding standards so as
to deliver error free output.
- Code Review.
- Integration and Unit Testing: Define unit test cases based on the technical design/functional
design in a way that is comprehensive and verifies accuracy of developed features.
- Execute the unit test cases defined to ensure error free execution and deploying it in the
development environment.
- Testing functionality in a controlled environment pre and post deployment.
- Perform documentation of different modules of application using Atlassian.
- Maintaining the systems once they are up and running.
- Sprint Planning and Backlog Refinements.
- Scrum/Daily Stand-ups.
Experience Summary
25th
July’16 – Till Date Midas IT Services (I) Pvt. Ltd. Delhi as Sr. Software Engineer
2nd
May’16 – 22nd
July’16 mCURA Health Care Pvt. Ltd. Gurgaon as Sr. Software Engineer
24th
Nov’11 – 29th
Apr’16 APTARA Inc. Noida as Software Engineer
9th
Dec’10 – 23rd
Nov’11 Planman Technologies Pvt. Ltd. New Delhi as Programmer
Education Summary
MCA from I.G.N.O.U. Delhi (2007–2011)
12th
from JNV Mainpuri, U.P. - CBSE (2002)
B. Sc. (Computer Science) from Dr. B.R.A.U. Agra (2002–2005)
10th
from JNV Mainpuri, U.P. - CBSE (2000)

Technical Skills
Languages/Domain
ASP.Net Core, ASP.Net API, ASP.Net MVC , Angular 2+, Ionic, Flutter, ReactJs,
AngularJs, C#, WCF, WPF, JavaScript, Bootstrap, HTML5, CSS3
Web Server IIS 6.0/7.0, IIS Express, Kestrel, & popular Web Browsers
Major Projects
Ontellus/MyKeais Web Portal | https://www.ontellus.com
Ontellus is specializes in retrieval of all types of records via subpoena and/or authorization. We
retrieve records from hospitals, clinics, pharmacies, personnel, insurance claims, business records,
Medicare, IRS, Social Security and all other private and government entities.
Tools/Technologies: ASP.Net Core 2.0, Java, SQL Server 2012/08, MongoDB, AngularJS, Bootstrap
Ontellus/Keais Packet Worker Windows Service
Packet Worker is used by MyKeais/Ontellus to generate packets to send different parties of
case/order based on firms and states.
Tools/Technologies: ASP.Net API 2.0, Entity Framework, SQL Server 2008, MongoDB
ImSafeNow App (iOS | Android)
I'mSafeNow aims to help women and children feel safe and secure through wearable technology
and a community of ''Network of Helpers''.
Tools/Technologies: Ionic 3, Angular 5, ASP.Net API 2.x, SQL Server 2016
Libraries/APIs: Google | Facebook Login, SMS Gateway, Push Notification, Google Direction API,
Email Verification, Geo Location, Social Media Sharing, Camera, Contacts, QR Code Scanner
System Software
Visual Studio, SSMS, VS Code, Swagger, nSwag Studio, DevExpress, Git,
TortoiseGit, Bitbucket, JIRA, Jenkins, Bamboo, MS Word, MS Excel
RDBMS/DBMS SQL Server 2016/2012/2008, MongoDB, SQLite, MS Access
Ontellus/Keais Template Builder Windows App
Template Builder is used to create/manage templates, packets, contacts and firms for
MyKeais/Ontellus; It is also used to print templates and packets in word and PDF format.
Tools/Technologies: ASP.Net API 2.0, Entity Framework, SQL Server 2008, MongoDB, DevExpress
Forms, Wix Toolset
Infield App (iOS | Android)
V5 Global is a container India composed business plan consulting and remaking affiliation that gives
an extensive gathering of organizations in the arrangements and displaying space.
Tools/Technologies: Flutter, Asp.Net API 2.0
Libraries/APIs: Push Notification, Geo Location, Camera, Contacts, SMS, Geo Location, SQLite.
AMEN Bizz App (iOS | Android)
MAZE Technologies is a professional web design and development company based in New York,
America. MAZE Technologies is a full-services provider for corporate or individual interested in
designing their design & development needs of web-based projects.
Tools/Technologies: Ionic 3, Angular 5
Libraries/APIs: SMS Gateway, Push Notification, Email Verification, Camera, Contacts

mCura Web Portal | API – WCF Services | http://mcura.com
mCURA is a silicon valley startup that is committed to bring the most excellent innovations to suit
the highly evolving healthcare IT domain. We strongly believe that the healthcare providers /
organizations should have all the relevant clinical data available to them anytime / anywhere, to
make the right decision. Built on this belief, "Enterprise Clinic Management Suite" presents the
right data at your FINGERTIPS.
Tools/Technologies: WCF Services, SQL Server 2008, jQuery, Bootstrap
WMS Web Portal | http://dswebsvr02.aptaracorp.com/aptarawms
WMS known as Workflow Management System widely used by APTARA and their vendors to
manage daily work flow, to generate different type of reports (like daily/weekly/monthly
production/revenue reports).
Team facilitator (FAC) can initiate/allocate jobs, the end user (PG) will automatically get respective
job on their portal. After completing, the job will be available for next stage and the respective PG
and FAC will automatically be informed
Tools/Technologies: ASP.Net, jQuery, SQL Server 2008
Trainings
6 months Advanced .Net MVC and AngularJS training from Croma Campus, Noida (Nov 2015)
Training on Email Educates by Aptara Inc. (May 2012)
Personal Profile
Name Manmohan Shakya
Strength Self-Motivating, Team Player, Learning habit, Honesty
Permanent Add 152, Village & Post- Daloopur, Dist. Mainpuri, U.P. – 205261
I hear by declare that the above information is true to the best of my knowledge.
Date: - ………………………………
Place: - (MANMOHAN SHAKYA)
6 months Training on ASP.Net, and SQL Server 2005 from MICM Shahadara Delhi (July 2010)
Date of Birth 10th Dec 1985
mCura Smart Card Printing Windows App
Smart Card Printing Application is specially used at patient registration window to print their smart
card; that smart card then then used for patient check in/check out and to maintain their record.
Tools/Technologies: WCF Services, WPF, WCF Services, SQL Server 2008
IEEE XML/HTML Conversion Application
It is used to convert raw XML into IEEE standard XML based on provided DTD, and converted XML
into IEEE standard HTML.
Tools/Technologies: C#, Windows Forms, Regex, XML
Managerial & Behavioral Training by Aptara Inc. (July 2012)
Hobbies Problem Solving, Trainings, Surfing, Listening to music

TITLE OF THE PROJECT
COUNSELING BOOKING
MANAGEMENT SYSTEM

3
Introduction:-
counseling booking Management System is a web based portal. Any registered user book
the counseling for next 30 days. This portal is design for an open university like IGNOU.
At presently this university has 5 counseling s. Every has facility for online counseling
including camera, computer, web link etc. There are multiple users who want to use these
facilities. They need to use the counseling booking Management System facility. A
registered user can do this. A counseling session is of 1 hour duration and can be performed
from 9 am to 6 am. User can book counseling for next 30 days only. A user is allowed to
book a maximum of 20 sessions in the slot of next 30 days. A session can also be cancelled,
but it should be done at least one day in advance.
In this system, there are two types of users known as counselor whose book the
counseling a
nd other user whose got counseling,this type of user is known as only user.
The counselors book the counseling and make payment through internet banking/credit
card etc.
Users take appointment and attend the counseling session. Counselors also perform
cancelation .He/she cancels the counseling session 1 day advance.

4
Objective:-
counseling booking Management System is a web based portal. It has following
objective:-
 Counseling is booked for 30 days.
 Only registered users can take counseling.
 Before counseling he/she got an appointment.
 Counselor book counseling s according to need and make payment.
 Registered user take counseling for making a payment of Rs 1000.
 Payment is valid for next 15 days.

5
CATEGORY OF THE PROJECT
RDBMS stands for Relation Database Management System. The RDBMS is responsible for:
1.) Maintaining the relationships between data in the database.
2.) Ensuring that data is stored correctly- that the rules defining the relationships
between data are not violated.
3.) Recovering all data to a point of known consistency in the event of a system
failure
4.) RDBMS also provides referential integrity i.e. Primary Key-Foreign Key and
Unique Key-Foreign Key.
SQL Server is designed to be a client server system. Client server systems are constructed
so that the database can reside on a control computer known as a Server and be shared
among several users.
SQL Server can work with thousands of client applications simultaneously.
Transact-SQL:-
SQL Server user Transact-SQL as its database query and programming language SQL is a
set of commands that allows the user to specify the information to be retrieved or modified
with Transact SQL. We can access data and query, update and manage relational database
system.

6
Module Description:-
counseling booking Management System has following modules:-
1. User: - This module performs the registration facilities. Any user, it he/she wants to
take counseling then first if all performs online registration and got a valid ID &
password. Through this ID he/she perform login and take appointment. After that
he/she got a counseling for any one counselor. The counselor name is selected by the
user.
2. Counselor :- This modules store the counselor list. Counselors also book the
counseling for next 30 days. Any counselor have the right to provide only 20
session in this 30 days.One session is 1 hour. At the booking time counselor pay
booking amount Rs 5000 as a security .This amount is referable. counselor make
payment to university. Payment is depend on candidate. 40% payments given to the
university and remaining 60% take by the counselor.
3. Counseling details: - This modules store the list ofcounseling s. Every counseling
hasa unique ID through this counselor book this s. All s have facility for online
counseling including camera, computer, web link etc.
4. Booking Handler: - This module is responsible to book the counseling .
Counselor book the for next 30 days. At the time of booking counselor pay Rs 5000
for advance. After that system generate a booking No.
5. Cancelation Master: -This module is responsible for doing cancelation. A counselor
cancels his/her counseling session before one day in advance.

7
6. Payment Master:-This module is responsible for handling project information
counselor make a payment for booking amount. User make a payment for getting
counseling.Payment made by with net booking credit card/Atm card etc.

8
Data Structure:-
Users Details
Name Type Size Description
U-ID Varcher 20 This is primary
key
Password Varcher 20 Used for
password
Name Varcher 30 Used for name
of the user
Address Varcher 500 Used for hold
address
Phone Numeric Used for storing
phone number
Email-ID Varcher 20 Used for storing
emailed
D-of-reg. Date/time Used for
storing date of
registration
Counselor Details

9
C-ID Varcher 20 This field is the
primary key.
Password Varcher 20 Used for store
password
Name Varcher 30 Used for
storing name
of
the counselor
Address Varcher 500 Hold address
Phone Numeric Store phone
number
Email-ID Varcher 20 Store emailed
Specialization Varcher 500 Hold the
specialization
of counselor
D-of-reg. Date/time store date of
registration
Counseling Master
ID Varcher 20 This is primary
key. This field
store statin

10
number.
Location Varcher 200 This field store
location of
counseling
.
Facilities type Varcher 200 Hold
information
about facilities
provided by
counseling
.
Address Varcher 500 Address of
counseling
Phone no. Numeric Store phone
number
Fax no. Numeric This field store
fax number of
counseling
.

11
Booking details
NAME TYPE SIZE Description
U_id Varchar 20 This is user id
through this
field ,table
connect with
userdetails.
C_id Varchar 20 This is
counselor ID.
Through this
field this table
linked with
counselor
details table.
_id Varchar 20 This field store
the information
of counseling .
Through this
field table
linked with

12
details
Bookingno Varchar 20 This is
booking id.
This field is
the primary
key
of this table.
BookingDate Date/Time This field store
the booking
details.
Time Date/time This field store
booking time.
Pay_id Varchar 30 This is
payment id
field. Through
this field table
linked with
payment
details.
Cancellation Details
U_id Varchar 20 This is userid

14
counselorid.
bookingid.
Cancilid Varchar 20 This is
cancilationid.
This is the
primary key.
Cancildate Date/time This field store
cancelation
date.
Canciltime Date/time This field store
cancelation
time.
Payid Varchar 30 This field store
payment
information.
Payment_Details
field.

15
counselor id
fields
Payid Varchar 30 This is
paymentid
fields
paytype Varchar 50 This field
describe
paymenttype
like
throug
h
creditcardetc
Amount Int This field hold
payment
amount
Date Date/time This field hold
payment date.
Time Date/time This field hold
time of payment

16
Appoitmentdetails
U_id varchar 20 This is userid
field
C_id varchar 20 This is
counselorid.
Payid varchar 30 This is
paymentid.
Ap_no varchar 30 This is
appointment
no. this is the
primary key
Date Date/time This is
appointmen
t date.
Time Date/time This is
appointmen
t time.
Duration Time This field store
time duration.

17
DATA FLOW DIAGRAM: - It is a graphical representation of flow of data
through a system. In this diagram, the external entities provide input data for the
processing. During the processing, some intermediate data is generating. After final
processing, the final output data is generating.
Rules of making DFD: - there are following seven rules for the construction of data
flow diagram
1) Arrow should not cross each other.
2) Square, circles, and files must bear names.
3) Decomposed data flow must be balance.
4) No two data flows, square or circles can have the same name.
5) Draw all data flows around the outside of the diagram.
6) Choose meaningful names for data flows processes and data stores.
7) Control information such as record counts, passwords and validation requirements
are not pertinent to a data flow diagram.
DFD are describe for different
level e.g.:
i. 0 level DFD
ii. 1 level DFD
iii. 2 level DFD

18
The symbols used in DFD are as follows: -
Symbol Name Description
Data flow
Representation the
connectivity between
process
Process
Performs some
processing of input
External
Entity
Define source or
destination of system
data.
or
Data store Repository of data

19
DFD
Counseling
booking
Management
System
Cancellation master
Counselor
Payment Master
Appotment
Booking Handler
User
Counseling
details

20
1st Level DFD
perform store
User
Registra
t ion
User_details
access
Take appoitment
Appoitm
ent store Appoitmen
t details
Perform
Counselor
Registratio
n
stor
e Counselordetails
Counselin
g details
see
counseling master
Booking
Handler Payment
master
Access
Cancilation
master
Access
Access Stor
e Store Store Access
Access
Bookingdetails Paymentdetails cancilataiondetails
counselor
User

21
Co
Co
Co
Co
Co
Co
Co
Co
Co
C
ou
u
u
u
u
u
u
u
u
un
n
n
n
n
n
n
n
n
n
s
selinselinselinselinselinselinselinselinselinselingggggggggg
mmmmmmmmmmananananananananananagagagagagagagagagageeeeeeeeeemmmmmmmmmmentententententententententent
Second Level DFD
Registration master
User Details
Counselor details
Registration
master
check Login Id and
password
If correct
Generate a
welcome
message. You
see the course
details
User/Counselor Inform toSorry, your
Id and
password is
User fill sing
up and
submit
Course
master
generate
Id and
password
store into
database User_details
counselordetails
College
master
Counseling
management
Take
appointment
acce
If
not
correct
Give
to
New
user
Login

22
ENTITY RELATIONSHIP - DIAGRAM
An ER diagram is a model that identifies the concept or entities that exist in a system and
the relationships between those entities. An ERD is often used as a way to visualize a
relational database: each entity represents a database table and the relationship lines
represents the key in one table that point to specific records in related tables.
Advantages of ER diagram
 Professional and faster Development.
 Productivity Improvement.
 Fewer Faults in Development.
 Maintenance becomes easy.

23
passwo
rd
U_ID
Name
user
Addres
s
phone
take
U_id
C_id
Appoitment
Pay_id
Apno
date
Cancilat
i n_id
U_id
C_id
_i d
id
location
for
time
addre
cancilationmaster ss
Bookingno
C_id
perfo
rm
Bookin
g
Handle
r
U_i
d
Ma
nag
Intera
ct
phone
no
Counselin
g
C_id
see
facilitie
stype
specialization
id
ammount C_id
Payment Mak
es
paytype
Counselo
r Add
r ess
Pay_id U_id password name

24
TESTING
Testing is the process to uncover the errors.
Objectives of Testing: -There are following
objectives:
i. Testing is the process of executing the program to find error.
ii. A group test has a high probability of finding the errors.
iii. A successful test uncovers the all errors that have not been found.
Testing Principal: -There are following objectives:
i. The test should be according to the customer’s requirement.
ii. There should be a planning for testing before it starts.
iii. Poreto principle implies that 80 percent of all errors uncover during testing will
likely be traceable to 20 percent of all program components.
iv. Testing should begin ‘in the small’ and progress toward testing ‘in the large’.
There are two types of testing: -
1. Black Box Testing
2. White Box Testing
1. Black Box Testing: -It is also called behavioral testing. The program is directly run by
the computer to find the errors.
Objective of the Black Box Testing
i. Incorrect or missing function.
ii. Interface error.
iii. Errors in data structures on database access.
iv. Performance error.
v. Initialization and termination error.

25
2. White Box Testing: -It is also called glass box testing. It traces all the paths of a
program manually to find the errors.
Advantage of White Box Testing
i. It guarantees that all independent paths have been checked at least once.
ii. It chicks all logical decisions for true and false.
iii. Executes all loops at their boundary values.
iv. Checks internal data structures.
Reasons for White Box Testing
i. It can find logical errors, which cannot be found by ‘black box’.
ii. We often believe that a logical path is not likely to be executed when, in fact, it may
be executed on a regular basis.
iii. Typographical errors are random. The block box testing can find out typing error
but typing error but typing error are in the program.

26
INPUT/OUTPUT REPORT :-
This page describe the format or layout of input/ output. This is tentative page, At this
time we design some pages format. At report submission time we design remaining page.
Home Page:- This is default page of our website. On this page there are following
options available like Counseling details, Counselor ,Registration, Login Option etc.
Registration page:- This Is the common page of counselor as well as user. At the time
of registration user select type like counselor or customer. And fill the details and select
user Id and Password.
Login page:-A registered user perform Login with help of this page.. On this page user
fill Login Id and password and click on submit button. On this page forget password link is
also available.
Counseling Details Page:- This page is handled by Admin. Admin Upload
counseling Details. On this page there are following details like Counseling , There
space, Location , Charge, Facilities etc. Counselor see this details and book Counseling
according to need.

27
Tools/Platform ,Hardware and Software requirement specification:-
Hardware
i. Processor – I3 5th Generation
ii. RAM -4 GB
iii. Hard disk – 500GB
iv. Keyboard
v. Mouse
vi. Printer
vii. Monitor – LCD (17 inch)
Software
i. Operating System - Windows 10
ii. Microsoft Visual Studio 2015
iii. SQL Server 2012
iv. Microsoft Office 2013

28
Limitation of the system
counseling booking Management System have some limitation. At presently this
system work only for one open university like IGNOU.

29
Future Scope
This project is more success in future ,because counseling is needed to all candidate whose
pass the12th class. After counseling student select appropriate courses.

2
INTRODUCTION:-
Counseling booking Management Systemis a web based portal. Any registered user book
the counseling station for next 30 days. This portal is design for an open university like
IGNOU. At presently this university has 5 counseling stations. Every station has facility for
online counseling including camera, computer, web link etc. There are multiple users who
want to use these facilities. They need to use the counseling booking Management
Systemfacility. A registered user can do this. A counseling session is of 1 hour duration and
can be performed from 9 am to 6 am. User can book counseling station for next 30 days
only. A user is allowed to book a maximum of 20 sessions in the slot of next 30 days. A
session can also be cancelled, but it should be done at least one day in advance.
In this system, there are two types of users known as counselor whose book the
counseling station and other user whose got counseling this type of user is known as only
user.
The counselors book the counseling station and make payment through internet
banking/credit card etc.Users take appointment and attend the counseling session.
Counselors also perform cancelation .He/she cancels the counseling session 1 day advance

3
OBJECTIVE OF THE PROJECT:- counseling station booking Management System is a
web based portal. It has following objective:-
 Counseling station is booked for 30 days.
 Only registered users can take counseling.
 Before counseling he/she got an appointment.
 Counselor book counseling stations according to need and make payment.
 Registered user take counseling for making a payment of Rs 1000.
 Payment is valid for next 15 days.

4
Tools/Platform ,Hardware and Software requirement specification:-
Hardware
1. Processor – I3 5th
Generation
2. RAM -4 GB
3. Hard disk – 500GB
4. Keyboard
5. Mouse
6. Printer
7. Monitor – LCD (17 inch)
Software
1. Operating System - Windows 10
2. Microsoft Visual Studio 2015
3. SQL Server 2012
4. Microsoft Office 2013

5
System Analysis:-
System Analysis by definition is a process of systematic investigation for the purpose of
gathering data, interpretin
g the facts, diagnosing the problem and using this information to either build a completely
new system or to recommend the improvements to the existing system. A satisfactory system
analysis involves the process of examining a business situation with the intent of improving
it through better methods and procedures. In its core sense, the analysis phase defines the
requirements of the system and the problems which user is trying to solve irrespective of
how the requirements would be accomplished.
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding
the details of an existing system or a proposed one and then deciding whether the proposed
system is desirable or not and whether the existing system needs improvements. Thus,
system analysis is the process of investigating a system, identifying problems, and using the
information to recommend improvements to the system.

6
Process Design of System Analysis

7
Feasibility Study
Types of feasibility
Technical Feasibility: -It is concerned with the availability of hardware and software
required for the development of the system. The
I. Feasibility is the determination of whether or not a project is worth doing. The process
followed in making this determination is called a feasibility technical needs of the
system may vary considerable, but might include:
 The facility to produce outputs in a given time.
 Response time under certain condition.
 Ability to process a certain volume of transaction at a particu
 Operational Feasibility: -Operational feasibility is all about problems that lar
speed.
 Facility to communication data to distinct location. may arise during operations.
There are two aspects related with this issue :-
 What is the probability that the solution developed may not be put to use or may
not work?
 What is the inclination of the management and end users towards the solution?
II. Economic Feasibility: -It is the measure of cost effectiveness of the project. The
economic feasibility is nothing but judging whether the possible benefit of solving the
problem is worth right or not.
III. Social Feasibility: -Social feasibility is determined a proposed project will be
acceptable to the people or not.
IV. Management Feasibility: -This type of feasibility determines a proposed project will
be acceptable to management. If Managements doesnot support or gives a negligible
support to it. The analyst will tend to view the project as a non feasible one.
V. Legal Feasibility: - Legal feasibility studies issues arising out of the need to the
development of the system. The possible consideration might include copyright law,
labour law, antitrust legislation, foreign trade, regulation etc.

8
VI. Time Feasibility: -Time feasibility is a determination of whether a proposed project
can be implemented fully within a stipulated time frame.

9
Fact Finding Techniques
To Study any system the analyst needs to do collect facts and all relevant information the
facts when expressed in quantitative form are termed as data. The success of any project is
depended upon the accuracy of available data. Accurate information can be collected with
help of certain methods/ techniques. These specific methods for finding information of the
system are termed as fact finding techniques. Interview, Questionnaire, Record View and
Observations are the different fact finding techniques used by the analyst. The analyst may
use more than one technique for investigation.
Interview
This method is used to collect the information from groups or individuals. Analyst selects the
people who are related with the system for the interview. In this method the analyst sits face
to face with the people and records their responses. The interviewer must plan in advance the
type of questions he/ she is going to ask and should be ready to answer any type of question.
He should also choose a suitable place and time which will be comfortable for the
respondent.
The information collected is quite accurate and reliable as the interviewer can clear and cross
check the doubts there itself. This method also helps gap the areas of misunderstandings and
help to discuss about the future problems. Structured and unstructured are the two sub
categories of Interview. Structured interview is more formal interview where fixed questions
are asked and specific information is collected whereas unstructured interview is more or
less like a casual conversation where in-depth areas topics are covered and other information
apart from the topic may also be obtained.
Questionnaire
It is the technique used to extract information from number of people. This method can be
adopted and used only by an skillful analyst. The Questionnaire consists of series of
questions framed together in logical manner. The questions are simple, clear and to the point.

10
This method is very useful for attaining information from people who are concerned with the
usage of the system and who are living in different countries. The questionnaire can be
mailed or send to people by post. This is the cheapest source of fact finding.
Record View
The information related to the system is published in the sources like newspapers,
magazines, journals, documents etc. This record review helps the analyst to get valuable
information about the system and the organization.
On-Site Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the
organization and observes and understand the flow of documents, working of the existing
system, the users of the system etc. For this method to be adopted it takes an analyst to
perform this job as he knows which points should be noticed and highlighted. In analyst may
observe the unwanted things as well and simply cause delay in the development of the new
system.

11
Scheduling
Gantt chart:
Basic planning uses bar charts that show project activities and the amount of time they
will take. This activity scheduling method was first introduced in 1914 by Henry L.
Gantt as a rudimentary aid to plot individual tasks against time. The Gantt chart uses
horizontal bars to show the durations of actions or tasks. The left end marks the
beginning of the tasks; the right end its finish. Earlier tasks appear in the upper left and
later ones in the lower right.

12
In planning this project, several steps are undertaken:
1. Identify the activities and tasks in the stage. Each activity must be identified to plan the
completion date and allocate responsibilities among members of the project team. In our
project, there are seven activities :
i. Understanding Project Requirement
ii. Designing Tables
iii. Designing Forms
iv. Coding
v. Report Designing
vi. Testing
vii. Implementation
2. Determine the tasks for each activity and the estimated completion times. Each activity is
broken down into several tasks.
3. Determine the total estimated time for each activity and obtain an agreement SAto
proceed.
4. Plot activities on a Gantt chart. All activities, tasks, and milestones are drawn on the
Gantt chart, with emphasis on simplicity and accuracy.
5. Review and record progress periodically. The actual amount of time spent on each
activity is recorded and compared with the budgeted times.

13
Program Evaluation and Review Technique (PERT)
Like the Gantt chart, PERT makes use of tasks. Like milestone charts, it shows
achievements. These achievements however are not task achievements. They are terminal
achievement, called events. Arrows are used to represent tasks and circles represent the
beginning or completion of a task. The PERT chart uses these paths and events to show the
interrelationships of project activities.
The events in my project can be categorised as:
1. Meeting to the Employees of company to understand the project.
2. Table Designing
3. Form Designing
4. Writing Codes
5. Designing Reports
6. Testing the project
7. Implementation of project
Each task is limited by an identifiable event. An event has no duration; it simply tells you
that the activity has ended or begun. Each task must have a beginning and an ending event. A
task can start only after the tasks depends on have been completed. PERT does not allow
“looping back” because a routing that goes back to a task does not end.
A PERT chart is valuable when a project is being planned. When the network is finished, the
next step is to determine the critical path. It is the longest path through the network. No task
on the critical path can be held up without delaying the start of the next tasks and, ultimately,
the completion of the project. So the critical path determines the project completion date.

14
System Requirements Specification (SRS)
It is a set of complete and precisely stated properties along with the constraints of the
system that the software must satisfy. A well designed software requirements
specification establishes boundaries and solution of system to develop useful software.
Requirements of SRS: -The SRS should specify only the external system
behavior and not the internal details. It also specifies any constraints imposed on
implementation. A good SRS is flexible to change and acts as a reference tool for
system developer, administrator and maintainer.
Characteristics of a SRS
a. All the requirements must be unambiguously.
b. It should be complete.
c. The requirements should be realistic and achievable with current technology.
d. It must be verifiable and consistent.
e. It should be modifiable.
f. It should be traceable to other requirements and related documents.
Rules for Specifying Software requirements
The following are the rules for specifying software requirements:
 Apply and use an industry standard to ensure that standard formats are used to
describe the requirements.
 Use standard models to specify functional relationships, data flow between the
systems and sub system and data structure to express complete requirements.
 Limit the structure of paragraphs to a list of individual sentences to increase the
tractability and modifiability of each requirement and to increase the ability to
check for completeness.

15
SRS of theProject Structure of a Typical SRS Document
1. Introduction : -
 System Reference and business objective of the document.
 Goals and objectives of the software, describing it in the context of the
computer base system.
 The scope of the document.
2. Information Description : -
 Information flow representation.
 Information context and structure representation.
 Description of sub system.
 Details of information flow context and structure are documents.
3. Functional Description of the System : -
 Functional description
 Restrictions/limitations
 Performance requirements
 Design constraints
 Diagrams to represent the overall structure of the software graphically.
4. Test and Validation Criteria : -
 Performance limitation , if any
 Expected software response
 It is essential that time and attention be given to this section.

16
Introduction
counseling booking Management Systemis a web based portal. Any registered user book the
counseling station for next 30 days. This portal is design for an open university like IGNOU.
At presently this university has 5 counseling stations. Every station has facility for online
counseling including camera, computer, web link etc. There are multiple users who want to
use these facilities. They need to use the counseling booking Management Systemfacility. A
from 9 am to 6 am. User can book counseling station for next 30 days only. A user is
allowed to book a maximum of 20 sessions in the slot of next 30 days. A session can also be
cancelled, but it should be done at least one day in advance.
Information description:
counseling booking Management Systemis a web based portal. Any registered user book the
counseling station for next 30 days. This portal is design for an open university like IGNOU.
At presently this university has 5 counseling stations. Every station has facility for online
counseling including camera, computer, web link etc. There are multiple users who want to
use these facilities. They need to use the counseling booking Management Systemfacility. A
from 9 am to 6 am. User can book counseling station for next 30 days only. A user is
allowed to book a maximum of 20 sessions in the slot of next 30 days. A session can also be
cancelled, but it should be done at least one day in advance.

17
In this system, there are two types of users known as counselor whose book the counseling
station and other user whose got counseling, this type of user is known as only user.
banking/credit card etc.
Users take appointment and attend the counseling session. Counselors also perform
cancelation .He/she cancels the counseling session 1 day advance.
Functional description:-
counseling booking Management Systemhas following modules:-
1. User: - This module performs the registration facilities. Any user, it he/she wants to
take counseling then first if all performs online registration and got a valid ID &
password. Through this ID he/she perform login and take appointment. After that
he/she got a counseling for any one counselor. The counselor name is selected by the
user.
2. Counselor :- This modules store the counselor list. Counselors also book the
counseling station for next 30 days. Any counselor have the right to provide only 20
session in this 30 days.One session is 1 hour. At the booking time counselor pay
booking amount Rs 5000 as a security .This amount is referable. counselor make
payment to university. Payment is depend on candidate. 40% payments given to the
university and remaining 60% take by the counselor.
3. Counseling station details: - This modules store the list ofcounseling stations. Every
counseling station hasa unique ID through this counselor book this stations. All
stations have facility for online counseling including camera, computer, web link etc.

18
4. Booking Handler: - This module is responsible to book the counseling station.
Counselor book the station for next 30 days. At the time of booking counselor pay Rs
5000 for advance. After that system generate a booking No.
5. Cancelation Master: -This module is responsible for doing cancelation. A counselor
cancels his/her counseling session before one day in advance.
6. Payment Master:-This module is responsible for handling project information
counselor make a payment for booking amount. User make a payment for getting
counseling.Payment made by with net booking credit card/Atm card etc

19
Survey of Technology
.NET FRAMEWORK:-
Features
The .NET Framework is an integral Windows component that supports building and running
the next generation of applications and XML Web services. The .NET Framework is
designed to fulfill the following features:
 To provide a consistent object-oriented programming environment whether object
code is stored and executed locally, executed locally but Internet-distributed, or
executed remotely.
 To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
 To provide a code-execution environment that promotes safe execution of code,
including code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on the
.NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the
.NET Framework class library.
The .NET Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code, thereby
creating a software environment that can exploit both managed and unmanaged features. The

20
.NET Framework not only provides several runtime hosts, but also supports the development
of third-party runtime hosts.
1. The Parallel Extensions for The .NET Framework will be built into mscorlib.dll.
The fact that PFx will be part of the core .NET library says a lot about how much faith
and support it’s getting within Microsoft. BTW, here are some really great demos
for PFx in .NET 4.5.
2. Code contracts.
Code contracts allow you to assert truths about your code as if you are writing a unit
test. But these assertions live within your production code and are both verified by the
compiler as well as the runtime
3. The WPF and Silver light designers mostly work.
Now this shouldn’t be a point to make me smile or get excited about, but it is. The
pain and suffering around the Visual Studio support for WPF and Silver light
designers has been so bad that a mostly-working, and sometimes truly innovative
design-time experience within Visual Studio gives me real hope for these
technologies.
4. WF has a rehostable designer (really, they mean it this time).
There are some great uses for giving regular users a WF designer experience with the
right granularity of activities. Now it’s much easier. Here’s an app that rehosts the
designer:
public Main Window ()
{
InitializeComponent();
WorkflowDesigner wd=new WorkflowDesigener ();
Grid.SetColumn(wd.View, 1);

21
Wd.Load(new MyActivity());
gridDesigner.Children.Add(wd.View);
}
}
5. ASP.NET MVC has wicked JavaScript support.
JQuery is there by default. That’s awesome. But there is also a class similar to the
Html class (for HTML helpers) called Ajax. This static class has functions like
Ajax.ActionLink and effectively brings the functionality of UpdatePanel to MVC!
INTRODUCTION SQL
More than 10 years ago, the biggest factor in the performance of a business application is the
speed of the SQL it runs. It took me longer to realize just how much room for improvement
typically lies in that SQL. The SQL that most affects the load on a system and the
productivity of its end users can usually be improved by a large factor. In the 1970s, IBM
developed a product called SEQUEL, or Structured English Query Language, which
ultimately became SQL, the Structured Query Language.
IBM, along with other relational database vendors, wanted a standardized method
for accessing and manipulating data in a relational database. Over the decades,
many competing languages have allowed programmers and developers to access
and manipulate data. However, few have been as easy to learn and as universally accepted as
SQL. Programmers and developers now have the benefit of learning a language that, with
minor adjustments, is applicable to a wide variety of database applications and products.
SQL in a Nutshell describes four implementations of the current SQL standard, SQL99 (also

22
known as SQL3): Microsoft’s SQL Server, MySQL, Oracle, and SQL. For those migrating
from implementations of the earlier SQL standard,
The Relational Database Model Relational Database Management Systems (RDBMSs), such
as SQL Server and Oracle, are the primary engines of information systems worldwide,
particularly Internet/Intranet applications and distributed client/server computing systems.
An RDBMS is defined as a system whose users view data as a collection of tables related to
each other through common data values. Data is stored in tables, and tables are composed of
rows and columns. Tables of independent data can be linked (or related) to one another if
they each have columns of data (called keys) that represent the same data value. This concept
is so common as to seem trivial; however, it was not so long ago that achieving and
programming a system capable of sustaining the relational model was considered a long shot
that would have limited usefulness.

23
COMPARISON BETWEEN SQL SERVER AND ORACLE:-
 The First biggest difference: Transaction control. In Oracle everything is a
transaction and it is not permanent until you COMMIT. In SQL Server, there is (by
default) no transaction control. An error half way through a stored procedure will not
rollback the DDL in previous steps.
 The Second biggest difference: MVCC. In SQL Server and Oracle is different. SQL
Server will allow dirty reads, and writes can block reads in MS SQL.
Also consider:
 When we setup an Oracle server, we tend to have one database with many
"users/schemas", and tablespaces that are shared by all our users. SQL Server has
separate databases that do not share disk files.
 SQL Server uses "logins" to give us access to the SQL Server instance and each
database has "users" that map to a login to get individual access to the tables and
views etc.
 Typically, all the objects in a database are owned by dbo.
 TSQL is similar to PL/SQL, but (in my opinion) less powerful. We may need to
simplify your SQL to get it to work as well as we'd expect in Oracle.
 If you like Oracle, all the "getting under the hood" and "explain plan optimization"
then this training and experience will work well for you against guy's who just code
straight SQL Server TSQL and expect the server to perform fast by magic.

24
 SQL Server does not have packages. This might start off as a bonus (PL/SQL packages
can be a PITA) but eventually you'll start to get a big nest of similarly named stored
procedures in the database and you'll wish there was a way you could organize and group
then them better.

25
DATA FLOW DIAGRAM: - it is a graphical, representation of flow of data
through a system. In this diagram, the external entities provide input data for the
processing. During the processing some intermediate data is generated. After final
processing the final output data is generated.
Rules of making DFD: - There are following seven rules given construction ofdata
flow diagrams.
 Arrows should not cross each other.
 Squares, circles and files must bear names.
 Decomposed data flow must be balanced.
 No two data flows, squares or circles can have the same name.
 Draw all data flow around the outside of the diagram.
 Choose meaningful names for data flows process and data stores.
 Control information such as record counts passwords and validation requirements are
not pertinent to a data-flow diagram.
DFD are describe for different level
e.g.:-
I. 0 level
II. 1st
level
III. 2 level

26
The symbols used in DFD are as follows: -
Symbol Name Description
Data flow
Representation the
connectivity between
process
Process
Performs some
processing of input
External Entity
Define source or
destination of system
data.
or
Data store Repository of data

27
DFD
Use
r
Counselin
g
station
booking
Manageme
Cancellation
Counsel
Payment Master
Appotment
Booking Handler
Counseling
station details

28
1st
Level DFD
perform store
User
Registr
at ion
User_details
Take appoitment
Appoit
m ent
access
store Appoitment
details
Perform
Counselor
Registratio
n
store
Counselordetails
Counselin
g station
details
see
counselingstationmaster
Booking
Handler
Paymen
t master
Access
Cancilation
master
Access
Access Store
Store
Access
Store
Access
Bookingdetails Paymentdetails cancilataiondetails
counselor
User

29
CCCCCCCCCCouououououououououounsensensensensensensensensenselllllllllliiiiiiiiiingngngngngngngngngng
s
mmmmmmmmmmananananananananananagagagagagagagagagagemeemeemeemeemeemeemeemeemeeme
Second Level DFD
Registration master
User Details
Cou nselor details
Registratio
n
check Login Id
and
If correct
Generate a
welcome
message.
You see the
course
User/Counsel Inform to
Sorry,
your
Id and
Cours
e
User fill
sing
up
generate
Id and
passwor
d store
into User_details
counselordetails
Colleg
e
Counseling
manageme
nt
Take
appointment
acce
If
not
correct
Give
to
New
user
Login

30
ENTITY RELATIONSHIP - DIAGRAM
An ER diagram is a model that identifies the concept or entities that exist in a system and the
relationships between those entities. An ERD is often used as a way to visualize a relational
database: each entity represents a database table and the relationship lines represents the key
in one table that point to specific records in related tables.
Advantages of ER diagram
 Professional and faster Development.
 Productivity Improvement.
 Fewer Faults in Development.
 Maintenance becomes easy.

31
pass
w ord
U_I
Name
use
r
Addr
e ss
pho
n e
tak
e
U_i
d
C_i
d
Appoitmen
t
Pay_id
Apno
date
Cancil
a
tin_id
U_i
d
C_id
Statio
n
_id
station
i
locatio
n for
tim
e
addr
cancilationmaste d es
s
Bookin
g
C_id
ammo
u nt
perf
orm
Bookin
g
Handle
r
statio
n id
C_id
U_i
d
Ma
na
Inter
act
pho
n
eno
Counselin
g Station
C_id
s
e
e
faciliti
estyp
specializati
Payment Ma
kes
Counsel
or Ad
d
res
s

32
payty
p Pay
_i
U_id passw
o
name

33
DATA DICTIONARY
Users Details
U-ID Varcher 20 This is primary
key
Password Varcher 20 Used for
password
Name Varcher 30 Used for name
of the user
Address Varcher 500 Used for hold
address
Phone Numeric Used for storing
phone number
Email-ID Varcher 20 Used for storing
emailed
D-of-reg. Date/time Used for storing
date of
registration

34
Counselor Details
C-ID Varcher 20 This field is the
primary key.
Password Varcher 20 Used for store
password
Name Varcher 30 Used for
storing name of
the counselor
Address Varcher 500 Hold address
Phone Numeric Store phone
number
Email-ID Varcher 20 Store emailed
Specialization Varcher 500 Hold the
specialization
of counselor
D-of-reg. Date/time store date of
registration

35
Counseling Station Master
Station ID Varcher 20 This is primary
key. This field
store station
number.
Location Varcher 200 This field store
location of
counseling
station.
Facilities type Varcher 200 Hold
information
about facilities
provided by
counseling
station.
Address Varcher 500 Address of
counseling
station
Phone no. Numeric Store phone
number
Fax no. Numeric This field store

36
fax number of
counseling
station.
Booking details
U_id Varchar 20 This is user id
through this
field ,table
connect with
userdetails.
counselor ID.
Through this
field this table
linked with
counselor
details table.
Station_id Varchar 20 This field store
the information
of counseling
station.

37
Through this
field table
linked with
station details
Bookingno Varchar 20 This is booking
id. This field is
the primary key
of this table.
BookingDate Date/Time This field store
the booking
details.
Time Date/time This field store
booking time.
Pay_id Varchar 30 This is
payment id
field. Through
this field table
linked with
payment
details.

38
Cancellation Details
counselorid.
bookingid.
Cancilid Varchar 20 This is
cancilationid.
This is the
primary key.
Cancildate Date/time This field store
cancelation
date.
Canciltime Date/time This field store
cancelation
time.
Payid Varchar 30 This field store
payment
information.

39
Payment_Details
field.
counselor id
fields
Payid Varchar 30 This is
paymentid
fields
paytype Varchar 50 This field
describe
paymenttype
like through
creditcardetc
Amount Int This field hold
payment
amount
Date Date/time This field hold
payment date.
Time Date/time This field hold
time of payment

40
Appoitment details
U_id varchar 20 This is userid
field
C_id varchar 20 This is
counselorid.
Payid varchar 30 This is
paymentid.
Ap_
no
varchar 30 This is
appointment no.
this is the
primary key
Date Date/time This is
appointment
date.
Time Date/time This is
appointment
time.
Duration Time time duration.

42
Database Diagram
userdetail *
Id
Fname
Username
Email
password
Age
gender
Address
phone
DoReg
Image
Appoitmentdetails *
U_id
C_id
Ap_no
Date
Time
Duration
Payment_Details *
U_id
C_id
Payid
Paytype
Amount
Date
Time
Counselor_Details *
C_ID
Password
Name
Address
Phone
[Email-ID]
Specialization
[D-of-reg.]
Booking details *
C_id
Station_id
Bookingno
Time
Pay_id
Counseling Station Master *
[Station ID]
Location
[Facilities type]
Address
[Phone no.]
[Fax no.]
stationid *
stationid
Cancellation Details *
C_id
Bookingno
Cancilid
Cancildate
Canciltime
Payid
station_id

43
MODULARIZATION DETAILS
1. MODULAR DESIGN CONCEPTS
(i) Functional Independence: The concept of functional independence is a direct outgrowth
of modularity and the concepts of abstraction and information hiding.
The principle of information hiding suggests that modules be “characterized by design
decisions that (each) hides from all others”. In other words, modules should be specified and
designed so that information (procedure and data) contained within a module is inaccessible
to other modules that have no need for such information. Hiding implies that effective
modularity can be achieved by defining a set of independent modules that communicate with
one another only that information necessary to achieve software function. Abstraction helps
to define the procedure entities that make up the software. As data and procedure are hidden
from other parts of the software inadvertent errors introduced during modification are less
likely to propagate to other locations within the software. Functional independence is
achieved by developing modules with “single-minded” function and an “aversion” to
excessive interaction with other modules.
Advantages: Independent modules are easier to maintain (and test) because secondary
effects caused by design or code modification are limited, error propagation is reduced, and
reusable modules are possible. Thus, with taking utmost care of this concept we have
maintained functional independence in our project COUNSELING BOOKING
MANAGEMENT SYSTEMat some extent that required interaction among different modules
is maintained.
(ii) Cohesion: Cohesion of a module represents how tightly bound the internal elements of
the module are to one another. Cohesion of a module gives the Designer an idea about
whether the different elements of a module belong together in the same module.

44
(iii) Coupling: Coupling is a measure of interconnection among modules in a software
structure. Coupling depends on the interface complexity between modules, the point at
which entry or reference is made to a module, and what data pass across the interface. In
software design, we strive for lowest possible coupling. Simple connectivity among modules
results in software that is easier to understand and less prone to a “ripple effect” when errors
occur at one location and propagate through a system.
Data coupling: Data coupling means simple argument list (data) is passed and a one to one
correspondence exists. A variation of data coupling is found when a portion of a data
structure rather than simple arguments is passed via a module interface.
Control coupling: When a “control flag” (a variable that controls decisions in a subordinate
or super ordinate module) is passed between modules.
External coupling: It is a relatively high level of coupling occurs when modules are tied to
an environment external to software.
Common coupling: When a number of modules reference a global data area. In
COUNSELING BOOKING MANAGEMENT SYSTEMwe have maintained
the use of global data but restricted ourselves against the common consequences of this
coupling.
Content coupling: The highest degree of coupling, content coupling occurs when one
module makes use of data or control information maintained within the boundary of another
module. Secondarily, content coupling occurs when branches are made into the middle of a
module. As this type of coupling makes software complex so in COUNSELING BOOKING
MANAGEMENT SYSTEMwe have tried our best to avoid such coupling.
As the cohesion and coupling are clearly related. Usually the greater the cohesion of each
module in a system, the lower the coupling between modules is. So, we have maintained a
balance between these two engineering concepts.

45
DATABASE INTEGRITY & CONSTRAINTS
Security constraints guard against accidental or malicious tampering with data, whereas
integrity constraints ensure that any properly authorized access, alteration, deletion, or
insertion of the data in the database does not change the consistency and validity of the data.
This requires that there is a need for guarding against invalid database operations. An
operation here is used to indicate any action performed on behalf of a user or application
program that modifies the state of the database. Such operations are the result of actions such
as update, insert, or delete. In short, invalid changes have to be guarded against by the
security subsystem. Database integrity involves the correctness of data; this correctness has
to be preserved in the presence of concurrent operations, errors in the user’s operations and
application programs, and failures in hardware and software. For example, the concurrency
control mechanism ensures that two concurrent transactions are serialized. However, the
integrity constraints must be applied to both these concurrent operations and these
constraints ensures that each of these transactions, when run to completion, concurrently or
in isolation, will not cause the database to become invalid. The recovery subsystem ensures
that failures of various types, which may cause the loss of some of the actions of one or more
transactions, will not cause the database to become inconsistent. We consider some type of
constraints that the database has to enforce to maintain the consistency and validity of data.
One aspect that has to be dealt with by the integrity subsystem is to ensure that only valid
values can be assigned to each data-item. This is referred to as domain integrity. Another set
of integrity constraints are the so-called structural and semantic constraints. Some of these
types of constraints are addressed by the data models used and others are addressed in the
design of the database by Combining appropriate functional dependencies indifferent
records. Some if not most of the functional dependencies can be expressed if the DBMS
allows each record type or relation
to have an associated primary key. In traditional system, application programs were
responsible for the validation of data and maintaining the consistency of the data used by the
programs. However, depending on data application programs to perform these checks has the
following drawback.

46
 Each application program must have correct validation and consistency check
routines; a failure in one program could lead to database inconsistencies.
 Each application program must be aware of the semantic of the complete database to
enforce the correct consistency checks; this is not always the case and unnecessarily
burdens the application program writers.
 There will be considerable duplication of efforts.
 Integrity constraints are hard to understand when they are buried in the code of
application programs.
 No consistency or validity checks are possible for direct database manipulation using a
query language.
Centralizing the integrity checks directly under the DBMS reduces duplication and ensures
the consistency and validity of the database. The centralized integrity constraints can be
maintained in a system catalogue and Can be accessible to the database users via the query
language. This does not rule out an application program performing some specific checking,
including input validation.

47
User Interface
Home Page
This is the Home Page of our website. This is the first interaction of user with our website.

48
About us Page
This is the About us Page of our website. Here user will get details about our website goals
etc..

49
Contact us Page
This is the Contact us Page of our website. Here user will get contact information related to
our company website.

50
Registration Page
This is the Registration Page of our website. Here new user can register with our website
and will get User Id and Password for further Processes.

51
Login Page
This is the Login Page of our website. Here user will perform login with User Id and
Password and will do further process.

52
Book Appointment Page
This is the Book Appointment Page of our website. Here user will book appointment with
counsellor.

53
Payment Page
This is the Payment Page of our website. Here user will make Payment for his booking.

54
Counsellor Detail
This is the Counsellor Detail Page of our website. Here user will see Detail of Counsellors
available.

55
Station Master Page
This is the Station Master Page of our website. Here Counsellor can add new Counselling
Station Details.

56
Station Details Page
This is the Station Details Page of our website. Here counsellor user can see
Counselling station detail.

57
Book Station
This is the Book Station Page of our website. Here counsellor can book counselling station
for his/her counselling session.

58
Appointment Cancellation Page
This is the Appointment Detail Page of our website. Here counsellor can see his
appointments and also can cancel them.

59
CODING
Master Page
Design Code
<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs"
Inherits="MasterPage" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Counseling Booking Management System </title>
<link href="StyleSheet.css" rel="stylesheet" type="text/css" />
</head>
<body>
<form id="form1" runat="server">
<div class="all">
<div>
<center style="font-size: 25px; font-weight: bold; font-style:
italic; color: #FFFFFF; background-color: #000000">Counselling Station 
Booking Management</center>
</div>
<div style="background-color: #9CAAC1">
<div id="header">
<div id="menu">
<div id="menu_h">
<a href="Home.aspx" id="menu_b">Home</a>
</div>
<div id="menu_a">
<a href="Aboutus.aspx" id="menu_b">About Us</a>
</div>

60
<div id="menu_a">
<a href="Contactus.aspx" id="menu_b">Contacts</a>
</div>
<div id="menu_a">
<a href=" Appointment.aspx"
id="menu_b">Appointment</a>
</div>
<div id="menu_a">
<a href="Book_Station.aspx" id="menu_b">Book
Station</a>
</div>
<div id="menu_a">
<a href="Counseller_Details.aspx"
id="menu_b">Counseller</a> 
</div>
<div id="menu_a">
<a href="Registration.aspx"
id="menu_b">Registration</a>
</div>
<div id="menu_a">
<a href="Cancle.aspx" id="A1">Cancletion</a>
</div>
<div id="menu_a">
<asp:LinkButton ID="LinkButton1" runat="server"
OnClick="LinkButton1_Click">logout</asp:LinkButton>
</div>
</div>
</div>
</div>
214px">
<div>
<img src="Image/banner-4.jpg" width="100%" style="height:

61
</div>
<div style="background-color: #9CAAC1;">
<asp:ContentPlaceHolder ID="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>
</div>
<div>
<center style="font-size: 15px; font-weight: bold; font-style:
italic; color: #FFFFFF; background-color: #000000">
Copyright © Counselling Booking Management System
      By <b>Amit Singh</b> </center>
</div>
</div>
</form>
</body>
</html>

62
C# Code
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
public partial class MasterPage : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{
if (Session["Login_id"] == null)
{
}
else
{
}
}
LinkButton1.Text = "Login";
LinkButton1.Text = "Logout";
protected void LinkButton1_Click(object sender, EventArgs e)
{
if (LinkButton1.Text == "Logout")
{
Session.RemoveAll();
Server.Transfer("Home.aspx");
}
else if (LinkButton1.Text == "Login")
{
Response.Redirect("~/Login.aspx");
}
}
}

63
Home Page
Design Code
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"
AutoEventWireup="true" CodeFile="Home.aspx.cs" Inherits="_Default" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<div style="padding: 15px; background-color: #9CAAC1;">
<p style="font-size: 15px; font-weight: bold;">Counselling Booking Management
System
</p>
<p style="text-align: justify">
counseling booking Management Systemis a web based portal. Any registered
user book the counseling station for next 30 days. This portal is design for an
open university like IGNOU. At presently this university has 5 counseling
stations. Every station has facility for online counseling including camera,
computer, web link etc. There are multiple users who want to use these
facilities. They need to use the online counseling station booking facility. A
registered user can do this. A counseling session is of 1 hour duration and can
be performed from 9 am to 6 am. User can book counseling station for next 30
days only. A user is allowed to book a maximum of 20 sessions in the slot of
next 30 days. A session can also be cancelled, but it should be done at least
one day in advance.
In this system, there are two types of users known as counselor whose
book the counseling station and other user whose got counseling ,this type of
user is known as only user.
banking/credit card etc.
Users take appointment and attend the counseling session. Counselors also
perform cancelation .He/she cancels the counseling session 1 day advance.
</p>
</div>
</asp:Content>

64
C# Code
using System;
using System.Linq;
using System.Web;
public partial class _Default : System.Web.UI.Page
{
{
if (!string.IsNullOrEmpty(Convert.ToString(Session["PaymentStatus"])))
{
Response.Write("<script>alert('" +
Session["PaymentStatus"].ToString() + "')</script>");
Session["PaymentStatus"] = string.Empty;
}
if (!string.IsNullOrEmpty(Convert.ToString(Session["BookingStatus"])))
{
Response.Write("<script>alert('" +
Session["BookingStatus"].ToString() + "')</script>");
Session["BookingStatus"] = string.Empty;
}
}
}

65
Registration Page
Design Code
AutoEventWireup="true" CodeFile="Registration.aspx.cs" Inherits="_Default" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">
<div style="height: 438px; background-color: #B0BBCF; padding: 15px;">
<div style="float: left">
<div id="registration_main_header">
<center style="font-size: 25px; font-weight: bold">
Registration Form</center>
</div>
<div id="registration_header">
<div>
<div style="float: left; width: 458px;">
<div>
<br />
<asp:Label ID="lblmsg" runat="server"></asp:Label>
</div>
<div>
<asp:Label ID="lblname" runat="server" Text="Name"></asp:Label>
         
             &n
bsp;  
<asp:TextBox ID="txtname" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator
ID="nameValidator" runat="server" ValidationGroup="G" ErrorMessage="Fill
this box" ControlToValidate="txtname"
EnableClientScript="False"></asp:RequiredFieldValidator>
<br />
</div>
<div>
<br />
<asp:Label ID="lblid" runat="server" Text="User Id"></asp:Label>

66
           
           
<asp:TextBox ID="txtid" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator ValidationGroup="G"
ID="RequiredFieldValidator1" runat="server" ErrorMessage="Fill this box"
ControlToValidate="txtid"
EnableClientScript="False"></asp:RequiredFieldValidator><br />
<br />
</div>
<div>
<asp:Label ID="lblpsw" runat="server" Text="Password"></asp:Label>
   
             &n
bsp; 
<asp:TextBox ID="txtpsw" runat="server" TextMode="Password"></asp:TextBox>
ID="RequiredFieldValidator2" runat="server" ValidationGroup="G"
ErrorMessage="Fill this box" ControlToValidate="txtpsw"
<br />
</div>
<div>
<asp:Label ID="lblcpsw" runat="server" Text="Confirm Password"></asp:Label>
     
<asp:TextBox ID="txtcpsw" runat="server" TextMode="Password"></asp:TextBox>
<asp:CompareValidator ValidationGroup="G"
ID="cvconfirmpsw" runat="server" ErrorMessage="Password not match"
ControlToValidate="txtpsw"
ControlToCompare="txtcpsw"></asp:CompareValidator>
<asp:RequiredFieldValidator ID="RequiredFieldValidator3" ValidationGroup="G"
runat="server" ErrorMessage="Fill this box" ControlToValidate="txtcpsw"
<br />
</div>
<div>
<asp:Label ID="lbl_user_type" runat="server" Text="User Type"></asp:Label>

67
                 
<asp:DropDownList ID="ddl_utype" runat="server"
OnSelectedIndexChanged="ddl_utype_SelectedIndexChanged" Height="22px"
Width="128px">
<asp:ListItem>--Select--</asp:ListItem>
<asp:ListItem>Student</asp:ListItem>
<asp:ListItem>Counseller</asp:ListItem>
</asp:DropDownList>
<br />
<br />
</div>
<div>
<asp:Label ID="lbldob" runat="server" Text="Date Of Birth"></asp:Label>
            
<asp:TextBox ID="txtdob" runat="server" TextMode="Date"
Visible="True"></asp:TextBox>
<asp:RangeValidator ValidationGroup="G"
ID="RangeValidator1" runat="server" ErrorMessage="DD/MM/YYYY"
SetFocusOnError="False"
ControlToValidate="txtdob" MaximumValue="01/01/2014"
MinimumValue="01/01/1950"
Type="Date"></asp:RangeValidator>
<asp:RequiredFieldValidator ID="RequiredFieldValidator5"
runat="server" ErrorMessage="Fill this box" ValidationGroup="G"
ControlToValidate="txtdob" EnableClientScript="False"></asp:RequiredFieldValidator><br />
<br />
</div>
</div>
<div>
<br />
<asp:Label ID="lblmno" runat="server" Text="Mobile No"></asp:Label>
                 
<asp:TextBox ID="txtmno" runat="server"></asp:TextBox>

68
Visible="True"
<asp:RegularExpressionValidator ValidationGroup="G"
ID="revmob_no" runat="server" ErrorMessage="Only 10 number "
ValidationExpression="d{10}"
ControlToValidate="txtmno"></asp:RegularExpressionValidator>
ID="RequiredFieldValidator6" runat="server" ErrorMessage="Fill this box"
ValidationGroup="G" ControlToValidate="txtmno"
<br />
</div>
<div>
<asp:Label ID="lblemailid" runat="server" Text="Email Id"></asp:Label>
           
         
<asp:TextBox ID="txtmailid" runat="server"></asp:TextBox>
<asp:RegularExpressionValidator ID="revemail" runat="server"
ValidationGroup="G" ErrorMessage="Only email pattern"
Visible="True" ValidationExpression="w+([-+.']w+)*@w+([-.]w+)*.w+([-
.]w+)*"
ControlToValidate="txtmailid"></asp:RegularExpressionValidator>
ErrorMessage="Fill this box" ControlToValidate="txtmailid"
<br />
</div>
<div>
<asp:Label ID="lbldate" runat="server" Text="Date" ></asp:Label>
                  
       
<asp:TextBox ID="txtdate" runat="server" TextMode="Date"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator8"
runat="server" ErrorMessage="Fill this box" ValidationGroup="G"
ControlToValidate="txtdate" EnableClientScript="False"></asp:RequiredFieldValidator><br />
<br />

69
</div>
<div>
<asp:Label ID="lblsex" runat="server" Text="Sex"></asp:Label>
                   
   
    
<asp:DropDownList ID="ddlgen" runat="server" Height="22px" Width="132px">
<asp:ListItem>--Select--</asp:ListItem>
<asp:ListItem>Male</asp:ListItem>
<asp:ListItem>Female</asp:ListItem>
</asp:DropDownList>
<br />
<br />
</div>
<div>
<br />
<asp:Label ID="lbladdress" runat="server" Text="Address"></asp:Label>
                 
   
<asp:TextBox ID="txtaddress" runat="server"
TextMode="MultiLine"></asp:TextBox>
ErrorMessage="Fill this box" ControlToValidate="txtaddress"
<br />
</div>
</div>
</div>
<br />
<div style="width: 920px">
             &n

70
bsp;            &nbsp
;             &
nbsp;       
<asp:Button ID="btnsubmit" runat="server" Text="Submit" Height="22px"
Width="14%"
OnClick="btnsubmit_Click" BackColor="Black" ForeColor="White"
ValidationGroup="G" />
             &n
bsp;            &nbsp
;             &
nbsp;       
<asp:Button ID="btncancel" runat="server" Text="Cancel" Height="22px"
Width="14%"
BackColor="Black" OnClick="btncancel_Click" ForeColor="White" />
</div>
</div>
</div>
</div>
</div>
</asp:Content>

71
C# Code
using System;
using System.Linq;
using System.Web;
using System.Data;
using System.Data.SqlClient;
{
DataContextClass _obj_dc = new DataContextClass();
{
}
protected void btnsubmit_Click(object sender, EventArgs e)
{
string name = txtname.Text;
string userid = txtid.Text;
string pwd = txtpsw.Text;
string utype = ddl_utype.Text;
string dob = txtdob.Text;
string mobileno = txtmno.Text;
string email_id = txtmailid.Text;
string Address = txtaddress.Text;
string sex = ddlgen.Text;
if (utype == "Counseller")
{
//fu.SaveAs(Server.MapPath("Profile_Picture/" + fu.FileName));
//string path = Server.MapPath("Profile_Picture/" + fu.FileName);
string query = "insert into
Registration_Counseller_Table(Name,User_Id,Password,User_Type,Date_of_Birth,Mob

72
ile_no,Email_id,Date,Sex,Address) values('" + name + "','"+ userid + "','" +
pwd + "','" + utype + "','" + dob + "','" + mobileno + "','" + email_id + "','"
+ txtdate.Text + "','" + sex + "','" + Address + "')";
int i = _obj_dc.creat(query);
if (i > 0)
{
}
else
{
}
else
{
}
Server.Transfer("Login.aspx");
lblmsg.Text = "Data not saved";
//fu.SaveAs(Server.MapPath("Profile_Picture/" + fu.FileName));
//string path = Server.MapPath("Profile_Picture/" + fu.FileName);
string query = "insert into
Registration_Student_Table(Name,User_Id,Password,User_Type,Date_of_Birth,Mobile
_no,Email_id,Date,Sex,Address) values('" + name + "','" + userid + "','" + pwd
+ "','" + utype + "','" + dob + "','" + mobileno + "','" + email_id + "','" +
txtdate.Text + "','" + sex + "','" + Address + "')";
int i = _obj_dc.creat(query);
if (i > 0)
{
}
else
{
}
}
Server.Transfer("Login.aspx");
lblmsg.Text = "Data not saved";
}

73
protected void btncancel_Click(object sender, EventArgs e)
{
txtname.Text = "";
txtid.Text = "";
txtpsw.Text = "";
ddl_utype.Text = "";
txtdob.Text = "";
txtmno.Text = "";
txtmailid.Text = "";
txtaddress.Text = "";
ddlgen.Text = "";
txtdate.Text = "";
}
protected void ddl_utype_SelectedIndexChanged(object sender, EventArgs e)
{
}
}

74
Login Page
Design Code
AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="_Default" %>
Runat="Server">
<div id="logmdiv">
<%--<div style="float: left; width: 300px; height: 260px;">
<marquee direction="up" onmouseover="this.stop();"
onmouseout="this.start();" behavior="alternate"><center><asp:Image
ID="marquee_image" runat="server" ImageUrl="~/images/Welcome.gif" /> TO
:)  &nbsp ---> </center></marquee>
</div>--%>
<br />
<div style="padding: 20px">
<div id="logform" style="background-color: #BCC7D8">
<div><center style="font-weight: bold">
<br />
<br />
Login Form
<br />
<br />
</center></div>
<div><center>
<asp:Label ID="lbluid" runat="server" Text="User
ID"></asp:Label>
     
<asp:TextBox ID="txtuid"
runat="server"></asp:TextBox></center></div>
<br />
<div><center>
<asp:Label ID="lblpwd" runat="server"
Text="Password"></asp:Label>
  

75
<asp:TextBox ID="txtpwd" runat="server"
TextMode="Password"></asp:TextBox>
<br />
</center></div>
<div><center>
     
<asp:RadioButtonList ID="RadioButtonList1" runat="server"
RepeatDirection="Horizontal">
<asp:ListItem>Student</asp:ListItem>
<asp:ListItem>Counseller</asp:ListItem>
</asp:RadioButtonList>
<asp:RequiredFieldValidator ID="rfv_radiob" runat="server"
ControlToValidate="RadioButtonList1"
ErrorMessage="Please select any
one"></asp:RequiredFieldValidator>
</center></div>
<br />
<div><center>
             &
nbsp;    
<asp:Button ID="btnlogin" runat="server" Text="Login"
OnClick="btnlogin_Click"
BorderColor="#0099FF" Width="72px" />
    
<asp:Button ID="btncancel" runat="server" Text="Cancel"
OnClick="btncancel_Click"
BorderColor="#0099FF" />
<br />
<br />
</center>
</div>
<div><center>

76
          
<asp:CheckBox ID="chksingup" runat="server" Text="Keep Me
Sing in" />
 <br />
<br />
</center>
</div>
<div><center>
<asp:LinkButton ID="lbtnnew_user" runat="server" Text="New
User" OnClick="lbtnnew_user_Click"
/>           
<asp:LinkButton ID="lbtnforget_pwd" runat="server"
Text="Forget Password" OnClick="lbtnforget_pwd_Click" />
<br />
<br />
</center></div>
</div>
</div>
</div>
</asp:Content>

77
C# Code
using System;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Data;
using System.Data.SqlClient;
{
DataContextClass dc_obj = new DataContextClass();
{
if (Session["Login_id"] != null)
{ Response.Redirect("~/Home.aspx"); }
}
protected void btnlogin_Click(object sender, EventArgs e)
{
try
{
if (RadioButtonList1.SelectedItem.Text == "Student")
{
string query = "select * from Registration_Student_Table where
User_Id='" + txtuid.Text + "' AND Password='" + txtpwd.Text + "'";
DataTable dt = dc_obj.getdatatable(query);
if (dt.Rows.Count > 0)
{
string uid = dt.Rows[0]["User_Id"].ToString().Trim();
string pwd = dt.Rows[0]["Password"].ToString().Trim();
if (txtuid.Text == uid && txtpwd.Text == pwd)
{
Session["Login_id"] = txtuid.Text;

78
Session["UType"] = "S";
Response.Redirect("~/Home.aspx");
}
else
{
Response.Write("<script>alert('Sorry Enter correct id
and password')</script>");
}
}
if (dt.Rows.Count <= 0)
{
Response.Write("<script>alert('Sorry Enter correct id and
password')</script>");
}
}
else if (RadioButtonList1.SelectedItem.Text == "Counseller")
{
string query = "select * from Registration_Counseller_Table
where User_Id='" + txtuid.Text + "' AND Password='" + txtpwd.Text + "'";
DataTable dt = dc_obj.getdatatable(query);
if (dt.Rows.Count > 0)
{
string uid = dt.Rows[0]["User_Id"].ToString().Trim();
string pwd = dt.Rows[0]["Password"].ToString().Trim();
if (txtuid.Text == uid && txtpwd.Text == pwd)
{
}
else
{
Session["Login_id"] = txtuid.Text;
Session["UType"] = "C";
Response.Redirect("~/Station_master.aspx");

79
Response.Write("<script>alert('Sorry Enter correct id
and password')</script>");
}
}
if (dt.Rows.Count <= 0)
{
Response.Write("<script>alert('Sorry Enter correct id and
password')</script>");
}
}
}
catch (Exception)
{
}
}
protected void btncancel_Click(object sender, EventArgs e)
{
txtuid.Text = "";
txtpwd.Text = "";
}
protected void lbtnnew_user_Click(object sender, EventArgs e)
{
Response.Redirect("Registration.aspx");
}
protected void lbtnforget_pwd_Click(object sender, EventArgs e)
{
Response.Redirect("Forget_pwd.aspx");
}
}

80
About Us Page
Design Code
AutoEventWireup="true" CodeFile="Aboutus.aspx.cs" Inherits="_Default" %>
Runat="Server">
<div style="padding: 15px; background-color: #9CAAC1;">
<p style="font-size: 15px; font-weight: bold;"> About Us</p>
<p style="text-align: justify"> Online counseling station booking is a web
based portal. It has following objective:-
</p>
</p>
<p style="text-align: justify"> Counseling station is booked for 30 days.
<p style="text-align: justify"> Only registered users can take
counseling.
</p>
<p style="text-align: justify"> Before counseling he/she got an
appointment.
</p>
<p style="text-align: justify"> Counselor book counseling stations
according to need and make payment.
</p>
<p style="text-align: justify"> Registered user take counseling for
making a payment of Rs 1000.
</p>
<p style="text-align: justify"> Payment is valid for next 15 days.
</p>
</div>
</asp:Content>

81
C# Code
using System;
using System.Linq;
using System.Web;
{
{
}
}

82
Appointment Page
Design Code
AutoEventWireup="true" CodeFile="Appointment.aspx.cs" Inherits="_Default" %>
runat="Server">
<div style="height: 396px; padding: 20px;">
<div style="background-color: #9CAAC1">
<div>
<p style="font-size: 15px; font-weight: bold"> </p>
<p style="font-size: 15px; font-weight:
bold">    Appointment Form</p>
<br />
<div>
<asp:Label ID="lblid" runat="server" Text="User
Id"></asp:Label>
           
             &
nbsp;     
<asp:TextBox ID="txtid" Height="25px" Width="150px"
runat="server"></asp:TextBox><br />
<div>
<br />
<asp:Label ID="lblid0" runat="server" Text="Counseller
Id"></asp:Label>
           
           
<asp:DropDownList ID="txtcid" runat="server"
Height="25px" Width="150px" DataSourceID="SqlDataSource1" DataTextField="Name"
DataValueField="User_Id"></asp:DropDownList>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:DBCS %>" SelectCommand="SELECT * FROM
[Registration_Counseller_Table]"></asp:SqlDataSource>
<br />

83
<br />
</div>
</div>
<div>
<asp:Label ID="lbldob" runat="server"
Text="Date"></asp:Label>
       
             &
nbsp;            
 
<asp:TextBox ID="txtdate" runat="server" Height="25px"
Width="150px" Visible="True" TextMode="Date"></asp:TextBox><br />
<br />
<div>
<asp:Label ID="lbldob0" runat="server"
Text="Time"></asp:Label>
     
             &
nbsp;             
 
<asp:TextBox ID="txttime" runat="server" Height="25px"
Width="150px" Visible="True" TextMode="Time"></asp:TextBox>
<br />
<br />
</div>
</div>
</div>
<div>
<asp:Label ID="lbldob1" runat="server"
Text="Duration"></asp:Label>
     
             &
nbsp;          

84
<asp:TextBox ID="txtdur" runat="server" Height="25px"
Width="150px" Visible="True"></asp:TextBox>
<br />
<br />
</div>
<br />
<asp:Button ID="btnsubmit" runat="server" Text="Payment"
Height="22px" Width="14%"
OnClick="btnsubmit_Click" BackColor="Black" ForeColor="White"
/>
</div>
</div>
</asp:Content>

85
C# Code
using System;
using System.Linq;
using System.Web;
{
{
if (Session["UType"] != null)
{
if (Session["UType"].ToString() != "S")
{
string message = "Unauthorised user to access the Page! Only
Student can Access. If registered please login First.";
string url = "Home.aspx";
string script = "window.onload = function(){ alert('";
script += message;
script += "');";
script += "window.location = '";
script += url;
script += "'; }";
ClientScript.RegisterStartupScript(this.GetType(), "Redirect",
script, true);
}
}
if (Session["UType"] == null)
{
string message = "Unauthorised access the Page! Only Registered
Student can Access. If registered please login First.";
string url = "Home.aspx";

86
string script = "window.onload = function(){ alert('";
script += message;
script += "');";
script += "window.location = '";
script += url;
script += "'; }";
ClientScript.RegisterStartupScript(this.GetType(), "Redirect",
script, true);
}
txtid.Text = Session["Login_id"].ToString();
}
protected void btnsubmit_Click(object sender, EventArgs e)
{
{
}
else
{
Session["User_id"] = txtid.Text;
Session["C-id"] = txtcid.Text;
Session["Date"] = txtdate.Text;
Session["Time"] = txttime.Text;
Session["Duration"] = txtdur.Text;
Response.Redirect("Payment.aspx");
Response.Write("<script>alert('Sorry Please first
login')</script>");
}
}
}

87
Appointment Detail Page
Design Code
AutoEventWireup="true" CodeFile="Appointdetail.aspx.cs" Inherits="_Default" %>
runat="Server">
<div style="background-color: #9CAAC1; text-align: center">
<h2 style="text-align: center; font-weight: bold; font-family:
Nyala;">Appointment Details</h2>
<table align="center" style="text-align: center;">
<tr>
<td>
<asp:ListView ID="ListView1" Style runat="server"
DataKeyNames="ID" DataSourceID="SqlDataSource1">
<EmptyDataTemplate>
<span>No Record Found.</span>
</EmptyDataTemplate>
#000000;">
<ItemTemplate>
<span style="background-color: #DCDCDC; color:
<asp:Label ID="IDLabel" runat="server"
Visible="false" Text='<%# Eval("ID") %>' />
<br />
<asp:Label ID="PidLabel" runat="server"
Visible="false" Text='<%# Eval("Pid") %>' />
<br />
user_id:
<asp:Label ID="user_idLabel" runat="server"
Text='<%# Eval("user_id") %>' />
<br />
Date:

Final (1).pdf

Recommended

Recommended

More Related Content

Similar to Final (1).pdf

Similar to Final (1).pdf (20)

Recently uploaded

Recently uploaded (20)

Final (1).pdf