Low Level Function
1.3.4 Inform and Guide User

Overview

This Function shall be capable of providing the following facilities:

(1) A HMI through which the Traveller or Driver can be guided to provide the precise definition of the service that they want, and the way that they wish to pay for it.
(2) The HMI shall also enable the Traveller or Driver to select the appropriate contract, inform them about their rights to use the service, and display the associated price.
(3) The ability for the Function to be activated by functionality in either the Manage Public Transport Operations Area or the Provide Traveller Journey Assistance Area, or even directly for simple operations.
(4) The ability to ask for a credit check to be done on the Traveller or Driver and also to check to see whether an advance payment has been made.
(5) The ability to initiate the recovery of any advanced payment, or else initiate the computation of the fee.

Functional Requirements

(a) get the information about the service requested from the MPTO or PTJA areas, or directly from the user.
(b) if these areas just ask for a tariff (and not a transaction), go to (g)
(c) get user's ID
(d) obtain the corresponding contracts
(e) get user's choice of contract
(f) check with "Access" and/or "Credit Control" and, if necessary, register a violation.
(g) send the choice and contract to 1.3.6 to check if advanced payment has been made
(h) send the different elements to 1.3.5 to initiate the computation of the corresponding fee
(i) if payment has already been completely made, send an agreement to the "Access Control" system
(j) if not, reduce the fee by the amount already paid, send the elements to 1.3.7 to recover fees,

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 1.3 Perform Electronic Payment Transaction
  • Functional Tree of Area 1

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    4.1.0.1
    The system shall be able to use a variety of relevant payment methods either electronic or not, including central account and post payment, central account and prepayment, on-board account etc.
    4.1.0.2
    The system shall manage customer data (identification, account, rights of residents, etc.).
    4.1.0.3
    The system shall give exact details of any financial transaction to the traveller.
    4.1.1.1
    The system shall have a minimum impact on the traffic flow, e.g. a short transaction duration.
    4.1.1.2
    The system shall have a minimum impact on the driving task.
    4.1.1.3
    The system shall not do anything to reduce the safety of either the travellers in the vehicle, or the staff close to the equipment, e.g. in toll booths.
    4.1.2.2
    The system shall enable a single payment to be paid for services offered by different related transport systems (e.g. metro, bus, train, road and parking).
    4.1.3.3
    The system shall have the maximum security necessary for electronic financial transactions.
    4.1.3.5
    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.