Low Level Function
1.3.3 Check User's Contract

Overview

This Function shall be capable of providing the following facilities:

(1) The ability to read the corresponding contracts, and verify the access rights, based on the user's ID.
(2) If there is a "free ride" request, the ability to cancel the rest of the transaction.

Functional Requirements

(a) receive user ID and service request
(b) extract corresponding contract from the store of "contract" Data
(c) check the access rights by asking the "Access Control" Function,
(d) sends the contract information back to the "inform and guide user" Function
(e) in case of reception of a "free ride request", no further checks are performed

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.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).