Refining the project plan
Beyond the introduction, let's elaborate a bit on the project idea.
Trading is a time consuming activity. In many occurrences though, one only waits for specific signals such as indicator values or pattern breakouts, and react to those. Sometimes, a trader's strategy might include a whole sequence of such reactions, either in a quick succession he could fail to perform manually, or over several hours, wasting valuable time.
Cryptomate shall solve this issue by allowing the user to plan his strategy ahead of time and let the tool apply it. Such a strategy will involve detecting conditions on technical indicators, price action, and possibly customizable inputs. Upon those, Cryptomate will react by either notifying the user, or opening and closing positions automatically.
Cryptomate shall leave the door open to, but not implement, quantitative trading features, including probabilistic models and deep machine learning.
Details of how the user defines their strategy, what notifications and tracking features should be included remains to be defined.
Defining a design strategy
A new project with no legacy to accommodate may either be a clean slate or a blank page, depending on how one looks at it. Before we start filling it, we need to define our strategy:
- As architects, we must get a better understanding of the business objectives of the stakeholders.
- From those objectives, we must then determine requirements and constraints.
This will allow us to get a deeper understanding, which we will gather into a workbook. We will then use that knowledge to define the high-level architecture, exploring common patterns and tailoring them to our needs.
As this is an illustrative, small-team project, we choose to devote a maximum of one day to this upfront design phase. We will then review the design once a month, feeding the knowledge we gather as the project advances back into the design process.
Ready? Let's go to the next post then.