Project design link full-process digital management method and system

Abstract

The invention relates to a full-process digital management method and system for a project design link. The method comprises the following steps: editing a project design document in a project process on line; integrating the project design documents, associating various project design documents based on demand BRP, and digitally penetrating various project design documents by taking function points as base points; various project design documents are disassembled and integrated, and digital assets are precipitated in a system dimension; and performing targeted modification and updating based on the function points, and multiplexing the digital assets through the function points and the associated contents of the function points. According to the method, demand design, development scheme design and test scheme design in the research and development process are managed in a centralized mode, full-process digital management of design research and development links is achieved, design assets in the management process are split and integrated according to system dimensions, and design asset precipitation and reuse of the system dimensions are achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of project digital management, and in particular to a method and system for digital management of the entire process of project design. Background Art

[0002] During the project implementation, business requirements are analyzed by BA to form offline requirements specifications (referred to as soft requirements). Development or testing produces design documents such as Logic, API, DB and test plans based on the soft requirements. Each project document is stored separately according to requirements or system dimensions, and the data is relatively fragmented. Whether the document content covers all requirements or relevance is entirely controlled by humans.

[0003] Currently, project documents are scattered, making it extremely difficult for project members to find them. In addition, offline Word documents are not updated in a timely manner or notifications are not in place, which easily leads to version differences and causes deviations in project implementation. Various types of project documents are relatively independent, making it difficult to determine whether the requirements are fully covered or their relevance, which easily leads to deviations in project implementation. Documents lack review benchmarks and have varying quality. After requirements are completed, it is difficult to accumulate system-related documents, trace functional logic, and reuse digital assets. Summary of the invention

[0004] In order to address the shortcomings of the existing technology, the present invention centrally manages the demand design, development plan design, and test plan design in the research and development process, realizes the digital management of the entire process of design and development, and realizes the precipitation of design assets in the system dimension by splitting and integrating the design assets in the management process according to the system dimension.

[0005] To achieve the above objectives, the technical solutions adopted by the present invention include:

[0006] A digital management method for the entire process of project design, characterized by comprising:

[0007] S1. Project design documents in the process of online editing of the project, including business requirements documents, software requirements specifications, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan;

[0008] S2. Integrate project design documents, link various project design documents based on demand BRP, and digitize all kinds of project design documents based on functional points;

[0009] S3. Disassemble and integrate various project design documents to precipitate digital assets in a system dimension;

[0010] S4. Perform targeted modification and update based on the function points, and reuse digital assets through the function points and the associated contents of the function points.

[0011] Furthermore, the online editing includes: document content editing, function reference, document addition, deletion, modification and query, multi-person sharing, version recording and comparison.

[0012] Furthermore, the digitization based on functional points runs through various documents, including:

[0013] Based on the business needs of function point splitting, a function point ID is assigned to the function point as a unique ID, and the function point ID is used to run through downstream documents and merge system specifications;

[0014] Generate a user story optional list based on the function point, the user story optional list inherits the function point ID, and the tasks in the user story optional list are strongly associated with the function point;

[0015] Create R&D Logic, API, and DB documents based on the function points, where the R&D Logic, API, and DB documents are strongly associated with the function points;

[0016] Initialize the technical test plan and user acceptance test plan documents through the demand BRP, synchronize the test points in the technical test plan and user acceptance test plan documents based on the function points, and the test points inherit the function point ID;

[0017] The test points are used as a directory of test cases in the technical test plan and user acceptance test plan documents, and the test cases are associated with the function points.

[0018] Furthermore, the various project design documents are disassembled and integrated to precipitate digital assets in a system dimension, including:

[0019] Disassemble the system to which each function point in the project design document belongs based on the function point ID, identify the modules, function services, and function points layer by layer, locate and integrate them, submit them to the corresponding system, and generate a system specification;

[0020] Based on the function point ID, the system to which each test point in the project design document belongs is disassembled, and the modules, functional services, and function points are identified layer by layer, and then located and integrated into the corresponding system test baseline.

[0021] Furthermore, the targeted modification and update based on the function point, and the reuse of the digital assets through the function point and the associated content of the function point, include:

[0022] When a function point is changed, the logic description is modified by referencing the function point in the system manual, and the R&D Logic, API, and DB documents associated with the function point are updated accordingly;

[0023] By digitally associating function points with test points, test cases can be reused for test adjustment and verification.

[0024] Furthermore, the method further comprises:

[0025] The project design document is finalized after review, which includes initiating a CheckList review to the core members of the project and notifying the entire project team of the updated content points of the document.

[0026] The present invention also relates to a digital management system for the entire process of project design, which is characterized by comprising:

[0027] Online editing module, used for online editing of project design documents in the project process, including business requirement documents, software requirement specifications, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan;

[0028] The digital penetration module is used to integrate project design documents, associate various project design documents based on demand BRP, and digitally penetrate various project design documents based on functional points;

[0029] The asset sedimentation module is used to disassemble and integrate various project design documents and sediment digital assets in a system dimension;

[0030] The asset reuse module is used to perform targeted modification and update based on function points, and reuse digital assets through function points and their associated contents.

[0031] The present invention also relates to a computer-readable storage medium, characterized in that a computer program is stored on the storage medium, and the computer program implements the above method when executed by a processor.

[0032] The present invention also relates to an electronic device, characterized in that it comprises a processor and a memory;

[0033] The memory is used to store program instructions;

[0034] The processor is used to execute the above method by calling program instructions.

[0035] The present invention also relates to a computer program product, comprising a computer program and / or instructions, characterized in that the computer program and / or instructions implement the steps of the above method when executed by a processor.

[0036] The use of the project design full-process digital management method and system described in the present invention can achieve at least the following technical effects:

[0037] 1. Unified document management: The tool supports online editing and management of various documents. At the same time, based on the demand dimension, it integrates business requirement documents, software requirement documents, development plan design, test plan, user acceptance test plan and other documents in the project implementation process to solve the problems of poor version management and traceability difficulties;

[0038] 2. Digitalization throughout design documents: Software requirement documents are split by function points, and business logic is written by citing system function points. Downstream documents such as logic design, API design, DB design, task design, and test case design are all digitally associated with function points as the core, achieving comprehensive coverage and effective penetration of project design status;

[0039] 3. Design asset sedimentation: The functional logic in the software requirement document and the associated logic design, API design, DB design, and test case design are all split, integrated, and sedimented in the system dimension, and support the reuse of digital assets.

[0040] 4. Project collaboration and review mechanism: Supports online review process, all documents are reviewed and checked by CheckList, archived documents are merged and reviewed, and document changes or tasks are reminded in real time, which greatly improves project collaboration efficiency and document quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.

[0042] Figure 1 A schematic diagram of a process flow of a digital management method for the entire process of a project design link according to the present invention;

[0043] Figure 2 This is a schematic diagram of the structure of a digital management system for the entire process of project design in the present invention;

[0044] Figure 3 The figure is a schematic structural diagram of an electronic device of the present invention. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. It should be understood that the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments, and these embodiments are only used to illustrate the present application and are not used to limit the scope of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0046] like Figure 1As shown, the embodiment of the present invention discloses a method for digital management of the entire process of project design, and the steps of the process include:

[0047] Step S1. Edit the project design document during the project online, wherein the project design document includes business requirement document, software requirement specification, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan.

[0048] Specifically, online editing includes: document content editing, function reference, document addition, deletion, modification and query, multi-person sharing, version recording and comparison.

[0049] Among them, R&D Logic, API, and DB are three key components in the software development process.

[0050] Logic: refers to the business logic of the software, that is, the rules and processes of how the software processes data and performs tasks according to business requirements, which defines the behavior and functions of the software;

[0051] API (Application Programming Interface): These are predefined functions that enable interactive communication between software components without access to source code, and can access specific functions or data;

[0052] DB (database): used to store and manage data. In software development, it can persistently store application data, including user information, usage configuration, etc. The database also includes functions such as data creation, query, update and management.

[0053] Research and development of Logic, API, and DB can ensure that the software system works as expected and supports the collaborative development process of project design. Specifically, the logic part defines in detail how to respond to user operations and process business logic; the API interface defines the interface specification to ensure the interactive response between software systems; the database part needs to build a data model according to business needs to ensure data integrity.

[0054] Step S2. Integrate project design documents, link various project design documents based on demand BRP, and digitize all kinds of project design documents based on functional points.

[0055] Project design documents are integrated into the management tool for unified management. Various project design documents are associated with each other through the demand BRP as the unique key value. The management tool includes the demand ledger function, which can aggregate project information and document deliverables. Documents are carried in the form of attachments. All related documents can be accessed and viewed through the key value, thereby improving project management efficiency.

[0056] Demand BRP is business demand planning, which can serve as a unique identifier for business or project requirements. It can effectively link various project design documents for easy management. This method helps ensure that project team members can quickly locate all documents related to specific requirements, thereby improving work efficiency and project delivery success rate.

[0057] In this embodiment, the soft function point ID is used as the base point for radiation, and digitization runs through various project design documents, including:

[0058] In the requirement design phase, business requirements are split based on function points. This phase can support the reference of a system function point for logical description or modification. Each system function point is assigned a unique ID (function point ID) as the key value throughout the downstream documents or merged system specifications;

[0059] In the user story design phase, a user story optional list is generated based on the function point. The user story optional list inherits the function point ID. The tasks in the user story optional list are strongly associated with the function point. The application architect can clarify the tasks to be created through the function point to achieve the effect of checking for omissions and filling gaps. R&D personnel can quickly locate the corresponding function point from the task and quickly understand the business function logic;

[0060] In the R&D design stage, R&D Logic, API, and DB documents are created based on the function points. There is a strong correlation between the R&D Logic, API, and DB documents and the function points. The R&D design process can be understood through the function points, and the corresponding function logic can be viewed through the R&D design documents.

[0061] During the test plan design phase, the technical test plan and user acceptance test plan documents are initialized through the requirement BRP, and the test points in the technical test plan and user acceptance test plan documents are synchronized based on the function points. The test points inherit the function point ID, which strengthens the correlation between the test points and the functions.

[0062] During the test case design phase, the test points are used as the directory of test cases in the technical test plan and user acceptance test plan documents. The test cases are digitally associated with the functional points, which effectively verifies whether the test cases fully cover the required functions.

[0063] Step S3. Disassemble and integrate various project design documents to precipitate digital assets in the system dimension.

[0064] Specifically, various project design documents are disassembled and integrated to precipitate digital assets from a system dimension, including:

[0065] Software requirement documents, R&D Logic, API, and DB documents are disassembled into the systems to which each function point belongs based on the function point ID. Through layer-by-layer identification of modules, function services, and function points, they are located, integrated, and submitted to the corresponding system. Tools are used to compare changes such as function logic design. The system manager merges and reviews, overwrites the original system function design, and generates a system specification.

[0066] The test points in the test plan inherit the function point ID of the requirement specification. Based on the function point ID, the system to which each test point belongs in the project design document is disassembled, and the modules, function services, and function points are identified layer by layer, and the positioning is integrated into the corresponding system test baseline. At the same time, the test point is the parent directory of the test case, and the test case is deposited into the system test baseline along with the test point.

[0067] Step S4: Perform targeted modification and update based on the function points, and reuse digital assets through the function points and the associated contents of the function points.

[0068] Specifically, targeted modification and updating are performed based on the function points, and digital assets are reused through the function points and the associated contents of the function points, including:

[0069] If the requirements design stage involves changes to functional points, the functional points in the system manual can be referenced to modify the logical description. At the same time, the R&D Logic, API, DB and other documents associated with the functional point can be referenced together, and targeted updates can be made during the R&D design stage. Since there is a digital connection between functional points and test points, the test link can quickly reuse baseline use cases for test adjustment and verification.

[0070] In an embodiment of the present invention, it also includes:

[0071] The project design document is finalized after review, which includes initiating a CheckList review to the core members of the project and notifying the entire project team of the updated content points of the document.

[0072] like Figure 2 As shown, the embodiment of the present invention discloses a digital management system for the entire process of project design, and its structure includes:

[0073] Online editing module, used for online editing of project design documents in the project process, including business requirement documents, software requirement specifications, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan;

[0074] The digital penetration module is used to integrate project design documents, associate various project design documents based on demand BRP, and digitally penetrate various project design documents based on functional points;

[0075] The asset sedimentation module is used to disassemble and integrate various project design documents and sediment digital assets in a system dimension;

[0076] The asset reuse module is used to perform targeted modification and update based on function points, and reuse digital assets through function points and their associated contents.

[0077] By using this system, the above-mentioned operation processing method can be executed and the corresponding technical effects can be achieved.

[0078] An embodiment of the present invention is given below.

[0079] 1. Users can create different types of documents and edit them according to online document templates. The documents are always guaranteed to be up-to-date and unique.

[0080] 2. Users can save manually or quickly during editing, and the data will be automatically saved every 5 minutes to avoid data loss.

[0081] 3. Since there are associations between documents, users can view the entire project document based on the document or requirement number. They can find all by searching for one document, which greatly improves collaboration efficiency.

[0082] 4. The finalized documents must be reviewed and approved by the project team members to ensure the quality of the documents. It supports users to submit document reviews, set review inspection members, review resolution members, and document update notification members, which ensures the quality of the documents while improving the collaborative efficiency of update notifications.

[0083] 5. Records will be made after each document version is submitted for review. Users can also compare two different versions to quickly learn about document modifications.

[0084] 6. After the project requirements are put into production, all kinds of documents will decompose and integrate the contents into various systems for sedimentation. Users can understand the system's functions, functional logic, R&D logic and other information by reading the system manual, which helps users understand the system.

[0085] 7. Provide specific scenario applications based on the characteristics of different project roles, including:

[0086] (1) Scenario application of BA role:

[0087] When editing software requirements, if the required functional points have been deposited in the system specification, the BA can quote the system specification functional points in the text and modify its logic to achieve the reuse of digital assets and reduce the repeated editing of historical logic.

[0088] Soft demand users can associate demand IDs to unify soft demands into a certain demand, thus integrating demand-related documents.

[0089] In the UserStory task creation phase, the tool will provide a task list based on the functional points in the software requirements. The BA can select the task list to quickly associate and create. The task and the document functional point form a digital association, and the functional logic of the document can be quickly located through the task.

[0090] It supports the integration of offline attachments. Interactive visuals, tracking points and other documents can be uploaded to the attachments. Project members can find relevant offline project documents through software requirements.

[0091] After the demand is put into production, the software demand document is automatically submitted and merged into the system specification. The functional logic in the document will be decomposed and submitted to each system for merging. The BA of each system will conduct a merger review of its functional logic, and if passed, it can be merged into the specification of the system.

[0092] (2) Research and develop role-based scenarios, including:

[0093] When R&D documents (such as Logic, DB, API, etc.) are completed, they support associating soft requirement function points, effectively associating the functional logic and technical logic of the business. After the requirements are launched, they are merged into the system specification along with the soft requirement function points to achieve digital asset sedimentation. The requirements can also be reused and modified later.

[0094] When R&D personnel receive UserStory tasks, they can locate the functional points of the software requirements through deep links and accurately locate the demand logic of the function.

[0095] (3) Scenario application of test roles, including:

[0096] The test plan (including UAT user acceptance test plan) document supports users to associate the requirement ID, unify the test plan to a certain requirement, and achieve the integration of requirement-related documents.

[0097] When users associate a requirement ID, the document data can be initialized, and data such as project implementation progress data, software function points, story test tasks, etc. in the document can be automatically associated and filled to form a preliminary draft of the plan. Users can make adjustments on the initialized document, which greatly improves editing efficiency. At the same time, the function points and test points in the document will also form an effective association, strengthening the relevance of the document content from top to bottom.

[0098] During the test case design phase, the tool recommends that users use the three-level directory of software requirement function points as the case directory. Users use and design test cases under this directory, and then the cases are effectively associated with the software requirement function points and the test plan test points.

[0099] After the demand is put into production, the test cases will be decomposed and submitted to the test baseline of each system for merging. The person in charge of each system test will review the merger of their test cases. If passed, they can be merged into the test baseline of the system. If there is a need to adjust its functional points in the future, the test cases of the functional points can be reused.

[0100] An embodiment of the present invention also provides a computer-readable storage medium capable of implementing all the steps in the method in the above embodiment, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, all the steps in the method in the above embodiment are implemented.

[0101] The embodiment of the present invention further provides an electronic device for executing the above method, as a device for implementing the method, and its structure is as follows: Figure 3 As shown, the electronic device 300 includes: a processor 301 and a memory 303. The processor 301 and the memory 303 are connected, such as through a bus 302. Optionally, the electronic device 300 may also include a transceiver 304. It should be noted that in actual applications, the transceiver 304 is not limited to one. It is understandable that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the specific structure of the electronic device 300. In other embodiments of the present application, the electronic device 300 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. Optionally, the electronic device may also include a display screen 305 for displaying images, or receiving user operation instructions when necessary.

[0102] The processor 301 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 304 may include a receiver and a transmitter. The transceiver 304 is applied in the embodiment of the present application to implement the function of the electronic device of the embodiment of the present application communicating with other devices when executed.

[0103] Processor 301 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 301 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0104] The processor 301 may also include one or more processing units, for example, the processor 301 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processor (NPU). Among them, different processing units may be independent devices or integrated into one or more processors. Among them, the controller may be the nerve center and command center of the electronic device 300. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions. A memory may also be set in the processor 301 for storing instructions and data. In some embodiments, the memory in the processor 301 is a high-speed cache memory. The memory may store instructions or data that the processor 301 has just used or circulated. If the processor 301 needs to use the instruction or data again, it may be directly called from the memory. Repeated access is avoided, the waiting time of the processor 301 is reduced, and the efficiency of the system is improved.

[0105] The processor 301 can run the method provided in the embodiment of the present application. The processor 301 can include different devices. For example, when a CPU and a GPU are integrated, the CPU and the GPU can cooperate to execute the method provided in the embodiment of the present application, for example, part of the algorithm in the method is executed by the CPU, and another part of the algorithm is executed by the GPU to obtain faster processing efficiency.

[0106] The bus 302 may include a path to transmit information between the above components. The bus 302 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 302 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0107] The memory 303 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or may include a high-speed random access memory, or may include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0108] Optionally, the memory 303 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 301. The processor 301 is used to execute the application code stored in the memory 303 to implement the method provided in any embodiment of the present application.

[0109] The memory 303 can be used to store computer executable program codes, which include instructions. The processor 301 executes various functional applications and data processing of the electronic device 300 by running the instructions stored in the memory 303. The memory 303 may include a program storage area and a data storage area. Among them, the program storage area may store the code of the operating system, application program, etc. The data storage area may store data created during the use of the electronic device 300 (such as images, videos, etc. collected by the camera application), etc.

[0110] The memory 303 may also store one or more computer programs corresponding to the method provided in the embodiment of the present application. The one or more computer programs are stored in the above-mentioned memory 303 and are configured to be executed by the one or more processors 301, and the one or more computer programs include instructions, and the above-mentioned instructions can be used to execute each step in the above-mentioned corresponding embodiment.

[0111] Of course, the code of the method provided in the embodiment of the present application can also be stored in an external memory. In this case, the processor 301 can run the code of the method stored in the external memory through the external memory interface, and the processor 301 can control the running process.

[0112] The display screen 305 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 300 may include 1 or N display screens 305, where N is a positive integer greater than 1. The display screen 305 can be used to display information input by a user or information provided to a user and various graphical user interfaces (GUI). For example, the display screen 305 can display photos, videos, web pages, or files.

[0113] The electronic device provided in the embodiment of the present application is applicable to any embodiment of the above method. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0114] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0115] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or multiple boxes.

[0116] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction system, which is implemented in the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0117] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps of the functions specified in a box or multiple boxes. Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they know the basic creative concept. Therefore, the attached claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0118] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A digital management method for the entire process of project design, characterized in that: include: S1. Project design documents in the process of online editing of the project, including business requirements documents, software requirements specifications, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan; S2. Integrate project design documents, link various project design documents based on demand BRP, and digitize all kinds of project design documents based on functional points; S3. Disassemble and integrate various project design documents to precipitate digital assets in a system dimension; S4. Perform targeted modification and update based on the function points, and reuse digital assets through the function points and the associated contents of the function points.

2. The method according to claim 1, characterized in that The online editing includes: document content editing, function reference, document addition, deletion, modification and query, multi-person sharing, version recording and comparison.

3. The method according to claim 1, characterized in that The digitization based on function points runs through all kinds of documents, including: Based on the business needs of function point splitting, a function point ID is assigned to the function point as a unique ID, and the function point ID is used to run through downstream documents and merge system specifications; Generate a user story optional list based on the function point, the user story optional list inherits the function point ID, and the tasks in the user story optional list are strongly associated with the function point; Create R&D Logic, API, and DB documents based on the function points, where the R&D Logic, API, and DB documents are strongly associated with the function points; Initialize the technical test plan and user acceptance test plan documents through the demand BRP, synchronize the test points in the technical test plan and user acceptance test plan documents based on the function points, and the test points inherit the function point ID; The test points are used as a directory of test cases in the technical test plan and user acceptance test plan documents, and the test cases are associated with the function points.

4. The method according to claim 1, characterized in that The above-mentioned disassembly and integration of various project design documents and the precipitation of digital assets in the system dimension include: Disassemble the system to which each function point in the project design document belongs based on the function point ID, identify the modules, function services, and function points layer by layer, locate and integrate them, submit them to the corresponding system, and generate a system specification; Based on the function point ID, the system to which each test point in the project design document belongs is disassembled, and the modules, functional services, and function points are identified layer by layer, and then located and integrated into the corresponding system test baseline.

5. The method according to claim 1, characterized in that The targeted modification and update based on the function point, and the reuse of digital assets through the function point and the associated content of the function point, include: When a function point is changed, the logic description is modified by referencing the function point in the system manual, and the R&D Logic, API, and DB documents associated with the function point are updated accordingly; By digitally associating function points with test points, test cases can be reused for test adjustment and verification.

6. The method according to claim 1, characterized in that The method further comprises: The project design document is finalized after review, which includes initiating a CheckList review to the core members of the project and notifying the entire project team of the updated content points of the document.

7. A digital management system for the entire process of project design, characterized in that: include: Online editing module, used for online editing of project design documents in the project process, including business requirement documents, software requirement specifications, R&D Logic, API, DB, technical testing plan, and user acceptance testing plan; The digital penetration module is used to integrate project design documents, associate various project design documents based on demand BRP, and digitally penetrate various project design documents based on functional points; The asset sedimentation module is used to disassemble and integrate various project design documents and sediment digital assets in a system dimension; The asset reuse module is used to perform targeted modification and update based on function points, and reuse digital assets through function points and their associated contents.

8. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: including a processor and a memory; The memory is used to store program instructions; The processor is configured to execute the method according to any one of claims 1 to 6 by calling program instructions.

10. A computer program product comprising a computer program and / or instructions, characterized in that: When the computer program and / or the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images