CN111047301B - Spacecraft development process management system and method - Google Patents
Spacecraft development process management system and method Download PDFInfo
- Publication number
- CN111047301B CN111047301B CN201911343492.3A CN201911343492A CN111047301B CN 111047301 B CN111047301 B CN 111047301B CN 201911343492 A CN201911343492 A CN 201911343492A CN 111047301 B CN111047301 B CN 111047301B
- Authority
- CN
- China
- Prior art keywords
- model
- module
- node
- development
- submodule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention provides a spacecraft development process management system which comprises six modules, namely a standard library, a development process, a file system, a development team, system management and user login. The invention further provides a spacecraft development process management method based on the system. The spacecraft development process management platform is applied to the spacecraft development process, the problems of task nodes and process change in the spacecraft development process can be quickly solved, the problems in the spacecraft development process can be timely found through model process difference analysis and model file system comparison analysis, the spacecraft development quality is strictly controlled, the working efficiency of the model development process is improved, and the spacecraft is ensured to be successfully launched on schedule.
Description
Technical Field
The invention relates to the technical field of data analysis, in particular to a spacecraft development process management system and method.
Background
The spacecraft development process management comprises technical process management and quality management, because the spacecraft development tasks relate to multiple departments, wide contents and dynamic and variable processes, a plurality of quality problems can occur in the execution process of one type task, the problems of high complexity, long period, heavy tasks, limited manpower resources and the like exist, the development process is difficult to control in real time, and along with the continuous improvement of the development function and the structural complexity of the spacecraft, an old development management system is difficult to meet the new requirements of the whole process and all-round management.
Disclosure of Invention
The invention aims to provide a spacecraft development process management system and a spacecraft development process management method, which are used for solving the problems of task node and process change in the existing spacecraft development process.
The technical scheme for solving the technical problems is as follows:
a spacecraft development process management system comprises a standard library module, a development process module, a file system module, a development team module, a user login module and a system management module, wherein the development process module, the file system module, the development team module, the user login module and the system management module are respectively connected with the standard library module;
the standard library module is used for providing standard basic data support for the development flow module, the file system module, the development team module and the third-party system;
the development flow module is used for analyzing the difference between the model flow and the standard flow and providing administrator setting operation for the development team module;
the file system module is used for analyzing the difference between the files in the standard library module and the spacecraft model number files;
the development team module is used for inquiring a development team personnel list according to the specific spacecraft model;
the user login module is used for controlling the access authority of the system;
the system management module is used for controlling data management and authority operation of the system.
Further, the standard library module comprises a standard file system sub-module, a development team sub-module and a general flow sub-module;
the standard file system submodule is used for taking a scheme submitted in the process of developing the spacecraft and related files as a standard file system to provide a reference standard for model development, the standard file system submodule is divided into different versions according to the year, and each standard file system version comprises a file name list and files corresponding to the names of all stages in the process of developing the spacecraft;
the development team submodule is used for taking a role participated in the development process of the spacecraft model as a standard role of each spacecraft model development team;
the general flow sub-module is used for displaying standard task nodes and node sequences in the development process of the spacecraft on a WEB page in a flow chart mode.
Still further, the standard file system sub-module comprises a first list query unit, a version increase unit, a version modification unit and a version deletion unit;
the development team submodule comprises a role list query unit, a role adding unit, a role modifying unit and a role deleting unit;
the general flow submodule comprises a flow version management unit, a flow chart management unit and a flow node management unit;
the flow version management unit comprises a list query subunit, a version increasing subunit, a version modifying subunit, a version deleting subunit, a flow chart management subunit, a flow chart releasing subunit and a flow node management subunit;
the flow chart management unit comprises a flow chart drawing subunit, a flow chart inquiring subunit, a flow chart deriving subunit, a flow node deriving subunit and a flow chart layout adjusting subunit;
the flow node management unit comprises a node list inquiry subunit, a node adding subunit, a node modifying subunit, a node deleting subunit, a node sorting subunit, a node leading-in subunit, a node leading-out subunit, a node type setting subunit, an automatic numbering subunit, a node logical relationship subunit and a node list automatic generation flow chart subunit.
Furthermore, the development flow module comprises a model flow submodule, a difference analysis submodule and a model management submodule;
the model flow sub-module is used for maintaining specific model flow information and providing model flow data for the difference analysis sub-module as a data source for difference analysis;
the difference analysis submodule is used for comparing and analyzing the model process node and the standard process node, and searching out potential quality problems in the model development process;
the model management submodule is used for carrying out data maintenance on the spacecraft model according to the spacecraft model management and setting a model manager;
the model flow sub-module comprises a model annual flow chart management unit, a model flow node list unit, a model flow task tracking and monitoring unit and a model flow chart drawing unit;
the model management submodule comprises a second list query unit, a list adding unit, a list modifying unit and a list deleting unit.
Still further, the file system module comprises a model file system submodule and a statistical analysis submodule;
the file system submodule is used for maintaining model file system data and file attachments and providing basic data for the statistical analysis submodule;
the statistical analysis sub-module is used for analyzing the difference between the standard file system and the model file system and counting and prejudging the influence result of the development process design files and scheme files which are lacked or added in the model file system on the model quality.
Furthermore, the development team module comprises a model development team sub-module and a flow chart editing permission sub-module;
the model development team submodule is used for providing authority for managing model checking and analyzing the influence of the integrity of model development team personnel on model quality;
the flow chart editing permission submodule is used for providing development flow chart editing permission for members of a development team.
Still further, the system management module comprises a system administrator submodule, a security and secrecy administrator submodule and a security audit administrator submodule;
the system administrator submodule is used for protecting the data security of the system; the system comprises a menu management unit, an organization management unit, a role management unit, a user management unit, a dictionary management unit and a system operation log unit;
the security and secrecy manager submodule is used for providing the access authority of each service module of the system for a user and providing user security settings, and the user security settings comprise account unfreezing and security classification settings;
the security and confidentiality manager submodule comprises a role authority management unit, a role authorization unit, a user authorization unit and a user confidentiality level setting unit;
the safety audit manager submodule is used for viewing operation logs of a system manager and a safety secrecy person; the system comprises an administrator operation log unit and a security personnel operation log unit.
Still further, the user login module comprises a user system authentication submodule, and the user system authentication submodule is used for authenticating the access and login authority of the user.
Based on the system, the invention also discloses a spacecraft development process management method, which comprises the following steps:
s1, generating general process node data, standard file system data and standard development team role data according to spacecraft development, and maintaining the data of a standard library module by utilizing the data;
s2, maintaining data of the model management submodule, setting the authority of a model manager and the model manager for logging in the system, maintaining data of a model development team, and setting the editing and checking authority of a model flow chart of personnel of the development team;
and S3, logging in the system by using model development personnel set by the model development team module, and maintaining the data of the model flow submodule and the data of the file system submodule.
S4, data of the universal process sub-module is quoted according to the data of the model process sub-module to serve as basic data of a model development process, node data of the development process is modified according to the characteristics of the model development process, and the modified process data serve as model development process data;
s5, according to the model development flow data, utilizing difference analysis of development flow data in the general flow sub-module and the model flow sub-module to identify a vulnerability in the model development process;
s5, basic data of a standard file system sub-module is quoted as basic data of a model file system, the file system data is modified according to the vulnerability development process node data, and the modified data is used as the model file system;
and S6, according to the data of the model file system, performing difference analysis by respectively using the data of the standard file system sub-module and the model file system sub-module, identifying scheme design documents and development reports which are lacked in the model development process, finding out potential quality problems of model development, and finishing management of spacecraft development.
The invention has the following beneficial effects:
the invention provides a spacecraft development process management system and a method, comprising 6 modules of a standard library, a development process, a file system, a development team, system management, user login and the like; the standard library comprises 3 submodules of a file system, a development team and a general flow, the development flow comprises 3 submodules of model management, difference analysis and model flow, the file system comprises a model file system and 2 submodules of statistical analysis, the system management comprises 3 administrators of a system administrator, a safety officer and an auditor, the three rights are separated, and the safety of system data is protected, wherein the administrator comprises 6 submodules of menu management, mechanism management, role management, user management, dictionary management, system operation logs and the like, the safety officer comprises 3 submodules of role authorization, user operation logs and the like, the auditor comprises 2 submodules of administrator operation logs, safety officer operation logs and the like, and the user login comprises CA login, domain account login and user name password login. The spacecraft development flow management platform is applied to the spacecraft development process, the problems of task nodes and flow change in the spacecraft development process can be solved quickly, the problems in the spacecraft development process can be found in time through model flow difference analysis and model file system comparison analysis, the spacecraft development quality is controlled strictly, the work efficiency of the model development flow is improved, and the successful launch of the spacecraft on schedule is guaranteed.
Drawings
FIG. 1 is a system block diagram of the present invention.
FIG. 2 is a schematic diagram of the standard library module of the present invention.
Fig. 3 is a schematic structural diagram of a process version management unit according to the present invention.
FIG. 4 is a schematic diagram of a flow chart management unit according to the present invention.
Fig. 5 is a schematic structural diagram of a flow node management unit according to the present invention.
FIG. 6 is a schematic structural diagram of a model flow sub-module according to the present invention.
Fig. 7 is a schematic structural diagram of a model management submodule in the present invention.
FIG. 8 is a schematic structural diagram of a system administrator submodule in the present invention.
FIG. 9 is a diagram of the sub-module of the security and privacy administrator of the present invention.
FIG. 10 is a block diagram of a security auditor administrator sub-module of the present invention.
FIG. 11 is a flow chart of the method of the present invention.
Fig. 12 is a schematic diagram of a node and a node relationship in this embodiment by importing Excel.
Fig. 13 is a flowchart of Excel node data in this embodiment.
Detailed Description
The following description of the embodiments of the present invention is provided to facilitate the understanding of the present invention by those skilled in the art, but it should be understood that the present invention is not limited to the scope of the embodiments, and it will be apparent to those skilled in the art that various changes may be made without departing from the spirit and scope of the invention as defined and defined in the appended claims, and all matters produced by the invention using the inventive concept are protected.
Examples
The invention constructs a whole-process, monitorable and visual spacecraft process development management system, which is applied to various model systems, subsystems and single-machine products borne by a whole body part, according to the aerospace product development process and the product guarantee working characteristics, a management platform takes system-level products as key points, development and planning as basis and quality management standards as drive, links originally dispersed production processes, summarizes and analyzes data such as plan, progress, quality and the like in real time, forms a closed loop according to results and deliverables to the completion conditions of assessment nodes, realizes strict progress management and quality monitoring of the whole process, effectively traces problems and accountants, and ensures that model tasks are completed successfully on schedule.
As shown in fig. 1, a spacecraft development process management system includes a standard library module, and a development process module, a file system module, a development team module, a user login module, and a system management module, which are respectively connected to the standard library module;
the standard library module is used for providing standard basic data support for the development flow module, the file system module, the development team module and the third-party system;
the development flow module is used for analyzing the difference between the model flow and the standard flow and providing administrator setting operation for the development team module;
the file system module is used for analyzing the difference between the files in the standard library module and the spacecraft model number files;
the development team module is used for inquiring a development team personnel list according to the specific spacecraft model;
the user login module is used for controlling the access authority of the system;
the system management module is used for controlling data management and authority operation of the system;
as shown in fig. 2, the standard library module includes a standard document system sub-module, a development team sub-module, and a general flow sub-module; the standard file system submodule is used for taking a scheme submitted in the process of developing the spacecraft and related files as a standard file system to provide a reference standard for model development, the standard file system submodule is divided into different versions according to years, and each standard file system version comprises a file name list and files corresponding to the names of all stages in the process of developing the spacecraft; the development team submodule is used for taking a role participated in the development process of the spacecraft model as a standard role of each spacecraft model development team; the general flow sub-module is used for displaying standard task nodes and node sequences in the development process of the spacecraft on a WEB page in a flow chart mode. The standard file system sub-module comprises a first list query unit, a version increasing unit, a version modifying unit and a version deleting unit; the development team submodule comprises a role list query unit, a role adding unit, a role modifying unit and a role deleting unit; the general flow sub-module comprises a flow version management unit, a flow chart management unit and a flow node management unit.
As shown in fig. 3, the process version management unit includes a list query subunit, a version addition subunit, a version modification subunit, a version deletion subunit, a process diagram management subunit, a process diagram release subunit, and a process node management subunit; as shown in fig. 4, the flowchart management unit includes a flowchart drawing subunit, a flowchart querying subunit, a flowchart deriving subunit, a flow node deriving subunit, and a flowchart layout adjusting subunit; as shown in fig. 5, the process node management unit includes a node list query subunit, a node addition subunit, a node modification subunit, a node deletion subunit, a node sorting subunit, an import node subunit, an export node subunit, a node type setting subunit, an automatic numbering subunit, a node logical relationship subunit, and an automatic flow chart generation subunit for the node list.
As shown in fig. 6, the development process module includes a model process sub-module, a difference analysis sub-module, and a model management sub-module; the model flow sub-module is used for maintaining specific model flow information and providing model flow data for the difference analysis sub-module as a data source for difference analysis; the difference analysis submodule is used for comparing and analyzing the model process node and the standard process node, and searching out potential quality problems in the model development process; the model management submodule is used for carrying out data maintenance on the spacecraft model according to the spacecraft model management and setting a model manager; the model flow sub-module comprises a model annual flow chart management unit, a model flow node list unit, a model flow task tracking and monitoring unit and a model flow chart drawing unit; as shown in fig. 7, the model management submodule includes a second list inquiry unit, a list addition unit, a list modification unit, and a list deletion unit.
The file system module comprises a model file system submodule and a statistical analysis submodule; the file system submodule is used for maintaining model file system data and file attachments and providing basic data for the statistical analysis submodule; the statistical analysis submodule is used for analyzing the difference between the standard file system and the model file system and counting and prejudging the influence result of the lack or increase of the development process design files and scheme files in the model file system on the model quality.
The development team module comprises a model development team sub-module and a flow chart editing permission sub-module; the model development team submodule is used for providing authority for managing model checking and analyzing the influence of the integrity of model development team personnel on model quality; the flow chart editing permission submodule is used for providing development flow chart editing permission for members of a development team.
The system management module comprises a system administrator submodule, a security and secrecy administrator submodule and a security audit administrator submodule; as shown in fig. 8, the system administrator submodule is used for protecting the system data security; the system comprises a menu management unit, an organization management unit, a role management unit, a user management unit, a dictionary management unit and a system operation log unit; the security and secrecy manager submodule is used for providing access permission of each service module of the system for a user and providing user security setting, and the user security setting comprises account number unfreezing and security level setting; as shown in fig. 9, the security and privacy administrator sub-module includes a role authority management unit, a role authorization unit, a user authorization unit, and a user privacy level setting unit; as shown in fig. 10, the security audit administrator sub-module is used to view system administrator and security clerk operation logs; the system comprises an administrator operation log unit and a security personnel operation log unit. The user login module comprises a user system authentication submodule which is used for authenticating the access and login authority of a user.
As shown in fig. 11, the present invention is based on the above system, and also discloses a spacecraft development process management method, including the following steps:
s1, generating general process node data, standard file system data and standard development team role data according to spacecraft development, and maintaining the data of a standard library module by utilizing the data;
s2, maintaining data of the model management submodule, setting the authority of a model manager and the model manager for logging in the system, maintaining data of a model development team, and setting the editing and checking authority of a model flow chart of personnel of the development team;
and S3, logging in the system by using model development personnel set by the model development team module, and maintaining the data of the model flow submodule and the data of the file system submodule.
S4, data of the universal process sub-module is quoted according to the data of the model process sub-module to serve as basic data of a model development process, node data of the development process is modified according to the characteristics of the model development process, and the modified process data serve as model development process data;
s5, according to the model development flow data, utilizing difference analysis of development flow data in the general flow sub-module and the model flow sub-module to identify a vulnerability in the model development process;
s5, basic data of a standard file system sub-module is quoted as basic data of a model file system, the file system data is modified according to the vulnerability development process node data, and the modified data is used as the model file system;
and S6, according to the data of the model file system, performing difference analysis by respectively using the data of the standard file system sub-module and the model file system sub-module, identifying scheme design documents and development reports which are lacked in the model development process, finding out potential quality problems of model development, and finishing management of spacecraft development.
In this embodiment, basic data such as a general flow submodule, a standard file system submodule, a development team submodule, and the like are maintained in the standard library module. In the development process module, the data of the universal process submodule is quoted by the medium-size process submodule to be used as the basic data of a model development process, the node data of the development process is modified according to the characteristics of the model development process, and the modified process data is used as the model development process data; the development process data in the general process sub-module and the model process sub-module are quoted in the difference analysis sub-module for comparative difference analysis, and potential quality problems in the model development process are identified; the model management submodule is used for maintaining basic information of spacecraft models and setting a model manager, the model manager maintains information of personnel of a model development team in the development team module and sets editing and viewing permissions of the personnel of the development team on a flow chart; a model file system sub-module in a file system module refers to basic data of a standard file system sub-module as basic data of a model file system, the file system data is modified according to the self characteristics of the model, and the modified data is used as the model file system; and the system administrator submodule maintains the information of the menu, the mechanism, the role, the personnel and the data dictionary. And the security and secrecy manager submodule is used for setting the authority of the roles, assigning roles to business personnel, setting security level and freezing or unfreezing user states. And the safety audit manager submodule audits operation logs of a system manager and a safety secrecy manager.
In the embodiment, the spacecraft development process management platform system is based on Java + Oracle + easy UI + mxGraph environment, and is applied to a Web system for task node monitoring and process quality management in the spacecraft development process; the standard library module comprises 3 sub-modules of a file system, a development team and a general flow; the file system submodule is used for: according to actual business requirements, a scheme and related files required to be submitted in the process of spacecraft development are used as a standard file system, and a reference standard is provided for model development. The standard file system is divided into different versions according to the year, each standard file system version comprises a file name list and files corresponding to the names in each stage in the spacecraft development process, and one file name can correspond to a plurality of file attachments. The standard file system comprises version list query, version increase, version modification and version deletion; the file list inquiry, the file name maintenance and attachment uploading, the file modification and the file deletion are included below each version.
In this embodiment, the development team submodule is configured to: according to actual business requirements, roles which must participate in the process of developing the spacecraft model are used as standard roles of each model developing team, and at least one person needs to participate in the developing work of the spacecraft below each role. The standard development team comprises role list query, role addition, role modification and role deletion.
In this embodiment, the general flow sub-module is configured to: according to actual business requirements, standard task nodes and node sequences required in the development process of the spacecraft are displayed on a WEB page in a flow chart mode. The standard development process comprises process version management, wherein the process version management comprises list query of versions, version addition, version modification, version deletion, process diagram management, process diagram release and process node management. The flow chart management comprises flow chart drawing, flow chart query, flow chart picture export, flow node export to Word and flow chart layout adjustment; the process node management comprises node list query, node addition, node modification, node deletion, node sorting, node import through Excel, node export to Excel, node type setting, automatic numbering, one-key node logic relationship setting and automatic generation of a flow chart through a node list.
In this embodiment, the node list management: and clicking the node list to enter the node list management page of the flow chart through an operation button column of the version list page, and inquiring all list items of the flow chart by default. The fields displayed by the list are respectively a number level, a unique code, a membership, a convergence, a node name, a node number, an execution state, a plan number, completion time and an operation button column. Above the node list, flow node maintenance buttons are arranged, which are buttons for main line, primary branch, secondary branch, automatic numbering, emptying aggregation, emptying logic, setting logic, importing Excel, exporting Excel, flow diagram display, adding new nodes, and the like.
In this embodiment, node and relationship maintenance: the node data maintenance has 3 modes in common, and Excel, button bars and flowchart editing are imported. Introducing Excel: and maintaining the nodes and the node relation by importing Excel data.
In this embodiment, clicking the "import Excel" button of the button bar, popping up the Excel file import page, clicking the "download Excel template", inputting the required data in the Excel template according to the rule, and importing the data into the system by importing Excel, as shown in fig. 12:
numbering level: the logical relationship and the automatic numbering of the flow nodes depend on the numbering levels which are respectively as follows: the main line, the first-level branch and the second-level branch, the main line node is represented by the number "1", the first-level branch is represented by the number "2" and "3", wherein 2 represents the branch start, 3 represents the branch follow, the second-level branch is represented by the number "4" and "5", wherein 4 represents the branch start, 5 represents the branch follow, 2n represents the branch start, and 2n +1 represents the branch follow. A necessary precondition for setting the numbering level is to set the order of the nodes.
Item code number: the master nodes are denoted by M1, M2, M3.. Mn, the level heights of the primary branch nodes are denoted by a, b, c.. Z, and the lengths of the primary branch nodes are denoted by 1, 2, 3.. N, such as: first level of branch node: m3a1, M3a2, M3a3.. M3an, primary branch node second tier: m3b1, M3b2, M3b3.. M3bn; the first level of the secondary branch of M3b1 is denoted as M3b1a1, M3b1a2, the second level of the secondary branch of M3b1 is denoted as M3b1b1, M3b1b2, and so on. The secondary branch converges to the primary branch, which returns to the main line node and must form a closed loop.
Is subject to: the current node father node is numbered, the M1 node is an initial node, and the father node is empty, for example: the father node of the M2 node is the M1 node, the father node of the M3a1 is the M2 node, and the father node of the M3b2 is the aggregation node MERGE-M3b1.
In this embodiment, the node type: m represents a primary node, Q represents a quality node, and S represents a secondary node.
In this embodiment, the unique code: the unique code represents a unique value of the current node in the flowchart.
In this embodiment, after the Excel completes the node data work, it is represented in a flow chart manner as shown in fig. 13;
in this embodiment, the button bar: node relationships are maintained by operating different types of button operations:
clicking a 'new node' button of a button column, inputting necessary information of a node name, clicking a 'none' node level selection, belonging to the 'none' node selection, selecting a 'main node' node of a node type, clicking a 'save' button, generating a first starting node in a flow chart as a main line node 1, clicking the 'new' button on an operation column of a node list, adding a next node of the first node, selecting a 'next level' node level, selecting a 'main node' node of the node type, clicking a 'save' button, generating a second node main line node 2, repeating the steps in sequence, and generating the main line node and the branch node.
And clicking a 'modification' button of the button column to modify the relationship and description information of the currently selected row node.
Clicking a 'delete' button of the button column to delete the node of the currently selected row, and automatically butting the front node and the rear node of the current node to form a superior-inferior relation.
And completing node entry of the flow chart by operating the steps, wherein if the entry node number level has errors, the number level of the node is adjusted by the main line, the primary branch and the secondary branch of the button column. The first-level branch needs to be converged into a main line node, the first-level branch or the second-level branch to be converged is selected, a 'convergence' button is clicked, and node convergence information is generated in a table in a converging mode.
Automatic numbering: and automatically numbering the nodes according to certain rules according to the node branch level and the information convergence system. Clicking the "automatic numbering" button, the system automatically generates the numbers of all nodes. The numbering rules are as follows: the node type is a main node, the level of a main line node is 1, the serial numbers are M1, M2 and M3.. Mn, and the like in sequence, the serial numbers of primary branches are 2 (branch start) and 3 (branch end), the serial numbers of a1 st layer of the primary branch of M2 are M2a1, M2a2 and M2a3.. M2an, the serial numbers of a2 nd layer of the primary branch are M2b1, M2b2 and M2b3.. M2bn, and the serial numbers of a3 rd layer of the primary branch are M2c1, M2c2 and M2c3.. M2cn in sequence; the number levels of the secondary branches are 3 (branch start) and 4 (branch end) M2b2, the number of the 1 st layer of the secondary branch is M2b1a1, M2b1a2, M2b1a3.. M2b1an, the number of the 2 nd layer of the secondary branch is M2b1b1, M2b1b2, M2b1b3.. M2b1bn, the number of the 3 rd layer of the secondary branch is M2b1c1, M2b1c2, M2b1c3.. M2b1cn by analogy; the convergent node numbers of the secondary branch nodes M2b1an, M2b1bn and M2b1cn are MERGE-M2b1, and the convergent node numbers of the primary branch nodes M2an, M2bn and M2bn are MERGE-M2; the node type is a quality node, the level of a main line node is 1, the serial numbers of the main line node are Q1, Q2 and Q3.. Qn, the serial numbers of the first-level branches are 2 (the beginning of the branch) and 3 (the end of the branch), the serial numbers of the 1 st layer of the first-level branch of the Q2 are Q2a1, Q2a2 and Q2a3.. Q2an, the serial numbers of the 2 nd layer of the first-level branch are Q2b1, Q2b2 and Q2b3.. Q2bn, and the serial numbers of the 3 rd layer of the first-level branch are Q2c1, Q2c2 and Q2c3.. Q2cn; the secondary branch number levels of 3 (branch start) and 4 (branch end) M2b2 are the secondary branch layer 1 numbers Q2b1a1, Q2b1a2, Q2b1a3.. Q2b1an, the secondary branch layer 2 numbers Q2b1b1, Q2b1b2, Q2b1b3.. Q2b1bn, and the like for the secondary branch layer 3 numbers Q2b1c1, Q2b1c2, Q2b1c3.. Q2b1cn; the convergent nodes of the secondary branch nodes Q2b1an, Q2b1bn and Q2b1cn are numbered as MERGE-Q2b1, and the convergent nodes of the primary branch nodes Q2an, Q2bn and Q2bn are numbered as MERGE-Q2; and the main node M and the quality node Q are mutually interspersed and displayed.
And node logic: the node logic refers to the incidence relation among the nodes, and the relation among the nodes has a parent-child relation and a peer relation. The nodes of parent-child relationship are in left-right chain structure, and the same level relationship is in up-down parallel structure. And the nodes automatically generate the logical relationship between the nodes by using a recursion and convergence algorithm according to the node sequence, the numbering level and the two key indexes. The necessary precondition for setting the logical relationship of the nodes is to ensure the sequence and the number level of the nodes and the accuracy of the two key values. And clicking a 'set logic' button by a user, automatically generating a connection logic relation between nodes by the system, clicking an 'empty logic' button, clearing the connection logic relation of all nodes in the flow chart, and clearing values which belong to and converge in two columns.
Exporting Excel: clicking an 'export Excel' button, outputting all node information under the flow chart to Excel by the system, and downloading the node information to a local computer of a user through a browser.
The flow chart shows that: clicking a 'flow chart display' button, and calculating the coordinate value of the node by the system according to the connection logic relationship between the nodes, wherein the abscissa distance between the two flow nodes is 200, the ordinate distance is 50, the node length is 120, and the node height is 60. The abscissa distance between the flow nodes and the sink nodes is 110, and the node diameter is 30; after the coordinate of each node is calculated, generating an XML file representing the flow chart according to an XML protocol format of the mxGraph, quoting a JS library of the mxGraph by a WEB browser, analyzing the XML by the mxGraph to generate codes in an SVG format, and rendering the codes to a user.
In this embodiment, the flow chart: and sequentially displaying information of the spacecraft development process nodes in a graph mode. Clicking a pop-up shortcut menu on the flow chart by a right key, wherein the menu comprises functions of adding nodes, modifying nodes, deleting nodes and checking details on the flow chart; and clicking a left button on the flowchart to drag the position of the flowchart. Clicking the plus sign on the upper right of the flow chart to amplify the flow chart, and clicking the minus sign to reduce the flow chart; clicking a 'picture exporting' button at the upper left, exporting a flow chart to png pictures and downloading the png pictures to a client; clicking a 'export WORD' button, the system inquires the detailed information of all the process nodes of the flow chart, exports the detailed information to a WORD file according to a certain format, and downloads the WORD file to a local computer of a user. Clicking the "export Visio" button, the system exports the flowchart to the VISIO file and downloads it to the user's local computer.
In this embodiment, the node is newly added: the flow node is clicked on the flow chart by right click, the lower level or the same level node of the node is newly added in a graph mode, and the list information of the flow chart node and the flow node is synchronous, related and influenced mutually in real time.
In this embodiment, modifying a node: and modifying the detailed information of the flow node, wherein the detailed information comprises fields such as node name, node type, membership, node level and the like.
In this embodiment, deleting a node: after the nodes on the flow chart are deleted, the nodes before and after the nodes are deleted can be automatically butted, and the flow chart is refreshed.
In this embodiment, the development process module includes a model process sub-module, a difference analysis sub-module, and a model management sub-module. A model flow submodule: the method comprises model year flow chart management, model flow node list, model flow task tracking and monitoring and model flow chart drawing. The nodes of the flow chart display different colors according to the plan state. Yellow: in the compilation, ice blue: issued, green: completed, pink: delayed completion, red: incomplete, grey: has been cancelled. And monitoring the state of the planned task node of the spacecraft development process in real time. Clicking the 'adjusting layout' button can adjust the node layout mode of the current flow chart, and clicking the 'saving' button to save the current modified flow chart. Clicking the cancel button cancels the modification of the layout of the current flow chart. The undo button is the last step in the return to the flowchart layout operation and the resume button is the undo of the undo. The export pictures button may export the current flow chart into png pictures format and download to the client. And clicking a node by a right button, popping up a right-click menu, wherein the right-click menu comprises a view detail, a newly added node, a modified node, a deleted node and a clear convergence, the drawing mode and the node management mode of the model flow chart are the same as the general flow submodule code implementation logics of the standard library module, the model flow management is an example of the standard library flow, and the model realizes the task node visual monitoring and the spacecraft development flow of a specific model.
In this embodiment, the difference analysis submodule: different stages of different versions in the general flow compare different stages in the model flow, such as the general flow scheme stage compares the model flow scheme stage, and the comparison results are displayed in four boxes with different colors. The number of general process nodes, the number of model process actual nodes and the number of model process newly added nodes. And the difference analysis list displays nodes with different comparison results by default, and clicks a 'display all' button to display all nodes of the general flow and the model flow at a certain stage. Clicking a development flow menu, and entering a difference analysis page; the difference analysis query condition is divided into a stage process node of a standard library and a certain model process node list comparison of a model process; displaying comparison statistical information, the total number of general process nodes, the total number of model process nodes, the number of model process missing nodes and the number of model process newly added nodes under a query condition; the difference analysis list takes the unique serial number of the flow node as a main line, the standard library node and the model library node are displayed on the same line, the missing node of the list line is represented by red color, and the newly added node is represented by yellow color; and the difference analysis list displays difference nodes of the standard library and the model library by default, a 'display all' button is clicked, and all node lists of the standard library and the model library of the query process are displayed in the list.
In this embodiment, the model management submodule: and the model management carries out data maintenance on the model, including the list query, addition, modification and deletion of the model. When the model is added, the manager of the model needs to be selected, and the model manager can maintain the personnel of the development team of the model.
In this embodiment, the file system module: the main objective of the file system is to analyze the difference between the files of the standard file system and the files of the model after all the files of a certain model are classified in the standard file system. And counting the total number of standard files of the file systems of different versions in the topmost blue square, wherein the number of the standard files corresponds to the actual files, and the number of the standard files does not correspond to the actual files. And counting redundant actual files related to the current model in a yellow box. The actual file synchronizes data from the AVIDM system through model coding, and the synchronized data file corresponds to a standard file system through a file unique code. Clicking on the associated actual file to view the current file version revision list. The login user can only check the file system under the model by the owned model authority. The system type automatically displays the system type in the field according to the model, the model field comprises deep space, remote sensing and navigation, and one model can only belong to one field.
In this embodiment, the development team module: the model development team module refers to a specific model development team module, a personnel list of the development team is inquired according to the specific model, only personnel in the model development team can check the data of the model, and a model manager maintains the development team of the model, including personnel addition, modification, deletion and list inquiry.
In this embodiment, the system management module: and the system management module divides a system administrator submodule, a security and confidentiality administrator submodule and a security audit administrator submodule according to the roles of the three persons.
In this embodiment, the system administrator submodule: the system administrator submodule comprises menu management, mechanism management, user management, role management and data dictionary management. The menu management mainly aims at the menu management of the service modules except for the system management; the organization management refers to administrative organization management, and comprises adding, modifying, deleting and listing query of organizations; user management means adding, modifying, deleting and listing query to system service users; the role management refers to the role maintenance of the authority of the system operation module, and comprises role addition, modification, deletion and list inquiry; the data dictionary management comprises a system data dictionary and a business data dictionary, and the dictionary data used in the system is managed, and the data dictionary management specifically comprises the following characteristics:
1) Configuring and adjusting system parameters;
2) Establishing a service account, wherein the service user account is unique and cannot be modified;
3) The user sets a secret level, and the secret level comprises (secret, secret and none);
4) The database secret level data is tamper-proof, and the user ID + secret level- > md5 encryption- > is stored in the database- > the user secret level is inquired each time, tamper-proof check is carried out;
5) Establishing a mechanism, a data dictionary and role (adding, deleting, changing and searching) functions;
6) Three-member account numbers cannot be created, and the three-member account numbers cannot be seen;
7) Checking system operation logs (including system task logs, system abnormal logs and the like);
a security and secrecy manager submodule: the safety manager sub-module comprises functions of role authority management, role authorization, user security level setting and the like. Role authority management refers to authority control of the role on the distribution menu or button level; role authorization refers to assigning roles to system users; user authorization refers to assigning roles to users; the user security level setting means that the security level of a user is designated, and security level tamper resistance is set, the security level tamper resistance is obtained by splicing the security level levels through a user ID and performing hash calculation by using MD5, and the method specifically comprises the following characteristics:
1) Assigning a service authority (not including the authority owned by three members) to the role, and assigning a plurality of roles to the user and assigning a plurality of users to the role;
2) Changing the user state, resetting the password, prompting whether the user security level is modified, and if the modified line record is red, prompting;
3) Resetting passwords for the three-member account, and freezing and managing;
4) Checking operation logs of service users and safety auditors;
a safety audit manager submodule: and checking operation logs of a system administrator and a security secrecy operator.
In this embodiment, the user login module: the user login comprises system authentication of 4 types of user systems including a system administrator, a security administrator, an audit administrator and a service user. The system authentication authorization contains the following specific characteristics:
1. CA authentication: the ordinary service user logs in through the red key, inputs the login address, and the system identifies the red key to log in automatically;
2. and (3) authentication of a user name and a password: the three-member account logs in through a user name and a password, and the password can be submitted to a background after being encrypted at the front end;
3. authentication password setting: setting password complexity and periodic change function, setting password complexity: letters and capital letters plus numbers, the length of the password is more than or equal to 10 digits, the password is reminded of overdue, the password is forced to expire in 7 days, and the password can be modified after expiration to log in the system;
4. session timeout: the page is not operated for 30 minutes, the session is overdue, and the user logs in again;
5. locking an account number: the password is lost and mistaken for 5 times, the account number is frozen, and an audit log is formed after login fails;
6. and (3) permission setting: the function of access authorization mode based on user role, information category and system function category is provided;
7. and (3) access authorization: for an application system with a B/S architecture, all pages should be authenticated and access controlled to prevent illegal access to the system by faking URLs.
In this embodiment, the present invention provides an intelligent security information system for WEB work management and quality data analysis, which includes flowchart drawing, flowchart generation of flowchart from flow node data, automatic numbering of flow nodes, flowchart node status monitoring, flowchart export to PNG picture, flowchart export to VISIO, flowchart node data export WORD, flowchart node data difference analysis, file system data analysis, and three-person separation.
In this embodiment, the flowchart is drawn to maintain the flow task node information on the flowchart and to affect the node list data;
in this embodiment, the flow node automatic generation flow chart is used for automatically generating a flow chart according to the flow node arrangement algorithm;
in this embodiment, the automatic process node numbering is used to automatically generate a number for each process node according to the process node numbering rule algorithm;
in this embodiment, the process node state monitoring is used for the process node to drive the color change of the process graph node according to the task completion condition;
in this embodiment, the PNG picture derived by the flowchart is used for producing the PNG picture by drawing the picture in JAVA language according to the logical relationship of the nodes and the node coordinates of the flowchart;
in the embodiment, the flow chart is exported to a VISIO land, and a VISIO file is generated through a JS language and downloaded to a client through a browser according to the logical relationship and the node coordinates of the nodes of the flow chart;
in the embodiment, the process node data is exported to the WORD, and the process node data is exported to the WORD file according to the process sequence and the node detailed information in a table mode and is downloaded to the client through the browser;
in the embodiment, the flow node data difference analysis is used for carrying out difference comparison analysis through the model development flow node and the standard development flow node, finding out the defects of the current model development flow and solving the existing problems in time;
in the embodiment, the file system data analysis is used for carrying out comparative analysis on the model file system and the standard file system in the three fields of deep space, remote sensing and navigation, finding out the technical scheme file with the model missing in the development process in time, and playing a vital role in controlling the development quality of the spacecraft;
in this embodiment, three members are separated: the system is internally provided with three roles of a system administrator, a security and privacy administrator and a security auditor, each role is provided with two account numbers, the system cannot have the function of creating the three roles, a super administrator with the highest authority is strictly forbidden to exist, the system administrator, the security and privacy administrator and the security auditor divide the authority according to the minimum authorization principle, and the authorities among the administrators can be independent, supervised and restricted.
The specific implementation mode is as follows:
1. the environmental requirements are shown in table 1:
TABLE 1
2. The implementation steps are as follows:
installing JDKs and setting environment variables;
installing the REDIS and modifying a server access password of the REDIS;
TOMCAT is installed and 80 port numbers are confirmed as unoccupied;
modifying a configuration file of a WEB project, changing a corresponding database address, a user name and a password for database access and a REDIS service access password, then packaging into a war packet, placing the war packet into a TOMCAT/webtops directory, deploying a static page into the TOMCAT/webtops directory, and starting a WEB service by double start under the TOMCAT/bin directory;
and (5) the user can access the system by accessing http:// ip: port/index. Html through a Web browser.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (5)
1. A spacecraft development process management system is characterized by comprising a standard library module, a development process module, a file system module, a development team module, a user login module and a system management module, wherein the development process module, the file system module, the development team module, the user login module and the system management module are respectively connected with the standard library module;
the standard library module is used for providing standard basic data support for the development flow module, the file system module, the development team module and the third-party system;
the development flow module is used for analyzing the difference between the model flow and the standard flow and providing administrator setting operation for the development team module;
the file system module is used for analyzing the difference between the files in the standard library module and the spacecraft model number files;
the development team module is used for inquiring a development team personnel list according to the specific spacecraft model;
the user login module is used for controlling the access authority of the system;
the system management module is used for controlling data management and authority operation of the system;
the standard library module comprises a standard file system sub-module, a development team sub-module and a general flow sub-module;
the standard file system submodule is used for taking a scheme submitted in the process of developing the spacecraft and related files as a standard file system to provide a reference standard for model development, the standard file system submodule is divided into different versions according to the year, and each standard file system version comprises a file name list and files corresponding to the names of all stages in the process of developing the spacecraft;
the development team submodule is used for taking a role participated in the development process of the spacecraft model as a standard role of each spacecraft model development team;
the general flow sub-module is used for displaying standard task nodes and node sequences in the development process of the spacecraft on a WEB page in a flow chart mode;
the standard file system sub-module comprises a first list query unit, a version increasing unit, a version modifying unit and a version deleting unit;
the development team submodule comprises a role list query unit, a role adding unit, a role modifying unit and a role deleting unit;
the general flow sub-module comprises a flow version management unit, a flow chart management unit and a flow node management unit;
the flow version management unit comprises a list query subunit, a version increasing subunit, a version modifying subunit, a version deleting subunit, a flow chart management subunit, a flow chart releasing subunit and a flow node management subunit;
the flow chart management unit comprises a flow chart drawing subunit, a flow chart inquiring subunit, a flow chart deriving subunit, a flow node deriving subunit and a flow chart layout adjusting subunit;
the flow node management unit comprises a node list inquiry subunit, a node adding subunit, a node modifying subunit, a node deleting subunit, a node sorting subunit, a node leading-in subunit, a node leading-out subunit, a node type setting subunit, an automatic numbering subunit, a node logical relationship subunit and a node list automatic generation flow chart subunit;
the development flow module comprises a model flow submodule, a difference analysis submodule and a model management submodule;
the model flow submodule is used for maintaining specific model flow information and providing model flow data for the difference analysis submodule as a data source for difference analysis;
the difference analysis submodule is used for comparing and analyzing the model process node and the standard process node, and searching out potential quality problems in the model development process;
the model management submodule is used for carrying out data maintenance on the spacecraft model according to the spacecraft model management and setting a model manager;
the model flow sub-module comprises a model annual flow chart management unit, a model flow node list unit, a model flow task tracking and monitoring unit and a model flow chart drawing unit;
the model management submodule comprises a second list query unit, a list adding unit, a list modifying unit and a list deleting unit;
the file system module comprises a model file system submodule and a statistical analysis submodule;
the file system submodule is used for maintaining model file system data and file attachments and providing basic data for the statistical analysis submodule;
the statistical analysis submodule is used for analyzing the difference between the standard file system and the model file system and counting and prejudging the influence result of the lack or increase of the development process design files and scheme files in the model file system on the model quality.
2. The spacecraft development process management system of claim 1, wherein the development team module comprises a model development team sub-module and a flow chart editing permission sub-module;
the model development team submodule is used for providing authority for managing model checking and analyzing the influence of the integrity of model development team personnel on model quality;
the flow chart editing permission submodule is used for providing development flow chart editing permission for members of a development team.
3. The spacecraft development process management system of claim 1, wherein the system management module comprises a system administrator submodule, a security and privacy administrator submodule and a security audit administrator submodule;
the system administrator submodule is used for protecting the data security of the system; the system comprises a menu management unit, an organization management unit, a role management unit, a user management unit, a dictionary management unit and a system operation log unit;
the security and secrecy manager submodule is used for providing access permission of each service module of the system for a user and providing user security setting, and the user security setting comprises account number unfreezing and security level setting;
the security and confidentiality manager submodule comprises a role authority management unit, a role authorization unit, a user authorization unit and a user confidentiality level setting unit;
the safety audit manager submodule is used for viewing operation logs of a system manager and a safety secrecy manager; it includes an administrator operation log unit and a security officer operation log unit.
4. The spacecraft development flow management system of claim 1, wherein the user login module comprises a user system authentication submodule, and the user system authentication submodule is used for authenticating access and login authority of a user.
5. A spacecraft development process management method of a spacecraft development process management system according to any one of claims 1 to 4, comprising the steps of:
s1, generating general process node data, standard file system data and standard development team role data according to spacecraft development, and maintaining the data of a standard library module by utilizing the data;
s2, maintaining data of the model number management submodule, setting the authority of a model number manager and the login authority of the model number manager to the system, maintaining data of a model number development team, and setting the editing and checking authority of personnel of the development team on a model number flow chart;
s3, logging in the system by using model development personnel set by the model development team module, and maintaining the data of the model flow submodule and the data of the file system submodule;
s4, data of the universal process sub-module is quoted according to the data of the model process sub-module to serve as basic data of a model development process, node data of the development process is modified according to the characteristics of the model development process, and the modified process data serve as model development process data;
s5, according to the model development flow data, utilizing difference analysis of development flow data in the general flow sub-module and the model flow sub-module to identify a vulnerability in the model development process;
s5, basic data of a standard file system sub-module is quoted as basic data of a model file system, the file system data is modified according to the vulnerability development process node data, and the modified data is used as the model file system;
and S6, respectively utilizing the data of the standard file system submodule and the model file system submodule to perform difference analysis according to the data of the model file system, identifying scheme design documents and development reports which are lacked in the model development process, finding out the problem of model development, and finishing the management of spacecraft development.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911343492.3A CN111047301B (en) | 2019-12-24 | 2019-12-24 | Spacecraft development process management system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911343492.3A CN111047301B (en) | 2019-12-24 | 2019-12-24 | Spacecraft development process management system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111047301A CN111047301A (en) | 2020-04-21 |
| CN111047301B true CN111047301B (en) | 2023-04-18 |
Family
ID=70238710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911343492.3A Active CN111047301B (en) | 2019-12-24 | 2019-12-24 | Spacecraft development process management system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111047301B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112507168A (en) * | 2020-12-17 | 2021-03-16 | 武汉卓尔信息科技有限公司 | Application workflow processing method and framework |
| CN116187625B (en) * | 2023-04-24 | 2023-07-14 | 中国西安卫星测控中心 | Space survey operation control resource scheduling plan comparison method and device based on bit operation |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016022204A1 (en) * | 2014-08-02 | 2016-02-11 | Apple Inc. | Context-specific user interfaces |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100514121C (en) * | 2001-10-01 | 2009-07-15 | 松下电器产业株式会社 | Projection type display apparatus |
| CN1294510C (en) * | 2003-01-28 | 2007-01-10 | 中国南方航空股份有限公司 | Computer-aided teaching system and method for stimulated aviation training |
| US20080077417A1 (en) * | 2006-09-21 | 2008-03-27 | Lazzarino William A | Systems and Methods for Citation Management |
| CN103441986B (en) * | 2013-07-29 | 2017-05-17 | 中国航天科工集团第二研究院七〇六所 | Data resource security control method in thin client mode |
| US9846849B2 (en) * | 2013-09-19 | 2017-12-19 | Oracle International Corporation | System and method for providing an editor for use with a business process design environment |
| US20160335598A1 (en) * | 2015-02-12 | 2016-11-17 | John Aylmer | Multi-Destination Instrumentation Delivery System for Solar System Exploration to create and sustain commercial, heavy industrial and research opportunities |
| CN107194550A (en) * | 2017-05-08 | 2017-09-22 | 天津市科学学研究所 | Local chronicle mirror compiles cloud platform |
| CN108305011A (en) * | 2018-02-11 | 2018-07-20 | 中国航天标准化研究所 | A kind of space flight quality management system efficiency evaluation method that forward and reverse combines |
| CN108964996B (en) * | 2018-07-04 | 2021-08-27 | 航天神舟智慧系统技术有限公司 | Urban and rural integrated information grid system and information sharing method based on same |
| CN109814840A (en) * | 2018-12-17 | 2019-05-28 | 北京机电工程研究所 | A kind of customizable collaborative design and development platform for supporting resource quickly to apply and method |
| CN109670728B (en) * | 2018-12-29 | 2021-03-16 | 武昌船舶重工集团有限公司 | Ship design quality information management system based on database |
-
2019
- 2019-12-24 CN CN201911343492.3A patent/CN111047301B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016022204A1 (en) * | 2014-08-02 | 2016-02-11 | Apple Inc. | Context-specific user interfaces |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111047301A (en) | 2020-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11574234B2 (en) | Blockchain for data and model governance | |
| CN109086627B (en) | Form data operation auditing method | |
| US8028269B2 (en) | Compliance management method and system | |
| US6005571A (en) | Graphical user interface for managing security in a database system | |
| CN104376237B (en) | A kind of method of controlling security and system for being directed to information in production process | |
| US20050138420A1 (en) | Automatic role hierarchy generation and inheritance discovery | |
| US20040267593A1 (en) | Systems and methods for managing litigation and other matters | |
| US20040181378A1 (en) | Financial modeling and forecasting system | |
| US20120215749A1 (en) | System And Method For Managing Records Using Information Governance Policies | |
| CN108898317B (en) | Method for respectively authorizing form operation authority according to form field values | |
| CN111680310B (en) | Authority control method and device, electronic equipment and storage medium | |
| CN111047301B (en) | Spacecraft development process management system and method | |
| CN109961264A (en) | A kind of enterprise information management system and management method | |
| CN111897866A (en) | Remote sensing monitoring pattern spot docking system and using method thereof | |
| CN108875391B (en) | Authority display method for system after employee logs in account | |
| CN108985659B (en) | Method for carrying out approval process and approval node authorization on user | |
| CN111815290B (en) | Territorial space planning system based on GIS | |
| CN109033861B (en) | Method for authorizing authorized operator in system | |
| US11914741B2 (en) | Data security | |
| CN116415203A (en) | Government information intelligent fusion system and method based on big data | |
| CN116738449A (en) | DSMM-based data security management and control and operation system | |
| Kumar | An attack tree template based on feature diagram hierarchy | |
| CN110995747A (en) | Distributed storage security analysis method | |
| Kouns | Open source vulnerability database | |
| US20220327534A1 (en) | Security system and method that allows users to securely setup and maintain system security for all business systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |