1. SnapValet ARB Team 03 1

2. SnapValet ARB Team Evaluation Molly Karcher 2

3. Strengths and Weaknesses: Operational View Strengths All members are friendly, collaborative, and punctual in regards to deadlines Quick and decisive in task delegation; good sense of communal responsibility Use of online collaboration tools (Google groups, Bugzilla, Winbook, Facebook messages, etc. Weaknesses Deliverables generated very close to deadlines, leaves minimal time for verification Lack of availability of remote team member during normal workday hours 3

4. Strengths and Weaknesses: Technical View Strengths All computer science Masters students; ability to quickly and effectively learn new technologies Collectively, strong familiarity with MySQL and relational databases Collectively, strong familiarity with Java, so learning Android shouldn’t be that painful Weaknesses Lack of mobile development experience (on both iOS and Android platforms) Lack of familiarity with transaction management tools/APIs There remain a lot of uncertainties in technical requirements 4

5. WinWin Conditions AgreePotentiallyOpen Admin Interface WC_3383 WC_3385 WC_3387 WC_3391 Advertisements WC_3210 Geolocation CheckinWC_3203 Mobile TransactionsWC_3392WC_3204 Notifications WC_3384, WC_3390WC_3205 Profile ManagementWC_3208 QR Code Reader WC_3215 5

6. SnapValet ARB Operations Concept Description Abhinandan Patni 6

7. Outline System Purpose Shared Vision Proposed System Benefits Chain Diagram System Boundary Desired Capabilities and Goals 7

8. System Purpose To enable cashless transactions for valet parking payment. To increase the speed of the valet pick-up service. To improve the valet experience of customers. To facilitate better transaction and account management for valet companies. 8

9. Shared Vision 9

10. Proposed System – Entity Relationship Diagram 10

11. Proposed System – Business Workflow Diagram 11

12. Benefits Chain Diagram 12

13. System Boundaries 13

14. Desired Capabilities Mobile Payment Gateway (OC1) Car Pick-Up Request (OC2) Queue Look-Up (OC3) Ticket Number Details (OC4) Notifications (OC5) Admin Interface (OC6) Advertisements and Suggestions (OC7) Transaction Summary (OC8) 14

15. LEVELS OF SERVICE Response Time – Simple (Must Have) Availability (Should Have) Security (Must Have) Maintainability (Must Have) 15

16. Organizational and Operational Transformations Need for central tablet per valet parking area. Valet head for each position. Employee IDs a must. Update the list of restaurants serviced. Customers have to enter ticket numbers Valet heads are notified of requests on the tablet. Customers are notified on their smartphones by valet staff. Payment can be done via mobile transaction. 16

17. SnapValet ARB Prototype Brian Vanover 17

18. Outline SnapValet Intro Basalmiq Mockups Google Places API 18

19. Registration Valet employees will have a login autogenerated when employers add them via a web application Employees will use this login to register by providing the login along with the additional requested information. 19

20. Geolocation Check-in Both customers and valet employees will check in to locations using geolocation Locations will be suggested using the Google Places API Locations will be filtered based on a radial proximity and place type 20

21. Vehicle Request Following check-in, customers can request their vehicle by entering the number on the ticket that was given to them by the valet. This will generate a request that will be displayed in the valet queue following a prompt for payment 21

22. Payment Customers will have the option of paying cash or mobile. Payment will be verified before release of the vehicle 22

23. Valet Interface Request QueueShift Management 23

24. Google Places API http://greenbay.usc.edu/csci577/fall2014/projects/te am03/Valuation/PRO/geolocation_prototype.html Lat/Long plugged in for demonstrative purposes Venues limited to restaurants, nightclubs, shopping malls, movie theaters, lodging Radial/nearby parameters varied 24

25. SnapValet Requirements Ridhima Manjrekar 25

26. Outline Customers Valet Company Valet Operators System 26

27. Customers [WC_3208]Create and manage my SnapValet profile [WC_3205]Request for my car via the app [WC_3203]check into/select a location through my mobile phone so that the I can pay for my valet [WC_3392]either request or request and pay for valet so that I have the option to not enter in my credit card information if I don’t want to [WC_3215]enter my ticket number from the valet ticket so that I can request my car now/later. 27

28. Valet Company [WC_3204]offer an easier payment option- credit card [WC_3391]Use the system to maintain more reliable transactional data 28

29. Valet Operators [WC_3384]receive real-time requests from customers in an organized queue [WC_3387]have my own login and check-in location [WC_3386]see if a customer has paid or not in the queue so that I know whether to collect cash. [WC_3390]send notifications to the customer that their car is ready 29

30. System [WC_3213]The application shall be secure - channel is encrypted. (SSL). [WC_3216]The budget for the project shall not exceed $10,000 30

31. SnapValet ARB SSAD Ditong Ding 31

32. Outline System Context Artifacts & Information Behavior 32

33. System Context 33

34. Artifacts & Information 34

35. Behavior Valet Service Employee Management Account Management 35

36. Life Cycle Plan -Saikarthik Desiraju 36

37. Life Cycle Strategy ICSM and Architected Agile >One incremental commitment cycle >Weekly team meetings, Client meetings, Defect Tracking >Next Milestone: Development Commitment Review Foundations phase strategy: >Assess scope of the project >Develop necessary skills/tech >Elaborate software architecture >Identify COTs >Prototype modules 37

38. Stakeholder roles RoleTeam Member ClientMona A Project ManagerBrian Vanover Feasibility AnalystXiaoting Bi Operational Concept EngineerAbhinandan Patni IIV & V, Quality focal pointMolly Karcher Requirements EngineerRidhima Manjrekar Software ArchitectDitong Ding Life Cycle PlannerSaikarthik Desiraju Operational Concept Engineer, Developer New Team Member (CS577b) System MaintainerSnapValet employee 38

39. Stakeholder responsibilities & Project Plan 39

40. Stakeholder responsibilities & Project Plan 40

41. Stakeholder responsibilities & Project Plan 41

42. Stakeholder responsibilities & Project Plan 42

43. Stakeholder responsibilities & Project Plan 43

44. Resource Estimation 7 member team 2 semester project Total hours required ~1100hrs. Each member works for 16hrs/week for 10 weeks of development Number of modules :5 Programming Language : Java Total budget ~$10,000 44

45. Scale DriverValue PRECHigh (2.48) FLEXHigh (2.03) RESLLow (5.65) TEAM High (2.19) PMATLow (6.24) Scale Factors & Cost Drivers Cost DriverValue RELYNominal (1.00) DATAHigh (1.14) DOCUNominal (1.00) CPLXNominal (1.00) RUSEVery High (1.15) TIMENominal (1.00) STORNominal (1.00) PVOLLow (0.87) Cost DriverValue ACAPHigh (0.85) PCAPHigh(0.88) PCONNominal (1.00) APEXLow (1.10) LTEXLow (1.09) PLEXVery Low (1.19) TOOLVery High (0.78) SITEExtra High (0.80) SCEDNominal(1. 00) Profile Management & Login 45

46. COINCOMOII Estimate 46

47. Feasibility Evidence Description Xiaoting Bi 47

48. Business Case Analysis 48

49. Business Case Analysis Cost & Benefits 49

50. Personnel Costs 50

51. Hardware and Software Costs Personnel Costs (cont.) 51

52. Benefit Analysis For client: For users: 52

53. ROI Analysis 53

54. Risks 54

55. Risks (cont.) 55

56. Risks (cont.) 56

57. Process Feasibility 57

58. Process Feasibility (cont.) 58

59. 1.Persona : Gem Basic Demographic Age: 23 Hometown: Los Angeles Marital Status: Single Job: Student of USC Attributes She does not take change with her. User Scenario: She wanted to go to a restaurant but she’s not used to taking change with her. So she downloaded SnapValet and was able to pay by her credit card. Goals: No need to pay cash. Information Source: Advertisement 59

60. 2.Persona: Tom Basic Demographic Age: 27 Hometown: Los Angeles Marital Status: Single Job: Sales manager Attributes Impatient in waiting for a valet operator to pick his car back. User Scenario: He usually goes out for a dinner but he’s impatient in waiting a valet operator parking his car and picking his car back. Yesterday he went to a restaurant and it’s so busy. So he used SnapValet to request his car back before he went out waiting outside. Goals: He does not want to wait too long to pick his car back. Information Source: Advertisement 60

61. 3.Persona : Angela Basic Demographic Age: 42 Hometown: Los Angeles Marital Status: Single Job: Accountant Attributes Impatient in waiting for a valet operator to park her car and does not want to add her bank account in the app. User Scenario: She had to go to a restaurant to celebrate her friend’s birthday. But she still had a lot of work to do at night. So she use SnapValet to request her car back without waiting outside for a long time. As she didn’t want to add her bank account in the app, she paid by cash. Goals: She doesn’t need to wait too long for giving her car to a valet operator and pays by cash. Information Source: Friends 61

62. 4. Persona: Jerry Basic Demographic Age: 31 Hometown: Los Angeles Marital Status: Single Job: Valet operator of SM valet company Attributes Hardworking User Scenario: He is a valet operator of SM valet company. After parking a car for a user, he went to central device and found that a driver requesting his car, so he picked the car back and sent a notification to the user that the car was available. Goals: Higher salary and tips. 62

63. 5. Persona : Bob Basic Demographic Age: 40 Hometown: Los Angeles Marital Status: Married Job: Manager of SM Valet Company Attributes Decisive, trying to improve profit for company. User Scenario: He is a manager of SM valet company. As it’s inconvenient for users to pay cash, SM company decided to use SnapValet. Valet Operators are arranged to certain locations and valet service fee can be charged via credit card or cash. They provide two choices for users. Goals: Make more profits. 63

64. Quality Focal Point Molly Karcher 64

65. Traceability Matrix OCDRequirementsUse CaseTest Case OC-1 Mobile Payment GatewayWC_3204 UC-2 UC-4TBD OC-2 Car pick-up requestWC_3392 WC_3215UC-2TBD OC-3 Queue Look-up WC_3392 WC_3386 WC_3384 UC-1 UC-2TBD OC-4 Ticket Number DetailsWC_3215 UC-2 UC-4TBD OC-5 NotificationsWC_3390 WC_3205 UC-1 UC-2TBD OC-6 Admin Interfacing WC_3391 WC_3387 WC-3386 WC_3385 UC-1 UC-4 UC-5 UC-6 UC-7TBD OC-7 Transaction SummaryWC_3391UC-7TBD OC-8 Advertisements & SuggestionsWC_3210UC-2TDB 65

66. Current Defects All current confirmed defects will not need to be addressed until development stage Relevant non-component activities and deliverable defects are all resolved/verified. Stats: Total (40), Confirmed (6), Verified (34) 66

67. Defect Prevention & Identification Strategies Continuous reprioritization of defect list, integration into feature- development schedule, and assignment to correct team members IIV&V member responsibility, to be completed weekly or by team sprint- planning meeting Quality control through version control (Git) Informal code reviews through merge/pull requests Testing o Continuous integration + automated testing o Test-driven/test-first development strategy 67