2021 CAB302 Major Project | Group 24 | Electronic Trading Platform

Specification

Marking Criteria

Workflow

1. Create an Issue
2. Comment /cib on an issue to indicate you are currently working on it. A new branch with the issue number and title is automatically generated.
3. In IntelliJ, fetch and checkout to the automatically created branch.
4. Implement then Commit and Push.
5. Create a Pull Request and Merge if all checks have passed. The issue will automatically close.

Notice Board: Final Submission on 06/06/2021

Requirements Progresses (14/18)

• Has a graphical user interface
• Has separated user interfaces for normal users and admins
• User authentication: User needs to log in to use the application
• User can see & trades using organisationalUnit's credits & assets
• User cannot place orders with higher price / quantity than the organisational unit can afford
• User can see current BUY & SELL offers
• Admin can create new organisational units and edit the units' credits and asset quantity
• Admin can edit & create new asset
• Admin can edit & create new user
• Password are hashed before being sent and is stored in hashed form
• Has a server that can interact with database and return reponse to client's request
• Server can facilitate and match sell-buy order
• Has server-side database to store user information, asset information, organisational unit information and trade information
• User can access and remove a listed order from their organisational unit
• Client & Server can run using configurations from a .properties file
• User can view price history of asset. Price history is graphical
• Notification on trade reconciliation
• User can change their password

Documents Table of content

1. Workflow Guide
2. Installation Guide
3. Requirements
4. Database
   1. Database Design
5. Application Design
   1. Client
   2. Server
   3. Common Classes
6. Networking