In this post, I will share more about our end product and how we are working together as a team. As we continued to work on the project, we began to have a better idea of how to split up the work and a better idea of what we want our website to look like.
Ultimately, our targeted users are investors who are familiar with algorithmic trading. Our website would be set up to show them the results of the algorithms that have been ran by our team. Currently, our algorithms focus on two objectives: net profit and drawdown. Our website would include a graph with a Pareto curve made up of optimal solutions. The investors can look at the results and decide what would be the best strategy to go with.
We have four people on our team. Currently, one person is working on the algorithms and getting results from the runs, one person is working on managing the database, and two people working on the front-end. I’m handling the database portion so I will be sharing a little bit more about that.
In my previous post, I mentioned that we were going to use a MySQL database. After learning more about our needs, as a team, we decided a NoSQL database fits better. One of the main reasons we decided to switch to a document-oriented database was its flexibility. We are able to change what fields are needed for each document in the database. The flexibility makes it easier and quicker for us to make changes to each document we add instead of having to make updates to the whole table if we use a relational database. We have made several changes from our initial database schema. These changes came from feedback from our group members as well as our advisor.
We decided to use Google Cloud to host our website and Google’s Datastore is our database. Google has a great tutorial on how to set up a cloud project. We are using Python but several languages are supported including Go, Java, and JavaScript.
We have the wire-frame of the website up and running. All the processes are connected. There is more work to be done to get more results that we can show to our end users. We also have to work on polishing our UI. We are working well as a team and are making good progress in Sprint 2!
Leave a Reply