smartCrypto
Project Definition Document (Initial Brief)
Purpose of this document
The purpose of this document is to define a proposed project with enough information for an informed decision to be made on whether to approve the project to proceed.
This document is the responsibility of the Project Team.
Project approval is dependent upon the document being completed and reviewed by the teacher of the project course.
● If the project is approved, it can then begin planning and execution,
● If the project is not approved, the Project Team can review the project and resubmit for reconsideration.
Table of Contents
- Purpose of this Document
- Table of Contents
- Project Definition Information
- Project Idea
- Project Purpose
- Team Member Capabilities
- Project Outcomes/Requirement Objectives
- Initial Scope of the Project
- Time Objective
- Parties Involved
- Constraints
- Feasibility
- Roles & Responsibilities
- Initial Issues
- Risks
- Deliverables, Timeframes and Dependencies
1. Project Definition Information
Project Name: |
smartCrypto |
Project Team: |
Jason Xu |
Mentoring Teacher: |
Edwin Griffin |
Proposed Project Start Date: |
July 31, 2022 |
2. Project Idea
The project smartCrypto uses data from crypto market to train a model that can predict the trending of a specific crypto coin in runtime, based on pass record of this coin and also the global trending.
3. Project Purpose
Last few months, I put $15,000 in crypto to invest. Of course, thanks for the Russian-Ukraine situation, I lost 70%. I HAVE TO make this money back somehow by investing crypto again (of course). To make sure I make more profit with less stress, here we come smartCrypto.
4. Team Member Capabilities
Team Member |
Capabilities |
Jason Xu |
Knowledge of C#, JavaScript (Node.js, JQuery), Object-C, PHP, HTML, CSS, SQL, Python, Shell, C++ Knowledge of Linux (command line)
|
5. Project Outcomes/Requirement Objectives
Outcome |
Description |
Obtain data from crypto market |
Can obtain data (i.e. price) from crypto market (i.e. Binance) |
A trained model based on the data |
Can generate a model base on the obtained data |
Make prediction by using the model |
Can predict crypto price trending using the generated model |
6. Initial Scope of the Project
In Scope |
Out of Scope |
Selected time ranged data for model training |
Ability to change the data and retrain the model |
Request real time statistics of a crypto coin from crypto market |
Ability to change crypto market source |
An interface to demonstrate prediction (either in GUI or CLI) |
|
Custom crypto coin to analyse |
|
7. Time Objective
The timeframe for this project is: 11 weeks
8. Parties Involved
Party |
Involvement |
Test users |
Testing and review of features and user-interface |
Mr. Griffin |
Review the project |
9. Constraints
Constraint |
Impact on Project Success (High/Med/Low) |
The quantity and accuracy of data |
High |
The ability to implement a model training process |
High |
The hash computing performance when training the model |
High |
10. Feasibility
Skill Required
|
Resource with skill / capability |
Crypto data source |
Binance API |
Model training + make prediction |
Tensorflow/Pytorch |
User interface |
HTML/CSS/JS Or Command Line |
Project information / user documentation |
Word Journal website |
Ability to alter the crypto price |
None |
Feasibility Scale: 90%
11. Roles & Responsibilities
Team Member |
Roles / Responsibilities |
Jason Xu |
Project Lead System Analyst Frontend developer Backend developer Documentation Specialist |
12. Initial Issues
Issue |
Description |
Lack of time – Jason |
Jason has a lot of assignments + assessments as he is a Year 12 student (most importantly he does specialist mathematics). Alternatively, he has lots of different projects to work on (open source projects). Therefore, he might not have enough time to work on the project. |
13. Risks
Risk |
Description |
Impact of Risk (L M H) |
Mitigation / Reduction |
Team sickness |
Team member becomes sick/ill for extended period of time |
H |
Request extension from the teacher; or, Reduce the amount of work |
Loss of model |
Somehow the saved trained model is lost |
H |
Weekly backup the model |
14. Deliverables, Timeframes and Dependencies
Timeframe estimate: 11 weeks
Deliverable |
Duration |
Completion Date |
Dependencies |
Data crawling |
1 Week |
End Week 2 |
None |
Model training |
1 Week |
End Week 3 |
Data crawling complete |
Model implementation |
1 Week |
End Week 4 |
Model training complete |
User interface |
1 Week |
End Week 5 |
Model implementation complete |
Testing |
6 Weeks |
End Week 11 |
User interface complete |
Documents + PowerPoints |
1 Week |
End Week 12 |
Testing complete |