Small amount of Cordova set up & coding for a demo app. must be completed today
Budget: $30 – $250 USD
i will supply full documentation for the task: but the actual work isnt much and is listed below:
Part 1)
A)
Suggest 5 functional requirement/obstacles for a demo taxi booking app.
B)
Add graphical user interface elements (that is, controls such as input fields and buttons) to the HTML page in order to support the expanded functional requirements above. It is up to you to select whicheverHTML elements you think are most relevant; you may reuse elements to fulfil different requirements. You should ensure that the elements are visible at all times. The interface should fit within a single screen without scrolling, but no CSS styling is required. You are not required to validate the input.
There are comments in the file telling where to put the code. leave the comments in place.
take a screenshot of the running app either on an Android device, theemulator, or running on Google Chrome browser.
Part 2
A
Use the skeleton project i will supply to implement the functional requirements FR1-3 below.
Note FR1.3 and FR3 are ALREADY IMPLEMENTED in the skeleton project.
FR1. The app shall offer, request and cancel taxi-sharing for an employee with a valid ACCOUNT ID. This functional requirement is further refined as follows:
FR1.1 Offering a taxi for a duration of availability with a pick-up address (the campus or train station),starting date, time and duration (in hours) for which the offering user is prepared to wait (using the taxi/orders API)
FR1.2 Requesting a taxi at a pick-up address for a specific date and time using the taxi/orders API
FR1.3 Cancelling all taxi orders by deleting all existing orders (offers and requests) associated with an ACCOUNT ID (using the taxi/orders API). ALREADY IMPLEMENTED
FR2. For an employee, the app shall show available matching taxi offers on a map. This functional requirement has been refined as follows:
FR2.1 The matching offers and requests should be found (using the matches API)
FR2.2 For each match the map location should be found (using the OpenStreetMap API) and then shown on the map.
FR3. Additional ACCOUNT ID can be registered on the system ALREADY IMPLEMENTED
API information is provided
Openstreet Rest API is provided for map
Part 1)
A)
Suggest 5 functional requirement/obstacles for a demo taxi booking app.
B)
Add graphical user interface elements (that is, controls such as input fields and buttons) to the HTML page in order to support the expanded functional requirements above. It is up to you to select whicheverHTML elements you think are most relevant; you may reuse elements to fulfil different requirements. You should ensure that the elements are visible at all times. The interface should fit within a single screen without scrolling, but no CSS styling is required. You are not required to validate the input.
There are comments in the file telling where to put the code. leave the comments in place.
take a screenshot of the running app either on an Android device, theemulator, or running on Google Chrome browser.
Part 2
A
Use the skeleton project i will supply to implement the functional requirements FR1-3 below.
Note FR1.3 and FR3 are ALREADY IMPLEMENTED in the skeleton project.
FR1. The app shall offer, request and cancel taxi-sharing for an employee with a valid ACCOUNT ID. This functional requirement is further refined as follows:
FR1.1 Offering a taxi for a duration of availability with a pick-up address (the campus or train station),starting date, time and duration (in hours) for which the offering user is prepared to wait (using the taxi/orders API)
FR1.2 Requesting a taxi at a pick-up address for a specific date and time using the taxi/orders API
FR1.3 Cancelling all taxi orders by deleting all existing orders (offers and requests) associated with an ACCOUNT ID (using the taxi/orders API). ALREADY IMPLEMENTED
FR2. For an employee, the app shall show available matching taxi offers on a map. This functional requirement has been refined as follows:
FR2.1 The matching offers and requests should be found (using the matches API)
FR2.2 For each match the map location should be found (using the OpenStreetMap API) and then shown on the map.
FR3. Additional ACCOUNT ID can be registered on the system ALREADY IMPLEMENTED
API information is provided
Openstreet Rest API is provided for map