Discussion of article "How to create Requirements Specification for ordering an indicator" - page 5
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
+100
Trying to change/teach/make the customer think is a utopian idea.
If he doesn't have a clear idea of what he wants to get before placing an order, no article (neither short, nor detailed, nor in video format) will make him understand the issue in detail. And if he already understands what he wants, there are no difficulties with the presentation (including illustrations where they are necessary).
Everything else falls on the programmer's shoulders and is included in the cost of the work. With experience we manage to recognise inadequates quickly, literally by a few lines. And there are practically no bad orders.
The article will remain without the audience planned for it (but perhaps it will interest other inquisitive minds).
Andrei, you are an experienced person. There are difficulties in transferring thoughts to paper (to comp). I had a friend, alas deceased, who could not speak at all, always kept silent in companies. But he wrote such texts that everyone read them. And there were variants quite the opposite. Now the customer - a lot of emotions, and then it turns out that in the TOR there is no system for setting positions. That is, it was written - to put once a day, then - oh no, we need to once an hour!!!! Judging by the experience of past work, this hysteria will continue.
Updated the draft article in my very first post - added sections
Useful software for writing TOR
Formulation of Terms of Reference in the form of an Algorithm
Examples of Terms of Reference
I also have an example of the second ToR, I need another one. Throw in ideas, please. And read/suggest/criticise.
The better we make the article for the customer, the easier it will be for all of us.
The article should include a reminder of the rights of the parties to the result of intellectual labour, whether the source code is transferred, a guarantee of errors and corrections in case they are discovered as a result of changes in the software or the occurrence of previously unprecedented situations. Perhaps the price of the contract should depend on it.
I think it is worth explaining to the customer that logic is important in the algorithm and acquaint him with a minimum set of operators so that he could express his thoughts in formulas.
Complex indicators and mathematical algorithms are better to make in Excel, where formulas and all logic will be visible, which will simplify mutual understanding, and besides it is quite convenient to draw panels in Excel. I myself have repeatedly attached such files to the TOR.
For TOR advisor need the basics of block diagrams, otherwise the code is likely to be written in such a way that minimal edits will require total corrections - from experience.
For block diagrams I like this Diagram Designer programme http://meesoft.logicnet.dk out of many.
About the debugging/acceptance mode - I think that here we should talk about the need to print to the log about the events occurring in the Expert Advisor, such as blocking the signal by filter, calculated values of indicators and other important situations for the customer, and in addition you can put graphical objects on important situations, of course this should be disabled in case there is no need for this data. Such things make it much easier to check and accept the work. And, it is not superfluous to put a counter to fix the time spent on the calculation of the body of the programme at each event - the issue of brake codes is relevant for Freelance.
It is necessary to remind the customer about checking the work of the indicator and EA through the strategy tester, checking the work on different TF (especially relevant for MT5!), and the subsequent check on real quotes, including indicators. Here it would be good to use a programme that will make screens periodically - to track indicator redraws.
In case of revealing errors in the work of the order, the Customer should document the error and reasonably write a brief claim, rather than start an emotional correspondence with the Executor.
In case of order errors, the Customer should document the error and reasonably write a brief complaint rather than starting an emotional correspondence with the Contractor.
Block diagram and Excel will be added, thank you
I will add the block diagram and Excel, thank you
You are welcome, but it would be good not to ignore the other wishes, they are probably even more important for the Customer.
By the way, it is not superfluous to remind the Customer that there are omissions in the history, for example, due to a break in the stock exchange or absence of quotes, and the indicator and Expert Advisor work should be checked on this data.
Please, but it would be good not to ignore the other wishes, they are probably even more important for the Customer.
Perhaps I will add the rest down below - for those who will read the article to the end. It is definitely not worth writing it at the beginning - they may drop it without finishing it.
That's reasonable.
Added text to the section Useful programmes for TOR writing and Acceptance and verification of the indicator
One more TOR example remains to be added and can be published
Added one more example of ToR, ending and some text in Acceptance and verification of the indicator
If someone will offer a third example of ToR for inserting into the article, it would be great. In extreme case I will do it myself.