Objectives
- To guide customers throughout their tour in Nepal minimizing their expenses and to
provide satisfaction during the period of our service.
- To facilitate the visitor to make reservation.
- Incase of any inquiry, our project provide feedback service.
- Provide package tours to places in Nepal like Pokhara, Chitwan and other visiting
places.
Problems
1. As the current system was manual and the customers couldn’t get enough detailed
information and options to know about different visiting places of Nepal through the
system.
2. They had to visit time and again the organization for small inquiries which would loss
their effort and time.
3. The customers were unable to know time schedule of tour packages which used to get
changing with situations and the customers could not plan their timing according to them.
4. Also, the customers who are far from the organization could not book their tour packages
in their desired day as they had to visit the organization to do it where booking in phone
calls was not accepted as payment is not assure in that case so when they would come to
the organization, they had to face problems like as: the destinated day would already be
packed up or no tour package in that day.
5. The information/data were not made updated to the customers in the current system with
the changes made in the organization.
6. The records have high possibility of being lost or
New System Requirements
The new system has following requirements. Some of them are listed as below.
- Online booking of customers for tour packages.
- Inquiry.
- Feedback
- Information about different places of Nepal just visiting website.
- Updated information about tour packages and changes
- Events of the agency are updated on the new proposed system.
COST AND BENEFITS
The proposed new system provides benefits in long run, thus never takes user in loss.
They are listed as below:
COST
The new proposed system consists of development, implementation and operational phase
which cost accordingly and are described below:
Development Cost
The development cost is the one that is calculated by the developer once at the time when
system is to be developed. It includes the costs like salaries of workers that have involvement
in the development of the system, purchase of software, hardware and initial user training if
required.
Implementation Cost
The implementation cost covers the expenses that include the expenses related with the
implementation of the new system such as cost for the installation of required hardware and
software that is essential to run the system. Apart from that the cost of acquiring important
devices like computer, printers as well as communicative equipments like telephone/fax,
routers, etc.
Operational Cost
The operational cost includes the expenses that are calculated after the implementation of the
system and continue while the system is in use. These are the costs that include the system is
in phase of maintaining, ongoing training, annual software license fees and other costs that
will come according to the new system requirement.
BENEFITS
To The Customer
To The Company
- The staff members do not need of turning a pile of file book for searching customer
- The agency can be visited not only by the people living in Nepal but worldwide
because of the new proposed system which helps the agency to be promoted.
Hardware 40,000
Coding 24,000
Design 20,000
Software 10,000
OPERATIONAL COST
Marketing 80,000
Others 20,000
By the end of year 5, the cumulative benefits are NRS 30, 00,100 which is near NRS
26, 20,000 cumulative costs through that year. By the end of year 6, the NRS 39, 20,100
cumulative benefits have exceeded the cumulative costs which are NRS 35, 90,000. At some
point in time, closure to the end of year 6 the accumulated cost and benefits are equal. The
payback period of the proposed new system is therefore, approximately 5.5 years.
WORK DISTRIBUTION:
Work Distribution plays an important role in the development of project. There should
be an equal contribution of each member of a group. In our project, we have three
individual members who have equally given their best in each part of the project to
develop it.The work distribution is as follows:
AESHU SHERCHAN
Proposal:
1. Introduction
2. Proposal of the new system
3. Initial new system requirements
4. Hardware and Software requirement
5. Cost/Benefit
6. Gantt Chart
Analysis:
1. Introduction
2. Fact Finding
- Questionnaire
- Sampling
3. Description of current system
- Illustration supporting narrative
- Process Flows
4. Requirement specification for new system
Design
1. Description of new system
- Process flows
2. Detailed design
- Data design
- Architectural design
- Procedural design
- Interface design
Proposal:
1. Introduction
2. Proposal of the new system
3. Initial new system requirements
4. Hardware and Software requirement
5. Cost/Benefit
6. Gantt Chart
Analysis:
1. Introduction
2. Fact Finding
- Observation
- Document Review
3. Description of current system
- Problems and Limitations of current system
- Scope and Constraints
4. Requirement specification for new system
Design
1. Description of new system
- Narrative
2. Detailed design
- Data design
- Architectural design
- Procedural design
- Interface design
Hardware
1. Developer's side
• A websever
• A database server
2. User's side
• A normal computer
• Printer
Software Equipment
1. Developer's side
• Front End =XHTML,RSS Feed
• Back End=Php,XML,My SQL
• Window/Linux with internet connection
• Micro media Dream weaver
2. User's side
• Window/Linux with internet connection
• An internet browser
• RSS Feed reader/RSS compatible browser
ANALYSIS
INTRODUCTION
The "Info Travel and Tour" is a company that provides complete tour packages within
different places of Nepal for both internal (Nepali citizens) and external (tourists) visitors.
The main aim of this company believes in is to help our country to rise economically through
tourism.
In the current system of the company, all the business operations are performed in a
manual way i.e. simply in a paper work. The business works from keeping staff and customer
records to management of tour packages and payment are all done manually in the company.
The customer has to walk to the company in order to get the information about company and
tour packages managed by it. Even though full details of places of Nepal and time schedule
of tour packages is not possible to know in a single day of visit.
So, it consumes a lot of time of both customers and the company. Similarly, to book or
cancel the tour packages customer has to again walk to the company though making phone
call is also done but confirmation of attending the tour package i.e. payment is only allowed
in cash which is not possible until visiting the company. Therefore, the company lacks to
provide comfort and flexibility of facilities to the customers in the current system. Along
with it, there is another dizziness of searching customer and staff record list in time from a
pile of record book. To make note of tour packages already organized and later be organized
in a paper work also losses time and effort. There is a greater risk of loosing important
records as the business work become vast and time goes by. Overall the current system of the
company is quite unsystematic, slow and difficult to handle the business operations.
The new system proposed by the company is totally based upon computerized system
along with online features as internet has become most common and popular on day to day
basis among people. So, the new system covers the drawbacks of current system in a great
extent. The online features that can found in the new system are:
1. Online reservation
The online reservation or booking is the feature through which users can reserve their
seats online without having to walk to the company choosing the tour package preferred and
suitable for them. These features give comfort to the users to complete all the procedures
required to have a tour package through online, and single staff of the company can register
all customer records ready for the tour package because of the online system. Besides these,
the users are facilitated to view different places and related tour package information
provided by the company in a while just surfing on internet. This saves the time and effort of
both the company and users with ease of comfortness and reliability.
Questions to Customer
• What is the reason behind visiting the travel agency?
• How often do you prefer to go in a tour?
• How often do you use internet?
• Do you think online reservation or payment meet your desired requirement?
• Does online system saves your time and effort?
Observation:
Observation is way of observing the current system is another fact finding technique. By
which it gives you additional perspective and a better understanding of system procedures.
Personal observation also let us to verify statement made in interviews whether procedures
relay operate as they describe or not.
Research:
Research is another fact finding techniques. Research includes reviewing book, journal, new
etc. Research also involve site visit where we can observe another system and exchange
views with other professional. Besides it we can get the answer to question Internet has
become one valuable tool.
Details Of Fact Finding Techniques are as Follows:
For Manager
50
40
30
20
10
50
40
30
20
10
50
40
30
20
10
• Do you think putting the information about tour package will help to reduce the
amount of enquiries?
50
40
30
20
10
50
40
30
20
10
50
40
30
20
10
Booking Both
Inquiry
40
30
20
10
50
40
30
20
10
50
40
30
20
10
Yes No
50
40
30
20
10
The current system of the travel agency is totally based upon written database methodology
or simply we can say as a manual system that is one of the oldest way used in most of the
fields to store the data/records. All the data including staff/customer records,
registration/booking records, customer information, etc. are kept in hand written papers. So,
to store the record and retrieve the record, it consumes a lot of time to turn pile of papers.
In current system, booking is taken through telephone calls which may create
misunderstanding between staff and visitor and the payment is also not guaranteed from the
visitor. Besides these, the visitors have to book the tour packages only in the office hours.
Problems And Limitations Of Current System
• As the current system is manual and the customers cannot get desired enough detailed
information and options to know about different visiting places of Nepal where tour
package is available through the system.
• The customers need to visit time and again the organization for small inquiries which
would loss their effort and time.
• The customers were unable to know time schedule of tour packages which used to get
changing with situations and the customers could not plan their timing according to
them.
• Also, the customers who are far from the organization could not book their tour
packages in their desired day as they had to visit the organization to do it where
booking in phone calls was not accepted as payment is not assure in that case so when
they would come to the organization, they had to face problems like as: the estimated
day would already be packed up or no tour package in that day.
• The information/data were not made updated to the customers in the current system
with the changes made in the organization.
• The records have high possibility of being lost or damaged.
Current
ORGANIZATIONAL CHART System
Reservation
Clerk Customer Agents
Inform
Customer Reservatio
available
Details n
seats/Room
Manage
Tour
Context Diagram (DFD Level 0):
Sales notification
Tour package enquiry
Transportation/Hotel
Customer
Confirmation
Enquiry of Booking
hotel
/transportation Payment
ticket
Availability of seat
Availability of notification
Send Payment
Customer Do Inquiry
Get Details
Receive Ticket Payment
Send
Confirmation/
Send Booking Cancellation Tour Keep Payment
Package Record
Details
Verify Tour
Confirmatio Package
n/Cancellati Tour Inquiry
Provide
on Ticket Details
Ticket/Room Notification
The Input Output Specifications of Current System:
Process No: 1
Process: Enquiry about tour package
Input (Customer): Tour Package detail
Output (Agent): Make note of the detail
Process No: 2
Process: Check the seat availability
Input (Customer): Ask for the availability of seat
Output (Agency): Confirm the seat is available
Process No3:
Process: Record the information of the customer
Input (customer): Provide all the required information to agency
Output (agency): Keep the record of the customer
Process No: 4
Process: Payment
Input (customer): If customer is on phone they will reserve the seats and if the customer is on
phone they will pay direct by walk
Output (agency): Gives the ticket of tour package to the customer and inform about the date
and time of start of tour package.
Input/output of Cancellation Process
Process No: 1
Process: Request for cancellation
Input (customer): Give their detail including name, address etc.
Output (Agency): Check for the validity of the tour package.
Process No: 2
Process: Check the validity of cancellation
Input (Agency): Check the term and condition sign by the customer
Output (Customer): Customer will be notify about the validation
Process No: 3
Process: If cancellation request is valid
Input (Agency): Money is refund to the customer according to business rule
Output (customer): Tour will cancelled as request by the customer
FLOWCHART OF CURRENT SYSTEM (BOOKING)
Start
Customer
Inquiry
Telephon
e Or
Walk-In
No
Manager
Inquiry
Yes if
booking
Notify the Customer
availabl
e?
Keep Customer
Detail Record
Booking/Payment
Stop
SCOPE AND CONSTRAINTS
Scope:
The main scope of the project is to create efficient way of booking especially for the
foreigner, to view tour package, to check whether the booking is all reserved or not .If the
reservation is not packed then give the visitor full privilege of on line booking and online
payment. By which visitor can get advantage of reservation on line which is efficient and fast
way of reservation in this 21st century. It has made visitor’s time consuming and easier as
they don’t have to bother of booking through phone. Today internet is not unknown to people
mostly in foreign country and this new system is introduced by the company with the
intension to attract more tourist in Nepal. The new system will overcome all its pros and cons
of current system. Online booking help the visitor as they don’t have to waste money in
booking through phone.
New Proposed system will give customer view of different tour package with on line
booking and on line payment. It promises to make the visitor inform about the delay of the
tour in case of some critical case. Moreover, this system will overcome problem of carry
money with them as there is a risk of getting lost of money in a long distance.
Requirement Specification:
In the proposed system, the requirements such as booking, payment, cancellations, enquiries
and management of tour package system are enclosed. This system satisfies all the
requirements related to the customers, agencies and administrative modules.
The requirements existing in the proposed system are mentioned below:
Administrator
(Full Privilege)
Control User
(Agencies)
End User
(Customer)
For the new system we intended to add some of the automated features like online
booking, login feature, email forwarding and storage of customer and company details that
has made the operations of the company reliable and efficient. And some parts will still
remain manual in the system. The main reason of some of the operations not being
automated i.e. manual is because of unavailability of service of PayPal.
The security is the main concerned feature of the new system. When a user intends to
use a common PC for all level of users then, authentication should be a main necessity. In
case, in the absence of security checks, any employee can access to the PC or hack the
details or manipulate the data which hampers the business management. It could lead to
many problems like loss of data, disorder of data, etc.
The new proposed system divides the top-level user i.e., the system administrators, into
two categories namely:
Operational privilege – Such privilege allows admin user to create control users and give
privilege to perform regular operation which shall be done by administrator.
Full privilege – Such privilege provide privilege to the admin users to create operational
admin users that could be perform by operational privilege admin users.
System administrator users are branched with control user such as bus agencies. Such user
can work for all the operational such as booking and basic self account operations.
The end users are the customer or passenger’s logging in the system for booking and
awaiting their tickets. They will not have the same full privilege as the administrator but are
given low privilege which is enough for them such as booking and cancellation
Process flows
Start
Web master/Admin
Login
Is user &
pass
true?
Manage System
Logout
Stop
Context level Diagram for New System
Login/Request
Control User/ Approval/Reject
Agents
View schedule/
booking
End-User/ Login/Be member
Member
Cancellation Request
Process No : 2
Process : For the Membership
Input (client) : Member/customer fill the membership form with their personal
details like name, address, phone number, concerned tour package
etc…
Output (system) : System will keep the filled information into database, and system
directs to the member/customer profile page
Process No : 3
Process : For searching
Input (customer) : Customers select the desire tour package, hotel, etc. from the
optional values displayed in the screen provided by the system.
Output (system) : System will display the customer booked tour package, hotels from,
to and price rate.
Process No : 4
Process : For Viewing tour package
Input (customer) : The member will click on the desired tour package.
Output (system) : The system will display the details about the tour package, hotels,
price etc
Process No : 5
Process : For booking
Input (customer) : The customer will fill up the form as provided by the system.
Output (System) : System will keep the filled information into database, and system
directs to the member/customer profile page
Process No : 6
Process : If tour package is not available on substitute options
Input (customer) : Customer will book the tour package for other accessible time and
schedule.
Output (system) : System will display the customer detail form.
Input/ Output Specification of Cancellations Process (New
system).
Process No : 1
Process : Enter system
Input (client) : Enters the system URL address e.g. (www.e-busnepal.com)
Output (system) : System will be opened displaying all the information relating like,
bus companies, seats available, bus routes etc…
Process No : 2
Process : Login into the system
Input (client) : Member enters their user name in login screen.
Output (system) : If the user name is valid, system will display the profile of the
member
Process No : 3
Process : View Booking
Input (client) : Member will view their booking bus seat and click on cancel icon.
Output (system) : System will display the “CR” text in status of member.
Process No : 4
Process : Cancellations
Input (client) : On Agent profile a request will be pending. If cancellation can be
done, agent will approve the cancellation request.
Output (system) : System will display the message “Ticket has been cancelled”.
Data Design
Handing of data is necessary in the system as there are many data in volume. In our
system My SQL is used for handling of data. The detail databases used in system are as
below:
Database Name: Green
Table Name Primary Key No of columns
annualreport reportID 3
tbl_admin 3
tbl_cat Cat_id 5
tbl_news newsId 5
tbl_cat2 Cat_id 5
tbl_product Product_id 10
tbl_product2 Product_id 10
tbl_item Item_id 6
Table Detail:
Table Name: annual report
Column Data Type Default Primary Key Foreign Key Null
Name
ReportID Int(5) - ReportID - No
ReportTitle Varchar(50) - - - No
Report Varchar(50) - - - No
Table name:tbl_admin
Column Data Type Default Primary Key Foreign Key Null
Name
admin_user varchar(25) - - - No
admin_pass Varchar(100) - - - No
admin_status int(1) - - - No
Normalization:
1NF:
green(ReportID, ReportTitle, Report, admin_user, admin_pass, admin_status,
cat_id,cat_name, cat_desc, cat_added, cat_status, NewsId, NewDate, NewsTitle,
NewsDetail, ExpireDate, cat_id, cat_name, cat_desc, cat_added, cat_status, cat_id,item_id,
item_name, item_desc, item_added, item_status, product_id, item_id, product_added,
product_name, product_desc, product_itinerary, product_image1, product_image2,
product_image3,product_days, product_id, item_id, product_added, product_name,
product_desc, product_itinerary, product_image1, product_image2, product_image3,
product_days.)
2NF
Admin
Admin_user, admin_pass, admin_status, ReportID, ReportTitle, ReportID, ReportTitle,
Report, News_Id, News_Date, NewsTitle, NewsDetail, ExpireDate
Cat2
cat_id, cat_name, cat_desc, cat_added, cat_status,cat_id,item_id,product_name,
product_added, product_desc, product_itinerary, product_image1, product_image2,
product_image3, product_days.
Cat
cat_id, cat_name, cat_desc, cat_added, cat_status, cat_id, item_id, item_name, item_desc,
item_added, item_status, product_id, product_desc,product_itinary, , product_image1,
product_image2, product_image3, product_days.
3NF
annualreport
ReportID, ReportTitle,Report
Tbl_admin
admin_user, admin_pass, admin_status
tbl_cat
cat_id, cat_name, cat_desc,cat_added, cat_status
tbl_news
NewsId, NewsDate, NewsTitle, NewsDetail,ExpireDate
tbl_cat2
cat_id, cat_name, cat_desc, cat_added, cat_status
tbl_item
cat_id, item_id, item_name, item_desc, item_added, item_status
tbl_product
product_id, product_added, product_name, product_desc, product_itinery, product_image1,
product_image2, product_image3, product_days
tbl_product_2
product_id, item_id, product_added, product_name, product_desc, product_itinerary,
product_image1, product_image2, product_image3, product_days
ARCHITECTURAL DESIGN
Architectural Design
The new system is based on web applications and provides online booking
facilities. All these processes and functions are done through the internet with help of
internet browser. The application of GUI (Graphical User Interface) used in this
system has made this system more effective to all the users. This system contain
storage, access and retrieval of data which get processed systematically
The modules with their related operations included in the system are described
below:
Administrative module:
1. Administrative management
i. Verify and accept new member
Verifying the new member and approving them. The member will be
approved by the admin users of the system.
ii. Listing the members
After the member request has been approved by the system
administrator their member will be approved and they are listed in the
system.
iii. Deleting members (Active/inactive)
The system administrator can delete the members if they aren’t in an
active position i.e. not using the system systematically.
iv. Managing the user interface of the system if required
If any system changes are needed to be changed the system admin
will change the system as until the system won’t fulfill the requirements.
Control user module:
The customers can search the tour package schedules and un-
booked seats of the concerned tour package, hotel and flight .
2. Search price and fare
This module provides the user interface for searching the tour
package, hotel and flight prices and fare which are provided by the
travel agency.
3. Booking
Hardware Development:
The proposed system above will require certain hardware development that can
meet company requirements to handle large amount of data. It should be capable to store,
process and retrieve output data despite of complex circumstances.
The hardware components selected for the company are as follows:
• Processor
The project was done under processor like Intel® Dual-Core processor
T4400 (2.20, 2.20) GHz. The respective processor detail was enough to
control the use of main storage to store data with the sequence of operations
and to create real time calculation.
• RAM
The memory used during the development was 1979 MB. It was sufficient
to accumulate the instructions coming up to be obeyed, instructions presently
to come, data pending processing, data currently processed and data coming
up for output.
• Storage
The storage used during the development process was 120 GB Hard-disk
Drive, system need to handle large volume of data
• UPS
UPS was required to maintain the work stability and save the work if incase
power was cut off during the time of work.
Development software:
The developed proposed system requires superior software to hold large
calculation and be able to retrieve the result easily in short period of time. Therefore,
the system would be best optimized when the calculations are run on the server and
then the outcomes are intended for the user through web browser. Since the calculations
are run on server there’s no reliance or overhead to the client machine.
The hardware components have been therefore, accordingly selected. The selections
are given below:
• Server-side Web Programming
For server side web programming the software tool used is PHP
(Hypertext Pre Processor) wamp5. PHP is the basis and is the best for the
development of proposed system.
• Database System
For the proposed system database MySQL 5.0.24 was used. This made the
proposed system to handle, deal with, operate large amount of data with no
trouble. MySQL and PHP installer comes in a same package so this software is
also open source.
• Graphics and layout
The proposed system development requires a lot of graphical work that
is user friendly and has lots of feature in one package. It contains around all
straightforward familiar tools for the user and easily use by the customer. For
proposed system Adobe Photoshop was used as graphics designing tool.
• Web Development Tool
Macromedia Dream Weaver 8 was used as web development tool.
Implementation hardware:
The developed proposed system requires high performance of computation,
retrieval, updating, and management operations on the server machine. The proposed
system is openly intended to hardware configurations on client side. So, the system
provides the similar performance irrelevant of hardware configuration on the
implementation side.
The suggested hardware requirements are:
• Processor:
The processor helps to run a program or system in short interval of time.
Here, the Internet browser helps to open the system in a short interval of
time. So, the processor is very important in proposed system.
• Storage:
The users don’t need extra disk space to run the systems as the operating
system itself includes an internet browser and all the data related to the
particular user is store in the server.
• RAM:
RAM is useful for open a proposed system in short period. It gives
relief to an extent for the computation; retrieval of data which are
manipulated by the server itself and results are send to users.
• Printer:
The end user needs a monochrome printer in order to print and
confirm the booking of tour package ticket .Customer can make the payment
for the concerned tour package after confirmation. Customers are free to
print the ticket numerous times as they require. The control users may need
to print the reports i.e. bookings (both confirmed and cancelled), transaction
reports etc. While the admin users may need to print the reports relating Bus
Company, routes, news/announcements etc.
Implementation software:
The proposed system needs minimum software specification with least
processing principle. As the system is a web-based application, internet connection is
must for the end users to use the system. The software requirements are specified as
below:
• Operating System:
As the system is a web-based, it requires an Operating System to run
the application. The proposed system operates efficiently on Windows Vista,
Linux, Windows Xp, Windows 7, Mac OS etc.
• Web browser:
• Each and every web based application need to have a Web Browser to run the
system. The proposed system is best optimized for Microsoft Internet Explorer.
Besides this, it can operate on other web browser such as Google Chrome, Fire Fox,
Safari etc.
Development
And
Implementation
Testing
Testing is an important part of program development which main purpose is to do tests
not to demonstrate that there are no errors in the program but to detect errors that may
still exist.
Testing Techniques Applied:
The program made by any professional programmer is never error free and perfect at
all despite all the programmers intend to make it completely error free. Some weak points
in the program always remain there. So, to reduce the errors as well as to check whether
the new system works properly or not before the end users use it, various testing
techniques are used. Such testing techniques applied in the system are described below:
Black Box Testing
1. Boundary Value Analysis
Boundary value analysis technique is used to obtain the test cases at the limit of input
range. For example: In the booking form, the name of the customer cannot exceed 25
characters.
2. Equivalence Partitioning
Equivalence testing technique is used to test the input data to ensure their valididity i.e.
valid or invalid. For example: In the admin/ Webmaster panel one valid adminname (that
doesn’t exist in the admin database) and one invalid adminname (that exist in the admin
database) is used to obtain the admin/webmaster panel.
White Box Testing
3. Loop Testing
Loop testing technique is used in order to make sure that all the loops that exist in the
program module functions correctly.
4. Data flow Testing
Data flow testing technique is used to simplify and make simple the data flow inherent in
the current system accordingly to which proposed new system can reflect the current
tendency.
5. Condition testing
Condition testing technique is used to test each and every condition used in the program
and to make sure that the modules executes as defined in the condition. For example: In
change password module, the old password of the admin is changed only if the admin
types the correct old password and that matches the old password.
6. Validation Testing
Validation testing technique is used to check the validation used in the program works
correctly as expected or not. JavaScript validation methods used in the program identify
any invalid data inputs and see that these inputs cannot be entered into the system.
7. Unit Testing
Unit testing technique is used to make sure that all the program modules are capable of
working independently or with other modules without any error.
8. Integration Testing
Integration testing technique is a logical combination of unit testing. It shows the
information flow between different modules. It is used to make sure that the complete
program module works properly with other module after combining the unit modules.
Implementation
Conversion Plan:
After the proposed new system got developed and tested in detail to reduce errors and
bugs, the system is ready to be implemented. The implementation part is done going
through the phases as described below:
Pre-Implementation:
1. Release Documentation:
The documentation is released in order to familiarize the end users with
the features and functions used in the new system. With the released
documentation that includes user manual and operations, the users can have
basic idea about the new system which will support them to understand the
system before attending any training session.
2. User Training:
The user training is most important part of the implementation phase
that gives user an opportunity to know about how to use the system before
using it in the actual operation. This helps them to have a comfortable
environment and can easily cooperate with the features of the system. In
the training, they would be toe them a better understanding on the role
they are playing within the system that will surely improve their work
performance.
3. Data Conversion:
As the current system is totally a manual system, so that it maintain all its
data in hard copies. Hence, to use the proposed new system all the data that
are maintained manually has to be entered into the new system before it
runs in the actual environment. For example: the data of staff records that is
stored manually will have to be entered into the new system’s database in
order to create users for the new system.
Post-Implementation:
1. Program reviews:
After the changeover procedure has been successfully completed, the system is
ready for operational practice in the live environment. Even though the system
has to be reviewed occasionally to make sure that the system is always capable
of satisfying user requirements. Along with that, feedbacks will be taken from
the users to ensure if they are having any kind of complicated problems using
the system and if any additional improvement is needed for the implemented
system.
2. Program Maintenance:
Both the members of our group Anita Gurung and Aeshu Sherchan will be
responsible for the distribution of user manual and documentation to the users. This
distribution will take a day for our group to do the task.
User training
Both the group members Anita Gurung and Aeshu Sherchan will be present for the
user training. The user training will be sub divided into two classes: basic computer
training (for those who are new and don’t have basic knowledge about computer)and
system training(to use the system). The user training will be conducted for two weeks
where both the basic computer training and system training will be done an hour a
day.
Data conversion
Our both group members will be present for data conversion including the users. As
the current system maintain all its data manually, those data should be entered into
the proposed new system which will be demonstrated among users as later they have
to enter the data into the new system when it is implemented.
In this procedure, there is both the involvement of our group members. Here, for the
conversion of current manual system into proposed new system phase conversion
technique will be used where both current manual system and new system will be
operated parallel. Our group members will be conducting the conversion by putting
the manual system data into the new system part by part and when all the parts of data
get successfully transmitted to the new system, the current system will be removed.
Critical Appraisal:
Group Appraisal:
Nepal Tourism board has declared 2011 as the tourism year so this travel agency thinks
of modify their website and added more facilities so that can attract more tourists from all
around the world and improvement of internal tourism in off season.
Through our findings and research, we have found on the current system do not have online
facilities of booking on the tour package. With the intension of visiting more tourists from all
over the world our team has decided over taking old system i.e. manual with new system.
The new system will be access easily to the end user or customer which will have more
facilities then current like on line booking system, email forwarding, view tour package with
all information and price. Beside it has important news included in the website.
As we have gone throughout the system our team had faced many problem and
limitation regarding the design and development. We have selected cost effective, common
and well known tool which are well-liked and easily available for the user. In development
and implementation phase hardware and software were selected, procedure design,
architecture design and data design were done for the backup of the system and incase if the
system gets corrupt or there is loss of the data then it will be helpful in the future .
Our system was generally divided into two sections one is the admin panel (web master)
other is end users (passengers).
1. Admin panel
Admin panel is the most essential part of the system that maintains and updates the
system. Admin can add, delete and edit the all information of the hotel, news, tour package
etc. The admin user has full privilege on the system. He/she can add, delete and edit the all
information of the hotel, news, tour package etc.
2. End User
End users are the people who browse the website. This system mostly focuses on the
system. They help the tour agency to run the business so the interface are made user friendly.
The system will give the end user to view all the information related to tour package, hotel
etc and can book online on the concern tour and hotel if they desire. The user will find the
system very useful and effective. Online booking will help them and they don’t have worry
about accommodation and traveling.
Individual Appraisal:
• Project Proposal
Both the members of our group visited the travel agency and
talked to the proprietor of the agency. Studying the manual system of the
agency, I found out the basic problems and limitations that the user faced
from the current system.
• Design
Studying the current manual system of the agency, through our group
discussions I performed the analysis to get concept to transform the
current process flow into the online system. For the interface design I
chose easy use, cost effective tools that are commonly used and popular
among users. I am also in charge for listing out the requirement
specification that is desirable in the system.
• Software Development
Though we together discussed and worked for the software
development I was mainly responsible for the development of
booking/reservation process of tour package. We discussed and studied the
current manual system of reservation process together. I was also
responsible to conceptualize and design the transformation of current users
operation into the online system. It would require process and data flow
into the new system as it was in manual system. Apart from these I was
given charge for the tasks listed in work distribution accordingly to be
completed individually with interaction on equal interval of time.
• Testing
I was in charge to test the test log whether it is working properly
or not.
• Implementation
As my task was to develop test logs, it would later be used for
checking whether the test logs worked properly or not as desired by the
system, I had next responsible for user training and demonstration but it was
group involvement task. I was also responsible to the others tasks listed in
work distribution.
Anita Gurung (1801-T107-0003)
• Project Proposal
I had to go through a detail study and list the initial requirements for
the proposed new system. And, the hardware and software equipment to be
used in the development also was my task to do. I also pointed out the scope
and constraints of the system.
• Analysis
For analysis, we our group members visited the travel agency and
collected the required information from the proprietor of the agency. I started
the analysis through travelling different travel agencies and bus companies
finding on my places along with discussing with friends and seniors. I made
the questionnaires for the agency proprietor for the requirements they need for
the agency and wanted in the new system. So that, I was responsible for
requirements specification expected by the new system.
• Design
We studied the current system of the agency through which I got the
working mechanism of agency’s manual system. Then, I prepared the process
flow of the new online system. I was also given the task of procedural design
based on the program structure and procedural information for each module
that should be presented.
• Software Development
Since this phase is most fundamental, we had gone through the
group study and discussions. And, I was given the task of booking/reservation
of hotel process. Beside this we all helped each other to their task aiming to
make the system user interface to the users/customers. I was also responsible to
the others tasks listed in work distribution.
• Testing
I was responsible for the test cases which was earlier prepared by my
group member. I prepared test case description, conclusion and result.
• Implementation
I took the responsibility for preparing the schedule and plan for
conversion and implementation. I was also responsible for User training and
demonstration which was a group involvement task.
Test Plan
SN. Description
1 Admin user login
4 Test if an error message is displayed when the admin user logs in with an invalid
username or password.
5 Test if the system displays the tour contents.
6 Test if the admin user can view list of tour package content.
7 Test if the admin user can view selected tour package content.
8 Test if the admin user can view general detail section of selected tour package.
9 Test if the admin user can view gallery section of the selected tour package.
10 Test if the admin user can view itinerary section of selected tour package.
11 Test if the admin user can view the tour package booking section.
12 Test if the admin user can edit the selected tour package content.
16 Test if the admin user can edit and delete tour package category.
17 Test if the admin user can add new item in the tour package category.
18 Test if the admin user can view the edit section of tour package category.
28 Test if the admin user can view general detail section of the selected hotel.
29 Test if the admin user can view the gallery section of selected hotel.
30 Test if the admin user can view itinerary section of selected hotel.
32 Test if the admin user can edit the selected hotel content.
36 Test if the admin user can edit and delete hotel category.
37 Test if the admin user can add new item in the hotel category.
38 Test if the admin user can view the edit section of the hotel category.
41 Test if the user can view the ‘home’ page of the company.
44 Test if the user can view the list of available tour packages.
45 Test if the user can view general detail section of the selected tour package.
46 Test if the user can view the gallery section of selected tour package.
47 Test if the user can view itinerary section of selected tour package.
48 Test if the user can view the tour package booking section.
50 Test if the user can view general detail section of the selected safari
51 Test if the user can view the gallery section of selected safari.
54 Test if the user can view the list of available rafting packages.
55 Test if the user can view general detail section of the selected rafting package.
56 Test if the user can view the gallery section of selected rafting package.
57 Test if the user can view itinerary section of selected rafting package.
60 Test if the user can view general detail section of the selected lodge.
61 Test if the user can view gallery section of the selected lodge.
62 Test if the user can view itinerary section of selected lodge.
63 Test if the user can view the lodge booking section..
64 Test if the user can view the list of available hotel.
65 Test if the user can view general detail section of the selected hotel
66 Test if the user can view the gallery section of selected hotel.
67 Test if the user can view itinerary section of selected hotel.
68 Test if the user can view the hotel booking section..
70 Test if the user can view the details clicking on the home page image.
71 Test if the user can download the files and images provided by the system.
72 Test if the user can open/save the selected file.
74 Test if the field filled more than its limitation is acceptable or not.
Test Log
ADMIN
SN 1
Description Admin user login
Input username: admin password: admin
Expected The admin user should be able to log in.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 2
Description Admin user logout
Input Click on the logout link.
Expected The admin user should be able to logout.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 3
Description Test if the admin user can change his/her account password.
Input old password: admin new password: admin1
Expected The admin user should be able to change his/her password.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 4
Description Test if an error message is displayed when the admin user logs in with an
invalid username or password.
Input Invalid username or password
Expected An error message should be displayed.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
TOUR PACKAGE
SN 5
Description Test if the system displays the tour contents.
Input Click on the 'TOUR’ link.
Expected The system should display the Tour contents.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 6
Description Test if the admin user can view list of tour package content.
Input Click on the ‘content list’ link.
Expected The system should display the list of tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 7
Description Test if the admin user can view selected tour package content.
Input Click on the desired tour package.
Expected The system should display the selected tour package page with contents.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 8
Description Test if the admin user can view general detail section of the selected tour
package.
Input Click on the ‘general detail’ icon.
Expected The admin user should be able to view general detail section of the
Result selected tour package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 9
Description Test if the admin user can view the gallery section of selected tour
package.
Input Click on the ‘gallery’ icon.
Expected The admin user should be able to view gallery section of selected tour
Result package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 10
Description Test if the admin user can view itinerary section of selected tour package.
Input Click on the ‘itinerary’ link.
Expected The admin user should be able to view itinerary section of selected tour
Result package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 11
Description Test if the admin can view the tour package booking section..
Input Click on the ‘booking’ link.
Expected The admin user should be able to view the tour package booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 12
Description Test if the admin user can edit the selected tour package content.
Input Click on the ‘edit’ icon.
Expected The admin user should be able to edit selected tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 13
Description Test if the admin user can delete tour package content.
Input Click on the ‘delete’ icon.
Expected The admin user should be able to delete tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 14
Description Test if the admin user can post new tour package content.
Input Click on the ‘post new content’ link.
Expected The admin user should be able to post or add tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 15
Description Test if the admin can add new tour package category.
Input Click on the ‘add new category’ link.
Expected The admin user should be able to add new tour package category.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 16
Description Test if the admin user can edit and delete tour package category.
Input Click on ‘edit category’ link.
Expected The admin user should be able to edit and delete tour package category.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 17
Description Test if the admin user can add new item in the tour package category.
Input Click on the ‘add new item’ link.
Expected The admin user should be able to add new item in the tour package
Result category.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 18
Description Test if the admin user can view the edit section of tour package category.
Input Click on the ‘edit item’ link.
Expected The admin user should be able to view the edit section of tour package
Result category.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 19
Description Test if the admin user can edit tour package content.
Input Click on the ‘edit’ icon.
Expected The admin user should be able to edit tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 20
Description Test if the admin user can delete tour package content.
Input Click on the ‘delete’ icon.
Expected The admin user should be able to delete tour package content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 21
Description Test if the admin user can add news.
Input Click on the ‘add news’ link.
Expected The admin should be able to add news.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 22
Description Test if the admin user can view and edit news.
Input Click on ‘view/edit news’ link.
Expected The admin user should be able to view and edit news.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 23
Description Test if the admin user can upload file.
Input Click on the ‘attach new file’ link.
Expected The admin user should be able to upload file.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 24
Description Test if the admin user can view and edit file.
Input Click on the ‘view/edit file’ link.
Expected The admin user should be able to view and edit the file.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
HOTEL
SN 25
Description Test if the system displays the hotel contents.
Input Click on the 'HOTEL’ link.
Expected The system should display the hotel contents.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 26
Description Test if the admin user can view list of hotel content.
Input Click on the ‘content list’ link.
Expected The system should display the list of hotel content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 27
Description Test if the admin user can view selected hotel content.
Input Click on the desired hotel.
Expected The system should display the selected hotel page with contents.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 28
Description Test if the admin user can view general detail section of the selected hotel.
Input Click on the ‘general detail’ icon.
Expected The admin user should be able to view general detail section of the
Result selected hotel.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 29
Description Test if the admin user can view the gallery section of selected hotel.
Input Click on the ‘gallery’ icon.
Expected The admin user should be able to view gallery section of selected hotel.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 30
Description Test if the admin user can view itinerary section of selected hotel.
Input Click on the ‘itinerary’ link.
Expected The admin user should be able to view itinerary section of selected hotel.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 31
Description Test if the admin can view the hotel booking section..
Input Click on the ‘booking’ link.
Expected The admin user should be able to view the hotel booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 32
Description Test if the admin user can edit the selected hotel content.
Input Click on the ‘edit’ icon.
Expected The admin user should be able to edit selected hotel content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 33
Description Test if the admin user can delete hotel content.
Input Click on the ‘delete’ icon.
Expected The admin user should be able to delete hotel content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 34
Description Test if the admin user can post new hotel information.
Input Click on the ‘post new hotel info’ link.
Expected The admin user should be able to post or add new hotel information.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 35
Description Test if the admin can add new hotel category.
Input Click on the ‘add new category’ link.
Expected The admin user should be able to add new hotel category.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 36
Description Test if the admin user can edit and delete hotel category.
Input Click on ‘edit category’ link.
Expected The admin user should be able to edit and delete hotel category.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 37
Description Test if the admin user can add new item in the hotel category.
Input Click on the ‘add new item’ link.
Expected The admin user should be able to add new item in the hotel category.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 38
Description Test if the admin user can view the edit section of the hotel category.
Input Click on the ‘edit item’ link.
Expected The admin user should be able to view the edit section of the hotel
Result category.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 39
Description Test if the admin user can edit hotel content.
Input Click on the ‘edit’ icon.
Expected The admin user should be able to edit hotel content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 40
Description Test if the admin user can delete hotel content.
Input Click on the ‘delete’ icon.
Expected The admin user should be able to delete hotel content.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
END USER/CUSTOMER
SN 41
Description Test if the user can view the ‘home’ page of the company.
Input Click on the ‘Home’ link.
Expected The system should display the home page of the company.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 42
Description Test if the user can view the company profile.
Input Click on the ‘company profile’ link.
Expected The system should display the company profile.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 43
Description Test if the user can view contact us page.
Input Click on the ‘contact us’ link.
Expected The system should display the contact us page.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 44
Description Test if the user can view the list of available tour packages.
Input Click on the ‘tour package’ link.
Expected The system should display the list of available tour packages.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 45
Description Test if the user can view general detail section of the selected tour
package.
Input Click on the ‘general detail’ icon.
Expected The user should be able to view general detail section of the selected tour
Result package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 46
Description Test if the user can view the gallery section of selected tour package.
Input Click on the ‘gallery’ icon.
Expected The user should be able to view gallery section of selected tour package.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 47
Description Test if the user can view itinerary section of selected tour package.
Input Click on the ‘itinerary’ link.
Expected The user should be able to view itinerary section of selected tour package.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 48
Description Test if the user can view the tour package booking section..
Input Click on the ‘booking’ link.
Expected The user should be able to view the tour package booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 49
Description Test if the user can view the list of available safari.
Input Click on the ‘Nepal safari’ link.
Expected The system should display the list of available safari.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 50
Description Test if the user can view general detail section of the selected safari.
Input Click on the ‘general detail’ icon.
Expected The user should be able to view general detail section of the selected
Result safari.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 51
Description Test if the user can view the gallery section of selected safari.
Input Click on the ‘gallery’ icon.
Expected The user should be able to view gallery section of selected safari.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 52
Description Test if the user can view itinerary section of selected safari.
Input Click on the ‘itinerary’ link.
Expected The user should be able to view itinerary section of selected safari.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 53
Description Test if the user can view the safari booking section..
Input Click on the ‘booking’ link.
Expected The user should be able to view the safari booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 54
Description Test if the user can view the list of available rafting packages.
Input Click on the ‘Nepal rafting’ link.
Expected The system should display the list of available rafting packages.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 55
Description Test if the user can view general detail section of the selected rafting
package.
Input Click on the ‘general detail’ icon.
Expected The user should be able to view general detail section of the selected
Result rafting package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 56
Description Test if the user can view the gallery section of selected rafting package.
Input Click on the ‘gallery’ icon.
Expected The user should be able to view gallery section of selected rafting
Result package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 57
Description Test if the user can view itinerary section of selected rafting package.
Input Click on the ‘itinerary’ link.
Expected The user should be able to view itinerary section of selected rafting
Result package.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 58
Description Test if the can view the rafting package booking section..
Input Click on the ‘booking’ link.
Expected The user should be able to view the rafting package booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 59
Description Test if the user can view the list of available lodge.
Input Click on the ‘lodge’ link.
Expected The system should display the list of available lodge.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 60
Description Test if the user can view general detail section of the selected lodge.
Input Click on the ‘general detail’ icon.
Expected The user should be able to view general detail section of the selected
Result lodge.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 61
Description Test if the user can view the gallery section of selected lodge.
Input Click on the ‘gallery’ icon.
Expected The user should be able to view gallery section of selected lodge.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 62
Description Test if the user can view itinerary section of selected lodge.
Input Click on the ‘itinerary’ link.
Expected The user should be able to view itinerary section of selected lodge.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 63
Description Test if the user can view the lodge booking section..
Input Click on the ‘booking’ link.
Expected The admin user should be able to view the lodge booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 64
Description Test if the user can view the list of available hotel.
Input Click on the ‘hotel’ link.
Expected The system should display the list of available lodge.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 65
Description Test if the user can view general detail section of the selected hotel.
Input Click on the ‘general detail’ icon.
Expected The user should be able to view general detail section of the selected hotel.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 66
Description Test if the user can view the gallery section of selected hotel.
Input Click on the ‘gallery’ icon.
Expected The user should be able to view gallery section of selected hotel.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 67
Description Test if the user can view itinerary section of selected hotel.
Input Click on the ‘itinerary’ link.
Expected The user should be able to view itinerary section of selected hotel.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 68
Description Test if the user can view the hotel booking section..
Input Click on the ‘booking’ link.
Expected The admin user should be able to view the hotel booking section.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 69
Description Test if the user can view the selected news.
Input Click on the desired news title link.
Expected The system should display the details of selected news.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 70
Description Test if the user can view the details clicking on the home page image.
Input Click on the image.
Expected The system should display the details about the image.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 71
Description Test if the user can download the files and images provided by the system.
Input Click on the ‘download forms’ link.
Expected The system should display the file list.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 72
Description Test if the user can open/save the selected file.
Input Click on the selected file link.
Expected The system should display open/save panel and give the access to user to
Result download the selected file.
Actual Result Actual result was as expected.
Conclusion Test case was successful.
FORM VALIDATION
SN 73
Description Test if the validation of form works properly or not.
Input Field to be filled is left empty.
Expected The system should display an error message.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 74
Description Test if the field filled more than its limitation is acceptable or not.
Input Fill the field with characters/numbers more than its specified limitation.
Expected The system should not accept such entry and display an error message.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.
SN 75
Description Test if the email entered is in the correct format.
Input Fill the field with incorrect email address format.
Expected The system should not accept such entry and display an error message.
Result
Actual Result Actual result was as expected.
Conclusion Test case was successful.