Software project configuration method and device, server and storage medium

Abstract

The invention relates to the technical field of information, in particular to a software project configuration method and device, a server and a storage medium, and the method comprises the steps: obtaining work items of each stage of a software project; creating a set corresponding to the work items of each stage, configuring the work items, and establishing a traceability relationship and a hierarchical relationship between the work items according to the configured work items; and according to the set corresponding to the work items of each stage and the traceability relationship and hierarchical relationship between the work items, constraining the software project, so that the software project conforms to a standardized management specification. Therefore, the problems of how to optimize and standardize the research and development process of the automobile software and how to ensure the efficient delivery of the software project are solved.

Description

Technical Field

[0001] The present application relates to the field of information technology, and in particular to a configuration method, device, server and storage medium for a software project. Background Art

[0002] With the rapid development of electrification, networking, intelligence and sharing in the automotive industry, vehicles are gradually shifting from traditional mechanical drive to software drive, which has led to a significant increase in the number of automotive software. Automotive software process improvement and capability assessment are widely adopted as a model framework for evaluating the level of software development capabilities in the automotive industry. However, the software development processes within each company may not be unified, resulting in inefficiency and unstable quality. Therefore, how to optimize and standardize the development process of automotive software and ensure the efficient delivery of high-quality software projects has become a key issue that needs to be solved urgently in the automotive industry. Summary of the invention

[0003] The present application provides a configuration method, device, server and storage medium for a software project to solve the problem of how to optimize and standardize the R&D process of automotive software and ensure the efficient delivery of software projects.

[0004] The first aspect of the present application provides a method for configuring a software project, comprising the following steps: obtaining work items for each stage of the software project; creating a collection corresponding to the work items for each stage and configuring the work items, and establishing a traceability relationship and a hierarchical relationship between each work item based on the configured work items; constraining the software project based on the collection corresponding to the work items for each stage, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with standardized management specifications.

[0005] Optionally, configuring work items includes: configuring custom fields and work item types for each work item, wherein custom fields include: field identifier, Chinese name displayed by the field, and field data type; defining all states and all executable actions for each work item, and establishing a mapping relationship between states and actions.

[0006] Optionally, establishing a hierarchical relationship between each work item includes: configuring a relationship type between each work item; and establishing a hierarchical relationship between each work item according to a field identifier of each work item and a relationship type between each work item.

[0007] Optionally, a traceability relationship is established between each work item, including: creating upstream traceability and downstream traceability for each work item; creating a traceability relationship between each work item based on the upstream traceability and downstream traceability, wherein the traceability relationship is used to update the status of all associated work items according to the traceability relationship of the target work item when the target work item changes.

[0008] Optionally, if the development tasks of the current stage are completed, the collection corresponding to the work items of the current stage is closed, the collection of the current stage and the files contained therein are regarded as the baseline, and the collection corresponding to the work items of the next stage references the baseline, wherein the baseline is frozen in the collection corresponding to the work items of the next stage.

[0009] Optionally, collections are used to organize output documents at different stages and support collection version control and user permission management.

[0010] The second aspect of the present application provides a configuration device for a software project, including: an acquisition module, used to acquire work items at each stage of the software project; a processing module, used to create a collection corresponding to the work items at each stage and configure the work items, and establish a traceability relationship and a hierarchical relationship between each work item based on the configured work items; a constraint module, used to constrain the software project based on the collection corresponding to the work items at each stage, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with standardized management specifications.

[0011] Optionally, the processing module is further used to: configure custom fields and work item types for each work item, where custom fields include: field identifier, Chinese name displayed by the field, and field data type; define all states and all executable actions of each work item, and establish a mapping relationship between states and actions.

[0012] Optionally, the processing module is further used to: configure the relationship type between each work item; and establish a hierarchical relationship between each work item according to the field identifier of each work item and the relationship type between each work item.

[0013] Optionally, the processing module is further used to: create upstream traceability and downstream traceability for each work item; create a traceability relationship between each work item based on the upstream traceability and downstream traceability, wherein the traceability relationship is used to update the status of all associated work items according to the traceability relationship of the target work item when the target work item changes.

[0014] Optionally, if the development tasks of the current stage are completed, the collection corresponding to the work items of the current stage is closed, the collection of the current stage and the files contained therein are regarded as the baseline, and the collection corresponding to the work items of the next stage references the baseline, wherein the baseline is frozen in the collection corresponding to the work items of the next stage.

[0015] Optionally, collections are used to organize output documents at different stages and support collection version control and user permission management.

[0016] The third aspect of the present application provides a server, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a configuration method for a software project as described in the above embodiment.

[0017] The fourth aspect of the present application provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed, it is used to implement a configuration method for a software project as in the above embodiment.

[0018] Therefore, this application has at least the following beneficial effects:

[0019] The embodiment of the present application can obtain the work items of each stage of the software project, and create a special collection for the work items of each development stage to organize all relevant documents generated in each stage, ensure the centralized management of information, and establish the traceability relationship and hierarchical relationship between each work item to ensure that any changes can be reflected in the upstream and downstream related documents in a timely manner. Therefore, the traceability relationship, hierarchical relationship and collection are used to constrain the entire project to ensure that it complies with the established management specifications, thereby meeting the requirements of the automotive software process improvement and capability assessment standards, and improving the compliance and quality of the project.

[0020] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0022] Figure 1 A flowchart of a method for configuring a software project according to an embodiment of the present application;

[0023] Figure 2 An example diagram of creating a collection according to an embodiment of the present application;

[0024] Figure 3 A diagram showing the relationship between the concepts of a set and product delivery according to an embodiment of the present application;

[0025] Figure 4 An example diagram of work item types provided according to an embodiment of the present application;

[0026] Figure 5 A bidirectional traceability relationship diagram between work items provided according to an embodiment of the present application;

[0027] Figure 6 A flowchart of a configuration work item provided according to an embodiment of the present application;

[0028] Figure 7 An exemplary diagram of a configuration device for a software project according to an embodiment of the present application;

[0029] Figure 8 Schematic diagram of the structure of a server according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0031] The following describes the configuration method, device, server and storage medium of the software project of the embodiment of the present application with reference to the accompanying drawings. In response to the problems mentioned in the above background technology, the present application provides a configuration method for a software project, in which the work items of each stage of the software project are obtained, and a special collection is created for the work items of each development stage to organize the relevant documents generated in that stage, thereby ensuring the centralized management of information, and establishing a traceability relationship and hierarchical relationship between each work item to ensure that any changes can be reflected in the upstream and downstream related documents in a timely manner. Thus, the traceability relationship, hierarchical relationship and collection are used to constrain the entire project to ensure that it complies with the established management specifications, thereby meeting the requirements of the automotive software process improvement and capability assessment standards and improving the compliance and quality of the project.

[0032] Specifically, Figure 1 A flowchart of a method for configuring a software project provided in an embodiment of the present application.

[0033] like Figure 1 As shown, the configuration method of the software project includes the following steps:

[0034] In step S101, work items of each phase of the software project are obtained.

[0035] The software project development process includes multiple environments such as demand mining, architecture design, software design, unit testing, integration testing, defect management, and change management. Each link is a work item. The content displayed in each work item can be pre-configured in a fixed format, and upload and export templates can be created.

[0036] In step S102, a collection corresponding to the work items of each phase is created and the work items are configured, and a traceability relationship and a hierarchical relationship between each work item are established according to the configured work items.

[0037] Collections are used to organize output documents at different stages and support collection version control and user permission management. Figure 2As shown, by configuring the collection and its permissions, customizing the fields that the collection needs to display, creating different collections according to the task phase, and adding the output documents of the corresponding phase to the collection. Different versions of the same document can be added to different collections. If the development task of the current phase is completed, the collection corresponding to the work item of the current phase is closed, and the files contained in the collection of the current phase are regarded as the baseline. The collection corresponding to the work item of the next phase references the baseline, where the baseline is frozen in the collection corresponding to the work item of the next phase.

[0038] In the present embodiment of the application, when a collection is open, all documents belonging to it can still be edited, added or deleted. Collection documents are unique in that they are always opened in the context of the collection. Because links to work items appear in the document version or document baseline selected for the collection, all outgoing links in these documents will only go to other documents in the collection. For documents that have been added, it is easy to replace one version with another, change the baseline revision to HEAD or any other arrangement.

[0039] A collection consistency check run can check work item links, reporting any links to a specific revision that are not available in the collection, reporting any work items that cannot be resolved, reporting all links to a specific revision with the HEAD version, reporting any links to work items outside the collection (links created before the document / work item was added to the collection). Any work item in the collection that has multiple versions, a collection baseline places a marker in the history of the collection so that the state of the collection can always be referenced at important milestones. When a document is opened in the context of a collection baseline, it is highlighted in the navigation.

[0040] When you reuse a collection, a new collection is created that references the same content as the source collection. (The selected source collection documents are frozen in the new collection, just as they were when the reuse was completed.) You can reuse any collection at this time, including closed collections or collection baselines, and you can preview them before creating a collection. When you preview a collection, you can edit it before it is created without affecting the source collection. The documents in the latest version of the collection that is reused are assigned a version number and frozen in the newly created collection. When a collection is closed, the collection and the files it contains can be treated as a baseline. Administrators can define permissions that only allow certain users to close or reopen collections. After closing, the document is read-only, and users can no longer edit the collection description or the version of the document. If you need to edit, you need to reopen the collection. For closed collections, you can reopen it.

[0041] Once all teams have completed version 1 of their specifications and have conducted their own reviews, Phase 1 of the project ends and the collection is closed to represent version 1 of the product delivery in order to meet regulatory requirements, such as Figure 3 As shown by the oval in .

[0042] In one embodiment of the present application, configuring work items includes: configuring custom fields and work item types for each work item, wherein the custom fields include: field identifiers, Chinese names displayed by the fields, and field data types; defining all states and all executable actions for each work item, and establishing a mapping relationship between states and actions.

[0043] It is understandable that for each work item, customized fields are required for the information that needs to be displayed and pre-filled. Customized fields include field ID, Chinese name displayed by the field, and field data type. The field ID is unique and needs to be called in various situations such as form layout. Field data types include character type, text type, rich text type, enumeration type, and other custom types. Among them, the enumeration type needs to configure the work item to which the enumeration field belongs and enumerate all possible values ​​of the field. By customizing the import and export template containing these fields, the customization process needs to select the corresponding required fields that have been created to adjust the order. For text and table type work items, such as requirement documents, test cases, etc., they can be imported into the system through the aforementioned templates. For software models, it is necessary to install plug-ins through Simulink, select the required associated model, and import it into the project management system.

[0044] Define all states and all executable actions of the work item, and establish a mapping relationship between states and actions. In the actual execution process, click New to display the draft, click Submit to automatically update the document to Under Review, and click Approved to update the document to Approved. All states from New Draft to Under Review to Approved are triggered by different actions performed by different people. For example, the creator of the work item creates a new draft, which automatically changes to Under Review after the creator submits it, and the relevant approvers receive the work item and choose to agree or return it, which changes with the state of the work item.

[0045] In addition, the work item types in the embodiment of the present application are as follows: Figure 4 As shown, it includes requirement management, test cases, system models, defect management, change management and others. In the actual implementation process, the requirement manager uploads different requirement documents, the software developer imports the software models of different functional modules, and the tester imports several test cases corresponding to each function and automatically executes the test. The uploaded content will have corresponding entries in the work items to which they belong. If the work items fail the test, defects will be automatically created. These defects need to be handled by the corresponding developers to decide whether to change the software or change the requirements. Due to the establishment of the traceability relationship, the relevant work items that have been changed can be automatically marked to remind the corresponding relevant personnel.

[0046] In one embodiment of the present application, establishing a hierarchical relationship between each work item includes: configuring the relationship type between each work item; and establishing a hierarchical relationship between each work item according to the field identifier of each work item and the relationship type between each work item.

[0047] The embodiments of this application must first clarify the possible relationships between different types of work items. Common relationship types include, but are not limited to, parent-child relationships, associated relationships, etc. By configuring the relationship type between each work item and establishing a hierarchical relationship based on field identifiers, various tasks and documents in complex projects can be better organized and managed, thereby improving work efficiency. By associating work items and embedding the change impact analysis in the change process, refined management of change objects is achieved, and the system is fully managed in the online process domain. By configuring reports, multiple styles of display and analysis views to improve the transparency of project management, project managers can grasp the project progress in real time to support the full business tool chain of software development, from products to software, and then from software to products, to achieve an end-to-end closed loop of the R&D process and build a complete value ecosystem.

[0048] In one embodiment of the present application, a traceability relationship between each work item is established, including: creating upstream traceability and downstream traceability for each work item; creating a traceability relationship between each work item based on the upstream traceability and downstream traceability, wherein the traceability relationship is used to update the status of all associated work items according to the traceability relationship of the target work item when the target work item changes.

[0049] In the embodiment of the present application, to create a traceability relationship, first configure the relationship type between different types of documents, such as Figure 5 As shown. Create links for specific individual documents and other documents. If there are changes between documents with traceability relationships, upstream and downstream related documents will be reminded as prompts. You can create a small program through the dashboard to display the traceability relationship, clearly showing which sub-requirements, related models, use cases, etc. are under the requirements, ensuring that nothing is missed.

[0050] Specifically, the embodiment of the present application can identify all upstream work items that have a direct impact on the current work item, configure an upstream traceability relationship for each work item, and ensure that the current work item can be traced back to its source. For example, a design document can be traced back to the requirements document on which it is based. Secondly, identify all downstream work items affected by the current work item. Configure downstream traceability relationships for each work item to ensure that the subsequent impact can be traced from the current work item. For example, a design document can be traced to the code implementation and test cases it guides. When any upstream work item (such as a requirements document) changes, the system will automatically notify all associated downstream work items (such as design documents, code implementations, test cases), and update their status to "pending review", ensuring that all relevant parties understand the impact of the change and take necessary actions. Thus, not only the transparency and controllability of the project are improved, but also the consistency and coherence between all work items are ensured, which helps to improve overall development efficiency and product quality.

[0051] Combine the following Figure 6 The specific process of configuring work items is described in detail. First, clarify the different types of work items (such as requirements, tasks, defects, etc.) and define their basic properties for each type. Define specific fields for each work item type, which can include name, description, status, priority, etc., to record the information of each work item in detail. Second, create an enumeration menu, which is usually used to select a specific type of value. For example, the status field may have options such as "New", "In Progress", and "Completed". Third, design a form interface for entering and displaying work item information. This step ensures that users can easily create and edit work items. Fourth, define the processing flow of work items, including various stages from creation to completion. Workflows can help automate certain tasks and ensure that work items are processed according to predetermined steps. Fifth, create templates for batch import or export of work item data. This helps to quickly manage and update the information of a large number of work items. Sixth, configure the relationship between different work items to ensure that work items can be related to each other. Seventh, establish a traceability relationship between each work item to ensure that when a work item changes, all related work items can also be updated in time.

[0052] In step S103, the software project is constrained according to the set corresponding to the work items of each phase, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with the standardized management specifications.

[0053] According to the configuration method of the software project proposed in the embodiment of the present application, the work items of each stage of the software project are obtained, and a special collection is created for the work items of each development stage to organize all relevant documents generated in each stage, ensure the centralized management of information, and establish the traceability relationship and hierarchical relationship between each work item to ensure that any changes can be reflected in the upstream and downstream related documents in a timely manner. Thus, the traceability relationship, hierarchical relationship and collection are used to constrain the entire project to ensure that it complies with the established management specifications, thereby meeting the requirements of the automotive software process improvement and capability assessment standards and improving the compliance and quality of the project.

[0054] Next, a configuration device for a software project according to an embodiment of the present application will be described with reference to the accompanying drawings.

[0055] Figure 7 It is a block diagram of a configuration device for a software project in an embodiment of the present application.

[0056] like Figure 7 As shown, the configuration device 10 of the software project includes: an acquisition module 100 , a processing module 200 and a constraint module 300 .

[0057] Among them, the acquisition module 100 is used to obtain the work items of each stage of the software project; the processing module 200 is used to create a collection corresponding to the work items of each stage and configure the work items, and establish a traceability relationship and a hierarchical relationship between each work item based on the configured work items; the constraint module 300 is used to constrain the software project according to the collection corresponding to the work items of each stage, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with standardized management specifications.

[0058] In one embodiment of the present application, the processing module 200 is further used to: configure custom fields and work item types for each work item, where the custom fields include: field identifier, Chinese name displayed by the field, and field data type; define all states and all executable actions of each work item, and establish a mapping relationship between states and actions.

[0059] In one embodiment of the present application, the processing module 200 is further used to: configure the relationship type between each work item; and establish a hierarchical relationship between each work item according to the field identifier of each work item and the relationship type between each work item.

[0060] In one embodiment of the present application, the processing module 200 is further used to: create upstream traceability and downstream traceability for each work item; create a traceability relationship between each work item based on the upstream traceability and downstream traceability, wherein the traceability relationship is used to update the status of all associated work items according to the traceability relationship of the target work item when the target work item changes.

[0061] In one embodiment of the present application, if the work tasks of the current stage are completed, the collection corresponding to the work items of the current stage is closed, the files contained in the collection of the current stage are regarded as the baseline, and the collection corresponding to the work items of the next stage references the baseline, wherein the baseline is frozen in the collection corresponding to the work items of the next stage.

[0062] In one embodiment of the present application, a collection is used to organize output documents of different stages and supports collection version control and user authority management.

[0063] It should be noted that the above explanation of the embodiment of the method for configuring a software project is also applicable to the configuration device for a software project of this embodiment, and will not be repeated here.

[0064] According to the configuration device of the software project proposed in the embodiment of the present application, the work items of each stage of the software project are obtained, and a special collection is created for the work of each development stage to organize all relevant documents generated in each stage, ensure the centralized management of information, and establish the traceability relationship and hierarchical relationship between each work item to ensure that any changes can be reflected in the upstream and downstream related documents in a timely manner. Thus, the traceability relationship, hierarchical relationship and collection are used to constrain the entire project to ensure that it complies with the established management specifications, thereby meeting the requirements of the automotive software process improvement and capability assessment standards and improving the compliance and quality of the project.

[0065] Figure 8 A schematic diagram of the structure of a server provided in an embodiment of the present application. The server may include:

[0066] A memory 801 , a processor 802 , and a computer program stored in the memory 801 and executable on the processor 802 .

[0067] When the processor 802 executes the program, the configuration method of the software project provided in the above embodiment is implemented.

[0068] Furthermore, the server also includes:

[0069] The communication interface 803 is used for communication between the memory 801 and the processor 802 .

[0070] The memory 801 is used to store computer programs that can be executed on the processor 802 .

[0071] The memory 801 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0072] If the memory 801, the processor 802 and the communication interface 803 are implemented independently, the communication interface 803, the memory 801 and the processor 802 can be connected to each other through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 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.

[0073] Optionally, in a specific implementation, if the memory 801, the processor 802 and the communication interface 803 are integrated on a chip, the memory 801, the processor 802 and the communication interface 803 can communicate with each other through an internal interface.

[0074] The processor 802 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0075] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the configuration method of the software project as described above is implemented.

[0076] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. 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 application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0077] 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 technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0078] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0079] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0080] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0081] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for configuring a software project, characterized in that: The following steps are involved: Get work items at each stage of the software project; Creating a collection corresponding to the work items of each stage and configuring the work items, and establishing a traceability relationship and a hierarchical relationship between each work item according to the configured work items; The software project is constrained according to the set corresponding to the work items of each stage, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with standardized management specifications.

2. The method for configuring a software project according to claim 1, characterized in that: The configuring the work item includes: Configure custom fields and work item types for each work item, wherein the custom fields include: field identifiers, Chinese names displayed for the fields, and field data types; All states and all executable actions of each work item are defined, and a mapping relationship between states and actions is established.

3. The method for configuring a software project according to claim 2, characterized in that: Said Establish a hierarchical relationship between each work item, including: Configure the relationship type between each of the work items; A hierarchical relationship between each of the work items is established according to the field identifier of each of the work items and the relationship type between each of the work items.

4. The method for configuring a software project according to claim 2, characterized in that: The establishing of the traceability relationship between each of the work items includes: Create upstream traceability and downstream traceability for each of the work items; A traceability relationship between each of the work items is created according to the upstream traceability and the downstream traceability, wherein the traceability relationship is used to update the status of all associated work items according to the traceability relationship of the target work item when a target work item is changed.

5. The method for configuring a software project according to claim 1, characterized in that: If the development tasks of the current stage are completed, the collection corresponding to the work items of the current stage is closed, and the collection of the current stage and the files contained therein are regarded as the baseline. The collection corresponding to the development work items of the next stage references the baseline, wherein the baseline is frozen in the collection corresponding to the work items of the next stage.

6. The method for configuring a software project according to claim 1 or 5, characterized in that: The collection is used to organize output documents at different stages and supports collection version control and user authority management.

7. A configuration device for a software project, characterized in that: include: The acquisition module is used to obtain work items at each stage of the software project; A processing module, used to create a set corresponding to the work items of each stage and configure the work items, and establish a traceability relationship and a hierarchical relationship between each work item according to the configured work items; The constraint module is used to constrain the software project according to the set corresponding to the work items of each stage, the traceability relationship and the hierarchical relationship between the work items, so that the software project complies with standardized management specifications.

8. The software project configuration device according to claim 7, characterized in that: The processing module is further configured to: Configure custom fields and work item types for each work item, wherein the custom fields include: field identifiers, Chinese names displayed for the fields, and field data types; All states and all executable actions of each work item are defined, and a mapping relationship between states and actions is established.

9. A server, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method for configuring a software project according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the configuration method of the software project described in any one of claims 1 to 6 is implemented.

Images