System Functionality 1. In order to access the ATM, a customer must login with one of the following: A. A valid account number and a four-digit PIN B. A valid user name and password 2. New customers can register for an account. 3. Authenticated users can utilise the system to: ? make a deposit ? make a withdrawal (with sufficient funds available) ? make a single click ?fast? withdrawal of ?100 (with sufficient funds available) ? transfer funds to another account (with sufficient funds available) ? view an account balance ? print an account transaction statement (on screen) (Last week, two weeks, month or custom period) 4. The currency exchange rates will be provided by your own Restful service called Currency 5. The Web application will be developed using the DOTNET Framework and the MVC (Model?view?controller) software architectural pattern. 6. The Web application will contain a local database to keep persistent account data and transaction records 7. The Currency RESTful service will implement the Web API design architectural pattern and also contain a database to maintain currency data. 8. The design and implementation of a realistic and easy-to-understand user interface is expected and users may access the system through multiple devices so you should consider a responsive design. STEP BY STEP TEXT FILE REQUIRED TO PROOF THE PROGRAM WAS CREATED BY MYSELF ? All solution files and associated documentation submitted (explanation what code you used and why) explanation how the program is made. Step by step solution to prove the program was made by the student ? You will be required to discuss your code and design decisions.
VISUAL STUDIO 2013 or 2015 or 2016
Task:
The purpose of this assignment is for you to demonstrate your understanding of appropriate Web technologies, Web development tools, Web standards and current practice to solve a range of web site related problems.
You have been hired to design, develop and test a new Web based ATM (Automated Teller Machine). The web application gives customers access to their standard current and savings accounts, but also allows for transactions in multiple currencies (see the guidance below).
You are also required to evaluate your solution in relation to design, usability and functionality. The evaluation will include a description on your chosen testing strategy with appropriate plans, logs and results, identifying differences between expected and actual results. If your solution contains more errors that you have been able to solve, document the problems and describe what you have done to try and resolve them. The evaluation provides an opportunity to achieve additional marks by describing design features, functionality, good practice and enhancements.
System Functionality
1. In order to access the ATM, a customer must login with one of the following:
A. A valid account number and a four-digit PIN
B. A valid user name and password
2. New customers can register for an account.
3. Authenticated users can utilise the system to:
? make a deposit
? make a withdrawal (with sufficient funds available)
? make a single click ?fast? withdrawal of ?100 (with sufficient funds available)
? transfer funds to another account (with sufficient funds available)
? view an account balance
? print an account transaction statement (on screen) (Last week, two weeks, month or custom period)
4. The currency exchange rates will be provided by your own Restful service called Currency
5. The Web application will be developed using the DOTNET Framework and the MVC (Model?view?controller) software architectural pattern.
6. The Web application will contain a local database to keep persistent account data and transaction records
7. The Currency RESTful service will implement the Web API design architectural pattern and also contain a database to maintain currency data.
8. The design and implementation of a realistic and easy-to-understand user interface is expected and users may access the system through multiple devices so you should consider a responsive design.
Submission
? All solution files and associated documentation submitted (explanation what code you used and why) explanation how the program is made. Step by step solution to prove the program was made by the student)
? You will be required to discuss your code and design decisions.
