Requirements for the functions performed by the system

This subsection provides:
1) for each subsystem, a list of functions, tasks or their complexes (including those ensuring the interaction of parts of the system) to be automated;
when creating a system in two or more queues – a list of functional subsystems, individual functions or tasks put into effect in the 1st and subsequent queues;
2) time schedule for the implementation of each function, task (or set of tasks);
3) requirements for the quality of implementation of each function (task or set of tasks), the form of presentation of output information, the characteristics of the required accuracy and execution time, the requirements for the simultaneity of the execution of groups of functions, the reliability of the results;
4) a list and failure criteria for each function for which reliability requirements are specified.

4.2.1. Subsystem for collecting, processing and loading data
4.2.1.1 List of functions, tasks to be automated

Function Task
Manages the processes of collecting, processing and loading data Creation, editing and deletion of processes for collecting, processing and loading data
Formation of the sequence of execution of the processes of collecting, processing and loading data (regulations for loading data)
Defining and changing the schedule of data collection, processing and loading processes
Performing the processes of collecting, processing and loading data from sources into the data warehouse Starting procedures for collecting data from source systems, loading data into the area of temporary, permanent storage
Processing and transformation of extracted data
Support for slowly changing dimensions
Logs the results of collecting, processing and loading data Keeping logs of the results of collecting, processing and loading data
Operative notification of users about all emergency situations during the operation of the subsystem

4.2.1.2 Time schedule for the implementation of each function, task

Task Time limit requirements
Creation, editing and deletion of processes for collecting, processing and loading data The entire period of the system operation, if there is a need to change the processes of collecting, processing and loading data
Formation of the sequence of execution of the processes of collecting, processing and loading data (regulations for loading data) The entire period of the system operation, if it becomes necessary to modify the data loading schedule
Defining and changing the schedule of data collection, processing and loading processes The entire period of the system operation, if it becomes necessary to change the schedule of processes
Starting procedures for collecting data from source systems, loading data into the area of temporary, permanent storage After the data is ready in the source systems, daily in the time interval 00:00 – 03:00
Processing and transformation of extracted data Daily, after the appearance of all extracted data in the time interval 00:00 – 06:00
Support for slowly changing dimensions Regularly, when the subsystem is running for measurements of the corresponding type
Keeping logs of the results of collecting, processing and loading data Regularly, when the subsystem is running
Operative notification of users about all emergency situations during the operation of the subsystem Regularly, in case of an emergency situation during the operation of the subsystem

4.2.1.3 Requirements for the quality of implementation of functions, tasks

Task Form of presentation of output information Characteristics of accuracy and execution time
Creation, editing and deletion of processes for collecting, processing and loading data In the ETL interface standard means Determined by the operating regulations
Formation of the sequence of execution of the processes of collecting, processing and loading data (regulations for loading data) In the ETL interface standard means Determined by the operating regulations
Defining and changing the schedule of data collection, processing and loading processes In the ETL interface standard means Determined by the operating regulations
Starting procedures for collecting data from source systems, loading data into the area of temporary, permanent storage Text file The launch must be carried out exactly according to the established schedule.
Processing and transformation of extracted data Text file. Data in database structures Data must be converted to be loaded into HD model structures. No more than 2 hours
Support for slowly changing dimensions Data in database structures Data must be stored according to the rules for supporting slowly changing measurements of the appropriate type.
Keeping logs of the results of collecting, processing and loading data Text files At the time of data collection, processing and loading
Operative notification of users about all emergency situations during the operation of the subsystem Text file, window message, email Not later than 15 minutes after the occurrence of an emergency

4.2.1.4 List of failure criteria for each function

Function Rejection Criteria Recovery time Availability factor
Manages the processes of collecting, processing and loading data One of the tasks is not executed: 8 ocloc’k 0.85
Starts the processes of collecting, processing and loading data from sources into the data warehouse One of the function’s tasks is not running. 12 hours 0.75
Logs the results of collecting, processing and loading data One of the function’s tasks is not running. 12 hours 0.75

4.3.2. Requirements for information support

Requirements are given:
1) to the composition, structure and methods of organizing data in the system;
2) to information exchange between system components;
3) to information compatibility with adjacent systems;
4) on the use of all-Union and registered republican, industry classifiers, unified documents and classifiers operating at a given enterprise;
5) on the use of database management systems;
6) to the structure of the process of collecting, processing, transferring data in the system and presenting data;
7) to protect data from destruction in case of accidents and power failures of the system;
8) control, storage, updating and recovery of data;
9) to the procedure for giving legal force to documents produced by the technical means of the AU (in accordance with GOST 6.10.4).

4.3.2.1. Requirements for the composition, structure and methods of organizing data in the system
The data storage structure should consist of the following main areas:
– area of temporary data storage;
– area of permanent data storage;
– data mart area.
Areas of permanent storage and data marts should be built on the basis of a multidimensional data model, which implies the selection of individual dimensions and facts with their analysis according to the selected dimensions.
A multidimensional data model must be physically implemented in a relational DBMS according to the “star” and/or “snowflake” scheme.

4.3.2.2.

Requirements for the use of classifiers, unified documents and classifiers
The system, whenever possible, should use classifiers and directories that are maintained in data source systems.
The main classifiers and directories in the system (clients, gyms, article trainers, etc.) should be the same.
The values of classifiers and directories that are not in the source systems, but necessary for data analysis, must be maintained in specially designed files or database repositories.

Requirements for the structure of the process of collecting, processing, transmitting data in the system and presenting data

Requirements for the protection of data from destruction during accidents and power failures of the system
Information in the database of the system must be saved in the event of emergencies associated with power failures.
The system must have an uninterrupted power supply that ensures its normal functioning for 15 minutes in the absence of external power supply, and an additional 5 minutes for the correct completion of all processes.
Data backup should be carried out on a regular basis, in volumes sufficient to restore information in the data storage subsystem.

Requirements for control, storage, updating and recovery of data
The requirements for data control are:
– the system should log all events related to changes in its content, and be able to restore its state in case of failure using previously logged data changes.
The requirements for data storage are:
– storage of historical data in the system should be carried out for no more than 5 (five) previous years. At the end of this period, the data should be transferred to the archive;
– historical data exceeding the five-year threshold should be stored on a tape array with the possibility of their recovery.
The requirements for updating and restoring data are as follows:
– for the server for collecting, processing and loading data, it is necessary to ensure that its binary files (Home) are backed up once every 2 weeks and the copy is stored for 2 months;
– for the database server, it is necessary to ensure that its binary files are backed up once every 2 weeks and the copy is stored for 2 months;
– for data warehouse data, it is necessary to ensure backup and archiving to a tape array at the following time intervals:
-cold copy – quarterly;
-logical copy – monthly (end of the month);
-incremental backup – weekly (Sunday);
– archiving – quarterly;

4.3.2.9. Requirements for the procedure for giving legal force to documents produced by the technical means of the system
There are no requirements.

Be First to Comment

Leave a Reply

Your email address will not be published.