04-10-2012, 04:13 PM
A PROJECT REPORT ON Transport Routing System for College
Routing System.doc (Size: 348.5 KB / Downloads: 32)
ABSTRACT
Transport routing enables an effective and up-to-date system that allows the colleges and organizations to maintain transport for their organization members (Students and Lecturers) pick up and drop facility.
In today’s scenario only verbal and manual communication happens between the transport department and the students & lecturers. There is no automation system that exists today. The colleges prepare the schedule in excel sheets, print them out and hands it over to the drivers or concerned persons. Since the number of students/lecturers vary from vehicle to vehicle their renewals, vehicle maintenance become complex.
The system proposes to automate the above task. The college can maintain their own vehicles information along with the routes they take information of Students and Lectures, who are interested in availing the transport facility. It also provides the facility to deallocate a seat in the vehicle. The fuel consumption information of the vehicles are also to be maintained by the members meant for vehicle maintenance. This Application enables the College management to maintain the transport details of routes, vehicles, students & lecturer renewals, fuel information etc in an easier and standard manner.
INTRODUCTION
Transport routing enables an effective and up-to-date system that allows the colleges to maintain transport for their members (Students and Lecturers) pick up and drop facilities.
In today’s scenario only verbal and manual communication happens between the transport department and the students & lecturers. There is no automation system existing today. The colleges prepare the schedule in excel sheets print them out and hands it over to the drivers or concerned persons. Since the number of students/lecturers vary from vehicle to vehicle, their renewals, vehicle maintenance becomes complex.
The system proposes to automate the above functioning. The college can maintain their own vehicles information along with the routes they take, Students and Lectures information who are interested in availing the transport facility.
A route monitor module identifies the routes the vehicle travels and pickups or drops of the students only on that route. Some employees can be engaged to track the information of the vehicle moving daily to pick and drop them at their respective routes. The renewals and the list of the non renewaled candidates, clear information of the seats allocated to the students or lectures in the vehicles can be developed by the administrator.
It also provides the facility to deallocate a seat in the vehicle. The fuel information of the vehicles are also to be maintained by the members set for vehicle maintenance.
This Application enables the College management to maintain the transport details of routes, vehicles, students & lecturer renewals, fuel information etc in easier and standard manner.
PROJECT DESCRIPTION
The application that is designed uses the multilayer architecture where the application is placed under the control of webserver that provide security to the application and publish it in the network. The application maintains the transactions like handling the information of routes, the vehicles specified with the route information, vehicle drivers and supervisor information. The administrator allocates the seats for the required seats for students & lecturers. He also maintains the information of renewals & non renewals that are done regularly. The other users like HOD & Organizer can log-in to view the information of the students & lecturers availing the transportation & their renewal details.
The Application handles the information of routes, vehicles, students & lecturers information. It tracks the list of cleared & pending renewals. It enables the supervision to maintain the information of the daily trips that are set on vehicles for pickup & dropping. It allows the other users to view the required reports as necessary.
The application that is proposed is web oriented & hence uses JSP with HTML to design the required dynamic web pages. The client system can invoke or use the web pages using the browser tools provided in the respective operating system. Since the application is web oriented it needs to be deployed under the web server that provides security to the application. The clients can only execute to the remote areas but cannot alter the source code at any point. This provides the source code security. It also enables the administrator for easy future enhancements as the application is located only at one place.
SYSTEM ANALYSIS
The analysis of the existing system has to be carried to learn the details of the existing system. System analysis is the process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvements to the system. Only after the system’s analysis we can begin to determine how and where a computer information system can benefit all the users of the system. This accumulation of the system called a system’s study.
Present System:
In the current scenario, the information of the transportation provided by the colleges, are maintained offline (in registers). It becomes complex for the managing authority, to maintain the information of the vehicles with route specifications, the information of students & lecturers, allocation and de allocation of the seats in the vehicles etc. It also is difficult to track the information of the renewals to trace the completed & pending renewals data. The information of the trips made by the vehicles is maintained in person and the fuel information is offline making it difficult to trace their efficiencies.
Proposed System:
The application that is proposed online works under the control of the central server were the clients or users can access them from remote sources. The application that is designed split in to the several modules as below.
FEASIBILITY ANALYSIS
Many feasibility studies are disillusioning for both users and analysts. First, the study often presupposes that when the feasibility document is being prepared, the analyst is in a position to evaluate solutions. Second, most studies tend to overlook the confusion inherent in system development-the constraints and the assumed attitudes. If the feasibility study is to serve as a decision document, it must answer three key questions
SYSTEM DESIGN
Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. Design is the first step in the development phase for any engineered product or system. The designer’s goal is to produce a model or representation of an entity that will later be built. Beginning, once system requirement have been specified and analyzed, system design is the first of the three technical activities -design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where quality is fostered in software development. Design provides us with representations of software that can assess for quality. Design is the only way that we can accurately translate a customer’s view into a finished software product or system. Software design serves as a foundation for all the software engineering steps that follow. Without a strong design we risk building an unstable system – one that will be difficult to test, one whose quality cannot be assessed until the last stage.
DESIGNING A DATABASE:
Good design is a key factor of successful database building. A well designed database can lead to more efficient use of queries, forms, and reports, and can increase the reliability of the extracted information. In addition, an effectively designed database will be easier to expand as you organization’s information requirements grow and change.
Although there are guidelines to assist you in designing your database, there is no such thing as a perfect database design. Designing information systems always involves a degree of compromise. The purpose of this appendix is to provide a general overview of good database design principles. These guidelines should not be viewed as hard and fast rules, but rather suggestions for making your database design decision. Although there is no one correct way to create a database, there are some general steps that some professional systems developers follow. These steps generally reflect what is known as the Systems Development Life Cycle (SDLC). The SDLC breaks the task of creating a system into stages. A variety of techniques can be employed to answer these questions. One of the best ways is to involve the future end-users of the database. A database, however, may have hundreds or even thousands of users. However, if the database is very large, you might have to consult representatives of various user groups, such as a database design committee.
WORKING WITH TABLES IN DATASHEET VIEW:
Tables are used to store data in a database. Tables can be created in two views, Table Design view or Datasheet view. In addition, you can use the Table Wizard or import a table from an external file. Records are automatically saved as you move from record to record but changes to the layout of a table (or a form) must be saved.