By what means, where and how to write TOR for development?

Question

Preparation of terms of reference

Now we are preparing to start developing a new web service. The first step is the design and writing of technical specifications. I heard that many web offices are now abandoning such a concept as technical specifications and are getting by with the development of prototypes and explanations for them. We have always written technical specifications (there are many pages in a regular text document describing the functionality, structure, design, etc.). Now we doubt that it is worth doing this. Are there really any new trends in writing TK? How to do it right? Maybe there are some web services, applications? For example, I heard about such a thing as MindMap, though I didn’t quite understand how it could describe the possibilities of a future project.
In general, the task is worth it - a detailed description of the functionality of the future project. How and what is the right way to do it?

Answer 1

MindMap doesn't even hint to developers how to do it in practice. write everything in detail on paper, the more detailed the better:
- the user has the ability to: change the password, write messages, read messages, like messages
- possible actions with friends: block to read messages, block to send, blacklist (2 of the above actions together)
If you have a techie in your team, then at least write like this (some programmers will orgasm from a clear technical specification, and someone will not have enough freedom):
- incoming data of the format of such and such
- processed using Get, Post with referrer check
- make an API on request with a secret key and a limit of 10 thousand requests per day, give parameters A, B, C in JSON format