Finding, Reserving, and Paying for Parking - Revision history

Megankatsumi: Text replacement - "iso5087-1:Agent" to "ISO5087-1:Agent"

2022-12-16T04:28:33Z

Text replacement - "iso5087-1:Agent" to "ISO5087-1:Agent"

← Older revision		Revision as of 04:28, 16 December 2022
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=ISO5087-1:Activity, ~~iso5087~~-1:Agent		\|Required Classes=ISO5087-1:Activity, ISO5087-1:Agent
	\|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

Megankatsumi: Text replacement - "=iso5087-1:Activity" to "=ISO5087-1:Activity"

2022-12-16T03:02:12Z

Text replacement - "=iso5087-1:Activity" to "=ISO5087-1:Activity"

← Older revision		Revision as of 03:02, 16 December 2022
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=~~iso5087~~-1:Activity, iso5087-1:Agent		\|Required Classes=ISO5087-1:Activity, iso5087-1:Agent
	\|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

Megankatsumi: Text replacement - "5087-1:Agent" to "iso5087-1:Agent"

2022-12-15T13:36:42Z

Text replacement - "5087-1:Agent" to "iso5087-1:Agent"

← Older revision		Revision as of 13:36, 15 December 2022
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=iso5087-1:Activity, ~~5087~~-1:Agent		\|Required Classes=iso5087-1:Activity, iso5087-1:Agent
	\|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

Megankatsumi: Text replacement - "5087-1:Activity" to "iso5087-1:Activity"

2022-12-15T13:30:55Z

Text replacement - "5087-1:Activity" to "iso5087-1:Activity"

← Older revision		Revision as of 13:30, 15 December 2022
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=~~5087~~-1:Activity, 5087-1:Agent		\|Required Classes=iso5087-1:Activity, 5087-1:Agent
	\|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

Megankatsumi at 14:01, 14 December 2022

2022-12-14T14:01:56Z

← Older revision		Revision as of 14:01, 14 December 2022
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=5087-1:Activity		\|Required Classes=5087-1:Activity, 5087-1:Agent
	\|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

Megankatsumi at 14:01, 14 December 2022

2022-12-14T14:01:30Z

← Older revision		Revision as of 14:01, 14 December 2022
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=~~Agent~~		\|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

KenVaughn at 21:52, 22 August 2022

2022-08-22T21:52:30Z

← Older revision		Revision as of 21:52, 22 August 2022
Line 27:		Line 27:
	\|Required Classes=Agent		\|Required Classes=Agent
	\|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=~~NewTestSpecifification1~~		\|Specifications=Specification:ISO 5206-1 ITS — Parking — Part 1: Core data model
	\|Scenario License=License TBD		\|Scenario License=License TBD
	\|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case		\|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case

KenVaughn at 21:22, 22 August 2022

2022-08-22T21:22:31Z

← Older revision		Revision as of 21:22, 22 August 2022
Line 4:		Line 4:
	\|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.		\|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		\|Actors=Traveller, Parking Facility
	\|Basic Flow of Events=Traveller enters destination into interface device with details about the parking needs		\|Basic Flow of Events=1. Traveller enters their destination into the interface device with details about the parking needs.
	System provides list of parking places near destination
	~~Traveller~~ requests details for a parking place		2. System provides a list of parking places near the destination.
	~~System~~ provides details for a parking place
	~~Traveller~~ requests a reservation		3. The traveller requests details for a selected parking place.
	~~System~~ requests payment details
	~~Traveller~~ provides payment information		4. The system provides details for the selected parking place.
	~~System~~ confirms payment and provides proof of reservation
	\|Flow Exceptions=A traveller may request details for multiple parking places but will typically select only one.		5. The traveller requests a reservation.
	A traveller may escape from the flow of events at any time.
	The system may reject the payment and not reserve the space.		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.		\|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=~~ProduceState~~		\|Required Classes=Agent
	\|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=NewTestSpecifification1		\|Specifications=NewTestSpecifification1

Xuanni1 at 03:14, 28 September 2021

2021-09-28T03:14:22Z

← Older revision		Revision as of 03:14, 28 September 2021
Line 25:		Line 25:
	{{Supplementary Figures		{{Supplementary Figures
	\|Figure Row={{Figure Row		\|Figure Row={{Figure Row
	\|Figure=Class Diagram for Find Parking Places Within a Radius.png,		\|Figure=Class Diagram for Find Parking Places Within a Radius.png
	\|Caption=Class Diagram for Find Parking Places Within a Radius		\|Caption=Class Diagram for Find Parking Places Within a Radius
	}}		}}
	}}		}}

KenVaughn: Created page with "{{Use Case |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..."

2021-07-05T16:00:02Z

Created page with "{{Use Case |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..."

New page

{{Use Case
|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=Traveller enters destination into interface device with details about the parking needs
System provides list of parking places near destination
Traveller requests details for a parking place
System provides details for a parking place
Traveller requests a reservation
System requests payment details
Traveller provides payment information
System confirms payment and provides proof of reservation
|Flow Exceptions=A traveller may request details for multiple parking places but will typically select only one.
A traveller may escape from the flow of events at any time.
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=ProduceState
|References=Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
|Specifications=NewTestSpecifification1
|Scenario License=License TBD
|Licensing Comments=Use case presented here is generalized but consistent with the APDS use case
|Use Case Status=Pending Approval
}}
{{Supplementary Figures
|Figure Row={{Figure Row
|Figure=Class Diagram for Find Parking Places Within a Radius.png,
|Caption=Class Diagram for Find Parking Places Within a Radius
}}
}}