RU53034U1 - AUTOMATED DATABASE MANAGEMENT SYSTEM FOR JUDICIAL AND EXECUTIVE BUSINESS - Google Patents

Abstract

The invention relates to computer technology, in particular, to an automated database management system of judicial and executive records management.

The technical result is to increase the speed of the system by localizing the addresses of the file of cases on the identifier of the user allowed to work with the specified file of cases.

The technical result is achieved by the fact that the system comprises a module for receiving a password code, a module for selecting a base address of user passwords, a module for managing a password selection, a module for generating an address for reading server database records, a module for receiving user passwords from a database, a user identification module, a file address localization module affairs, module for cyclic support of file numbers of cases, module for receiving file numbers of file cases, module for selecting addresses of file cases in the server database, reception module case data from the server database, module for issuing case data to the user.

Description

The invention relates to computer technology, in particular, to an automated database management system of judicial and executive records management.

The peculiarity of judicial and executive clerical work is its constant change. The process of reforming the judicial system of the Russian Federation, the constant amendment of laws and instructions on paperwork leads to the fact that traditional approaches to creating such automated systems become unjustified.

Any changes in the quantity and nature of accounting information will lead to the fact that the created automated system will need to be constantly updated, amended and

changes, involve additional capital investments in the implementation of these works.

Therefore, it is necessary to initially lay down the requirement for the system to be able to modify without interfering with the source programs.

The core of the automated system of judicial and executive records management is the database of filing files of judicial or executive documents, which directly stores information on complaints, protests, case data, participants in trials, etc. all instances of the court.

The control database contains a description of table structures, rules and processing algorithms, interaction, and is responsible for the automatic formation of the interface parts of the system. Using this module, the system administrator can make changes to the structure, manage communications and information flows between file cabinets, and differentiate user access to stored information.

It should be noted that the interface part must satisfy the requirements of all categories of court users. It should combine the convenience of navigation and search with the appearance of the data presentation.

The principle of dividing the total volume of card file data into stages fits seamlessly into the procedural procedure for going through a case from the moment it arrives in court to a decision or sentence on the case. In addition to this, it should be possible to customize the appearance of each workplace to the requirements and

the wishes of a particular user: determining from the total number of requests those that are most often used at this workplace, the order in which database fields are presented, a list of document templates that this user operates on.

In its form, for example, the workplace of the secretary who registers criminal cases is no different from the workplace of the secretary for civil cases, the difference is the content and presentation of the data. This approach greatly simplifies the implementation and development by users of the principles of work in this technology.

Thus, technically, the core of the created system should be the module for designing and creating software in the judicial and executive record keeping system (setup module), which will allow for the modification of court databases and user workstations "centrally", to support the operation of the systems in an up-to-date state background of changes in legislation, principles and rules for the registration of cases and materials in courts.

Considering that for the full-fledged activity of courts in matters of judicial and executive record keeping, communication between automated systems of judicial bailiff services, sections of magistrates' judges, investigative bodies, the Supreme Court of the Russian Federation, etc. is necessary, the developed system should operate on various DBMS platforms. But regardless of the platform, the user's workplace should remain unchanged.

Known technical solutions that could be used to build such a system (1, 2).

The first known system includes data receiving and storage modules connected to control and data processing modules, search and selection modules connected to data storage and display modules, the synchronizing inputs of which are connected to the outputs of the control unit (1).

A significant drawback of this system is the impossibility of solving the problem of updating data stored in memory in the form of relevant documents at the same time as solving the problem of delivering the contents of these documents to users in real time.

Another system is known that contains data processing modules, the information inputs of which are connected to the data reception and control modules, and the outputs are connected to the first group of memory modules, the central processor module, the inputs of which are connected to the outputs of the memory modules of the first group and data processing modules, and the outputs connected to the inputs of the memory modules of the second group and data display modules (2).

The last of the above technical solutions is closest to the described.

Its disadvantage lies in the low speed of the system, due to the fact that the query procedure is implemented by searching for records across the entire database and their subsequent processing by the central processor, which for large

The amount of database data inevitably leads to an unjustified waste of time.

The purpose of the invention is to increase the system performance by localizing the addresses of the file of cases on the basis of the user ID allowed to work with the specified file of cases.

This goal is achieved by the fact that in the known system containing the password code receiving module, the information and synchronizing inputs of which are the first information and synchronizing inputs of the system, the module for generating the address for reading the server database records, the information output of which is the address output of the system, and the synchronizing output is the first synchronizing output of the system, the module for receiving user passwords from the database, the information and synchronizing inputs of which are system information and synchronization inputs, a file cabinet case number receiving module, information and synchronizing inputs of which are the third information and synchronizing system inputs, a case file cyclical number support module, the information output of which is the first information output of the system, and the synchronizing output is the second synchronizing system output , a module for receiving case data from a server database, the information and synchronizing inputs of which are quarters and the synchronizing information and the system inputs, and one output is a second information output of system, the module data output case

a user, one information input of which is the fifth information input of the system, and other information inputs are connected to the corresponding outputs of the case data receiving module from the server database, while the synchronizing input of the case data output module is connected to the fourth synchronizing input of the system, the control inputs of the data output module cases to the user are the first and second control inputs of the system, the information outputs of the module for issuing data to the user are information in system group moves, and the control outputs of the case data output module to the user are the system group control outputs, a module for selecting the base address of user passwords is introduced, the information input of which is connected to the output of the password code receiving module, and the synchronization input is connected to the first synchronizing input of the system, the information output of the module for selecting the base address of user passwords is connected to the first information input of the module for generating the address for reading database records faith, and the synchronizing output is connected to the first synchronizing input of the module for generating the address for reading the server database records, the user identification module, one information input of which is connected to the output of the password code receiving module, another information input of the user identification module is connected to the output of the user password receiving module from the database data, and the clock input is connected to the second clock input of the system, while

one output of the user identification module is connected to the installation input of the unit for generating the read address of the server database records, the password selection control module, the information input of which is connected to the other information output of the selection of the base address of the user passwords, the synchronization input is connected to one output of the user identification unit, and the installation the input is connected to another output of the user identification unit, while the information output of the password selection control unit with it is single with the second information input of the server database record read address generation unit, one synchronization output of the password selection control unit is connected to the second synchronization input of the server database record read address generation unit, and the other synchronization output is a signal output of the system, the file cabinet address localization module, the information input of which is connected to the third information output of the module for selecting the base address of user passwords, and synchronizing the input is connected to the other output of the user identification module, while the information output of the file cabinet address localization module is connected to the information input of the case file cyclical module, and the synchronizing output of the file cabinet address localization module is connected to the synchronization input of the file cabinet cyclic support module, and the module selection of file cabinet file addresses in the server database, the information input of which is connected to the output of the receiving module

file numbers of the file cabinet, and the synchronizing input is connected to the third synchronizing input of the system, while the information output of the file cabinet address selection module of the file cabinet in the server database is connected to the third information input of the server database record reading address generation module of the file cabinet, and the synchronizing output of the file cabinet file address selection module of the file cabinet The server database is the third synchronizing system output.

The invention is illustrated by drawings, in which Fig. 1 is a structural diagram of a system, Fig. 2 is a structural diagram of a selection module of a base address of user passwords, Fig. 3 is a structural diagram of a password selection control module, and Fig. 4 is a structural diagram of a generating module read addresses of server database records, FIG. 5 is a structural diagram of a user identification module, FIG. 6 is a structural diagram of a case file localization address module, FIG. 7 is a structural diagram of a cyclic card number support module case file, in Fig. 8 is a structural diagram of a module for selecting a file address of a file cabinet in a server database, in Fig. 9 is a structural diagram of a module for issuing case data to a user, and in Fig. 10 is a metadata structure of a database of judicial or enforcement proceedings.

The system (Fig. 1) contains a password code receiving module 1, a user password base address selection module 2, a password selection control module 3, a server database entry reading address generating module 4, a user password receiving module 5 from the database, a user identification module 6 ,

a case file address localization module 7, a case file cyclic number support module 8, a file cabinet case reception module 9, a file cabinet case number selection module 10, a file cabinet case address selection module 10 in the server database, a case data reception module 11 from the server database, a case data output module 12 to the user.

Figure 1 shows the first 15, second 16, third 17, fourth 18 and fifth 19 information inputs of the system, the first 20, second 21, third 22 and fourth 23 synchronizing inputs of the system, the first 24 and second 25 control inputs of the system, as well as the first 26 and second 27 information outputs of the system, a group of 28-31 information outputs of the system, the first 32, second 33 and third 34 synchronizing outputs of the system, a group of 35-38 control signals for recording, address output 39 of the system and signal 40 system output.

The password code receiving module 1 is made in the form of a register having an information input 15 synchronizing the input 20 and the output connected to the input 50 of block 2.

Module 2 (figure 2) selection of the base address of user passwords contains a decoder 40, a memory module 41, made in the form of read-only memory, register 42, elements 43-45 AND, elements 46-48 delay. The drawing shows the synchronizing 49 and information 50 inputs, as well as information 51-53 and synchronizing 54 outputs.

The password sampling control module 3 (FIG. 3) comprises a counter 55, a comparator 56, and a delay element 57. The drawing shows

information 58, synchronizing 59 and installation 60 inputs, as well as information 61 and synchronizing 62, 63 outputs.

Module 4 (FIG. 4) of generating a server database record read address contains an adder 65, an OR element 66, a group of OR elements 68, a delay element 69. The drawing shows information 70-72, synchronizing 73-74 and installation 75 inputs, as well as address 39 and synchronizing 32 outputs.

Module 5 (Fig. 1) of receiving user passwords from the database is made in the form of a register having an information input 16, synchronizing input 21 and output connected to input 81 of module 6.

The user identification module 6 (FIG. 5) comprises a comparator 78, a delay element 79. The drawing shows information 80, 81 and synchronizing 82 inputs, as well as outputs 83, 84.

Module 7 (Fig.6) localization of the addresses of the file cabinet contains a decoder 85, a memory module 86, made in the form of read-only memory, elements 87-89 AND, element 90 delay. The drawing shows information 91 and synchronizing 92 inputs, as well as information 93 and synchronizing 94 outputs.

Module 8 (Fig.7) of cyclic support of file numbers of cases contains a register 100, a counter 101, a memory block 102 made in the form of a permanent storage device, a register 103, elements 104-109 AND, elements 110-112 OR, elements 113-115 delay . The drawing shows information 120 and

synchronizing 121 inputs, as well as information 26 and synchronizing 33 outputs.

Module 9 (Fig. 1) of receiving the file number of the server card file is made in the form of a register having an information input 17, a clock input 22 and an output connected to the input 134 of the module 10.

Module 10 (Fig. 8) of selecting a file cabinet file address in the server database contains a decoder 125, a memory unit 126 made in the form of read-only memory, register 127, elements 128-130 And, elements 131-133 delays. The drawing shows information 134 and synchronizing 135 inputs, as well as information 136 and synchronizing 127 outputs.

Module 11 (Fig. 1) of receiving case data from the server database is made in the form of a register having an information input 18, synchronizing input 23 and outputs 155-159.

Module 12 (Fig. 9) for issuing case data to a user comprises a register 140, a decoder 141, groups 142-145 of AND elements, elements 146-149, an OR element 150, and a delay element 151. The drawing shows information 19, 160-163 and synchronizing 164 inputs, as well as information 28-31 and control 35-38 outputs.

All nodes and elements of the system are made on standard potential-impulse elements. To simplify the drawing, the chains of the initial installation of nodes and blocks are not shown.

All the workstations provided by the court administration system are integrated into a local area network and work with

a common database (not shown in the drawing). This allows you to organize the collective work of court employees and significantly reduces the likelihood of errors, since information about the motion of a particular case is entered into the database when it arises.

The principle of collective work does not mean that the user gets access to any information from the database. For each employee, the database administrator sets a password to enter the system, which determines the available information and functions.

When working with a file of cases, access to it is provided for the following categories of users:

- administrator;

- archivist;

- referee;

- Secretary of the Chancellery;

- Secretary of the court session.

The system operates as follows.

Considering the fact that various categories of users who work in an automated court case management system should see information on cases in accordance with their job descriptions and powers, the system uses a flexible system of settings for data access rights.

All users are divided into groups that are endowed with various privileges. For example, the database administrator has full access to information on cases, judges have full access to registration information on cases that they

considered and judicial documents that they created, secretaries of chancellery have access to registration information and information necessary for generating statistical reports.

The principle of access to data is based on the definition of user groups. The number of such groups is unlimited. For each group, access rules and the amount of data that are available to this group of users are determined.

For example, the presiding judge in the file of civil cases of the first instance sees all the cases that were or are under his consideration. Moreover, these cases are sorted in reverse order upon receipt.

When entering the system, users are authorized, i.e. each user allowed to work in the system must know his password (issued by the administrator) and enter it in the user identification window. After that, the system should determine to which group of users this user belongs and, accordingly, to which file cabinets are allowed.

To this end, the user password code from the input 15 of the system is fed to the information input of module 1, where it is entered by the synchronizing pulse supplied to input 20.

From the output of module 1, the user password code is fed to input 50 of block 2, from where it is supplied to the input of the decoder 40, which decrypts the password code and opens one input of one of the elements 43-45 I.

At the same time, the synchronizing pulse from the input 20 of the system through the input 49 of module 2 is fed to the input of element 46, where it is delayed by the time the password code is entered into module 1 and the decoder 40 is activated, and then, passing through the corresponding element 43-45 AND, the clock pulse firstly, it is received at the read input of a fixed memory cell of a permanent storage device 41, the content of which has the following structure:

THE CODE THE CODE THE CODE REFERENCE ADDRESS of the first memory cell in the system database, which contains the first password of the user registered in the system Total number of user passwords registered in the system User category identifier indicating case numbers to which this user is allowed

The indicated codes are read from the ROM 41 to the information input of the register 42. At the same time, the data read pulse from the output of the element 46 of module 2 is delayed by the element 47 for the time of reading data from the ROM 42, and arrives at the synchronizing input of the register 42, fixing the corresponding codes.

In this case, the code of the reference address of the first memory cell of the database from the output 51 of module 2 is supplied to the information input 70 of module 4, the code of the total number of passwords from the output 52 of module 2 is sent to the information input 58 of module 3, and the code of the user category identifier from the output 53 of module 2 enters the input 91 of the module 7.

Next, the reference address code from the input 70 of the module 4 is fed to one information input of the adder 65, which is in the initial state. In parallel with this, the same read pulse from the output of the delay element 47 of module 2 is again delayed by the delay element 48 for the time the codes are entered in register 42 and then from the output 54 of module 2 it goes to the synchronizing input 73 of module 4, from where it passes through the element 66 OR to the synchronizing adder input 65.

Considering that a zero code is supplied to the other input 71 of the adder 65 from the output 61 of the counter 55 of the module 3, which is also in the initial state, the adder 65 sums the code of the reference read address with the zero code of the counter 55 using a clock pulse. As a result, the output of the adder 65 the code of the reference read address remains unchanged, which is output from the adder 65 through the elements 68 OR of the group to the address output 39 of the system.

In parallel, the same clock pulse from the output of the OR element 66 of module 4 is delayed by the element 69 for the duration of the adder 65 operation, and then through the output 32 of the system it enters the input of the first channel of the database server interrupt.

By this signal, the server goes to the subroutine for reading the first password code at the specified address, issuing it to the information input 16 of the system and entering it into module 5 with a synchronizing pulse from the server to input 21.

From the output of module 5, the code of the first password read from the database, through the input 81 of module 6, is sent to one information input of the comparator 78 of module 6, to the other information input 80 of which from the output of block 1 the password code of the user entering the system is supplied.

At the same time, the synchronizing pulse from the input 21 of the system through the input 82 of module 6 is delayed by element 79 for the duration of entering the read password code into module 6, and then arrives at the synchronizing input of the comparator 78, comparing the input values of the password codes.

If the password input codes were not compared, then the comparator 78 at the output 83 of block 6 generates a synchronization signal, which, through the input 59 of block 3, is fed to the counting input of the counter 55, fixing the fact of viewing the first password code for recording personal identification data from the number of password codes of registered users and stored in the system database.

The output code of the counter 55 is fed to one input of the comparator 56 of module 3, the other information of which from input 58 is supplied with a code for the total number of password codes registered in the system.

In parallel, the synchronizing pulse from the input 59 of the module 3 is delayed by the element 57 for the duration of the counter 56 operation and arrives at the synchronizing input of the comparator 56 of the module 3.

By the synchronization signal supplied to its synchronizing input, the comparator 56 compares the number of scanned user password code entries with a fixed number of password codes registered in the system.

If the comparison of numbers did not happen, then the signal 62 is generated at the output of module 3, which passes through the element 66 OR through the input 74 of module 4 and is fed to the synchronizing input of the adder 65. At this pulse, the adder 65 adds the first unit to its reference address, which was received at its second input 71, and the newly formed address from the output of the adder 65 through the elements 68 OR group is issued to the address output of the system 39.

Simultaneously with this process, the synchronizing pulse from the output of the OR element 66 is delayed by the element 69 for the duration of the operation of the adder 65, and then through the first synchronizing output 32 of the system it is again fed to the input of the first channel of the database server interrupt.

By this signal, the server returns to the subroutine for reading the contents of the next database cell at the specified address, issuing it to the system information input 21 and entering the next password code from the database into module 5 with a synchronizing pulse from the server to input 21.

The described process of reconciling the password input code with the password codes stored in the database continues until the password input code is verified with all password codes stored in the server database.

If, as a result of such a verification, the input password code does not match any database password codes, then the comparator 56 of module 3, by outputting a signal to output 63, will record the fact of viewing all password codes of system users and confirm that there is no password code in the system database that was entered in block 1.

From the output 63 of module 3, the specified signal is immediately output to the output 34 of the system and then to the screen of the workstation, where it is displayed as a message that the password code is entered incorrectly.

If the comparator 78 of module 6 fixes the fact of the equality of the password codes located in modules 1 and 5, then the output 84 of the comparator 78 of module 5 generates a signal supplied to the input 92 of module 7, to the information input 91 of which is currently output from the output of module 53 2, a user category identifier code is supplied indicating the case numbers to which the user is allowed.

The code of the user category identifier from input 91 is fed to the input of the decoder 85, which decrypts the incoming code and opens one corresponding input element 87-89 I.

At the same time, the synchronizing pulse from the input 92 of the module 7 passes through the corresponding element And 87-89 And, and is fed to the read input of a fixed memory cell of a permanent storage device 86, which stores information about which cases this user is allowed to.

This information is read from the output 93 of the module 7 and is fed to the input 120 of the module 8 and then to the information input of the register 100, where it is entered by the synchronizing pulse from the input 92 of the module 7, delayed by the element 90 while reading data from the ROM 86 of the module 7.

The number of bits of the register 100 of module 8 corresponds to the number of cases that are in the file system of the system. If the corresponding category of the register is in a single state, then its output will be a high potential, indicating that the user is admitted to business with the number corresponding to this category. If the corresponding category of the register is in the zero state, then its output will be low potential, indicating that the user does not have access to the case, the number of which corresponds to the status of this category of the register.

To configure the system for the user’s work only with specific case numbers, a relational mechanism is used that connects to one main table, which can be any of the file cabinets for case accounting, a number of related (subordinate) tables.

In this case, navigation through the list of registered cases will be carried out according to the "main" table. This table is also responsible for adding, deleting records about the affairs of any of the file cabinets.

The number of “subordinate” tables may vary depending on what additional information on the case needs to be registered. This type of table may contain data on the parties to civil proceedings, the results of appeals against sentences and decisions, journals of familiarization with case materials, etc.

The structure of the database of judicial or executive records management is described in metadata, which is a set of tables presented in figure 10.

The metadata scheme begins with the FILES card table (item 1), which lists the logical names of the card files described in the metadata structure (for example, “card file for registering and recording cases of administrative offenses”, “card file for registering and recording civil cases in the court of first instance” etc.).

Any card index in this metadata structure is described in such a way that it will contain strictly one “main” table (called “Case” - item 2) and one or more (their number is not limited) subordinate tables (item 3). These tables indicate their logical names (for example, “Criminal proceedings”, “Persons in the case”, “Material evidence”) and physical names (ie what name the corresponding table in the database will have).

The tables Physical structure of “Cases” (item 4,) ПТ (item 6), Data Types (item 5) describes the structure of the “main” and subordinate tables (item 4, 6).

In this case, structure is understood as a complete list of all fields included in the described table indicating the logical (“Name of complaint”, “Region” ...) and physical (what name will have the corresponding field in the database table) names, as well as its type ("String", "Integer", "Catalog" ...). All possible types of fields described by this metadata structure are defined in the table (item 5).

Since the number of fields described in the tables (items 4, 6) can be quite large in both “Case” and “PT”, the concept of “stage” is introduced. A stage is a group of ordered (for the convenience of the user) fields from their common list. For example, the table “Persons in the case” may have stages: “Information about the person” (fields: “Name”, “Gender”, “Date of birth” ...), “Information about the crime” (fields: “Date of the crime ”,“ The plot of the charge ”...),“ Information on the sentence ”(fields:“ Date of sentencing ”,“ Sentence ”...), etc. At least one step must be described for each table.

In the metadata structure, the “stage” is encoded as follows: in the tables (items 7, 10), the list, name and sequence (if there are several stages) of each of the stages (in our example, this means that for the table “Persons in the case” is defined three stages). And in the tables (pos. 8, 9) those fields are described that are included in a particular stage.

After the steps are described for “Cause” and each of the PTs, it is possible to differentiate access rights for each user group described in the tables (pos. 8, 9) for each user group described in the table (pos. 23) . Possible access rights: “Read only”, “Field is not available” ... are stored in the table (pos.13).

For example, indicate that the “Accusation plot” field will be inaccessible to the user of the “Statistics” group, will be read-only to the user of the “Secretary of the Chancellery” group and will be available for change to the user of the “Judge” group. In the metadata structure, the distinction is encoded as follows: for each field of the stage described in the tables (pos. 8, 9), the tables (pos. 11, 12) indicate the list of access rights (pos. 13) and the group (pos. 23), on which this restriction is imposed.

When the user enters data, it becomes necessary to verify the "correctness" of the information entered. All the verification logic is in the procedures and functions located on the database server - with this approach, to change the verification logic, you need to make an adjustment only to the function or procedure itself, without affecting the user's workstation itself. Their list, as well as the sequence of "operation" are defined in the tables (pos. 14, 17), and the parameters (field values; user working in the system; user group ...), which are transmitted, if necessary, in the tables (pos. 15, 16).

After the description of the physical and logical structure is made in the metadata (pos. 1-13, 21-23), it is necessary to be able to configure the actions performed with the data at the time of adding, deleting and modifying records. Representation of these actions in the form of settings allows you to be independent of the type of DBMS and have “freedom of action” for data processing. These operations look like SQL scripts and are stored in tables (pos. 18, 19, 20).

All users of the system (pos. 25) are divided into groups (pos. 23). Each group is endowed with different permissions to access the general data array (but not to specific fields of the stage!), For example, the “Database Administrator” has full access to all information in the database; “Judges” full access to registration information on cases that they have considered and court documents that they have created; "Secretaries of Chancery" to registration information and information necessary for the formation of statistical reports, etc. There are no predefined “types” of groups (similar to pos. 5 or pos. 13). Their list, quantity, name and authority are determined during the design of the file cabinet in the table (item 23).

Before starting work with the system, the administrator using the database structure management software must enter in the table (pos. 25) all users (user name / for example, full name / and password), and bind them to table groups (pos. 23) with using the table (pos. 24).

Work with directories is carried out using two metadata tables. In one (item 21) there is information on the name of all the directories (for example, “Case Categories”, “Study Results” ...), in the other (pos. 22) is the content of all the directories (for our example, “Category 1”, "Category 2" ...).

Since the requirements for the functionality of tables that store data are different, in the description of the metadata they use several different types of “subordinate” tables:

- ordinary

- documents and templates

- movement of affairs

- libraries

In "ordinary tables" it is supposed to store data that does not require any special processing.

Tables defined in the metadata as “Documents” and “Templates” are responsible for the formation and storage of court documents tied to the registration card for the case.

Tables of the "Documents" type store documents that are relevant to a single case. The number of documents in the case is not limited. The data in these tables can serve as the basis for creating an archive of court documents.

Tables of the "Templates" type store typical document templates from the summons to the court to the determination made in the case. All templates are unique to each user. At any time, it is possible to create a new template that meets the requirements of judicial proceedings at a given time or to modify an existing one. When forming a document according to a template, data already entered on cases are used, which greatly simplifies the procedure for generating all accompanying documents for cases, such as summons, telegrams, notifications, etc.

The need for the type of “Movement of business” is due to the fact that the mode of working with data in tables of this type differs significantly from “ordinary tables”. As a rule, the data in these tables are entered automatically (by creating an algorithm of logical and procedural control) and they are used to stage the process of passing the case in court.

The type "Libraries" is used when connecting any external module (another program, etc.). These tables describe the interaction interface of this application with the external. In fact, this type is not a table in the classical sense, but just a method of calling another application.

The output potentials of the bits of the register 100 are supplied to the inputs of the corresponding elements 104-106 AND, which are also controlled by the output potentials of the corresponding bits of the counter 101. The counter 101 has a ring structure.

In the initial state, the first bit of the counter 101 is set to a single state. In this case, the direct output of each discharge of the counter 101 is connected to the input of the corresponding element 104-109 I.

As a result of this, the synchronizing pulse from input 121, having passed the OR element 110, is delayed by the element 113 for the time the data are entered into the register 100 of module 8, and then it goes to the inputs of the elements 104-109 AND, interrogating their status.

If the unit code is in the first category of register 100, then out of all elements 104-109 AND, only element 104 I will be in the open state, since it will be open at a different input with a high potential from the output of the first category of counter 101, and all other elements 105 -109 And they will be closed by low potentials from the remaining bits of counter 101.

The synchronizing pulse from the output of the element 104 And, firstly, is fed to the read input of a fixed memory cell of the permanent storage device 102, which stores the code of the number of the first case, which is in the file cabinet of the court proceedings, and reads the code of the case number to the input of the register 103.

Secondly, the same synchronizing pulse passes through the OR element 111, is delayed by the element 114 while reading the case number code from the ROM 102, and enters the synchronizing input of the register 103, entering the case number code into it.

The code of the case number from the output of the register 103 through the output 26 of the system is issued to the automated workstation, where the synchronizing pulse from the output 33 of the system also arrives.

In parallel with this, the synchronizing pulse from the output of the delay element 113 passes the And element 107, also open at the second input with the high potential of the first discharge of the counter 101, then the OR element 112 passes, and, firstly, it goes to the shift input of the ring counter 101, which shifts the unit from the first to the second category.

Secondly, the synchronizing pulse from the output of the OR element 112 passes through the OR element 110, is delayed by the delay element 113 and again goes to the inputs of the elements 104-109 I.

If the next bit of the register 100 is in the zero state, then the next case number code will not be read from the ROM 102, since the And element 105 will be closed. At the same time, the synchronizing pulse from the output of the delay element 113 passes through the AND element 108, opened by the high potential of the second discharge of the counter 101, and then goes to the shift input of the counter 101 and the OR element 110, and the cyclic process of issuing the case number codes in the court’s file is repeated. paperwork, to the user's workstation.

As a result of this, the main file cabinet window is formed on the user's workstation screen, an example of which is shown in Fig. 10.

The main window of the case file consists of the following elements (areas):

- title, main menu and toolbar of the main window;

- panel with a list of cases;

- shortcuts (bookmarks) that open access to individual information sections;

- toolbar of the current information section;

- one or two panels for entering, viewing and editing information on the case, which is currently active (on which stands a pointer in the panel with the list of cases).

The title of the window (the topmost, darkest area in figure 10) indicates the name of the file cabinet, as well as the name of the user who is logged in. In the right corner there are three buttons standard for all Windows applications designed to exit the system, to minimize the window to an icon and to enable / disable full-screen mode.

Below the header is the main menu bar of the items:

- service;

- work with documents;

- various reference information.

The listed menu items contain sub-items shown in Fig. 11 and allowing to switch to the corresponding operating modes.

A panel with a list of cases is shown in Fig. 12. This panel displays the numbers of only those cases that are related to the corresponding user who is logged in. The panel is designed to visualize the case number and to move from case to case using the navigation keys or with the mouse.

To go to cases whose numbers did not fit on the screen, the panel has a vertical scroll bar. At the bottom of the search panel displays information about the total number of civil cases that the user has access to in this session.

When you set the pointer on the line with the number of the required case and left-clicking, the corresponding information sections of the selected case appear on the right side of the AWP screen. In this case, the code of the case number selected on the display panel enters the information input of module 9, where it is entered by the synchronizing pulse of the manipulator from the input 22 of the system.

From the output of module 9, the case number code through the input 134 of module 10 is fed to the input of the decoder 125, which decrypts the case number code and opens one input 128-130 I.

At the same time, the synchronizing pulse from the input 22 of the system through the input 135 of the module 10 is fed to the input of the element 131, where it is delayed by the time the code of the case number is entered into the module 9 and the decoder 125 is activated, and then, passing through the corresponding element 128-130 And, the clock firstly, it enters the read input of a fixed memory cell of the permanent storage device 126, which contains the address of the contents of the requested case number in the server database, and reads it to the information input of the register 127.

Secondly, the synchronizing pulse from the output of element 131 is delayed by element 132 for the duration of reading the address code from the ROM 126, and arrives at the synchronizing input of the register 127, bringing the read address code into it.

From the output 136 of the module 10, the case address code is sent to the input 72 of the module 4, where the elements OR 68 of the group pass, and is issued to the address output 39 of the system.

In parallel, the synchronizing pulse from the output of element 132 is delayed by the time the code is entered in the register 127 of module 10 by element 133, and from the output 137 of module 10, through the output 34 of the system, it enters the input of the second channel of the database server interrupt.

By this signal, the server goes to the subroutine for reading the case data at the specified address, issuing them to the information input 18 of the system and entering them into module 11 with a synchronizing pulse from the server to input 23.

From the output 155 of module 11, the contents of all sections of the edited case are output to the output 27 of the system, from the output of 156 module 11, the output of the section “CASE” is fed to the input 160 of the module 12, from the output 157 the output of the section “HEARINGS” is sent to the input 161 of the module 12, from the output 158 module 11, the output of the section "DOCUMENTS" goes to the input 162 of the module 12, and from the output 159 of the module 11 the output of the section "TEMPLATES" goes to the input 163 of the module 12.

All information about the case is logically grouped. Only the contents of one section can be displayed on the screen at a time. To do this, just click on the appropriate shortcut:

- A BUSINESS;

- HEARINGS;

- DOCUMENTS;

- TEMPLATES.

If, for example, you select the “CASE” tab and click on it with the mouse, then the input code for the “CASE” section is sent to the input of system 19 and then the input of module 12, and the input of the system 24 receives a synchronizing signal from the mouse button, which goes to the synchronizing the input of the register 140 and enters into it the code of the indicated operation to select the section of the case.

From the output of register 140, the code of the selected case section is sent to the input of the decoder 144, which in our example decrypts the operation code and opens elements 142 And groups and element 146 I one input. The contents of the section are fed to the other input of elements 142 And groups from the input 160 of module 12 "A BUSINESS".

In parallel with this, the synchronizing signal from input 24 passes an OR element 150, is delayed by element 151 for the time the operation code is entered into register 140, and then it goes to the third input of elements 142 of the group, rewriting the contents of the CASE section through system output 28 to the user's workstation input.

Similarly, through the outputs 29-31 of the system, the remaining sections of the selected case are issued to the corresponding inputs of the user's workstation.

Having entered the corresponding section, the user has the opportunity to perform a set of operations, an example of which can be illustrated by the user's work with the "Documents" section.

The structure of the “Documents” section is represented by the following required details:

- date of creation of the document - determines the date of creation of the document;

- type of document - is determined by the corresponding directory of the subsystem having both predefined values (necessary for unified accounting) and values specified by the user;

- name of the document - defines the name of the document that will appear in all links to this document;

- text of the document - defines the contents of the document (usually a msword format file);

- author of the document - defines the name of the user who is the author of the document;

- a sign of publication of a document - determines the possibility of access to the document to users who are not its (document) authors;

- appointed date for the execution of the document - determines the date by which (inclusive) the document must be executed;

- date of actual execution - determines the date of actual execution of the document;

- comment - defines a line of arbitrary text.

At the same time, the Documents component implements the following set of functions:

- creating a new document;

- editing an existing document;

- deletion of an existing document;

- Insert the value of the index of the file cabinet into the document;

- publication of the document - opening access to the document to users who are not the author of the document;

After finishing work with the “Documents” section, the user from his workstation gives the command “Save the entered changes” by issuing a synchronizing signal to the input 25 of the system.

The control signal from the input 25 of the system is supplied to the inputs of elements 146-149 I. however, only one of them will be open at the other input, relating to the section the user is working with, for example, element 146 I. Then the control pulse passes through element 146 and through output 35 the system enters the input of the third channel of the server interrupt.

With the arrival of this signal at the input of the third interrupt channel, the server switches to the subroutine for writing the generated case file from the system output 27 to the system database at the address that corresponds to the address of the selected case installed on the system address output 39.

Thus, the introduction of new nodes and blocks made it possible to significantly increase the system performance by localizing the addresses of the file of cases according to the user ID allowed to work with the specified file of cases.

Sources of information taken into account when drawing up the description of the application:

1. US patent No. 5136708 M. cl. G 06 F 15/16, 1992

2. US Patent No. 5129083 M. cl. G 06 F 12/00, 15/40, 1992 (prototype).

Claims (1)

An automated database management system for judicial and executive records management, containing a password code receiving unit, the information and synchronizing inputs of which are the first information and synchronizing inputs of the system, a unit for generating a server database record read address, the information output of which is the system address output, and the synchronizing output is the first synchronizing system output, module for receiving user passwords from the database, information and synchronization whose synchronizing inputs are the second information and synchronizing inputs of the system, the module for receiving file numbers of the file cabinet, the information and synchronizing inputs of which are the third information and synchronizing inputs of the system, the module for cyclic support of file numbers of cases, the information output of which is the first information output of the system, and the synchronizing output is the second synchronizing system output, the module for receiving case data from the server database, information and synchronize whose inputs are the fourth information and synchronizing inputs of the system, and one output is the second information output of the system, a module for issuing case data to the user, one information input of which is the fifth information input of the system, and other information inputs are connected to the corresponding outputs of the base data receiving module server data, while the synchronizing input of the module for issuing case data to the user is connected to the fourth synchronizing input of the system, the control inputs of the module the issuance of case data to the user are the first and second control inputs of the system, the information outputs of the case data issuing module to the user are the information outputs of the system group, and the control outputs of the case data issuing module to the user are the control outputs of the system group, characterized in that the system contains a password base address selection module users, the information input of which is connected to the output of the password code receiving module, and the synchronization input is connected to the first synchronizing at the input of the system, while one information output of the module for selecting the base address of user passwords is connected to the first information input of the module for generating the address for reading the server database records, and the synchronizing output is connected to the first synchronizing input for the module for generating the address for reading server database records, the user identification module, one information input of which is connected to the output of the password code receiving module, another information input of the user identification unit n to the output of the module for receiving user passwords from the database, and the synchronizing input is connected to the second synchronizing input of the system, while one output of the user identification module is connected to the installation input of the module for generating the address for reading the server database records, the password selection control module, the information input of which is connected with another information output of the module for selecting the base address of user passwords, the synchronizing input is connected to one output of the user identification module th, and the installation input is connected to another output of the user identification module, while the information output of the password selection control module is connected to the second information input of the server database record read address generation module, one synchronization output of the password selection control module is connected to the second synchronization input of the address generation module reading server database records, and the other synchronizing output is the system signal output, the module for localization of card addresses case file, the information input of which is connected to the third information output of the selection module of the base address of user passwords, and the synchronization input is connected to the other output of the user identification module, while the information output of the address file localization module of the case files is connected to the information input of the module for cyclic support of case file numbers, and the synchronizing output of the module for localization of the addresses of the file of cases is connected to the synchronizing input of the module of cyclic support of numbers of the file of cases, a filing case address selection module in the server database, the information input of which is connected to the output of the card file case receiving module and the synchronizing input is connected to the third synchronizing input of the system, while the information output of the filing case address selection module in the server database is connected to the third information input the module for generating the address for reading records of the server database, and the synchronizing output of the module for selecting the file address of the file cabinet in the server database is the third synchronizer yuschim output system.