tours and travel management
DESCRIPTION
Tours and Travel ManagementTRANSCRIPT
TOURISM MANAGEMENT
CONTENTS1. PROJECT PROFILE
01-061.1 Project Profile
041.2 Project Preface
052. ABSTRACT
073. TOOLS AND TECHNOLOGY
08-183.1. Microsoft .NET Framework
3.2. Features Of Common Language Runtime
3.3. .Net Framework Class Library
3.4. ActiveX Data Objects .Net
3.5. Data Adapters
4. SRS
19-254.1. Requirements Specification
4.2. Functional Requirements
5. DATA FOLW
26-38 5.1. Data Flow Diagrams 6. UML DIAGRAM
39-447. E-R DIAGRAM
45-468. GANTT CHART
47-489. DATABASE DESIGN
49-539.1. Table Specification10. SCREEN SHOTS
54-6211. SYSTEM TESTING
63-6611.1. Unit Testing11.2. System Testing12. CONCLUSION
67-6813. BIBLIOGRAPHY
69-70LIST OF FIGURESFigure 1 :Home PageFigure 2:Registration Page
Figure 3:Login Page
Figure 4:Admin Home Page
Figure 5:Place Management Page
Figure 6:Hotel Management Page
Figure 7:Vehicle Management Page
Figure 8:View Feedback Page
Figure 9:User Home Page
Figure 10:View Places
Figure- 11:View Hotels
Figure 12:Give Feedback
Figure 13:Book Page
Project Preface:
Project Title: Odisha Tours and Travels Management.
Project Description: Odisha Tours and Travels Management is a web based project which describes about an organization whose work is to give information/services to those who wants to know about Odisha and its culture. By visiting this site one can know the place of Odisha and their specialty.
Basically, this project is having 2 modules.
1. Admin: Admin is the solo authority of this project and plays a vital role. Its work is to add information about Odisha. All the details which user will be able to see has to be kept by the Admin.
2. User: User is another important module of this project. It is that module where all the registered/layman user can take advantage. Layman user/unregistered user can only see about Odisha nothing else. In order to see the place details and hotel details one has to be registered here and in order to do that he/she can fill up a form and after the successful registration an Username/Password will be provided to him/her. This Username/Password will be helpful to entry to the modules.
The basic functionalities of the user are:
I. View Places:- Can view all the places.
II. View Hotels:- Can view all the hotels in a particulars place.
III. Give feedback:-Can give feedback to the Admin in order to comment/complement and can also give suggestion to make the functionalities better.
IV. Book Vehicle:- can book any no. of vehicles as per his/her need.
V. Change Password: Can change his/her old password.
This project can have extra features but as because this is our minor project, so we have limited it up to this. In our final submission we will extend this like,
Solution for Forget Password
View and Edit Profile
Something more about Vehicle management
Apply for deletion of profile
Validation of all the fields.
SYSTEM CONIFIGURATION
The hardware and software should be chosen carefully keeping following point in mind-
The System must be user friendly.
The System must be able to handle large number of data.
Processing speed of the system must be fast.
Hardware specification:
Processor :Core2 Duo
Speed :2.2 GHz
RAM :512MB GB
Hard Disk :160 GB
Key Board(104 keys) :Standard
Software Specification:
Operating system
: Windows XP
Programming specification
: J2EE
Framework/Open Source
: Struts 1.2
Integrated Development
Environment
: My Eclipse 6.1/ My Eclipse 5.5
Web Server
: Tomcat 6.0
Back End(Database)
: Oracle 10g
Tools : JSP, Servlet, HTML, ,CSS
Java Software
:JDK 1.6.0
Supporting Browsers:
Internet Explorer (7), Mozilla Firefox, Opera.
ABSTRACT
Now in the changing environment everybody wants speed and perfection, which cannot be possible without a computerization system, this is the age of information and technology. This computerization is going to change the traditional face of all the business organization and non-business organization. Most of the organization now uses computer system; we have also determined to computerize the Tours & Travel Management.
About The Tours & Travel Management
Tours & Travel Management is an Online Application which is used to store all the datas related to travel agency & all the information regarding the details of all the vehicles. Tours & Travel Management System, also offers Online Booking of Tickets to its Customers such as Car,Bus& Flight Booking. In this System, all the details & updates about the vehicle is maintained by the Administrator of the Software which can be viewed by the Customers while Booking a Vehicle.
A Customer has to be registered for booking a vehicle under this management. Its Provides a lots of Facilities to the Customers & a Customer Can book a vehicle at any instant & any time globally. Hence, the management wants to use a computerized system that will take care of Tours & Travel Management and provide information that can be used later to take strategic decisions. This system should be globally accessible and should be able to integrate with other system in the organization. In addition, all the data stored in this system should be secured.
WHY JAVA IS USED?
JAVAThe initial release of Java was nothing of revolutionary, but it did not mark the end of javas era of rapid innovation. Unlike most other software systems that usually settle into a pattern of small, increment improvements, java had already created java1.1 were more significant and substantial than the increase 1 the minor revision number would have you think. Java1.1 added many new library elements, redefined the way events are handled by applets, and reconfigured many features of the 1.0 library .It also deprecated several features originally defined by java1.0. Thus java1.1 both added and subtracted attributes from its original specification. Continuing in this evolution, java2 also and subtracts features.
Features added by 1.1
Version1.1 added some important elements to Java. Most of the addition occurred in the Java library. However, a few new language features were also included. Here is a list of the important features added by 1.1:
Java Beans, which are software components that are written in Java.
Serialization, which allows you to save and restore the state of an object.
Remote Method Invocation, which allows a Java, objects to invoke the methods of another Java object that located on a different machine. This is an important facility for building distributed applications.
Java Database Connectivity (JDBC), which allows programs to access SQL, databases from many different vendors.
The Java Native Interface (JNI), which provides a new way for your programs to interface with code libraries written in other languages.
Reflection, which is a process of determining the fields, constructors and methods of a java object at run time.
Various security features, such as digital signatures, messages digests, and access control lists and key generation.
Built in support for 16-bit character streams that handle Unicode characters.
Significant changes to event handling that improve the way in which events generated by graphical user interface (GUI) components are handled.
Inner classes, which allow one class to be defined within another.
Deprecated by Features 1.1As just mentioned java 1.1 depreciated many earlier library elements. For example, most of the original Date class was deprecated. However, the deprecated features did not go away. Instead, they were replaced with updated alternatives. In general, deprecated 1.0 feature is still available in java to support legacy code, but they should not be used by new applications.
Features added by java 2.0
Building upon 1.1, java 2.0 adds many important new features. Here is a partial list.
Swing is a set of user interface components that is implemented entirely in java You can use a look and feel that is either specific to a particular operating system or uniform across operating systems. You can also design your own look and feel.
Collections are group of objects. Java 2.0 provides several types of collection, such as linked lists, dynamic arrays and hash tables for use. Collections offer a new way to solve several common-programming problems.
Digital certificates provide mechanism to establish the identity of a user. You may think of them as electronic passports. Java programs can parse and use certificates to enforce security policies.
Text components can now receive Japanese, Chinese and Korean characters from keyboard. Using a sequence of keystrokes to represent one character does this.
The Common Object request Broker Architecture (CORBA) defines an Object request Broker (ORB) and an Interface Definition Language (IDL). Java 2.0 includes an ORB and an IDL to java compiler. The latter generates code from an IDL specification.
Performance improvements have been made in several areas. A Just-In-Time (JIT) compiler is included in JDK.
Many browsers include a Java Virtual Machine that is used to execute applets. Unfortunately, browsers JVMs typically do not include the latest java features. The java Plug-in solves this problem. It directs a browsers JVM .The JRE is a subset of the JDK. It does not include the tools and classes that are used in a development environment.
Various tools such as Javac, Java and Javadoc have been enhanced. Debugger and Profiler interfaces for the JVM arte available.
Features Deprecated by 2
Although not as extensive as the deprecations experienced between 1.0 and 1.1 some features of java 1.1 are deprecated by java 2.0. For example, the suspend (), resume () and stop () methods of the Thread class should not be used in new code.Javas Magic: The Byte Code:
The key that allows java to solve both the security and the portability problems just described is that the output of the java compiler is not an executable code. Rather, it is Byte Code. Byte Code is a highly optimized set of instructions designed to be executed by virtual machine that the java Run-time system emulates. This may come as it of surprise as you know c++ is compiled, not interpreted-mostly because of performance concerns. However, the fact that a java program is interpreted helps solve the major problems associated with downloading the program over the Internet.Here is why java was designed to be interpreted language. Because java programs are interpreted rather than compiled .It is easier to run them in wide variety of environments. Only the java runtime system needs to be implemented for each platform. Once the runtime package exists for a given system any java program can run on it. If java were a compiled langu8age then different versions of the same program will have to exist for each type of CPU connected to the Internet. Thus interpretation is the easiest way to create truly portable programs.Although java was designed to be interpreted, there is technically nothing about java that prevents on the fly compilation of Byte Code into native code. However, even if dynamic compilation were applied to Byte Code, the portability and safety would still apply, because the run time system would still be in change of the execution environment.
The Java Buzz Words
No discussion of the genesis of java is complete without a look at the java buzzwords. Although the fundamentals that necessitated the invention of java are portability and security, there are other factors that played an important role on molding the final form of the language. The java in the following list of buzzwords summed up the key considerations.
Simple
Portable
Object-oriented
Robust
Multithreaded
Architectural-neutral
High performance
Distributed
Dynamic
OBJECT ORIENTED PROGRAMMING AND JAVA
Object-oriented Programming was developed because of limitations found in earlier approaches of programming. To appreciate what OOP does, we need to understand what these limitations are and how they arose from traditional programming.
PROCEDURAL LANGUAGES
Pascal, C, Basic, FORTRAN, and similar languages are procedural languages. That is, each statement in the language tells the computer to do something: Get some input, add these numbers, divide by 6, and display the output. A program in a procedural language is a list of instructions. For very small programs no other organizing principle (often called a paradigm) is needed. The programmer creates the list of instructions, and the computer carries them out.
Division into Functions
When programs become larger, a single list of instructions becomes unwieldy. Few programmers can comprehend a program of more than a few hundred statements unless it is broken down into smaller units. For this reason the function was adopted as a way to make programs more comprehensible to their human creators. (The term functions are used in C++ and C. In other languages the same concept may be referred to as a subroutine, a subprogram, or a procedure.) A program is divided into functions, and (ideally, at least) each function has a clearly defined purpose and a clearly defined interface to the other functions in the program. The idea of breaking a program into functions can be further extended by grouping a number of functions together into a larger entity called a module, but the principle is similar: grouping a number of components that carry out specific tasks.
Dividing a program into functions and modules is one of the cornerstones of structured programming, the somewhat loosely defined discipline that has influenced programming organization for more than a decade.Problems with Structured Programming
As programs grow ever larger and more complex, even the structured programming approach begins to show signs of strain. You may have heard about, or been involved in, horror stories of program development. The project is too complex, the schedule slips, more programmers are added, complexity increases, costs skyrocket, the schedule slips further, and disaster ensues. Analyzing the reasons for these failures reveals that there are weaknesses in the procedural paradigm itself. No matter how well the structured programming approach is implemented, large programs become excessively complex. What are the reasons for this failure of procedural languages? One of
Relationship to the Real World
Procedural programs are often difficult to design. The problem is that their chief components--functions and data structures--don't model the real world very well. For example, suppose you are writing a program to create the elements of a graphics user interface: menus, windows, and so on. Quick now, what functions will you need? What data structures? The answers are not obvious, to say the least. It would be better if windows and menus corresponded more closely to actual program elements.
New Data Types
There are other problems with traditional languages. One is the difficulty of creating new data types. Computer languages typically have several built-in data types: integers, floating-point numbers, characters, and so on. What if you want to invent your own data type? Perhaps you want to work with complex numbers, or two-dimensional coordinates, or datesquantities the built-in data types dont handle easily. Being able to create your own types is called extensibility; you can extend the capabilities of the language. Traditional languages are not usually extensible. Without unnatural convolutions, you cant bundle together both X and Y coordinates into a single variable called Point, and then add and subtract values of this type. The result is that traditional programs are more complex to write and maintain.
The object oriented approachThe fundamental idea behind object-oriented languages is to combine into a single unit both data and the functions that operate on that data. Such a unit is called an object. An objects functions, called member methods in Java, typically provide the only way to access its data. If you want to read the item and return the value to you, you call a member function in the object. It will read the item and return the value to you. You cant access the data directly. The data is hidden, so it is safe from accidental modification. Data and its functions are said to be encapsulated into a single entity. Data encapsulation and data hiding are key terms in the description of object oriented languages. If you want to modify the data in an object, you know exactly what functions interact with it: the member functions in the object. No other functions can access the data. This simplifies writing, debugging, and maintaining the program.A Java program typically consists of a number of objects, which communicate with each other by calling one anothers members functions. We should mention that what are called member functions in C++ are called methods in Java. Also, data items are referred to as instance variables. Calling an objects member function is referred to as sending a message to the object. An analogy
You might want to think of objects as departmentssuch as sales, accounting, personnel, and so onin a company. Departments provide an important approach to corporate organization. In most companies (except very small ones), people dont work on personnel problems one day, the payroll the next, and then go out in the field as sales people the week after. Each department has its own personnel, with clearly assigned duties. It also has its own data: payroll, sales figures, personnel records, inventory, or whatever, depending on the department. The people in each department control and operate on those departments data. Dividing the company into departments makes its easier to comprehend and control the companys activities, and helps them maintain the integrity of the information used by the company. The payroll department, for instance, is responsible for the payroll data. If you are from the sales department, and you need to know the total of all the salaries paid in the southern region in July, you dont just walk into the payroll department and start rummaging through file cabinets. You send a memo to the appropriate person in the department, and then you wait for that person to access the appropriate person in the department, and then you wait for that person to access the data and send you a reply with the information you want. This ensures that the data is accessed accurately and that inept outsiders do not corrupt it. (This view of corporate organization is show in figure). In the same way, objects provide an approach to program organization, while helping to maintain the integrity of the programs data.
OOP: An approach to organization
Keep in mind that object-oriented programming is not primarily concerned with the details of program operation. Instead, it deals with the overall organization of the program. Characteristics of object-oriented languages:
Lets briefly examine a few of the major elements of object-oriented languages in general and Java in particular. Objects
When you approach a programming problem in an object oriented language, you no longer ask how the problem will be divided into functions, but how it will be divided into objects. Thinking in terms of objects, rather than functions, has a surprisingly helpful effect on how easily programs can be designed and objects in the real world.
STRUTS
Struts is an open source framework used for developing J2EE web applications using Model View Controller (MVC) design pattern. It uses and extends the Java Servlet API to encourage developers toadopt MVC architecture. Struts framework provides three key components:
1. A request handler provided by the application developer that is used tomap to a particular URI.
2. A response handler, which is used to transfer the control to another resource, which will be responsible for completing the response.
3. A tag library, which helps developers to create the interactive form, based applications with server pages.
Struts provides the basic infrastructure for implementing MVC allowing the developers to concentrate on the business logic.
Architecture of Struts:
Process flow:
Web.xml : Whenever the container gets start up the first work it does is to check the web.xml file and determine what struts action Servlets exist. The container is responsible for mapping all the file request to the correct action Servlet.A Request : This is the second step performed by the container after checking the web.xml file. In this the user submits a form within a browser and the request is intercepted by the controller.
The Controller : This is the heart of the container. Most Struts application will have only one controller that is ActionServlet which is responsible for directing several Actions. The controller determines what action is required and sends the information to be processed by an action Bean. The key advantage of having a controller is its ability to control the flow of logic through the highly controlled, centralized points.
Struts-config.xml : Struts has a configuration file to store mappings of actions. By using this file there is no need to hard code the module which will be called within a component. The one more responsibility of the controller is to check the struts.config.xml file to determine which module to be called upon an action request. Struts only reads the struts.config.xml file upon start up.
Model: The model is basically a business logic part, which takes the response from the user and stores the result for the duration of the process. This is a great place to perform the preprocessing of the data received from request. It is possible to reuse the same model for many page requests. Struts provide the ActionForm and the Action classes, which can be extended to create the model objects.
View: The view in struts framework is mainly a jsp page, which is responsible for producing the output to the user. Through the view Layer the user will interact with the System.
Struts tag libraries: These are struts components helps us to integrate the struts framework within the project's logic. These struts tag libraries are used within the JSP page. This means that the controller and the model part can't make use of the tag library but instead use the struts class library for strut process control.
Property file: It is used to store the messages that an object or page can use. Properties files can be used to store the titles and other string data. We can create many property files to handle different languages. Business objects: It is the place where the rules of the actual project exist. These are the modules that just regulate the day- to- day site activities.
The Response: This is the output of the View JSP object.
ORACLE 10g
In every S/W, database plays a vital role for storing the datas because everybody knows that without database an S/W is incomplete too. So it is bound to be used a database in every steps in making a S/W. In our project i.e. Human Resource Management System (HRMS) the Database that is used is Oracle10g.
Every record in the table has to be uniquely identified because in a relation all records are unordered which means that they cannot be identified with record number or position within the table.
There are some database terminologies are used they are as follows:
( Tables
( Records
( Fields
( Primary key
( Foreign key
( Master table
Description:--
Table: - A database contains data, which are stored and arranged in tables. Tables are known as relations. Here datas are arranged in row wise or column wise.
Records:- A table contains data arranged in rows every row is a separate record.
Fields: - The data in every row or record consists of several columns. These columns are called fields(while designing the database fields are reffered as properties or attributes).
Primary key:- This is the field which contains the data that will uniquely defines each record.the primary key values canot be repeated across the table.they canot be the blank.
Foreign key:- This is the field which contains the data that exists in the primary key field of the master table.any value inside the foreign key field must be taken from the corresponding primary key.
REQUIREMENT SPECIFICATION:
The software, which is designed for give the better services for the college administration and the user. The college administration need all the information regarding alumni registration, profile entry by admin,upload any type of photo of college in photogalary,facility to know the request contacts ,need all the CMS base facilities.Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC)
As it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
Developers Responsibilities Overview:
The developer is responsible for:
1) Developing the system, which meets the SRS and solving all the requirements of the system?
2) Demonstrating the system and installing the system at client's location after the acceptance testing is successful.
3) Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
4) Conducting any user training that might be needed for using the system.
5) Maintaining the system for a period of one year after installation.Functional Requirements:OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the users, students. The various types of outputs in general are:
. External Outputs, whose destination is outside the organization
. Internal Outputs whose destination is with in organization and they are the
Users main interface with the computer.
. Operational outputs whose use is purely with in the computer department.
. Interface outputs, which involve the user in communicating directly with Administrator.
Output Definition
The outputs should be defined in terms of the following points:
. Type of the output
. Content of the output
. Format of the output
.Location of the output
.Frequency of the output
.Volume of the output
.Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.
For Example
Will valid email address need to be inserted?
Output Media:
In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:
a. The suitability for the device to the particular application.
b. The need for a hard copy.
c. .The response time required.
d. The location of the users.
e. The software and hardware available &The cost.
Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:
The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.
INPUT DESIGN
Input design is a part of overall system design. The main objectives during the input design are as given below:
To produce a cost-effective method of input.
To achieve the highest possible level of accuracy.
To ensure that the input is acceptable and understood by the user.
INPUT STAGES:
The main input stages can be listed as below:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT TYPES
It is necessary to determine the various types of inputs. Inputs can be categorized as follows:
External inputs, which are prime inputs for the system.
Internal inputs, which are user communications with the system.
Operational, which are computer departments communications to the system?
Interactive, which are inputs entered during a dialogue.
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to;
Type of input
Flexibility of format
Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
PortabilityERROR AVOIDANCE
At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled.Occur, these types of errors can be discovered by using validations to check the input data.
DATA VALIDATION
Procedures are designed to detect errors in data at a lower level of detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data. Whenever an invalid data is keyed in, the system immediately provide a reports in the user sections and the user has to again key in the data and the system will accept the data only if the data is correct. Validations have been included where necessary.
The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user. The system has been designed with popup menus.
USERINTERGFACE DESIGN
It is essential to consult the system users and discuss their needs while designing the user interface:
USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:
1. User initiated interface the user is in charge, controlling the progress of the user/computer dialogue. In the computer-initiated interface, the computer selects the next stage in the interaction.
2. Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the user/computer dialogue. Information is displayed and the user response of the computer takes action or displays further information.
USER_INITIATED INTERGFACES
User initiated interfaces fall into two approximate classes:
Command driven interfaces: In this type of interface the user inputs commands or queries which are interpreted by the computer.
Forms oriented interface: The user calls up an image of the form to his/her screen and fills in theform. The forms oriented interface is chosen because it is the best choice.COMPUTER-INITIATED INTERFACESRight from the start the system is going to be menu driven, the opening menu displays the available options. Choosing one option gives another popup menu with more options. In this way every option leads the users to data entry form where the user can key in the data.
ERROR MESSAGE DESIGN:
The design of error messages is an important part of the user interface design. As user is bound to commit some errors or other while designing a system the system should be designed to be helpful by providing the user with information regarding the error he/she has committed.
This application must be able to produce output at different modules for different inputs.
Performance Requirements:
Performance is measured in terms of reports generated weekly and monthly.
Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system
The system should be accurate
The system should be better than the existing system
The existing system is completely dependent on the staff to perform all the duties.
DATA FLOW DIAGRAM:
A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFDs is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD.
The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design.
A DFD is also known as a bubble Chart 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 to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.
DFD SYMBOLS:
In the DFD, there are four symbols
1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data
NOTATIONS:
Data-Flows show the movement of data in a specific direction from the source to the destination. It represents a packet of data.
Fig:4 Data Flow
Processes show the operations performed on the data, which transform it from input to output.
Fig:5 Process
Sources and Destinations of data are the external sources and destinations of data, which may be people, programs, organizations or other entities interacting with the system, but are outside its boundary.
Fig:6 External Entity
Data Stores are places where data are stored such as files and tables.
Fig:7 Data Store
The output symbol is used when a hard copy is produced.
Fig:8 OutputCONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFDs:
1. Process should be named and numbered for an easy reference. Each name should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized
A DFD typically shows the minimum contents of data store. Each data store should contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out. Missing interfaces redundancies and like is then accounted for often through interviews.
SAILENT FEATURES OF DFDs
1. The DFD shows flow of data, not of control loops and decision are controlled considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the dataflows take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
Data Flow Diagrams
Input
Data Store
DATA FLOW DIAGRAM
Level 0
INPUT
OUTPUT
DATA STORE
LEVEL 1: -
User Details
Registered Successfully
USER_DETAILS
User name
Password
Valid User/Admin
LOGIN
Level 2
Place Management
Valid Admin
Hotel Management
Vehicle Management
Valid Admin
Add Place
Edit Place
Delete Place
Place Name
Place Added Successfully
PLACE_DETAILS
Place Name
Viewed
Edited Successfully
PLACE_DETAILS
PLACE_DETAILS
Place name
Viewed Details
Deleted
PLACE_DETAILS
Add Hotel
Valid Admin
Edit Hotel
Delete Hotel
Hotel Name
Hotel Added Successfully
HOTEL_DETAILS
Choose Hotel
edited
Edited Successfully
HOTEL_DETAILS
HOTEL_DETAILS
Choose Hotel
Viewed Details
Deleted
HOTEL_DETAILS
Valid Admin
Viewed
Deleted
FEEDBACK_DETAILS
Valid Admin
Add Vehicle
Vehicle Details
Vehicle Added
VEHICLE_DETAILS
View Place
Valid User
View Hotels
Change Password
Give Feedback
Book Vehicles
Valid User
viewed
Viewed Successfully
PLACE_DETAILS
HOTEL_DETAILS
Valid User
Viewed Successfully
HOTEL_DETAILS
Feedback Details
Feedback Given
FEEDBACK_DETAILS
Valid User
Old Password
Changed
New Password
LOGIN
Booking Details
Booked
SHAPE \* MERGEFORMAT
SHAPE \* MERGEFORMAT
SHAPE \* MERGEFORMAT
SHAPE \* MERGEFORMAT
ER Diagram:
E-R diagram are used to organize data as a relation, normalizing relations and finally obtaining a relational database model.
Elements of an E-R diagram are:
1. ENTITY: This specifies the real life objects & is represented as:
2. RELATIONSHIPS: These connect entities & establish meaningful dependencies between them and are represented by:
3. ATTRIBUTES: They specify the properties of entities & are represented by
E-R Diagram
ADMIN ER
GANTT CHART
TABLES SPECIFICATION:
TABLE NAME: USER_DETAILSPRIMARY KEY: SL_NO
FOREIGN KEY: USERID (LOGIN(SL_NO))
TABLE NAME: LOGIN
PRIMARY KEY: SL_NO
TABLE NAME: PLACE_DETAILS
PRIMARY KEY: PLACE_ID
TABLE NAME: HOTEL_DETAILS
PRIMARY KEY: HOTEL_ID
FOREIGN KEY: PLACE_ID (PLACE_DETAILS (PLACE_ID))
TABLE NAME: VEHICLE_DETAILS
PRIMARY KEY: SL_NO
TABLE NAME: FEEDBACK_DETAILSPRIMARY KEY: FEEDBACK_ID
TABLE NAME: BOOKPRIMARY KEY: BOOK_ID
FOREIGN KEY: HOTEL_ID (HOTEL_DETAILS (HOTEL_ID))
FOREIGN KEY: USER_ID (LOGIN (SL_NO))
Home Page
Registration page
Login
Admin Home
Place Management Page
Hotel Management Page
Vehicle Management Page
View Feedback Page User Home Page
View Places
View Hotels
Give Feedback
Book Page
Change Password
Testing:
After completed all the coding we have our proposed system developed. But how will the client believe that the developed system is up to his requirement? For this testing is essential.
To error is human. In this stage we cannot claim the cent% perfection of our system. Different factors are responsible for our system not to become error free. It may be the communication difference between out client and us. May be some short of negligence from our side of may be the time constraint.So , testing is a vital instrument that makes our system acceptable.
Basically, our System is tested for achieving 5 factors. These are: Online response Volume of transaction.
Stress testing
Recovery & Security
Usability
Unit Testing:
Unit testing is done for each of the program we have done. Our overall system consists of 30-34 independent program module is tested individually for checking their proper functionality.We have done this by debugging all independent modules & running them by giving adequate input necessary for each module.
Checking:
We have to check, whether:
The data validation is done properly or not.
Invoking another servlet program properly or not.
One module is supplying proper value(s) to another module or not
System Testing:
System testing is the last step for validating our system before its implementation.As we have mentioned earlier the 5 objectives of testing are tested then.
(i) Online Response
It is the response time checking. In this we have to check that the user should not face any hardship while using the software. Since our application is web based it is very important for the users part of view it.
We have tested this by giving different transaction on our different pages & observing the downloading time of different pages i.e. activating of our different programs.
For achieving the quicker response time have reduced some unnecessary picture. We have also used some efficient methods available in java programming language, which are quicker functionality than other.
(ii) Volume of Transaction:
Here the user has provided the maximum volume of the data to see whether within that volume the system works properly or not.
(iii)
Stress Testing:
Basic purpose of stress is to provide whether the system is taking the maximum stress or not. i.e .the system behaves properly under peak load or not.This testing is done by providing voluminous data collected from the user.(iv)Recovery & Security:
For system recovery & security we are not so much concerned . Because the software we used have its own recovery & security measures.
How ever for Login purpose we have used session concept for a secure Login.(V)Usability:
Usability test refers the user- friendly nature of our system. It is mostly related to normal operation & error handling procedures. For this purpose we have given easily assessable menus and good user interface.
Conclusion: The project has been appreciated by all the users in the organization as a good CMS site, which will cutoff the maintenance charge as well as time to update the different modules.
It is easy to use, since it uses the GUI provided in the user dialog.
User friendly screens are provided.
The usage of software increases the efficiency, decreases the effort.
It has been thoroughly tested and implemented.
Any endeavor is incomplete without the spirit of teamwork and the RSAT is no different. I could not only muster up support for hosting and fostering this project. But also gather up the enthusiastic team
Apart from the immense effort and support from all the team members,friends, there was a need of referring the following books. Besides that many websites also were visited to get some idea about designing the proposed application successfully.
LIST OF REFERRED BOOKS:
Fundamentals of Software Engineering by RajibMall,Eastern Economy Edition 2008.
Professional Ado.net Programing with Sql Server & Oracle Professional Asp.net 2.0
JavaScript Bible by Danny Goodman and Michael Morrison 5th Edition 2007.
Advance Java Script by Martin , Edition 2006.
LIST OF WEBSITES VISITED:
www.w3schools.com www.tizag.com www.microsoft.com www.codeproject .com www.google.com www.esnips.comSystem Testing
Contents
Project Profile
Tools
&
Technology
Fig-3 Struts Architecture
SRS
Data Flow
Diagram
DATA FLOW DIAGRAM (ZERO LEVEL)
Output
(0.0)
Process
UML
Diagram
SYSTEM.WEB.UI.FORMS
SYSTEM.WEB.UI.FORMS.CONTROLS
SYSTEM.DATA
SYSTEM
SYSTEM.WEB.UI.FORMS
SYSTEM.WEB.UI.FORMS.CONTROLS
BUTTON
Click
Text
Visible
Name
Causes validation
Sender as system.object
E as system.eventargs
TEXTBOX
Click
Text
Name
Visible
Textchanged
Sender as system.object
E as system.eventargs
Grid View
Click
Navigate
Data member
Datasurce
Databind
Template Field
Sender as system.object
E as system.windows.
Forms.navigateeventargs
SYSTEM
SYSTEM.WEB.UI.FORMS.FORM
FORM1
Dispose(protected,overloads,overwrites)
InitializeComponent(private)
New(public)
Load(private)
Sender(system object)
e(system.eventargs)
Disposing(boolean)
SYSTEM.DATA
SYSTEM.DATA..SQLCLIENT
Sqlconnection
Sqldataadapter
Dataset
Sqldeletecommand
Sqlupdatecommand
Sqlinsertcommand
Sqlselectcommand
Statechange
Rowupdated
Disposed
fill
Sender as object
E as system.data.
statechangeeventargs
SYSTEM.DATA.OLEDB
Oracleconnection
Oracleadapter
Dataset
Oracledeletecommand
Oracleupdatecommand
Oracleinsertcommand
Oracleselectcommand
Statechange
Rowupdated
Disposed
Fill
Sender as object
E as system.Data.
StateChangeEventArgs
Profile_id
Dist1
C_name
C_f_name
Has
doj
Profile_master
Topten_master
Has
Has
Reference_master
User_pswpsw
Intro_id
Profile_id
count
Profile_id
Profile_id
Profile_id
no
inactive
Has
User_login_master
-
-master
Gantt chart
Jan 20th Feb 25th March 5th April 10th May 10th May 28th
S
T
A
R
T
D
E
S
I
G
N
C
O
D
I
N
G
D
O
C
U
M
E
N
T
A
T
I
O
N
T
E
S
T
I
N
G
YEAR 2012
Database Design
Screen Shots
Conclusion
Bibliography
(0.0)
PROCESS
Registration Process
(1.0)
(1.1)
Login
(2.0)
Admin Process
Place Management
(2.0.0)
(2.0.0.0)
Place Addition
Place Details
(2.0.0.1)
Edit Place
View Place
(2.0.0.2)
Deletion
Hotel Management
(2.0.1)
(2.0.1.0)
Hotel Addition
Edit Hotel Details(2.0.1.1)
Updation
View Hotel
(2.0.1.2)
Deletion
View Feedback
(2.0.2)
Deletion
Vehicle Management
(2.0.3)
(2.0.3.0)
Add Vehicle
(2.1)
User Process
View Places
(2.1.0)
View Details
View Hotels
(2.1.1)
(2.1.2)
Give Feedback
Change Password(2.1.3)
Change Password
(2.1.4)
Book
VEHICLE_DETAILS
DATE OF FEEDBACK
NO OF VEHICLES
TYPE_OF_VEHICLE
HOTEL_ID
SPECIALITY
COMMUNICATION CHANNEL
PLACE_ID
DISTANCE FROM DISTRICT
PLACE_ID
DESCRIPTION
ACCOMODATION
Has a
PLACE_DETAILS
Type
HOTEL_DETAILS
DISTANCE FROM BBSR
DISTRICT
Has a
HOTEL_NAME
Hotel_id
Distance from district
Distance from district
DISTANCE FROM PLACE
Cost for Non-AC
Cost for AC
STRENGTH
FEEDBACK_DETAILS
LOGIN
AGE
USERID
SL_NO
TYPE
NAME
ADDRESS
AREA_TYPE
ADDRESS
COST FOR AC
COST FOR NON-AC
F_id
F_ID
SUBJECT
FEEDBACK
COMMENTS
USERID
ADDRESS
SLNO
PASSWORD
USERNAME
USER_DETAILS
NAME
Name
SL_NO
PHONE
ADDRESS
GENDER
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
SHAPE \* MERGEFORMAT