Docstoc

Team A

Document Sample
Team A Powered By Docstoc
					ATM Software
Requirements
     Team A
       Ard
    Christiaan
      Oscar
     Vasilis
         Functional Requirements
 The software should be able to control a Card Slot in the following
   ways:
       Draw Card in
       Read inserted Card data
       Eject Card out
       Withdraw Card to Invalid Card Stack
 The software should be able to control a Bill Stack that contains the
  bills currently available in the ATM. The software should be able to
  control a Bill Scanner and keep in memory the value of Bills
  currently available. When necessary, the System should be able to
  output the Bills needed to the Customer.
 The Software should be able to receive Customer input from a
  Keyboard that contains Numeric Keys [0-9] and other Functional
  Keys {Enter, Backspace, Cancel}
 The Software should be able to control a X cm * Y cm b&w screen
  for output to the Customer.
      Functional Requirements
 The Software should be able to query the Central
  Authentication Server in order to cross-check Customer
  PINs.
 The Software should be able to query the Central
  Accounts Server in order to retrieve Customer Account
  details (balance, etc.)
 The Software should forbid access to the Secured
  Transactions for Non-Authenticated Customers.
 The Software should Eject the Card from the Card Slot
  when the Cancel button is pressed, except if the Card
  has been withdrawn in the Invalid Card Slot or there is a
  Secured Transaction pending. In the latter case, the
  cancelation is performed after the Secured Transaction
  finishes.
       Functional Requirements –
        Customer Authentication
 Upon insertion of a Card in the Card Slot the Software
  should draw the Card in and read Customer Data from
  the Card.
 The software should display on the Screen a prompt for
  the Customer to enter a PIN number. When a PIN is
  entered, should be checked for validity with the
  Authentication Server.
 If the PIN is valid the Software should allow the
  Customer to proceed to the Secured Transactions. If the
  PIN is invalid the Software should allow the Customer to
  make another two Authentication Attempts (PIN entries)
  before it withdraws the Card in the Invalid Card Stack.
  Functional Requirements – Cash
             Withdrawal
1. An Authenticated Customer selects the Menu Option “Cash
   Withdrawal” and confirms by pressing the Enter button. The
   Software prompts on the Screen for the Customer to enter an
   Amount for withdrawal. The Customer Enters an Amount and
   confirms by pressing the Enter button.
2. The Software checks that the Amount entered is a multiple of the
   Bills currently available and if not then prompts the Customer to
   enter another Amount. If the Amount Entered is a multiple of the
   Bills available, the Software checks with the Central Accounts
   Server that the Amount Entered is not exceeding the Balance of the
   Account. If the Amount Entered is exceeding the Account Balance
   then the Software prompts the user to enter another Amount by
   repeating (2).
3. If the Amount Entered is both a multiple of the Available Bills and
   less than or equal to the Account Balance, the Software updates the
   Account on the Central Accounts Server appropriately by
   decreasing the Balance with an amount equal to the Amount to be
   withdrawn.
     Functional Requirements – Cash
            Withdrawal (cont.)
4.    The Software outputs the bills necessary to cover the Amount
      Entered.
5.    The Software creates a log entry with the Customer Data, Amount
      Withdrawal and DateTime.
6.    The Software Ejects the Card form the Card Slot.
7.    The Software Logs the Customer Out and returns to the initial
      state (Customer Authentication).
  Non-Functional Requirements
 Reliability: No loss of data in the case of
  problems (power failure, severed data
  connection, fire etc.). The Software should have
  the appropriate logging mechanisms in place.
 Speed: Customer-System Response response
  time must be minimal.
 Ease of use: Customer should not need training
  for using the Software
 The System should be fool-proof!

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:3/19/2013
language:English
pages:7