City Guide

PROJECT REPORT
ON
City Guide
Name: Garima Kumari (1513210056)
Rovinsh (1513210131)
Ankita Singh (1513210031)
Department of Computer Science and Engineering

GREATER NOIDA INSTITUTE OF TECHNOLOGY,
GREATER NOIDA
DR. APJ ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW
1
PROJECT REPORT
ON
City Guide
SUBMITTED IN THE PARTIAL FULFILLMENT FROR AWARD OF
DEGREE
IN
COMPUTER SCIENCE AND ENGINEERING
(BATCH 2015-2019)
BY
Name: Garima Kumari - (1513210056)
Rovinsh - (1513210131)
Ankita Singh - (1513210031)
Department of Computer Science and Engineering

GREATER NOIDA INSTITUTE OF TECHNOLOGY,
GREATER NOIDA
DR. APJ ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW
2
Certificate of Originality
I hereby declare that the Project entitled (City Guide) submitted to the Department of Computer
Science & Engineering, GREATER NOIDA INSTITUTE OF TECHNOLOGY, GREATER
NOIDA,U.P. in partial fulfillment for the award of the degree of BACHELOR OF
TECHNOLOGY in session 2015-19 is an authentic record of my own work carried out under the
guidance of Mrs. Kumud Yadav and that the project has not previously formed the basis for
the award of any other degree/diploma.
Signature of Student
Place: Greater Noida Garima kumari(1513210056)
Date:1/06/2019 Ankita Singh (1513210031)
Rovinsh (1513210131)
This is to certify that the above statement made by the above candidate/students are correct to
the best of my knowledge.
Signature of Guide
Guide Name: Mrs. Kumud Yadav
(Designation:)
(iii)
3
ACKNOWLEDGEMENT
I am highly grateful to “Mrs. Kumud Yadav” for giving his valuable time and constructive
guidance to prepare the seminar report.
It would not have been possible to complete this work in short period of time without his
guidance kind encouragement and valuable guidance. I also thank my parents to motivate me for
preparing the project report on City Guide.
Signatrure of Student
Gaima kumari- (1513210056)

Ankita Singh- (1513210031)
Rovinsh- (1513210131)
(v)
4
ABSTRACT
The project title ‘City Guide’ in Asp.net, is a web-based product used to store the details of
particular city and helps all the users who just visits our website. This site also provides all the
services like Restaurants table, Beauty parlor , Education details, Health and hospital related
information, city news.
The City Guide template was designed to be a small guide for sites that display information for
local cities or small towns. It mimics the layout of common city sites and provides the ability for
one to add many modules to the homepage in a clean, concise manor.
Cities are being equipped with multiple information systems to provide public services for city
officials, officers, citizens, and tourists. There have been concerns with efficient service
implementation and provision, e.g., data islands and function overlaps between systems and
applications. Service-oriented guides are efficient at facilitating information sharing and
collaborative work between city systems and users. The goal of this research is to make cities
responsive, agile and to provide composite services efficiently and cost efficiently. A service-
oriented framework for city guides is proposed to design, integrate and streamline city systems
and applications. A model driven collaborative development platform of the proposed framework
was developed for service-oriented digital guides. The architecture and implementation issues of
the platform are discussed. The service identification policies are discussed within the
framework. A case study has been developed and evaluated on the platform to provide a
composite service, i.e., a traffic search service on a city guide.
(vi)
5
Chapter-1
INTRODUCTION
The project title ‘City Guide’ in Asp.net, is a web-based product used to store the details of
particular city and helps all the users who just visits our website. This site also provides all the
services like Restaurants table, Beauty parlor , Education details, Health and hospital related
information, city news
The City Guide template was designed to be a small guide for sites that display information for
local cities or small towns. It mimics the layout of common city sites and provides the ability for
one to add many modules to the homepage in a clean, concise manor.
Cities are being equipped with multiple information systems to provide public services for city
officials, officers, citizens, and tourists. There have been concerns with efficient service
implementation and provision, e.g., data islands and function overlaps between systems and
applications. Service-oriented guides are efficient at facilitating information sharing and
collaborative work between city systems and users. The goal of this research is to make cities
responsive, agile and to provide composite services efficiently and cost efficiently. A service-
oriented framework for city guides is proposed to design, integrate and streamline city systems
and applications. A model driven collaborative development platform of the proposed framework
was developed for service-oriented digital guides. The architecture and implementation issues of
the platform are discussed. The service identification policies are discussed within the
framework. A case study has been developed and evaluated on the platform to provide a
composite service, i.e., a traffic search service on a city guide.
City Guide is an information guide that is proposed to provide various information about Gr.
Noida like Entertainment Places, Educational institutes, social activities and other important
places such as banks, shopping centers, commercial complexes etc.
The guide aims to provide complete information about Gr. Noida using the following two
mechanisms:
6
 Information given by users is to be presented on the web site after through verification by
admin.
 Information to be collected through classifieds posted on the guide by various social,

businesses, educational and professional entities having operations in Gr. Noida is to be
presented.
This website will provide fast, convenient and user-friendly public e-services to business and citizens.
This platform brief information about the city by using efficient software. To get details about the
top restaurants, hospital , hotels etc. CITY GUIDE is an efficient website.
It provides everyone with the detailed description about everything which is there in the city and is going
to happen in future and guides the visitors with stories and event listings.
1.1 City Guide Project Modules:
There are four modules in our project .They are listed below with their description.
1. Administrator Module
2. Login/signup Module
3. User Module
1.1.1Administrator Module:
The admin module is the major module as it is responsible for carrying out the major operations
regarding site updates. It maintains information regarding other two modules. The various
software components in administrator module update alerts, update restaurants, and update site
information with reference to fig1.1.
The details regarding complete history such as political and social is entered by admin and he
want he can edit the details once entered. The details regarding emergency such as phone
numbers of with respect to emergency is entered by admin and he can edit the details one he
entered. The details regarding conventional places such as description, location, address and
image of the place entered by him and he can edit the details once entered.
7
.
ADMIN
LOGIN
UPDATE VERIFY MANAGE
STATUS USER DETAILS STORED INFORMATION
fig 1.1:-Working of Administrator
1.1.2 Login/Sign up Module:
In this module Poster enter the User id and password is checked and only valid user id and
password will get entry into member’s zone. This is a security feature to avoid entry of
unauthorized users.
Through this module new posters can sign up them. After giving their details, they will get a user
id and password. Then to get entry into poster section they need to provide this id and password
and only poster with valid id and password will get entry into poster zone. This is also a security
feature to avoid entry of unauthorized user.
1.1.3 User Module:

There are mainly two types of user (with reference fig1.2) who are participating in the website.
8
User1 –
User 1 is the Advertiser who will register himself to post the classifieds and other
advertisements on the website which when verified by the admin is displayed on the website.
This information can be retrieved by user 2.
User 2-
User 2 is the visitor who can perform the following task:-
 Search appropriate location and places to explore.

 Retrieve the best activity going to happen in the city.
 Able to retrieve full information for any of the selected option.
USER
USER 1(ADVERTISER) USER 2(VISITOR)
REGISTER
REGISTER
LOGIN LOGIN
POST ADDS SEARCH SELECT USE
fig 1.2:- Working of User
9
Chapter-2
SYSTEM DESIGN
Health:
It provides the information regarding the hospitals in the city. The health module displays the
information about the hospitals, health centers, pathology labs, gyms etc. This module lets the
user to know about each and every detail of the health related places present in the city. Also this
makes it easier and convenient for the visitor to check about these places all on the single
platform. As we know that being fit is the major goal of every one nowadays , be they are youth
,children or senior citizens so in that way this module is a major attraction of our city guide with
the reference of fig2.1.
Restaurant:
This module wake to provide service facility to restaurant and also to the customer . The services
that are provided is reservation and table management by the customer through the system ,
customer information management and table information management are the major task of the
administrator Main objective to build the system is to provide ordering and reservation service
to the customer. With this system reservation management will become easier and systematic to
replace traditional systems.
Education:
School web sites, especially in the public sector, are generally under-developed. Lack of
expertise among non-teaching staff has been a contributing factor, and many institutions have not
acted to make their web presence a priority; these schools perceive themselves as 'stretched' with
respect to budgets and time. Thus this CITY GUIDE website is viewed as a public face for the
schools present in a particular city - a more sophisticated newsletter or advertisement.
10
Beauty:
This module displays all the beauty and grooming centers in the city. This provides the user to
check for the appropriate center according to individual requirements. This module also provides
bookings according to the time slots available and also helps the user to check for the availability
of the free slots for their particular work.
Classifieds:
The classified section of the guide is for the advertiser. While signing up for the guide the
required field asks the user to opt for the choice of being an advertiser or the visitor. Using this
module the advertiser can post the ads for rental homes, jobs and many other relatable things.
HEALTH STORE
CITY GUIDE
EDUCATED BANK
BEAUTY
fig 2.1:-Working of modules
11
Chapter-3
SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information to recommend improvements on the system. It is a problem-solving activity that
requires intensive communication between the system users and system developers. System
analysis or study is an important phase of any system development process. The system is
studied to the minutest detail and analyzed. The system analyst plays the role of the interrogator
and dwells deep into the working of the present system. The system is viewed as a whole and the
input to the system are identified. The outputs from the organizations are traced to the various
processes. System analysis is concerned with becoming aware of the problem, identifying the
relevant and decisional variables, analyzing and synthesizing the various factors and determining
an optimal or at least a satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now the existing system is subjected to close study and problem areas
are identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then
weighed with the existing system analytically and the best one is selected. The proposal is
presented to the user for an endorsement by the user. The proposal is reviewed on user request
and suitable changes are made. This is loop that ends as soon as the user is satisfied with
proposal.
Preliminary study is the process of gathering and interpreting facts, using the information for
further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does various
feasibility studies. In these studies, a rough figure of the system activities can be obtained, from
which the decision about the strategies to be followed for effective system study and analysis can
be taken.
12
3.1 Project Scope: -
The aim of this project is to design, build and test a “providing a platform to the citizens’ so that
they can search anything go around” system. This will be a vastly complex software
development project which will take approximately two semesters to complete. The project will
be split up into stages and documented thoroughly throughout.
Project management is a key factor of this task to ensure the strict deadlines are adhered to. It is
also of paramount importance that tried and tested practices and techniques from the field are
adhered to ensure that no common development project mistakes are reproduced.
3.2 Problem Faced: -
Problem statement is one of the basic and important phases of project development. When the
basic problem is determined, it is documented and the symptomatic problem is analyzed, then the
current list of basic problem is completed. A system is simply a set of components that interact to
accomplish some purpose.
In this maintaining the details of different types of tasks , their status , details of tasks , their
self-rating , login details of the different types of users ( Appraise , Appraiser, Reviewer, and
Admin), personal details of the employees. Final evaluation details, employee average rating and
consolidated rank details are to be kept in a database and also can be retrieved easily when the
authorized user wants to get or update the data.
13
Chapter-4
PROPOSED SYSTEM
The aim of proposed system is to develop a system of improved facilities. The proposed system
can overcome all the limitations of the existing system. The system provides proper security and
reduces the manual work. The existing system has several disadvantages and many more
difficulties to work well. The proposed system tries to eliminate or reduce these difficulties up to
some extent. The proposed system will help the user to reduce the workload and mental conflict.
The proposed system helps the user to work user friendly and he can easily do his jobs without
time lagging.
4.1 Feasibility Study: -
Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus, when a new application is proposed it
normally goes through a feasibility study before it is approved for development.
The document provides the feasibility of the project that is being designed and lists various areas
that were considered very carefully during the feasibility study of this project such as Technical,
Economic and Operational feasibilities. The following are its features:
4.2 Economic Feasibility: -
The developing system must be justified by cost and benefit. Criteria to ensure that effort is
concentrated on project, which will give best, return at the earliest. One of the factors, which
affect the development of a new system, is the cost it would require.
14
The following are some of the important financial questions asked during preliminary
investigation:
 The costs conduct a full system investigation.

 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also, all the resources are already available, it gives an indication of the
system is economically possible for development.
4.3 Technical Feasibility: -
The system must be evaluated from the technical point of view first. The assessment of this
feasibility must be based on an outline design of the system requirement in the terms of input,
output, programs and procedures. Having identified an outline system, the investigation must go
on to suggest the type of equipment, required method developing the system, of running the
system once it has been designed.
Technical issues raised during the investigation are:
 Does the existing technology sufficient for the suggested one?
 Can the system expand if developed?
The project should be developed such that the necessary functions and performance are achieved
within the constraints. The project is developed within latest technology. Through the technology
may become obsolete after some period of time, due to the fact that never version of same
software supports older versions, the system may still be used. So, there are minimal constraints
involved with this project. The system has been developed using Java the project is technically
feasible for development.
4.4 Operational Feasibility: -
An estimate should be made to determine how much effort and care will go into the deploying of
the system including the training to be given to the user. Usually, people are reluctant to change
that come in their progression. The computer initialization will certainly affected the turn over,
15
transfer and employee job status. Hence an additional effort is to be made to train and educate
the user in the new way of the system.
16
Chapter-5
CHARTS AND GRAPHS
5.1 Flow Chart: -
A flowchart is a type of diagram that represents an algorithm, workflow or process, showing the
steps as boxes of various kinds, and their order by connecting them with arrows. This
diagrammatic representation illustrates a solution model to a given problem. Flowcharts are used
in analyzing, designing, documenting or managing a process or program in various fields.
 Flow chart symbols: -
Flowcharts use special shapes to represent different types of actions or steps in a process. Lines
and arrows show the sequence of the steps, and the relationships among them. These are known
as flowchart symbols with reference to fig-5.1.
Fig-5.1: - Symbols of flow chart

START
17
LOGIN REGISTRATION
IS VALID NO
YES
YES NO
IS
ADMIN
ADMIN USER
CHANGE PASSWORD AND CHANGE PASSWORD AND
PROFILE PROFILE
MANAGE CLASSIFIED VIEW CLASSIFIED
MANAGE HEALTH CENTER LIST

VIEW HEALTH LIST
MANAGE BEAUTY CENTER LIST VIEW BEAUTY CENTER
MANAGE RESTAURANT LIST VIEW RESTAURANT DETAILS
STOP
Fig-5.2: - Flow Chart
18
5.2 Data Flow Diagram:-
A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a preliminary step
to create an overview of the system without going into great detail, which can later be elaborated.
DFDs can also be used for the visualization of data processing (structured design).
A DFD shows what kind of information will be input to and output from the system, how the
data will advance through the system, and where the data will be stored. It does not show
information about process timing or whether processes will operate in sequence or in parallel,
unlike a traditional structured flowchart which focuses on control flow, or a UML activity
workflow diagram, which presents both control and data flows as a unified model.
Database Input System Output Customer
Fig- 5.3: - Example of DFD
19
Symbols of DFD: -
VIEWER REGISTRATION REGISTRATION POSTER

LOGIN LOGIN
SEARCH POST A NEW
INFORMATION CITY ADDS
GUIDE
VIEW ADDS EDIT & MAINTAIN ADS
SEND RESPONSE VIEW RESPONSES

EDIT INFORMATION POST INFORMATION
ADMINISTRATOR
Fig - 5.4: - 0 level DFDs
20
Search View
Information Information
Viewer
Database
View Database
Search
Ads Send
Ads Response
View
Ads Post
Responses
Ads
Category
Edit Login Poster
Ads Process
New Poster
Maintain
View Registered Users
Category Registered
Users
Send
Administrator
Notification
Manage
Info
Maintain
Advertisers’
Details Database
Fig 5.5:- 1 level DFD

21
5.3 E-R Diagram:-
Definition:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships
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.
Entity Relationship (ER) diagram:
This diagramming technique is used to visually present a database schema or data model and was
original proposed by Chen in the 1970s. There are many different data modeling notations; some
are very similar to UML class diagrams (with the exception of operations). However, the
notation the used here is slightly different, as proposed by Elmasrietal.
The database schema for this system is shown in figure. The table object has been left out of the
diagram because the table management feature set had been dropped from the requirements
before this stage of the design process.
Some important database design decisions are as follows:
o To store the total price of an order with the order rather than calculating it on the fly when
looking at past orders. This is because the price of menu items could change at any time, so
the total price at the time of ordering must be stored so that the total price is not incorrectly
calculated in future.
o Similar to the previous point, the order receipt is stored as a hard-copy and not regenerated
when reviewing past orders because things such as the restaurant name or VAT percentage
are subject to change. Receipts stored need to be exactly the same as the customer copy in
case of dispute.
22
CITY GUIDE
Fig 5.6:- ER Diagram
23
5.4 Gantt Chart: -
A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. On the left of the chart is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar; the position and length of the bar reflects the start date, duration and end date of the activity.
This allows you to see at a glance:
 What the various activities are

 When each activity begins and ends
 How long each activity is scheduled to last
 Where activities overlap with other activities, and by how much
 The start and end date of the whole project
PHASE-1
Description Start Date Duration End Date
Planning 05-Oct-18 2 07-Oct-18
System Design 07-Oct-18 10 17-Oct-18
Architect Design 30-Oct-18 12 11-Nov-18
Module Design 13-Nov-18 20 03-Dec-18
24
Module Design
Architect Design
Start Date
Duration
System Design
Planning
Fig-5.7: -Phase1 Gantt chart
PHASE-2
Description Proposed start Duration End date
date
Development 1-feb-19 30 03-mar-19
Integration and 5-mar-19 15 20-mar-19
testing
Implementation 25-mar-19 15 09-apr-19
Operations 10-apr-19 04 14-apr-19
Operations
Implementation
Proposed Start Date
Duration
Integration &Testing
Development
Fig-5.8: - Phase2 Gantt chart
25
Chapter-6
THE V-MODEL
In software development, the V-model represents a development process that may be considered
an extension of the waterfall model, and is an example of the more general V-model. Instead of
moving down in a linear way, the process steps are bent upwards after the coding phase, to form
the typical V shape. The V-Model demonstrates the relationships between each phase of the
development life cycle and its associated phase of testing. The horizontal and vertical axes
represent time or project completeness (left-to-right) and level of abstraction (coarsest-grain
abstraction uppermost), respectively.
Fig-6.1:- Verification and Validation model ( V-model)
26
 Verification phases
- Requirements analysis
- System design
- Architecture design
- Module design
 Validation phases
- Unit testing
- Integration testing
- System testing
- User acceptance testing
27
Chapter-7
SYSTEM SPECIFICATIONS
7.1 Software Requirements:-
TOOLS/PLATFORMS, LANGUAGES:
Front End : Html, JavaScript, CSS

 User friendly GUI
 Client-Side Validation
 Adaptive Design
Middle- Tier : C#,Asp.net

 Microsoft visual studio
Back End : SQL server

 Security
 Performance
 Scalability
 Reliability
 Support RDBMS concepts
 Microsoft SQL Server Management
Studio
28
7.2 Hardware Requirements: -
DEVELOPER SIDE:-
PCs
 Memory: minimum 8GB RAM Memory
 Monitor: 1024 x 728 pixel resolution or better
 Hard drive: 512Gigabyte, at least gigabytes free
 Processors: minimum intel i5 versions or better
CLIENT SIDE:-
PCs
 Memory: Minimum 1GB RAM Memory
 Monitor: 1024 x 728 pixel resolution or better
 Hard drive: 512Gigabyte configuration at least 1GB Free
 Processors: minimum AMD series or high
29
Chapter-8
SYSTEM TESTING
Software Testing is the process of executing software in a controlled manner, in order to answer
the question - Does the software behave as specified? Software testing is often used in
association with the terms verification and validation. Validation is the checking or testing of
items, includes software, for conformance and consistency with an associated specification.
Software testing is just one kind of verification, which also uses techniques such as reviews,
analysis, inspections, and walkthroughs. Validation is the process of checking that what has been
specified is what the user actually wanted.
Validation : Are we doing the right job?
Verification : Are we doing the job right?
Software testing should not be confused with debugging. Debugging is the process of analyzing
and localizing bugs when software does not behave as expected. Although the identification of
some bugs will be obvious from playing with the software, a methodical approach to software
testing is a much more thorough means for identifying bugs. Debugging is therefore an activity
which supports testing, but cannot replace testing.
Other activities which are often associated with software testing are static analysis and dynamic
analysis. Static analysis investigates the source code of software, looking for problems and
gathering metrics without actually executing the code. Dynamic analysis
looks at the behavior of software while it is executing, to provide information such as execution
traces, timing profiles, and test coverage information.
Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers based
system. Nothing is complete without testing, as it vital success of the system testing objectives,
there are several rules that can serve as testing objectives.
30
They are :-
 Testing is a process of executing a program with the intend of finding an error.

 A good test case is one that has high possibility of finding an undiscovered error.
 A successful test is one that uncovers an undiscovered error.
If a testing is conducted successfully according to the objectives as stated above, it would

uncovered errors in the software also testing demonstrate that the software function appear to be
working according to the specification, that performance requirement appear to have been met.
There are three ways to test program.
 For correctness
 For implementation efficiency
 For computational complexity
Test for correctness are supposed to verify that a program does exactly what it was designed to
do. This is much more difficult than it may at first appear, especially for large programs.
8.1 Test Plan
A test plan implies a series of desired course of action to be followed in accomplishing various
testing methods. The Test Plan acts as a blue print for the action that is to be followed. The
software engineers create a computer program, its documentation and related data structures. The
software developers is always responsible for testing the individual units of the programs,
ensuring that each performs the function for which it was designed. There is an independent test
group (ITG) which is to remove the inherent problems associated with letting the builder to test
the thing that has been built. The specific objectives of testing should be stated in measurable
terms. So that the mean time to failure, the cost to find and fix the defects, remaining defect
density or frequency of occurrence and test work-hours per regression test all should be stated
within the test plan.
31
The levels of testing include:
 Unit testing
 Integration Testing
 Data validation Testing
 Output Testing
8.1.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design – the software
component or module. Using the component level design description as a guide, important
control paths are tested to uncover errors within the boundary of the module. The relative
complexity of tests and uncovered scope established for unit testing. The unit testing is white-
box oriented, and step can be conducted in parallel for multiple components. The modular
interface is tested to ensure that information properly flows into and out of the program unit
under test. The local data structure is examined to ensure that data stored temporarily maintains
its integrity during all steps in an algorithm’s execution. Boundary conditions are tested to ensure
that all statements in a module have been executed at least once. Finally, all error handling paths
are tested.
Tests of data flow across a module interface are required before any other test is initiated. If data
do not enter and exit properly, all other tests are moot. Selective testing of execution paths is an
essential task during the unit test. Good design dictates that error conditions be anticipated and
error handling paths set up to reroute or cleanly terminate processing when an error does occur.
Boundary testing is the last task of unit testing step. Software often fails at its boundaries.
Unit testing was done in Sell-Soft System by treating each module as separate entity and testing
each one of them with a wide spectrum of test inputs. Some flaws in the internal logic of the
modules were found and were rectified.
32
8.1.2 Integration Testing
Integration testing is systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors associated with interfacing. The objective is to take
unit tested components and build a program structure that has been dictated by design. The entire
program is tested as whole. Correction is difficult because isolation of causes is complicated by
vast expanse of entire program. Once these errors are corrected, new ones appear and the process
continues in a seemingly endless loop.
After unit testing in Sell-Soft System all the modules were integrated to test for any
inconsistencies in the interfaces. Moreover differences in program structures were removed and a
unique program structure was evolved.
8.1.3 Validation Testing or System Testing

This is the final step in testing. In this the entire system was tested as a whole with all forms,
code, modules and class modules. This form of testing is popularly known as Black Box testing
or System tests.
Black Box testing method focuses on the functional requirements of the software. That is, Black
Box testing enables the software engineer to derive sets of input conditions that will fully
exercise all functional requirements for a program.
Black Box testing attempts to find errors in the following categories; incorrect or missing
functions, interface errors, errors in data structures or external data access, performance errors
and initialization errors and termination errors.
8.1.4 Output Testing or User Acceptance Testing

The system considered is tested for user acceptance; here it should satisfy the firm’s need. The
software should keep in touch with perspective system; user at the time of developing and
making changes whenever required. This done with respect to the following points
 Input Screen Designs,

 Output Screen Designs,
 Online message to guide the user and the like.
33
The above testing is done taking various kinds of test data. Preparation of test data plays a vital
role in the system testing. After preparing the test data, the system under study is tested using
that test data. While testing the system by which test data errors are again uncovered and
corrected by using above testing steps and corrections are also noted for future use.
8.2 Validation Checking:

At the culmination of integration testing, software is completely assembled as a package;
interfacing errors have been uncovered and corrected, and a final series of software test-
validation checks may begin. Validation can be defined in many ways, but a simple definition
(Albeit Harsh) is that validation succeeds when software functions in a manner that can be
reasonably expected by a customer. Software validation is achieved through a series of black-box
tests to be conducted and a test procedure defines specific test cases that will be used in attempt
to uncover errors in conformity with requirements. Both the plan and procedure are designed to
ensure that all functional requirements are satisfied; all performance requirements are achieved;
documentation is correct and human –Engineered and other requirements are met. Once the
application was made free of all logical and interface errors , inputting dummy data to ensure
that the software developed satisfied all the requirements of the user did validation checks
.However , the data are created with the intent of determining whether the system will process
them correctly .
In the proposed system, if the clients click the send button after selecting a file from his file list,
then the system will show the confirmation message for sending files. Similarly if a client makes
an attempt to download a file from the server file list, then also the system will show the
confirmation message for downloading. This is how the data validations were made in the
proposed system.
34
Chapter-9
SYSTEM IMPLEMENTATION
The purpose of System Implementation can be summarized as follows: making the new system
available to a prepared set of users (the deployment), and positioning on-going support and
maintenance of the system within the Performing Organization (the transition). At a finer level of
detail, deploying the system consists of executing all steps necessary to educate the Consumers
on the use of the new system, placing the newly developed system into production, confirming
that all data required at the start of operations is available and accurate, and validating that
business functions that interact with the system are functioning properly. Transitioning the
system support responsibilities involves changing from a system development to a system
support and maintenance mode of operation, with ownership of the new system moving from the
Project Team to the Performing Organization.
A key difference between System Implementation and all other phases of the lifecycle is that all
project activities up to this point have been performed in safe, protected, and secure
environments, where project issues that arise have little or no impact on day-to-day business
operations. Once the system goes live, however, this is no longer the case. Any miscues at this
point will almost certainly translate into direct operational and/or financial impacts on the
Performing Organization. It is through the careful planning, execution, and management of
System Implementation activities that the Project Team can minimize the likelihood of these
occurrences, and determine appropriate contingency plans in the event of a problem.
9.1 Implementation Methods:-
Implementation is a process of ensuring that the information system is operational. It involves −
 Constructing a new system from scratch.
 Constructing a new system from the existing one.
Implementation allows the users to take over its operation for use and evaluation. It involves
training the users to handle the system and plan for a smooth conversion.
35
9.1.1Conversion Methods:-
The four methods of conversion are −
 Parallel Conversion:-
Old and new systems are used simultaneously.
 Direct Cutover Conversion:-

New system is implemented and old system is replaced completely.
 Pilot Approach:-
Supports phased approach that gradually implement system across all users.
 Phase-In Method:-
Working version of system implemented in one part of organization based on feedback, it is

installed throughout the organization all alone or stage by stage.
9.2 Implementation plan:-

One of my favorite management tools is the implementation plan I develop to support my
strategic plan.
An implementation plan breaks each strategy into identifiable steps, assigns each step to one or
more people and suggests when each step will be completed. For example, if one strategy is to
create a membership campaign, one step might be to design a membership brochure. This
project might be assigned to a member of the marketing or development staff and might be
planned for completion in December of this year.
If there is no effective method to carry out the strategic plan, the strategic plan is likely to
collect dust and can lead to planning backlash, the feeling that planning is a waste of time. In an
industry where the scarcity of resources is always a key limiting factor, good planning is
essential.
Implementation is the carrying out, execution, or practice of a plan, a method, or any design,
idea, model, specification, standard or policy for doing something. As such, implementation is
the action that must follow any preliminary thinking in order for something to actually happen.
36
9.2.1 Major Tasks:-
This section provides a brief description of each major task required for the implementation of
the system. Add as many subsections as necessary to this section to describe all the major tasks
adequately. The tasks described in this section are not site-specific, but generic or overall project
tasks that are required to install hardware and software, prepare data, and verify the system.
Include the following information for the description of each major task, if appropriate:
 What the task will accomplish

 Resources required to accomplish the task
 Key person(s) responsible for the task
 Criteria for successful completion of the task
 Examples of major tasks are the following:
 Providing overall planning and coordination for the implementation
 Providing appropriate training for personnel
 Ensuring that all manuals applicable to the implementation effort are available when
needed
 Providing all needed technical assistance
 Scheduling any special computer processing required for the implementation
 Performing site surveys before implementation
 Ensuring that all prerequisites have been fulfilled before the implementation date
 Providing personnel for the implementation team
 Acquiring special hardware or software
9.2.2 Implementation Schedule:-
In this section, provide a schedule of activities to be accomplished during implementation. Show
the required tasks in chronological order, with the beginning and end dates of each task.
37
Chapter-10
DATABASE DESIGN
A database is an organized mechanism that has the capability of storing information through
which a user can retrieve stored information in an effective and efficient manner. The data is the
purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements are gathered
together and a database is designed which will meet these requirements as clearly as possible.
This step is called Information Level Design and it is taken independent of any individual
DBMS.
In the second step, this Information level design is transferred into a design for the specific
DBMS that will be used to implement the system in question. This step is called Physical Level
Design, concerned with the characteristics of the specific DBMS that will be used. A database
design runs parallel with the system design.
The organization of the data in the database is aimed to achieve the following two major
objectives.
 Data Integrity
 Data independence
Normalization is the process of decomposing the attributes in an application, which results in a
set of tables with very simple structure. The purpose of normalization is to make tables as simple
as possible.
Normalization is carried out in this system for the following reasons.
 To structure the data so that there is no repetition of data , this helps in saving.
 To permit simple retrieval of data in response to query and report request.
 To simplify the maintenance of the data through updates, insertions,
 Deletions.
 To reduce the need to restructure or reorganize data which new application
 Requirements arise.
38
10.1 Relational Database Management System (RDBMS):-
A relational model represents the database as a collection of relations. Each relation resembles a
table of values or file of records. In formal relational model terminology, a row is called a tuple,
a column header is called an attribute and the table is called a relation. A relational database
consists of a collection of tables, each of which is assigned a unique name. A row in a tale
represents a set of related values.
10.1.1 Relations, Domains & Attributes:

A table is a relation. The rows in a table are called tuples. A tuple is an ordered set of n
elements. Columns are referred to as attributes. Relationships have been set between every table
in the database. This ensures both Referential and Entity Relationship Integrity. A domain D is a
set of atomic values. A common method of specifying a domain is to specify a data type from
which the data values forming the domain are drawn. It is also useful to specify a name for the
domain to help in interpreting its values. Every value in a relation is atomic, that is not
decomposable.
10.1.2 Relationships:-
 Table relationships are established using Key. The two main keys of prime importance are
Primary Key & Foreign Key. Entity Integrity and Referential Integrity Relationships can be
established with these keys.
 Entity Integrity enforces that no Primary Key can have null values.
 Referential Integrity enforces that no Primary Key can have null values.
 Referential Integrity for each distinct Foreign Key value, there must exist a matching Primary
Key value in the same domain. Other key are Super Key and Candidate Keys.
 Relationships have been set between every table in the database. This ensures both
Referential and Entity Relationship Integrity.
10.1.3 Normalization:-
As the name implies, it denoted putting things in the normal form. The application developer via
normalization tries to achieve a sensible organization of data into proper tables and columns and
where names can be easily correlated to the data by the user. Normalization eliminates repeating
groups at data and thereby avoids data redundancy which proves to be a great burden on the
computer resources. These includes:
39
 Normalize the data.
 Choose proper names for the tables and columns.
 Choose the proper name for the data.
 First Normal Form:-
The First Normal Form states that the domain of an attribute must include only atomic values
and that the value of any attribute in a tuple must be a single value from the domain of that
attribute. In other words 1NF disallows “relations within relations” or “relations as attribute
values within tuples”. The only attribute values permitted by 1NF are single atomic or indivisible
values.
The first step is to put the data into First Normal Form. This can be donor by moving data into
separate tables where the data is of similar type in each table. Each table is given a Primary Key
or Foreign Key as per requirement of the project. In this we form new relations for each non-
atomic attribute or nested relation. This eliminated repeating groups of data.
A relation is said to be in first normal form if only if it satisfies the constraints that contain the
primary key only.
 Second Normal Form:
According to Second Normal Form, for relations where primary key contains multiple attributes,
no non-key attribute should be functionally dependent on a part of the primary key.
In this we decompose and setup a new relation for each partial key with its dependent attributes.
Make sure to keep a relation with the original primary key and any attributes that are fully
functionally dependent on it. This step helps in taking out data that is only dependent on a part of
the key.
A relation is said to be in second normal form if and only if it satisfies all the first normal form
conditions for the primary key and every non-primary key attributes of the relation is fully
dependent on its primary key alone.
40
 Third Normal Form:-
According to Third Normal Form, Relation should not have a non-key attribute functionally
determined by another non-key attribute or by a set of non-key attributes. That is, there should be
no transitive dependency on the primary key.
In this we decompose and set up relation that includes the non-key attributes that functionally
determines other non-key attributes. This step is taken to get rid of anything that does not depend
entirely on the Primary Key.
A relation is said to be in third normal form if only if it is in second normal form and more over
the non key attributes of the relation should not be depend on other non-key attribute.
10.2 Tables Structure

Table Name: Admin
Primary Key: id
FIELD NAME DATA TYPE SIZE

Name Varchar 45
Email Varchar 45
Username Varchar 45
Password Varchar 45
ID Varchar 45
Table-10.1
41
Table Name: beauty
Primary Key: id
Field Name Data Type SIZE

Name Varchar 45
Contact Varchar 45
Otime Varchar 45
Ctime Varchar 45
Address Varchar 45
Location Varchar 45
Image Longblob
Id Varchar 45
Love Varchar 45
Unlike Varchar 45
Table-10.2
Table Name: classified
Primary Key: id

Name Varchar 255
Contact Varchar 45
Address Varchar 450
Desc Varchar 450
Image Longblob
Userid Varchar 450
Id Varchar 450
Table-10.3
42
Table Name: education
Primary Key: id

Name Varchar 255
Contact Varchar 45
Type Varchar 450
Option Varchar 450
Language Varchar 45
Address Varchar 450
Location Varchar 450
Image Longblob
Id Varchar 450
Love Varchar 45
Table-10.6
Table Name: health
Primary Key: id

Name Varchar 45
Contact Varchar 45
Otime Varchar 45
Ctime Varchar 45
Address Varchar 45
Location Varchar 45
Image Longblob
Id Varchar 45
Love Varchar 45
Unlike Varchar 45
Table-10.7
43
Table Name: restrauant
Primary Key: id

Name Varchar 45
Contact Varchar 45
Total table Varchar 45
Price Varchar 45
Address Varchar 45
Location Varchar 1000
Image Longblob
Id Varchar 450
Love Varchar 45
Unlike Varchar 45
Table-10.8
44
Chapter-11
SAMPLE CODE
Fig 11.1:- Home page
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Index.aspx.cs"

Inherits="Index" %>
<!DOCTYPE html> </html>

<head>
<title>City Guide</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta charset="utf-8">
<meta name="keywords" content="Fast Service a Responsive web template, Bootstrap Web
Templates, Flat Web Templates, Android Compatible web template,
Smartphone Compatible web template, free webdesigns for Nokia, Samsung, LG, SonyEricsson,
Motorola web design" />
<link href="css/bootstrap.min.css" rel="stylesheet" type="text/css" media="all">
<link href="css/fontawesome-all.min.css" rel="stylesheet" type="text/css" media="all">
<link href="css/easy-responsive-tabs.css" rel='stylesheet' type='text/css' />
<link rel="stylesheet" href="css/flexslider.css" type="text/css" media="all">
45
<link rel="stylesheet" type="text/css" href="css/style_common.css" />
<link rel="stylesheet" type="text/css" href="css/style1.css" />
<link href="css/style.css" rel="stylesheet" type="text/css" media="all" />
<link href="//fonts.googleapis.com/css?family=Roboto:400,500,700,900" rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Open+Sans:400,600,700,800"
rel="stylesheet">
</head>
<body>
<form runat="server">
<header>

<nav class="navbar navbar-expand-lg navbar-light">
<a class="navbar-brand" href="Index.aspx">City Guide</a>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-
target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-
expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarSupportedContent">

<ul class="navbar-nav ml-auto">
<li class="nav-item ">
<a class="nav-link" href="Index.aspx">Home </a>
</li>
<li class="nav-item">
<a class="nav-link" href="MerchantLogin.aspx">Merchant</a>
</li>
<a class="nav-link" href="Login.aspx">User</a>
</li>
<a class="nav-link " href="AdminLogin.aspx">Admin</a>
</li>
<a class="nav-link " href="News.aspx">News</a>
</li>
<a class="nav-link " href="Videos.aspx">Videos</a>
</li>
</ul>
</nav>


46

<div class="w3l_banner_info">
<div class="slider">
<div class="callbacks_container">
<ul class="rslides" id="slider3">
<li>
<div class="slider-img">
<div class="slider_banner_info">
<div class="text">
<h3 class="word wisteria">
Be So Good,They can't Ignore you
</div>
</div>
</div>
</li>
<li>
<div class="slider-img-2">
<div class="text">
<h3 class="word wisteria">Good Food, Good Mood</h3>
</div>
</div>
</div>
</li>
<li>
<div class="slider-img-3">
<div class="text">
<h3 class="word wisteria">Dear God,Today I woke up.I'm healthy
and alive thank you!!</h3>
</div>
</div>
</div>
</li>
</ul>
</div>
</div>
</div>

</header>
47
<section class="bannerbottom py-lg-5 py-md-4 py-md-3 py-2">
<div class="bannerbottom py-lg-5 py-md-4 py-md-3 py-2">
<div class="container">
<div class="row">
<div class="col-md-4 col-sm-12 w3_ban1">
<div class="card">
<img class="card-img-top" src="images/bb1.jpg" alt="Card image cap">
<div class="card-body">
<h5 class="card-title">Education</h5>
<p class="card-text">Some quick example text to build on the Fast
Service and make up the bulk of the card's content.</p>
<a href="User/UserHome.aspx?catid=1" class="btn btn-
primary">Explore</a>
</div>
</div>
</div>
<div class="card">
<h5 class="card-title">Health Care</h5>
</div>
</div>
</div>
<div class="card">
<h5 class="card-title">Beauty</h5>
</div>
</div>
</div>
<div class="col-md-4 col-sm-12 w3_ban">
<div class="card">
<h5 class="card-title">Store</h5>
48
</div>
</div>
</div>
<div class="card">
<h5 class="card-title">Bank</h5>
</div>
</div>
</div>
<div class="card">
<h5 class="card-title">Shopping Complex</h5>
</div>
</div>
</div>
</div>
</div>
</div>
</section>




49

<section class="footer">
<h3>City Guide</h3>
<div class="wrapper">
<ul class="social-icons icon-circle icon-zoom list-unstyled list-inline">
<li><a href="#"><i class="fab fa-facebook-f"></i></a></li>
<li><a href="#"><i class="fab fa-twitter"></i></a></li>
<li><a href="#"><i class="fab fa-linkedin-in"></i></a></li>
</ul>
</div>
<div class="copyright">
<p>© 2018 Fast Service. All Rights Reserved | Design by <a
href="https://w3layouts.com/">W3layouts</a></p>
</div>
</div>
</section>


<div class="modal video-modal fade" id="myModal" tabindex="-1" role="dialog" aria-
labelledby="myModal">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
City Guide
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span aria-hidden="true">×</span>
</button>
</div>
<section>
<div class="modal-body">
<div class="loginf_module">
<div class="module form-module">
<div class="toggle">
<i class="fa fa-times fa-pencil"></i>
<div class="tooltip">Register</div>
</div>
<div class="form">
<h3>Login to your account</h3>
<form action="#" method="post">
<input type="text" name="Username" placeholder="Username"
required="">
<input type="password" name="Password" placeholder="Password"
required="">
<input type="submit" value="Login">
50
</form>
<div class="cta">
<a href="#">Forgot password?</a>
</div>
</div>
<div class="form">
<h3>Create a new account</h3>
<form action="#" method="post">
<input type="text" name="Username" placeholder="Username"
required="">
<input type="password" name="Password" placeholder="Password"
required="">
<input type="email" name="Email" placeholder="Email address"
required="">
<input type="text" name="Phone" placeholder="Phone Number"
required="">
<input type="submit" value="Register">
</form>
</div>
</div>
</div>
</div>
</section>
</div>
</div>
</div>

<script src="js/jquery.min.v3.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/move-top.js"></script>
<script src="js/easing.js"></script>
<script src="js/SmoothScroll.min.js"></script>


<script src="js/responsiveslides.min.js"></script>
<script>
// You can also use "$(window).load(function() {"
$(function () {
// Slideshow 4
$("#slider3").responsiveSlides({
auto: true,
pager: true,
nav: false,
speed: 500,
51
namespace: "callbacks",
before: function () {
$('.events').append("<li>before event fired.</li>");
},
after: function () {
$('.events').append("<li>after event fired.</li>");
}
});
});
</script>

<script src="js/easy-responsive-tabs.js"></script>
<script>
$(document).ready(function () {
$('#horizontalTab').easyResponsiveTabs({
type: 'default', //Types: default, vertical, accordion
width: 'auto', //auto or any width like 600px
fit: true, // 100% fit in a container
closed: 'accordion', // Start closed if in accordion view
activate: function (event) { // Callback function if tab is switched
var $tab = $(this);
var $info = $('#tabInfo');
var $name = $('span', $info);
$name.text($tab.text());
$info.show();
}
});
$('#verticalTab').easyResponsiveTabs({
type: 'vertical',
width: 'auto',
fit: true
});
});
</script>


<script type="text/javascript">
$(window).load(function () {
$("#flexiselDemo1").flexisel({
visibleItems: 4,
animationSpeed: 1000,
autoPlay: true,
autoPlaySpeed: 3000,
pauseOnHover: true,
52
enableResponsiveBreakpoints: true,
responsiveBreakpoints: {
portrait: {
changePoint: 480,
visibleItems: 1
},
landscape: {
changePoint: 640,
visibleItems: 2
},
tablet: {
changePoint: 768,
visibleItems: 3
}
}
});
<script type="text/javascript" src="js/jquery.flexisel.js"></script>

});
</script>

<script src="js/jquery.magnific-popup.js" type="text/javascript"></script>
<script>
$('.popup-with-zoom-anim').magnificPopup({
type: 'inline',
fixedContentPos: false,
fixedBgPos: true,
overflowY: 'auto',
closeBtnInside: true,
preloader: false,
midClick: true,
removalDelay: 300,
mainClass: 'my-mfp-zoom-in'
});
});
</script>
var words = document.getElementsByClassName('word');
var wordArray = [];
var currentWord = 0;
words[currentWord].style.opacity = 1;
for (var i = 0; i < words.length; i++) {
53
splitLetters(words[i]);
}
function changeWord() {
var cw = wordArray[currentWord];
var nw = currentWord == words.length - 1 ? wordArray[0] : wordArray[currentWord +
1];
for (var i = 0; i < cw.length; i++) {
animateLetterOut(cw, i);
}
for (var i = 0; i < nw.length; i++) {

nw[i].className = 'letter behind';
nw[0].parentElement.style.opacity = 1;
animateLetterIn(nw, i);
}
currentWord = (currentWord == wordArray.length - 1) ? 0 : currentWord + 1;

}
function animateLetterOut(cw, i) {
setTimeout(function () {
cw[i].className = 'letter out';
}, i * 80);
}
function animateLetterIn(nw, i) {
setTimeout(function () {
nw[i].className = 'letter in';
}, 340 + (i * 80));
}
function splitLetters(word) {
var content = word.innerHTML;
word.innerHTML = '';
var letters = [];
for (var i = 0; i < content.length; i++) {
var letter = document.createElement('span');
letter.className = 'letter';
letter.innerHTML = content.charAt(i);
word.appendChild(letter);
letters.push(letter);
}
wordArray.push(letters);
}
54
changeWord();
setInterval(changeWord, 4000);
</script>


<script src="js/jquery.waypoints.min.js"></script>
<script src="js/jquery.countup.js"></script>
<script>
$('.counter').countUp();
</script>


<script src="js/skill.bars.jquery.js"></script>
<script>
$('.skillbar').skillBars({
from: 0,
speed: 4000,
interval: 100,
decimals: 0,
});
});
</script>


<script>
$('.toggle').click(function () {
// Switches the Icon
$(this).children('i').toggleClass('fa-pencil');
// Switches the forms
$('.form').animate({
height: "toggle",
'padding-top': 'toggle',
'padding-bottom': 'toggle',
opacity: "toggle"
}, "slow");
});
</script>
var slideIndex = 1;
showSlides(slideIndex);
55
function plusSlides(n) {
showSlides(slideIndex += n);
}
function currentSlide(n) {
showSlides(slideIndex = n);
}
function showSlides(n) {
var i;
var slides = document.getElementsByClassName("mySlides");
var dots = document.getElementsByClassName("dot");
if (n > slides.length) { slideIndex = 1 }
if (n < 1) { slideIndex = slides.length }
for (i = 0; i < slides.length; i++) {
slides[i].style.display = "none";
}
for (i = 0; i < dots.length; i++) {
dots[i].className = dots[i].className.replace(" active", "");
}
slides[slideIndex - 1].style.display = "block";
dots[slideIndex - 1].className += " active";
}
</script>


/*
var defaults = {
containerID: 'toTop', // fading element id
containerHoverID: 'toTopHover', // fading element hover id
scrollSpeed: 1200,
easingType: 'linear'
};
*/
$().UItoTop({ easingType: 'easeOutQuart' });
});
</script>



jQuery(document).ready(function ($) {
$(".scroll").click(function (event) {
56
event.preventDefault();
$('html,body').animate({ scrollTop: $(this.hash).offset().top }, 1000);
});
});
</script>
$(function () {
$('[data-toggle="popover"]').popover()
})
</script>


</form>
</body>
</html>

Fig 11.2:- User Login

<div class="row signup" style="display: none;">
<div class="col-lg-10 col-lg-offset-1" style="margin-top: 100px;">
<div class="panel panel-default">
<div class="panel-heading">
Signup
57
<div class="btnDiv pull-right">
<button class="btn btn-primary btn-xs" id="loginBtn">Login</button>
</div>
</div>
<div class="panel-body">
<form class="form-horizontal" action="Signup" method="post" >
<div class="col-lg-6">
<div class="form-group">
<label for="inputEmail3" class="col-sm-2 control-label">Name</label>
<div class="col-sm-10">
<input type="text" class="form-control" name="name" placeholder="Enter
name.." required="required" id="nameId"
onkeypress="return onlyAlphabets(event,this);">
<p style="color: red;" class="nameError"></p>
</div>
</div>
<label for="inputEmail3" class="col-sm-2 control-label">Phone</label>
<input type="text" class="form-control" name="phone"
maxlength="10"placeholder="Enter phone.."oninvalid="this.setCustomValidity('Plese Enter a
valid phone number must be 10 digit')" oninput="setCustomValidity('')" required="required"
id="phoneId" onkeypress="return onlyNos(event,this);">
<p style="color: red;" class="phoneError"></p>
</div>
</div>
<label for="inputEmail3" class="col-sm-2 control-label">Gender</label>
<select class="form-control" name="gender" required="required">
<option>Male</option>
<option>FeMale</option>
</select>
</div>
</div>
<label for="inputEmail3" class="col-sm-2 control-label">DOB.</label>
<input type="date" class="form control"name="dob"required="required"id="dobId">
<p style="color: red;" class="dobError"></p>
</div>
</div>
</div>
58
<label for="inputEmail3" class="col-sm-2 control-label">Select Purpose</label>
<select class="form-control" name="purpose" required="required">
<option>Visitor</option>
<option>Advertist</option>
<option>Both</option>
</select>
</div>
</div>
<label for="inputEmail3" class="col-sm-2 control-label">Email</label>
<input type="email" class="form-control" name="email" placeholder="Enter
Email" required="required" id="email_Id">
<p style="color: red;" class="emailError"></p>
</div>
</div>
<label for="inputEmail3" class="col-sm-2 control-label">Username</label>
<input type="text" class="form-control" name="username" placeholder="Enter your username"
required="required" id="usernameId">
<p style="color: red;" class="usernameError"></p>
</div>
</div>
<label for="inputPassword3" class="col-sm-2 control-label">Password</label>
<input type="text" class="form-control" name="password" placeholder="Enter Password"
required="required" id="passwordId">
<p style="color: red;" class="passwordError"></p>
</div>
</div>
<div class="col-sm-offset-2 col-sm-10">
<button type="submit" class="btn btn-default btn-block" >Save</button>
</div>
</div>
</div>
</form>
</div>
</div>
</div>
</div>
</div>
59
$("#nameId").blur(function(){
var phone=$("#nameId").val();
if (phone.length<3)
{
$('.nameError').html("The name must be 3 characters!");
$('#nameId').focus();
return false;
}
else if(phone.length>=3)
{
$('.nameError').html("");
$('.nameError').hide();
}
});
$("#phoneId").blur(function(){
var phone=$("#phoneId").val();
if (phone.length<10||phone.length>10)
{
$('.phoneError').html("The phone must be 10 characters!");
$('#phoneId').focus();
return false; }
else if (phone.length==10)
{
$('.phoneError').hide();});
$("#email_Id").blur(function(){
var email=$("#email_Id").val();
var atpos = email.indexOf("@");
var dotpos = email.lastIndexOf(".");
if (atpos<1 || dotpos<atpos+2 || dotpos+3>email.length) {
$('.emailError').html("Please enter a valid email!");
$('#email_Id').focus();
return false;
}
else
{
$('.emailError').hide();
}});
$("#usernameId").blur(function(){
var username=$("#usernameId").val();
if (username.length>12||username.length<6) {
$('.usernameError').html("username must be 6 to 12 character!");
$('#usernameId').focus();
60
return false;
}
else
{
$('.usernameError').hide();
}});
$("#passwordId").blur(function(){
var password=$("#passwordId").val();
if (password.length>12||password.length<6) {
$('.passwordError').html("password must be 6 to 12 character!");
$('#passwordId').focus();
return false; }
else
{
$('.passwordError').hide();
fig 11.3:- Admin Login

<%@include file="navbar1.jsp"%>
<div class="container-fluid">
<div class="row" style="margin-top:0px!important;">
<img src="image/city1.jpg" alt="" class="img-responsive" style="height:600px;
width:100%!important;"/></div>
61
<div class="row" style="margin-top:0px!important;">
<h1 style="margin-top:0px!important;" class="text-center"><strong class="heading">welcome
<span style="color: #009999;">to</span>
<span style="color: red;">city guide </span></strong></h1><hr/>
<p>City Guide is an information guide that is proposed to provide various information about
Gr.Noida like Entertainment Places, Educational institutes, social activities and other important
places such as shopping centers, commercial complexes etc.</p><p class="text-justify"
style="font-size: 20px;"></p>
<p>This website will provide fast, convenient and user-friendly public e-services to business
and citizens. This platform brief information about the city by using efficient software. To get
details about the top restaurants, theaters, events, hotels etc CITY GUIDE is an efficient
website.It provides everyone with the detailed description about everything which is there in the
city and is going to happen in future and guides the visitors with stories and event listings.This
website will provide fast, convenient and user-friendly public e-services to business and citizens.
This platform brief information about the city by using efficient software.</p>
<p class="text-justify" style="font-size: 20px;"></p></div></div>
Fig 11.4:-Restaurent page

<div class="row">
62
<div class="well well-lg text-center" >Reastaurant List <span class="badge" style="padding:
8px;"><%ArrayList<RestaurantModel>
restoDb=(ArrayList<RestaurantModel>)session.getAttribute("restoDb");
if(restoDb!=null)
{
for(RestaurantModel show: restoDb)
{
count++;
}} %>
<%=count%></span></div></div>
<div class="row list">
<%int counta=0;
if(restoDb!=null)
{
for(RestaurantModel show: restoDb)
{
counta++;%>
<div class="col-lg-3"> <div class="boxDiv" >
<div class="image"><img alt="" src="image/1.jpg" class="img-responsive"></div>
<div class="cotent">
<ul class="list-group">
<li class="list-group-item text-center active">
<%=show.getName() %> </li>
<li class="list-group-item text-center list-group-item-success">
<%=show.getAddress()%> </li>
<li class="list-group-item list-group-item-info">
Contact : <span class="badge"><%=show.getContact()%></span></li>
Price/table : <span class="badge"><%=show.getPrice()%></span> </li>
Like : <span class="badge" style="background-color: green;">
<%=show.getLove()%></span> </li>
UnLike : <span class="badge" style="background-color: red;">
<%=show.getUnlike()%></span></li></ul></div>
<div class="btnDiv panel-footer" style="margin-top: -20px; background-color: #111; height:

40px; padding-right: 0px;">
<a href="LikeResto?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-up fa-1x"
style="color: red;"></i></a>
<a href="UnlikeResto?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-down fa-1x"
style="margin-left: 20px; color: yellow;"></i></a></div>
<a href="<%=show.getLocation()%>" target="_blank"><button class="btn btn-xs btn-info btn-
block">Location!</button></a></div>
63
<button class="btn btn-xs btn-primary btn-block" id="<%=counta%>"
onclick="bookNow(this.id)" ata-toggle="modal" data-target="#myModal">Book Now!
</button></div></div></div>
</div>
<input type="hidden" id="name<%=counta%>" value="<%=show.getName()%>">

<input type="hidden" id="address<%=counta%>" value="<%=show.getAddress()%>">
<input type="hidden" id="price<%=counta%>" value="<%=show.getPrice()%>">
<input type="hidden" id="id<%=counta%>" value="<%=show.getId()%>"<%}} %>
</div>
Fig 11.5:- Health page

<div class="row">
<div class="well well-lg text-center" >Health List
<span class="badge" style="padding: 8px;">
<%
int count=0; ArrayList<HealthModel>
healthDb=(ArrayList<HealthModel>)session.getAttribute("healthDb");
if(healthDb!=null)
{
for(HealthModel show: healthDb)
{
count++;
}} %>
<%=count%></span>
</div></div>
<div class="row list"<%

if(healthDb!=null)
{
for(HealthModel show: healthDb)
{ %>
<div class="col-lg-3"> 
<div class="boxDiv" >
64
<li class="list-group-item text-center active"> <%=show.getName()%> </li>
<li class="list-group-item text-center list-group-item-success">
<%=show.getAddress()%> </li>
Contact : <span class="badge"><%=show.getContact()%></span> </li>
Like : <span class="badge" style="background-color: green;"><%=show.getLove()%></span>
</li>
UnLike : <span class="badge" style="background-color:red;"><%=show.getUnlike()%></span>
</li></ul></div>
<div class="btnDiv panel-footer" style="margin-top: -20px; background-color: #111;

height: 40px; padding-right: 0px;"><div class="col-lg-4">
<a href="LikeResto?thisId=<%=show.getId()%>">
<i class="fa fa-thumbs-o-up fa-1x" style="color: red;"></i></a>
<a href="UnlikeResto?thisId=<%=show.getId()%>">
<i class="fa fa-thumbs-o-down fa-1x" style="margin-left: 20px; color: yellow;"></i></a></div>
<a href="<%=show.getLocation()%>" target="_blank"><button class="btn btn-xs btn-info btn-
block">Location!</button></a></div></div></div>
</div><%
}}%>
</div>
65
Fig 11.6:- Classified page
<%int count=0;
ArrayList<ClassifiedModel>
classifiedDb=(ArrayList<ClassifiedModel>)session.getAttribute("classifiedDb");
if(classifiedDb!=null)
{for(ClassifiedModel show: classifiedDb)
{
count++;
}}%> <%=count%></span>
</div></div>
<div class="row list"><%

if(classifiedDb!=null)
{
for(ClassifiedModel show: classifiedDb)
{%>
<li class="list-group-item text-center active"> <%=show.getName()%> </li>
<li class="list-group-item text-center list-group-item-success"><%=show.getAddress()%> </li>
<%}}%>
</div></div>
66
Fig 11.7:- classify page
<div class="row">
<div class="well well-lg text-center" >
Beauty Lis<span class="badge" style="padding: 8px;"><%
int count =0;
ArrayList<BeautyModel>
beautyDb=(ArrayList<BeautyModel>)session.getAttribute("beautyDb");
if(beautyDb!=null)
{
for(BeautyModel show: beautyDb)
{
count++;
}}%>
<%=count%>
</span></div></div>

<a href="LikeHealth?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-up fa-1x"
<a
href="UnlikeHealth?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-down fa-1x"
style="margin-left: 20px; color: yellow;"></i></a></div>
67
<a href="<%=show.getLocation()%>" target="_blank">
<button class="btn btn-xs btn-info btn-block">Location!</button></a></div>
<button class="btn btn-xs btn-primary btn-block" id="<%=count%>"
onclick="bookNow(this.id)" ata-toggle="modal" data-target="#myModal">Book Now!
</button></div></div>
</div>
<input type="hidden" id="name<%=count%>" value="<%=show.getName()%>">
<input type="hidden" id="address<%=count%>" value="<%=show.getAddress()%>">
<input type="hidden" id="id<%=count%>" value="<%=show.getId()%>">

<%
}
}
%>
</div>
</div>
68
Fig 11.8:- Education page
<div class="row">
<div class="well well-lg text-center" >
Eductaion List
<span class="badge" style="padding: 8px;"><%
int count=0;
ArrayList<EducationModel>
eduDb=(ArrayList<EducationModel>)session.getAttribute("eduDb");
if(eduDb!=null)
{
for(EducationModel show: eduDb)
{
count++;
}}%>
<%=count%></span></div></div>
<div class="row list"><%

if(eduDb!=null)
{
for(EducationModel show: eduDb)
{%>
<div class="image"<img alt="" src="image/1.jpg" class="img-responsive">
</div>
69
<li class="list-group-item text-center active"> <%=show.getName()%></li>
<li class="list-group-item text-center list-group-item-success"><%=show.getAddress()%></li>
Contact : <span class="badge"><%=show.getContact()%></span> </li>
Like : <span class="badge" style="background-color: green;"><%=show.getLove()%></span>
</li>
<li class="list-group-item list-group-item-info">UnLike : <span class="badge"
style="background-color: red;"><%=show.getUnlike()%></span>
</li></ul></div>

<a href="LikeResto?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-up fa-1x"
<a href="UnlikeResto?thisId=<%=show.getId()%>"><i class="fa fa-thumbs-o-down fa-1x"
style="margin-left: 20px; color: yellow;"></i></a>
</div>
<a href="<%=show.getLocation()%>" target="_blank">
<button class="btn btn-xs btn-info btn-block">Location!</button></a>
</div></div></div>
<%
}
}
%>
</div>
</div>
Fig 11.9:- Acount page
<div class="container-fluid">
<div class="row">
<div id="carousel-example-generic" class="carousel slide" data-ride="carousel">

70
<ol class="carousel-indicators">
<li data-target="#carousel-example-generic" data-slide-to="0" class="active"></li>
<li data-target="#carousel-example-generic" data-slide-to="1"></li>
<li data-target="#carousel-example-generic" data-slide-to="2"></li>
<li data-target="#carousel-example-generic" data-slide-to="3"></li> </ol>


<div class="carousel-inner" role="listbox">
<div class="item active">
<img src="image/slide/rest/1.jpg" >
</div>
<div class="item">
</div>
<div class="item ">
</div>
<div class="item">
</div> </div>


<a class="left carousel-control" href="#carousel-example-generic" role="button" data-
slide="prev">
<span class="glyphicon glyphicon-chevron-left" aria-hidden="true"></span>
<span class="sr-only">Previous</span> </a>
<a class="right carousel-control" href="#carousel-example-generic" role="button" data-
slide="next">
<span class="glyphicon glyphicon-chevron-right" aria-hidden="true"></span>
<span class="sr-only">Next</span></a></div>
</div>
<br><br>
<div class="panel panel-primary" id="bookedRestoDiv">

<div class="panel-body">
<h3 style="text-align: center;">Booked Order Details</h3>
<div class="row">
<div class="col-lg-12" >
<table class="table table-bordered">
<thead>
<tr>
<th>Sl.no</th>
<th>Name</th>
<th>Contact</th>
71
<th>Resto Name</th>
<th>Table.</th>
<th>Price/Table</th>
<th>TotalPrice</th>
<th>Address</th>
</tr>
</thead>
<tbody ><%
int count123=1;
ArrayList<BookRestoModel>
bookedRestoDb=(ArrayList<BookRestoModel>)session.getAttribute("bookedRestoDb");
if(bookedRestoDb!=null)
{
for(BookRestoModel show: bookedRestoDb)
{%>
<tr>
<td><%=count123++ %></td>
<td><%=show.getName()%></td>
<td><%=show.getContact()%></td>
<td><%=show.getItemName()%></td>
<td><%=show.getNumberOfTable()%></td>
<td><%=show.getPrice()%></td>
<td><%=show.getTotalPrice()%></td>
<td><%=show.getAddress()%></td></tr>
<%
}}
%>
</tbody>
</table>
<hr>
</div></div>
</div> 
</div>
72
Fig 11.10:- Admin page
<h1 data-shadow='CityGuide!'>CityGuide!</h1>
<div class="row login" id="AdminLogin">
<div class="col-lg-6 col-lg-offset-3" style="margin-top: 120px;">
<div class="panel panel-info">
<div class="panel-heading">
Admin Login

</div>
<div class="panel-body" style="padding-left:30px;padding-right:30px;">

<p style="color: red"><%=wrong%></p>
73
<form class="form-horizontal" action="<%=request.getContextPath()
%>/AdminLogin" method="post">
<label for="inputEmail3" class="col-sm-2 control-label">Username</label>
<input type="text" class="form-control" name="username"
placeholder="Username/Email...." required="required">
</div>
</div>
<label for="inputPassword3" class="col-sm-2 control-label">Password</label>
<input type="password" class="form-control" name="password"
placeholder="Password" required="required">
</div>
</div>
<div class="col-sm-offset-2 col-sm-10">
<button type="submit" class="btn btn-primary btn-block">Sign in</button>
</div>
</div>
</form>
</div>
</div>
</div>
</div>
74
Chapter-12
CONCLUSION
The project titled as “CITY GUIDE” is a web based application. This software is developed with
scalability in mind. Additional modules can be easily added when necessary. The software is
developed with modular approach. All modules in the system have been tested with valid data
and invalid data and everything work successfully. Thus the system has fulfilled all the
objectives identified and is able to replace the existing system.
The project has been completed successfully with the maximum satisfaction of the organization.
The constraints are met and overcome successfully. The system is designed as like it was decided
in the design phase. The project gives good idea on developing a full-fledged application
satisfying the user requirements.
The system is very flexible and versatile. This software has a user-friendly screen that enables
the user to use without any inconvenience. Validation checks induced have greatly reduced
errors. Provisions have been made to upgrade the software. The application has been tested with
live data and has provided a successful result. Hence the software has proved to work efficiently.
75
Chapter-13
REFRENCE
BOOKS:
 Charles Hampfed (2000) ‘Instant Java Server Pages’ University of Toronto

 Herbert Schildt (2000) ‘Java Complete Reference’ Tata McGraw Hill
 John Zukowski (2000) ‘Mastering Java2’ BPB Publications
 Jamie Jaworsky ‘J2EE Bible’ Techmedia
 Stefen Denninger ‘Enterprise Java Beans-2.1’ Author’s Press
 Ian Somerville ‘Software engineering’
 Rajeev mall ‘Software engineering’
 Elmasri Navathe ‘Fundamentals of database systems’
ONLINE REFERENCE:
 www.theserverside.com
 www.java.sun.com
76
77
78

City Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

City Guide

Загружено:

Авторское право:

Доступные форматы

PROJECT REPORT

Ankita Singh (1513210031)

Department of Computer Science and Engineering

Name: Garima Kumari - (1513210056)

Ankita Singh - (1513210031)

Department of Computer Science and Engineering

Place: Greater Noida Garima kumari(1513210056)

Date:1/06/2019 Ankita Singh (1513210031)

Gaima kumari- (1513210056)

 Information to be collected through classifieds posted on the guide by various social,

1.1 City Guide Project Modules:

UPDATE VERIFY MANAGE

STATUS USER DETAILS STORED INFORMATION

fig 1.1:-Working of Administrator

1.1.2 Login/Sign up Module:

1.1.3 User Module:

User 2 is the visitor who can perform the following task:-

 Search appropriate location and places to explore.

USER 1(ADVERTISER) USER 2(VISITOR)

POST ADDS SEARCH SELECT USE

fig 1.2:- Working of User

fig 2.1:-Working of modules

3.2 Problem Faced: -

4.1 Feasibility Study: -

4.2 Economic Feasibility: -

 The costs conduct a full system investigation.

4.3 Technical Feasibility: -

4.4 Operational Feasibility: -

 Flow chart symbols: -

Fig-5.1: - Symbols of flow chart

MANAGE CLASSIFIED VIEW CLASSIFIED

MANAGE HEALTH CENTER LIST

MANAGE BEAUTY CENTER LIST VIEW BEAUTY CENTER

MANAGE RESTAURANT LIST VIEW RESTAURANT DETAILS

Fig-5.2: - Flow Chart

Database Input System Output Customer

Fig- 5.3: - Example of DFD

VIEWER REGISTRATION REGISTRATION POSTER

SEND RESPONSE VIEW RESPONSES

Fig - 5.4: - 0 level DFDs

Fig 5.5:- 1 level DFD

Entity Relationship (ER) diagram:

Some important database design decisions are as follows:

Fig 5.6:- ER Diagram

 What the various activities are

Planning 05-Oct-18 2 07-Oct-18

System Design 07-Oct-18 10 17-Oct-18

Architect Design 30-Oct-18 12 11-Nov-18

Module Design 13-Nov-18 20 03-Dec-18

Fig-5.7: -Phase1 Gantt chart

Fig-5.8: - Phase2 Gantt chart

Fig-6.1:- Verification and Validation model ( V-model)

7.1 Software Requirements:-

Front End : Html, JavaScript, CSS

Middle- Tier : C#,Asp.net

Back End : SQL server

Validation : Are we doing the right job?

Verification : Are we doing the job right?

 Testing is a process of executing a program with the intend of finding an error.

If a testing is conducted successfully according to the objectives as stated above, it would

There are three ways to test program.

8.1 Test Plan

8.1.1 Unit Testing

8.1.3 Validation Testing or System Testing