Mini project report
On
TOURISM MANAGEMENT
In the partial fulfillment of 4th semester of MCABY
SUJEESH T.K
DEPARTMENT OF COMPUTER APPLICATIONS COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY KOCHI-22DECLARATION
I hereby declare that the work being presented in the project report “TOURISM MANAGEMENT” in partial fulfillment of the requirement of the degree of Master of Computer Application is Authentic record of my own work carried out at College and not submitted anywhere else for any degree or diploma. This to certify that above information is correct to the best of my Knowledge.
SUJEESH T.K
ACKNOWLEDGEMENT
This Project itself is an acknowledgement to the inspiration, drive and technical assistance contributed by many individuals. This project would have never seen the light of this day without the help and guidance I have received. I express my gratitude to Dr. K.V. Pramod, Head, Department of Computer Applications, Cochin University of Science And Technology, Cochin, Kerala for providing me with excellent infrastructure and awesome environment that laid potentially strong foundation for my professional life. I also express my deep gratitude to my bellowed teachers Mrs. Malathi S, Dr.B.kannan for the keen interest, timely suggestions and help for completing of this mini project. I extend my sincere thanks all non-teaching staffs for providing the necessary facilities. I extend my heartfelt thanks to my parents, friends and well wishers for their support and timely help.
SUJEESH T.K
CONTENTS
TITLE PAGE NO.1. INTRODUCTION 6
OBJECTIVE
2. SYNOPSIS 7
3. SYSTEM ANALYSIS 8-10
3.1 PURPOSE
3.2 PROBLEM DEFINITION
3.3 FEASIBILITY
3.3.1 TECHNICAL FEASIBILITY
3.3.2 ECONOMIC FEASIBILITY
3.3.3 OPERATIONAL FEASIBILITY
3.4 OVERVIEW
4. SYSTEM REQUIREMENTS SPECIFICATION 11-14
4.1 PURPOSE, SCOPE AND OVERVIEW
4.2 GENERAL DESCRIPTION
4.2.1 PRODUCT PERSPECTIVE
4.2.2 PRODUCT FUNCTIONS
4.2.3 USER CHARACTERISTICS
4.2.4 GENERAL CONSTRAINTS
4.3. FUNCTIONAL REQUIREMENTS
4.4. USER INTERFACE REQUIREMENTS
4.5. PERFORMANCE REQUIRMENTS
4.6. NON FUNCTIONAL REQUIREMENTS
5. SQA PLAN 15 - 21
5.1 PURPOSE
5.2 SQA TASKS
5.3 STANDARDS, PRACTICES, CONVENTIONS, METRICS
5.4 TEST
5.5 TOOLS, TECHNIQUES AND METHODOLOGIES
5.6 APPENDIX
6. SYSTEM ENVIRONMENT 22 - 24
HARDWARE SOFTWARE OPERATING SYSTEM INFO ABOUT THE LANGUAGE
7. SYSTEM DESIGN 25 - 32
INPUT DESIGN
OUTPUT DESIGN
DATABASE DESIGN
ARCHITECTURAL DESIGN- DATA FLOW DIAGRAM
8. SYSTEM IMPLEMENTAION 33
9. SOFTWARE DESIGN 34 - 36
TEST PLAN
TEST CASES
10. CONCLUSION 36
11. SCREEN SHOTS 37 - 48
12. BIBLIOGRAPHY 49
INTRODUCTION
The web site which deals with the reservation of hotels in 5 major torist places of kerala is known as tour de kerala .This site helps the people in the world to reserve the hotels in advance before they reach the place through internet.Even a person with less computer knowledge can easily reserve the hotels.The only knoledge required is ability to read English. Every people loves nature and art.They visit famous places during holidays and spent some days and enjoys.But due to lack of authentic information people cannot be able to reach the correct place.So I tried to give the maximum information about the places through site. This site makes the resevation problem simple.Because from this site people can easily understand whether rooms are available ia a paricular hotel.This site also provides information about the festivals,temples,wild life,ayurvedic treatments of Kerala.
OBJECTIVE
The main objective of this software are to manage the hotels more efficiently and defectively and to avoid any difficulties that may be faced in the normal system. The primary objective is to: • Increase the efficiency • To store information about user, reserved the hotels,permenantly. • To store information about available rooms. • Reduce paper works and storage requirements • Better and error free output, time saving SYNOPSIS The project entitled “Tourism Management” was started as an endeavor to bring up a portal that would give information about some famous tourist places of Kerala. It includes online hotel booking, information about various information about festivals,temples,beaches etc of Kerala . In order to minimize the manual labor work, it is sufficient to make the inventory system computerized. It will help the laborer to do the reservation process smoothly and will produce error free output.
LIMITATIONS OF A MANUALLY KEPT SYSTEM:- • Details of reservatinos are kept in books. • Error may occur in calculations of the reservation of rooms . • Poor customer service. • Large number of records is needed. • Searching of the records is difficult and consumes a lot of time.
PROPOSED SYSTEM:- The proposed system computerizes the following procedures. • Hotel reservation • Give information about Kerala. This new system is user friendly and more effective. Here instead of using manual records, data are kept in databases, which help in easy retrieval, updation and deletion of data. The system also supports password protection, which denies any unauthorized access and distribution of data stored in databases. The user can update the reservation status as he wish. He can also view the room numbers allotted to him. If the hotel can not allott a room to the user, the program displays a message showing that rooms are not available. The administrator do the registration of hotels in to the site.He have the right to cancel the reservation of a user if he is not valid
3.SYSTEM ANALYSIS System analysis or study is an important phase of any system development process. The system is studied to the minute detail and analyzed. The system analyst dwelled deep into the working of the present system. The system was viewed as a whole and the input of the system are identified. During analysis phase for each problem identified many alternative solutions were evaluated and selected the most feasible one. A feasibility analysis was performed to evaluate possible solutions to recommend the most feasible one. 3.1 Purpose The web site entitled “tour de kerala” is developed to automate the management of files and infrastructure in a no. of hotels. This provides ease of use and better control to the user. The new proposed features are speed in processing, accuracy in calculation and reduce manual work
3.2 Problem Definition :-To develop a software solution to a problem, the first step is to understand the problem. The problem here is to maintain an up to date details of the available rooms and to keep a neat record of the customers who reserved rooms. The proposed system must provide the following functions. Room reservation Room cancelation Requirements specify the capability that the system must provide in order to solve the problem. It can be software, hardware and user interface. The requirement here is that the package should provide functionalities like Speed Accuracy Backup Security User friendly 3.3 FEASIBILITY After the problem is clearly understood and solutions proposed, the next step is to conduct the feasibility study. Feasibility study is defined as evaluation or analysis of the potential impact of a proposed project or program. The objective is to determine whether the proposed system is feasible. There are three aspects of feasibility study to which the proposed system is subjected as discussed below.
3.3.1. Technical Feasibility Technical feasibility assesses whether the current technical resources are sufficient for the new system. If they are not available, can they be upgraded to provide the level of technology necessary for the new system? It checks whether the proposed system can be implemented in the present system without supporting the existing hardware. 3.3.2. Economic Feasibility Economic feasibility determines whether the time and money are available to develop the system. It also includes the purchase of new equipment, hardware, and software. A software product must be cost effective in the development, on maintenance and in the use. Since the hardware and resources are already available with the organization and the organization can afford to allocate the required resources.
3.3.3. Operational Feasibility Operational feasibility determines if the human resources are available to operate the system once it has been installed. The resources that are required to implement or install are already available with the organization. The persons of the organization need no exposure to computer but have to be trained to use this particular software. A few of them will be trained. Further, training is very less. The management will also be convinced that the project is optimally feasible.
3.4 OVERVIEW
Thus the system is to provide the following advantages. Completely user friendly and menu driven High level of security Reduces repetitive manual work Provides backup Accuracy Time Saving Faster access Faster report production
4. SYSTEM REQUIREMENTS SPECIFICATION
4.1 Purpose, Scope and Overview The purpose of the project Tourism Management is to create web site named tour de kerala is to manage the overall functions of a hotel. The user can reserve the rooms in a hotel through this site and can also cancel the rooms if he don’t want . The system also prepares and records the rooms reserved and available for a particular period. We can consider each task as a different module thereby reducing human effort. A administrator of this software can have a detailed knowledge about all the working areas of the software. All the problems arise in the manual system are studied deeply, alternative solutions are considered and the most feasible solution is generated This document is the only one that describes the requirements of the system to be developed. The Software is helpful for both the administrator and the customers. This one is intended to provide facilities like computerized calculation of room availability, daily updating etc. The proposed system is equipped with a range of functions in almost all areas of a Hotel. All the areas of operations are examined in detail and the software can be considered as an optimal solution. Various analytical methods are applied to the initial investigation. The authorized administrator can do the main functions of the hotel. 4.2. General description
4.2.1 Product perspective: The administrator can check the current status of the available rooms. Also the system provides reservation details for a particular period by the user. 4.2.2 Product Functions: The general functionality of the project is to establish an easy way to search tourist places and book the hotels .The main modules of the proposed system are Admin and Users. The proposed system is helpful to the user to know about various facilities that provides various tourist places and he can choose the better place
4.2.3 User characteristics: The main users of this product are those who have the right to access this software. This ability is given through a user name and password. These users are sure to be literate with the computers.
4.2.4 General constraints:
1 Every action is monitored and controlled by the administrator. Therefore, any failure in the admin section will affect the entire working of the organization.
2 The system shall permit only authorized members who having the appropriate right to update, edit and delete the information
3 Users shall be required to log in for using the functionality
4.3. Functional requirements The various Functional requirements of the system can be summarized as follows:
1. Accession and updating of records of available rooms in the Hotel
2. Store reservation and sales details.
3. Control over the use of system by the administrator.
4. Calculation of the room availability and store the details.
4.4 User Interface Requirements:
The system should be designed in such a way that only authorized users should be allowed to access the particular modules. The records of room details should be accessed and used by only administrators and no one else. The user should always be in control of the application and not the vice versa. The user interface should be consistent so that the user can handle the application with ease and speed. The application should be visually, conceptually clear.
Administrator mode:
• Administrator’s login
• Hotel registration
• User requests
• User details
User mode:
• User Login
• New user Signup
• Reservation
• Reservation Cancel
• Queries
4.5. Performance Requirements:
The system must have following characters:
1. The system is developed keeping in mind both the customer and the administrator.
2. The administrators should be provided with a host of options to control the functioning of the system.
3. The entire process related tools has to be automated thus providing the user with an option of taking up of their choice as and when required
4.6. Other Non Functional Attributes
Nonfunctional requirements define system properties and constraints it arise through user needs, because of budget constraints or organizational policies, or due to the external factors such as safety regulations, privacy registration and so on. Nonfunctional requirements are:
1. Security
2. Reliability
3. Maintainability
4. Portability
5. Extensibility
6. Reusability
7. Resource Utilization
5. SQA PLAN
5.1 Purpose, Scope and Overview The purpose of this plan is to define the Software Quality Assurance (SQA) for “TOURISM MANAGEMENT” , SQA tasks and responsibilities; provide reference documents and guidelines to perform the SQA activities; provide the standards, practices and conventions used in carrying out SQA activities; and provide the tools, techniques, and methodologies to support SQA activities, and SQA reporting. This plan establishes the SQA activities performed throughout the life cycle of the “TOURISM MANAGEMENT”. The goal of the SQA program is to verify that all software and documentation to be delivered meet all technical requirements. The SQA procedures defined herein shall be used to examine all deliverable software and documentation to determine compliance with technical and performance requirements.
5.2 SQA Tasks Good software practice requires a measure of independence for the SQA group. This independence provides a key strength to SQA; that is, SQA has the freedom, if the quality of the product is being jeopardized, to report this possibility directly above the level of the project. While in practice this rarely occurs, for almost all problems are correctly addressed at the project level, the fact that the SQA group can go above the project level gives it the ability to keep many of these problems at the project level. Figure below shows the SQA organization with relation to the project organization. Figure: “TOURISM MANAGEMENT SYSTEM” Organization The following describes the functional groups that influence and control software quality. a. Program Management/Line Management (Sponsor) is responsible for the following items:
1. Identifying an individual or group independent from the project to audit and report on the project’s SQA function.
2. Identifying the quality factors to be implemented in the system and software.
b. Project Management is responsible for:
1. Resolving and following-up on any quality issues raised by SQA.
2. Identifying, developing and maintaining planning documents such as the Program Management Plan
. c. System Engineering is responsible for:
1. Implementing the engineering practices, processes, and procedures as defined in program/project planning documents.
d. Software Design/Development is responsible for:
1. Identifying, implementing, and evaluating the quality factors to be implemented in the software. e. Software Test is responsible for:
1. Verifying ,Implementing the software test practices, processes, and procedures as defined in program/project planning documents.
f. System Test is responsible for: 1. Verifying the quality factors are implemented in the system (software and hardware).
g. Logistics is responsible for:
1. Reviewing and commenting on the “TOURISM MANAGEMENT” SQA Plan.
2. Implementing the quality program in accordance with this SQA Plan. h. Software Configuration Management (SCM) is responsible for:
1. Implementing the SCM practices, processes, and procedures as defined in reference
(e) and other program/project planning documents.
i. Independent Verification and Validation (IV&V) is responsible for:
1. Implementing the practices, processes, and procedures as defined for IV&V in program/project planning documents.
j. Systems Engineering Process Office (SEPO) is responsible for:
1. Maintaining the SQA Process.
2. Ensuring SQA training availability.
3. Providing assistance in software process engineering and software process improvement. TASKS TO BE PERFORMED An SQA task is performed in relationship to what software development activities are taking place. One or more SQA tasks can be performed concurrently until a task is completed.
• Evaluate System Requirements Analysis Process
• Evaluate System Design Process
• Evaluate Software Requirements Analysis Process
• Evaluate Software Design Process
• Evaluate Software Tools
• Evaluate Software Implementation and Unit Testing Process
• Evaluate End-item delivery Process
• Evaluate Configuration Management Process
5.3 STANDARDS, PRACTICES, CONVENTIONS AND METRICS
To verify the delivery of a fully conforming, high-quality product, every individual assigned to the project will participate in quality assurance. This section describes the procedures used by SQA to verify that the quality assurance provisions of this SQA Plan and applicable standards, practices, conventions, and metrics are met. The following measurements will be made and used to determine the cost and schedule status of the SQA activities: SQA milestone dates (planned) a. SQA milestone dates (completed)
b. SQA work scheduled (planned)
c. SQA work completed (actual)
d. SQA effort expended (planned)
e. SQA effort expended (actual)
f. SQA funds expended (planned)
5.4 TEST TOURISM MANAGEMENT testing activity includes unit level testing, integration testing, performance testing (CI Qualification Testing), and acceptance testing (System Qualification Testing). Figure 5-1 provides the Test Process Flow. SQA shall audit and verify that the software and test documentation is subject to configuration management control. SQA shall witness the tests and verify that test results are recorded and evaluated. SQA shall coordinate the maintenance of Problem/Change Report (P/CR), sometimes called Software Trouble Report (STR), logs with SCM and shall verify that software changes are controlled according to reference (e). SQA shall witness regression testing resulting from P/CRs or STRs to verify the effectiveness of the correction.
5.5 TOOLS, TECHNIQUES, AND METHODOLOGIES
Tools - SQA software tools include, but are not limited to, operating system utilities, debugging aids, documentation aids, checklists, structuring preprocessors, file comparators, structure analyzers, code analyzers, standards auditors, simulators, execution analyzers, performance monitors, statistical analysis packages, software development folder/files, software traceability matrices, test drivers, test case generators, static or dynamic test tools, and information engineering CASE tools.
Techniques - techniques include review of the use of standards, software inspections, requirements tracing, requirements and design verification, reliability measurements and assessments, and rigorous or formal logic analysis.
Methodologies - methodologies are an integrated set of the above tools and techniques. The methodologies should be well documented for accomplishing the task or activity and provide a description of the process to be used. Where applicable, SQA will use SEPO organizational processes and tailor the processes specific to the project
CODE CONTROL Code control includes the items listed below:
a. Identifying, labeling, and cataloging the software to be controlled
b. Identifying the physical location of the software under control
c. Identifying the location, maintenance, and use of backup copies
d. Distributing copies of the code
e. Identifying the documentation that is affected by a change
f . Establishing a new version
g . Regulating user access to the code.
MEDIA CONTROL Media control includes adequate protection from unauthorized access.
SUPPLIER CONTROL Prior to any purchase of software to support the development effort, SQA and project members will define and provide complete requirements to the supplier/vendor. The Software Tool Evaluation Process will be followed. Part of the evaluation process will require the supplier or vendor to describe their technical support, handling of user questions and problems, and software product upgrades. All supplier software has been operationally tested in the target system. No future supplier software is planned.
RECORDS COLLECTION, MAINTENANCE AND RETENTION
SQA activities are documented by records and reports that provide a history of product quality throughout the software life cycle. Measurement data collected will be reviewed for trends and process improvement. All SQA records will be collected and maintained in the SDL or archival storage for the life cycle of the product.
5.6 Appendix
CMM Capability Maturity Model CI Configuration Item IEEE Institute of Electrical and Electronics Engineers IV&V Independent Verification and Validation P/CR Problem/Change Report SCM Software Configuration Management SDD Software Design Document SDF Software Development File SDP Software Development Plan SDR System Design Review SEI Software Engineering Institute SEPO Systems Engineering Process Office SQA Software Quality Assurance SRR System Requirements Review
6. SYSTEM ENVIRONMENT
The following hardware and software are required for the development and deployment of the system.
6.1 Hardware
CPU : Intel Pentium IV 600MHz
Memory : 128 MB RAM
Hard disk Space : 20 GB or higher
6.2 Software
Operating System : Windows XP
Development Tools
Front End : HTML, PHP
Back End : MySQL
6.2.1 Operating System Info
WINDOWS XP OPERATING SYSTEM
The operating system used was Microsoft Windows XP. The Windows XP provides a suitable environment for the smooth functioning of the project. Windows XP makes personal computing easy. Power, performance, a bright new look and plenty of help when you need it. Windows XP has it all, along with unmatched dependability and security. 6.2.2 ABOUT THE LANGUAGE
PHP LANGUAGE
PHP was written as a set of CGI binaries in the C programming language by the Danish/Greenlandic programmer Rasmus Lerdorf 1994, to replace a small set of perl scripts he had been using to maintain personal homepage. Lerdorf initially created PHP to display his resume and to collect certain data, such as how much traffic his page was receiving. Personal Home Page Tools was publicly released on 8 June 1995 after Lerdorf combined it with his own Form Interpreter to create PHP/FI PHP has a formal development manual that is maintained by the free software community. In addition, answers to many questions can often be found by doing a simple Internet search. PHP user assists each other through various media such as chat, forums, newsgroups and PHP developer web sites. In turn, the PHP development team actively participates in such communities, garnering assistance from them in their own development effort (PHP itself) and providing assistance to them as well. There are many help resources available for the novice PHP programmer. Basic Object oriented programming functionality was added in PHP 3. Handling of objects was completely rewritten for PHP 5, allowing for better performance and more features. In previous versions of PHP, objects were handled like primitive types. The drawback of this method was that the whole object was copied when a variable was assigned, or passed as a parameter to a method. In the new approach, objects are referenced by handle, and not by value. PHP 5 introduced private and protected member variables and methods, along with abstract classes and abstract methods. It also introduced a standard way of declaring constructors and destructors similar to that of other object-oriented languages, such as C++ and an exception-handling model similar to that of other programming languages.
JAVA SCRIPT & HTML JavaScript is an object based scripting language that offers cross platform operation across the span of the WWW. JavaScript provides a means of embedding interactive paths and intelligence within HTML documents. The object-based nature of JavaScript offers programmers significant power and flexibility through the ability to create functions and new objects. Performing certain processing functions at the client side – such as form validation and data retrieval from local data arrays-reduces the burden imposed on the server side and can provide a sense of greater responsiveness to a viewer an HTML document enhanced with JavaScript. As the term website development sounds unique language strikes is every one’s mind, which is nothing but hypertext Markup Language. This language specifies all the function in a single sentence, which is called as Tag. This language has Built-in Tags to specify the contents of the Web Pages. The main advantage of this language is easy to learn and use. It does not state out the errors. Browser based software takes less memory and executes at faster rate. All browser based software executes at client side and hence in faster execution. APACHE SERVER A Web server is the server software behind the World Wide Web. It listens for requests from a client, such as a browser like Netscape or Microsoft's Internet Explorer. When it gets one, it processes that request and returns some data. This data usually takes the form of a formatted page with text and graphics. The browser then renders this data to the best of its ability and presents it to the user. Web servers are in concept very simple programs. They wait for requests and fulfill them when received. Web servers communicate with browsers or other clients using the Hypertext Transfer Protocol (HTTP), which is a simple protocol that standardizes the way requests, are sent and processed. The Web server is responsible for fetching the information. While Web servers may have been simple at some point, they are not anymore. All Web servers are not created equal. MYSQL MySQL is a multithreaded, multi-user SQL database management system (DBMS) which has, according to Mysql AB, more than 10 million installations Mysql is owned and sponsored by a single for-profit firm, the Swedish company Mysql AB, which holds the copyright to most of the codebase. This is similar to the JBoss model and how the Free Software Foundation handles copyright in its projects, and dissimilar to how the Apache project does it, where the software is developed by a public community and the copyright to the codebase is owned by its individual authors. Libraries for accessing Mysql databases are available in all major programming languages with language-specific APIs. In addition, an ODBC interface called MyODBC allows additional programming languages that support the ODBC interface to communicate with a Mysql database, such as ASP or Coldfusion. The Mysql server and official libraries are mostly implemented in ANSI C. BROWSERS A Browser is a software program used to view HTML documents within the World Wide Web. The primary goal of a web browser is to send and receive data from the Web Server that provides the Web page. The server sends the web page in the HTML markup language and the browser interprets that HTML code, presenting the page to the user. Internet Explorer: - Internet is the Microsoft‘s contribution to the Web browser community. The Internet Explorer is based on Microsoft’s ActiveX technology and is available for Windows, Windows NT, and Macintosh platforms. One significant capability of the Internet Explorer is that support the embedded intrinsic and ActiveX controls within the Web pages, with which JavaScript can interact. 7. SYSTEM DESIGN System design is the second phase of the software life cycle. The system goes through logical and physical state of development. The user oriented performance specification is extended into a design specification, while designing the needed system. The principle activities during this phase are the design of database of input processing and output and definition of the system. The design phase begins when the Requirement Specification document for the software to be developed is available. 7.1 INPUT DESIGN Input design is the process of converting a user-oriented description of the inputs to a computer-based business system into a programmer-oriented specification. The input screens are designed in such a way that it recognizes any erroneous input. The data entry screens are designed in such a way that it is interactive in nature. Online error messages are also displayed. Pull down data windows are also attached in order to avoid erroneous data entry in case of predefined data input. Advanced GUI tools are used in order to reduce the time of data input and for better menu utilization. Checking of data is done before it is transferring for processing. Input screens must provide an effort-les working environment to the user. Features of Input Screen • Well defined messages through specially designed message boxes. • Pull down data window for entering pre-defined data. • Uncomplicated screen layout. • System error message boxes must be provided to control erroneous data. 7.2 OUTPUT DESIGN The output design is for designing the necessary outputs according to the requirements of various users. Output design must be done efficiently so that the processed information is conveyed to the user. The output screen is generated for viewing the details of each entered data. Output can be displayed on the monitor or it can be transferred to the printer. The validity of Output is an important factor. The results of calculations need to be evaluated before it is transferred to any output device. Any error found must be displayed message box. Objectives of Output Design • Design output to reveal the information accurately • Provide high quality output. • Proficiency to choose output device. • Provide up-to-date report • Output must be clear and unambiguous 7.3 DATABASE DESIGN Databases are the store houses of data used in the software systems. A database is a collection of stored data organized in such a way that the data requirements are satisfied by the database. The data is stored in tables inside a database. The general objective is to make the information access easy, quick, inexpensive and flexible for the user. There are also some specific objectives like redundancy elimination, privacy, security and performance. Several tables are created for manipulation of data for the system. A collection of relative records make up a table. To design and store data to the needed forms tables are prepared. Two essential settings for a database are • Primary key- The field that is unique for all the record occurrences. • Foreign key- The field used to set relation between tables
TABLE DESIGN
Administrator
Tables administrator For the login validation of administrator
7.4 ARCHITECTURAL DESIGN DATA FLOW DIAGRAMS A DFD describes what data flow (logical) rather than how they are processed, so it does not depend on hardware, software, data structure or file organization. It is also known as ‘bubble chart’. A data Flow Diagram is a structured analysis and design tool that can be used for flowcharting in place of, or in association with, information-oriented and process-oriented system flowcharts. A DFD is a network that describes the flow of data and the processes that change, or transform, data throughout a system. This network is constructed by using a set of symbols that do not imply a physical implementation. It has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design phase that functionally decomposes the requirement specifications down to the lowest level of detail. A DFD can be considered as an abstract of the logic of an information-oriented or a process-oriented system flow-chart. For these reasons DFDs are often referred to as logical flow diagrams. The four basic symbols used to construct data flow diagrams are shown below: A rectangle represents a data source or destination. A directed line represents the flows of data, which is data stream. An enclosed figure, usually a circle or an oval bubble, represents a process that transforms data streams. An open-ended rectangle represents data storage. These are symbols that represent data flows, data sources, data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes. The principle processes that take place at nodes are 1. Combining data streams 2. Splitting data streams 3. Modifying data streams Level - 0 Administrator Module Administrator User Module Database userlog Level1 Site Administrator section Administrator password adminname hotel_info userlog Hotel Administrator section Administrator password adminname reservation query userlog User section userlog password logname query reservation userlog 8.SYSTEM IMPLEMENTATION Implementation is the stage in the project where the theoretical design is turned into a working system and is giving confidence on the new system for the users that it will work efficiently and effectively. It involves careful planning, investigation of the current system and its constraints on implementation, design of methods to achieve the change over, an evaluation, of change over methods. Apart from planning major task of preparing the implementation are education and training of users. The more complex system being implemented, the more involved will be the system analysis and the design effort required just for implementation. The data that is required to run the system is stored in the appropriated databases and will be accessed using the database supporting languages whenever required. The data processing function should be able to respond more quickly and effectively to change information needs data quality accessibility and at the same time relevance should be given the utmost importance. Implementing a system consists of three primary activities of training, conversion and post implementation The implementation includes the following things. • Careful planning • Investigation of system and constraints. • Design the methods to achieve the charge over. • Training the staff in the changed phase. • Evaluation of change over method. The method of implementation and time scale to be adopted are found out initially. 9. SOFTWARE TESTING System testing provides the file assurance that software once validated must be combined with all other system elements. System testing verifies whether all elements have been combined properly and that overall system function and performance is achieved. Characteristics of a Good Test: • Tests are likely to catch bugs • No redundancy • Not too simple or too complex 9.1 TYPES OF TESTING 9.1.1 Unit Testing Unit testing focuses verification effort on the smallest unit of Software design that is the module. Unit testing exercises specific paths in a module’s control structure to ensure complete coverage and maximum error detection. This test focuses on each module individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing. 9.1.2 Integration Testing Integration testing addresses the issues associated with the dual problems of verification and program construction. After the software has been integrated a set of high order tests are conducted. The main objective in this testing process is to take unit tested modules and builds a program structure that has been dictated by design. 9.1.3 User Acceptance Testing User Acceptance of a system is the key factor for the success of any system. The system under consideration is tested for user acceptance by constantly in touch with the prospective system users at time of developing and making changes wherever required is done in regard to the following point: • Input Screen design • Output Screen design • Menu driven system 9.1.4 Validation Testing Entering incorrect values does the validation testing and it is checked whether the errors are being considered. Incorrect values are to be discarded. The errors are rectified 9.1.5 Output Testing After performing the validation testing the next step is output testing of the proposed system, since no system could be useful if it does not produce the required output in a specific format. Asking the users about the format required by them, testing the output generated are considered into two ways. One is onscreen and another is printed format. The output format on the screen was found to be correct as the format was designed in the system design phase according to the user needs. For the hard copy also, the output comes out as specified requirement by the user. Hence output testing does not result in any correction in the system 9.2 TEST CASES In system testing, test data should cover the possible values of each parameter based on the requirements. Since testing every value is impractical, a few values should be chosen from each equivalence class. An equivalence class is a set of values that should all be treated the same. Ideally, test cases that check error conditions are written separately from the functional test cases and should have steps to verify the error messages and logs. Realistically, if error test cases are not yet written, it is ok for testers to check for error conditions when performing normal functional test cases. It should be clear which test data, if any, is expected to trigger errors “TOURISM MANAGEMENT SYSTEM” has used so many such test cases, as shown below. Test Cases Input Output 1 Entering invalid username and password Message box – “Invalid username or password” 2 Entering a checkindate greater than check out date Message box - “checkour date should come after checkin date “ 3 Saving without filling all the mandatory fields Message box – “Enter the corresponding data” 4 4 Pressing buttons without selecting appropriate fields Message box – “Select an item code ” 10. CONCLUSION The tour de kerala Website has been implemented by considering all the possible problems present in the existing in reservation system. Unauthorized accessing of this website and the database are prevented with password security. And the user payment section is very secure part of the website. Limitations of the System • Only Demand Draft is used for payment. • Only static updating of website is possible. Further Enhancements • Payment through Smart cards can be implemented. • Dynamic updating can be implemented. 11. Screen shots HOME The home page consists of small information about kerala tourism.This page consists of 13 links.HOME,PROFILE, LOGIN/LOGOUT,TRAVEL GUIDE,WILD LIFE TOURISM,BEACHES,HILLSTATION TOURISM,AYURVEDA TOURISM AND the links to hotels in kerala. USER LOGIN This page is used for the user to login to the site using loginname and password. SIGN UP This page is used for the new customer who want to register in the site HOTEL BOOKING When we click on the links to the hotels of different districts in kerala a registration form will be displayed along with a list of the hotels present in that district.A customer can register his name through this page. PASSWORD CHANGE User can change his password using the old password.And he has to confirm his password by retyping it. EDIT PROFILE User can update his profile using this form. QUERY User can send their query through this form. ADMIN This page is used for the administrator to access the request send by the user.Administrator only can login to this part using his id and password USER DETAILS Site administrator will get the information of the user who have registered in this site HOTEL REGISTRATION Site administrator registers the hotels to this site through this form EDIT Hotel administrator can add the no.of rooms in their hotels. QUERY Hotel administrator can see the query entered by the customer. 11. BIBLIOGRAPHY BOOKS 1) The Complete Reference HTML : Kenny Chu 2) PHP Black Book : Peter Moulding 3) PHP Bible : Tim Converse 4) Php, Apache, MySQL Web development : Jason Gerner 5) Java Script : Arman Dhanesh WEBSITES 1. www.php.net 2. www.trvelguru.com 3. www.keralatourntravel.com
posted by SAMCA CUSAT @ 9:45 PM
0 Comments
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home