Low Level Function
6.7.1 Define Traveller's General Trip Preferences

Overview

This Function shall be capable of providing the following facilities:

(1) The ability for the Traveller to specify a set of factual data to be used as General Trip Preferences (GTP) for use each time they want to plan a trip.
(2) There shall be no requirement for the Traveller to do this more than once and the data shall be used as a preparation to full personalisation.
(3) Once a planned trip has been completed, the ability to ask the Traveller for any comments on the performance of the trip and any changes that are needed to the GTP data.
(4) The ability to enable the Traveller to receive an output of their current GTP data and to amend that data, even if this is not the result of the performance of a planned trip.

Functional Requirements

(a) continuously monitor for the receipt of the input data flows
(b) if the data flow received in (a) is from a traveller and contains GTP data send it to the Manage General Trip Preferences Storage function in the data flow containing GTP data, making sure that each time the data flow is sent, the Traveller identity is included
(c) if the data flow received in (a) contains a request from the Traveller for their GTP data, use the data flow containing GTP data to request that the data is provided
(d) when following (c) the data flow containing requested GTP data is received, provide output of the assembled GTP data to the Traveller
(e) if the data flow received in (a) contains a request for the traveller to provide their post trip preferences, send the post trip preferences request data flow to the traveller
(f) as a result of (e) monitor for the receipt of the post trip preferences data flow from the traveller
(g) when the data flow in (f) is received, send its contents to the Evaluate Trip After Completion function in the post trip preferences data flow
(h) as a result of (g) send any changes to the traveller's GTP data to the Manage General Trip Preferences Storage function in the GTP update data flow, not forgetting to include the traveller's identity
(i) if no input from the traveller is received in (f) send a null response to the Evaluate Trip After Completion function in the post trip preferences data flow.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 6.7 Manage General Trip Preferences
  • Functional Tree of Area 6

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    10.2.1.9
    The system shall enable the traveller to specify any special needs that he or she may have, e.g. disability, young children, etc.
    6.1.0.4
    The system shall be able to provide information on alternative routes where they are quicker, cheaper, shorter, scenic, etc.
    6.1.0.5
    The system shall enable travellers to plan their trip using their own travel criteria (modes of transport, time of departure/arrival, road selection criteria, etc.).
    6.1.0.6
    The system shall enable travellers to plan their trip according to the needs of their disabilities.
    6.1.0.7
    The system shall be able to provide information so that travellers may share a vehicle with others for all or part of a (multi-modal) journey.
    6.1.2.8
    The system shall provide information in the native language at the output location, and/or from a user selected choice of other appropriate foreign languages.
    6.1.3.1
    The system shall be able to provide facilities for the necessary user identification when a traveller requests information that may result in the purchase or booking of services.
    6.1.3.8
    The system shall be able to provide customised pre-trip information to hand-held and in-vehicle devices.
    6.2.2.8
    The system shall be able to provide road information according to different geographic scales, e.g. local, regional, national, international.
    6.2.3.1
    The system within the vehicle, or in the centre, shall support various types of presentation to the user.
    6.2.3.2
    The system shall normally provide messages from a finite set of well defined messages.
    6.2.3.3
    The system shall provide information in the native language at the output location, and/or from a user selected choice of other appropriate foreign languages, when applicable.
    6.2.3.4
    The system shall provide information using "open" standard communication protocols.
    6.2.3.5
    The system shall be able to provide customised on-trip information to hand-held and in-vehicle devices.
    6.2.3.6
    The system shall enable drivers to customise the style and content of the information that they receive from hand-held and in-vehicle devices.
    6.2.3.7
    The system shall be able to retain the customisation details in a manner that is independent of any physical output device.
    6.4.1.4
    The system shall be able provide customised navigation information to the destination using a variety of selection criteria.
    6.4.2.2
    The system shall contain menus which are structured in a logical manner and oriented towards the requirements of the driver (e.g. the most frequently used function shall be the easiest to select).
    7.6.2.3
    The system shall enable a traveller to request and receive personalised journey plans in advance, assess different plans according to certain criteria (e.g. vehicle type, travel time, cost, expected traffic density, planned events, facilities en route, parking), and to save one for future use.