Edit Use Case Definition: Finding, Reserving, and Paying for Parking

You do not have permission to edit this page, for the following reason:

Domain:	Smart GovernmentSmart TransportationSmart EducationSmart HealthcareSmart HomeSmart Campus
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	ISO5087-1:Activity, ISO5087-1:Agent
	ContractDivisibleResourceDwellingUnitEmployeeEmploymentStatusEntityExceptionDayFacilityFamilyFeatureFirmFirstManifestationGeo:FeatureGeo:GeometryGeometryGoalHouseholdISO21972:IndicatorISO21972:RatioIndicatorISO5087-1:ActivityISO5087-1:AgentISO5087-1:AgreementISO5087-1:AllocationISO5087-1:AtomicAgreementISO5087-1:ComplexAgreementISO5087-1:ConjunctiveStateISO5087-1:ConsumeStateISO5087-1:DailyRecurringEventISO5087-1:DayOfWeekISO5087-1:DisjunctiveStateISO5087-2:AddressISO5087-2:AmendingBylawISO5087-2:BridgeISO5087-2:BridgeSegmentISO5087-2:BuildingISO5087-2:BuildingUnitISO5087-2:BusinessEstablishmentISO5087-2:BylawISO5087-2:CitizenshipISO5087-2:CityISO5087-2:CityDivisionISO5087-2:CityResidentISO5087-2:ClauseISO5087-2:ConditionPrecedentISO5087-2:ContractualCommitmentISO5087-2:ContractualDefinitionISO5087-2:ContractualElementISO5087-2:ControlledEntityISO5087-2:DefinitionInfrastructureElementInputInstantIntervalLandAreaMainBylawManifestationManifestationStateMonthMonthlyRecurringEventNonBindingTermNonDivisibleResourceNonTerminalStateOccupationOperatingHoursOrg:PostOrganizationOrganizationAgentOrganizationalUnitOutcomeOutputParking::PlaceHierarchy::HierarchyElementGeneralParking::PlaceHierarchy::PlacePersonPersonIDPhoneNumberPostProduceStateProgramProv:ActivityProv:AgentProv:EntityRailLineRailLineSegmentRecurringEventReleaseStateRepresentationResidenceResourceRevisionBylawRoadRoadSegmentRoleScheduleServiceSexStakeholderStateTemporalEntityTerminalResourceStateTerminalStateTime:InstantTime:IntervalTime:TemporalEntityTpso:ArcTunnelTunnelSegmentUseStateWarrantyWeeklyRecurringEventYearlyRecurringEventschema:legislationJurisdiction
Required Object Properties
	accessesArcachievedAtafteragentInvolvedInasWKTassociatedLocationbeforebeginOfbeginsRecurringStatebeginsRecurringTimecapacityInUsecausedBycausescitizenOfcomponentOfcontainedIncontainsdayofWeekdwellingUnitOccupiedByeffectOfenabledByenablesendOfendsRecurringStateendsRecurringTimeestablishedOnexistsAtfor time intervalforActivityforCityforResourceforStatefromPerspectiveOfhasActivityhasActualAmounthasAddresshasAddressTypehasAllocationhasAssethasAvailableCapacityhasBeginninghasBeneficialStakeholderhasBylawhasCapacityhasCatchmentAreahasCityhasClaimhasClausehasComponenthasContractTexthasContractualElementhasContributingStakeholderhasCountryhasDecomphasDefinitionhasDutyhasDwellingAddresshasEffecthasEmploymentStatushasEndhasFirstManifestationhasGenderhasGeometryhasGoalhasGovernmenthasHomeTypehasIDTypehasImportancehasIncomehasIndicatorhasInputhasLandAreahasLastManifestationhasLocationhasMonthhasNextManifestationhasNoClaimhasOperatingHourshasOutcomehasOutputhasPartyhasPenaltyClausehasPersonIDhasPhoneTypehasPlannedAmounthasPreconditionhasPreviousManifestationhasPrivilegehasProperParthasQuantityhasRepealClausehasResidencehasResidentialRelationshiphasResourcehasSchedulehasServicehasSeveranceClausehasSexhasSignatoryhasSkillhasStatushasStreetDirectionhasStreetTypehasSubAgreementhasSubRecurringEventhasSubStatehasSubactivityhasTimehasTransitionClausehasTypehouseholdOccupiesimmediateComponentOfimmediateContainedInimpactsinsideintendedImpactinvolvesAgentisExecutedOnisValidForoccursBeforeoccursDirectlyBeforeoperatesorg:hasMemberorg:hasPostorg:hasSubOrganizationorg:hasUnitorg:heldByorg:postInorg:roleorg:subOrganizationOfownspartOfparticipatesInperformplaysRoleprecedesManifestationpreconditionOfproperPartOfpropertPartOfprov:usedprov:wasAssociatedWithprov:wasAttributedToprov:wasDerivedFromprov:wasGeneratedByrecursAdditionrecursExceptresourceOfsatisfiedByscheduledForschema:birthDateschema:birthplaceschema:childrenschema:dayOfWeekschema:deathDateschema:deathPlaceschema:issuedByschema:legislationChangesschema:legislationJurisdictionschema:legislationLegalForceschema:legislationTypeschema:parentschema:spousespecifiesAgreementtenureTypetime:hasTimeusedByIndicatorvalidForvalidInvalue
Required Data Properties
	dateInEffectdayOfMonthendTimehasAreaCodehasBuildinghasCitySectionhasClosingTimehasCountryCodehasIdentifierhasNamehasOpeningTimehasPhoneNumberhasPostalBoxhasPostalCodehasProvincehasStreethasStreetNumberhasUnitNumberhasXSDDurationinXSDDateTimeStampphotoIDschema:abstractschema:additionalNameschema:datePublishedschema:descriptionschema:expiresschema:familyNameschema:givenNameschema:identifierschema:keywordsschema:legalNameschema:legislationDateschema:legislationIdentifierschema:namestartTimewgs84:latwgs84:long
Issues
Reference(s)	Alliance for Parking Data Standards: Parking Data Specification: Use Case Document: Release 2.1 (April 2020)
Relevant Specification(s)	ISO 5087-1 City data model — Part 1: Foundation level conceptsISO 5087-2 City data model — Part 2: City level conceptsISO 5087-3 City Data Model Transportation PlanningNewTestSpecifification1Specification:Curb Data SpecificationSpecification:ISO 5206-1 ITS — Parking — Part 1: Core data model
Licensing Information:	Cc-by-3.0Cc-by-4.0GPL v3License TBDMIT License
Other Licensing Notes:	Use case presented here is generalized but consistent with the APDS use case
Use Case Status:	Pending ApprovalApprovedClosed

Supplementary Figure(s)

Figure

Figure: Caption:

Figure: Caption:

Add another

Summary:

This is a minor edit

Watch this page

Save page Show preview Show changes Cancel