Home Vegetables Unified system of program documentation new guests. Download guest. unified system of program documentation. See what the "Unified System for Program Documentation" is in other dictionaries

Vegetables

Unified system of program documentation new guests. Download guest. unified system of program documentation. See what the "Unified System for Program Documentation" is in other dictionaries

Establishing interrelated rules for the development, design and circulation of programs and program documentation.

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.

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

Since the ESPD is a set of GOSTs, at present its use on the territory of the Russian Federation is only advisory in nature, that is, the ESPD is applied on a voluntary basis (unless otherwise provided by the agreement, contract, separate laws, court decision, etc.).

Encyclopedic YouTube

1 / 3

Panel building calculation

Webinar: What's New in Advance Steel 2018 for Steel Design

Master class #2 "Autodesk Fusion 360 - a unified environment for innovative design

Subtitles

Classification

ESPD standards are divided into groups shown in the table.

List of standards included in the ESPD

GOST 19.001-77. ESPD. General provisions.
GOST 19.002-80. ESPD. Schemes of algorithms and programs. Execution rules. - Replaced by GOST 19.701-90
GOST 19.003-80. ESPD. Schemes of algorithms and programs. Conditional graphic designations. - Replaced by GOST 19.701-90
GOST 19.004-80. ESPD. Terms and Definitions. - Replaced by GOST 19.781-90
GOST 19.005-85. ESPD. P-schemes of algorithms and programs. Conditional graphic designations and execution rules.
GOST 19.101-77. ESPD. Types of programs and program documents.
GOST 19.102-77. ESPD. Development stages.
GOST 19.103-77. ESPD. Designation of programs and program documents.
GOST 19.104-78. ESPD. Basic inscriptions.
GOST 19.105-78. ESPD. General requirements for program documents.
GOST 19.106-78. ESPD. Requirements for program documents made in printed form.
GOST 19.201-78. ESPD. Technical task. Requirements for content and design.
GOST 19.202-78. ESPD. Specification. Requirements for content and design.
GOST 19.301-79. ESPD. Program and test procedure. Requirements for content and design.
GOST 19.401-78. ESPD. Program text. Requirements for content and design.
GOST 19.402-78. ESPD. Program description.
GOST 19.403-79. ESPD. List of holders of originals.
GOST 19.404-79. ESPD. Explanatory note. Requirements for content and design.
GOST 19.501-78. ESPD. Form. Requirements for content and design.
GOST 19.502-78. ESPD. Description of the application. Requirements for content and design.
GOST 19.503-79. ESPD. System programmer's guide. Requirements for content and design.
GOST 19.504-79. ESPD. Programmer's Guide. Requirements for content and design.
GOST 19.505-79. ESPD. Operator's manual. Requirements for content and design.
GOST 19.506-79. ESPD. Description of the language. Requirements for content and design.
GOST 19.507-79. ESPD. List of operating documents.
GOST 19.508-79. ESPD. Maintenance manual. Requirements for containment and formation.
GOST 19.601-78. ESPD. General rules for duplication, accounting and storage.
GOST 19.602-78. ESPD. Rules for duplication, accounting and storage of program documents made in printed form.
GOST 19.603-78. ESPD. General rules for making changes.
GOST 19.604-78. ESPD. Rules for making changes to program documents made in printed form.
GOST 19.701-90 (ISO 5807-85). ESPD. Schemes of algorithms, programs, data and systems. Conventions and rules of execution.
GOST 19781-90. Provision of information processing systems software. Terms and Definitions.

And software documentation.

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.

List of standards included in the ESPD

GOST 19.001-77. ESPD. General provisions.
GOST 19.003-80. ESPD. Schemes of algorithms and programs. Conditional graphic designations.
GOST 19.005-85. ESPD. P-schemes of algorithms and programs. Conditional graphic designations and execution rules.
GOST 19.101-77. ESPD. Types of programs and program documents.
GOST 19.102-77. ESPD. Development stages.
GOST 19.103-77. ESPD. Designation of programs and program documents.
GOST 19.104-78. ESPD. Basic inscriptions.
GOST 19.105-78. ESPD. General requirements for program documents.
GOST 19.106-78. ESPD. Requirements for program documents made in printed form.
GOST 19.201-78. ESPD. Technical task. Requirements for content and design.
GOST 19.202-78. ESPD. Specification. Requirements for content and design.
GOST 19.301-79. ESPD. Program and test procedure. Requirements for content and design.
GOST 19.401-78. ESPD. Program text. Requirements for content and design.
GOST 19.402-78. ESPD. Program description.
GOST 19.403-79. ESPD. List of holders of originals.
GOST 19.404-79. ESPD. Explanatory note. Requirements for content and design.
GOST 19.501-78. ESPD. Form. Requirements for content and design.
GOST 19.502-78. ESPD. Description of the application. Requirements for content and design.
GOST 19.503-79. ESPD. System programmer's guide. Requirements for content and design.
GOST 19.504-79. ESPD. Programmer's Guide. Requirements for content and design.
GOST 19.505-79. ESPD. Operator's manual. Requirements for content and design.
GOST 19.506-79. ESPD. Description of the language. Requirements for content and design.
GOST 19.507-79. ESPD. List of operating documents.
GOST 19.508-79. ESPD. Maintenance manual. Requirements for content and design.
GOST 19.601-78. ESPD. General rules for duplication, accounting and storage.
GOST 19.602-78. ESPD. Rules for duplication, accounting and storage of program documents made in printed form.
GOST 19.603-78. ESPD. General rules for making changes.
GOST 19.604-78. ESPD. Rules for making changes to program documents made in printed form.
GOST 19.701-90 (ISO 5807-85). ESPD. Schemes of algorithms, programs, data and systems. Conventions and rules of execution.

Links

Wikimedia Foundation. 2010 .

See what the "Unified System for Program Documentation" is in other dictionaries:

- (ESKD) a set of state standards that establish interrelated rules, requirements and norms for the development, execution and circulation of design documentation developed and applied at all stages of the life cycle ... Wikipedia

system- 4.48 system combination of interacting elements organized to achieve one or more stated objectives Note 1 to entry: A system can be viewed as a product or the services it provides. Note 2 In practice… …

RD 153-34.1-35.521-00: Guidelines. Composition and maintenance of operational documentation in the workshops of automated process control systems (TAI) of thermal power plants- Terminology RD 153 34.1 35.521 00: Guidelines. The composition and maintenance of operational documentation in the workshops of automated process control systems (TAI) of thermal power plants: 1. Automated process control system (APCS) System ... ... Dictionary-reference book of terms of normative and technical documentation

- (EIS) is a set of organizational, technical, software and information tools combined into a single system for the purpose of collecting, storing, processing and issuing the necessary information intended to perform the functions ... ... Wikipedia

ESPD- A unified system of program documentation ... Dictionary of abbreviations of the Russian language

The Unified Program Documentation System (ESPD) is a set of state standards that establish interrelated rules for the development, execution and circulation of programs and program documentation. The ESPD standards establish requirements, ... ... Wikipedia

- (TOR, terms of reference) the source document for the development and testing of the product. Contents 1 The concept of TK 2 The place of TK in structures ... Wikipedia

operational documentation- 30 operational documentation Formwork documentation, made in accordance with the requirements of GOST 2.601 95 (passport, operating instructions, etc.)

Unified system of program documentation. Schemes of algorithms and programs. Execution rules.

Unified system of program documentation. Schemes of algorithms and programs. Conditional graphic symbols

Unified system of program documentation. Terms and Definitions.

Unified system of program documentation. P-schemes of algorithms and programs.

Unified system of program documentation. Types of programs and program documents.

Unified system of program documentation. Development stages.

Unified system of program documentation. Designations of programs and program documents.

Unified system of program documentation. Basic inscriptions.

Unified system of program documentation. General requirements for program documents.

Unified system of program documentation. Requirements for program documents made in printed form.

Unified system of program documentation. Technical task. Requirements for content and design.

Unified system of program documentation. Specification. Requirements for content and design.

Unified system of program documentation. Program and test procedure. Requirements for content and design.

Unified system of program documentation. Program text. Requirements for content and design.

Unified system of program documentation. Program description.

Unified system of program documentation. List of holders of originals.

Unified system of program documentation. Explanatory note. Requirements for content and design.

Unified system of program documentation. Form. Requirements for content and design.

Unified system of program documentation. General description. Requirements for creation and design.

Unified system of program documentation. System programmer's guide. Requirements for content and design.

Unified system of program documentation. Programmer's Guide. Requirements for content and design.

Unified system of program documentation. Operator's manual. Requirements for content and design.

Unified system of program documentation. Description of the language. Requirements for content and design.

Unified system of program documentation. List of operating documents.

Unified system of program documentation. Maintenance manual. Requirements for content and design.

Unified system of program documentation. General rules for duplication, accounting and storage.

Unified system of program documentation. Rules for duplication, accounting and storage of program documents made in printed form.

Unified system of program documentation. General rules for making changes.

Unified system of program documentation. Rules for making changes to program documents made in printed form.

ESPD - refers to the complex systems of general technical standards

The ESPD is a system of interstate standards of the CIS countries operating on the territory of the Russian Federation, based on an interstate agreement on standardization. The ESPD standards cover that part of the documentation that is created during the development of software tools and is mostly related to documenting the functional characteristics of software tools. ESPD standards are advisory in nature

ESPD is a set of state standards that establish interconnected rules for the development, execution and circulation of programs and program documentation

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

1. Unification of software products for the mutual exchange of programs and the use of previously developed programs in new developments

2. Reducing labor intensity and increasing the efficiency of development, maintenance, production and operation of software products

3. Automation, production and storage of program documentation

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

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

The ESPD includes:

1. Fundamental and organizational and methodological standards

2. Standards defining the forms and content of policy documents used in data processing

3. Standards for automating the development of policy documents

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

ESPD standards are divided into classification groups

ESPD standards are designated as follows:

GOST 19.001-77

19 - belonging of standards to ESPD

0 - General

77 - year of approval

GOST 19.503-79- system programmer's guide. Requirements for content and design. An abstract and content is required. The System Programmer's Guide should contain the following sections:

1. General information about the program

The purpose and functions of the program and information about the hardware and software that ensure the implementation of this program

2. Structure of the program

Information about the structure of the program, its constituent parts, about the links between the constituent parts, and about links with other programs

3. Program setting

Description of actions for setting up the program for a specific application (setting up the composition of technical means, selection of functions, etc.)

4. Checking the program

Description of verification methods that allow you to give general conclusions about the operability of the program (test cases, run methods, results)

5. Additional features

Description of additional sections, functionality of the program and ways to select them

6. Message to the system programmer

Texts of messages issued during the execution of the program, a description of their content and actions to be performed on these messages

7. List of documents

Depending on the features of the document, it is allowed to combine individual sections and introduce new ones. In justified cases, it is allowed not to give the section "additional features", and in the names of the sections - to omit the word program, or replace it with the name of the program

Additional materials (examples, illustrations, tables, graphs…)

GOST 19.504-79- programmer's guide. Requirements for content and design. Abstract and content are required. The programmer's manual should contain the following sections:

1. Purpose and conditions of use

Purpose and functions, conditions necessary for implementation (RAM size, requirements for the composition and parameters of peripheral devices, software requirements)

2. Characteristics of the program

Description of the main characteristics and features of the program (temporary characteristics of the operating mode, means of monitoring the correct execution and self-healing of the program)

3. Appeal to the program

Description of the procedures for calling the program (methods of transferring control and data parameters)

4. I/O data

Description of the organization of I/O information and, if necessary, its coding

5. Message

Texts of messages issued to the programmer or operator during the execution of the program, a description of their content and actions to be performed on these messages

6. List of documents

Depending on the features of the document, it is allowed to combine individual sections and introduce new ones. Additional materials (examples, illustrations, tables, graphs…)

GOST 19.505-79- operator's manual. Requirements for content and design. Abstract and content are required. The operator's manual should contain the following sections:

1. Purpose of the program

Information about the purpose and information sufficient to understand the functions of the program and its operation

2. Program execution conditions

Conditions necessary for the execution of the program (minimum and (or) maximum composition of hardware and software)

3. Program execution

The sequence of operator actions that ensure the loading, launch and termination of the program (a description of the functions, format and possible options for commands with which the operator loads and controls the execution of the program, as well as the program's responses to these commands should be given

4. Message to the operator

Texts of messages issued during the execution of the program, description of their content and corresponding actions of the operator (actions of the operator in case of failure, the possibility of restarting the program ...)

5. List of documents

Depending on the features of the document, it is allowed to combine individual sections and introduce new ones. It is allowed to illustrate the content of sections with explanatory examples, tables, diagrams and graphs. In the annex to the operator's manual, it is allowed to include various materials that are inappropriate to be included in sections of the manual

GOST 19.101-77

Group T55

INTERSTATE STANDARD

Unified system of program documentation

TYPES OF PROGRAMS AND PROGRAM DOCUMENTS

Unified system for program documentation. Types of programs and program documents

MKS 35.080

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 date of introduction was set to 01.01.80

EDITION (January 2010) with Amendment No. 1 approved in June 1981 (IUS 9-81).

This standard establishes the types of programs and software documents for computers, complexes and systems, regardless of their purpose and scope.

The standard fully complies with ST SEV 1626-79.

(Changed edition, Rev. N 1).

1. TYPES OF PROGRAMS

1.1. The program (according to GOST 19781-90) may be identified and used independently and (or) as part of other programs.

1.2. Programs are divided into types given in table.1.

Table 1


Program type	Definition
Component	A program considered as a whole, performing a complete function and used independently or as part of a complex
Complex	A program consisting of two or more components and (or) complexes that perform interrelated functions and is used independently or as part of another complex

1.3. The documentation developed for the program can be used for the implementation and transfer of the program on data carriers, as well as for the manufacture of the software product.

1.2, 1.3. (Changed edition, Rev. N 1).

2. TYPES OF PROGRAM DOCUMENTS

2.1. Software documents include documents containing information necessary for the development, manufacture, maintenance and operation of programs.

2.2. Types of program documents and their content are given in Table 2.

table 2


Type of policy document
Specification	The composition of the program and documentation for it
	List of enterprises that store the originals of program documents
Program text	Recording the program with the necessary comments
Program description	Information about the logical structure and functioning of the program
	Requirements to be verified when testing the program, as well as the procedure and methods for their control
Technical task	Purpose and scope of the program, technical, technical, economic and special requirements for the program, necessary stages and terms of development, types of tests
Explanatory note	Scheme of the algorithm, a general description of the algorithm and (or) the functioning of the program, as well as the rationale for the adopted technical and technical and economic solutions
Operating documents	Information for ensuring the functioning and operation of the program

2.3. Types of operational documents and their content are given in Table 3.

Table 3


Type of operational document
	List of operational documents for the program
Form	The main characteristics of the program, completeness and information about the operation of the program
Application Description	Information about the purpose of the program, scope, applied methods, class of tasks to be solved, restrictions on application, minimum configuration of technical means
	Information for testing, ensuring the functioning and tuning of the program for the conditions of a particular application
Programmer's Guide	Information for using the program
Operator's manual	Information to ensure the procedure for communication between the operator and the computer system during the execution of the program
Language description	Description of the syntax and semantics of the language
	Information for the use of test and diagnostic programs in the maintenance of technical means

2.4. Depending on the method of implementation and the nature of the application, program documents are divided into the original, duplicate and copy (GOST 2.102-68), intended for the development, maintenance and operation of the program.

2.5. Types of program documents developed at different stages and their codes are given in Table 4.

Table 4


The code document type	Type of document	Development stages
		Preliminary design	Technical project	working draft
				component	complex
	Specification
	List of original holders
	Program text
	Program description
	Statement of operational documents
	Form
	Application Description
	System Programmer's Guide
	Programmer's Guide
	Operator's manual
	Language description
	Service Manual
	Test program and methodology
	Explanatory note
	Other documents

Legend:

- the document is obligatory;

- the document is obligatory for the components having independent application;

- the need to draw up a document is determined at the stage of development and approval of the terms of reference;

- - the document is not compiled.

2.2-2.5. (Changed edition, Rev. N 1).

2.6. It is allowed to combine certain types of operational documents (with the exception of the statement of operational documents and the form). The need to combine these documents is indicated in the terms of reference. The merged document is assigned the name and designation of one of the merged documents.

The merged documents must contain the information that must be included in each merged document.

2.7. At the stage of development and approval of the terms of reference, the need to draw up technical conditions containing requirements for the manufacture, control and acceptance of the program is determined.

Specifications are developed at the stage "Detailed design".

2.8. The need to draw up a technical specification for components that are not intended for independent use, and complexes included in other complexes, is determined by agreement with the customer.

(Introduced additionally, Rev. N 1).

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