SnapValet ARB - PowerPoint PPT Presentation

Loading...

PPT – SnapValet ARB PowerPoint presentation | free to download - id: 6d36eb-NTA5N



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

SnapValet ARB

Description:

SnapValet ARB Team 03 * Current Defects All current confirmed defects will not need to be addressed until development stage Relevant non-component activities and ... – PowerPoint PPT presentation

Number of Views:67
Avg rating:3.0/5.0
Slides: 68
Provided by: usc120
Learn more at: http://greenbay.usc.edu
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: SnapValet ARB


1
SnapValet ARB
  • Team 03

2
SnapValet ARB Team Evaluation
  • Molly Karcher

3
Strengths and Weaknesses Operational View
  • Strengths
  • Weaknesses
  • 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.
  • Deliverables generated very close to deadlines,
    leaves minimal time for verification
  • Lack of availability of remote team member during
    normal workday hours

4
Strengths and Weaknesses Technical View
  • Strengths
  • Weaknesses
  • 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 shouldnt be that painful
  • 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

5
WinWin Conditions
  Agree Potentially Open
Admin Interface     WC_3383 WC_3385 WC_3387 WC_3391
Advertisements     WC_3210
Geolocation Checkin WC_3203    
Mobile Transactions WC_3392 WC_3204  
Notifications WC_3384, WC_3390 WC_3205  
Profile Management WC_3208    
QR Code Reader     WC_3215
6
SnapValet ARB Operations Concept Description
  • Abhinandan Patni

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

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.

9
Shared Vision
10
Proposed System Entity Relationship Diagram
11
Proposed System Business Workflow Diagram
12
Benefits Chain Diagram
13
System Boundaries
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)

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

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.

17
SnapValet ARB Prototype
  • Brian Vanover

18
Outline
  • SnapValet Intro
  • Basalmiq Mockups
  • Google Places API

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.

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

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

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

23
Valet Interface
  • Request Queue
  • Shift Management

24
Google Places API
  • http//greenbay.usc.edu/csci577/fall2014/projects/
    team03/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

25
SnapValet Requirements
  • Ridhima Manjrekar

26
Outline
  • Customers
  • Valet Company
  • Valet Operators
  • System

27
Customers
  • WC_3208Create and manage my SnapValet profile
  • WC_3205Request for my car via the app
  • WC_3203check into/select a location through my
    mobile phone so that the I can pay for my valet
  • WC_3392either request or request and pay for
    valet so that I have the option to not enter in
    my credit card information if I dont want to
  • WC_3215enter my ticket number from the valet
    ticket so that I can request my car now/later.

28
Valet Company
  • WC_3204offer an easier payment option- credit
    card
  • WC_3391Use the system to maintain more reliable
    transactional data

29
Valet Operators
  • WC_3384receive real-time requests from
    customers in an organized queue
  • WC_3387have my own login and check-in location
  • WC_3386see if a customer has paid or not in the
    queue so that I know whether to collect cash.
  • WC_3390send notifications to the customer that
    their car is ready

30
System
  • WC_3213The application shall be secure -
    channel is encrypted. (SSL) .
  • WC_3216The budget for the project shall not
    exceed 10,000

31
SnapValet ARB SSAD
  • Ditong Ding

32
Outline
  • System Context
  • Artifacts Information
  • Behavior

33
System Context
34
Artifacts Information
35
Behavior
36
Life Cycle Plan
-Saikarthik Desiraju
37
Life Cycle Strategy
  • ICSM and Architected Agile
  • gtOne incremental commitment cycle
  • gtWeekly team meetings, Client
    meetings, Defect Tracking
  • gtNext Milestone Development
    Commitment Review
  • Foundations phase strategy
  • gtAssess scope of the project
  • gtDevelop necessary skills/tech
  • gtElaborate software architecture
  • gtIdentify COTs
  • gtPrototype modules

38
Stakeholder roles
Role Team Member
Client Mona A
Project Manager Brian Vanover
Feasibility Analyst Xiaoting Bi
Operational Concept Engineer Abhinandan Patni
IIV V , Quality focal point Molly Karcher
Requirements Engineer Ridhima Manjrekar
Software Architect Ditong Ding
Life Cycle Planner Saikarthik Desiraju
Operational Concept Engineer, Developer New Team Member (CS577b)
System Maintainer SnapValet employee
39
Stakeholder responsibilities Project Plan
40
Stakeholder responsibilities Project Plan
41
Stakeholder responsibilities Project Plan
42
Stakeholder responsibilities Project Plan
43
Stakeholder responsibilities Project Plan
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

45
Scale Factors Cost Drivers
Profile Management Login
Cost Driver Value
RELY Nominal (1.00)
DATA High (1.14)
DOCU Nominal (1.00)
CPLX Nominal (1.00)
RUSE Very High (1.15)
TIME Nominal (1.00)
STOR Nominal (1.00)
PVOL Low (0.87)
Cost Driver Value
ACAP High (0.85)
PCAP High(0.88)
PCON Nominal (1.00)
APEX Low (1.10)
LTEX Low (1.09)
PLEX Very Low (1.19)
TOOL Very High (0.78)
SITE Extra High (0.80)
SCED Nominal(1.00)
Scale Driver Value
PREC High (2.48)
FLEX High (2.03)
RESL Low (5.65)
TEAM High (2.19)
PMAT Low (6.24)
46
COINCOMOII Estimate
47
Feasibility Evidence Description
  • Xiaoting Bi

48
Business Case Analysis
49
Business Case Analysis
Cost Benefits
50
Personnel Costs
51
Personnel Costs (cont.)
Hardware and Software Costs
52
Benefit Analysis
For client
For users
53
ROI Analysis
54
Risks
55
Risks (cont.)
56
Risks (cont.)
57
Process Feasibility
58
Process Feasibility (cont.)
59
1.Persona Gem
Basic Demographic Age 23 Hometown Los
Angeles Marital Status Single Job Student of USC
User Scenario She wanted to go to a restaurant
but shes not used to taking change with her. So
she downloaded SnapValet and was able to pay by
her credit card.
Attributes She does not take change with her.
Information Source Advertisement
Goals No need to pay cash.
60
2.Persona Tom
Basic Demographic Age 27 Hometown Los
Angeles Marital Status Single Job Sales manager
User Scenario He usually goes out for a dinner
but hes impatient in waiting a valet operator
parking his car and picking his car back.
Yesterday he went to a restaurant and its so
busy. So he used SnapValet to request his car
back before he went out waiting outside.
Attributes Impatient in waiting for a
valet operator to pick his car back.
Information Source Advertisement
Goals He does not want to wait too long to pick
his car back.
61
3.Persona Angela
Basic Demographic Age 42 Hometown Los
Angeles Marital Status Single Job Accountant
User Scenario She had to go to a restaurant to
celebrate her friends 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 didnt want to
add her bank account in the app, she paid by cash.
Attributes Impatient in waiting for a
valet operator to park her car and does not want
to add her bank account in the app.
Information Source Friends
Goals She doesnt need to wait too long for
giving her car to a valet operator and pays by
cash.
62
4. Persona Jerry

Basic Demographic Age 31 Hometown Los
Angeles Marital Status Single Job Valet
operator of SM valet company
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.
Attributes Hardworking
Goals Higher salary and tips.
63
5. Persona Bob

Basic Demographic Age 40 Hometown Los
Angeles Marital Status Married Job Manager of
SM Valet Company
User Scenario He is a manager of SM valet
company. As its 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.
Attributes Decisive, trying to improve profit for
company.
Goals Make more profits.
64
Quality Focal Point
  • Molly Karcher

65
Traceability Matrix
OCD Requirements Use Case Test Case
OC-1 Mobile Payment Gateway WC_3204 UC-2 UC-4 TBD
OC-2 Car pick-up request WC_3392 WC_3215 UC-2 TBD
OC-3 Queue Look-up WC_3392 WC_3386 WC_3384 UC-1 UC-2 TBD
OC-4 Ticket Number Details WC_3215 UC-2 UC-4 TBD
OC-5 Notifications WC_3390 WC_3205 UC-1 UC-2 TBD
OC-6 Admin Interfacing WC_3391 WC_3387 WC-3386 WC_3385 UC-1 UC-4 UC-5 UC-6 UC-7 TBD
OC-7 Transaction Summary WC_3391 UC-7 TBD
OC-8 Advertisements Suggestions WC_3210 UC-2 TDB
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)

67
Defect Prevention Identification Strategies
  • Continuous reprioritization of defect list,
    integration into feature-development schedule,
    and assignment to correct team members
  • IIVV 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
  • Continuous integration automated testing
  • Test-driven/test-first development strategy
About PowerShow.com