An item-based demand configuration control method

Abstract

The present invention relates to the technical field of demand management, and specifically to an item-based demand configuration control method. The use of an item-based approach to compile requirements can greatly improve the granularity of demand management, while the item-based approach indirectly promotes the completeness, clarity, and accuracy of the demand description. By assigning the attribute "applicable configuration" to the requirement item, it is possible to manage the requirements of multiple configurations in the same requirement module, effectively manage the capability differences of different configurations, assist in the reuse of demand-based design implementation and verification, assist in the analysis of the impact of demand changes, and improve the efficiency and quality of model development; by establishing a difference identifier for similar requirements, it can fully reflect the differences between similar requirements of configurations, and further improve the management of configuration capability differences; by customizing the view, it is convenient to view the complete requirements of a certain configuration; by identifying the configuration adapted to the baseline in the baseline, the configuration management of the configuration can be clear and controllable.

Description

Technical Field

[0001] The present invention relates to the technical field of demand management, and in particular to an item-based demand configuration control method. Background Art

[0002] Currently, with the rapid development of technology and the segmentation of user needs, the number of sub-configurations of the same model continues to increase, leading to more and more model requirements and more frequent changes in requirements. In addition, the gradual shortening of model release cycles has led to increasingly serious model development progress and quality issues, placing tremendous pressure on configuration control. How to effectively manage the requirements of different configurations, distinguish the capability differences between different configurations, increase the demand-based reuse between configurations, and improve the quality of demand change impact analysis, thereby improving model development efficiency and quality, has become a pressing issue.

[0003] Regarding demand configuration control, the most advanced solutions in the industry are:

[0004] 1. Prepare requirements in itemized form and manage them using a requirements management system;

[0005] 2. Each configuration is managed independently. The same model can be derived from the configuration by copying the content of the basic configuration and making additions, deletions, and modifications based on it.

[0006] Current industry solutions manage each configuration independently, making it difficult to distinguish the capabilities of different configurations, including inherited requirements, additions, and deletions. In particular, it's impossible to compare similar requirements across configurations, and to reflect the differences between similar requirements (i.e., requirements described in the same point but with different details, such as differences in the functional performance indicators of a specific requirement) across different configurations. This makes it impossible to implement requirement-based reuse and conduct a unified impact analysis of requirement changes across configurations. Each configuration must independently modify requirements, develop, test, and verify, resulting in a significant amount of duplicated work and impacting the progress and efficiency of model development. Summary of the Invention

[0007] Purpose of the invention: The technical problem to be solved by the present invention is to provide a configuration control technology based on requirement items, which can distinguish the capability differences of different configurations, improve the reuse efficiency of different configurations and the quality of change impact analysis, thereby improving the efficiency and quality of model research and development.

[0008] The technical solution of the present invention is a method for controlling item-based demand configuration, comprising the following steps:

[0009] Step 1: Select a demand management system, establish a demand directory structure in the system according to the hierarchical framework of model requirements, and establish a demand module for model requirements in each directory structure;

[0010] Step 2: Create the attribute "Applicable Configuration" of the requirement item in the requirement module, and the attribute enumeration value contains known configurations;

[0011] Step 3: Write requirements in the requirements module in an itemized manner, with each item describing only one requirement point;

[0012] Step 4: The "applicable configuration" of each requirement item in the requirement module is marked as the initial configuration adapted by the requirement module;

[0013] Step 5: Construct derived configuration requirements based on the existing requirement items in the requirement module:

[0014] 1) If an existing requirement item is applicable to a derived configuration, select the derived configuration in the "Applicable Configuration" attribute of the requirement item;

[0015] 2) If an existing requirement item is completely inapplicable to a derived configuration, add a new requirement item in the requirement module and select only the derived configuration in the "Applicable Configuration" attribute;

[0016] 3) If there are similar requirements differences between existing requirements and derived configurations, the following methods can be used to identify them:

[0017] a) Customize the copy operation to copy an existing requirement item to generate a derived configuration requirement item. The copy process automatically identifies and records the relationship between similar requirements of the two. The "applicable configuration" of the derived configuration requirement item only identifies the derived configuration;

[0018] b) Manually create a new derived configuration requirement item and establish a link between the derived configuration requirement item and the existing requirement item to identify and record that the two requirement items belong to the same type of requirements. The "applicable configuration" attribute value of the derived configuration requirement item only identifies the derived configuration.

[0019] Step 6: Filter the "Applicable Configuration" attribute value of the requirement item in the requirement module and customize the view of different configurations;

[0020] Step 7: Conduct item-based demand configuration control:

[0021] 1) Select a view of a certain configuration to view the complete requirements of the configuration and conduct design, development and verification accordingly;

[0022] 2) Carry out configuration management: When establishing a baseline for a configuration in the requirements module, identify the configuration corresponding to the baseline in the baseline name or description. When viewing, publishing, or comparing baselines, select the baseline and filter the configuration containing the baseline identifier in the "Applicable Configuration" attribute value. This is the configuration baseline content;

[0023] 3) Retrieve and publish capability differences of different configurations: If the "applicable configuration" attribute value of a requirement item identifies different configurations at the same time, it means the capability of each configuration is the same; if the "applicable configuration" attribute value of a requirement item only identifies a certain configuration and there is no similar requirement relationship, it means non-similar capability difference; if the "applicable configuration" attribute value only identifies a certain configuration and there is a similar requirement relationship, it means similar capability difference;

[0024] 4) Develop demand-based reuse: For capabilities that are the same across configurations or have similar capabilities, existing design implementation and verification of the requirements can be reused to improve R&D efficiency.

[0025] 5) Conduct impact analysis of requirement changes: When requirements change, determine the affected configurations based on the "applicable configurations" of the changed requirement items, analyze the impacts and take corresponding measures to avoid quality problems caused by inadequate change impact analysis.

[0026] Furthermore, it also includes step eight, repeating steps five to seven when adding a new derivative configuration, and building requirements for all configurations of the same model in the existing requirement module.

[0027] Furthermore, in step eight, if the existing requirement directory structure and modules cannot adapt to the new configuration when adding a new derivative configuration, repeat steps one to four to build the requirements of the new configuration;

[0028] Furthermore, in step 1, the requirement catalog structure can be dynamically adjusted according to changes in the model requirement hierarchy framework;

[0029] Furthermore, in step 2, when a new configuration is subsequently added, a corresponding new configuration is added to the "applicable configuration" enumeration value to dynamically adapt to the new configuration control;

[0030] Furthermore, in step three, the itemized requirements include functionality, performance, data processing, interfaces, security, reliability, design constraints, quality, and schedule. Each requirement should be described in separate paragraphs to reflect the detailed differences in the comprehensive capabilities of each configuration.

[0031] Furthermore, in step 5 3), the method of identifying the differences between similar requirements is not limited to the two given methods, and any method that can establish identification of similar requirements is applicable;

[0032] Furthermore, in step 6, the filtering method used in customizing the view of a certain configuration is to filter the requirement entries whose "applicable configuration" attribute value in the requirement module contains the configuration;

[0033] Furthermore, in step 7 (5), if the change of the requirement item causes a change in its applicable configuration, the applicable configuration of the requirement item needs to be re-identified.

[0034] Beneficial effects of the present invention:

[0035] In the above solution, the itemized approach of compiling requirements can greatly improve the granularity of demand management. At the same time, the itemized approach indirectly promotes the completeness, clarity, and accuracy of the demand description.

[0036] Assigning the attribute "applicable configuration" to the requirement items enables the management of requirements of multiple configurations in the same requirement module, which can effectively manage the capability differences of different configurations, assist in the reuse of requirement-based design implementation and verification, assist in the analysis of the impact of requirement changes, and improve the efficiency and quality of model development; by establishing difference identification for similar requirements, the differences between similar requirements between configurations can be fully reflected, and the management of configuration capability differences can be further improved; through customized views, the complete requirements of a certain configuration can be easily viewed; by identifying the configuration that the baseline adapts to in the baseline, the configuration management of the configuration can be clear and controllable.

[0037] This method can also be extended to other areas of requirements engineering, such as the status management of requirements items. By assigning the "requirement status" attribute to requirement items, the status of requirement analysis, design, implementation, and verification can be effectively controlled, and the progress and quality of requirement development can be managed. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram of requirement items and attributes;

[0039] Figure 2 To establish a schematic diagram of the difference identification of similar requirements based on copying;

[0040] Figure 3 A schematic diagram for identifying differences between similar requirements is established in a link-based manner. DETAILED DESCRIPTION

[0041] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0042] Item-based demand configuration control method:

[0043] 1) Select a demand management system that supports itemized management, such as DOORS, establish a demand directory structure according to the product decomposition structure of the model, and establish corresponding product development demand modules in each level of the directory.

[0044] 2) Each product development requirement module uniformly establishes the requirement item attribute "applicable configuration". The attribute is defined as an enumeration item or multiple options. The attribute enumeration value contains the names of different known configurations of the model;

[0045] 3) Prepare requirements in the corresponding requirement module according to the principle that each item only describes a single requirement point;

[0046] 4) In the "Applicable Configuration" of the requirement item in each product development requirement module, select the initial adapted configuration from the enumeration value;

[0047] 5) Build derived configuration requirements based on existing requirements:

[0048] (1) For each requirement item in the product development requirement module, if it is applicable to the derived configuration, directly select the new configuration in the "Applicable Configuration" attribute of the item;

[0049] (2) For the requirement items in each product development requirement module, if the requirement items of the derived configuration are completely different from the existing requirement items, a new requirement item is added to the module, the requirement item of the derived configuration is written, and its "applicable configuration" attribute value is marked as the new configuration;

[0050] (3) For the existing requirement items in each product development requirement module, if there are similar requirement differences between the derived configuration requirements and the existing requirement items, any of the following methods can be used to identify them:

[0051] a) Customize the method of generating new configurations in the selected demand management system:

[0052] a.1 For each product development requirement module, add the attribute "Generate New Configuration", and the attribute enumeration value includes derived configuration;

[0053] a.2 Select the requirement item for which you want to generate a derived configuration based on the base configuration, and set the "Generate New Configuration" attribute value of the item to Derived Configuration;

[0054] a.3 Click the Generate New Configuration operation customized in the Demand Management System;

[0055] a.4 The demand management system automatically copies the basic configuration item, pastes the derived configuration item below it, and automatically sets the "Applicable Configuration" attribute value of the newly generated item to the derived configuration. At the same time, it clears the "Generate New Configuration" attribute value of the basic configuration item and automatically records the similar demand relationship between the two items.

[0056] b) Establish similar demand relationships based on links:

[0057] b.1 Create a new derived configuration entry below the basic configuration requirement entry, edit the entry content, and mark the "Applicable Configuration" attribute value as derived configuration;

[0058] b.2 Establish a similar requirement link relationship from the derived configuration item to the basic configuration item.

[0059] 6) In the demand management system, develop views of different configurations and corresponding filtering methods for the views as follows:

[0060] For example, if you specify the A configuration view:

[0061] A configuration view content = {R1, R2...Rn}

[0062] Ri = requirement item in the product development requirement module, i = 1…n

[0063] Ri's

[0064] 7) Carry out item-based demand configuration control:

[0065] (1) View the complete configuration requirements

[0066] Select the view of the configuration you want to view. The requirements management system will automatically filter the requirements items of the product development requirements module according to the view's filtering method and present the filtered results, which are the complete requirements of the selected configuration.

[0067] (2) Carry out configuration management

[0068] When a configuration needs to be published and a baseline is established, a baseline is established for the entire requirement module. The configuration that the baseline is adapted to is noted in the baseline notes using the format of -match-configuration name. After selecting a baseline in the customized system operation, the system automatically applies the configuration in the baseline notes to filter the "Applicable Configuration" attribute and presents the baseline content of the filtered configuration.

[0069] (3) Differences in the ability to retrieve and publish different configurations

[0070] The demand management system uses the following methods to determine the capability differences of different configurations and present the results:

[0071] i. If the "Applicable Configuration" attribute value of a requirement item identifies different configurations at the same time, it means that the capability is the same for all configurations;

[0072] ii. If the "applicable configuration" attribute value of a requirement item only identifies a certain configuration and there is no similar requirement relationship, it is a non-similar capability difference;

[0073] iii. If the "Applicable Configuration" attribute value only identifies a certain configuration and there is a similar demand relationship, it is a similar capability difference;

[0074] (4) Carry out requirement-level reuse: For the same capabilities of each configuration and the differences in similar capabilities, the existing design implementation and verification of the reuse requirement items can be referred to improve R&D efficiency;

[0075] (5) Conduct impact analysis of requirement changes: When requirements change, determine whether there are other configurations affected based on the "applicable configurations" of the changed requirement item to avoid quality problems caused by inadequate change impact analysis.

[0076] Examples:

[0077] 1) Define an organizational-level requirement module template in the requirement management system. Define the item attribute "Applicable Configuration" and the attribute enumeration value in the template. Add the A configuration to the attribute enumeration value. Define the A configuration view in the template. The filtering condition is that the "Applicable Configuration" attribute value of the item contains the A configuration. Define the item attribute "Generate New Configuration" in the template. The attribute enumeration value is temporarily empty.

[0078] 2) Based on the model product decomposition structure, establish a product hierarchy catalog and product development requirement modules in the demand management system. The modules reference the "applicable configuration" attributes and views in the organization-level requirement module template;

[0079] 3) In each product development requirement module, the product development requirements of the basic configuration are compiled in an itemized manner, and the "applicable configuration" attribute value of the requirement items are all marked as A configuration;

[0080] 4) Build the requirements of configuration B based on configuration A:

[0081] a) The "Applicable Configuration" attribute enumeration value of the organizational requirement module template has been added with the B configuration, and this has been synchronized to each product development requirement module; a new B configuration view has been added to the organizational requirement module template, with the filtering condition being that the "Applicable Configuration" attribute value of the item contains the B configuration, and this has been synchronized to each product development requirement module; the "Generate New Configuration" attribute enumeration value of the organizational requirement module template has been added with the B configuration;

[0082] b) Inherit the A configuration entry: select B configuration in the "Applicable configuration" attribute value of the entry

[0083] c) Newly added entries with different capabilities: Normally added entries, the “Applicable Configuration” attribute value is marked as B configuration;

[0084] d) Add a new similar requirement item: mark the "Generate New Configuration" attribute enumeration value of the corresponding item as Configuration B, select the "Generate New Configuration" menu bar button of the requirement management system, and the requirement management system will automatically copy and paste the new item below the original item. The "Generate New Configuration" attribute value of the original item will be cleared, and the "Applicable Configuration" of the new item will be marked as Configuration B; at the same time, the background of the requirement management system will record the similar requirement relationship between the two items.

[0085] 5) Carry out item-based demand configuration control

[0086] a) View the complete requirements of the configuration: Select the corresponding configuration view, and the requirements management system will automatically filter according to the view filter conditions to present the complete requirements of the selected configuration;

[0087] b) Manage and control capability differences between different configurations: When the B configuration requirement module is submitted for release, the requirement management system automatically generates the same capability items, non-similar capability differences, and similar capability differences between configuration B and configuration A based on the defined capability difference comparison method, combined with the "applicable configuration" attribute and similar requirement relationships. The results are presented to the person in charge of configuration B, who confirms them before submitting them for release.

[0088] c) Conduct change impact analysis: The product development requirement change process is strongly integrated with the requirement module in the requirement management system. When changing the B configuration item, the requirement module to be changed and the corresponding item in the module are selected in the change process. If it is detected that the item "applicable configuration" is also applicable to A configuration, the process will automatically flow to the person in charge of A configuration for confirmation to confirm whether A configuration has been changed.

[0089] 1) Requirements are compiled in an itemized manner, with each requirement item being assigned the attribute of "applicable configuration." This attribute allows a requirement module to adapt to multiple configurations, and quantitatively identifies the same requirements across different configurations. This solves the problems of difficulty in reusing requirements across configurations and analyzing the impact of requirement changes. It can assist in requirement-based reuse across configurations and assist in change impact analysis, achieving industry-leading standards.

[0090] 2) By obtaining customized copy operations or establishing links to identify similar requirements of different configurations and assigning the "applicable configuration" attribute to requirement items, the system identifies the same requirements, different requirements, and similar but different requirements of different configurations. This solves the problem of difficulty in specifying the differences between different configurations and enables automatic analysis of capability differences between different configurations, reaching a leading level in China.

[0091] The above description is merely a detailed description of specific embodiments of the present invention. Any unspecified portions are conventional techniques. However, the scope of the present invention is not limited thereto. Any changes or substitutions that can be readily conceived by a person skilled in the art within the technical scope disclosed in the present invention are intended to be encompassed within the scope of the present invention. The scope of the present invention shall be determined by the scope of the claims.

Claims

1. A method for controlling demand configuration based on items, characterized in that: The steps include: Step 1: Select a demand management system, establish a demand directory structure in the system according to the hierarchical framework of model requirements, and establish a demand module for model requirements in each directory structure; Step 2: Create the attribute "Applicable Configuration" of the requirement item in the requirement module. The attribute enumeration value contains known configurations. Step 3: Write requirements in the requirements module in an itemized manner, with each item describing only one requirement point; Step 4: The "applicable configuration" of each requirement item in the requirement module is marked as the initial configuration adapted by the requirement module; Step 5: Construct derived configuration requirements based on the existing requirement items in the requirement module: Step 5 is as follows: 1) If an existing requirement item is applicable to a derived configuration, select the derived configuration in the "Applicable Configuration" attribute of the requirement item; 2) If an existing requirement item is completely inapplicable to a derived configuration, add a new requirement item in the requirements module and select only the derived configuration in the "Applicable Configuration" attribute; 3) If there are similar requirements differences between existing requirements and derived configurations, the following method shall be used to identify them: a) Customize the copy operation to copy an existing requirement item to generate a derived configuration requirement item. The copy process automatically identifies and records the relationship between similar requirements. The "Applicable Configuration" of the derived configuration requirement item only identifies the derived configuration. b) Manually create a new derived configuration requirement item and link it to an existing requirement item to indicate and record that the two requirement items belong to the same category. The "Applicable Configuration" attribute value of the derived configuration requirement item only identifies the derived configuration. Step 6: Filter the "Applicable Configuration" attribute value of the requirement item in the requirement module and customize the view of different configurations; Step 7: Conduct item-based demand configuration control.

2. The item-based demand configuration control method according to claim 1, characterized in that: It also includes step eight, repeating steps five to seven when adding a new derivative configuration, and building requirements for all configurations of the same model in the existing requirement module.

3. The item-based demand configuration control method according to claim 2, characterized in that: In step eight, if the existing requirement directory structure and modules cannot adapt to the new configuration when a new derivative configuration is added, repeat steps one to four to build the requirements of the new configuration.

4. The item-based demand configuration control method according to claim 1, characterized in that: In the step 1, the requirement directory structure can be dynamically adjusted according to the changes in the model requirement hierarchy framework.

5. The item-based demand configuration control method according to claim 1, characterized in that: In step 2, when a new configuration is added subsequently, a corresponding new configuration is added in the "applicable configuration" enumeration value to dynamically adapt to the new configuration control.

6. The item-based demand configuration control method according to claim 1, characterized in that: In step three, the itemized description of requirements includes functions, performance, data processing, interfaces, security, reliability, design constraints, quality, and progress. Each requirement is described in separate paragraphs to reflect the detailed differences in the all-round capabilities of each configuration.

7. The item-based demand configuration control method according to claim 1, characterized in that: In step 3) of step 5, the method for identifying the differences between similar requirements is not limited to the two given methods, and any method that can establish identification of similar requirements is applicable.

8. The item-based demand configuration control method according to claim 1, characterized in that: The sixth step is to customize the filtering method used in the view of a certain configuration, that is, to filter the requirement entries whose "applicable configuration" attribute value in the requirement module includes the configuration.

9. The item-based demand configuration control method according to claim 1, characterized in that: The step seven is specifically as follows: 1) Select a view of a certain configuration to view the complete requirements of the configuration and conduct design, development and verification; 2) Conduct configuration management: When establishing a baseline for a configuration in the requirements module, identify the configuration corresponding to the baseline in the baseline name or description. When subsequently viewing, publishing, or comparing baselines, select the baseline and filter for configurations containing the baseline identifier in the "Applicable Configuration" attribute value. This is the configuration baseline content. 3) Retrieve and publish capability differences between different configurations: If the "Applicable Configuration" attribute value of a requirement item identifies different configurations at the same time, it means that the capability is the same for all configurations. If the "Applicable Configuration" attribute value of a requirement item only identifies a certain configuration and there is no similar requirement relationship, it means that the capability is not similar. If the "Applicable Configuration" attribute value only identifies a certain configuration and there is a similar requirement relationship, it means that the capability is similar. 4) Develop demand-based reuse: For capabilities that are the same across configurations or differences in similar capabilities, reuse existing design implementations and verifications for the requirements to improve R&D efficiency. 5) Conduct impact analysis of requirement changes: When requirements change, determine the affected configurations based on the "applicable configurations" of the changed requirement item, analyze the impact, and take appropriate measures to avoid quality issues caused by inadequate change impact analysis. If the changed requirement item causes its applicable configuration to change, the applicable configuration of the requirement item needs to be re-identified.

Images