Difference between revisions of "Finding, Reserving, and Paying for Parking"
Megankatsumi (talk | contribs) |
|||
| Line 25: | Line 25: | ||
3. The system may reject the payment and not reserve the space. | 3. The system may reject the payment and not reserve the space. | ||
|Information Requirements=Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered. | |Information Requirements=Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered. | ||
| − | |Required Classes= | + | |Required Classes=5087-1:Activity |
|References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020) | |References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020) | ||
|Specifications=Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model | |Specifications=Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model | ||
Revision as of 14:01, 14 December 2022
Domain
Smart Transportation
Summary
A traveller needs to find, reserve and pay for parking with fees applied to the traveller's account.
Description
A traveller is using a rental vehicle to reach a meeting at a remote site. Prior to starting the trip, the traveller wishes to find, reserve and pay for parking to maximize the efficiency of the journey. The traveller wishes to pay for parking as a part of the car hire charge. The meeting that the traveller attends goes longer than expected and the vehicle is parked for longer than the original reservation was made for.
Actors
Traveller, Parking Facility
Basic Flow of Events
1. Traveller enters their destination into the interface device with details about the parking needs.
2. System provides a list of parking places near the destination.
3. The traveller requests details for a selected parking place.
4. The system provides details for the selected parking place.
5. The traveller requests a reservation.
6. The system requests payment details.
7. The traveller provides payment information.
8. The system confirms payment and provides proof of reservation.
Flow Exceptions
1. A traveller may request details for multiple parking places but will typically select only one.
2. A traveller may escape from the flow of events at any time.
3. The system may reject the payment and not reserve the space.
Information Requirements
Destination location, parking place location, estimated arrival time at parking place, estimated departure time from parking place, parking place operating hours, existing relationships between the traveller and any parking service providers, rates for each parking place, space availability, services offered by the parking place, payment methods offered.
Required Classes
Required Object Properties
Required Data Properties
Issues
References
Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
License Information
License TBD
Specifications
Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model
Other Licensing Notes
Use case presented here is generalized but consistent with the APDS use case
Approval Status
Supplementary Figures
| Figure | Caption |
|---|---|
| Class Diagram for Find Parking Places Within a Radius |
