Prototype Report. Tour Conductor. Team 5

Transcription

1 Prototype Report Tour Conductor Team 5 Team Members Ajay Kumar G C Manas Yadav Ankush H Prasad Aadithya B K Andrew Han Joseph Mouawad Roles Project Manager, Life Cycle Planner Feasibility Analyst, Prototyper/Builder System Architect, Project Manager Requirements Engineer, UML Modeler IIV&V, Quality Focal Point Operational Concept Engineer, Prototyper 10/18/15

2 Version History Date Author Version Changes made Rationale 10/12/15 BK, RR 1.0 Initial draft for ARB presentation 10/13/15 BK., RR 2.0 Populate the document with information relevant to Tour Conductor 11/28/15 BK 3.0 Populate the document with features created after the ARB session Initial draft Update based ARB feedback and FC package submission Showcasing new features in the system ii

3 Table of Contents Prototype Report...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures... v 1. Introduction Navigation Flow Prototype... 3 iii

4 Table of figures Figure 1: Navigation flow of Android application 1 Figure 2: Navigation flow of website 2 Figure 3: Textbox for user to enter a search string 3 Figure 4: User clicks on the marker to view information 4 Figure 5: GUI prototype of login screen 5 Figure 6: GUI prototype of create or edit tours page 6 Figure 7: User does not have navigation turned on. Notify user 7 Figure 8: User can search for a tour using either of the two options 8 Figure 9: User searches for a tour either using a keyword or current location 9 Figure 10: User selects a tour from the available list of tours 10 Figure 11: List of stops in a tour can be seen by swiping the screen from left to right direction 11 Figure 12: User wants to navigate through the tour 12 Figure 13: A fully functional landing page for the tour creator 13 Figure 14: User successfully logs in and can either create/edit/delete a tour 14 Figure 15: User wants to create a new tour 15 Figure 16: User wants to edit a previously created tour 16

5 Table of tables Table 1: Textbox for user to enter a search string 3 Table 2: User clicks on the marker to view information 4 Table 3: GUI prototype of login screen 5 Table 4: GUI prototype of create or edit tours page 6 Table 5: User does not have navigation turned on. Notify user 7 Table 6: User can search for a tour using either of the two options 8 Table 7: User searches for a tour either using a keyword or current location 9 Table 8: User selects a tour from the available list of tours 10 Table 9: List of stops in a tour can be seen by swiping the screen from left to right direction 11 Table 10: User wants to navigate through the tour 12 Table 11: A fully functional landing page for the tour creator 13 Table 12: User successfully logs in and can either create/edit/delete a tour 14 Table 13: User wants to create a new tour 15 Table 14: User wants to edit a previously created tour 16 v

6 1. Introduction 1.1. Purpose of the prototype Prototyping is an effective way to mitigate risk. Our prototype currently includes Graphical User Interface for the website, Algorithmic approach to solve a problem in the Android application as well as a PHP script acting as a server. These prototypes are developed so that we can give the client a fair idea of what the final product is going to look and feel like. Also, we can demonstrate our understanding to the client visually so that we can get a feedback that is clear and accurate. Prototype also serves as feasibility evidence. We gain knowledge about how difficult to implement a particular feature will be so that we can mitigate or solve this problem early. 1.2 Status of the prototype Building a prototype is one of the ways of mitigating risk. Our prototype can be divided into three sections Android: The Android prototype that we have designed is capable of accepting a search string from the user and send this to the server. The server would then search the database using this string and return all the information about that particular location back to the application. The application would receive the data and populate a marker window when it is clicked. Server: The server/back-end prototype is capable of receiving a request from the android application and search a pre-filled database schema for the search string. It would then encode the data into JSON and send it back to the application. GUI prototype for Tour creator s website: A rough GUI prototype of the website has been created and this will enable us to understand what kind of layout, the client is actually looking for. 1

7 2. Navigation Flow Figure 1: Navigation Flow of Android application Figure 2: Navigation flow of website 2

8 3. Prototype The following figures and tables show and discuss the purpose of each of the three prototype. Table 1: Text box for the user to enter a search string This figure shows a textbox where the user can enter the location he wants to search. The map would then show a marker at the specified location. This prototype will help us in completing CR 1 As a tour taker, I can search for tours by entering a location and CR 3 As a tour taker, I can click on a marker to view the information associated with that location User opens the android application. User can click on a marker to see the information related to that stop. Figure 3: Text box for the user to enter a search string 3

9 Table 2: User clicks on a marker to view information The user can click on a marker to see all the information associated with a location. It includes photos, description about the location, geographical coordinates and stop ID/name. CR 3 As a tour taker, I can click on a marker to see the information associated with that location User enters a string to search for tours or in this case, a location. User can acquire more information about a location by viewing the contents. Figure 4: User clicks on a marker to view information 4

10 Table 3: GUI prototype of login screen GUI prototype of the website. First page where the user needs to enter his username and password CR 6 As a tour creator, I can login to the website and create or edit tours. Tour creator has registered with the owner, wants to create/edit tours and opens the page. Tour creator can create or edit tours. Figure 5: GUI prototype of login screen 5

11 Table 4: User successfully logs in and wants to create or edit tours GUI prototype of the website. Tour creators enters this page after he successfully logs in and wants to create or edit tours. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. Tour creator has registered with the owner and has successfully logged in. Tour creator creates, edits or deletes tours. Figure 5: GUI prototype of creating/editing tours 6

12 Table 5: User does not have navigation turned on. Notify user Notify user when GPS is turned off. Notifying is important because current location is required for the application. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User opens the android application to take tours. GPS is turned on and the application works as expected. 7

13 Table 6: User can search for a tour using either of the two options Two options are presented to the user Search using a keyword or search by location. CR 1 As a tour taker, I can search for tours by entering text or current location. User opens the android application to take tours and GPS is turned on. User can search for tours using either option 8

14 Table 7: User searches for a tour either using a keyword or current location User searches for a tour either using a keyword or current location and sees the list of available tours. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User opens the android application to take tours and searches for tour using either of the option User can take any of the available tour 9

15 Table 8: User selects a tour from the available list of tours User searches for a tour either using a keyword or current location and selects a tour from the list of available tours CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User opens the android application to take tours and searches for tour using either of the option and selects a tour. User can tour a particular neighborhood 10

16 Table 9: List of stops in a tour can be seen by swiping the screen from left to right direction User can see all the stops in a tour and each stop s description and image by swiping the screen from left to right direction. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User has a selected tour from a list of available tours. User get s an overview of all the stops in a tour. 11

17 Table 10: User wants to navigate through the tour User wants to take the tour and decides to navigate. In-built google maps application is opened to aid the user with navigation CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User wants to navigate through a selected tour. User can go from one stop to another. 12

18 Table 11: A fully functional landing page for the tour creator Landing page is the site which will be first seen by a tour creator CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User/Tour creator wants to create a tour User can create a tour 13

19 Table 12: User successfully logs in and can either create/edit/delete a tour User logs in and can access all the features of the website CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User wants to create/edit/delete a tour User can create/edit/delete a tour by choosing the appropriate option 14

20 Table 13: User wants to create a new tour User has successfully logged in and now wants to create a tour of a particular neighborhood. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User has the correct credentials to log in. User has created a tour that can be viewed in the Android application 15

21 Table 14: User wants to edit a previously created tour User can edit a previously created tour; Edit may comprise of adding/deleting stops, editing information of a stop or deleting the entire tour. CR 2 As a tour creator, I can upload information about a tour. CR 5 As a tour creator, I can edit or delete tours. User has the credentials to log in. User can edit a tour in any manner he wants. 16