Overview

This Function shall be capable of providing the following facilities:

(1) The ability to manage the store of General Trip Preferences (GTP) Data.
(2) The data in this store shall be available for Travellers to use for every trip that they plan.
(3) The ability to keep the preferences for each Traveller separate and only allow the data for each Traveller to be entered, accessed and updated by the Traveller that owns it.
(4) The ability to respond to any request from the Travel Information Operator for a copy of the data in the store of General Trip Preferences (GTP) Data with all of it, but with the identity of each Traveller and other personal data (e.g. payment details, contact information) removed in order to comply with the relevant EU Data Protection directives.

Functional Requirements

(a) continuously monitor for the receipt of any of the input data flows
(b) when the data flow containing GTP data is received in (a), check that it contains GTP data for a Traveller whose identity is included
(c) check the identity of the Traveller against those whose Preferences are already in the store of General Trip Preferences (GTP) Data, and create a new set of preference data if they are not found
(d) if in (c) preference data for the traveller identity are found in the store of General Trip Preferences (GTP) Data, then those in the data flow shall be used to update those in the store
(e) if the data flow containing GTP update is received in (a) only the preference data for the traveller to whom the data belongs shall be updated in the store of General Trip Preferences (GTP) Data
(f) if the data flow containing GTP data includes a request for all the GTP data for a particular Traveller identity, extract that data from the store of General Trip Preferences (GTP) Data and send it to the Define Traveller's General Trip Preferences using the data flow containing requested GTP data
(g) if the request for applicable GTP parameters data flow is received, only the data for the Traveller making the request shall be retrieved from the store of General Trip Preferences (GTP) Data and sent to the Define Traveller Trip function in the requested applicable GTP parameters data flow
(h) if the data flow containing a request for a copy of the GTP data is received, all of the Preferences in the data store of General Trip Preferences (GTP) Data shall be retrieved, stripped of their traveller identities plus other personal data (e.g. payment details, contact information) and send to the Enable Operator Access to General Trip Preferences function in the data flow containing the requested copy of GTP data
(i) preference data shall be loaded into and read from the data store of General Trip Preferences (GTP) Data using the data flows load GT data and read GTP data respectively.

Diagrams

Parent Higher Level Function

• 6.7 Manage General Trip Preferences

Input logical dataflows

• ptja_GTP_data
• ptja_GTP_update
• ptja_read_GTP_data
• ptja_request_applicable_GTP_parameters
• ptja_request_copy_of_GTP_data
• ptja_trip_results_from_traveller

Output logical dataflows

• ptja_load_GTP_data
• ptja_requested_applicable_GTP_parameters
• ptja_requested_copy_of_GTP_data
• ptja_requested_GTP_data

User needs