GOST 19.001 77 general provisions. Classification and designation of espd standards

  • 03.03.2020

Name:

General provisions

Active

Introduction date:

Cancellation date:

Replaced with:

Text GOST 19.001-77 Unified system of program documentation. General provisions

NATIONAL STANDARDS

UNIFIED SYSTEM OF PROGRAM DOCUMENTATION

Official edition

Standartinform

Attention readers!

federal state unitary enterprise The Russian Scientific and Technical Information Center for Standardization, Metrology and Conformity Assessment prepared for publication in 2010 collections of national standards compiled according to the sectoral (thematic) principle.

The collections include official publications of the standards with all changes and amendments approved (adopted) on the date of publication of the collection.

In 2010, collections of standards will be published on the following topics:

Leguminous crops. Specifications Cereal crops. Specifications Confectionery products. Analysis Methods

Potatoes, vegetables, gourds. Specifications Cereal products. Specifications. Analysis Methods

Margarines, fats for cooking, confectionery and baking industries Stone fruits. Specifications Meat products. Analysis Methods

Processed fruits and vegetables. Analysis Methods

Wheat processing products. Pasta. Specifications. Analysis Methods

Food products, canned food. Methods of microbiological analysis

Live fish, chilled and frozen. Specifications

Fish and fish products. Analysis methods. Marking. Package

Oilseeds

Juices. Specifications. Analysis Methods

Raw materials and food products. Methods for determination of toxic elements Unified system design documentation(ESKD)

Unified system of program documentation (ESPD)

Unified system of technological documentation (ESTD)

System for the development and production of products

Hex head bolts and hex nuts up to Ø 48 mm. Design and dimensions

Oil and oil products. General rules and norms

Pipes metal and connecting parts to them. Part 2. Threaded pipes. Pipes metal and connecting parts to them. Part 4. Pipes made of ferrous metals and alloys, cast and connecting parts to them. Main dimensions. Methods technological tests pipes

© Standartinform, 2010

GOST 19.001-77

INTERSTATE STANDARD

UNIFIED SYSTEM OF PROGRAM DOCUMENTATION

GENERAL PROVISIONS

Official edition

Standartinform

INTERSTATE STANDARD

Unified system of program documentation

GENERAL PROVISIONS

Unified system for program documentation General principles

By the Decree of the State Committee of Standards of the Council of Ministers of the USSR dated May 20, 1977 No. 1268, the introduction date was set

This standard establishes the purpose, scope, classification and designation rules for the standards included in the Unified System for Program Documentation (ESPD) complex.

1. PURPOSE OF ESPD

ITS Unified System of Program Documentation - complex state standards, establishing interconnected rules for the development, design and circulation of programs and program documentation.

1.2. The ESPD standards establish requirements governing the development, maintenance, production and operation of programs, which makes it possible to:

unification of software products for the mutual exchange of programs and the use of previously developed programs in new developments;

reducing labor intensity and increasing the efficiency of development, maintenance, manufacture and operation of software products;

automation of production and storage of program documentation.

Program maintenance includes the analysis of functioning, development and improvement of the program, as well as making changes to it in order to eliminate errors.

2. SCOPE AND COMPOSITION OF THE ESPD

2.E The rules and regulations established in the ESPD standards apply to programs and software documentation for computers, complexes and systems, regardless of their purpose and scope.

2.2. The ESPD includes:

fundamental and organizational and methodological standards;

standards that define the forms and content of program documents used in data processing;

standards that provide automation of the development of program documents.

2.3. The development of organizational and methodological documentation that defines and regulates the activities of organizations for the development, maintenance and operation of programs should be carried out on the basis of ESPD standards.

Official Edition ★

Reprint prohibited

) Standards Publishing House, 1977 © STANDARTINFORM, 2010

Reissue. January 2010 5

3. CLASSIFICATION AND DESIGNATION OF ESPD STANDARDS

3.1. ESPD standards are divided into groups shown in the table.

3.2. The designations of the ESPD standards are built on a classification basis.

The designation of the ESPD standard should include: the numbers 19 assigned to the class of ESPD standards;

one digit (after the dot) indicating the code of the classification group of standards specified in and. 3.1;

a two-digit number that determines the serial number of the standard in the group; a two-digit number (after the dash) indicating the year the standard was registered.

An example of the designation of the standard “Unified system of program documentation. General provisions": GOST 19. 0 01-77

Year of registration of the standard

Ordinal number of the standard in the group

Classification group of standards

Class (ESPD standards)

  • GOST 19.001-77 Unified system of program documentation. General provisions
  • GOST 19.005-85 Unified system of program documentation. P-schemes of algorithms and programs. Conditional graphic designations and execution rules
  • GOST 19.101-77 Unified system of program documentation. Types of programs and program documents
  • GOST 19.102-77 Unified system of program documentation. Development stages
  • GOST 19.103-77 Unified system of program documentation. Designations of programs and program documents
  • GOST 19.104-78 Unified system of program documentation. Basic inscriptions
  • GOST 19.105-78 Unified system of program documentation. General requirements for program documents
  • GOST 19.106-78 Unified system of program documentation. Requirements for program documents made in printed form
  • GOST 19.201-78 Unified system of program documentation. Technical task. Requirements for content and design
  • GOST 19.202-78 Unified system of program documentation. Specification. Requirements for content and design
  • GOST 19.301-79 Unified system of program documentation. Program and test procedure. Requirements for content and design
  • GOST 19.401-78 Unified system of program documentation. Program text. Requirements for content and design
  • GOST 19.402-78 Unified system of program documentation. Program description
  • GOST 19.403-79 Unified system of program documentation. List of original holders
  • GOST 19.404-79 Unified system of program documentation. Explanatory note. Requirements for content and design
  • GOST 19.501-78 Unified system of program documentation. Form. Requirements for content and design
  • GOST 19.502-78 Unified system of program documentation. Description of the application. Requirements for content and design
  • GOST 19.503-79 Unified system of program documentation. System programmer's guide. Requirements for content and design
  • GOST 19.504-79 Unified system of program documentation. Programmer's Guide. Requirements for content and design
  • GOST 19.505-79 Unified system of program documentation. Operator's manual. Requirements for content and design
  • GOST 19.506-79 Unified system of program documentation. Description of the language. Requirements for content and design
  • GOST 19.507-79 Unified system of program documentation. Statement of operational documents
  • GOST 19.508-79 Unified system of program documentation. Maintenance manual. Requirements for content and design
  • GOST 19.601-78 Unified system of program documentation. General rules for duplication, accounting and storage
  • GOST 19.602-78 Unified system of program documentation. Rules for duplication, accounting and storage of program documents made in printed form
  • GOST 19.603-78 Unified system of program documentation. General rules for making changes
  • GOST 19.604-78 Unified system of program documentation. Rules for making changes to program documents made in printed form
  • GOST 28195-89 Software quality assessment. General provisions
  • GOST 34.601-90 Information technology. Set of standards for automated systems. Automated systems. Stages of creation
  • GOST 34.602-89 Information technology. Set of standards for automated systems. Terms of reference for the creation of an automated system
  • GOST R 56447-2015 Gas, gas condensate, oil and gas and oil and gas condensate fields. Seismic data processing and interpretation software. Basic functional and technical requirements
  • GOST R 56448-2015 Gas, gas condensate, oil and gas and oil and gas condensate fields. Software for geological modeling of deposits. Basic functional and technical requirements
  • GOST R 56450-2015 Gas, gas condensate, oil and gas and oil and gas condensate fields. Software for hydrodynamic modeling of hydrocarbon collection and treatment systems. Basic functional and technical requirements
  • GOST R 55711-2013 Complex of technical means for automated adaptive HF (HF) duplex radio communication. Work algorithms
  • GOST R 56566-2015 Information technologies. Process evaluation. Part 9: Target Process Profiles
  • GOST R 55692-2013 Electronic modules. Methods for compiling and debugging test programs for automated control
  • GOST R 56449-2015 Gas, gas condensate, oil and gas and oil and gas condensate fields. Software for hydrodynamic modeling of deposits. Basic functional and technical requirements
  • GOST R 56413-2015 Information technologies. European profiles of professions in the ICT sector
  • GOST R ISO/IEC 15026-1-2016 System and software engineering. Guaranteeing systems and software. Part 1. Concepts and vocabulary
  • GOST R ISO/IEC 15026-4-2016 System and software engineering. Guaranteeing systems and software. Part 4: Lifecycle Assurances
  • GOST R 56920-2016 System and software engineering. Software testing. Part 1. Concepts and definitions
  • GOST R 56921-2016 System and software engineering. Software testing. Part 2. Testing processes
  • GOST R ISO/IEC 26555-2016 System and software engineering. Tools and methods of technical management of the product line
  • GOST R ISO/IEC 29155-1-2016 System and software engineering. The structure of a comparative analysis of the effectiveness of the implementation of information technology projects. Part 1. Concepts and definitions
  • GOST R 54360-2011 Laboratory information management systems (LIMS). Standard Guide for LIMS Validation
  • GOST R 54593-2011 Information technologies. Free software. General provisions
  • GOST R ISO/IEC 12207-2010 Information technology. System and software engineering. Software Life Cycle Processes
  • GOST R 53798-2010 Standard Guide for Laboratory Information Management Systems (LIMS)
  • GOST R ISO/IEC 15504-1-2009 Information technologies. Process evaluation. Part 1. Concept and vocabulary
  • GOST R ISO/IEC 15504-2-2009 Information technology. Process evaluation. Part 2: Conducting an assessment
  • GOST R ISO/IEC 15504-3-2009 Information technology. Process evaluation. Part 3. Assessment guidance
  • GOST R 57098-2016 System and software engineering. Life cycle management. Guidelines for describing the process
  • GOST R 57100-2016 System and software engineering. Architecture Description
  • GOST R 57101-2016 System and software engineering. Life cycle processes. Project management
  • GOST R 57102-2016 Information technologies. System and software engineering. Life cycle management. Part 2: Guidance for the application of ISO/IEC 15288
  • GOST R 57122-2016 Gas, gas condensate, oil and gas and oil and gas condensate fields. Well construction design software. Basic functional and technical requirements
  • GOST R 57193-2016 System and software engineering. Systems Life Cycle Processes
  • GOST R ISO/IEC 15504-5-2016 Information technology. Process evaluation. Part 5: Software Life Cycle Process Assessment Model Sample
  • GOST 34009-2016 Means and control systems for railway traction rolling stock. Software requirements
  • GOST R 57318-2016 Industrial automation systems and integration. Application and management of systems engineering processes
  • GOST R ISO/IEC 25001-2017 Information technology. System and software engineering. Requirements and quality assessment of systems and software (SQuaRE). Planning and management
  • GOST R ISO/IEC 33004-2017 Information technology. Process evaluation. Requirements for Process Reference Models, Process Assessment Models and Maturity Models
  • GOST R ISO/IEC 15414-2017 Information technology. Open distributed processing. reference model. Enterprise Description Language
  • GOST IEC 60848-2016 GRAFCET Specification Language for Sequential Function Charts
  • GOST R ISO/IEC 25051-2017 Information technology. System and software engineering. Requirements and quality assessment of systems and software (SQuaRE). Quality Requirements for Ready-to-Use Software (RUSP) and Testing Instructions
  • GOST R ISO/IEC 33001-2017 Information technology. Process evaluation. Concepts and terminology
  • GOST R ISO/IEC 33002-2017 Information technology. Process evaluation. Requirements for conducting a process assessment
  • GOST R ISO/IEC 33003-2017 Information technology. Process evaluation. Requirements for process measurement systems
  • GOST R ISO/IEC 33020-2017 Information technology. Process evaluation. Process measurement system for evaluating process capabilities
  • GOST R 57640-2017 Information technologies. Process Reference Model (RPM) for Information Security Management
  • GOST R ISO/IEC 30121-2017 Information technology. The concept of risk management associated with the conduct of forensic examination of evidence presented in digital form
  • GOST R 58041-2017 Gas, gas condensate, oil and gas and oil and gas condensate fields. System of standards for software for solving problems of prospecting, exploration and development of deposits. Basic provisions and technical requirements
  • GOST R 58042-2017 Gas, gas condensate, oil and gas and oil and gas condensate fields. Basic requirements for the initial data of software systems for solving problems of prospecting, exploration and development of deposits
  • GOST R ISO/IEC 10746-1-2004 Information technology. Open distributed processing. base model. Part 1. Basic provisions
  • GOST R ISO/IEC 10746-4-2004 Information technology. Open distributed processing. base model. Part 4. Architectural semantics
  • GOST R ISO/IEC 12119-2000 Information technology. Software packages. Quality requirements and testing
  • GOST R ISO/IEC 12207-99 Information technology. Software Life Cycle Processes
  • GOST R ISO/IEC 14764-2002 Information technology. Software Maintenance
  • GOST R ISO/IEC 15026-2002 Information technology. System and Software Integrity Levels
  • GOST R ISO/IEC 15288-2005 Information technology. System engineering. Systems Life Cycle Processes
  • GOST R ISO/IEC 15504-4-2012 Information technology. Process evaluation. Part 4. Guidance on application for process improvement and evaluation
  • GOST R ISO/IEC 15910-2002 Information technology. The process of creating software user documentation

GOST 19.001-77

Group T55

INTERSTATE STANDARD

Unified system of program documentation

GENERAL PROVISIONS

Unified system for program documentation. general principles

Introduction date 1980-01-01


By the Decree of the State Committee of Standards of the Council of Ministers of the USSR dated May 20, 1977 N 1268, the introduction date was set to 01.01.80

REPUBLICATION. January 2010


This standard establishes the purpose, scope, classification and designation rules for the standards included in the Unified System for Program Documentation (ESPD) complex.

1. PURPOSE OF ESPD

1. PURPOSE OF ESPD

1.1. The unified system of program documentation is a set of state standards that establish interconnected rules for the development, design and circulation of programs and program documentation.

1.2. The ESPD standards establish requirements governing the development, maintenance, production and operation of programs, which makes it possible to:

unification of software products for the mutual exchange of programs and the use of previously developed programs in new developments;

reducing labor intensity and increasing the efficiency of development, maintenance, manufacture and operation of software products;

automation of production and storage of program documentation.

Program maintenance includes the analysis of functioning, development and improvement of the program, as well as making changes to it in order to eliminate errors.

2. SCOPE AND COMPOSITION OF THE ESPD

2.1. The rules and regulations established in the ESPD standards apply to programs and software documentation for computers, complexes and systems, regardless of their purpose and scope.

2.2. The ESPD includes:

fundamental and organizational and methodological standards;

standards that define the forms and content of program documents used in data processing;

standards that provide automation of the development of program documents.

2.3. The development of organizational and methodological documentation that defines and regulates the activities of organizations for the development, maintenance and operation of programs should be carried out on the basis of ESPD standards.

3. CLASSIFICATION AND DESIGNATION OF ESPD STANDARDS

3.1. ESPD standards are divided into groups shown in the table.

Group code

Group name

General provisions

Fundamental Standards

Development Documentation Rules

Rules for the execution of manufacturing documentation

Maintenance Documentation Rules

Rules for the implementation of operational documentation

Rules for handling program documentation

Reserve groups

Other standards

3.2. The designations of the ESPD standards are built on a classification basis.

The designation of the ESPD standard should include:

digits 19 assigned to the class of ESPD standards;

one digit (after the dot) indicating the code of the classification group of standards specified in clause 3.1;

a two-digit number that determines the serial number of the standard in the group;

a two-digit number (after the dash) indicating the year the standard was registered.

An example of the designation of the standard "Unified system of program documentation. General provisions":



Electronic text of the document
prepared by CJSC "Kodeks" and checked against:
official publication
Unified software system
documentation: Sat. GOSTs. -
M.: Standartinform, 2010

Attention readers!

The Federal State Unitary Enterprise "Russian Scientific and Technical Center for Information on Standardization, Metrology and Conformity Assessment" prepared for publication in 2010 collections of national standards compiled according to the sectoral (thematic) principle.

The collections include official publications of the standards with all changes and amendments approved (adopted) on the date of publication of the collection.

In 2010, collections of standards will be published on the following topics:

Leguminous crops. Specifications

Cereal crops. Specifications

Confectionery products. Analysis Methods

Potatoes, vegetables, gourds. Specifications

Cereal products. Specifications. Analysis Methods

Margarines, fats for cooking, confectionery and baking industry

Stone fruits. Specifications

Meat products. Analysis Methods

Processed fruits and vegetables. Analysis Methods

Wheat processing products. Pasta. Specifications. Analysis Methods

Food products, canned food. Methods of microbiological analysis

Live fish, chilled and frozen. Specifications

Fish and fish products. Analysis methods. Marking. Package

Oilseeds

Juices. Specifications. Analysis Methods

Raw materials and food products. Methods for determining toxic elements

Unified system for design documentation (ESKD)

Unified system of program documentation (ESPD)

Unified system of technological documentation (ESTD)

System for the development and production of products

Hex head bolts and hex nuts up to Ø 48 mm. Design and dimensions

Oil and oil products. General rules and regulations

Pipes metal and connecting parts to them. Part 2. Threaded pipes. Pipes metal and connecting parts to them. Part 4. Pipes made of ferrous metals and alloys, cast and connecting parts to them. Main dimensions. Methods for technological testing of pipes

INTERSTATE STANDARD

ONE SYSTEM
PROGRAM DOCUMENTATION

GENERAL PROVISIONS

Moscow
Standartinform
2010

INTERSTATE STANDARD

Unified system of program documentation

GENERAL PROVISIONS

Unified System for program documentation.
general principles

GOST
19. 001-77

Reissue. January 2010

By the Decree of the State Committee of Standards of the Council of Ministers of the USSR dated May 20, 1977 No. 1268, the introduction date was set

01.01.80.

This standard establishes the purpose, scope, classification and designation rules for the standards included in the Unified System for Program Documentation (ESPD) complex.

1. PURPOSE OF ESPD

1.1. The unified system of program documentation is a set of state standards that establish interconnected rules for the development, design and circulation of programs and program documentation.

1.2. The ESPD standards establish requirements governing the development, maintenance, production and operation of programs, which makes it possible to:

unification of software products for the mutual exchange of programs and the use of previously developed programs in new developments;

reducing labor intensity and increasing the efficiency of development, maintenance, manufacture and operation of software products;

automation of production and storage of program documentation.

Program maintenance includes the analysis of functioning, development and improvement of the program, as well as making changes to it in order to eliminate errors.

2. SCOPE AND COMPOSITION OF THE ESPD

2.1. The rules and regulations established in the ESPD standards apply to programs and software documentation for computers, complexes and systems, regardless of their purpose and scope.

2.2. The ESPD includes:

fundamental and organizational and methodological standards;

standards that define the forms and content of program documents used in data processing;

standards that provide automation of the development of program documents.

2.3. The development of organizational and methodological documentation that defines and regulates the activities of organizations for the development, maintenance and operation of programs should be carried out on the basis of ESPD standards.

3. CLASSIFICATION AND DESIGNATION OF ESPD STANDARDS

3.1. ESPD standards are divided into groups shown in the table.

3.2. The designations of the ESPD standards are built on a classification basis.

The designation of the ESPD standard should include:

digits 19 assigned to the class of ESPD standards;

one digit (after the dot) indicating the code of the classification group of standards specified in clause 3.1;

a two-digit number that determines the serial number of the standard in the group;

a two-digit number (after the dash) indicating the year the standard was registered.

Name of the document in RussianUnified system of program documentation. General provisions
Name of the document for English language Unified system for program documentation. general principles
Document statusActive
Date of entry into force of the document 01.01.1980
the date latest edition document 04.03.2010
KGS codeT55
OKSTU code 5004;0019

Standard text

This standard establishes the purpose, scope, classification and designation rules for the standards included in the Unified System for Program Documentation (ESPD) complex.

1. Purpose of the ESPD

1.1. The unified system of program documentation is a set of state standards that establish interconnected rules for the development, design and circulation of programs and program documentation.

1.2. The ESPD standards establish requirements governing the development, maintenance, production and operation of programs, which makes it possible to:

    unification of software products for the mutual exchange of programs and the use of previously developed programs in new developments;

    reducing labor intensity and increasing the efficiency of development, maintenance, manufacture and operation of software products;

    automation of production and storage of program documentation.

Program maintenance includes the analysis of functioning, development and improvement of the program, as well as making changes to it in order to eliminate errors.

2. Scope and composition of the ESPD

2.1. The rules and regulations established in the ESPD standards apply to programs and software documentation for computers, complexes and systems, regardless of their purpose and scope.

2.2. The ESPD includes:

    fundamental and organizational and methodological standards;

    standards that define the forms and content of program documents used in data processing;

    standards that provide automation of the development of program documents.

2.3. The development of organizational and methodological documentation that defines and regulates the activities of organizations for the development, maintenance and operation of programs should be carried out on the basis of ESPD standards.

3. Classification and designation of ESPD standards

3.1. ESPD standards are divided into groups shown in the table.

Group codeGroup name
0 General provisions
1 Fundamental Standards
2 Development Documentation Rules
3 Rules for the execution of manufacturing documentation
4 Maintenance Documentation Rules
5 Rules for the implementation of operational documentation
6 Rules for handling program documentation
7 Reserve groups
8
9 Other standards

3.2. The designations of the ESPD standards are built on a classification basis.

STATE STANDARD OF THE UNION OF THE SSR

UNIFIED SYSTEM OF PROGRAM DOCUMENTATION

GENERAL PROVISIONS

GOST 19.001-77

STATE STANDARD OF THE UNION OF THE SSR

By the Decree of the State Committee of Standards of the Council of Ministers of the USSR dated May 20, 1977 No. 1268, the validity period is established

from 01.07.1978

until 07/01/1983

This standard establishes the purpose, scope, classification and designation rules for the standards included in the Unified System for Program Documentation (ESPD) complex.

1. PURPOSE OF ESPD

1.1. The unified system of program documentation is a set of state standards that establish interconnected rules for the development, design and circulation of programs and program documentation.

1.2. The ESPD standards establish requirements governing the development, maintenance, production and operation of programs, which makes it possible to:

unification of software products for mutual exchange of programs ii application of previously developed programs in new developments;

reducing labor intensity and increasing the efficiency of development, maintenance, manufacture and operation of software products;

automation of production and storage of program documentation.

Program maintenance includes the analysis of functioning, development and improvement of the program, as well as making changes to it in order to eliminate errors.

2. SCOPE AND COMPOSITION OF THE ESPD

2.1. The rules and regulations established in the ESPD standards apply to programs and software documentation for computers, complexes and systems, regardless of their purpose and scope.

2.2. The ESPD includes:

fundamental and organizational and methodological standards;

standards that define the forms and content of program documents used in data processing;

standards that provide automation of the development of program documents.

23. The development of organizational and methodological documentation that defines and regulates the activities of organizations for the development, maintenance and operation of programs should be carried out on the basis of ESPD standards.