How to learn how to write technical specifications for developers?

Question

Microsoft

I have been working with external developers for a long time. I work for an insurance company. I do business process analysis. I supervise the development and implementation of various systems. From the portal and CRM based on "Bitrix" to the medical systems "Bars Med" and CRM Microsoft. As I feel, I have not reached a professional level in writing technical specifications for developers. In the future, I would like to go to an IT company as a business analyst. Please tell me how to practice and quickly learn how to write technical specifications? So that this knowledge would then come to me in an IT company (is engaged in the development and provision of IT services) I am attaching an
excerpt from my assignment.

Answer 1

All programmers hate this kind of nonsense, where tasks are described in small text and occasionally slurred screenshots are attached.
Master mockups to draw element diagrams, master special programs for creating screenshots (like the one that is built into Yandex.disk and allows you to draw all sorts of arrows and comments on top of the pictures)
Now this will be understandable to all TK, not paperwork.
A couple of mockup programs to help you:
ninjamock.com
https://balsamiq.com/products/mockups/

Answer 2

There should be no screenshots in the TOR at all. Maximum - block diagram.
Screenshots and pictures are not TK, this is a Federal Law - a Functional Task. Do not confuse!
If screenshots are inserted into the TOR, then the TOR for a more or less average project will consist of 100-150 sheets, which is absurd. The requirements must be stated in the TOR. According to which, then a test methodology for the delivery of the project and separately functional tasks for a particular requirement or liver of requirements will be written.
ToR should be easy to control changes. If you have to change screenshots or rewrite an entire chapter to make a change, then hard labor and suffering await you. I stick to no more than 30 pages in the TOR.

Answer 3

In my opinion, the screenshot is not technical specifications, but requirements management. The ToR is a well-structured document that is as clear and unambiguous as possible. I am a developer, for me the main requirements for TK
I personally do not have formal requirements, but there are a lot of templates lying around on the net

Answer 4

I personally would not speak for all programmers. Screenpresso can also be called a good program in terms of screenshots. As for the TK - alas, you have it stupid. What is the second point about? "If you specify zero, then zero will be displayed in the amount."
When choosing goods with the "VHI" type, you should indicate not only the price in rubles, but also the quantity. If the quantity is not specified or is 0, the price must be zero.
Does it look like the truth? Can you hear the difference? You describe what the business tells you. This is not a TOR, this is a business requirement. I wrote how the program should behave.

Answer 5

Write simple conditions so that you will break your brain until you understand what they want from you :) (our teachers usually write like that :))

Answer 6

nobody has learned. and you won't succeed

Answer 7

mastertz.ru

Master TK - a free program for creating technical specifications for a website, software, etc.
The program provides easy creation of a professional TK in accordance with GOST.
It is possible to edit a previously created project, export the results in HTML and Microsoft Word format.
Does not require installation, works from any media.
There is built-in documentation (recommendations, GOSTs).