Preparation of technical specifications (TZ) on the site using GOST

I was interested at one time with technical documentation and I found such interesting standards on the open spaces of my native Internet. Standards is not easy, but GOST. Of course, they were not created specifically for the production of documentation for the sites, but they are quite enough to create a sufficiently serious technical task (hereinafter - TK) for a site of average complexity. I think that with a skillful approach, you can use them in the preparation of any documentation relating to Internet technologies.

The first thing I would like to draw attention to is the official standards. The most relevant to our topic in this case will be:

• “TECHNICAL TASK ON CREATING AN AUTOMATED SYSTEM” (GOST 34.602-89) is a capacious piece of work with all possible types of software, which makes the document very spatial in relation to the creation of documentation for the sites, but serves as a good universal documentary basis for drawing up the TOR.

• "TECHNICAL TASK. REQUIREMENTS FOR THE CONTENT AND DECORATION" (GOST 19.201-78) - more suitable for the design of TK to the site, In my opinion - a shorter version of the previous GOST and more convenient to use, because practically, it is a ready-made set of sections of TK as a whole.
')
It is convenient to use them in a pair, since in the first (GOST 34.602-89) there are forms of the title and last sheet of the TK and how to formalize the document as a whole so that it has legal force, and in the second (GOST 19.201-78) the very principle of creating the TZ is described. The points of the second GOST and their sequence quite allow us to use it as a plan for drawing up the TK.

As a lyrical digression, I want to draw attention to one, regularly arising question - who should provide the TK, the customer or performer? Many performers believe that it is impossible to work without TK from the customer, many customers refuse to write TZ, because “this is not our job, you need to write to you”. In this case both sides are wrong. In my opinion, the very design of the TZ should be done by the performer, but taking into account the wishes of the customer. That is, the work of drawing up the TZ should be joint! You can not cross it on each other. Ideally, it is best to meet on a neutral territory and solve all controversial issues immediately over a cup of hot coffee. This will save a lot of time, both for the customer and the performer, since I do not have to find out what was meant by one or another point in the TK and would allow to immediately solve all disputed issues in a calm atmosphere. In the end, both win - the customer will be calm that the performer understood him correctly, and the performer, in turn, will be able to immediately exclude options when the customer wants the impossible. Immediately it will be possible to negotiate all deadlines and other nuances.
If there is no possibility of a personal meeting, the customer can transfer in writing all his wishes to the performer - the performer and the customer already correct the dubious points and decide jointly controversial issues in the process of communication via Skype, ICQ, e-mail or phone and bring the document to its final form. which will suit both sides.

And, of course, it is worth remembering that a document properly drawn up and signed by signatures is the key to the security of both parties who signed it.