HeKatE Case: Cashpoint


The system is composed of till which can access a central resource containing the detailed records of customers’ bank accounts. A till is used by inserting a card and typing in a Personal Identification Number (PIN) which is encoded by the till and compared with a code stored on the card. After successfully identifying themselves to the system, customers may either:

  1. make a cash withdrawal or
  2. ask for a balance of their account to be printed.

Withdrawals are subject to a user resources, which means the total amount that user has on account. Another restriction is that a withdrawal amount may not be greater than the value of the till local stock.

Tills may keep illegal cards, i.e. after three failed tests for the PIN.

→

See for a full Description (see Description in the design process).




  • enteredPin - a PIN number that has been entered by user.
  • correctPIN - a PIN number that is stored on the card.
  • authorized - indicates if the user has entered the correct PIN.
  • userAccountAmount - the amount of the free founds on the user account.
  • cashPointAmount - the amount of the founds that are available in a cashpoint.
  • failedAttempts - the number of failed attempts to authorization.
  • requestedAction - the operation that user want to execute.
  • cashPointActivity - the final operation invoked by cashpoint.


  • enteredPinauthorized
  • correctPINauthorized
  • enteredPinfailedAttempts
  • correctPINfailedAttempts
  • authorizedcashPointActivity
  • userAccountAmountcashPointActivity
  • cashPointAmountcashPointActivity
  • failedAttemptscashPointActivity
  • requestedActioncashPointActivity

See for a full Conceptualization (see Conceptualization in the design process).

Conceptual design

See for a full Conceptual Design (see Conceptual Design in the design process).

Attribute Specification

See for a full Attribute Specification. (see Attribute Specification in the design process).


XTT prototype


See for a full Prototyping. (see Prototyping in the design process).

Logical Design

See for a full Logical Design. (see Logical Design in the design process).

Formal Analysis

See for a full Formal Analysis. (see Formal Analysis in the design process).

Physical Design

Used states:

  • init0:
    [enteredPin, 1111],[correctPin, 1111],[desiredAmount, 100.0],[cashPointAmount, 100000.0],[userAccountAmount, 10000.0],[userRequestedAction, withdraw]
  • init1:
    [enteredPin, 1111],[correctPin, 1112],[desiredAmount, 100.0],[cashPointAmount, 100000.0],[userAccountAmount, 10000.0],[userRequestedAction, withdraw]
  • init2:
    [enteredPin, 1111],[correctPin, 1111],[desiredAmount, 100.0],[cashPointAmount, 10.0],[userAccountAmount, 10000.0],[userRequestedAction, withdraw]
  • init3:
    [enteredPin, 1111],[correctPin, 1111],[desiredAmount, 100.0],[cashPointAmount, 1000.0],[userAccountAmount, 10.0],[userRequestedAction, withdraw]

→

See for a full Physical Design. (see Physical Design in the design process).

See for a full Integration. (see Integration in the design process).


See for a full Summary. (see Summary in the design process).

hekate/cases/hekate_case_cashpoint/start.txt · Last modified: 2019/06/27 15:49 (external edit)
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0