CN114037316A - Information system engineering supervision project risk situation query method - Google Patents
Information system engineering supervision project risk situation query method Download PDFInfo
- Publication number
- CN114037316A CN114037316A CN202111364738.2A CN202111364738A CN114037316A CN 114037316 A CN114037316 A CN 114037316A CN 202111364738 A CN202111364738 A CN 202111364738A CN 114037316 A CN114037316 A CN 114037316A
- Authority
- CN
- China
- Prior art keywords
- module
- project
- risk
- view
- information system
- 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.)
- Granted
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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a risk situation query method for an information system engineering supervision project, which comprises the steps of sending a user risk query request to a query front-end module for evaluation implementation, calling all rule mapping examples from a container to be matched and traversed with the request, and returning a program object to a front end; the front-end module distributes program objects to the project progress control module, the example implementation module, the standing book monitoring module and the technical index evaluation module for adaptation, and an adapted attribute class is generated; the attribute classes are adapted to generate view objects; returning the adapted logical view name to the front-end module; the front-end module distributes the adapted view, calls an analyzer to analyze the logical view name, and returns a specific view object after analysis; and the front-end module calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and the query result is output to a user through the risk situation map module. The problem that the risk query result of the information system engineering project is difficult to show the dynamic risk trend is solved.
Description
Technical Field
The invention relates to the technical field of project risk query, in particular to a method for querying the risk situation of an information system engineering supervision project.
Background
Successful information system engineering, in addition to the widespread use of information technology products and equipment, also relies heavily on the ability and level of the personnel using the information technology products and equipment to perform in the engineering process. Therefore, the information system engineering management needs to monitor technical activities and increase management of selecting project team personnel for project participating parties, including preventive management and control measures for risks caused by blind spots generated by various human recognitions, also including human factor analysis of human behaviors when problems or accidents occur, and further including daily supervision and management when no accidents occur in daily life.
The construction content of the information system engineering project is increasingly complex, the general engineering plan made in the engineering planning and feasibility research stage is often in a rough scale, the future cannot be predicted, and the method is generally used for estimating the engineering investment scale rather than guiding the construction implementation. In addition, information system engineering has the characteristics of strong technological and knowledge intensive property, and the visibility of the engineering construction process is not strong. The participating units participate in the project at different stages or periods, and the plan formulated by the participating units is usually started from project tasks of the participating units, so that the project global planning is lacked. When multiple projects are developed simultaneously and in parallel, project managers of participating organizations are respectively responsible for providing a progress view based on the whole situation. With the deep development of the construction task, the participating parties are difficult to control the global progress due to the lack of reference objects, so that the difference between the planned target and the actual effect of each sub-item cannot be known.
Disclosure of Invention
Therefore, the invention provides an information system engineering supervision project risk situation query method to solve the problem that the risk dynamic trend of the information system engineering project is difficult to display in the risk query result.
In order to achieve the above purpose, the invention provides the following technical scheme:
the invention discloses a risk situation query method for an information system engineering supervision project, which comprises the following steps:
s1, sending the user risk query request to a query front-end module for evaluation and implementation, calling all rule mapping instances from a container to perform matching traversal with the request, and returning a program object to the front end;
s2, the front end module distributes program objects to the project progress control module, the example implementation module, the standing book monitoring module and the technical index evaluation module for adaptation, and an adapted attribute class is generated;
s3, adapting the attribute classes to generate view objects;
s4, returning the adapted logic view name to the front-end module;
s5, the front-end module distributes the adapted view to a project progress control module, a case implementation module, a ledger monitoring module and a technical index evaluation module, and calls an analyzer to analyze the logical view name into a physical view and return to a specific view object after analysis;
and S6, the front-end module calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and the query result is output to the user through the risk situation map module.
Further, in the step S1, the front end receives the query request, calls all rule mapping instances from the container to perform matching traversal with the request, generates a specific program instruction for the matching rule, encapsulates the instruction as an execution program object, and returns the execution program object to the front end.
Further, in the step S2, the front-end module distributes the program object to the project schedule control module, the example implementation module, the ledger monitoring module, and the technical index evaluation module for adaptation, and generates an adapted attribute class.
Further, in the steps S3 and S4, the inside performs adaptation on the attribute class to complete the creation of the requested data model and the processing of the business logic, generates a view object, and returns the adapted logical view name to the front-end module.
Further, the project progress control comprises the planning time, the application time, the period deviation and the planning change condition of each sub-project, reflects project management state data, controls key nodes and key plans of each project task, fills in the actual execution condition of each project task, performs statistical analysis on the residual workload of the sub-tasks, calculates the deviation result, and performs highlight display on high-risk events.
Further, the example can implement the example key index: whether the routine is called, whether key affiliates participate in the routine, whether the routine passes the rectification measure or not are statistically analyzed, and after a resolution is formed on each routine in a project period, the tracking conditions of the management and control measures and effects taken by a user reflect the dynamic management state of the project.
Furthermore, the standing book monitoring reflects whether the project milestone node works normally, the standing book monitoring module collects and arranges standing book information according to the number of days to become a clue for the supervisor to continuously track and monitor, and data collected aiming at problems are recorded in a pareto analysis table or a sequence diagram according to the order of importance.
Furthermore, a technical index framework is developed for the high technical characteristics of the information system engineering project by the technical index evaluation, and the technical index framework is integrated into a technical index management module to reflect dynamic data of whether the engineering project technology works effectively.
Further, in the step S5, the front-end module distributes the adapted view to the project progress control module, the example implementation module, the ledger monitoring module, and the technical index evaluation module, calls the parser to parse the logical view name into a physical view, and returns a specific view object after parsing.
Further, in the step S6, the front-end module calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and the query result is output to the user through the risk situation map module.
The invention has the following advantages:
the invention discloses a risk situation query method for an information system project supervision project, which can carry out statistical management operation on risk management related data among different periods of each sub-project/task of an information system project through a standardized data entry and management process. Meanwhile, the program can automatically calculate and summarize the input data and display the data of each module in a chart form, so that the time for manually carrying out the step is saved, and the use cost is saved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so as to be understood and read by those skilled in the art, and are not used to limit the conditions that the present invention can be implemented, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the effects and the achievable by the present invention, should still fall within the range that the technical contents disclosed in the present invention can cover.
Fig. 1 is a flowchart of a risk situation query method for an information system engineering supervision project according to an embodiment of the present invention;
fig. 2 is an architecture diagram of a risk situation query method for an information system engineering supervision project according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a project schedule control architecture according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of example implementation statistics provided by the present invention;
fig. 5 is a standing book monitoring statistical chart according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of index evaluation statistics provided by an embodiment of the present invention;
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Examples
Referring to fig. 1, the present embodiment discloses a method for querying risk situations of an information system engineering supervision project, where the method includes:
s1, sending the user risk query request to a query front-end module for evaluation and implementation, calling all rule mapping instances from a container to perform matching traversal with the request, and returning a program object to the front end;
s2, the front end module distributes program objects to the project progress control module, the example implementation module, the standing book monitoring module and the technical index evaluation module for adaptation, and an adapted attribute class is generated;
s3, adapting the attribute classes to generate view objects;
s4, returning the adapted logic view name to the front-end module;
s5, the front-end module distributes the adapted view to a project progress control module, a case implementation module, a ledger monitoring module and a technical index evaluation module, and calls an analyzer to analyze the logical view name into a physical view and return to a specific view object after analysis;
and S6, the front-end module calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and the query result is output to the user through the risk situation map module.
In step S1, the front end receives the query request, calls all rule mapping instances from the container to match the request, generates specific program instructions for the matching rules, encapsulates the instructions into executable program objects, and returns the executable program objects to the front end.
And the front-end module distributes program objects to the project progress control module, the example implementation module, the standing book monitoring module and the technical index evaluation module for adaptation, and generates an adapted attribute class. And performing adaptation on the attribute classes inside to complete the creation of the requested data model and the processing of business logic, generating a view object, and returning the names of the adapted logic views to the front-end module.
The project progress control module, the example implementation module and the standing book monitoring module are all quantitative analysis, and each module samples according to the period number. For a single project with a small number of project periods, the program adopts random sampling or drawing; for complex information system integration projects, dividing levels of Wei integrators, suppliers and interface providers by a program according to an integration relation, and extracting representative samples in each level according to a random principle; for the total and subcontract processes, the program samples every K individuals from the total sample. The user fills in a sufficient amount of data of the result of the supervision measures, the program uses the mean value and the variance of the distribution condition of the tested sample data to represent the data fluctuation range, and outputs the result of the quantization analysis. The technical index evaluation module is used for qualitative analysis, and the program judges according to the risk threshold value. The program can analyze the four sub-modules and synthesize the data of the four sub-modules to analyze the overall state of the engineering risk
Referring to fig. 3, the project schedule control is a schedule time, an actual time, a period deviation, and a schedule change situation of each sub-project included in the project, which is data reflecting a project management state. And controlling key nodes and key plans of each project task, filling the actual execution condition of each project task, and performing statistical analysis on the remaining workload of the subtasks. And automatically calculating a deviation result by a program, and highlighting the high-risk event.
Referring to fig. 4, an example implementation is that, because the project period of the information system engineering is long, a manager regularly calls a holding routine meeting, which is an important means for tracking the daily activities of the project, finding and coordinating the problem solving in time, and ensuring the project implementation quality. The example implementation module can perform statistical analysis on example key indexes, such as whether to call an example, whether to participate in a key relationship person, whether to implement a corrective measure passed by the example, and the like. The module can track the tracking condition of the control measures and effects taken by the user after a resolution is formed for each instance in the project period, and the tracking condition is data reflecting the dynamic management state of the project.
Referring to fig. 5, the ledger monitoring is generally divided into stages for an information system engineering project plan, each stage is provided with a milestone node, and the ledger is a record table for reflecting whether the work of the milestone nodes of the project is normally carried out. The standing book monitoring module collects and arranges the standing book information according to the term to form a clue for continuous tracking and monitoring of a proctoring person, and data collected aiming at problems are recorded in a pareto analysis table or a sequence diagram according to the order of importance.
The standing book is divided into four states of a tracked knotted state, a tracked unknotted state, an untracked-time node and an untracked-time node, circular tracking monitoring and iterative updating are carried out until the problem returns to zero, the total quantity of the standing book items in a certain time period of each project and the quantity of each state item can be counted and compared, and the counting can be carried out according to the proportion of the quantity of each state standing book to the total quantity of the standing book, the proportion of the quantity of each source standing book to the total quantity of the standing book, or the counting can be carried out according to the time of the project. For the four states of the machine account, the program monitoring disposal schemes are respectively as follows:
the knot has been tracked: indicating that the event has been queried and that the event has ended. And marking by the user.
Unknotted has been tracked: indicating that the event has been polled and that the event has not completed by that time. When the situation occurs, the program automatically prompts that the event needs to be postponed, and the system records the operation process when the user operates the event. If the delay reaches three times or more, the program triggers a threshold alarm.
Untracked arrived time node: indicating that the event has not been queried by the time. This occurs and the program gives a red prompt message.
Untracked missed time node: indicating that the time node has not arrived, nor has it been queried. The program respectively reminds the day before and the day after the machine account plan is finished, and the two reminders are distinguished by different colors.
Referring to fig. 6, since visibility of the information system engineering project process is poor, each party must confirm and evaluate the work in time after the technology is implemented, and the result can determine whether the work is effective. A technical index framework is developed aiming at high technical characteristics of an information system engineering project and is integrated into a technical index management module. The module reflects dynamic data of whether the engineering project technical work is effective or not. Through quantitative analysis of technical indexes, a program carries out statistical analysis on conditions of 'completing proportion', 'whether the project is in a reasonable interval', 'whether a filling problem exists', 'progress difference of each project' and the like of the project, project situation analysis is given through a histogram, a user carries out risk judgment according to the normal distribution condition of the histogram, and reasons for project risk generation in the current period are deduced. The analysis result not only reflects the effective condition of the work result of the construction unit, but also provides reference data for the progress control of the supervision personnel.
In the step S5, the front-end module distributes the adapted view to the project progress control module, the example implementation module, the ledger monitoring module and the technical index evaluation module, calls the parser to parse the logical view name into a physical view, returns a specific view object after parsing, calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and outputs the query result to the user through the risk situation map module.
Referring to fig. 2, in this embodiment, the implementation process of the method is a DevOps lightweight development mode constructed based on a micro-service technology, and is deployed in a docker container for rapid construction, and an application design scheme with front and back ends separated is adopted. The front end is focused on the UI page presentation of the service, and the user experience degree is very important. The back end focuses on business logic processing, takes data as a center, focuses on data storage, high concurrency requests and the like. In order to better adapt to complex scenes of information system engineering, a simulation test container and a production verification container are arranged. The former is used for testing the matching degree of model indexes and risk scenes, and the test is deployed to a production verification container after passing. An information system engineering project risk control operation platform is deployed in the simulation test container, components comprise user management service, audit service, dictionary service and accessory service, emphasis is placed on identifying user requests, and program response processes are tracked. The information system engineering project risk supervision control service desk is deployed in the production verification container, few components of a user management service, a dictionary service and an attachment service are configured, and the visualization effect of providing rich response results for user requests is emphasized.
According to the information system project supervision project risk situation query method disclosed by the real-time example, the statistical management operation can be performed on the risk management related data among different periods of each sub-project/task of the information system project through the standardized data entry and management process, and compared with the traditional data management mode, the visualization and integration of the dynamic trend of the risk can be effectively improved. Meanwhile, the program can automatically calculate and summarize the input data and display the data of each module in a chart form, so that the time for manually carrying out the step is saved, and the use cost is saved.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. A risk situation query method for an information system project supervision project is characterized by comprising the following steps:
s1, sending the user risk query request to a query front-end module for evaluation and implementation, calling all rule mapping instances from a container to perform matching traversal with the request, and returning a program object to the front end;
s2, the front end module distributes program objects to the project progress control module, the example implementation module, the standing book monitoring module and the technical index evaluation module for adaptation, and an adapted attribute class is generated;
s3, adapting the attribute classes to generate view objects;
s4, returning the adapted logic view name to the front-end module;
s5, the front-end module distributes the adapted view to a project progress control module, a case implementation module, a ledger monitoring module and a technical index evaluation module, and calls an analyzer to analyze the logical view name into a physical view and return to a specific view object after analysis;
and S6, the front-end module calls the evaluation model to the risk analysis module to render the physical view to generate a query result, and the query result is output to the user through the risk situation map module.
2. The method as claimed in claim 1, wherein the step S1 is implemented by receiving a query request from the front end, calling all rule mapping instances from the container to match the request, generating specific program instructions for the matching rules, packaging the program instructions into executable program objects, and returning the executable program objects to the front end.
3. The method for inquiring the risk situation of the information system engineering supervision project of claim 1, wherein in the step S2, the front end module distributes the program object to the project progress control module, the example implementation module, the ledger monitoring module and the technical index evaluation module for adaptation, so as to generate the adapted attribute class.
4. The method as claimed in claim 1, wherein in steps S3 and S4, the internal adaptation of the attribute class completes creation of the requested data model and processing of business logic, generates a view object, and returns the adapted logical view name to the front-end module.
5. The method as claimed in claim 3, wherein the project schedule control includes planning time, application time, period deviation and planning change condition of each sub-project, reflects project management state data, controls key nodes and key plans of each project task, fills actual execution condition of each project task, performs statistical analysis on the remaining workload of the sub-tasks, calculates deviation result, and performs highlight display on high-risk event.
6. The information system engineering supervision project risk situation query method of claim 3, characterized in that the instantiations implement an instantiating key index: whether the routine is called, whether key affiliates participate in the routine, whether the routine passes the rectification measure or not are statistically analyzed, and after a resolution is formed on each routine in a project period, the tracking conditions of the management and control measures and effects taken by a user reflect the dynamic management state of the project.
7. The information system engineering supervision project risk situation query method of claim 3, characterized in that the ledger monitoring reflects whether project milestone node work is normally carried out, the ledger monitoring module collects and arranges ledger information according to the number of futures into clues for coherent tracking monitoring of supervisors, and data collected for problems are recorded in a pareto analysis table or a sequence chart according to the order of importance.
8. The method for inquiring risk situation of information system engineering supervision project as claimed in claim 3, wherein the technical index evaluation develops a technical index framework for the high technical features of the information system engineering project, and integrates the technical index framework into the technical index management module, reflecting the dynamic data of whether the engineering project technical work is valid or not.
9. The method for inquiring risk situation of information system engineering supervision project of claim 1, wherein in the step S5, the front end module distributes the adapted view to the project progress control module, the example implementation module, the ledger monitoring module and the technical index evaluation module, calls the parser to parse the logical view name into the physical view, and returns the concrete view object after parsing.
10. The method as claimed in claim 1, wherein in step S6, the front end module calls the risk analysis module to perform an evaluation model to render the physical view to generate a query result, and the query result is output to the user through the risk situation map module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111364738.2A CN114037316B (en) | 2021-11-17 | 2021-11-17 | Information system engineering supervision project risk situation query method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111364738.2A CN114037316B (en) | 2021-11-17 | 2021-11-17 | Information system engineering supervision project risk situation query method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114037316A true CN114037316A (en) | 2022-02-11 |
| CN114037316B CN114037316B (en) | 2023-04-07 |
Family
ID=80144673
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111364738.2A Active CN114037316B (en) | 2021-11-17 | 2021-11-17 | Information system engineering supervision project risk situation query method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114037316B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5761674A (en) * | 1991-05-17 | 1998-06-02 | Shimizu Construction Co., Ltd. | Integrated construction project information management system |
| US6122627A (en) * | 1997-05-09 | 2000-09-19 | International Business Machines Corporation | System, method, and program for object building in queries over object views |
| CN107169673A (en) * | 2017-06-09 | 2017-09-15 | 上海嘉实（集团）有限公司 | Management system/method, computer-readable recording medium and the terminal of construction project |
| CN108446895A (en) * | 2018-03-26 | 2018-08-24 | 郑州大学 | A kind of engineering construction project intelligent management system |
| CN109615324A (en) * | 2018-12-06 | 2019-04-12 | 江苏苏科建设项目管理有限公司 | One kind being based on the project management method of " wisdom management " system |
| CN110851465A (en) * | 2019-11-15 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Data query method and system |
| CN112950164A (en) * | 2020-07-09 | 2021-06-11 | 北京中百信信息技术股份有限公司 | Information system engineering supervision working hour recording information system based on standardized rules |
| CN113657804A (en) * | 2021-08-30 | 2021-11-16 | 江盛权 | Building engineering EPC cost and progress management system based on BIM technology |
-
2021
- 2021-11-17 CN CN202111364738.2A patent/CN114037316B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5761674A (en) * | 1991-05-17 | 1998-06-02 | Shimizu Construction Co., Ltd. | Integrated construction project information management system |
| US6122627A (en) * | 1997-05-09 | 2000-09-19 | International Business Machines Corporation | System, method, and program for object building in queries over object views |
| CN107169673A (en) * | 2017-06-09 | 2017-09-15 | 上海嘉实（集团）有限公司 | Management system/method, computer-readable recording medium and the terminal of construction project |
| CN108446895A (en) * | 2018-03-26 | 2018-08-24 | 郑州大学 | A kind of engineering construction project intelligent management system |
| CN109615324A (en) * | 2018-12-06 | 2019-04-12 | 江苏苏科建设项目管理有限公司 | One kind being based on the project management method of " wisdom management " system |
| CN110851465A (en) * | 2019-11-15 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Data query method and system |
| CN112950164A (en) * | 2020-07-09 | 2021-06-11 | 北京中百信信息技术股份有限公司 | Information system engineering supervision working hour recording information system based on standardized rules |
| CN113657804A (en) * | 2021-08-30 | 2021-11-16 | 江盛权 | Building engineering EPC cost and progress management system based on BIM technology |
Non-Patent Citations (2)
| Title |
|---|
| 任东星: "基于SSH框架的监理项目管理系统的设计与实现", 《福建电脑》 * |
| 创求进: ""SpringMVC从前端接收请求后的执行过程"", 《CSDN》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114037316B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114037311B (en) | Information system engineering supervision project risk assessment method | |
| Li et al. | Architectural technical debt identification based on architecture decisions and change scenarios | |
| Kurapati et al. | Agile software development practice adoption survey | |
| US8375364B2 (en) | Size and effort estimation in testing applications | |
| KR101066949B1 (en) | Computer readable recording medium having task analysis program and task analyzer | |
| Gehlot et al. | An introduction to systems modeling and simulation with colored petri nets | |
| US7877284B2 (en) | Method and system for developing an accurate skills inventory using data from delivery operations | |
| US8799210B2 (en) | Framework for supporting transition of one or more applications of an organization | |
| US8705723B2 (en) | Systems and methods for scheduling contact center agents | |
| de Souza Carvalho et al. | A comparative analysis of the agile and traditional software development processes productivity | |
| CA2804441C (en) | Database performance analysis | |
| US7865382B2 (en) | Compliance control framework | |
| CN103226743A (en) | TRL-based technical maturity assessment information processing method for aeronautic equipment | |
| US20060129879A1 (en) | System and method for monitoring the status and progress of a technical process or of a technical project | |
| CN114462969A (en) | Project progress real-time monitoring method and device, electronic equipment and storage medium | |
| CN110070307A (en) | A kind of Information Visualization Management System based on WBS | |
| Ordonez et al. | The state of metrics in software industry | |
| US7822587B1 (en) | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior | |
| CN111723004B (en) | Measurement method for agile software development, measurement data output method and device | |
| CN114037316B (en) | Information system engineering supervision project risk situation query method | |
| CN112465457A (en) | Supervision project management method, system, device and computer storage medium | |
| CN114037314A (en) | Information system engineering supervision project risk dynamic analysis method | |
| Roubtsova et al. | KPIs and their properties defined with the EXTREME method | |
| CN113962664A (en) | Method, device, equipment and medium for human resource evaluation | |
| Greasley | A simulation of a workflow management system |
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 | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Liu Qingbo Inventor after: Zhou Wei Inventor after: Ma Da Inventor after: Lu Xuezhe Inventor before: Liu Qingbo Inventor before: Zhou Wei Inventor before: Li Rui Inventor before: Ma Da Inventor before: Lu Xuezhe |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |