Spécifications

Specify your Requirements Specification here point by point. Try to describe your requirements briefly and clearly, so that your potential developer is able to correctly assess its complexity and cost, as well as the required execution time.

A bad or too generic description will result in your order being ignored, or you will spend a lot of time negotiating the details with each applicant.

Remember: It is better to spend thirty minutes to prepare a good text than to lose hours and days to resolve misunderstandings after concluding the Agreement or when accepting the order execution results.

Répondu

1
Développeur 1
Évaluation
(93)
Projets
114
24%
Arbitrage
21
29% / 52%
En retard
8
7%
Gratuit
2
Développeur 2
Évaluation
(31)
Projets
40
15%
Arbitrage
0
En retard
0
Gratuit
Commandes similaires
step by step and structure this into a full IEEE 830 / ISO/IEC/IEEE 29148 style Requirements Specification. This format will include: Introduction System Overview Functional and Performance Requirements Traceability Matrix (linking requirements to test cases) Verification and Validation Compliance Standards 1. Introduction 1.1 Purpose The purpose of this document is to define the technical requirements for the
1.Sinyal Perdagangan : Sinyal beli: garis MACD utama memotong garis sinyal ke atas (macd_current>signal_current && macd_previous<signal_previous). Sinyal jual: garis MACD utama memotong garis sinyal ke bawah (macd_current<signal_current && macd_previous>signal_previous). Gambar di bawah menunjukkan kasus beli dan jual. 2. Posisi ditutup pada sinyal yang berlawanan: Posisi beli ditutup pada sinyal jual, dan posisi

Informations sur le projet

Budget
30+ USD
Délais
à 30 jour(s)