Railway engineering project management system and method

Abstract

The invention discloses a railway engineering project management system and method, and relates to the technical field of railway signal information.The system is characterized in that when general software is changed, a general software management module manages changed general software information and triggers a communication management module; the engineering software management module synchronously updates the engineering software information based on the updated general software information; when the engineering software is changed, the engineering software management module manages the changed engineering software information and triggers the communication management module; and the engineering software management module secondarily updates the engineering software information based on the general software information in the general software management module, or the general software management module synchronously updates the general software information based on the updated engineering software information. By adopting the system, a more efficient and reliable management means can be provided, and the problem that project progress is blocked due to the fact that information is not synchronized in time is solved.

Description

Technical Field

[0001] The present invention relates to the field of railway signal information technology, and in particular to a railway engineering project management system and method. Background Art

[0002] In the related art, a signal system configured by application data and / or application algorithms allows the approved general software to be customized according to the individual needs of the specific application of each engineering project to obtain the engineering software required by the engineering project.

[0003] Although general software has the characteristics of standardization, stability and universality to a certain extent, in fact, after the first approval for application, general software will change due to internal and external factors such as changes in technical standards and bug fixes, and several versions will be formed in chronological order. At the same time, the life cycle of an engineering project is as long as more than ten years. Not only are the start times different, but the project progress is also fast or slow. After delivery, the engineering design may change due to station reconstruction, which requires the re-compilation of application data / algorithms, resulting in changes in engineering software. In this case, changes in general software will affect the functionality and safety of engineering software, and will also affect the planning, implementation and cost of engineering projects. Summary of the invention

[0004] Based on this, it is necessary to provide a railway engineering project management system and method that can enhance the real-time performance of information transmission between general software and engineering software in response to the above technical problems.

[0005] A railway engineering project management system, comprising:

[0006] General software management module, used to manage general software information;

[0007] Engineering software management module, used to manage engineering software information;

[0008] A communication management module, used for executing information interaction between the general software management module and the engineering software management module;

[0009] Wherein, when the general software is changed, the general software management module manages the changed general software information and triggers the communication management module; the engineering software management module synchronously updates the engineering software information based on the updated general software information;

[0010] When the engineering software changes, the engineering software management module manages the changed engineering software information and triggers the communication management module; the engineering software management module updates the engineering software information for a second time based on the general software information in the general software management module, or the general software management module synchronously updates the general software information based on the updated engineering software information.

[0011] In the above scheme, the general software information includes general software basic information and general software defect information; the general software management module stores the general software basic information with the general software version as the identification unit, and stores the general software defect information with the defect as the identification unit;

[0012] The engineering software information includes engineering software project information and engineering software development information; the engineering software management module uses engineering projects as identification units to store the engineering software project information, and uses engineering software versions as identification units to store the engineering software development information.

[0013] In the above scheme, when the version of the general software changes, the general software management module collects the general software basic information of the new version of the general software, determines the target software version that matches the software identifier of the new version of the general software, and adds a historical version mark to the target software version;

[0014] The engineering software management module filters out a target project that matches the applicable system and application scope corresponding to the software identifier, and updates the general software version used by the target project; wherein, if the target project does not specify general software, or, if the target project specifies general software and the target project has no software production progress, the new version of general software is designated as the general software of the target project; if the target project specifies general software and the target project has a software production progress, the software production progress of the target project is set to a general software version exception.

[0015] In the above scheme, when the application scope of the general software changes, the engineering software management module screens out the target project that matches the application scope of the general software before the application scope changes, updates the software production schedule of the target project, and updates the general software version used by the target project according to the general software basic information in the general software management module; wherein,

[0016] If the target project has no software production progress, the general software version used by the target project is cleared; if the target project has software production progress, the software production progress of the target project is set to be a general software version exception.

[0017] In the above scheme, when a new defect occurs in the general software, the general software management module collects general software defect information of the new defect, and screens to obtain a target general software version that matches the general software version of the new defect, and adds the new defect to the target general software version;

[0018] The engineering software management module selects target projects that match the application scope of the target general software version according to the target general software version, and updates the current requirements of the target project according to the software production progress of the target project; wherein,

[0019] If the target project does not have the software production progress, the newly added defects are added as the current requirements of the target project; if the target project has a software production progress field, a new requirement prompt for the target project is issued.

[0020] In the above scheme, when adding a new engineering project, the engineering software management module collects the engineering software project information of the newly added engineering project, and screens and obtains the target general software version according to the system model of the newly added engineering project; the target general software version is determined as the general software version used by the newly added engineering project, and the associated defects of the target general software version are determined as the current requirements of the newly added engineering project.

[0021] In the above scheme, when the version of the engineering software changes, the engineering software management module collects the engineering software development information of the new version of the engineering software, verifies the common software version used by the engineering project to which the new version of the engineering software belongs and the common software version used by the new version of the engineering software, and updates the engineering software development information of the new version of the engineering software and the engineering software project information of the engineering project to which the new version of the engineering software belongs based on the verification results.

[0022] In the above scheme, the engineering software management module updates the software production progress of the engineering project to which the engineering software belongs when the management status of the engineering software changes;

[0023] When there is a general software defect repaired in the engineering software development information of the engineering software, the general software management module updates the repair progress of the corresponding general software in the general software management module regarding the repaired general software defect.

[0024] In the above scheme, the railway engineering project management system also includes a user management module for performing authority management on system users; the system user is used to issue administrator authority to the system user to add new management objects in the general software management module or the engineering software management module when the general software or the engineering software changes.

[0025] A railway engineering project management method, characterized in that it is applied to a railway engineering project management system, and the method comprises:

[0026] When general software is changed, the changed general software information is managed based on the general software management module;

[0027] Execute information interaction between the general software management module and the engineering software management module based on the communication management module, and synchronously update the engineering software information according to the updated general software information based on the engineering software management module;

[0028] When the engineering software is changed, the changed engineering software information is managed based on the engineering software management module;

[0029] Based on the communication management module, information interaction is performed between the general software management module and the engineering software management module, and based on the engineering software management module, the engineering software information is updated for a second time according to the general software information in the general software management module, or based on the general software management module, the general software information is synchronously updated according to the updated engineering software information.

[0030] The above-mentioned railway engineering project management system includes a general software management module, an engineering software management module and a communication management module, wherein the general software management module and the engineering software management module can uniformly manage general software information and engineering software information, and the communication management module can realize information interaction between the general software management module and the engineering software management module, and can timely transmit the changed general software information or engineering software information to the general software management module and the engineering software management module, thereby assisting specific engineering projects to trigger corresponding changes in engineering software in time according to actual needs and schedule plans, avoiding rework of engineering software and affecting the progress of engineering projects, and is conducive to improving the implementation efficiency of engineering projects. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A schematic diagram of the structure of a railway project management system in one embodiment;

[0032] Figure 2 A schematic diagram of the system architecture of a railway engineering project management system in one embodiment;

[0033] Figure 3 is a functional schematic diagram of a general software management module in one embodiment;

[0034] Figure 4 is a functional schematic diagram of an engineering software management module in one embodiment;

[0035] Figure 5A schematic diagram of operation flow A of a railway project management system in one embodiment;

[0036] Figure 6 A schematic diagram of operation flow B of a railway project management system in one embodiment;

[0037] Figure 7 A schematic diagram of the C operation flow of a railway project management system in one embodiment;

[0038] Figure 8 A schematic diagram of the D operation flow of a railway project management system in one embodiment;

[0039] Fig. 9 It is a schematic diagram of the E operation process of a railway project management system in one embodiment;

[0040] Fig.10 The figure is a management flow diagram of a railway engineering project management system in one embodiment. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0042] The implementation details of the technical solution of the embodiment of the present application are described in detail below.

[0043] In one embodiment, Figure 1 As shown, a schematic diagram of the structure of a railway engineering project management system is provided. Based on the diversity and variability of management information of the railway engineering project management system and the flexibility of application requirements, and considering the future expansion of information and functions, the system adopts a three-tier architecture system of B / S (Browser / Server Architecture), and combines it with a network architecture style REST (Representational State Transfer) based on HTTP protocol for communication, so that the system can achieve the effect of front-end and back-end separation, so as to improve the availability, reliability and scalability of the system.

[0044] The B / S three-tier architecture system consists of the presentation layer, business layer and data layer. The system architecture is as follows Figure 2 The presentation layer is responsible for interacting with users and providing a user interface. Users can access system functions through a browser, including the display page for general software information, the display page for engineering software information, the user management page, and the personal homepage.

[0045] The business layer is responsible for processing core business logic, receiving requests from the presentation layer, and interacting with the data layer. The business processed includes permission authentication, log monitoring, information management, document management, and status updates.

[0046] The data layer is responsible for data storage, retrieval and management, and provides a data access interface. The data layer includes master nodes and different replica sets. The master node is the main node in the database, responsible for processing all write operations and most read requests. The replica set is a group of database nodes, including at least one master node and one or more replica nodes. The replica node maintains the same data copy as the master node. If the master node fails, a new master node can be quickly elected to ensure the continuous availability of the system. The replica set also provides redundant backup of data to protect data from single point failures.

[0047] Reference Figure 1 As shown in the figure, in the railway engineering project management system, according to the functional modules, it can be divided into general software management module, engineering software management module and communication management module. The following is a detailed description of each functional module.

[0048] The general software management module is used to manage general software information, including collecting, storing and displaying general software information. General software information refers to the relevant attribute information of general software, including the development, version management, maintenance and various related status information of general software.

[0049] The engineering software management module is used to manage engineering software information, including collecting, storing and displaying engineering software information. Engineering software information refers to the relevant attribute information of the engineering software used in each engineering project.

[0050] It should be noted that general software is basic software used in railway scenarios, with standardized functions and features, and can support a variety of tasks and user needs. Engineering software is software that is customized and expanded based on general software according to the needs of specific engineering projects.

[0051] Assume that the project is to establish the interlocking system engineering software for a certain station. It is necessary to compile and approve the general application software of the computer interlocking system in accordance with the corresponding technical standards. The general software is customized according to the needs of the project, that is, a set of application data / algorithms describing the number, type and topological relationship of signal equipment at a certain station is configured on the basis of the general software to obtain the engineering software of the project, and the signal control and turnout management of the station are realized through the engineering software.

[0052] It can be seen that changes in general software will affect the use of engineering software. If the changed information cannot be synchronized to the general software management module or the engineering software management module in a timely manner, information asymmetry or lag will cause related problems, such as:

[0053] (1) Failure to obtain change information of general software in a timely manner results in the project engineering software being delivered with defects, i.e., the engineering software has unresolved problems or defects at the time of delivery;

[0054] (2) Failure to obtain change information of general software in a timely manner affects the rework progress of engineering software and increases costs;

[0055] (3) When general software changes occur, it is impossible to timely and accurately determine the scope of impact and repair on all engineering projects, which further leads to the inability to timely repair the affected engineering projects;

[0056] (4) It is impossible to obtain the repair progress of general software in real time, resulting in a lack of dynamic management of engineering software changes and defect repairs, which affects the maintenance department's judgment and analysis of feedback issues.

[0057] The communication management module in the railway engineering project management module is responsible for the information interaction of each module, and executes the information interaction between the general software management module and the engineering software management module. It can realize efficient and real-time communication between the general software management module and the engineering software management module, thereby solving the above-mentioned related problems caused by information asymmetry or lag.

[0058] Among them, the communication management module can be triggered by the general software management module or the engineering software management module, that is, the trigger information of the communication management module can be divided into active triggering of the general software management module and active triggering of the engineering software management module according to its affiliation.

[0059] When the general software changes, the general software management module will manage the general software information after the change, including collecting, storing and displaying the changed general software information, thereby updating the general software information in the general software management module. It is understandable that for a general software, it may undergo changes such as iterations of different software versions, repairs of defects, changes in the scope of application, etc. The general software management module will sort out the general software information from the initial general software to the latest general software one by one, that is, the changed basic software information will not replace the basic software information stored in the general software management module, but the general software management module will manage the originally stored basic software information and the changed basic software information together.

[0060] In addition, the general software management module will trigger the communication management module, so that the communication management module executes information interaction between the general software management module and the engineering software management module, so that the changed general software information can be synchronized to the engineering software management module in time, so that the engineering software management module can synchronously update the engineering software information based on the updated general software information, and can synchronously adjust the engineering software of the engineering projects involved, thereby ensuring the functionality and safety of the engineering software.

[0061] When the engineering software changes, the engineering software management module manages the changed engineering software information, including collecting, storing and displaying the changed engineering software information, thereby updating the engineering software information in the engineering software management module. It is understandable that for engineering software, there may be new engineering software, iterations of different software versions, software management status and other changes. The engineering software management module will organize any changes in the engineering software of each engineering project, that is, the changed engineering software information will not replace the engineering software information stored in the engineering software management module, but the engineering software management module will manage the originally stored engineering software information and the changed engineering software information together.

[0062] And the engineering software management module actively triggers the communication management module, so that the communication management module, under the active triggering of the engineering software management module, executes information interaction between the general software management module and the engineering software management module, so that the general software information of the general software management module can be synchronized to the engineering software management module, so that the engineering management module can update the engineering software information for a second time based on the general software information, wherein here the changed engineering software information is mainly updated. For example, in an application scenario, there is a newly established engineering project, and the engineering software management module creates a new management object for managing the changed engineering software information, wherein at this time, the management object contains the project establishment information about the engineering software, and the engineering software is built on the general software, based on this, the engineering software management module synchronizes the general software information to the engineering software management module through the communication management module, and fills the general software used by the engineering software in the management object based on the general software information, thereby realizing the secondary update of the engineering software information.

[0063] In addition, after the communication management module is triggered, the engineering software information updated by the engineering software management module can be synchronized to the general software management module, so that the general software management module can synchronously update the general software information based on the updated engineering software information. For example, in an application scenario, the version of the engineering software is changed to repair the defects of the general software. The engineering software management module creates a new management object to manage the changed engineering software information and records the relevant information of the new version of the engineering software (including the defect information repaired by the new version of the engineering software). Then, the engineering software management module synchronizes the updated engineering software information to the general software management module through the communication management module, so that the general software management module can synchronously update the defect repair status of the general software based on the updated engineering software information, thereby realizing the synchronous update of the general software information.

[0064] In one embodiment, Figure 3 As shown, Figure 3 The functional diagram of the general software management module is shown. The general software information in the general software management module can be classified into general software basic information and general software defect information, wherein the general software basic information records all general software released to engineering applications and is used to describe the basic characteristics of the general software (such as the software name, etc.), and the general software defect information records all defects found in the general software and is used to describe the details of the general software defects.

[0065] The general software management module can classify and store general software information, wherein the general software management module uses the general software version as the identification unit, and one version of general software is a management object to store the general software basic information. As shown in Table 1, Table 1 shows a list of general software basic information stored in the general software management module, wherein one management object corresponds to one list.

[0066] Table 1

[0067] Information No. Information Name G-DS-SW-01 Software Title G-DS-SW-02 Software Identification G-DS-SW-03 Software version number G-DS-SW-04 Release time G-DS-SW-05 Applicable systems G-DS-SW-06 Scope of application / limitations G-DS-SW-07 Related defects

[0068] For general software defect information, the general software management module uses defects as identification units, and one defect is a management object to store the general software defect information. As shown in Table 2, Table 2 shows a list of general software defect information stored in the general software management module, wherein one management object corresponds to one list.

[0069] Table 2

[0070] Information No. Information Name G-DS-DEF-01 Defect Number G-DS-DEF-02 Defects G-DS-DEF-03 Scope (general software version list) G-DS-DEF-04 Severity level G-DS-DEF-05 Repair plan G-DS-DEF-06 Repair progress G-DS-DEF-07 Contingency Plan

[0071] In practical applications, refer to Figure 3As shown, the general software management module will display the stored general software information on the front page. For the display of general software information, the general software management module provides two types of first-level display interfaces according to the user type, namely the "general software-software information" interface and the "general software-defect information" interface.

[0072] The general software management module also provides a secondary display interface for the repair progress (i.e., G-DS-DEF-06 field) in the general software defect information. The secondary display interface is used to display the defect repair progress ledger, that is, to display the repair progress of the defect in all projects involved in the defect through a list. Among them, in the secondary display interface, the general software management module also provides the functions of sorting, filtering, and statistics based on the key items in the list.

[0073] Among them, the three display interfaces provided by the general software management module all support exporting ledger files according to the interface display, as well as (single / batch) downloading of documents associated with specified information.

[0074] like Figure 4 As shown, Figure 4 The functional diagram of the engineering software management module is shown. The engineering software information in the engineering software management module can be classified into engineering software project information and engineering software development information, wherein the engineering software project information records all engineering projects and is used to describe the basic information of the engineering projects; the engineering software development information records all engineering software in the engineering projects and is used to describe the development status of the engineering software.

[0075] The engineering software management module can classify and store engineering software information. The engineering software management module uses engineering projects as identification units. A delivery task of an engineering project is a management object, and the engineering software project information is stored. As shown in Table 3, Table 3 shows a list of engineering software project information stored in the engineering software management module, wherein one management object corresponds to one list.

[0076] Table 3

[0077]

[0078] Each engineering project includes multiple engineering software versions, so the engineering software management module uses the version of the engineering software as an identification unit, and one version of the engineering software is a management object to store the engineering software development information. As shown in Table 4, Table 4 shows a list of engineering software development information stored in the engineering software management module, where one management object corresponds to one list.

[0079] Table 4

[0080]

[0081]

[0082] It should be noted that the storage structure in the engineering software management module can be simply understood as a process record of engineering software development information providing engineering software project information. The engineering software project information should check the latest version information in the engineering software development information and keep it consistent. In addition, the current requirements in the engineering software project information and the associated requirements in the engineering software development information are numbers assigned by the engineering software management module after the engineering design data and general software update / repair requirements are combined and managed, and they are uniquely corresponding to each version of the engineering software.

[0083] In practical applications, refer to Figure 4 As shown, the engineering software management module will display the stored engineering software information on the front-end page. The engineering software management module provides a first-level display interface: "Engineering Software-Project Information" interface, which is used to display engineering software project information.

[0084] The engineering software management module provides a secondary display interface for each engineering project: the "Engineering Software-Development Information" interface, which can record and manage the engineering software change process in each engineering project.

[0085] The engineering software management module provides the functions of sorting, filtering and counting according to the key items displayed on the interface (such as S-DS-PRJ-03 field, S-DS-PRJ-04 field, S-DS-PRJ-06 field, S-DS-PRJ-07 field and S-DS-PRJ-10 field) in the first-level display interface ("Engineering Software-Project Information" interface).

[0086] Among them, all the above display interfaces support exporting ledger files according to the interface display, as well as (single / batch) downloading of documents associated with specified information.

[0087] In one embodiment, based on the management experience of general software, the general software management module can actively trigger information for general software version changes, including the existence of general software released for the first time, or general software released with changes. Figure 5 As shown, Figure 5 A schematic diagram of the A operation flow of the railway engineering project management system is shown, wherein the A operation refers to the management flow executed by the general software management module and the engineering software management module when the version of the general software changes.

[0088] Step AS1: When the general software version changes, the general software management module needs to create a new management object to manage the general software basic information of the new version of the general software.

[0089] Step AS2: The general software management module collects the general software basic information of the new version of the general software. The general software management module stores the collected general software basic information based on the newly created management object and with reference to the data structure shown in Table 1.

[0090] Step AS3: The general software management module filters the general software versions. From the general software basic information of different software versions that have been stored, the target software version that matches the software identifier of the new version of the general software is filtered out, that is, the G-DS-SW-02 field of the general software basic information is filtered out, thereby filtering out different versions belonging to the same general software.

[0091] Step AS4: The general software management module adds a historical version mark to the target software version obtained by screening. Since the general software has released the latest version, the latest software version of the general software is determined by adding the historical version mark. In actual application, the historical version mark can be added to the G-DS-SW-06 field in the list corresponding to the target software version.

[0092] Step AS5: The engineering software management module performs a system legality screening on the engineering software project. Among them, the general software management module actively triggers the communication management module. After the information interaction performed by the communication management module, the engineering software management module can obtain the latest general software information in the general software management module. According to the adaptation system (G-DS-SW-02 field and G-DS-SW-05 field) corresponding to the software identification of the new version of the general software, the engineering software project information is screened.

[0093] The engineering software management module determines whether the screening is passed. If not, the A operation flow is terminated. If yes, it means that the engineering software management module has screened all engineering projects that are consistent with the applicable system of the software to which the new version of the general software belongs.

[0094] Step AS6: The engineering software management module performs application restriction screening. Based on the screened engineering projects, the engineering software management module performs secondary screening according to the application scope corresponding to the software identification of the new version of the general software (field of G-DS-SW-06), eliminates items that do not meet the requirements, and thus obtains the target project.

[0095] The engineering software management module determines whether the screening is passed. If not, the A operation process ends. If yes, the next step is performed. Based on the above two rounds of screening, the engineering software management module can screen the engineering projects involved in the new version of the general software.

[0096] Step AS7: The engineering software management module checks the general software version used by the target project (S-DS-PRJ-07 field). It is understandable that when the software version of the general software changes, it will affect the engineering projects using the general software. Therefore, the engineering software management module needs to filter out the affected engineering projects and further update the versions of the general software used by these target projects.

[0097] Step AS8: If the engineering software management module detects that the target project does not specify the general software (i.e., the S-DS-PRJ-07 field is empty), the new version of the general software is specified as the general software of the target project, and the S-DS-PRJ-07 field of the target project is updated according to the G-DS-SW-03 field of the new version of the general software. At this point, the process of job A is completed.

[0098] Step AS9: If the target project has specified general software (ie, the S-DS-PRJ-07 field is not empty), further check the software production progress of the target project (S-DS-PRJ-10 field).

[0099] Among them, if the target project has no software production progress (that is, the S-DS-PRJ-10 field is empty), it means that the target project has not started to develop engineering software. Based on this, the engineering software management module executes step AS8, determines the general software used by the target project as the latest version, and updates the S-DS-PRJ-07 field of the target project according to the G-DS-SW-03 field of the new version of the general software.

[0100] Step AS10: If the target project has a software production schedule (i.e., the S-DS-PRJ-10 field is not empty), it means that the target project has used the historical version of the general software to develop the engineering software. Based on this, it is necessary to set the software production schedule of the target project (i.e., the S-DS-PRJ-10 field) to the general software version exception, so as to remind the engineering personnel to adjust the engineering project plan in time to avoid the delivery of engineering software with defects or the need to redevelop the engineering software.

[0101] In one embodiment, based on the management experience of general software, the general software management module can actively trigger information when the application scope of the general software changes, where the application scope of the general software is affected by the functional changes of the general software. When the application scope of the general software changes (that is, the G-DS-SW-06 field of the general software changes), the general software management module updates the basic information of the general software according to the changed application scope. And the general software management module triggers the communication management module to execute information exchange between the general software management module and the engineering software management module. Figure 6 As shown, Figure 6The diagram shows a B operation flow diagram of the railway engineering project management system, wherein the B operation refers to the management process executed by the engineering software management module when the application scope of the general software changes.

[0102] Step BS1: The engineering software management module screens historical related projects. Specifically, the engineering software management module can obtain the general software information in the general software management module through the communication management module. The engineering software management module selects the target projects that are consistent with the application scope of the general software before the change in the engineering software project information according to the application scope of the general software before the change, and determines the engineering projects affected by the change in the application scope of the general software. In this way, the engineering software management module can further update the software production progress of the target project (S-DS-PRJ-10 field) and the version of the general software used (S-DS-PRJ-07 field).

[0103] Step BS2: The engineering software management module checks the software production progress of the target project (S-DS-PRJ-10 field).

[0104] Step BS3: If there is no software production progress (i.e., the S-DS-PRJ-10 field is empty), the engineering software management module clears the relevant data of the general software version used by the target project (i.e., clears the S-DS-PRJ-07 field), thereby preventing expired information from affecting the development of subsequent engineering software.

[0105] Step BS4: If the target project has a software production schedule (i.e., the S-DS-PRJ-10 field is not empty), the engineering software management module sets the software production schedule of the target project to a general software version exception, and changes the S-DS-PRJ-10 field to a general software version exception, thereby reminding the engineering personnel of the target project to adjust the engineering project plan in time to avoid the delivery of engineering software with problems or the need for re-development.

[0106] Step BS5: For the common software version used by the target project, the engineering software management module refers to Figure 5 Steps AS5 to AS10 in the above are updated.

[0107] Based on this, the engineering software management module can respond and adjust related engineering projects in a timely manner after the application scope of general software changes, thereby ensuring the smooth progress of engineering projects and reducing unnecessary risks and costs.

[0108] In one embodiment, based on the management experience of general software, the general software management module can also actively trigger information when the defects of the general software change, that is, when new general software defects are found. Figure 7 As shown, Figure 7The diagram shows a C operation flow diagram of the railway engineering project management system, wherein the C operation refers to the management flow executed by the general software management module and the engineering software management module when the defects of the general software change.

[0109] Step CS1: When the defects of the general software are changed, the general software management module needs to create a new management object to manage the general software defect information of the newly added defects.

[0110] Step CS2: The general software management module collects relevant information of the newly added defects, and based on the newly created management object, stores the general software defect information of the newly added defects with reference to the data format shown in Table 2.

[0111] Step CS3: The general software management module filters the general software version. Specifically, the general software management module filters the general software basic information according to the general software version of the newly added defect (i.e., the G-DS-DEF-03 field) to obtain the target general software version, thereby filtering out the software version affected by the newly added defect.

[0112] Step CS4: The general software management module adds a new defect to the target general software version, that is, the G-DS-DEF-01 field in the general software defect information corresponding to the new defect is added to the G-DS-SW-07 field in the general software basic information corresponding to the target general software version, thereby establishing an association between the target general software version and the new defect. In actual applications, the G-DS-DEF-01 field corresponds to the defect number of the new defect, and each defect number corresponds to a defect, so that a defect can be indicated by the defect number.

[0113] Step CS5: The engineering software management module selects engineering projects. Specifically, the general software management module triggers the communication management module to perform information exchange between the general software management module and the engineering software management module. The engineering software management module uses the synchronized general software information and the application scope of the target general software to select target projects that are consistent with the application scope of the target general software in the engineering software project information, thereby confirming the engineering projects affected by the newly added defects.

[0114] Among them, if the engineering software management module screening fails, that is, the target project does not exist, then the C operation process is terminated.

[0115] Step CS6: The engineering software management module checks the software production progress of the target project (S-DS-PRJ-10 field) to update the current requirements of the target project.

[0116] Step CS7: If the target project has no software production schedule (i.e., the S-DS-PRJ-10 field is empty), the engineering software management module will add the newly added defects as the current requirements of the target project, i.e., add the newly added data (i.e., the defect number of the newly added defect) of the G-DS-SW-07 field in the general software basic information of the target general software version to the S-DS-PRJ-09 field in the engineering software project information of the target project. This ensures that the newly added defects are considered and handled in a timely manner in subsequent project planning and demand management, and avoids the situation where engineering software is delivered with defects.

[0117] Step CS8: If the target project has software production progress (i.e. the S-DS-PRJ-10 field is not empty), a new requirement reminder for the target project will be issued to prompt the engineering personnel of the target project to adjust the project plan in time. This can reduce the rework of subsequent engineering software and ensure that defective software will not be delivered due to omissions or errors.

[0118] In one embodiment, based on the management experience of engineering software, the engineering software management module can actively trigger information for adding a new engineering project. It is understandable that when an engineering project is added, the engineering software under the engineering project needs to be developed, resulting in changes in the engineering software. Figure 8 As shown, Figure 8 The figure shows a schematic diagram of the D operation process of the railway engineering project management system, wherein the D operation refers to the management process executed by the engineering software management module when a new engineering project is added.

[0119] Step DS1: When a new engineering project is added, the engineering software management module creates a new management object to manage the engineering software information of the new engineering project.

[0120] Step DS2: The engineering software management module collects the engineering software project information of the newly added engineering project, and stores the engineering software project information based on the newly created management object and referring to the data format of Table 3.

[0121] Step DS3: The engineering software management module screens and adapts the general software. Specifically, the engineering software management module actively triggers the communication management module to execute the information interaction between the general software management module and the engineering software management module, so that the engineering software management module can synchronously obtain the general software information of the general software management module. The engineering software management module screens the general software basic information according to the system model of the newly added engineering project (the S-DS-PRJ-06 field in the engineering software project information), and screens out the target general software version, wherein the applicable system (the G-DS-SW-05 field in the general software basic information) and application scope (the G-DS-SW-06 field in the general software basic information) of the target general software version match the system model of the newly added engineering project, so that the appropriate general software version can be selected for the newly added engineering project to avoid problems caused by incompatible or inapplicable versions.

[0122] Step DS4: The engineering software management module updates the common software version used by the newly added engineering project. Specifically, the engineering software management module determines the target common software version as the common software version used by the newly added engineering project, that is, updates the G-DS-SW-03 field in the engineering software project information of the newly added engineering project according to the S-DS-PRJ-07 field in the common software basic information of the target common software version, thereby ensuring that the common software version information recorded in the project is the latest information, which is convenient for engineering personnel to use in subsequent implementation.

[0123] Step DS5: The engineering software management module updates the current requirements of the newly added engineering project. Specifically, the engineering software management module determines the defect data associated with the target general software version as the current requirements of the newly added engineering project, that is, the G-DS-SW-07 field in the general software basic information of the target general software version is added to the S-DS-PRJ-09 field in the engineering software project information of the newly added engineering project, so that the known defects can be associated with the project requirements, so that appropriate repair measures can be taken in the process of developing the engineering software.

[0124] Based on the engineering software management module, when adding new engineering projects, the engineering software information is updated to ensure that when the engineering project starts software production, the engineering personnel can obtain the general software version used and related information such as defect repair, so as to avoid the rework or defective delivery of subsequent engineering software due to the use of the wrong version of the general software.

[0125] In one embodiment, based on the management experience of engineering software, the engineering software management module can actively trigger the information of engineering software version change. Fig. 9 As shown, Fig. 9The E operation flow diagram of the railway engineering project management system is shown, wherein the E operation refers to the management flow executed by the engineering software management module and the general software management module when the version of the engineering software is changed.

[0126] Step ES1: When the version of the engineering software changes, the engineering software management module creates a new management object to manage the engineering software development information of the new version of the engineering software.

[0127] Step ES2: The engineering software management module collects the engineering software development information of the new version of the engineering software, and stores the engineering software development information based on the newly created management object and with reference to the data format of Table 4.

[0128] Step ES3: The engineering software management module verifies whether the general software version used by the engineering project to which the new version of the engineering software belongs is consistent with the general software version used by the new version of the engineering software, that is, the S-DS-SW-03 field in the engineering software development information is verified according to the S-DS-PRJ-07 field in the engineering software project information, which can ensure that the general software version used by the engineering software of the current engineering project is consistent with the expected general software version, avoiding problems caused by mismatch of general software versions. This judgment result will further determine the configuration of the new version of the engineering software. The engineering software management module updates the engineering software development information of the new version of the engineering software and the engineering software project information of the engineering project to which it belongs based on the verification result, so that engineering personnel can understand the progress of the engineering project.

[0129] Step ES4: If the verification is consistent, it indicates that the newly released version of the engineering software is valid and can be identified as the latest version of the engineering software for the engineering project to which it belongs. The engineering software management module then updates the currently released engineering software identification of the engineering project to which it belongs (i.e., the S-DS-PRJ-08 field in the engineering software project information) according to the engineering software identification of the new version of the engineering software (i.e., the S-DS-SW-02 field in the engineering software development information) to ensure that the engineering software identification pointed to by the engineering project is in the latest state for subsequent use and reference.

[0130] Step ES5: The engineering software management module will also update the fields related to the development progress in the engineering software development information of the new version of the engineering software, including changing the software configuration management status of the new version of the engineering software (i.e., the S-DS-SW-06 field in the engineering software development information) to the completed status, indicating that the configuration management process of the new version of the engineering software has ended and the engineering software update has been successful.

[0131] Step ES6: The engineering software management module changes the software release status of the new version of the engineering software (i.e., the S-DS-SW-07 field in the engineering software development information) to a pending status, indicating that the new version of the engineering software is ready to be released and is waiting for further operations to execute the release.

[0132] Step ES7: The engineering software management module will also update the progress of the engineering project to which the new version of the engineering software belongs, and change the software production progress of the engineering project (i.e., the S-DS-PRJ-10 field in the engineering software project information) to "software to be released", indicating the current progress status of engineering software production, so that engineering personnel can understand the progress of the engineering project.

[0133] Step ES8: The purpose of releasing the new version of engineering software may include repairing related defects of general software. Based on this, the engineering software management module actively triggers the communication management module to execute information interaction between the general software management module and the engineering software management module, so that the general software management module can update the repair progress of related defects of general software based on the synchronized engineering software general information. Specifically, the general software management module checks the synchronized engineering software information to determine whether the new version of engineering software has repaired the general software defects. If the S-DS-SW-05 field in the engineering software development information of the new version of engineering software is not empty, it means that the new version of engineering software has repaired the general software defects. Based on this, the general software management module updates the repair progress corresponding to the general software used by the new version of engineering software (i.e., the G-DS-DEF-06 field in the general software defect information).

[0134] Step ES9: If the verification is inconsistent, it indicates that there is a problem with the general software version used by the new version of the engineering software. Therefore, the engineering software management module marks the software configuration management status of the new version of the engineering software (i.e., the S-DS-SW-06 field in the engineering software development information) as abnormally interrupted to prevent this version of the engineering software from being erroneously delivered to field applications.

[0135] Step ES10: The engineering software management module also marks the engineering project described in the new version of the engineering software, and changes the software production progress of the engineering project (i.e., the S-DS-PRJ-10 field in the engineering software project information) to a general software version exception, so that engineering personnel can clearly understand the cause of the exception and take corresponding solutions in time.

[0136] Based on this, the engineering software management module updates the engineering software information under abnormal conditions, which can interrupt the configuration management process of the new version of the engineering software, thereby interrupting subsequent engineering software releases and other links, and preventing the delivery of unintended versions of engineering software.

[0137] In one embodiment, based on the management experience of engineering software, the engineering software management module can actively trigger information for changes in the engineering software management status, where the engineering software management status refers to the situation where any of the software release status, software customer simulation status, software delivery status, and software archiving status changes.

[0138] When the engineering software management status changes, the engineering software management module needs to synchronously update the software generation progress of the engineering project to which the engineering software belongs (i.e., the S-DS-PRJ-10 field in the engineering software project information) to ensure that the engineering project progress information is always consistent with the current engineering software status, so that engineering personnel can grasp the project progress in real time.

[0139] It is understandable that when the engineering software version changes, there is a possibility that the engineering software will repair the general software defects. Therefore, when the engineering software management status changes, it may affect the progress of repairing the general software defects. Based on this, the engineering software management module actively triggers the communication management module to execute the information interaction between the general software management module and the engineering software management module. The general software management module checks the repair of general software defects in the synchronized engineering software development information (i.e., the S-DS-SW-06 field). If the field is not empty, the repair progress of the general software (i.e., the G-DS-DEF-06 field in the general software defect information) is updated synchronously, so that the progress of defect repair can be tracked in real time.

[0140] In practical applications, reference Figure 3 and Figure 4 The general software management module and the engineering software management module are respectively configured with data interfaces. The general software management module collects general software information through the configured data interfaces, and the engineering software management module collects engineering software information through the configured data interfaces. Figure 3 and Figure 4 In the example, the data interfaces configured by the general software management module and the engineering software management module include the first data interface, the second data interface and the third data interface respectively. The first data interface is used to receive information manually input online. The administrator manually fills in the information online through the railway engineering project management system and submits it for saving. The first data interface obtains the information manually filled in by the administrator to complete the information collection.

[0141] The second data interface is used to receive the record files uploaded by the administrator. The administrator uploads the record files online (single / batch) through the railway engineering project management system. The second data interface extracts relevant information according to the agreed rules to complete the information collection.

[0142] The third data interface is used to receive data transmitted by the existing management system. The general software management module establishes a connection with the existing product management system through the third data interface, receives the agreed information from the product management system, and stores it in the general software management module, thereby completing the collection of general software information. The engineering software management module establishes a connection with the existing engineering software production management system through the third data interface, receives the agreed information from the engineering software generation management system, and stores it in the engineering software management module, thereby completing the collection of engineering software information.

[0143] In one embodiment, Figure 1 As shown, the railway engineering project management system also includes a user management module, which provides a function of hierarchical allocation of permissions. The system administrator designates a module administrator, and the module administrator creates an account according to user requirements and allocates applicable permissions to achieve permission management of system users. Among them, system users with administrator permissions can manage management objects in the general software management module and the engineering software management module. When the general software or the engineering software is changed, new management objects are added to the general software management module and the engineering software management module.

[0144] The user management module can create work permissions based on the daily work responsibilities of offline work roles to the greatest extent possible, optimize online and offline work interfaces, improve the convenience and timeliness of information transmission, and create a good foundation for system data maintenance.

[0145] The railway engineering project management system manages general software information in a unified manner through the general software management module, and manages engineering software information in a unified manner through the engineering software management module. On this basis, it cooperates with the communication management module to realize information interaction between the general software management module and the engineering software management module, so that the software management module and the engineering software management module can be synchronized to the changed general software information and engineering software information.

[0146] In one embodiment, a railway project management method applied to a railway project management system is provided, and the method may include:

[0147] Step 1: When the general software is changed, the changed general software information is managed based on the general software management module.

[0148] The general software management module in the railway engineering project management system is responsible for managing general software information, including collecting, storing and displaying general software information. General software information refers to the relevant attribute information of general software, including the development, version management, maintenance and various related status information of general software.

[0149] When the general software changes (such as the version of the general software, the application scope of the general software, and the defects of the general software), the railway engineering project management system will manage the changed general software information based on the general software management module, thereby updating the general software information stored in the general software management module.

[0150] Step 2: Based on the communication management module, information interaction is performed between the general software management module and the engineering software management module, and based on the engineering software management module, the engineering software information is synchronously updated according to the updated general software information.

[0151] The railway engineering project management system will also execute information exchange between the general software management module and the engineering software management module based on the communication management module, realizing efficient and real-time communication between the general software management module and the engineering software management module. In the case of changes in the general software, the communication management module is triggered by the general software management module, so that the engineering software management module can be synchronized with the latest general software information.

[0152] Here, the engineering software management module in the railway engineering project management system is responsible for managing engineering software information, including collecting, storing and displaying engineering software information. Engineering software information refers to the relevant attribute information of the engineering software used in each engineering project.

[0153] Engineering software is obtained by customizing general software according to the requirements of engineering projects. Therefore, when the general software changes, it is necessary to update the engineering software information of the engineering software affected by the changed general software.

[0154] The railway engineering project management system can obtain the latest general software information based on the engineering software management module, thereby synchronously updating the engineering software information according to the updated general software information, and can synchronously adjust the engineering software of the engineering projects involved, ensuring the functionality and safety of the engineering software.

[0155] Among them, when the general software of the railway engineering project system changes, it involves the A, B and C operation processes. For the A, B and C operation processes, please refer to Figure 5 , Figure 6 and Figure 7 and the specific instructions above for A, B, and C assignments.

[0156] Step 3: When the engineering software is changed, the changed engineering software information is managed based on the engineering software management module.

[0157] In actual applications, in addition to changes in general software, engineering software will also change (including new projects, engineering software versions, and engineering software management status). The railway engineering project management system will manage the changed engineering software information based on the engineering software management module, thereby updating the engineering software information stored in the engineering software management module to ensure that the engineering software information stored in the engineering software management module can reflect the real-time situation of the engineering project.

[0158] Step 4: Based on the communication management module, information interaction is performed between the general software management module and the engineering software management module, and based on the engineering software management module, the engineering software information is updated according to the general software information in the general software management module, or based on the general software management module, the general software information is synchronously updated according to the updated engineering software information.

[0159] When the engineering software changes, the communication management module will be triggered by the engineering software management module. The railway engineering project management system executes information interaction between the engineering software management module and the general software management module through the communication management module, so that the engineering software management module in the railway engineering project management system can be synchronized to the general software information, and then based on the general software information synchronized to the engineering software management module, the engineering software information is updated for a second time. In actual applications, engineering software is built based on general software. Based on this, in the case of new engineering projects, that is, there are new engineering software, and it is necessary to select general software that meets the needs of the engineering project for the new engineering software, so as to develop the engineering software based on the selected general software. Therefore, the railway engineering project management system needs to perform a second update of the engineering software information based on the general software information.

[0160] In addition, after the communication management module is triggered, the general software management module in the railway engineering project management system can synchronize the changed engineering software information, and then update the general software information based on the engineering software information synchronized to the general software management module, so that the general software information can be updated in real time. In actual applications, engineering software can repair defects in general software. Therefore, the railway engineering project management system needs to perform information interaction between the engineering software management module and the general software management module through the communication management module, so that the general software management module can synchronize the general software defect repair situation.

[0161] Among them, the update of engineering software involves the operation process of D and E of the railway engineering project management system. The operation process of D and E can be referred to Figure 8 and Fig. 9 As well as the specific instructions for assignments D and E above.

[0162] like Fig.10 As shown, Fig.10A management process diagram of a railway engineering project management system is shown.

[0163] Step MS1: Release a new version of general software;

[0164] Step MS2: the system automatically executes steps AS1 to AS10 in the A operation flow;

[0165] Step MS3: If the general software undergoes a change that affects the scope of application, the system automatically executes steps BS1 to BS5 in the B operation flow;

[0166] Step MS4: If a new common software defect is found, the system automatically executes steps CS1 to CS8 in the C operation flow;

[0167] Step MS5: If a new project is created, the system automatically executes steps DS1 to DS5 in the D operation flow;

[0168] Step MS6: If a new version of the engineering software is configured, the system automatically executes steps ES1 to ES10 in the E operation flow;

[0169] Step MS7: If the status of the engineering software changes, the system updates the software production schedule of the engineering project to which the engineering software belongs;

[0170] Step MS8: If the Repair General Software Defect field of the engineering software is not empty, the system updates the repair progress of the corresponding general software.

[0171] In the above embodiment, the railway engineering project management system is composed of a general software management module, an engineering software management module and a communication management module, wherein the communication management module can promptly transmit the change information to other modules, so that the general software and engineering projects can be adjusted in a timely manner, and the engineering projects can be assisted to trigger the update or optimization of the general software in the engineering software according to actual needs and schedule plans, which helps to avoid the delivery of engineering software with defects and promptly repair general defects and provide real-time feedback, and can provide more efficient and reliable management methods.

[0172] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0173] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0174] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. A railway engineering project management system, characterized in that: The railway engineering project management system includes: General software management module, used to manage general software information; Engineering software management module, used to manage engineering software information; A communication management module, used for executing information interaction between the general software management module and the engineering software management module; Wherein, when the general software is changed, the general software management module manages the changed general software information and triggers the communication management module; the engineering software management module synchronously updates the engineering software information based on the updated general software information; When the engineering software changes, the engineering software management module manages the changed engineering software information and triggers the communication management module; the engineering software management module updates the engineering software information for a second time based on the general software information in the general software management module, or the general software management module synchronously updates the general software information based on the updated engineering software information.

2. The railway engineering project management system according to claim 1, characterized in that: The general software information includes general software basic information and general software defect information; the general software management module stores the general software basic information with the general software version as the identification unit, and stores the general software defect information with the defect as the identification unit; The engineering software information includes engineering software project information and engineering software development information; the engineering software management module uses engineering projects as identification units to store the engineering software project information, and uses engineering software versions as identification units to store the engineering software development information.

3. The railway engineering project management system according to claim 2, characterized in that: When the version of the general software changes, the general software management module collects general software basic information of the new version of the general software, determines a target software version that matches the software identifier of the new version of the general software, and adds a historical version mark to the target software version; The engineering software management module filters out a target project that matches the applicable system and application scope corresponding to the software identifier, and updates the general software version used by the target project; wherein, if the target project does not specify general software, or, if the target project specifies general software and the target project has no software production progress, the new version of general software is designated as the general software of the target project; if the target project specifies general software and the target project has a software production progress, the software production progress of the target project is set to a general software version exception.

4. The railway engineering project management system according to claim 2, characterized in that: When the application scope of the general software changes, the engineering software management module selects a target project that matches the application scope of the general software before the application scope changes, updates the software production schedule of the target project, and updates the general software version used by the target project according to the general software basic information in the general software management module; wherein, If the target project has no software production progress, the general software version used by the target project is cleared; if the target project has software production progress, the software production progress of the target project is set to be a general software version exception.

5. The railway engineering project management system according to claim 2, characterized in that: When a new defect occurs in the general software, the general software management module collects general software defect information of the new defect, screens and obtains a target general software version that matches the general software version of the new defect, and adds the new defect to the target general software version; The engineering software management module selects target projects that match the application scope of the target general software version according to the target general software version, and updates the current requirements of the target project according to the software production progress of the target project; wherein, If the target project does not have the software production progress, the newly added defects are added as the current requirements of the target project; if the target project has a software production progress field, a new requirement prompt for the target project is issued.

6. The railway engineering project management system according to claim 2, characterized in that: When adding a new engineering project, the engineering software management module collects engineering software project information of the newly added engineering project, and filters out a target general software version based on the system model of the newly added engineering project; determines the target general software version as the general software version used by the newly added engineering project, and determines the associated defects of the target general software version as the current requirements of the newly added engineering project.

7. The railway engineering project management system according to claim 2, characterized in that: When the version of the engineering software changes, the engineering software management module collects the engineering software development information of the new version of the engineering software, verifies the common software version used by the engineering project to which the new version of the engineering software belongs and the common software version used by the new version of the engineering software, and updates the engineering software development information of the new version of the engineering software and the engineering software project information of the engineering project to which the new version of the engineering software belongs based on the verification result.

8. The railway engineering project management system according to claim 2, characterized in that: The engineering software management module updates the software production progress of the engineering project to which the engineering software belongs when the management status of the engineering software changes; When there is a general software defect repaired in the engineering software development information of the engineering software, the general software management module updates the repair progress of the corresponding general software in the general software management module regarding the repaired general software defect.

9. The railway engineering project management system according to claim 1, characterized in that: The railway engineering project management system also includes a user management module for performing authority management on system users; when the general software or the engineering software changes, the system user is issued administrator authority to add new management objects in the general software management module or the engineering software management module.

10. A railway engineering project management method, characterized in that: Applied to the railway engineering project management system according to any one of claims 1 to 9, the method comprising: When general software is changed, the changed general software information is managed based on the general software management module; Execute information interaction between the general software management module and the engineering software management module based on the communication management module, and synchronously update the engineering software information according to the updated general software information based on the engineering software management module; When the engineering software is changed, the changed engineering software information is managed based on the engineering software management module; Based on the communication management module, information interaction is performed between the general software management module and the engineering software management module, and based on the engineering software management module, the engineering software information is updated for a second time according to the general software information in the general software management module, or based on the general software management module, the general software information is synchronously updated according to the updated engineering software information.

Images