Consulting in the field of information technology (IT consulting). Putting the information system into operation The information system is being put into operation

The key document defining the interaction of the parties when implementing software solutions is the technical specification, which contains a set of requirements for the functionality of the software solution and verification and acceptance criteria. The main question that the technical specification should answer is: what should the future system do? The process of preparing technical specifications consists of development, execution, coordination and approval of the document. As a rule, it represents a joint work of specialists from the customer organization and the performing organization. Product IT consultants take part in this work.

The terms of reference are issued by the customer organization to the executing organization (system integrator) for the implementation of software solutions; its content includes previously developed requirements for the IS.

Methodological support for the preparation of technical specifications is GOST 34.602-89 "Information technology. Set of standards for automated systems. Automated systems. Technical specifications for the creation automated system", which defines a list of requirements for the content of the document and testing.

In accordance with the specified standard, the technical specification includes the following sections, which can be divided into subsections:

1. general information;
2. purpose and goals of creation (development) of the system;
3. characteristics of automation objects;
4. system requirements;
5. composition and content of work to create the system;
6. procedure for control and acceptance of the system;
7. requirements for the composition and content of work to prepare the automation object for putting the system into operation;
8. documentation requirements;
9. development sources.

6.7.5. Organization of management of the implementation process based on the creation of joint working groups

Like any project, an implementation project needs its own organizational structure, which should reflect the scope and complexity of implementation tasks. Such a structure should combine the specialized knowledge of employees of functional departments of the organization, knowledge of project management and implementation methodologies software product.

When creating an organizational structure for an implementation project, qualification requirements for participants are developed, labor costs for each stage of implementation are assessed and the required number of participants is determined, the roles and areas of responsibility of each team member are specified, personnel are selected and trained implementation methodologies and the tools used.

An example of the organizational structure of a project for implementing an ERP system at a large industrial enterprise can be the following organizational structure:

• a coordinating committee, which includes the enterprise management and senior managers, including the main project manager, as well as a leading consultant appointed by the managing director;
• the project manager and the implementation project team, which includes the technical team, representatives of key users, consultants, and senior management representatives.

A project's organizational structure may include various collaborative work groups that are assigned specific tasks within the project. This involves appointing different members of the work groups, assigning team leaders, and creating a reporting structure to report on each work group's performance, which is then consolidated into an overall project performance report.

Implementation methodologies Leading software developers provide for certain organizational structures of implementation projects and a clear distribution of roles with corresponding requirements for their skills and knowledge, enshrined in the documentation. An example is the documentation for implementation methodologies AcceleratedSAP, which defines in detail the roles of all participants in the organizational structure of the project, incl. and application consultant.

It should be noted that the organizational structure of the implementation project necessarily includes product IT consultants. Thus, the organizational structure of the SAP project includes Module Leaders, who are responsible for each of the basic modules planned for implementation.

Product IT consultants participate in the development of an implementation strategy as part of the main organizational structure, and also perform certain tasks at individual stages of implementation as part of joint working groups and perform the following main responsibilities:

• training of working group members implementation methodologies, used in this project;
• training users to work with the software product;
• preparation of educational materials;
• responsibility for meeting the deadlines for the implementation of specific modules of the software product;
• development of necessary documentation;
• assistance in the process of customizing the software product to the formulated requirements;
• development of test methods and management of the working group during testing;
• monitoring implementation results and making necessary modifications;
• discussion of user comments and identified project bottlenecks;
• user consultations.

6.7.6. Work in determining the boundaries of the project and implementation plan

The basis for preparing a project charter is the ANSI PMI PMBOK® 3-rd Edition (2004) standard - the main standard that describes all project management processes.

The project charter is the first official document of the project, formally certifying the existence of the project. This document Gives the project manager the authority to commit organizational resources to project operations.

The charter may include:

• general description of the project (leader, start of the project, completion of the project, brief description);
• purpose or rationale for the project, project objectives;
• project boundaries (main work performed);
• project results, system of measures (methods for evaluating results), composition and structure of project reports;
• organizational structure of the project;
• description of the role functions of project participants;
• description of interaction procedures;
• schedule milestones(main dates);
• description of procedures for managing changes, problems and risks;
• project budget.

In the process of preparing the Project Charter and the baseline plan, the main tasks of the product IT consultant are to determine the scope of the implementation project, select an implementation strategy and a deployment strategy (determining the plan for deploying the system from the pilot site to the rest, defined by the scope of the implementation project), planning project activities.

To determine the scope of the project, it is necessary to identify those types of activities and departments that will be affected by automation.

The definition of the project boundaries is carried out at the stage of preliminary survey of the organization. During the preliminary survey, all macro information about the organization is collected: information about the organizational functional structure, areas of activity, work and services performed, scale of the organization. Project boundaries are a specific list of works or business processes that are affected by automation. The project boundaries are the basis for determining the timing of the project and its cost, and planning design work.

Based on the information obtained as a result of the preliminary survey, the product IT consultant generates a report regulating the boundaries of the project. The delineated boundaries of the project are background information to develop the Project Charter.

The implementation strategy defines the approach to implementing a software product in an organization. There are various implementation strategies used by leading software developers. For example, when implementing ERP systems, the “Big Bang”, “Step by Step”, and pilot implementation strategies are usually used.

The “Big Bang” principle involves the simultaneous implementation of all functional modules of a software product and replacement of old systems.

With the "Step by Step" approach, the implementation of functional modules is spread over time, when, after the end of one implementation, another begins.

During pilot implementation, a prototype of the future system is implemented in a certain department of the enterprise, which, if successful, is distributed to other departments taking into account the accumulated experience. In this case, the prototype itself can be implemented according to the “Big Bang” or “Step by Step” principle. After finishing pilot project The system prototype is transferred to the remaining areas in accordance with the deployment strategy. As a rule, minimal changes are made due to the specifics of the sites.

Selecting appropriate implementation and deployment strategies is critical to the success of an implementation project.

Based on the adopted strategies, taking into account the set goals of the project, allocated resources and finances, a basic plan for the implementation project is developed.

Project baseline (cost, schedule) - an officially approved document against which project performance is measured and which is used to manage and monitor project execution. Such a plan includes a plan for the development of resources and a budget, a calendar schedule that determines the timing of the various milestones of the project. Such a plan is not static, it is improved as the project progresses and passes through various stages. Typically a project baseline includes:

• list of stages, substages, tasks and their relationships;
• deadlines for completing stages, substages, tasks, including all types of activities that are included in the implementation schedule;
• deadlines for providing results;
• labor intensity of the stages;
• planned resources by stages.

6.7.7. Development of the "System Design" document

The “System Design” document answers the fundamental question of the implementation project: how will we build the system so that it meets the requirements placed on it. During its development, the final detailing and documentation of all the organization’s requirements regarding certain business processes is carried out, and the necessary adaptation of the software product to user interface specifications is determined.

When developing the System Design document, IT product consultants conduct additional collection of information to confirm and clarify requirements; demonstrate to users the standard functionality of the software product based on test data, which is accompanied by filling out questionnaires with user opinions; identify gaps between the standard functionality of the software product and the requirements; develop appropriate recommendations and measures to eliminate them.

Based on an analysis of the coverage of the requirements by the standard functionality of the software product; analyzing the compliance of the forms of documents and reports of the enterprise with the forms of documents and reports standardly generated in the software product, the IT product consultant compiles a list of necessary modifications of the software product to adapt it to the characteristics of the organization, coordinates fundamental decisions, documents layouts of reports and primary forms, develops regulations for maintaining regulatory standards - reference information.

Since at the time of project implementation the organization may also use other software, when performing the specified work, issues of exporting and importing information and issues of organizing the transfer of data from old systems to the new one are also resolved.

The result of the work carried out is the document “System Design” and technical specifications for carrying out the necessary modifications. In accordance with the technical specifications, the organization performing the work finalizes the functionality of the system.

6.7.8. Managing the software product setup process

Configuring a software product in accordance with the formulated functional requirements and taking into account the characteristics of business processes is a long and labor-intensive process, since when performing this work, the logic of each of the business processes is implemented and a user interface is created.

These works are carried out on the basis of the developed document "System Design" and the corresponding technical specifications. An IT product consultant is involved in managing the process of customizing a software product to the stated requirements.

In general, at this stage, the business processes of the software product are configured in accordance with the organization’s business model; the necessary templates for reports and primary documents are created; means are being developed data export-import With software solutions already operating at the enterprise; directories and classifiers are configured; Additional application modules are being developed.

During the customization management process, the product IT consultant draws up a plan and scenarios for testing the modification of the software product. Testing allows you to ensure that the configured software product works without software errors and meets the agreed requirements subject area and organizational requirements. If errors are identified, work is carried out to eliminate them.

In addition, during the process of setting up a software product, a product consultant uses test data to demonstrate to users how configured business processes are carried out in the software product; coordinates comments and changes. In parallel with demonstrating the layout of the software product, he conducts training for end users, and also takes part in documenting the configuration and preparing documentation for end users.

6.7.9. Work on managing the process of creating a pilot version of the information system

Practical experience shows that work on creating an information system based on a selected software product, especially in large projects, is recommended to begin with pilot project. A pilot implementation project involves the implementation of a software product in a separate area within the framework of selected priority functions. The experience gained is then transferred to other functions and divisions.

A pilot project is a prototype of an information system that implements limited functionality, or covers a narrower scope of implementation, or stores and processes part of the data. Its task is to identify the effect of implementing a given software product in order to make a final decision on the feasibility of implementation on a full scale and to develop a basis for planning work on the implementation project.

Product IT consultant deals with planning issues pilot project. He participates in work to verify the readiness of pilot facilities (selected areas) for implementation, assesses the necessary resources, draws up a plan for converting data from old systems into a new system and a plan for conducting acceptance tests, and conducts user training.

As part of the work performed, the IT product consultant coordinates and approves possible changes, in accordance with which the software product and documentation are finalized.

Upon completion of the work, the product IT consultant participates in the preparation of a report containing the results pilot project.

6.7.10. Training the organization's personnel on the methodology for implementing and using the selected IT solution

The process of training the organization's personnel is supported by the training strategy, technology and training tools.

The training strategy is developed taking into account the stages and scale of implementation of the software product. The product IT consultant determines the general approach to training, plans the main stages and activities for training and certification of the acquired knowledge of personnel, draws up a training schedule, carries out a preliminary calculation of the number of students, and describes the resources required for training.

Training technology includes a list of training courses for which appropriate training programs are developed and is supported by training tools.

The composition of the training tool is usually as follows: documentation for description functionality software product; teaching aids; practical tasks for training and teaching materials; a training copy of the software product filled with test data for demonstration and training; other automated training tools, for example, test systems, electronic training materials.

Documentation of the strategy and technology of training is carried out in the form of preparing a special report, including a description of approaches to training, training courses and training programs, teaching tools used, resources required for training, curricula and training regulations.

An IT product consultant takes part in both the development of training tools and the preparation of a report documenting the training strategy and technologies.

The functional responsibilities of a product IT consultant include training the project team implementation methodologies and user training. In accordance with the developed training calendar plan, he conducts the prescribed training sessions. It should be noted that personnel training includes not only conducting training sessions, but also certifying the ability of personnel to ensure the functioning of the software product and to perform the work necessary for implementation.

6.7.11. Organization of trial operation of the information system and development of test methods

The information system based on the selected software product must prove its performance.

Testing an information system is a process of checking the performance of specified functions of the system, determining and verifying the compliance of the quantitative and qualitative characteristics of the system with the requirements of the technical specifications, identifying and eliminating deficiencies in the actions of the system, in the developed documentation.

In accordance with GOST 34.603-92 "Information technology. Types of testing of automated systems" for information systems The following types of tests are established: preliminary, trial operation, acceptance.

Preliminary tests are carried out after the developer has debugged and tested the supplied software and hardware of the system and provided them with the relevant documents on their readiness for testing, as well as after the personnel have familiarized themselves with the operational documentation.

Trial operation is carried out in order to determine the actual values ​​of the quantitative and qualitative characteristics of the information system and the readiness of personnel to work in the conditions of its functioning, determine the actual effectiveness of the information system, and adjust (if necessary) documentation.

When organizing trial operation information system, the task of a product IT consultant is to develop a document “Program and testing methods”.

The document "Test program and methodology" includes:

• conditions and procedure for the functioning of parts of the information system and the information system as a whole;
• duration trial operation, sufficient to verify the correct functioning of the information system when performing each function of the system and the readiness of personnel to work in the operating conditions of the information system; The work is completed by issuing a completion certificate trial operation and admission to acceptance tests.

  6.7.12. Managing the introduction of an information system into commercial operation and developing its regulations

  The task of managing the introduction of an information system into commercial operation includes the preparation and approval of a detailed plan for the transition to a new system and a plan for its further support, carrying out acceptance tests information system. An IT product consultant takes part in this work.

  As already mentioned, acceptance testing of an information system should be preceded by its trial operation. Based on the results trial operation The experience gained is being disseminated to all areas within the project boundaries in accordance with the adopted information system deployment strategy.

  Acceptance tests of the information system are carried out to determine its compliance with the technical specifications and quality assessment trial operation and resolving the issue of the possibility of accepting the information system for commercial operation.

  In accordance with GOST 34.603-92 "Information technology. Types of testing of automated systems" document "Program acceptance tests" contains:

  • a list of objects allocated in the system for testing and a list of requirements that the objects must meet (with reference to the clauses of the technical specifications);
  • acceptance criteria for the system and its parts;
  • conditions and timing of testing;
  • testing facilities;
  • names of persons responsible for testing;
  • testing methods and processing of their results;
  • list of completed documentation.

  Acceptance tests include checking:

  • completeness and quality of implementation of functions at standard, limiting, critical values ​​of parameters of the automation object and in other conditions of functioning of the information system specified in the technical specifications;
  • fulfilling each requirement related to the system interface;
  • staff work in an interactive mode;
  • means and methods for restoring the functionality of an information system after failures;
  • completeness and quality of operational documentation.

  6.7.13. Organizing monitoring of the results of implementing the information system and making the necessary modifications

  Within the established time frame, the product IT consultant carries out work to organize monitoring of the operation of the information system and make the necessary modifications. These works are aimed at improving the efficiency and performance of the information system. Typically they include the following activities:

  • additional user training;
  • user consultation;
  • monitoring the performance of the information system;
  • analysis of the obtained monitoring results and development of recommendations for making the necessary changes
  • managing the process of making changes and modernizing the information system;
  • development of additional documentation, making changes to existing documentation.

Certificate of acceptance for trial operation is formed based on the results of preliminary tests and includes: conclusions drawn from the results of comprehensive tests; tasks for trial operation.

Working period of the commission

This section of the acceptance certificate provides the start and end dates of the acceptance committee’s work to conduct preliminary tests.

The start of testing is November 1, 2010.
The end of testing is December 31, 2010.
The total duration of testing is 44 working days.

Name of the customer organization, executing organization and co-executing organization

The names of the organizations participating in the testing and those who drew up the certificate of acceptance of the information system for trial operation are given.

The customer organization is JSC "Customer".
The executing organization is CJSC "Implementer".
Co-executing organization – Co-executor LLC (if any).

Composition of AIS functions accepted for trial operation

The composition of AIS functions accepted for trial operation is listed. Functions can be transferred both system-wide and across subsystems. The functions are taken from the section "Requirements for functions performed by the system" of the technical specifications for creating an information system.

List of components of technical, software, information and organizational support checked during trial operation

This section of the acceptance certificate contains a list of tests carried out during trial operation. The list of tests is taken from the "Scope of tests" section of the Test Program.

During trial operation, the tests presented in the table below are subject to testing.

List of documents presented to the commission

This section of the acceptance certificate contains a list of documents provided to the commission necessary for trial operation.

Instructions for creating and maintaining a database (data set), version 1 dated September 12, 2010.
- User Manual, version 1 dated September 14, 2010.
- ...

Assessment of compliance of the adopted AIS with the technical specifications

An assessment of the compliance of the adopted AIS with the technical specifications is provided.

Based on the results of preliminary tests, the System meets the requirements presented in the document: "". Version 1.0.

Main results of acceptance into trial operation

This section of the acceptance certificate lists the main results obtained from the trial operation of the information system.

Based on the results of the trial operation, the following main results should be obtained:
- The system is operational;
- Subsystems of the System – interact;
- The system meets the requirements of the document “Technical specifications for the creation of an automated system”. Version 1.0.;
- All characteristics to be assessed are within acceptable limits.

Commission decision to accept AIS for trial operation

The decision of the commission on the possibility or impossibility of accepting the information system for trial operation is given.

Kovtun M.V. October 2010.

I APPROVED

Deputy Director of the Department of State Regulation in Economics

Ministry of Economic Development of the Russian Federation
______________ V.N. Rudenko
« 09 » _ November __ 2011

ACT OF ENTERING INTO TRIAL OPERATION

Automated information system for project management, developed under the government contract dated November 7, 2011 No. GK-158-OF/D01.
In accordance with the joint decision of the Customer (Ministry of Economic Development of Russia) and the Contractor (OTR 2000 LLC) to put it into trial operation.

Commission consisting of:

Chairman of the commission:

Deputy Director of the Department of State Regulation in Economics V.N. Rudenko,

Commission members:

Acting Head of the Electronic Society Development Department of the Department of State Regulation in Economics S.V. Pushakov,

Advisor to the Department of Methodological Support for the Organization of Interdepartmental Cooperation of the Department of State Regulation in Economics A.V. Matveenko,

Leading consultant of the electronic society development department of the Department of state regulation in economics N.N. Kirsanova,

Head of the direction of OTR 2000 LLC A.I. Kuleshova,

Project Manager of OTR 2000 LLC O.V. Strakhova,

Leading analyst of OTR 2000 LLC Yu.M. Gudkova,

Researcher in the “Real Sector” direction at the Institute of Economics and Economics named after E.T. Gaidar E.R. Batarshina.
since "_ 08 _" November 2011 to "_ 09 _" November 2011 conducted preliminary tests of the applied software automated information system “Project Management Portal” (AIS PPU), installed in the Ministry of Economic Development of Russia.

1. 
   Preliminary tests were considered successfully completed.

1. 
   The main stages of development were completed in accordance with the Technical Specifications.
2. 
   Developed documentation meets requirements operation of software.
3. 
   The software is prepared for trial use.

1. 
   List of functions accepted for trial operation (section “Requirements for functions performed by the system” of the technical specifications):
   1. 
      Maintaining a list of projects.
   2. 
      Working with design entities.
   3. 
      Working with indicators to assess the status of work on the project.
   4. 
      Analytical module.
   5. 
      Document library.

1. 
   List of documents provided to the commission required for trial operation:
   1. 
      “Description of the AIS “Project Management Portal”” (System Passport);
   2. 
      “Instructions for the administrator of the AIS PPU”;
   3. 
      "User's Instructions for AIS PPU";
   4. 
      “Program and testing methods for AIS PPU”;
   5. 
      “Test tasks for AIS PPU”;
   6. 
      “Role instructions describing the procedure for working with AIS PPU as a project management tool “Interdepartmental interaction”.”
2. 
   Commission decision: Accept the software for trial operation from November 9, 2011.

APPLICATIONS:

1. 
   Preliminary test report No. 1
2. 
   Preliminary test report No. 2

Members of the commission:

V.N. Rudenko

S.V. Pushchakov

A.V. Matveenko

N.N. Kirsanova

A.I. Kuleshov

O.V. Strakhova

Yu.M. Gudkova

E.R. Batarshin

THE GOVERNMENT OF MOSCOW

ORDER

On the requirements for commissioning information systems created in the city of Moscow *

Document with changes made:
(Bulletin of the Mayor and Government of Moscow, N 37 (Volume 2), 07/07/2015);
(Bulletin of the Mayor and Government of Moscow, N 57, 10/13/2015);
dated December 5, 2017 N 694-RP (Official website of the Mayor and Government of Moscow www.mos.ru. 12/06/2017);
(Official website of the Mayor and Government of Moscow www.mos.ru, 12/20/2018).
____________________________________________________________________

________________

* Title as amended, put into effect by order of the Moscow Government dated June 30, 2015 N 370-RP..


In order to increase the efficiency of operation of information systems in the city of Moscow:

1. Establish that:

1.1. Executive authorities of the city of Moscow, ensuring the creation of information systems at the expense of the budget of the city of Moscow, organizations subordinate to such executive authorities of the city of Moscow, which, in accordance with legal acts of the city of Moscow, are entrusted with the powers to ensure the creation of information systems (hereinafter also referred to as executive authorities of the city Moscow and organizations providing the creation of information systems), carry out the commissioning of the specified information systems after carrying out acceptance tests confirming the readiness of the information system for commissioning, approval of the information security threat model, as well as the implementation of the necessary measures to protect the information contained in the information system , by drawing up legal acts (local regulations) of the executive authorities of the city of Moscow or organizations ensuring the creation of information systems, respectively (hereinafter referred to as legal acts on the commissioning of information systems) in the form according to the appendix to this order.
by order of the Moscow Government of December 19, 2018 N 891-RP.

1.2. Legal acts on the commissioning of information systems, the creation of which is not provided by the Department information technologies of the city of Moscow, are subject to agreement with the Department of Information Technologies of the city of Moscow. In the course of approval by the Department of Information Technologies of the city of Moscow, additional information about this information system, containing its description and (or) confirming the grounds for its creation, as well as the compliance of the costs of creation, may be requested from the executive authorities of the city of Moscow and organizations providing the creation of information systems information system of the planned cost of work on the development of information systems created in the city of Moscow, determined in accordance with the Methodology for calculating the planned cost of work on the creation, development and modernization of information systems of the city of Moscow, approved by a joint order of the Department of Economic Policy and Development of the City of Moscow and the Department of Information Technologies of the city Moscow.
(Clause as amended, put into effect by order of the Moscow Government dated December 19, 2018 N 891-RP.

1.3. In the event that the use of the information system will be carried out by several executive authorities of the city of Moscow or when using the information system it is planned to interact with residents of the city of Moscow and/or legal entities, the executive authority of the city of Moscow that ensures the creation of an information system or carries out the functions and powers of the founder of a subordinate organization that ensures the creation of an information system, in agreement with the Department of Information Technologies of the city of Moscow, submits in the prescribed manner for consideration by the Moscow Government a draft legal act of the Moscow Government containing a provision on the specified information system, which also reflects the definition of the information system, its tasks and functions, as well as the list of participants in information interaction using the information system and their powers, including the powers to process personal data contained in the information system.
by order of the Moscow Government of December 19, 2018 N 891-RP.

If a legal act of the Moscow Government defines the executive authority of the city of Moscow responsible for organizing the information content of the information system, the powers to organize the processing of personal data contained in the information system, determining the purposes of processing such personal data, as well as the powers of the owner of the information contained in the information system are assigned to the specified executive authority of the city of Moscow. At the same time, the authority to apply technical measures to ensure the security of personal data during their processing in the information system, necessary to fulfill the requirements for the protection of personal data established by the Government of the Russian Federation, is assigned to the operator of the information system.
(Paragraph as amended, put into effect by order of the Moscow Government dated October 6, 2015 N 563-RP.
(Clause 1.3 as amended, put into effect by order of the Moscow Government dated June 30, 2015 N 370-RP.

1.3(1). Measures to protect information contained in information systems implemented by the executive authority of the city of Moscow responsible for organizing the information content of the information system include:

The paragraph is no longer valid - .;

The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;

The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;

The paragraph has lost force - order of the Moscow Government dated December 19, 2018 N 891-RP.;

- determination of the degree of possible damage (possible negative consequences) from violation of confidentiality, integrity or availability of information for each type of information;
(Paragraph additionally included by order of the Moscow Government dated December 19, 2018 N 891-RP)

- assessment of the harm that may be caused to subjects of personal data in case of violation of the requirements of the legislation of the Russian Federation in the field of personal data;
(Paragraph additionally included by order of the Moscow Government dated December 19, 2018 N 891-RP)

Determination of requirements for the information system (subsystem) for protecting information contained in the information system.
(Item additionally included)

1.4. If there are no grounds for the adoption of a legal act of the Moscow Government containing a regulation on the information system, the legal act on the commissioning of the information system must be agreed upon with the executive authority of the city of Moscow that ensures the operation of the information system at the expense of the budget of the city of Moscow, or with one subordinate to such to the executive authority of the city of Moscow by the organization (if it is entrusted with the appropriate powers).
(Clause 1.4 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP, by order of the Moscow Government dated October 6, 2015 N 563-RP; as amended by order of the Moscow Government dated December 19, 2018 N 891-RP.

1.5. Access to the information contained in the information system is provided after the information system is put into operation by the information system operator or the organization authorized by it to perform the functions of the information system operator, by:

Free receipt of information not related to information limited access, unless otherwise established in the regulations on the information system;

Receipt of information by executive authorities of the city of Moscow, organizations subordinate to them, other organizations, individuals in accordance with the regulations on the information system;

Obtaining information based on contracts for use information resources information system, concluded by the operator of the information system or the organization authorized by him to perform the functions of the operator of the information system, with business entities (hereinafter referred to as the agreement for the use of information resources).
(Clause 1.5 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)

1.6. The agreement for the use of information resources is an adhesion agreement and must, among other things, provide for:

List of information systems, information from which must be provided;

Composition of information to which access is provided;

Purposes of providing access to information;

The amount of the fee for providing access to information if the information system operator has not established that access to it is provided free of charge;

Requirements and restrictions on the use of information, including when carrying out activities by an economic entity.
(Clause 1.6 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)

1.7. The information system operator ensures approval of forms of agreements for the use of information resources and their placement on the official website of the information system operator on the information and telecommunications network Internet, conclusion of agreements for the use of information resources and control of their implementation. The specified powers are exercised by the operator of the information system, regardless of whether the legal act of the Moscow Government containing the regulation on the information system specifies an executive authority of the city of Moscow, different from the operator of the information system, responsible for organizing the information content of the information system.
(Clause 1.7 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)

1.8. Under an agreement for the use of information resources, personal data and other information of limited access are not provided, except in cases where such provision is agreed with the subject of personal data or the owner of the information of limited access.
(Clause 1.8 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)

1.9. The legal act of the Moscow Government containing regulations on the information system may establish other features of providing access to information contained in the information system.
(Clause 1.9 was additionally included by order of the Moscow Government dated June 30, 2015 N 370-RP)

2. Entrust control over the implementation of this order to the Minister of the Moscow Government, Head of the Moscow Department of Information Technologies E.A. Lysenko.
(Clause as amended, put into effect by order of the Moscow Government dated December 19, 2018 N 891-RP.

Mayor of Moscow
S.S. Sobyanin

Application. About commissioning

Application
to the order of the Moscow Government
dated July 3, 2012 N 342-RP
(As amended as put into effect
by order of the Moscow Government
dated December 5, 2017 N 694-RP;
in the version put into effect
by order of the Moscow Government
dated December 19, 2018 N 891-RP. -
See previous edition)

About commissioning

In accordance with

(indicates the legal act of the Moscow Government in accordance with which the information system was created)

and for the purpose of implementation

(if a legal act of the Moscow Government is adopted containing a regulation on the information system, the name of the corresponding legal act is indicated)

taking into account the results accepted in the prescribed manner

(the name of the work is indicated - the subject of the contract (agreement) in accordance with which the information system was created)

produced under the contract (agreement) from

which is confirmed

(indicate the acceptance test report)

1. Accept with

into operation

(indicate the date of commencement of operation of the information system)

(indicate the name of the information system)

create an information system passport.

(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow)

based on the information contained in the information system passport, register the information system in the Unified Register of Information Systems and Resources of the City of Moscow.

(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow)

ensure the adoption of a legal act of the Moscow Government approving the regulations on the information system.

5. Establish that the operation of the information system

provides

(indicate the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow that exercises these powers)

(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow)

ensure the development and approval of organizational and administrative documents of the executive authorities of the city of Moscow, ensuring the creation of information systems that define measures to protect information during the operation of the information system, the development of which is provided for by regulatory legal acts and methodological documents of the federal executive body in the field of security and the federal body executive power, authorized in the field of countering technical intelligence and technical protection of information, as well as national standards in the field of information protection.

(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow)

ensure certification of the information system according to information protection requirements, as a result of which, in cases established by the legislation of the Russian Federation, the compliance of the protection of information contained in the information system with the requirements provided for by the legislation of the Russian Federation on information, information technology and information protection is confirmed.

(indicate the position, surname and initials of the person who is responsible for preparing officials and workers for operating the information system)

ensure the training of officials of the executive authority of the city of Moscow (employees of an organization subordinate to the executive authority of the city of Moscow), ensuring the creation of an information system, for the operation of the information system, including persons responsible for ensuring the security of information.

(indicate the structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow)

ensure the preparation of the executive authority of the city of Moscow (an organization subordinate to the executive authority of the city of Moscow), ensuring the creation of the information system, for the operation of the information system.

10. Monitoring the implementation of this legal act (local normative act)

assign to

(indicate the position, surname and initials of the person who is entrusted with control over the implementation of the legal act (local normative act)

Position of the head of the executive authority the city of Moscow or a subordinate authority executive power of the city of Moscow organization

Surname and initials

________________ If the registration of an information system passport and the registration of an information system in the Unified Register of Information Systems and Resources of the City of Moscow is carried out by the same structural unit of the executive authority of the city of Moscow or an organization subordinate to the executive authority of the city of Moscow, paragraphs 2 and 3 of this appendix can be combined .

The clause is included if, on the date of adoption of a legal act of the executive authority of the city of Moscow or a local regulatory act of an organization subordinate to the executive authority of the city of Moscow on the commissioning of an information system, a legal act of the Moscow Government containing a regulation on the information system has not been adopted. The paragraph is included if there are no grounds for the adoption of a legal act of the Moscow Government containing a provision on the information system.

Revision of the document taking into account
changes and additions prepared
CJSC "Kodeks"

3) a description of the operator’s actions when working with programs (rules for launching programs, work order, actions in possible non-standard situations, etc.).

Test case description includes description:

1) functions and parameters of the software tested by the test case;

2) the composition of the technical means necessary to test the software in this example;

3) input information;

4) results of running programs based on test case data;

5) operator actions when checking the program on a test example;

6) test results (control standard) of programs using a test example.

Procedure for transferring software documentation

All programs and instructions, tested by the developer on a test example, are handed over to the customer under a certificate certifying their acceptance for trial operation.

The software, instructions and descriptions of algorithms handed over to the customer must meet the requirements for the composition and content of the detailed design of the information system. Programs recorded on magnetic media are transferred to the customer. The customer provides the developer with magnetic media and computer time necessary for putting programs into trial operation and duplicating them (if necessary).

Acceptance of a set of tasks (subsystems) for trial operation involves solving a test case by specially trained customer personnel in the presence of developer representatives, followed by analysis of the results. By mutual agreement, the test case can be performed by the developer in the presence of the customer.

Based on the acceptance results, a software acceptance certificate for trial operation is signed. Discovered

Developer errors in programs and technical documentation are eliminated during the commissioning process.

Organizational and administrative documentation

For the main work carried out at the “Detailed Design” stage, the following organizational and administrative documentation is drawn up:

1) order to carry out work at the stage in accordance with the schedule organizational and technical measures;

2) schedule of joint work between the contractor and the customer;

3) act of verification on test examples and acceptance of work programs into trial operation;

4) act of readiness of regulatory and reference documentation;

5) the act of carrying out organizational and technical measures to prepare the enterprise for the implementation of the information system.

5.5. Putting the information system into operation

Commissioning of an information system and its individual elements is a process of gradual transition from existing methods management to automated control methods.

Commissioning of the information system is organized and carried out by the customer with the participation of the developer and co-executing organizations. Interaction between customer organizations, developers and co-executors is carried out on the basis of contractual terms and a schedule for putting the information system into commercial operation.

Commissioning is carried out in stages, starting from the stage of development of the technical project, as the working documentation is ready and the technical means are put into operation, ensuring the implementation of queues or information system objects capable of independent functioning.

You should begin putting the information system into operation if you have:

1) executed documents on the implementation of the action plan for the preparation of the facility;

2) working documentation for the implementation of a dedicated queue or information system as a whole;

3) trained personnel providing preparation for commissioning

operation and operation of a dedicated information system queue;

4) technical means of the information system accepted for operation, ensuring the functioning of the implemented sets of tasks.

Organization of work

Implemented:

1) trial operation of individual tasks and their complexes;

2) acceptance of task complexes for commercial operation;

3) carrying out acceptance tests;

4) acceptance of the system for commercial operation.

The composition and order of work are determined by the agreed commissioning schedules, which indicate the composition and timing of the following work:

1) for the construction, installation, commissioning and testing of information system objects from the moment of receipt of working documentation until the objects are put into commercial operation;

2) for carrying out trial operation and acceptance testing of task sets;

3) to ensure the transition from existing management methods

To methods provided for by the information system design.

At the stage “Putting the information system into operation”

the customer is obliged:

1) terminate execution organizational and technical measures to prepare the enterprise for the implementation of the information system and formalize them with acts;

2) ensure that the enterprise personnel comply with job and technological instructions;

3) put into operation the technical means necessary for the implemented technological data processing process;

4) issue an order with a schedule for conducting trial operation of the information system and analyze, together with the developer, the results of trial operation;

5) complete the trial operation of the complexes of tasks included in the information system and their acceptance for commercial operation;

6) make changes to the organizational structure of the enterprise in accordance with the information system project;

7) develop a draft order on the composition of the acceptance committee;

8) develop and coordinate with the developer a draft program acceptance tests;

9) organize the work of the acceptance committee, provide it with the required documentation and test the information system;

10) check the effectiveness of the implemented solutions in industrial operation conditions and, based on the results of the analysis of the functioning of the system, develop recommendations for its further development.

At the stage “Putting the information system into operation”

the developer is obliged:

1) adjust technical documentation based on the results of trial operation of the information system;

2) take part in the development of a draft program for acceptance testing of the information system;

3) provide methodological guidance and take part in putting tasks (sets of tasks) into commercial operation;

4) participate in the work of the commission for acceptance of the information system into commercial operation.

The procedure for conducting trial operation

The beginning of trial operation of tasks (sets of tasks), the terms of operation and the composition of the commission for the acceptance of a specific task or subsystem are determined by an order issued by the customer and agreed with the developer. Attached to the order is the agreement agreed with

the developer has a trial operation program, which defines the conditions for testing sets of tasks, the procedure for checking technical means when solving sets of problems (subsystems) and the procedure for eliminating deficiencies identified during trial operation.

Additional customer requirements that arise during trial operation and are not provided for in the technical specifications and technical design do not constitute grounds for a negative assessment of the results of trial operation and can be satisfied by additional agreement within the agreed time frame.

At positive results During the trial operation of tasks (subsystems), a bilateral act on their acceptance for commercial operation is drawn up.

After the information system has been accepted for commercial operation, the customer bears responsibility for its functioning within the scope of the accepted sets of tasks and tools.

Initial and reporting documents for testing information system software

Joint tests are carried out by a customer commission, which includes the development manager and some leading developers. The testing commission is guided by the following documents:

1) technical specifications for the creation of an information system approved by the customer and agreed with the developer;

2) current state and industry standards for software design and testing and technical documentation;

3) test program for all technical requirements

4) test methods for each section of the requirements of the technical specifications.

Test program, methods of their conduct and evaluation

The results are developed jointly by the customer and the developer and must be agreed upon and approved. They contain clarifications of the requirements of the technical specifications for a given system and must guarantee their correct verification. System documentation should

fully comply with the programs being tested, ensure that the system is understandable by maintenance personnel, and also provide the ability to develop and modernize programs to increase the duration of their life cycle.

Test program is a plan for conducting a series of experiments. It is developed from the position of minimizing the amount of testing while ensuring the reliability of the results obtained is specified and agreed upon with the customer. To do this, the sequence and scope of each testing during the testing process are determined to verify compliance with the requirements of the technical specifications when minimum costs. It can be especially difficult to select a set of stressful system operating situations under which testing should be carried out. Test program should contain the following clearly defined sections:

1) test object, its purpose and a list of the main documents that determined its development;

2) the purpose of the tests, indicating the main requirements of the technical specifications to be verified, and restrictions on testing;

3) actually test program, containing a check of the completeness of the developed system in accordance with the technical specifications and a test plan for checking the functioning of programs for all sections of the technical specifications and additional requirements formalized by separate solutions;

4) test methods, unambiguously defining all the concepts of the characteristics being tested, testing conditions, tools used for testing, methods for processing and evaluating test results for each section of the test program.

Large volume of heterogeneous data obtained during testing

software, and variety possible ways their processing, interpretation and evaluation lead to the fact that the most important factors for processing test results become methods for processing and evaluating results. In accordance with test methods, automation equipment must ensure completeness of characteristics checks for each section of methods and development

inspection protocols for items of the test program. The complexity of software and the close relationship between its various characteristics lead to the need for careful formulation of all test conditions and parameter values ​​​​at which the test must be performed.

Test results are recorded in protocols , which usually contain the following sections:

1) the purpose of testing and the section of the requirements of the technical specifications according to which the test is carried out;

2) indication of the methods in accordance with which the tests were carried out, processing and evaluation of the results;

3) testing conditions and characteristics of the initial

4) generalized test results with their assessment for compliance with the requirements of the technical specifications and other governing documents;

5) conclusions about the test results and the degree of compliance of the created software with a certain section of the requirements of the technical specifications.

The protocols for the entire program are summarized in an act, resulting in

a conclusion is made about the system’s compliance with the customer’s requirements and whether the work is completed with a positive or negative outcome. If all requirements of the technical specification are fully met, the customer is obliged to accept the system and the work is considered completed.

However, as already noted, for complex software packages it is difficult to foresee and correctly formulate all the requirements of the technical specifications at the initial stages of design. Therefore, during debugging and testing, it is often revealed that some requirements of the technical specifications are not met and sometimes even fundamentally cannot be fulfilled even with the most conscientious attitude to this on the part of the developer. In this case, it is necessary to work together between the customer and the developer to find a compromise solution when completing tests and drawing up a conclusion. Some shortcomings of the program complex during the testing process are only registered and recorded in terms of eliminating the commission’s comments,

who carried out the tests. This plan is an annex to the test results report and allows you to separate subsequent improvements from direct tests.

The procedure for carrying out acceptance tests

The customer is responsible for organizing and conducting acceptance into commercial operation. Acceptance of the information system for commercial operation is carried out upon completion of the customer's acceptance of all sets of tasks (subsystems) for commercial operation.

Tasks, sets of tasks (subsystems) and technical means of the information system that are not provided for in the technical specifications, but implemented by the customer independently, can be included in the complex of the information system being delivered only in agreement with the developer and after appropriate changes have been made to the technical specifications for the creation of the information system.

At the request of the customer or developer, representatives of subcontractors may be involved in the acceptance of the information system.

The customer presents the information system to the acceptance committee. In addition to the members of the commission, experts on certain issues of creating information systems may be involved in the acceptance process with the right of an advisory vote. The customer is obliged to ensure normal working conditions for the commission in accordance with the adopted information system acceptance program. To promptly resolve organizational issues that arise in the process of accepting the information system, a responsible representative from the developer organization is allocated by order of the head of the developer organization.

The customer, together with the developer, prepares a draft program for testing and acceptance of the information system and submits it to the acceptance committee for review and approval. The program indicates: the name of the information system being submitted, the directive documents on the basis of which the system was developed (if any), the composition of the acceptance committee and the number of the order for its appointment, purpose, objects, volume, location and

sequence of tests, methods of testing and evaluation of results.

The customer prepares together with the developer and transfers the following documents for temporary use to the commission:

1) orders, instructions, plans, contracts providing for the creation of an information system;

2) technical and economic justification, terms of reference, technical design, detailed design of the information system;

3) acts of consideration and approval of the technical design;

4) bilateral acts of the customer and the developer on the delivery of tasks, sets of tasks (subsystems), devices and their complexes into commercial operation in accordance with the approved technical specifications.

The acceptance committee provides:

1) checking documentation and functioning of the information system;

2) organizing working groups and distributing responsibilities among commission members to check individual subsystems;

3) checking the calculation of the economic efficiency of the created information system;

4) organizing workshops and preparing information system acceptance certificates.

Checking operating conditions and operating modes of technical

information system tools is carried out simultaneously with checking the functioning of complexes of tasks (subsystems). The preparedness of the personnel responsible for the operation of the information system is determined in accordance with the training program and job descriptions included in the working project. The results of the inspection are discussed at work meetings and documented in minutes.

The final stage of the commission’s work is the drawing up of an act, which indicates:

1) composition of the commission, positions and places of work of commission members;

2) term (date) of system acceptance;

3) the composition of performers (organizations, enterprises) who took part in the creation of the information system;

4) grounds for acceptance (orders, instructions and

5) list of presented information system documentation

And assessment of its compliance with current regulatory and technical documents;

6) compliance of actually completed and implemented work with technical specifications;

7) readiness of all types of support and structural divisions of the customer for the implementation and operation of the information system;

8) information about the effectiveness of the information system (comparison of existing or expected actual data on the volume and sources of savings obtained with calculated data);

9) conclusions of the commission on the possibility of accepting the information system;

The acceptance certificate in five copies is signed by the chairman and all members of the commission. The date of putting the information system into operation is the date of signing the act by the commission.

6. Information systems development team

Since the creation of a modern information system is a complex process that requires the joint efforts of a large number of different specialists, the formation of a team involved in the design, development and implementation of an information system is of great importance in modern conditions.

Organization of a team and distribution of work among specialists can be carried out according to several principles:

1) based on the distribution of system analysis (algorithmization) and program development among different teams;