In this project you will be designing the logic for a basic ATM banking machine

INSTRUCTIONS TO CANDIDATES

ANSWER ALL QUESTIONS

Programming Logic and Design – Project

Automatic Teller Simulator

INTRODUCTION

This project will allow you to apply your knowledge and skill in program logic and design. You will need to read and analyse the information provided and extract the vital pieces of information that will allow you to design the program logic and features of the solution to the problem presented. For the purposes of this project you will need to leverage the major components, features techniques and procedures that you learned in this course in order to complete the requirements of this project. You will need to create flowcharts, write pseudocode, prepare diagrams, apply modularization techniques, use the common programming structures of sequence, selection and looping and design the mainline logic as part of your final solution.

OBJECTIVES

The main objectives of this project are to:

• Interpret specifications and analysis performed
• Design a solution based on the requirements and specifications
• Design the logic required for a complete program design solution

TIME REQUIRED

You will require 8-10 hours to complete this project.

REQUIRED MATERIAL

You will need the following material to complete this project:

• Visio (Standard or Professional version) or other Flowchart software (At a minimum, Microsoft Word can be used)
• Microsoft Word ( for document preparation

In programming there are generally multiple possible solutions to the same problem.

Your solution may not be identical to someone else’s, but that does not mean that it is wrong. Your solution will not and should not look exactly like your colleague’s solution. Any good solution is acceptable if produced following the principles and guidelines presented in this course. Keep in mind that this is your first course, and the topics that have been presented, have been done so at an introductory level with the objective of introducing you to the fundamentals of programming logic and design. These same topics will be continuously re- enforced throughout the rest of the program and you will have the opportunity to expand on them as you progress. Therefore, the expected solution for this project will be one that is at an introductory level where you apply the design skills as you have learned in the course.

SPECIFICATIONS

In this project you will be designing the logic for a basic ATM banking machine. Your ATM must have at least three screens (login keypad screen, main transactions screen, administrator screen). You will assume that for the purposes of this project, that your client data, (PIN numbers, names etc are stored in an appropriate file or database within the system. You do not have to design the storage itself, but simply access it as required for validation purposes. Your system will have one single administrator who can perform the tasks described below.

Key Functions

 

The main functions of the ATM simulator may be summarized as follows:

• Before performing any transaction, the user must enter his or her name and PIN (personal identification number) on an input screen (login keypad. Since the operation of this input screen should simulate the normal operation of an ATM, the PIN should not appear as text on the screen. If the user name / PIN comobination is not valid, an appropriate message must appear on the screen and the user is prompted to try

In addition to the message which appears after every unsuccessful attempt, if after three tries the PIN matching the name has not been entered, the application should display a message requesting the user to try using the ATM again later and not allow further attempts. The names and PINs of users must be validated using data contained in the CustomerInfo database having the following structure:

• name (String)
• PIN (String – 4 characters)
• Once access has been authorized, the main transaction screen of the application should allow the user to carry out one of the following transactions:
• deposit
• withdrawal
• transfer
• bill payment
• When a user performs an operation, the application should first ask if it should be done using a chequing or savings account, and then ask for the transaction amount. Assume that customer banking account details are stored in a general database named Accounts.dat with the following structure:
• account type (1 character)
• PIN (String – 4 characters)
• account number (String – 16 characters)
• account balance (single)
• For a deposit, the user must enter the amount and, if required, be able to select the account type to be credited. The chequing account is the default for this transaction.
• For a withdrawal, the user must enter the amount and, if required, be able to select the account type to be debited. The chequing account is the default for this transaction subject to a maximum of $1,000 per transaction. If the user enters an amount greater than $1000, the system must present a message indicating that

$1000 is the maximum per withdrawal. The ATM accepts only transactions for which the amount entered is a multiple of $10. There is no daily maximum amount apart from the user’s account balance in which case the system must also inform the user if the account balance is less than the transaction amount. In addition, the ATM Machine starts its day with a full $20,000 in funds. Each withdrawal must also be validated against the amount left in the machine If the withdrawal amount is greater than the amount left in the machine, the system must inform the user that the machine has insufficient funds (not the user account)

• For a transfer, the user must be prompted to enter the amount and the type of transfer (from chequing to savings, or vice versa). This transaction is subject to a maximum $10,000. The system must allow only a transfer from checking to savings, or from savings to chequing. The system must also validate that the account balance from which the amount is being transferred has sufficient funds to cover the transaction amount. ( Hint: the validation of account balance is repeated in several places à consider modularization here!)
• For a bill payment, which is done from a chequing account only, the user must enter the amount of the transaction. The chequing account is debited by the same amount. In addition, a $1.25 fee is charged to the chequing account. The maximum per transaction is $10,000. Again, the account from which the amount is being taken, must have sufficient funds to cover the transaction
• The application must check the account balance before doing a transaction. Any transaction that would result in a negative balance must be
• The balance of the account affected by a transaction should be updated and displayed after each
• The user should be able to do as many transactions as he or she would like to do before leaving the
• A warning message should inform the user that the ATM can no longer carry out withdrawals when there is no money available. When a withdrawal transaction event occurs for an amount greater than the balance remaining in the ATM, the ATM should advise the user they can charge the transaction amount to the amount still available in the user’s account.
• When the application is initiated at start of each day, the bank’s balance money is automatically refilled with up to $5,000 for a maximum of $20,000.

Attachments:

Related Questions

. Introgramming & Unix Fall 2018, CRN 44882, Oakland University Homework Assignment 6 - Using Arrays and Functions in C

DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma

. The standard path finding involves finding the (shortest) path from an origin to a destination, typically on a map. This is an

Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t

. Develop a program to emulate a purchase transaction at a retail store. This program will have two classes, a LineItem class and a Transaction class. The LineItem class will represent an individual

Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th

. SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of Sea Ports. Here are the classes and their instance variables we wish to define:

1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of

. Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of Sea Ports. Here are the classes and their instance variables we wish to define:

1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of