Customer Meeting 2 Date: 26.02.19

1. Meeting details

Meeting Date/Starting Time: February 22, 2019
Meeting Purpose: Customer meeting about project requirements, clarifying vague points
Meeting Location: BM A4

2. Notes

2.1. Mock-up design should include real data, not a place holder.
2.2. Mock-up design should show a possible scenario for a user.
2.3. In a mock-up design, the design is not the first concern but also should not be the last concern.
2.4. Beside mock-up design, personas should be prepared that should explain for a possible user and its behavior.
2.5. System requirements should include the version/build numbers of supported operating systems and browsers.
2.6. In requirements, terms specific to this application should be explained in detail. For example, advanced search
2.7. "Shall be able to use" template should be used for requirements.

3. Customer Notes

3.1. Trader users should have IBAN numbers.
3.2. The application should support chief monetary units in the world.
3.3. Users should be able to deny the following requests coming from other users.
3.4. If a user profile is private, then the content produced by that user should only be visible to its followers.
3.5. Prediction success rate should be visible to everyone even a user's profile is private.
3.6. If a user follows another user, this user should get a notification about other users activities.
3.7. Users should be able to follow economic events. A user who is following an event should be notified after the event happened.
3.8. The application should contain an admin panel for developers to add new currencies into the system.
3.9. Trader users have to verify their email before making their first investment.
3.10. The application should support Turkish characters. The language of the app should be English. Any other language may be supported.
3.11. Specifications for the password should be clarified in the requirements. For example, the minimum length of the password.