Mobile Based Route Planner For Klang Valley Rail Transportaion
MOBILE BASED ROUTE PLANNER FOR KLANG VALLEY RAIL TRANSPORTAION MATTHEW GOH WEE HIEN A project proposal submitted in partial fulfilment of the requirements for the award of Bachelor of Science (Hons.) Software Engineering Faculty of Engineering and Science Universiti Tunku Abdul Rahman August 2013
ii DECLARATION I hereby declare that this project report is based on my original work except for citations and quotations which have been duly acknowledged. I also declare that it has not been previously and concurrently submitted for any other degree or award at UTAR or other institutions. Signature : Name : ID No. : Date :
iii APPROVAL FOR SUBMISSION I certify that this project proposal entitled “Mobile Based Route Planner For Klang Valley Rail Transportation” was prepared by Matthew Goh Wee Hien has met the required standard for submission in partial fulfilment of the requirements for the award of Bachelor of Science (Hons.) Software Engineering at Universiti Tunku Abdul Rahman. Approved by, Signature : Supervisor : Ooi Ean Huat Date :
iv The copyright of this report belongs to the author under the terms of the copyright Act 1987 as qualified by Intellectual Property Policy of Universiti Tunku Abdul Rahman. Due acknowledgement shall always be made of the use of any material contained in, or derived from, this report. 2013, Matthew Goh Wee Hien. All right reserved.
v Specially dedicated to my beloved family and those who love me .
vi ACKNOWLEDGEMENTS I would like to take this opportunity to express my deepest gratitude for those who have helped me throughout the completion of the project. First of all I would like to thank my project supervisor Mr James Ooi Ean Huat for his continuous guidance, support and encouragement given throughout the project execution. Other than that, I would like to thank my project moderator, Mr Madhavan for his advice and guidance to improve the project. Last but not least, I would also like to thank all my family and friends that have supported me in this project.
vii ABSTRACT This document describes and records the all the processes involved during the development of “Mobile Based Route Planner for Klang Valley Rail Transportation”. The target audience for this project is citizens that are not familiar with the rail system or backpackers that comes from foreign countries. The purpose of developing such application is to overcome the problem faced by the commuters when travelling using the current rail system. There is a lack of integration between the existing rail systems, although some route planner application is available in the market, but they are not intensive enough and does not offer the required information to the user. This project aims to deliver an application that will provide correct transit guidance for the commuters. Other than that, the application would be able to provide all necessary transit information such as fare, estimated travel time, station information, nearby attractions and service status to the commuter. The project is executed by adhering to the best practice of Software Engineering and Software Project Management. Each phase of the project is executed in sequence and documented clearly.
viii TABLE OF CONTENTS DECLARATION ii APPROVAL FOR SUBMISSION iii ACKNOWLEDGEMENTS vi ABSTRACT vii TABLE OF CONTENTS viii LIST OF TABLES xiii LIST OF FIGURES xiv LIST OF SYMBOLS / ABBREVIATIONS LIST OF APPENDICES xviii xix CHAPTER 1 2 INTRODUCTION 1 1.1 1 Klang Valley 1.1.1 Klang Valley Current Rail Transportation System 2 1.1.2 Klang Valley Rail Expansion 3 1.1.3 Klang Valley Future Integrated Rail Map 5 1.2 Problem Statement 6 1.3 Project Objectives 7 1.3.1 General Objectives 7 1.3.2 Specific Objectives 7 1.4 Project Scope 8 1.5 Technology Used 9 LITERATURE REVIEW 10
ix 2.1 Global Smartphones Market 10 2.2 Mobile Operating System 11 2.2.1 13 2.3 2.4 2.5 Android vs iOS Development Cost Development Method 14 2.3.1 Native Application 15 2.3.2 Web Application 15 2.3.3 Hybrid Application 16 2.3.4 Comparison between Native, Web and Hybrid Application 17 Existing Application In The Market 18 2.4.1 KL Transport Planner 18 2.4.2 KL Transit Planner 20 2.4.3 Metromy 21 2.4.4 Hong Kong MTR Mobile 22 Shortest Path Problem in Graph Theory 23 2.5.1 Breadth First Search 25 2.5.2 Dijkstra Algorithm 26 2.5.3 Comparison between Breadth First Search & Dijkstra Algorithm 3 4 27 METHODOLOGY 29 3.1 Evaluation of Development Methodology 29 3.1.1 Spiral Model 29 3.1.2 Prototyping Model 31 3.1.3 Rapid Application Development (RAD) 32 3.1.4 Adopted Project Development Methodology 34 3.2 Development Tools 35 3.3 Project Plan 36 3.3.1 Work Breakdown Structure 36 3.3.2 Gantt Chart 37 PROJECT SPECIFICATION 39 4.1 39 Requirements Gathering & Analysis
x 4.2 5 4.1.1 Outcome of Study of Existing System 40 4.1.2 Outcome of Document Analysis 41 Feasibility Study 42 4.2.1 Economic Feasibility 42 4.2.2 Technical Feasibility 43 4.2.3 Schedule Feasibility 43 4.2.4 Operational Feasibility 43 4.3 Functional Requirements 44 4.4 Non Functional Requirements 46 SYSTEM DESIGN 47 5.1 Entity Relationship Diagram 47 5.1.1 ER Diagram 1 (Route Calculation) 47 5.1.2 ER Diagram 2 (Android Application) 48 5.2 Data Dictionary 49 5.2.1 Data Dictionary for ER Diagram 1 49 5.2.2 Data Dictionary for ER Diagram 2 50 5.3 Use Case Diagram 52 5.4 Class Diagram 53 5.4.1 Class Diagram 1 (Route Calculation) 53 5.4.2 Class Diagram 2 (Android Application) 54 5.5 Activity Diagram 55 5.5.1 Route Planner 55 5.5.2 Service Status 56 5.5.3 Nearby Attractions 57 5.5.4 Saved Route 57 5.5.5 Saving Favourite Route 58 5.5.6 Share Route 58 5.6 Deployment Diagram 59 5.7 Overall System Architecture 59 5.8 User Interface Design 60 5.8.1 Main Page 60 5.8.2 Route Planner 61
xi 6 Route Result 61 5.8.4 Service Status 62 5.8.5 Service Status Details 63 5.8.6 Station Information 63 5.8.7 Nearby Attractions 64 5.8.8 Nearby Attraction Details 64 5.8.9 Saved Route 65 IMPLEMENTATION & TESTING 66 6.1 Implementation of Application 66 6.1.1 Route Calculation Module 66 6.1.2 Route Planner Module 68 6.1.3 Live Service Status Module 71 6.1.4 Route Saving & Sharing Module 72 6.1.5 Fare Display Module 74 6.1.6 Station Information & Nearby Attractions Module 75 6.2 6.3 6.4 7 5.8.3 Unit Testing 78 6.2.2 Main Screen 79 6.2.3 Route Planner Module 80 6.2.4 Service Status Module 81 6.2.5 Station Information & Nearby Attractions Module 82 6.2.6 Saved Route Module 82 Integration Testing 83 6.3.1 83 Test Cases System Testing 98 6.4.1 Testing Equipment Specification 98 6.4.2 Test Cases 99 CONCLUSION & RECOMMENDATION 103 7.1 Contribution of the Application 103 7.2 Limitations of Application 104 7.3 Future Enhancement 104 7.4 Conclusion 104
xii REFERENCES 106 APPENDICES 109
xiii LIST OF TABLES TABLE 1.1 TITLE PAGE Current Active & Serving Rail Line in Klang Valley 2 1.2 Current Active & Confirmed Rail Lines 3 2.1 Major Mobile Operating Systems in the World 11 2.2 Android vs iOS Development Cost 13 2.3 Most Famous Cross-platform IDE 16 2.4 Comparison Method between Different Development 17 2.5 Comparison Between BFS & Dijkstra Algorithm 27 4.1 Functions of various rail planner application. 40 4.2 Rail Lines and Average Train Frequency 41 4.3 Speed of train vs Station Distance. 41 5.1 Description for ER Diagram 2. 48
xiv LIST OF FIGURES FIGURE TITLE PAGE 1.1 Klang Valley Local Authorities & Map 1 1.2 Integrated Rail Map For Klang Valley (SPAD, 2012) 5 RapidKL Portal vs Existing Route Planner Application 6 1.3 2.1 Smartphones vs (Neilson, 2012) Feature Phones Penetration 10 2.2 Smartphone Growth Forecast (IDC, 2012) 11 2.3 Mobile Operating System Market Share on Q2 2011 and Q2 2012 (IDC, 2012) 12 2.4 Mobile Operating System Forecast (Gartner, 2011) 12 2.5 Hybrid Application Architecture 16 2.6 Screenshot of KL Transport Planner 18 2.7 Screenshot of KL Transit Planner 20 2.8 Screenshot of Metromy 21 2.9 Screenshot of Hong Kong MTR Mobile 22 2.10 Nodes and Edges of a Graph 24 2.11 Different Type of Graph 24 2.12 Breadth First Search Pseudo Code 25 2.13 Dijkstra Algorithm Pseudo Code 27 3.1 Spiral Development Model 29
xv 3.2 Prototyping Model 31 3.3 Rapid Application Development 33 3.4 Modules of the Project. 34 3.5 WBS Chart 36 3.6 Tasks Breakdown for Gantt Chart 37 3.7 Gantt Chart 38 5.1 ER Diagram for Route Calculation. 47 5.2 ER Diagram for Android Application. 48 5.3 Use Case Diagram 52 5.4 Class Diagram for Route Calculation. 53 5.5 Class Diagram for Android Application. 54 5.6 Activity Diagram for Route Planner. 55 5.7 Activity Diagram for Service Status. 56 5.8 Activity Diagram for Station Information. 56 5.9 Activity Diagram for Nearby Attractions. 57 5.10 Activity Diagram for Saved Route. 57 5.11 Activity Diagram for Saving Favourite Route. 58 5.12 Activity Diagram for Share Route. 58 5.13 Deployment Diagram for the Project. 59 5.14 Overall System Architecture of Project. 59 5.15 UI Design for Main Page. 60 5.16 UI Design for Route Planner. 61 5.17 UI Design for Route Result. 62 5.18 UI Design for Service Status. 62 5.19 UI Design for Service Status Details. 63
xvi 5.20 UI Design for Station Information. 63 5.21 UI Design for Nearby Attractions. 64 5.22 UI Design for Nearby Attraction Details. 64 5.23 UI Design for Saved Route. 65 6.1 Structure for edge table. 67 6.2 Section of Code for Adding Transfer Time. 67 6.3 CSV Structure of Pre-calculated Route Data. 68 6.4 Structure of routedata table. 68 6.5 Screenshot of Route Planner Interface. 69 6.6 Screenshot of Map Highlight & Sub Menu. 69 6.7 Section of Code for JavaScript Interface. 70 6.8 Screenshot of Route Result Interface. 70 6.9 Section of Code to Grab XML From Web Server. 71 6.10 Screenshot of Service Status Interface. 72 6.11 Structure of savedroute table. 72 6.12 Screenshot of Saved Route Interface. 73 6.13 Section of Code for Share Text. 73 6.14 Section of Code for Starting New Share Intent. 73 6.15 Screenshot of Share Button. 74 6.16 Screenshot of Share Action Provider & SMS Received. 74 6.17 RapidKL Fare Table. 75 6.18 Screenshot of Fare Display. 75 6.19 Structure of stationinfo table. 76 6.20 Screenshot of Station Information Interface. 76 6.21 Structure of stationattractions table. 76
xvii 6.22 Nearby Attractions List Interface. 77 6.23 Screenshot of Nearby Attraction Details Interface. 77
xviii LIST OF SYMBOLS / ABBREVIATIONS GPS Global Positioning System HTTP Hypertext Transfer Protocol IDC International Data Corporation KL Kuala Lumpur OS Operating System PHP Hypertext Preprocessor UI User Interface XML Extensible Mark Up Language
xix LIST OF APPENDICES APPENDIX A TITLE User Manual PAGE 109
1 CHAPTER 1 1 INTRODUCTION 1.1 Klang Valley Klang Valley is a rapid growing metropolitan area made up by Kuala Lumpur and several adjoining cities and towns in the state of Selangor. Although no official boundaries are drawn, but it is understood that Klang Valley is an area of approximately 2793km2 and comprised of 10 municipalities, each with own local authorities. Figure 1.1: Klang Valley Local Authorities & Map Klang Valley is the most important economic, political, education and cultural center for Malaysia and is home to approximately 7.2 million people (The
2 Star, 2013). In December 2010, Prime Minister Dato’ Seri Najib Tun Razak announced the development blueprint for Greater Klang Valley that aims to transform Klang Valley into top 20 most liveable city in the world and top 20 in economic growth. 1.1.1 Klang Valley Current Rail Transportation System For a metropolitan with dense population, there must be an effective public transportation system to mobilize millions of commuters from their home to workplace and vice versa. The survival and economic progress of a metropolitan like Klang Valley is tightly coupled to a complex mechanism of public transport that keeps the city functioning at normal pace each day. A glitch on the system will cause a tremendous financial impact. To date, Klang Valley has 8 dedicated rail lines running in parallel to serve the citizens. Table 1.1: Current Active & Serving Rail Line in Klang Valley Active & Serving Line Operator Number of Line Stations Kelana Jaya 23 Sentul Timur – Sri Petaling 18 Sentul Timur – Ampang 18 KL Monorail 11 KTM Batu Caves – Port Klang 27 KTM Tanjung Malim – Sungai 30 Gadut KLIA Ekspres 2 KLIA Transit 5 Total 134
3 1.1.2 Klang Valley Rail Expansion In conjunction to realize the vision of Greater Klang Valley, the government launched the Klang Valley MRT Project which aims to add 3 MRT lines into the current rail transport landscape. In December 2010, the government approved the first 51KM MRT line which span from Sungai Buloh to Kajang with a total of 31 stations (MRTCorp, n.d.). The construction of the first MRT line was officially launched on 8th July 2011 and is expected to be complete on year 2017. Details of the other 2 lines are currently under studies and will be implemented soon. Other than that, works on extending existing Kelana Jaya line and Sentul Timur – Sri Petaling line is on-going and is expected to complete in year 2014 (RapidKL, n.d.). Table 1.2: Current Active & Confirmed Rail Lines Active & Confirmed Future Line Operator Line No. of Stations Status 23 Stations Active Kelana Jaya 23 13 13 Under Construction 18 Stations Sentul Timur – Sri Petaling Active 18 13 13 Under Construction Sentul Timur – Ampang 18 All Active KL Monorail 11 All Active 27 All Active 30 All Active KLIA Ekspres 2 All Active KLIA Transit 5 All Active Sungai Buloh – Kajang 31 Under KTM Batu Caves – Port Klang KTM Tanjung Malim – Sungai Gadut
4 Construction MRT Line 2 22 Planning MRT Line 3 24 Planning
5 1.1.3 Klang Valley Future Integrated Rail Map Figure 1.2: Integrated Rail Map For Klang Valley (SPAD, 2012)
6 1.2 Problem Statement Despite the growing sophistication of rail network in Klang Valley. It lacks an effective mechanism to convey information about various rail routes to the commuters. Travelling from point A to point B by using rail is a dilemma especially for those who are not familiar with the system. When confirmed rail expansion is completed by year 2017, the total number of interchange node would be up to 17 and at that point of time, even the most frequent user of rail service would not be able to memorize all the interchange. Existing route planner is available in market, but they are not comprehensive enough because they are riding on the existing web service provided by RapidKL and only display routes operated by RapidKL without integration with other rail operators. Other than that, the User Interface of existing mobile applications is poorly designed and not user friendly. Thus, Klang Valley is in dire to have an effective route planner for its growing sophisticated rail system. Such application would not only effectively solve the above mentioned problem, but in addition, to promote and encourage the use of rail system. The idea to develop such application on mobile platform is due to the fact that smartphones are getting more common in Malaysia and the application can be easily accessed by users without the need of having an active data connection (except for Live Service Updates). Figure 1.3: RapidKL Portal vs Existing Route Planner Application
7 1.3 Project Objectives 1.3.1 General Objectives 1. To promote integration between all the rail lines with different operators and provide a common platform that contains information for all the different rail lines. 2. To provide an effective application to assist user to navigate through the complex rail network of Klang Valley and encourages the use of rail system by reducing the uncertainty faced by commuters when utilizing the system. 1.3.2 Specific Objectives 1. To develop a Mobile Based Rail Planning application that integrates all the confirmed rail lines in Klang Valley. 2. To provide a dedicated mobile based rail route planner without the need of having an active data connection (except Live Service Status). 3. To provide accurate transit guidance for commuters to reach their destination seamlessly. 4. To assist commuters on available route options so that they can plan their journey in advance. 5. To provide live service status to commuters so that they can opt for alternative route if glitches happen on their travelled route.
8 1.4 Project Scope The project aims to deliver a mobile based transit planner that includes Route Planner o Able to display correct routes from Point A to Point B. Latest Klang Valley Rail Route Map o Zoom-able Rail Route Map which includes Sg Buloh – Kajang MRT and KJ & SP Line extension. Dedicated UI for Mobile based environment o User friendly UI by adhering to Android UI Guidelines Savable & Sharable Routes via Email/SMS. o Route result can be saved for future use. Route can be shared with friends/families via Email/SMS. Travel Fare o Shows the correct fare payable from origin to destination. Live Service Status o Shows the live operating service status from all the rail lines. Estimated Travel Time o Algorithm to estimate transit time from origin to destination. Station Information o To display station operating time, facilities available and nearby attractions.
9 1.5 Technology Used Development Tools i. Android SDK ii. Apache Web Server iii. SQLite Database Programming Language Used i. Java ii. Java Script iii. HTML
10 CHAPTER 2 2 LITERATURE REVIEW 2.1 Global Smartphones Market Starting from year 2010, the world is experiencing a “Smartphone Boom” (Deutsche Welle, 2012) whereby smartphones are registering a strong growth compared to feature phone. According to research by a renowned global information and measurement firm Nielsen, smartphones penetration is growing steeply while sales of conventional phone ditches. In year 2013, the percentage of people owning smartphones are set to exceed feature phone. Figure 2.1: Smartphones vs Feature Phones Penetration (Neilson, 2012) Although Malaysia smartphones penetration rate (27% as of Q1 2012) is not as high as those in US (ITU, 2012), but studies by Nielsen has shown that smartphones market for Malaysia in year 2013 is very positive and is expected to
11 expand further. Analysis from International Data Corporation’s (IDC) forecasted that smartphones growth will remain strong until year 2017. Figure 2.2: Smartphone Growth Forecast (IDC, 2012) 2.2 Mobile Operating System One of the main selling points of a smartphones other than specification is its mobile operating system. Mobile operating system allows application to be developed under its platform to introduce additional functions. Currently there are 5 major mobile OS player in the world. Table 2.1: Major Mobile Operating Systems in the World OS Name OS Developer Latest Version Licence Development Android Google 6.1.3 Open Source Active iOS Apple 4.2.2 Closed Source Active Windows Phone Windows 8 Closed Source Active Blackberry RIM (Research In Motion) 7.1.0.649 Closed Source Active Symbian Nokia 10.1 Open Source Ceased (2011)
12 According to studies by IDC, the world mobile operating system is currently dominated by Android and iOS which makes up a total of 84.90% out of the market share. Android is the most popular operating system which constitutes 68% of market share in Q2 2012. Comparison with data from Q2 2011 shown that Android registered the strongest market share growth of 21.2% while other operating system shows decline except Windows Phone. Figure 2.3: Mobile Operating System Market Share on Q2 2011 and Q2 2012 (IDC, 2012) Research from renowned IT firm Gartner forecasted that Android future growth and outlook will remain strong and positive for many years to come. Figure 2.4: Mobile Operating System Forecast (Gartner, 2011)
13 2.2.1 Android vs iOS Development Cost Development cost is a great concern for programmers and companies when deciding on development platform. Platform with lower development cost is often preferred due to lower start-up capital. Android and iOS are the most famous mobile operating system in the world. The comparison of development cost between both of them is drawn on the table below. Table 2.2: Android vs iOS Development Cost Android iOS Developer Google Apple SDK Eclipse XCode SDK Platform Any MAC OS Only Language Java Objective C Any Smartphones & Tablets Only Apple Products RM75 One Time RM297 / Year Revenue Sharing 70:30 70:30 Application Store Google Play Apple Store Runs on Developer Fees *Based on conversion rate of 1 USD to 3 MYR. Based on the comparison of the both, Android is preferred due to lower development cost. Programmers can start developing Android applications simply by downloading the SDK from Google website which bundles all the required libraries and tools. Other than that, Android SDK is platform friendly and is able to run smoothly on a wide range of operating systems. Whereas to develop iOS application, a Mac machine is needed because XCode can only run in MAC OS environment, this will incur additional cost to purchase a Mac machine which costs up to RM3500 per unit. Application publication fees for Android are also cheaper because only a oneoff payment of RM75 is collected and developers can start publishing their applications to Google Play. Meanwhile to develop on iOS platform, developers need to pay RM297 each year to publish their application to Apple Store.
14 2.3 Development Method There are 3 ways of developing and delivering functionalities to smartphones each with cons and pros. Selection of development method between native application, web application and hybrid application is very subjective and depends greatly on a few constraints such as: Development Cost o The lowest investment over return ratio. Application Complexity o A quick application that only performs basic retrieving of data or complex application that performs complicated computations. Performance o Fast access needed or latency can be tolerated? User Interface Complexity o Rich user interface or simple? Available Human Capital o Man power available for development work and technical knowledge. Connectivity o Application needs constant connectivity or offline?
15 2.3.1 Native Application Application is built and installed on a specific platform. To support both Android and iOS, two set of codes need to be written using the standard SDK provided by each vendor, thus leading to higher development cost (Ngu and Do, 2012). Native application developed using Android SDK cannot be ported or installed on iOS. The user interface of native application is powered by the native graphic rendering libraries which are optimally designed for the particular platform. This ensures a smooth rendering of 2D and 3D graphics. Other than that, the code written using native libraries are all optimized & compiled for the platform, thus processing efficiency and performance is guaranteed. A more diversified application can be created using native approach due to the full privilege granted for hardware access. Application can be more creative by introducing different combinations of available hardware such as GPS, Gyroscopes, Compass and etc. 2.3.2 Web Application Web application must be accessed via web browser. Nothing will be installed on the device so an active data connection is needed. Web application can be written using any language (C#, Java, PHP, etc.) and can be displayed on different mobile operating system without rewriting the codes. The high portability reduces development cost. The user interface for web application is designed using HTML & Javascript thus web application cannot handle extensive 3D graphic processing (Ngu and Do, 2012). The performance of web application is slow and is greatly dependent on the connection speed. Web application has no access to application store thus programmers and companies can only advertise their application via websites. Other than that, web application often has limited functionalities due to the lack of access to device hardware. Only minimal hardware access is granted to web application such as GPS.
16 2.3.3 Hybrid Application Offer the best elements from native and web application. One set of code is written using cross-platform tools and can be deployed into different mobile platform with minimal changes and so development cost is lower compared to native application. Some of the most famous open-sourced cross-platform development tools are shown in the table below. Table 2.3: Most Famous Cross-platform IDE IDE PhoneGap Appcelerator Titanium Rhodes MoSync Development Language Developer HTML5, Javascript, CSS Nitobi Software HTML5, Javascript Appcelerator Inc HTML5, Javascript, Ruby Motorola C/C , Javascript, HTML, CSS MoSyncAB Hybrid application is basically a native app with embedded HTML codes. HTML and Javascript are used to display the user interface, thus hybrid application cannot render 3D graphics smoothly. Hybrid applications are typically slower than native application because the codes are not optimized (Charland and LeRoux, 2011). Although hybrid application enjoys access to device hardware, but it is limited and the supported API is different across developers. The architecture of hybrid application using PhoneGap is shown in the figure below. Figure 2.5: Hybrid Application Architecture
17 2.3.4 Comparison between Native, Web and Hybrid Application The table below shows the pros and cons of native, web and hybrid application. Table 2.4: Comparison between Different Development Method Native Web Hybrid User Interface Native Graphic Rendering API HTML5 & Javascript HTML5 & Javascript Performance Fast Slow Slow Portability Low High High Application Store Website Application Store High Low Moderate Offline / Online Online Offline / Online Highest Low Moderate Distribution Device Hardware Access Connectivity Development Cost After evaluating 3 different development methods, native application development is still preferred for the implementation of this project over web application and hybrid application. The main evaluation criterion is the concern on performance. Complex data type and computations will be performed to find the shortest possible route between origin and destination, thus performance of the application is very important. Web application and hybrid application are slow in performance, thus more time will need to be taken to compute the shortest route and this will give a bad user experience to the customer. The core functionalities of this project such as route planner is designed to be available offline after considering the fact that not every smartphone users subscribe to a data plan and a quality data connection is not always guaranteed especially when travelling underground using the rail system. So the application is not suitable to be implemented as web application because web application needs a consistent and stable data connection. Although hybrid application can work in offline state, but the lack of established standard over hybrid development platform is refraining user from using it (Singh and Palmieri, 2012).
18 2.4 Existing Application In The Market Currently there are 3 Android based route planning for Malaysia rail transportation is available in the market. All the application will be studied, analysed and compared based on the functions that will be delivered under the current project scope. Other than that, 2 overseas route planning application will be analysed too to act as a benchmark for the project. 2.4.1 KL Transport Planner The user interface for the application is bad because the interface does not scale well with the device screen. Besides that, the shortcut icons provided at the bottom of application lacks description and is not informative. The figure below shows the main screen of the application. Figure 2.6: Screenshot of KL Transport Planner
19 This application provides the following function, Route Planner Although there is a route planner function in the application, but the route planner is relying on RapidKL website as the backend and an active data connection is needed to compute the route. The main problem with RapidKL route planner is that it lacks integration to other rail operators. The route planner is only able to compute the route for the 4 rail lines (KL Monorail, Kelana Jaya Line, Ampang Line and Sri Petaling Line) serving under the company. Other rail line such as KTM Komuter & ERL is not included in the rail planner. Rail Route Map The application does provide a zoom-able rail route map for Klang Valley. Savable & Sharable Route The route result can be saved for future reference. It can be shared to other application that supports JPEG uploading. Fare Display This application can show the correct fare needed for travel. Live Service Status This application can show live service status, but it is not properly formatted. Service status from other rail operators such as KTM is harvested using Twitter. Thus some useless information such as re-tweets and morning greetings are also extracted which will cause confusions to user. The following functions are not supported in the application. Estimated Travel Time Station Information
20 2.4.2 KL Transit Planner The user interface of this application is considered good due to the simplicity of the application. The main screen of the application is shown in the figure below. Figure 2.7: Screenshot of KL Transit Planner This application provides the following function, Route Planner This application provides a route planner, but it is riding on RapidKL web service as the backend. As discussed earlier, RapidKL route planner lacks integration to other rail operators. Fare Display This application can show the correct fare needed for travel. The following functions are not supported in the application. Rail Route Map Savabe & Sharable Route Estimated Arri
6.1.1 Route Calculation Module 66 6.1.2 Route Planner Module 68 6.1.3 Live Service Status Module 71 6.1.4 Route Saving & Sharing Module 72 6.1.5 Fare Display Module 74 6.1.6 Station Information & Nearby Attractions Module75 6.2 Unit Testing 78 6.2.2 Main Screen 79 6.2.3 Route Planner Module 80 6.2.4 Service Status Module 81
the Route Planner application. It is designed to help the user quickly learn about the application and its features, as well as share tips to help the user use Route Planner to its fullest potential. This Guide will instruct how to do the following: 1. Login to Route Planner 2. Navigate Route Planner 3. Locate a Stop 4.
the Route Planner application. It is designed to help the user quickly learn about the application and its features, as well as share tips to help the user use Route Planner to its fullest potential. This Guide will instruct how to do the following: 1. Login to Route Planner 2. Navigate Route Planner 3. Locate a Stop 4.
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Descartes WinRoute , Descartes Route Planner On-demand , Descartes Route Planner and Descartes Route Planner RS Be flexible, scalable and elastic Be self hosted or hosted by Descartes New User Interface for Routing and Scheduling Plug in model for optimization issues (use benefits of our multiple optimization engines)
The Behavioral Medicine Treatment Planner The Group Therapy Treatment Planner The Gay and Lesbian Psychotherapy Treatment Planner . Psychotherapy Treatment Planner, 3rd Edition, The Child Psychotherapy Treatment Planner, 3rd Edition, and. The Addiction Treatment Planner, 2nd Edition.
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
READING COMPREHENSION PRACTICE EXAM. GENERAL INSTRUCTIONS: You will have 90 minutes for this test. Work rapidly but carefully. Do no spend too much time on any one question. If you have time after you have finished the test, go back to the questions you have left unanswered. The three parts of this test are English Usage, Sentence Correction, and Reading Comprehension. When you have finished .
