- Create an Issue
- 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. - In IntelliJ, fetch and checkout to the automatically created branch.
- Implement then
Commit and Push
. - Create a Pull Request and
Merge
if all checks have passed. The issue will automatically close.
- 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
- Workflow Guide
- Installation Guide
- Requirements
- Database
- Application Design
- Networking