CN112381370A

CN112381370A - Demand distribution automation method based on DOORS system

Info

Publication number: CN112381370A
Application number: CN202011209969.1A
Authority: CN
Inventors: 曾加刚; 杨艳歌
Original assignee: China Helicopter Research and Development Institute
Current assignee: China Helicopter Research and Development Institute
Priority date: 2020-11-03
Filing date: 2020-11-03
Publication date: 2021-02-19

Abstract

The invention belongs to the technical field of demand engineering, and discloses a demand distribution automation method based on a DOORS (data object oriented system), which is used for realizing automation of demand distribution and receiving processes, reducing the complexity of manual operation and avoiding the omission of manual operation of demand distribution through the check of demand distribution. The automatic establishment of the demand distribution link relation is realized, so that the demand needs to be rapidly transferred layer by layer downwards from the user, and the tracing of the demand is facilitated.

Description

Demand distribution automation method based on DOORS system

Technical Field

The invention belongs to the technical field of demand engineering, and particularly relates to a demand distribution automation method based on a DOORS system.

Background

With the development of industrial technology in China, the development of the model of the civil military aircraft in China is applying a development method based on system engineering. The demand engineering is the category of system engineering, and model development and implementation demand engineering is to implement a demand-based development process, take demand distribution and transmission as a main line and take demands of various levels as a basis to develop product development work. The tracing relation of the requirements is established through the distribution of the requirements, and the formed requirements of each level are all based on the requirements of users, so that the product development can comprehensively meet the users, and the risk of model development is reduced.

Model requirements are typically divided into system levels, with each level of system requirements being distributed down layer by layer. The system requirement of each level is allocated from the upper level, the self requirement definition is carried out in the level, and the requirement is allocated to the lower level after the requirement definition is finished. The original demand allocation method is mainly based on manual allocation of a demand management system, demand engineers manually create demand allocation links, and allocation of demands to the next level is performed. The demand for allocation by the next level is also received by means of manual copying. With the increase of the data volume of the demand items, the method has the problems that the demand distribution link is complex in creating operation and low in efficiency, and the omission is easy to occur in the distribution and the receiving of the demand.

Disclosure of Invention

The invention provides a demand distribution automation method based on a DOORS (data object oriented operating system), which is used for realizing the automation of demand distribution and receiving processes, reducing the complexity of manual operation and avoiding the omission of manual operation of demand distribution through the inspection of the demand distribution; the automatic establishment of the demand distribution link relation is realized, so that the demand needs to be rapidly transferred layer by layer downwards from the user, and the tracing of the demand is facilitated.

In order to achieve the purpose, the invention adopts the following technical scheme to realize the purpose:

a DOORS system based demand assignment automation method, the method comprising:

s1, defining a plurality of requirement items of a certain level in the DOORS system, wherein the requirement items are recorded in a formal distribution module under the level, and the attribute of each requirement item is completely supplemented; each requirement item has at least an "assignment" attribute; the "assign" attribute is used to characterize the name of the next hierarchical system to which the corresponding demand item may be assigned;

s2, selecting the names of a plurality of next-level systems to which the requirement item is distributed on the distribution attribute of each requirement item;

s3, according to the setting of the distribution attribute, distributing each demand item to a plurality of corresponding next-level systems;

s4, automatically creating formal receiving modules in a plurality of corresponding next-level systems in the DOORS system respectively, wherein the formal receiving modules are used for recording a plurality of distributed requirement items;

s5, receiving a plurality of distributed requirement items by a plurality of corresponding next-level systems in the DOORS system respectively;

and S6, establishing a link between the formal distribution module and the formal receiving module.

The technical scheme of the invention has the characteristics and further improvements that:

(1) after S2, and before S3, the method further includes selecting a demand baseline version to allocate.

(2) S1 specifically includes:

firstly, automatically acquiring a system name of a certain level, wherein the system name represents the level of a current model project system;

judging whether a lower system exists in a certain level, if no lower system exists in the certain level, the 'distribution' attribute is null;

otherwise, checking whether the attribute of each requirement item 'distribution' is defined.

(3) In the process of checking whether each requirement item 'distribution' attribute is defined:

if a certain requirement item is a catalogue, the attribute of 'distribution' cannot be set for the requirement item; otherwise, an "assign" attribute is defined for the item of requirements.

(4) Prior to S1, the method further comprises:

defining a global model project requirement hierarchical architecture array in a DOORS system;

a template of the requirement entry is defined.

(5) When the demand items are well defined for demand allocation, a demand baseline needs to be added first.

(6) In S3, each requirement entry is allocated to a corresponding plurality of next-level systems, specifically:

firstly, distributing the demand items to a specific project system according to the distribution attribute of the formal distribution module;

secondly, selecting 'demand is distributed to the system', and after the demand items are distributed to the system successfully, the demand receiving operation can be carried out in the specific project system.

(7) In the process of repeatedly selecting the 'demand is distributed to the system' operation, the next-level system can also perform a demand receiving operation.

The demand allocation automation method provided by the invention is simple to realize and convenient to deploy, and can be integrated into a DOORS system interface to provide an interactive operation menu. The method provides an automatic means for the distribution of the internal model requirements of the enterprise, and enables the requirement distribution process to be standardized, standardized and unified. The model demand is rapidly transmitted layer by layer from the user demand, the demand distribution work efficiency is improved, the omission of demand distribution is reduced, and the tracing of the demand is facilitated. The demand distribution automation method provided by the invention is mainly based on a demand management system, realizes the automatic distribution and receiving of demands from the upper level to the lower level according to the demand information level defined by a demand information architecture, and automatically establishes a demand link relation in the distribution and receiving processes, so that the demand distribution process is normalized, standardized and unified. Therefore, the problems of complex operation, distribution omission, low efficiency and the like in the demand distribution process are reduced, and meanwhile, the whole demand distribution process is effectively managed, so that the demand tracking is more efficient and convenient.

Drawings

Fig. 1 is a schematic flow chart of a demand allocation automation method based on a DOORS system according to an embodiment of the present invention.

Detailed Description

The invention provides a demand distribution automation method based on a DOORS (data object oriented operating system), which is used for realizing automation of demand distribution and receiving processes, reducing the complexity of manual operation and avoiding omission of manual operation of demand distribution through checking the demand distribution. The automatic establishment of the demand distribution link relation is realized, so that the demand needs to be rapidly transferred layer by layer downwards from the user, and the tracing of the demand is facilitated.

As shown in fig. 1, an embodiment of the present invention provides a demand assignment automation method based on a DOORS system, including the following steps:

(1) and completing requirement item definition of a certain level in the DOORS system, completing the attribute supplement of each requirement, and marking a baseline.

(2) A demand allocation setting. On the "assign" attribute of each demand, the name of the next hierarchical system to which the demand is to be assigned is selected.

(3) The demand assignment is checked. Check if the "assign" attribute of each demand has already selected the next hierarchical system to assign.

(4) And the requirement distribution check is completed, and if the check result shows that all the requirements have completed the requirement distribution setting, the next step is carried out. Otherwise, returning to the step (2) to complete the demand distribution setting.

(5) A demand baseline version to be assigned is selected.

(6) And (4) allocating the demand. According to the setting of the 'distribution' attribute, the demand can be automatically distributed to the corresponding next-level system, and the demand module can be automatically created to record the distributed demand under the corresponding system level in the DOORS system. Here, the allocated system hierarchy is a system hierarchy defined in the demand information architecture.

(7) And (4) receiving the demand. And creating a requirement formal module under a corresponding system level folder in the DOORS system, and receiving the distributed requirements. The demand object assigned from the upper level system is automatically received and created in the demand formalization module.

(8) And setting a link. The link of two formal modules of the distribution requirement and the receiving requirement and the link type function are realized.

Specifically, before the above steps of the present invention are performed, the following operations are required:

(1) defining a global model project requirement hierarchy array

And forming a global model project requirement hierarchical structure array according to the configuration condition of the model project information architecture in the DOORS system, wherein the array and the model are packaged in an application program for global calling.

(2) Customizing demand templates

And customizing a requirement template rule, well defining the view, the attribute type and the like of a requirement formal module, and preferably setting the customized attribute of each formal module to automatically distribute, receive and match the subsequent requirement.

(3) Forming a demand

After the customization of the requirement template is completed, requirement definition is needed to form a requirement formal module for the distribution of the requirement.

(4) Demand newly added baseline

And (4) performing requirement distribution on the defined requirement formal module, and adding a requirement baseline at first. The process is as follows:

firstly, before adding a baseline, judging whether baseline examination and sign setting is performed, if so, establishing the baseline, otherwise, setting a baseline application.

Then, carrying out baseline examination and signature setting, and carrying out baseline application setting after the setting is finished, wherein the examination and signature contents are as follows: "compilation", "collation", "audit", "approval", "release", "export".

And finally, completing the application by adding a new baseline to the demand.

Further, the checking demand assignment specifically includes:

firstly, automatically acquiring the type of a distribution system, namely the level of a current model project system, then judging whether a lower system exists, if the lower system does not exist, not distributing the demand, and prompting to end. Otherwise, the execution is continued.

Secondly, judging whether the distribution is required and then the receiving is finished, if the receiving is not finished, the distribution cannot be carried out; if the demand has been allocated and received, the demand can be reallocated and the system automatically sets and prompts "set allocation demand again".

Thirdly, if the check requirement distribution identifier is not checked, a new check requirement distribution identifier is needed.

Then, it is checked whether the requirement entry "assignment" attribute has been set. If the directory is the current directory, prompting that the attribute of 'distribution' cannot be set for the directory; if the item is a requirement item, the allocation is not set, and the specific requirement item is prompted to be not set.

Finally, whether the demand allocation is finished is checked. If the check is finished, modifying the check demand distribution identifier state 0, and simultaneously reminding the next step of setting the distribution system demand; if the check is not complete, the demand assignment flag state 1 is checked.

Further, setting the distribution system requirements specifically includes:

Secondly, whether the demand formal module of the model project system already sets the demand of the distribution system. If the demand of the distribution system is not set, the setting is started, if the formal module has a base line, the base line of the formal module is selected, otherwise, the establishment of the base line is prompted, and the program is terminated.

When the setting of the formal module base line is selected, whether an 'Allocation _ Summary formal module' (hereinafter, referred to as an index module, the Allocation _ Summary can define a name by itself) exists is judged, if not, an 'Allocation _ Summary formal module' index module is newly built, and an 'Allocation formal module' intermediate module (hereinafter, referred to as a detailed module) is newly built, and an Allocation record is newly added; if the 'Allocation _ Summary formal module' exists, only the middle module of the 'Allocation formal module' is newly established, and the Allocation record is newly added. And meanwhile, setting the distribution identification state of the formal module.

If the formal module already sets the demand of the distribution system, various conditions after demand distribution are judged. There are generally the following situations:

after the demand of the distribution system is set, the next step of 'demand distribution system' can be carried out "

All the demands are successfully distributed to the subordinate system and wait for receiving

After the 0-level request is allocated, wait for receiving

After the current level of demand is distributed, waiting for receiving

The level 0 request is received and the level one request is not received

The current level of demand has been received and the level 0 demand has not been received

After the demand is distributed and received, please set the distribution demand again

Further, the demand allocation system specifically includes:

firstly, according to the distribution identification state of the formal module, starting to distribute the requirement to the system, selecting the formal module requirement to distribute to a specific project system, and determining the project system according to the model project information architecture.

And secondly, selecting 'distributed to the system', if the project system is distributed completely, the project system cannot be distributed, if the project system is distributed completely, the project system is executed after being distributed completely.

When the project system is not allocated, the demand allocation is started, namely: newly adding records in an index module of the 'Allocation _ Summary formal module'; newly adding an Allocation record in the detail module of the 'Allocation formal module', modifying a record identifier in the Allocation formal module, judging whether the Allocation is finished, setting an Allocation identifier of the formal module, and prompting that the system Allocation of the selected project is successful.

And thirdly, after the demand is successfully distributed to the system, the system can operate in a specific project system and receive the demand. If there are many assignable systems under the project system, the "demand assignment to system" operation may be selected repeatedly.

In the process of repeatedly selecting the operation of 'demand distribution to system', the next-level system can also perform demand receiving operation.

Further, the requirement receiving specifically includes:

demand reception can handle two ways, namely: transfer demand reception and allocation demand reception. Firstly, the receiving requirement transferred from the project specification and concept service of the current level is called a transfer requirement; and secondly, the receiving demand distributed from the system of the upper level is called the distribution demand. Demand reception is divided into two cases, one is a brand new demand and one is demand coverage. A brand new requirement, namely, a new construction is started, and a transfer requirement and a distribution requirement are received; and the requirement covering is that after the requirement is successfully received and relevant work is started, a new baseline is updated, and then the requirement covering or a new requirement operation can be selected.

And (3) receiving the requirement, namely firstly completing the generation of the distribution requirement receiving template, then inputting a prefix of a requirement module, and then automatically initializing the view, the attribute and the attribute type in a formal module for receiving the requirement. And after the distribution requirement receiving template is generated, if the requirement is received for the first time. The process is as follows:

(a) and automatically acquiring the type of the distribution system, namely the hierarchy of the project system of the current model.

(b) Checking the index record of the 'Allocation _ Summary formal module', matching the name of the formal module in current operation, taking out the successfully allocated identifier, and judging whether to proceed the next step or quit according to the identifier.

(c) If not, circulating the detailed module name of the 'Allocation formal module' in the 'Allocation _ Summary formal module' index module and applying the detailed module. And if the detailed module has no requirement record, ending the operation, otherwise, carrying out the next operation.

(d) Defining the acquired current formal module name and path, simultaneously taking out the distributed module name and module path, applying the distributed module, matching the current detailed module ID demand number in the distributed module, if the current detailed module ID demand number is matched, newly adding one demand record in the current formal module, copying the related attribute content recorded by the ID demand number to the current formal module, simultaneously modifying the ID record identifier in the distributed module, modifying the identifier receiving state of the detailed module of the 'Allocation formal module', and counting.

(e) The processing and distributing module distributes the receiving sequence of the level and the receiving sequence of the level 0 and sets the specific identification state.

(f) System name, baseline version of received project with addition of module attributes in an assignment module

(g) Recording the successful receiving identifier in the modified 'Allocation _ Summary formal module' index module

(h) Modifying whether to receive completion indication in allocation module

(i) This completes the reception of the demand.

If the requirement is to be covered, the process is as follows:

(b) Judging the current formal module requirement receiving state identification, if the current formal module requirement receiving state identification meets the covering requirement, carrying out the following operation, otherwise, prompting to terminate,

(c) checking the index module record of the 'Allocation _ Summary formal module', matching the current project system, taking out the baseline version, and performing the next step when the obtained project name is consistent with the formal module name of the operation certainly; otherwise, it is not processed.

(d) Judging whether the detailed module of the 'Allocation formal module' has a requirement record, if so, carrying out the next step; otherwise, ending the current detailed module.

(e) Circularly taking out the distribution ID number and the distribution module name of the current module demand record to form a text record set; taking out module names and module paths of the distribution modules, applying the distribution modules, circularly taking out required item IDs (the distribution item IDs are father IDs of the current modules) and the names of the distribution modules in the distribution modules to form text records, and matching the text records with a text record set formed by taking out the current modules:

if the ID requirement number is matched with the ID requirement number, the related attribute content recorded by the current ID requirement number is copied to a current formal module (the attribute content can be copied according to the actual requirement), the ID record identification in the distribution module is modified, the identification receiving state in an 'Allocation formal module' detailed module is modified, the identification is set, and a change count is newly added

If not, adding a new demand entry record in the current formal module, similarly, copying the related attribute content of the current ID demand number record to the current formal module (the attribute content can be copied according to the actual demand customization), modifying the ID record identifier in the distribution module, correcting the identifier receiving state in the detailed module of the 'Allocation formal module', setting the identifier, and adding the demand addition count.

(f) The processing and distributing module distributes the receiving sequence of the level and the receiving sequence of the level 0 and sets the specific identification state.

(g) Modifying an assignment completion baseline version state for module attributes in an assignment module

(h) Recording the successful receiving identifier in the modified 'Allocation _ Summary formal module' index module

(i) Adding receiving system in distribution module

(j) Setting whether to receive completion flag in allocation module

(k) This completes the reception of the demand.

Further, the link setting specifically includes:

after the demands are distributed and received, the distributed and received demands are automatically linked, and the demands can be traced conveniently. The process is as follows:

(a) a target module is selected. The target modules are modules in which the required items in the operation modules are linked outwards or inwards, each operation module may have a plurality of target modules, and each target module is set once. In addition, the source module is the current operation module and is not selectable by default.

(b) A linking module is selected. The link module is a set of link modules, which are set to better manage the demand to satisfy the fixed modules, and the link modules have 6 types:

the method comprises the following steps of Satisfields: relationship-satisfying links between deposit requirements

Allocates: link for storing distribution relationships between requirements and designs

DerivedFrom: link for storing derived relationships between design and underlying requirements

Refers: links for storing relationships referenced by references

Verifies: link validity for depositing verification and Validation data to verification relationships between requirements or designs: link for depositing validation data to verification relationships between requirements or designs

(c) An existing attribute is selected. The attribute is set to be linked, and without special description, the attribute is selected to be 'gAllReqAllocationID', and the attribute can be defined and set in a program;

(d) the link direction is selected. There are three ways, target to source, source to target, bi-directional; the coherency operation link direction is generally defaulted.

(e) And (4) application determination. And selecting and confirming the content of the 4 steps to be set, and determining.

The requirement distribution automation based on the DOORS system can be completed by the operation of the 5 steps. The iterative operation can be circulated, and the setting requirements of different levels of requirements are met.

After the operation is finished, according to the requirement of each model project, packaging programs, directly installing, wherein the installation program package is divided into a basic package and a model package, and the basic package is mainly a file which is common to all models; the model packet mainly satisfies the specific special content used by each model. The demand distribution process is standardized, standardized and unified by service personnel in the actual use process.

The key technology of the invention is that the demand based on the demand information architecture level is automatically distributed and received; a demand distribution inspection method based on a DOORS system; the requirements of each hierarchical system are automatically distributed and received, the method is suitable for different hierarchical systems, and the process supports continuous loop iteration; the automatic demand distribution method based on the DOORS system is implemented mainly according to the information architecture of the model project system, the determined demand is subjected to the process operations of demand addition baseline, inspection demand distribution, setting distribution system demand, demand distribution to the system, next-level system demand receiving, link setting and the like, and meanwhile, a model project installation package can be realized.

Claims

1. A DOORS system-based demand assignment automation method, characterized in that the method comprises:

2. A DOORS system based demand assignment automation method in accordance with claim 1,

after S2, and before S3, the method further includes selecting a demand baseline version to allocate.

3. The DOORS system-based demand assignment automation method according to claim 1, wherein S1 specifically is:

4. A DOORS system based demand assignment automation method in accordance with claim 3,

in the process of checking whether each requirement item 'distribution' attribute is defined:

5. The DOORS system-based demand assignment automation method of claim 1, further comprising, prior to S1:

a template of the requirement entry is defined.

6. The DOORS system-based demand assignment automation method of claim 5, wherein demand assignment to defined demand items is performed by adding a demand baseline first.

7. The method of claim 1, wherein in S3, each requirement entry is allocated to a corresponding plurality of next-level systems, specifically:

8. The DOORS system-based demand assignment automation method of claim 7, wherein during the process of repeatedly selecting the demand assignment to system operation, the next level system can also perform demand receiving operation.