• Read the Needs Analysis document below to come up with a design documentation for a program. You need to identify the classes you will use, the algorithms used for various tasks, and an overall flow of the software. At this stage, you may define some of the algorithms at a high level (e.g., you will mention that you will use a sorting algorithm but you do not need to define the details of that algorithm.)

Need Analysis

The course project

application will be designed to simulate the reception of a bank. It will

simulate customer transactions, bank teller allocation, and the passing of

time. The application will also be required to print a report of interaction

with customers.

The simulation will allow

customers to enter the bank at random times. When a customer enters, they are

assigned to a teller. Each customer may request to open an account, close an

account, withdraw money or deposit money.

The bank teller is intended

to provide customers with timely service. There may be a minimum of 1 teller

working at a time to a maximum of three, depending on the number of customers

in the bank. One teller will be working until there are more than four

customers, then the second teller comes to help. Once there are more than eight

customers in the bank is when the 3rd power comes to help.

The simulation of time

passing will handle a few areas of time. First it will track of the current

time. The time will increment based on when customers enter the bank and how

long each transaction takes.

Lastly, the simulation will

end with a report of all customer transactions that took place during the day.

The report will display each customer's first name, last name, account number,

time of arrival, type of transaction, and amount of money involved.

Assumptions

The application is assumed to

be desired console application and requires no user input. Once the application

runs, it performs all the logic and prints the results. The application will be

created using the C++ programming language and utilize the object-oriented

design. There will be classes for customers, tellers, time, accounts, and

reports.

It is assumed that all

customers and their attributes will be created/ defined prior to entering the

bank. Customers can only make one transaction and not re-enter the bank after

they left. Customer transactions request will be randomized, and the time in

which they take will be randomized.

Scope

One area considered out of

scope is the user interface. The logic and design is for a console based

application. User input is also out of scope. All the attributes are

predetermined.

NOTE: This assignment is a

DATA STRUCTURE USING C++