February 17, 2017 at 06:20Convenient memo and 8 links to documentation according to GOST 34 (automated systems)
One Friday evening a few years ago, I received a task from the head to prepare the ToR for the competition over the weekend. Apparently, I too radiated joy from the upcoming weekend, and the boss simply was pleased to take them with something new and interesting, as he thought - because before that I had never worked with technical documents. Now I can’t recall what kind of system there was, but definitely some kind of monitoring. Saturday morning brought disappointment. Millions of links, hundreds of articles, one another more informative. From one abbreviation GOST blew boredom and dust. That’s how my acquaintance with the GOST 34 family of automated systems began. Under the cut, a convenient memo according to this very GOST, which quite by chance once met in the vast expanses of the network and helped to systematize data in a noble pile of documents.
This is how the memo looks and here is the link for downloading, printing and posting to the place of honor.
For your convenience, I have collected links to the above documents. In principle, this will be enough to satisfy the needs of the most demanding customer. Some of these standards will soon turn 30 years old, and in part they may not meet modern requirements. But in terms of completeness of coverage (and you might not have thought of some things), they have no equal in IT. If you are just starting your career path, I recommend that you look at these documents at least once so that you don’t have to puzzle over the sequence of creation and composition of these documents. And this brochure is simply must have on the wall at 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. Stage of creation
→ GOST 34.602-89 Terms of Reference for the creation of an automated system
→ GOST 34.603-92 Types of tests for 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 GOSTs of this series and how you manage to apply these recommendations in the process of compiling documentation. And below is a small survey. Thanks in advance for the feedback!
Article author: Anton Kasimov , architect of control systems, Jet Infosystems company.
This is how the memo looks and here is the link for downloading, printing and posting to the place of honor.
For your convenience, I have collected links to the above documents. In principle, this will be enough to satisfy the needs of the most demanding customer. Some of these standards will soon turn 30 years old, and in part they may not meet modern requirements. But in terms of completeness of coverage (and you might not have thought of some things), they have no equal in IT. If you are just starting your career path, I recommend that you look at these documents at least once so that you don’t have to puzzle over the sequence of creation and composition of these documents. And this brochure is simply must have on the wall at 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. Stage of creation
→ GOST 34.602-89 Terms of Reference for the creation of an automated system
→ GOST 34.603-92 Types of tests for 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 GOSTs of this series and how you manage to apply these recommendations in the process of compiling documentation. And below is a small survey. Thanks in advance for the feedback!
Article author: Anton Kasimov , architect of control systems, Jet Infosystems company.
Only registered users can participate in the survey. Please come in.
In what cases do you draw up design documentation for an automated system in accordance with GOST?
- 24.4% Always, and this is my credo 23
- 43.6% Only when such are the requirements of the customer 41
- 35.1% I make out in any form, but following some recommendations of GOST 33
- 10.6% I make out in any form (my own know-how) 10
- 2.1% Own option (please describe in the comments) 2
