Design by requirements and writing technical specifications for the developer, how?

Question

Preparation of terms of reference

Learn how to write technical specifications for a developer.
There are layouts in axure, there is a design, there is a description of the data structure, a description of the exchange protocol with our database, etc. descriptions + the customer is always at hand ready to answer all questions and the database developer, but it’s impossible to collect and structure the document in it all, so that the web developer starts working according to the TOR.

Answer 1

The best way to learn is by example . On the other hand, if you have the layouts, design and structure of the database, then this is actually the TOR. You have the minimum left - write it down in a form convenient for execution and control. Break the system into small sections (forms, pages, etc.), these will be sections of your TOR. Fill these sections with what you have. Here is the finished TK.
Keep in mind that if a developer requires a specification, then he has some idea about it, and if you do not please him, he will say that the specification is bad. There's nothing you can do about it. Not many people can write good technical specifications, they learn this for years. If you don't have that much time, change your strategy. Replace qualitative formalization with communication. So tell the developer: "we have all the necessary production, and the details, specifics and questions in personal communication."
An experienced developer with good accuracy can estimate the cost of implementing a layout (especially with a design). He does not need to chew all the details through the TK. Usually it is not possible to prescribe everything in the TOR, do not console yourself with hopes that now everything will be a penny for a penny. There are always discrepancies, ill-conceived moments and changes in the TK. Communication between the customer and the contractor is required.