Request for (20% to 30%) Changes

[matt-lebl]

After meeting with Developers. Write up a request for changes document as clients for your developer Team. Work as a team and think about changes in detail for the developers. Make sure to send the Document to your developer team before the next lab. This should be a separate document from the requirement Document. Make sure the changes are with respect to functionalities and are feasible and not like changing of platform etc.

• [x] Come up with five changes to request
• [x] Create Request for Changes form and submit to clients

Five changes to request:

1. Restrict bank transfers to clients of the bank only. In other words, clients won't be able to transfer funds between accounts at different institutions
2. Implement "recent transfers" or "contacts," a list of people to which a user can transfer money, for convenient access. Like contacts on eTransfer
3. Can you implement a UI change for dark mode
4. Implement accessibility features for users with accessibility issues such as vision or hearing impaired. Example features would be Colorblind modes, increasing/decreasing font sizes and audio descriptions
5. Implement a customizable main page that allows the user to put the most frequently used features on it.

[matt-lebl]

We'll request a change from them along the lines of "recent transfers" or "contacts," a list of people to which a user can transfer money, for convenient access. Like contacts on eTransfer.

Actually, the change will restrict bank transfers to clients of the bank only. In other words, clients won't be able to transfer funds between accounts at different institutions (to accounts they own or to accounts owned by others), and will only be able to transfer funds between accounts at the Atlantean bank (between accounts they own or accounts owned by others, like eTransfer).

[matt-lebl]

We'll have to come up with a handful more to ultimately request five changes.