Prototype Report Version 3.0. Prototype Report. LADOT Scanning. Team 08. Name Primary Role Secondary Role

Transcription

1 Prototype Report LADOT Scanning Team 08 Name Primary Role Secondary Role Anirudh Govil Project Manager Life Cycle Planner Jeffrey Colvin Prototyper Systems and Software Architect Aditya Kumar Feasibility Analyst Project Manager Nisheeth Joshi Systems and Software Architect Life Cycle Planner Niraj Brahmkhatri Operational Concept Engineer Requirements Engineer Corey Painter IIV&V Shaper i

2 Version History Date Author Version Changes made Rationale 10/05/11 JC 1.0 Original template 10/07/11 JC 1.1 Updated Team Roles 10/14/11 JC /16/11 JC 2.1 Updated diagrams and descriptions Changed formatting Added additional prototype photos Updated team roles 10/23/11 JC 3.0 Updated diagrams to have no conditional components Broke down sections into our deliverables compared to future plans Initial draft for use with ICM EPG Template version 2.1 Team roles in v1.0 were incorrect Project specifications had changed since v1.1 Response to feedback on v1.1 by TA s (such as Navigation Flow being incorrect) New format is easier to follow Additional diagrams for further clarification Team roles were further updated on the team website Changes from the ARB session and project rescoping ii

3 Table of Contents PROTOTYPE REPORT VERSION HISTORY TABLE OF CONTENTS TABLE OF TABLES TABLE OF FIGURES I II III IV V 1 - INTRODUCTION PURPOSE OF THE PROTOTYPE REPORT STATUS OF THE PROTOTYPE NAVIGATION FLOW TRUCK NAVIGATION FLOW FUTURE CONSIDERATION COMPUTER NAVIGATION FLOW CHART 3 3 PROTOTYPE LOGIN SCREEN CALL LOG POPUP JOB PERFORM SCREEN FUTURE CONSIDERATION TASK ALLOCATOR SCREEN REPORT WINDOWS 9 iii

4 Table of Tables iv

5 Table of Figures Figure 1 - Truck Navigation Flow Chart 2 Figure 2 Computer User Navigation Flow Chart 3 Figure 3 - Login Screen 5 Figure 4 - Call Log Screen 6 Figure 5 - Job Perform Screen 7 Figure 6 - Task Allocator Screen 8 v

6 1 - Introduction Purpose of the prototype report The purpose of the prototype report is to outline the current system prototype and its changes from previous revisions as well as show how the prototype will meet project requirements Status of the prototype The second version of the prototype report has been changed to reflect the project as of our Win-Win negotiation sessions. This has more clearly specified what users will be able to do what things (such as the Task Allocator and the Department Manager), removing the ability to edit time-sheets (as this will be done in DTIME after the FLAT file has been generated). The version has also been updated to reflect the true nature of the Navigation Flow diagrams as form navigation flow as opposed to user operation flow. 1

7 2 - Navigation Flow Truck Navigation Flow Figure 1 - Truck Navigation Flow Chart The Truck Navigation Flow Chart (Figure 1), shows the navigation flow of the system in place on the LADOT field worker trucks. The truck s software will only be able to be accessed by a Field Worker. Once logged in, a field worker will be able to log calls they receive at the Call Log Screen. After they log jobs, they will be able to go to the Job Select Screen, which allows them to select which logged call they should perform. Once a job has been chosen to perform, the field worker will be able to log their job status at the Job Perform Screen. After logging the completion of the job, the user will be able to log more calls (if they have none available) or select a new job from their call list. 2

8 2.2 Future Consideration Computer Navigation Flow Chart Figure 2 Computer User Navigation Flow Chart The Computer User Navigation Flow Chart (Figure 2), show the navigation flow for user s on the computer. There are 3 types of users who can use the computer system: Field Employees, Department Supervisors and Task Allocators. Each user will be able to log in but are then directed to different pages Field Employees The the field employee, once logged on to the system, will be able to view their own maintanence reports and edit them if they require Department Supervisors 3

9 Department supervisors will be directed to a search screen. On the search screen, they will be able to perform 2 different searches: by location and by employee. The search by employee will only be visible if the Department Supervisor is given the permission to view that employee s reports. Both search result screens will show a table sorted chronologically (most recent completed first), with columns sortable by: time assigned, time started, time completed, job type and work order number. The Employee search will also have a sortable column by location and the Location search will have a sortable column by employee name Task Allocators Task allocators will be brought to a screen that shows them a map of the trucks currently active as well as the current jobs that need assigning. Additionally to the map, there will be 2 lists, one for trucks and one for jobs. When the task allocator selects either a truck or a job, they will be able to assign a task. When selecting a truck to assign a task to, the task allocator will be prompted to select at least one task to assign to the truck. When selecting a task, the task allocator will be prompted to select only one truck to assign the task to. The Task Selection screen will show either a map and list of trucks or tasks, depending on what the assignment is for. The map will show the location of the truck or the task being assigned, and the list will be sorted by distance. 4

10 3 Prototype 3.1 Login Screen Figure 3 - Login Screen Figure 3, Login Screen, denotes a simple log-in screen for the truck software. The page simply requires entering a user name and password. 5

11 3.2 Call Log Popup Figure 4 - Call Log Screen Throughout the program, field worker s may log their calls at the Log Job Call popup window. Figure 4 shows the Log Job Call popup on top of the perform job screen. The Log Job Call popup allows workers to log all pertinent information in regards to receiving a call about a specific job. When finished, pressing the Log Call button will log the call and return the field worker to their current screen. 6

12 3.3 Job Perform Screen Figure 5 - Job Perform Screen When actually doing a job, the field worker will be presented with the Job Perform Screen. Upon arriving, the user will push the Log Arrival button, which will time-stamp on the screen their arrival time. A similar action will be done upon completion and departure. The right side of the screen is designated to various problems that could have arisen while performing the job. These will be focused on with checkboxes, while an Other box appears at the base in case of any other notes need to be added. When the Log Departure button has been pressed, the job will be closed, and the next job will be selected or the user will be prompted to log more calls. 7

13 3.4 Future Consideration Task Allocator Screen Figure 6 - Task Allocator Screen The Task Allocator Screen is broken down into 3 main components: the map, the trucks list and the tasks list. Certain actions do not change the physical screen page, but instead just change the layout of the current page (with the screen shot being of the basic default page). When the task allocator selects a truck from either the truck list or the map, the truck list is hidden, the trucks on the map are all hidden (except for the truck being given an assignment). The task list is updated to also have the distance from the current location in a column. The task allocator can than either select multiple tasks from the map or the task list and click an assign button (not shown for clarity of base screen) to assign the tasks. 8

14 Similar functionality exists for the tasks except hiding the tasks items and showing the trucks from the above example Report Windows As there are multiple report windows, none have been drawn. Each of the report windows (the user maintanence screen, the manager location screen and the manager employee screen) contains a simple sortable table with appropriate headers. 9