OPEN CABSTER PROJECT DOC
Download as DOCX, PDF0 likes827 views
The document provides requirements for an Open Cabster taxi management system. It includes sections on introduction and purpose, overall description of the system and its functions, user characteristics, and specific requirements. The system is designed to manage front office and back office functions for taxi operators, including vehicle booking, allocation, billing, maintenance management, and reporting.
OPEN CABSTER PROJECT DOC
- 1. OPEN CABSTER (CALL TAXI MANAGEMENT SYSTEM ) SOFTWARE REQUIREMENT SPECIFICATIONS DOCUMENTATION (SRS Documentation) KGiSL Institute of Technology, Saravanampatty, Coimbatore-641035. SUBMITTED BY DEEPAK KISHORE.S NARENDHRAN.S RAMGUHAN.G SIVA KUMAR.B
- 2. Table of Contents 1. Introduction 1.1. Purpose 1.2. Scope 1.3. Definitions 1.4. References 1.5. Overview 2. Overall Description. 2.1. Project perspective 2.2. Project functions 2.3. User characteristics 2.4. Constraints 2.5. Assumptions and Dependencies 3. Specific Requirement 3.1 External interface requirements 3.1.1. User interfaces 3.1.2. Hard ware interfaces 3.1.3. Software interfaces 3.1.4. Communication interfaces 3.2 Functional requirements 3.2.1. Information flows 3.2.1.1. Context Dataflow diagram 3.2.1.2. UML Diagrams
- 3. OPEN CABSTER 1. Introduction: 1.1. Purpose OPEN Cabster has been specifically designed keeping in mind the requirements of a cab operator. A cab operator operates in a service industry, which requires high standards of efficiency to be successful. A cab operator provides vehicles on hire to customers and bills them according to the tariff card. The key success factors in this business are quality of service, condition of the vehicle, competitive pricing, customer-interface etc. A cab operator has to keep tight control over these factors to be competitive and remain profitable. 1.2 Scope The scope of work would include: The scope of the product to manage the front End & Back Office functions of a CAB Operator consists of the following key modules. It is to be noted that all the modules may not be applicable to all transporters. Front – Office Management Vehicle Maintenance Management Administration Module MIS Reports 1.3. Definitions OPEN CABSTER – cab management system Customer : Any Person / persons / institution / Organization which is interested to Hire the Vehicle . 1.4 References 1.IEEE Documents for SRS
- 4. 1.5 Overview : OPEN CABSTER –CALL TAXI MANAGEMENT SYSTEM, The ideal solution for Fleet Management , is specially designed for Cab-Operators who operate a fleet of vehicles for hire. The vehicles maybe Cars, pickup vans, buses, etc. OPEN CABSTER enables you to manage demand-supply position of vehicles, keep a tab on the mileage, reduce maintenance expenditure and operating costs. It automates your entire front-office operations like accepting customer bookings, allocation of vehicles & drivers prepare customer invoices. The system also takes care of all back-office operations like capturing of maintenance costs incurred, fuel purchase, accident records, service log etc. Admin Module handles the entire Master forms such as Company information, Employee information User allocation, change password, Vehicle type , vehicle tariff, This module also helps to configure such as Financial year configuration etc., You can now be better organized and efficiently equipped to manage a small or large fleet of vehicles with up-to-date analytical information on Vehicle Bookings, Vehicle Allocation, Customer details, fuel issues, fuel consumption, mileage efficiency, maintenance expenditure, service log, etc 2. Over all description: 2.1 Project perspective a). System Interfaces: The application enables users to login directly to Web site / Intranet from their desktop using a conventional Web browser. OPEN CABSTER system is an Internet / Intranet Application. OPEN CABSTER – Cab is an independent, totally self-contained application runs web server like IIS and on Windows Operating System. This web enabled application works with browser like Internet explorer 5.0 and above at client side. OPEN CABSTER – Cab will be based on Internet architecture and the layout of the application is explained in the following diagram.
- 5. Architecture of OPEN CABSTER –Cab A. User: Who ever uses the system B. Web Server: The Business Logic / Validations / Security of the OPEN CABSTER – Cab will be implemented here. C. Database Server: The information of the OPEN CABSTER – Cab will be stored in the Database Server. It can also be called as Data Services (SQL Server 2005). b). User interfaces: This section describes the application with the help of word document proto type screen flow design. The next few screens explain the navigation of each and every page of OPEN CABSTER – Cab. c). Hardware Interfaces: This application is purely Internet Application, which runs through HTTP Protocol.
- 6. d). Software Interfaces: 1. Application installed on Web server. Clients can access server through any client by using WEB browser like Internet explorer 5.0 and above. 2. Client network should support any network protocol like TCP/IP. e). Communication interfaces: For the establishment of Internet following Communication protocols are necessary. 1. TCP/IP protocol. 2. HTTP protocol. f). Memory constraints: There is no constraints on memory related issues. Normal server and client Configuration is sufficient to run this application. 2.2 ProjectFunctions : 2.2.1 FrontOffice Automation: OPEN CABSTER comes in a plug and play environment supporting two modules – Operations and Maintenance . The Operations module automates the front-office activities – customer bookings, allocation / Duty Slip of vehicles and customer billing. The system captures all-important details related to these activities for further MIS analysis. Maintaining the Party / Customer details Vehicle Booking Details Vehicle Allocation Vehicle Billing
- 7. 2.2.2 MaintenanceModule: Free Yourself from Maintenance Headaches The maintenance module allows you to capture the maintenance costs incurred on a vehicle on account of spares & labor. The maintenance can be classified against a trip or service or breakdown.. It gives you analytical information on the average maintenance cost, mean time & mean-mileage between failures. You can also get a detailed report on each maintenance activity, and it can also tell you when the next service is due and when a particular document is supposed to be renewed. The Service Log is updated in two instances – once when the vehicle is being sent to the service station and next when it returns back to garage after service. The Entry/ Edit tab is presented by default to enter the service particulars. The History tab enables you to view the service history details of the vehicles in the fleet. The View tab shows the existing service records for editing pre-service details, update post-service details or cancellation. Maintaining The Accident Details Vehicle wise Managing the Services and breakdown of Vehicle Maintain the service Log of the vehicle Alerts for Maintenance 2.2.3 Administration Module: Admin Module handles the entire Master forms such as Company information, Employee information User allocation, change password, Vehicle type , vehicle tariff, This module also helps to configure such as Financial year configuration etc., Maintaining the Details of the Company Vehicle Type Vehicle Master Vehicle Tariff Employee Master User Master
- 8. 2.2.6 MIS Reports Module: The Reporting system is used for the management purpose, which easies the use of the application. For Management the total information will be available on finger tips. Reporting module consists of reporting by Vehicle availability, vehicle allocation, Vehicle Maintenance, Customer details, Customer bookings. Management reports (MIS) will be developed in crystal reports which can be displayed as reports given an option to convert that reports to Microsoft Office Word, Microsoft Office Excel, PDF formats. This data can be used for management to take crucial decisions. 2.3 User characteristics: Intended Users: Only Registered or employees of the co., can browse the site. Users have to enter a userid and password to login. User should have a minimum awareness of web applications like how to navigate with browser and down loading. 2.4. Constraints: As it is a web application on Internet it won’t have any constraints, regarding Hardware bottlenecks, Network traffic, regulatory policies, safety and security of this application. 2.5 Assumptions and dependencies: This application assumes the following:
- 9. 3.Specific requirements: 3.1 External interface requirements: Hardware environment: Application is being implemented in the following Internet environment: Client systems Any system that support Internet Browsing using any browser with a minimum 64 MB RAM and 200MHz clock speed Preferable client system – CORE 2 DUO or higher with 64 MB RAM running windows /98/NT/XP/HIGHER Network TCP/IP,HTTP DevelopmentEnvironment Client Systems PC’s running Windows 95/98/NT/VISTA/ Server System IIS4.0, Network TCP/IP,HTTP Soft ware tools used ASP.net , C# net , Sql server 2005 Project Documentation MS Word
- 10. 3.2 Functional requirements: 3.2.1.Informationflows : 3.2.1.1ContextData Flow Diagram: (First Level Data Flow Diagram) ADMIN FLOW DIAGRAM
- 11. 3.2.1.2 Second Level Data Flow Diagram Front Office Use Case Diagram