Overview

This Function shall be capable of providing the following facilities:

(1) A HMI through which the Car Pooler can register or de-register to be included in vehicle sharing travel plans.
(2) The HMI shall also enable the Car Pooler to take part in plans that they propose, or are proposed by other Car Poolers.
(3) The ability through the HMI for Car Poolers to accept or reject any proposed travel plan to be shared with other Car Poolers and to request and view only those travel plans in which they are active participants.
(4) The HMI shall also be capable of operating in a variety of locations and if necessary provide controlled access for registered Car Poolers.

Functional Requirements

(a) continuously monitor for the receipt of the travel needs data flow from the car pooler
(b) when the data flow in (a) is received, check to see of the personal details of the car pooler are available (i.e. the car pooler has previously registered by providing their details) and if not, wait for receipt of the personal details data flow from the car pooler
(c) when (b) has been completed, send the car pooler travel needs data flow to the Create Travel Plans for Vehicle Sharing function
(d) when in (b) the personal details for the car pooler are received, send the to the Manage Vehicle Sharing Information function in the car pooler details data flow
(e) as a result of (c) continuously monitor for receipt of the proposed travel plan from the Create Travel Plans for Vehicle Sharing function
(f) when the data flow in (e) is received, send its contents to the car pooler in the proposed travel plan data flow
(g) as a result of (f) await arrive of the accept travel plan data flow from the car pooler
(h) if the data flow in (g) contains a negative response send the travel plan rejected data flow to the Create Travel Plans for Vehicle Sharing function and include the reasons for rejection that have been provided by the car pooler
(i) if the data flow in (g) contains a positive response send the travel plan accepted data flow to the Create Travel Plans for Vehicle Sharing function
(j) if the personal details data flow is received from the car pooler, send the data it contains to the Manage Vehicle Sharing Information function in the car pooler details data flow
(k) if the deregistration data flow is received from the car pooler, send a delete indication to the Manage Vehicle Sharing Information function in the car pooler details data flow
(l) continuously monitor for receipt of the car pooler location data flow and when it is received, use its contents in the above request for a travel plan.

Diagrams

Parent Higher Level Function

• 4.6 Provide Facilities for Vehicle Sharing

Input logical dataflows

• flds-car_pooler_location
• ft.cp-accept_travel_plan
• ft.cp-deregistration
• ft.cp-personal_details
• ft.cp-request_current_travel_plan
• ft.cp-travel_needs
• mpto_proposed_travel_plan
• mpto_requested_current_travel_plan

Output logical dataflows

• mpto_car_pooler_details
• mpto_car_pooler_travel_needs
• mpto_request_current_travel_plan
• mpto_travel_plan_accepted
• mpto_travel_plan_rejected
• tt.cp-current_travel_plan
• tt.cp-proposed_travel_plan

User needs