e/u 6 >^^ 3^7f^ Universiti Teknologi MARA Development of Web-Based Fleet Management System Zulfa Binti Mohamed Hamim@Abdul Hamid Thesis submitted in fulfillment of the requirements for Bachelor of Science (Hons) Information System Engineering Faculty of Information Technology And Quantitative Science April 2005
DECLARATION I hereby declare that the work in this thesis is my own work and ideas except for quotations and summaries from others' work which have been appropriately acknowledged. April 20*, 2005 Zulfa Binti Mohamed Hamim@Abdul Hamid 2002611433 11
ACKNOWLEDGEMENT Alhamdulillah, in the name of Allah the All Mighty, the Most Compassionate, the Most Merciful and the Most Gracious, praise to Allah, the one and only, for giving me patience, strength and ability to complete this thesis. First and foremost, I would like to thank Prof. Dr. Noor Habibah Hj. Arshad because of her guides on what and how to do this thesis. I also owe deep thanks to my supervisor En. Ali Bin Seman for his supervision, assistance, idea and patience in supporting my thesis from proposal up to the completion of the dissertation, and thank him for giving me the opportunity to work under his supervision. I would like to address special appreciation to my beloved parents and my family for their love, care, pray and support that gave me strength to study. Without them I will not be able to completely finish this thesis. Not forgetting to Ir. Tn. Hj. Kamaludin Bin Othman and all staffs in Drainage and Irrigation Department of Pahang (DID) for their cooperation in completing this thesis. Moreover, I especially thank my fiiend, Nur Syazwani Ghazali for her technical help, encouragement and support to complete this thesis. Lastly, my sincere gratitude extends to all individuals who have contributed either directly or indirectly in ensuring the success of this thesis. Thank you. Ill
TABLE OF CONTENTS CONTENT ACKNOWLEDGEMENT TABLE OF CONTENTS LIST OF TABLES LIST OF FIGURES LIST OF ABBREVIATIONS CHAPTER 1: INTRODUCTION 1.0 The Background of the Project 1.0.1 Historical Development of the Department of Drainage and Irrigation (DID) 1.1 Project Problem 1.2 Project Scope 1.3 Project Objective 1.4 Project Significance 1.5 Project Limitation 1.6 Conclusion PAGE iii iv viii ix xii 1 2 5 5 6 7 7 8 CHAPTER 2: LITERATURE RIVIEW 2.0 Problemsof Existence System at the DID of Pahang 9 2.0.1 Aset JPS Pahang 10 2.0.2 SmartPay 11 2.1 Fleet 12 2.1.1 Fleet Management 12 2.2 Examplesof Real Fleet Management in Market 14 2.2.1 FleetFocus FA 14 2.2.2 Global Positioning System (GPS) 15 2.2.3 GPS Fleet Management and Fleet Tracking 16 2.2.4 GE Fleet Services 17 2.2.4.1 Driver Order Management 17 2.2.4.2 Fleet Reporting 18 IV
2.2.4.3 Vehicle Ordering 19 2.2.4.4 View/Update Vehicle 20 2.2.4.5 Fleet management Solutions 21 2.2.4.6 Electronic Fuel Card 22 2.2.5 Manager Plus 23 2.3 Conceptual Modeling for Web Development 25 2.3.1 The Architecture Framework of Web-based System 26 2.4 Conclusion 30 CHAPTER 3: RESEARCH APPROACHES AND METHODOLOGY 3.0 Unified Software Development Process (USD?) 31 3.0.1 Inception 31 3.0.2 Elaboration 32 3.0.3 Construction 32 3.0.4 Transition 32 3.0.5 The Activity Diagram 33 3.0.5.1 Project Planning 34 3.0.5.2 Data Collection 34 3.1 Conclusion 35 CHAPTER 4: CONSTRUCTION 4.0 Introduction 36 4.1 System Design 36 4.1.1 Actor and Use Case 37 4.1.2 Sequence Diagram 46 4.1.2.1 Sequence Diagram for Viewing Information by 46 Following the Status 4.1.2.2 Sequence Diagram for Keying In Information 47 4.1.2.3 Sequence Diagram for Viewing Comparison 47 4.1.2.4 Sequence Diagram for Updating Information 47 4.1.2.5 Sequence Diagram for Viewing Report by 48 Status
4.1.3 Class Diagram 49 4.2 Web page Design/Interface Design 51 4.2.1 Hierarchal system Workflow 51 4.2.2 Inputs and Outputs 58 4.2.2.1 Designing Inputs 58 4.2.2.2 Designing Outputs 58 4.2.3 Highlighting Information 59 4.3 Database Design 60 4.3.1 Entity-Relationship Modeling 60 4.3.2 Data Dictionary 61 4.4 Architecture Design 66 4.4.1 Web Client/Server Architecture 66 4.5 Implementation Design 70 4.5.1 Setting up Development Environment 70 4.5.2 Data Source Development 70 4.5.3 Engine Development 71 4.5.4 Interface Development 79 4.5.5 Hardware and Software for Developer 80 4.5.6 Hardware and Software for User 81 4.6 Conclusion 82 CHAPTER 5: RESULTS AND FINDINGS 5.0 Introduction 5.1 Login Page 5.2 Update Page 5.3 Add Data Page 5.4 Delete Page 5.5 View Page 5.6 Conclusion 83 84 86 88 98 101 108 CHAPTER 6: CONLUSIONS AND RECOMMENATIONS 6.0 Conclusions 109 6.1 Recommendations 111 VI
REFERENCES 112 APPENDICES Appendix A: Gantt Chart Appendix B: E-R Diagram Appendix C: Log Book Sample Appendix D: SmartPay Invoice Sample Appendix E: SmartPay Card Sample Appendix F: Sequence Diagrams Vll
LIST OF TABLES TABLE TITLE PAGE 4.0 Description of Tables 61 4.1 Attributes description of table DATAKAKITANGAN 62 4.2 Attributes description of table DATAKENDERAAN 62 4.3 Attributes description of table KENDERAAN 63 4.4 Attributes description of table SMARTP AY 64 4.5 Attributes description of table BUKULOG 65 vm
LIST OF FIGURES TITLE PAGE 2.1 2.2 2.3 3.0 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 5.0 5.1 5.2 The Architecture Framework of the Web-based System 26 The 3-tier Architecture for Web-based System Development 27 Framework of Web-based System Development 28 The Activity Diagram 33 Use Case External Interface Diagram 37 Main Use Case Diagram for WFMS 38 Use Case Diagram for Viewing Information About 42 Staffs and fleets Use Case Diagram for Keying In Information 43 Use Case Diagram for Viewing Monthly Report 44 Use Case Diagram for Viewing Comparison 44 Use Case Diagram for Updating Information 45 Packages in WFMS 49 Interfaces/Boundary Classes in WFMS Interface 50 Controller Class in WFMS Management Package 50 Entity Class in WFMS Storage Package 50 Structure Design for Penyelaras 52 Structure Design for Pemandu 53 Structure Design for Ketua Unit 54 Structure Design for Pegawai 55 Structure Design for Pentadbir Laman Web 56 Structure Design for Overall System Workflow 57 Web Client/ Web Server Diagram 68 WFMS System 69 Create New Data Source Dialog Box 71 Example of Login Page to Enter the System 84 Example of Error Login Page to Enter the System 84 Example of Penyelaras Status Page that is authenticated to 85 enter the System IX
5.3 Example of PentoJi>j> Lflt/nan ^efc Status Page that is 86 authenticated to enter the System 5.4 Example of Pentadbir Laman Web Status Page to Modify 87 the Information of the Selected Fleet the System 5.5 Example of Pe«toc?i>«r Zflman PFefo Status Page to Choose 88 the Add Form for New Staff Registration 5.6 Example of Add Form for Pentadbir Laman Web Status 89 Page 5.7 Example oi Pentadbir Laman Web Status Page after Adding 90 New Staff Information 5.8 Example of Pento<iZ>irZawfl«PFefe Status ConfirmationPage 91 after Adding New Staff Information 5.9 Example of PentoJfefr Zawflw ffe6 Status ConfirmationPage 92 after the New Staff Information is Added 5.10 Example of Penye/flra5 Sto^ui'at Kuantan District to Add 93 Log Book Information Page 5.11 Example of Penyelaras Status at HQ Position Page 94 5.12 Example of jpenye/ara5 5to^M5 at HQ Position Page to 95 Choose the Fleet to Add the Smart Pay Information Page 5.13 Example of Penyelaras Status at HQ Position Page to Alert 96 if there is No Fleet Record for Smart Pay Information of Selected Fleet 5.14 Example of Penj^e/ara^ istofu^ at HQ Position Page to Add 97 Smart Pay Information of Selected Fleet 5.15 Example oi Pentadbir Laman Web Status Page to Select the 98 Staff Information to be Deleted 5.16 Example oi Pentadbir Laman Web Status Page to Confirm 99 Deleting the Staff Information 5.17 Example oi Pentadbir Laman Web Status Page to Confirm 100 Deleting the Fleet Information 5.18 Example of Penyelaras Status at Kuantan District Page to 102 View the Staff Information at Kuantan District Only 5.19 Example of Penyelaras Status at Kuantan District Page to 103
View the Staff Information at Kuantan District Only 5.20 Example of Pentadbir Laman Web Status Page to View all 104 the Staffs Information 5.21 Example of Pentadbir Laman Web Status Page to View the 105 Analysis of Overall Log Book Report 5.22 Example of Pentadbir Laman Web Status Page to View the 106 Analysis of Overall SmartPay Report 5.23 Example of Pentadbir Laman Web Status Page to View the 107 Analysis of the Fleets Information Record 5.24 Exampleof Pentadbir Laman Web Status?sige to View the 108 Selected Fleet log Book Report XI
LIST OF ABBREVIATIONS WFMS DID LAN WAN ERP GPS AVL ASP HTML ODBC SQL ADO CGI GUI XML HTTP USDP UML DBMS RPC CASE IIS HCI Web-Based Fleet Management System Department of Drainage and Irrigation Local Area Network Wide Area Network Enterprise Resources Planning Global Positioning Systems Automated Vehicle-Locating Active Server Page Hyper Text Mark-up Language Open Database Connection Structured Query Language ActiveX Data Objects Common Gateway Interface Graphical User Interface Extensible Mark-up Language Hyper Text Transfer Protocol Unified Software Development Process Unified Modeling Language Database Management System Remote Procedure Calls Computer-Aided Software Engineering Internet Information Services Human Computer Interaction Xll
ABSTRACT This report is a detailed documentation of a web-based application entitled "Development Web-based Fleet Management System (WFMS)". The project objective is to develop the WFMS application using Active Server Pages (ASP) technology with applying the UML approaches. This system is developed to make the management fleets' operation of the Department of Irrigation and Drainage of Pahang to be a web-based application. The web-based application is designed by following the department requirements with the hope to help the department to get monthly report of the fleets from district all over Pahang, view the comparison between selfrecord log book report that is done by the driver and the SmartPay invoice from Petronas, and also view the information of the fleets and staffs who are using the system. Furthermore the system will produce the analysis of the overall fleets operation and the fleet's invoice. The development of the system has following the Unified Software Development Proces (USDP) which comprises of four phases including of inception, elaboration, construction and transition. In addition, the developer also put research technique to write the client/server scripting to match with the user requirements. The user who will interact with the system are already defined by the DID. The finding of this project is the output that will produce the information by following the user requirements. Xlll
CHAPTER 1 INTRODUCTION This chapter provides the background and rationale for the system development. It also gives details of project's problem, scope, objective, limitation and significance. In addition this chapter will briefly describe about the organization which will be the user of the system. 1.0 The Background of the Project Over the last two decades, virtually every facet of fleet management and operation has changed in one way or another. Most people will agree that the electronic age, specially the emergence of information system and telecommunication technology has had a profound in fleet management. However, they would also agree that the affect these things have had on the industry has been uneven. By breaking the organization of fleet management down into its constituent parts, we can better appreciate the transformative impact that technology had on the fleet management. Realizing whether it is accurate or just a myth it already happens almost in all organizations or industries which are dealing with transporting services no matter in our country or overseas countries. The development of Web-Based Fleet Management System (WFMS) is as required by the Department of Drainage and Irrigation (DID) of Pahang which they need a system to manage and monitor their fleet's information, maintenance, and can provide report of each vehicles they might have in each districts in Pahang by the end of each
month. Furthermore, this system will be easily reached by their staffs all over Pahang since it is a web-based system. 1.0.1 Historical Development of the Department of Drainage and Irrigation (DID) The history of the DID dates back to the early 1900's. In 1911, a separate Irrigation Branch of the Public Works Department (PWD) was formed to handle hydrological investigations. This branch was reorganized in 1920, and was then renamed the "Hydraulics Branch of the PWD" in the following year. Its scope of work was expanded to included surveys and investigations for river conservancy. The first food crisis occurred as early 1918. The second occurred following the trade depression and rubber slump in the late I920's. In 1927, the PWD was restructured and was provided with additional staff for river conservancy works to complement irrigation and water supply projects. Discussions on the need for a separate department to undertake irrigation and drainage works began in earnest in 1930. In the same year, the Government set up the Rice Cultivation Committee for the purpose of considering "What are the best steps to be taken in order to encourage rice cultivation in Malaya". This Committee submitted its report in 1931 and in the report it stated that, "Too great reliance on imported supplies of rice is a source of danger" and that "steps to encourage the extension of rice cultivation would be an insurance against possible future crisis owing to food shortage". One of the main recommendations of the rice Cultivation Committee Report called for the formation of an agency to deal with the problems of land and water development which were then the responsibility of the Hydraulic Unit,
Public Works Department. This culminated in 1932 with the formation of a new department, known as the Drainage and Irrigation Department which held executive power in the Straits Settlements and the Federated Malay States and advisory in nature in the Unfederated Malay States. In the same year, the DID assumed responsibility for river conservancy from the hydraulic Branch of the PWD. Its objectives were to provide, maintain or regain a stable river regime by maintaining natural channels, implementing flood control works and river diversions where necessary. In the early years, the DID had its headquarters building situated at the Suleiman Building, Kuala Lumpur. However in 1961, it shifted to the present DID buildings on Jalan Sultan Salahuddin in Kuala Lumpur. Uneven rainfall distribution, together with Malaysia's peculiar topography, makes it reliable to depend on rain fed method for rice cultivation. The DID's primary objectives were to alleviate these problems through sustainable irrigation methods and to prevent or reduce the effects of floods and the intrusion of tidal water into agricultural land. Plans were drawn up to improve irrigation and drainage facilities, develop new areas for rice cultivation, construct agricultural drainage facilities for the cultivation of other crops, and maintain as well as improve on the country's natural waterways. The DID's core business were redefined to include the importance of water in agriculture and food production, the need to protect life and property from river and coastal threats, the managements of water in enhancing the environment and as a national resource. Today, the DID comprise five main divisions: 1. Irrigation and Agricultural Drainage 2. Drainage and Flood Mitigation 3. River Engineering
4. Coastal Engineering 5. Hydrology and Water Resources These supporting Divisions are: 1. Corporate Development 2. Specialist Services 3. Mechanical Services 4. Human Resources Development 5. Quantity Survey 6. Administration and Finance 7. Information Technology 8. Quality and Productivity As listed above, DID has the Mechanical Services Division in each state of Malaysia. This division usually is given maintenance task and to deal with the fleets' operation of each state. The supervisor of this project at DID of Pahang require an online system that can be accessible by certain staffs that are involving with the fleet management system.
1.1 Project Problem There are some problems has been faced by the DID by using the existence system. Some problems that they encountered are as follow: 1. The existence log book system is not practically works. 2. Only few districts submit their monthly log book report. 3. The available information of exist data cannot be shared with other computer. 4. Existing system don't have security protection. As a precaution the WFMS is developed to prevent and overcome those problems. After having discussion with DID of Pahang, this system is developed with following the requirements from them. 1.2 Project Scope The project is developed for Mechanical Services Division of DID of Pahang. The users of this application are staffs of the DID Pahang. The system has a few fiinctions as required by DID which are: 1. To view, add, edit, update and search all the information of the DID, Pahang's fleets and staffs in Pahang including all districts such as Kuantan, Pekan, Maran, Bentong, Bera, Temerloh, Rompin, Cameron Highlands, Jerantut, Raub, Lipis, Pahang (HQ) and also the Mechanical Services Division. 2. To computerized the fleet's log book system management that can be sent online through Internet for each district all over Pahang.
3. To view the fleet's log book and report of each district at Pahang (HQ) in a summarization form. 4. The system only can be accessed by certain staff of DID of Pahang using their own password that will be given to them each by following their status. 5. To view a comparison between the monthly fleet's log book system and SmartPay (a monthly invoice from Petronas). This system will be used by the following status as below: 1. Ketua Unit - HQ Officers. 2. Pentadbir Laman Web as approved by Mechanical Engineer (the project supervisor at DID). 3. Pegawai - Officers in each district. 4. Penyelaras - staffs who will key in information the log book. 5. Pemandu - drivers who can view the log book report. 1.3 Project Objective The project objective is to develop Web-based Fleet Management System (WFMS) for Mechanical Services Division of DID of Pahang using ASP (Active Server Page) technology and UML approaches.
1.4 Project Significance Here are some of significances of the project: 1. Solving the existing problem that is done manually. 2. Introducing new application of the latest technology released and giving an explanation on that so they will know how the online system works. 3. The organization can update the information included in the system fast and easy. 4. The system has a password protection to keep the data always secured. 5. All the information for the system can be retrieved in any computer because the system is reachable via Local Area Network (LAN) or Internet. 1.5 Project Limitation To meet the users need and satisfaction, there are many problems that the developer encounters during the development process such as: 1. The developer has to deal with real user requirements which have a lot of changing information during the development processes. 2. Lacking of references and j oumals of this kind of system. 3. Difficulties on handling databases design.
1.6 Conclusion This Web-based Fleet Management System (WFMS) is developed to be an interactive web-based environment that is intended to facilitate and/or improve human problem solving capability within some target application domain. The nature of WFMS facility will therefore depend upon whom it is intended to serve and the job tasks for which it is to be used. In developing the system the developer discuss one way in which computer technology can be used to create WFMS that simultaneously fiilfils the need of both DID's administration and their staffs. The WFMS is based upon an online system where staffs of DID of Pahang can access to key in log book monthly record and also for office administration to access to a summarization of the report at the end of the month. The WFMS can be expanded to various aspects and ability to help the other user to use the system. As a conclusion, the developer hopes that this system can reduce the problem of the existence system.
CHAPTER 2 LITERATURE REVIEW This chapter provides the literature review that is related to the project development. It reviews about the existence of other systems. The sources are merely taken from books, articles, journals and also sources from Internet. 2.0 Problems of Existence System at the DID of Pahang hi the era of ICT, the internet is becoming one of essential medium to communicate with each other. The developer already given the explanation of the problem faced to manage and monitor their fleet management system by the supervisor's of the project at DID of Pahang. They currently have some windowbased systems to keep recording their fleet operation; nevertheless that information could not be shared with other computer because they have developed a window-based system. Furthermore, most of the fleet's report operation from each districts usually sent by post. Sometimes the DID of Pahang have a delayed report because of time and distance constraint. However not all reports from each districts have been sent to DID of Pahang due to some reasons. In addition, the present system that they have does not have a security protection. Anybody can access and get data from the computer which stores the fleet's information. Generally each driver who drives the fleet will write a daily report on the log book that already provided for each fleets. The log book contains the information about daily operation of the fleet such as the quantity of fuel they used or bought per day, the odometer reader value, name of drivers, type of fuel, and place and date of fiiel taken. When the report is done manually,
sometimes an unauthorized purchasing fuel might happen. The DID can trace this unauthorized transaction by getting monthly invoice report from Petronas which known as SmartPay invoice. As mentioned in problem statements, the DID already has their own solution to manage and supervise their fleet operation. Since the used of web technology is widely applied in most organization nowadays has made the DID want to change the manually system to be web-based so they can easily observe and control their fleet operation over Pahang state. Meantime, the DID is using two Microsoft Access window-based systems which are Aset JPS Pahang and SmartPay. 2.0.1 Aset JPS Pahang Aset JPS Pahang is a stand-alone system to supervise the fleet information of the DID in Pahang. This system is developed by the mechanical engineer of DID of Pahang, Ir. Kamaludin Othman. The functionality of the system is to add new fleet information including of fleet's registration number, brand, date of buying the fleet, cost, status and type of fleet. The system also can update the fleet information in databcise. Furthermore, the system allow user to view all the fleet detail information for each district in Pahang. This system doesn't have password protection that make the information in the system can be viewed by any staffs at DID of Pahang. 10
2.0.2 SmartPay SmartPay is also a stand-alone system which is developed to record the monthly invoice of purchasing fuel at Petronas station over Malaysia. Petronas has their own record keeping system of any fuel purchasing from divers of DID of Pahang which is also known as SmartPay system. Every driver has a card from Petronas which stored their information and also a fleet card of each fleet they used. So every purchasing fuel at the Petronas station will be kept until the end of the month and Petronas will send an invoice of every single purchasing fuel by the drivers of DID of Pahang. So the functionality of the SmartPay System which has been developed by one of the Mechanical Division Services Staff of the DID of Pahang, Zainal Abidin Mat Nor is to record the invoices from Petronas. In addition the staff can add the invoice information in the system and the system will provide the analysis report of fiiel usage for each fleet and the bills. Other than that the system also can view which bill that hasn't being paid yet. This system also doesn't have password protection. The DID of Pahang also has manually record keeping of purchasing the fiiel which known as log book that already kept in each fleet to record the daily operation of that fleet including the odometer reader, date and time of fleet operation, driver's name and the quantity per liter of purchased fuel. Hence the WFMS is developed to integrate all those systems to be web-enabled and easy to supervise their fleet operation. 11