πŸ“œ ⬆️ ⬇️

Convenient memo and 8 references to documentation in accordance with GOST 34 (automated systems)

One Friday evening, a few years ago, I received an assignment from the manager to prepare the weekend TK for the competition. Apparently, I radiated too much joy from the upcoming weekend, and it was just nice for the boss to take them with something new and interesting, as he thought - I hadn’t been able to work with technical documents before. Now I can not remember what the system was there, but just some kind of monitoring. Saturday morning brought disappointment. Millions of links, hundreds of articles each other more informative. From one abbreviation GOST blew boredom and dust. This is how my acquaintance with the GOST 34 family of automated systems began. Under the cut a handy memo on this very GOST, which quite by chance once met on the open spaces of the network and helped to systematize the data in a notable pile of documents.

gost_1.png

This is how the memo looks and here is the link to download, print and post to the place of honor.

gost_2.jpg
')
For your convenience, collected links to the documents. In principle, this will be enough to satisfy the most demanding customer. Some of these standards will soon be 30 years old, and in part they may not meet current needs. But in terms of completeness of coverage (and you could not even think about some things) they have no equal in IT. If you are just starting your career path, I recommend at least once to look at these documents, so that later you don’t wrestle with the sequence of creation and the composition of these documents. And this brochure is just a must have on the wall near your workplace.

β†’ GOST 34.003-90 Terms and Definitions

β†’ GOST 34.201-89 Types, completeness and designation of documents when creating automated systems

β†’ GOST 34.601-90 GOST 34.601-90. Automated systems. Stages of creation

β†’ GOST 34.602-89 Terms of Reference for the creation of an automated system

β†’ GOST 34.603-92 Types of testing automated systems

β†’ RD 50-34.698-90 Automated systems. Requirements for the content of documents

β†’ ESKD (GOST 2) Unified system for design documentation

β†’ ESPD (GOST 19) Unified system for program documentation

Tell us how often you have to deal with the State Standards of this series and how well you manage to apply these recommendations in the documentation process. Below is a small survey. Thanks in advance for the feedback!

Author of the article: Anton Kasimov , architect of control systems, Jet Infosystems.

Source: https://habr.com/ru/post/322018/


All Articles