Answer the question
In order to leave comments, you need to log in
How to write a clear technical specification without using GOST?
I read that GOST is described for the terms of reference for software development, but there is a question, most likely naive, I think that even large companies do not use it in the description of TK. Is it so? If you have experience, tell me how to form technical specifications in small companies up to 10 people in the IT department. Now I am doing TK according to the principle:
1. Description 2.
Conditions 3. Additional
requirements for the task.
I also try to write documentation, even most likely detailed descriptions of the added functionality, so that any employee of the company can read, understand, and even use it.
If you have experience in PM, tell me about these aspects of work - what should I take as a basis, am I doing it right?
Answer the question
In order to leave comments, you need to log in
I have never come across TK for 19 (ESPD), but I constantly work with TK for 34 (AS). For those who say that GOST is about bureaucracy, I recommend creating an automated system from scratch, at least on the scale of one city, in which at least 20 people will work, within a limited time frame, and work with the infobase on it. It will immediately become clear why GOST 34 is needed, and PMI for what, and a project for the system.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question