CN112214555A - Tracing method and tracing system - Google Patents
Tracing method and tracing system Download PDFInfo
- Publication number
- CN112214555A CN112214555A CN202010066407.XA CN202010066407A CN112214555A CN 112214555 A CN112214555 A CN 112214555A CN 202010066407 A CN202010066407 A CN 202010066407A CN 112214555 A CN112214555 A CN 112214555A
- Authority
- CN
- China
- Prior art keywords
- identifiers
- domain
- items
- identifier
- subdomain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/285—Clustering or classification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
- Y02T10/00—Road transport of goods or passengers
- Y02T10/60—Other road transportation technologies with climate change mitigation effect
- Y02T10/70—Energy storage systems for electromobility, e.g. batteries
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a tracing method and a tracing system, and belongs to the technical field of system development. The method comprises the following steps: defining identifiers of process domains in a plurality of process domains, determining the element type of each process domain, determining a mapping relation corresponding to elements of different process domains in the plurality of process domains, and defining sub-domain items and identifiers of the sub-domain items according to the mapping relation and the element type, wherein the sub-domain items can be vectors, columns or fields; and obtaining identifiers of the elements in the plurality of process domains through the identifiers of the sub-domain items, and then establishing a traceability relation between part of the identifiers of any elements in the plurality of process domains and the identifier of at least one element in the rest elements. The invention is used for BMS flow development.
Description
Technical Field
The invention relates to the technical field of system development, in particular to a method for constructing a tracing relation, a tracing method, equipment and a computer storage medium.
Background
The core of the bms (battery Management system), an electric vehicle core (battery related technology), is a system for monitoring and managing a battery. The battery protection is realized by collecting and calculating parameters such as voltage, current, temperature and residual electricity quantity (SOC) and further responsively controlling the charging and discharging processes of the battery, and is an important link for connecting the battery and the automobile. Therefore, how to develop a complete set of BMS is a key topic of research in the electric vehicle industry at home and abroad.
As in fig. 1, the arrows represent development steps and the dashed lines represent the inter-traceability between the various process domains. In the whole development process, in order to better develop the whole BMS system, the relationship between process domains needs to establish a complete and detailed retrospective relationship and ensure high consistency. Currently, there are many forms for establishing traceability relationships between process domains, and the relationships are mainly classified into two categories: ID (Identity) based traceability and name based traceability. Based on the ID tracing, corresponding ID numbers are established through each process domain, and tracing relations are established according to the ID numbers through application program tools such as Doors, PTC and the like; name-based tracing is established by the correlation tool by the name of the individual elements in each process domain.
At present, in the ID tracing-based method, because an independent ID number is applied to each process domain, and the number of elements corresponding to each process domain is different, when a tracing relationship is established, a one-to-many mapping relationship occurs, so that the problems that the actual tracing relationship is not clear in correspondence and the BMS function coverage is incomplete occur. In addition, because the number of the IDs of each process domain is large, problems such as correspondence errors and the like are prone to occur in the process of establishing the traceability relationship. Based on the name tracing method, when the tracing relation between the requirements is established, because the items of the requirements are many, the tracing representation is difficult when the tracing relation is established, and the strip-by-strip correspondence is not clear. The two major methods at present have uniqueness on establishment of a retrospective relationship, are only limited to be used in a certain project, and if the requirements are changed, added and deleted, the whole process needs to be reestablished, so that the resource waste is serious.
Disclosure of Invention
The invention aims to provide a tracing method and a tracing system, which solve the technical problems that in the prior art, due to different element numbers, the tracing process is complicated, the corresponding relationship is not clear, the coverage range is limited, or due to a plurality of required items, the tracing process is complicated and the corresponding relationship is not clear, and in the prior art, due to the uniqueness of the tracing relationship, the corresponding elements and identifiers, the reusability of projects is poor, and the like.
In order to achieve the above object, an embodiment of the present invention provides a method for constructing a traceback relationship, where the method includes:
s1) defining identifiers of process domains in a plurality of process domains, determining the element type of each process domain, determining the mapping relation corresponding to elements of different process domains in the process domains, and defining sub-domain items and identifiers of the sub-domain items according to the mapping relation and the element type, wherein the sub-domain items can be vectors, columns or fields;
s2) obtaining identifiers of elements in the plurality of process domains by the identifiers of the sub-domain items, and then establishing a traceability relationship of a part of the identifier of any element in the plurality of process domains and an identifier of at least one element of the remaining elements.
Specifically, in step S1), a sub-domain item is defined according to the mapping relationship and the element type, specifically:
respectively defining a plurality of subdomain items according to the element types of the same kind in the element types and the mapping relations of the same kind in the mapping relations, and configuring the hierarchies of the plurality of subdomain items relative to each process domain.
Specifically, the step S1) defines the sub-domain items and the identifiers of the sub-domain items, specifically:
defining a plurality of sub-domain items, and corresponding each process domain to all the sub-domain items;
and defining identifiers of the sub-domain items, wherein a partial process domain is selected, and the identifiers of the partial sub-domain items corresponding to the partial process domain are configured into the same characteristic characters or the same type of characteristic characters.
Specifically, the step S1) defines the sub-domain items and the identifiers of the sub-domain items, specifically:
and respectively defining a plurality of subdomain items and identifiers of each subdomain item at least by combining the functional module and the functional requirements corresponding to the functional module, and configuring the hierarchy of the plurality of subdomain items and the number of the identifiers of each subdomain item relative to each process domain.
Specifically, the identifier of the sub-domain entry is defined in step S1), specifically:
the identifier types of any two subdomain items are defined to be the same, and the identifier type of any one subdomain item is different from the identifier type of any one process domain in the plurality of process domains.
Specifically, the sub-field items defined in step S1) include:
a class item configured as a set of identifiers corresponding to at least functional and non-functional requirements of a portion of the plurality of process domains;
a functional module item configured as a set of identifiers corresponding to functional modules of a developed system, wherein a requirement definition of a functional module of the developed system corresponds to a requirement description of the functional requirement;
a unit item configured as an identifier set corresponding to a component of the function module;
a requirement item configured as a set of identifiers corresponding to at least identifiers of a portion of the plurality of process domains.
Specifically, the sub-field entry defined in step S1) further includes:
an additional item configured as a set of identifiers of test cases corresponding to the requirement item;
the additional item is further configured as a set of identifiers corresponding to different requirements definitions of the functional module in a plurality of items.
Specifically, the obtaining identifiers of the elements in the plurality of process domains through the identifiers of the sub-domain items in step S2) includes:
configuring a selected portion of an identifier of a current element to inherit an identifier of a process domain to which the current element belongs;
configuring the remaining part of the identifier of the current element to be consistent with the identifier of the sub-domain item relative to the selected part, and obtaining the identifier of the current element;
and updating the current element, jumping to a selected part configured with the identifier of the current element to inherit the identifier of the process domain to which the current element belongs, and finally obtaining the identifiers of the elements in the process domains.
Specifically, the step S2) of establishing the traceability relationship between the part of the identifier of any element in the plurality of process domains and the identifier of at least one element in the remaining elements includes:
determining different parts of the identifiers of any elements in the multiple process domains, and establishing a traceability relation between the part of the identifiers belonging to the sub-domain items or the part of the identifiers belonging to any process domain in the different parts and the identifier of at least one element in the rest elements.
The embodiment of the invention provides a tracing method, which comprises the following steps:
obtaining identifiers of elements in the process domain, selecting parts of the identifiers, and combining the selected parts of the identifiers through the traceability relation to obtain the identifiers of the elements with the same parts of the selected identifiers.
The embodiment of the invention provides a tracing system, which comprises:
and the tracing module is configured to at least have the functions of indexing and retrieving the identifiers of the elements and the tracing relations.
In another aspect, an embodiment of the present invention provides an apparatus, including:
at least one processor;
a memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor implements the aforementioned method by executing the instructions stored by the memory.
In yet another aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, cause the computer to perform the foregoing method.
The invention provides a retrospective scheme based on identifier establishment; in the scheme, a class is defined in each process domain, elements which can establish a traceability relation in different process domains are defined as the same identifier (if the class can be different), and for a one-to-many mapping relation, a subdomain item and an identifier of the subdomain item are defined; the whole tracing relation is clear in expression and can completely cover all the required elements; by the identifier of the sub-domain item, new elements can be added in each process domain at will, an identifier library can be formed along with the progress of a development process, different elements can be called based on different projects, the reusability is strong, and development resources are greatly saved.
Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the embodiments of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the embodiments of the invention without limiting the embodiments of the invention. In the drawings:
fig. 1 is a schematic view of a BMS development flow;
FIG. 2 is a schematic diagram of the main steps of the embodiment of the present invention;
fig. 3 is a schematic flowchart of an exemplary process of establishing a traceability relationship according to an embodiment of the present invention;
FIG. 4 is a diagram of identifiers for exemplary elements of an embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating embodiments of the invention, are given by way of illustration and explanation only, not limitation.
Example 1
As shown in fig. 2, an embodiment of the present invention provides a method for constructing a traceback relationship, which can be used for BMS procedure development, and the method includes:
s1) defining identifiers of process domains in a plurality of process domains, determining the element type of each process domain, determining the mapping relation corresponding to the elements of different process domains in the plurality of process domains, and defining subdomain items and the identifiers of the subdomain items according to the mapping relation and the element type;
s2) obtaining identifiers of elements in the plurality of process domains by the identifiers of the sub-domain items, and then establishing a traceability relationship between a part of the identifier of any element in the plurality of process domains and an identifier of at least one element in the remaining elements, wherein the traceability relationship may be a retrievable query relationship, a recallable relationship between a process domain and the remaining process domains, a retrievable query relationship, a recallable relationship between an element and the remaining elements, a retrievable query relationship, a recallable relationship between an identifier or a part of an identifier and a process domain and an identifier, a retrievable query relationship, a recallable relationship between an element requirement entry (description) and a process domain and an identifier, and a retrievable query relationship, a recallable relationship between an identifier or a part of an identifier and other identifiers or parts of other identifiers.
For each process domain definition domain ID, system requirements ID: SyR, System architecture ID: SyA, software requirement ID: SwR, software architecture ID: SwA, software detailing ID: UD, unit test ID: UT, software integration test ID: UIT;
the element types of the respective process domains may include:
the system requirements mainly comprise functional requirements and non-functional requirements, wherein the functional requirements (description) comprise requirements (definitions) corresponding to different functional modules, and the non-functional requirements comprise development environment requirements, hardware requirements, quality requirements and the like;
the system architecture mainly represents a dynamic structure and a static structure of the system through a structural diagram, and represents the corresponding relation between functional modules of the BMS system on the whole structure;
the software requirements are detailed on functional requirements in system requirements, and simultaneously comprise part of non-functional requirements, and each system requirement corresponds to one or more software requirements;
the software architecture is a structural definition of software hierarchy of each functional module, and comprises interface definition, definition of interaction relation between different functional modules and different hierarchies of the same functional module;
the detailed software design is that internal logic of each functional module is developed according to software requirements according to a functional module framework defined in a software architecture, in the design process, one functional module is divided into a plurality of sub-modules, and one sub-module is defined as a unit;
the unit test is to compile a test case according to the detailed design of the software, verify the model or the code through the test case after completing the software implementation (the model or the code) according to the detailed design of the software, and check whether the software implementation conforms to the detailed design of the software;
the software integration test is to integrate the units together to verify the software architecture and to verify whether the interface design of each functional module in the architecture is reasonable.
The mapping relationships corresponding to the elements of different process domains can be used to determine the association characteristics of the elements and the element types, such as the master-slave association characteristics and the logical sequence association characteristics of the data processing flow.
Specifically, in step S1), a sub-domain item is defined according to the mapping relationship and the element type, specifically:
respectively defining a plurality of subdomain items according to the element types of the same kind in the element types and the mapping relations of the same kind in the mapping relations, and configuring the hierarchies of the plurality of subdomain items relative to each process domain.
In some implementations, a same-class item is determined according to the element types of the same class in the element types and the mapping relationships of the same class in the mapping relationships, and then a plurality of sub-domain items are defined by the same-class item, where the same-class item may be an element having the same function implementation in different process domains, for example, a part of the same-class item is determined according to the element types of the same class in the element types, then a plurality of sub-domain items are defined by the part of the same-class item, and another part of the same-class item is determined according to the mapping relationships of the same class in the mapping relationships, and then a plurality of sub-domain items are further defined by the another part of the same-class item; for the hierarchy, if the subdomain entries are columns, the hierarchy is the order of the rest of the columns relative to the column in which the process domain is located; sub-domain items close to the process domain can be configured according to the importance described by the master-slave relationship and the requirement; in some implementations, the aforementioned hierarchy may be configured using a mapping relationship.
Specifically, the step S1) defines the sub-domain items and the identifiers of the sub-domain items, specifically:
defining a plurality of sub-domain items, and corresponding each process domain to all the sub-domain items;
and defining identifiers of the sub-domain items, wherein a partial process domain is selected, and the identifiers of the partial sub-domain items corresponding to the partial process domain are configured into the same characteristic characters or the same type of characteristic characters.
In some implementations, the same token or class of tokens can be a particular numeric value, letter, or string of numbers, tokens, and/or letters, such that some elements, even if not having descriptions corresponding to certain subdomain entries, do not cause confusion and ambiguity in the identifiers and correspondence of the elements.
Specifically, the step S1) defines the sub-domain items and the identifiers of the sub-domain items, specifically:
and respectively defining a plurality of subdomain items and identifiers of each subdomain item at least by combining the functional module and the functional requirements corresponding to the functional module, and configuring the hierarchy of the plurality of subdomain items and the number of the identifiers of each subdomain item relative to each process domain.
In some implementations, the number of identifiers (available for configuration) for each subdomain item may be determined based on the location of the different levels, e.g., nine subdomain items whose levels are closest to a process domain may be configured relative to the process domain, and the foregoing characteristics may be additionally specified for portions of the process domain, so that there may be a total of ten identifiers available for configuration for the subdomain items of that level.
Specifically, the identifier of the sub-domain entry is defined in step S1), specifically:
the identifier types of any two subdomain items are defined to be the same, and the identifier type of any one subdomain item is different from the identifier type of any one process domain in the plurality of process domains.
In some implementations, for example where a process field selects a particular numerical value, letter, or any of a string of numbers, tokens, and/or letters, the sub-field item selects any of the foregoing particular numerical values, letters, or any of the remaining two of the string.
Specifically, the sub-field items defined in step S1) include:
a class entry (which may be referred to simply as a class when in a column) configured as a set of identifiers corresponding to at least functional and non-functional requirements of a portion of the plurality of process domains;
a function module item (when in a column, it may be referred to as a function module for short) configured as an identifier set corresponding to a function module of a developed system, where a requirement definition of the function module of the developed system corresponds to a requirement description of the function requirement;
a unit item (which may be simply referred to as a unit when in a column) configured as an identifier set corresponding to a component of the function module;
a requirement item (in columns, simply requirement) configured as a set of identifiers corresponding to at least identifiers of a portion of the plurality of process domains;
the defined subdomain entries further include:
an additional item (which may be referred to as an additional item for short when in a column) configured as an identifier set of the test case corresponding to the requirement item;
the additional item is further configured as a set of identifiers corresponding to different requirements definitions of the functional module in a plurality of items.
The subdomain entries are preferably configured in the 5 dimensions described above, each dimension may have a set of identifiers of multiple identifiers, some of which may correspond to a particular requirement item.
In some implementations, obtaining identifiers of elements in the plurality of process domains from the identifiers of the sub-domain items in step S2) includes:
configuring a selected portion of an identifier of a current element to inherit an identifier of a process domain to which the current element belongs;
configuring the remaining part of the identifier of the current element to be consistent with the identifier of the sub-domain item relative to the selected part, and obtaining the identifier of the current element;
and updating the current element as the next element which is not configured with the identifier, jumping to a selected part configured with the identifier of the current element to inherit the identifier of the process domain to which the current element belongs, and finally traversing in sequence to obtain the identifiers of the elements in the process domains.
In some implementations, the step S2) of establishing a traceability relationship between the part of the identifier of any element in the plurality of process domains and the identifier of at least one element in the remaining elements includes: and determining different parts of the identifiers of any elements in the plurality of process domains, establishing a traceability relation between the part of the identifiers belonging to the sub-domain items or the part of the identifiers belonging to any process domain in the different parts and the identifier of at least one element in the rest elements, so that the identifiers of the process domains and the identifiers of the elements can be used for traceability processes.
The embodiment of the invention also provides a tracing method, which comprises the following steps:
obtaining identifiers of elements in the process domain, selecting parts of the identifiers, and combining the selected parts of the identifiers through the traceability relation to obtain the identifiers of the elements with the same parts of the selected identifiers.
In some implementations, as shown in fig. 3, the main flow of constructing the traceability relationship is mainly as follows: defining process domain IDs, analyzing the mapping relation of element types contained in each process domain and elements among the process domains, determining the same type items among different process domains, setting the element IDs aiming at the same type items, and establishing traceability (traceability relation).
From the foregoing, the ID may be defined as in Table 1 based on an analysis of each particular process domain:
TABLE 1 identifier correspondence Table
| Process domain | Class I | Functional module | Unit cell | Demand for | Attachment(s) | ||
| System requirements | SyR | 1-9 | 01-99 | 0 | 01-99 | 00-99 | |
| System architecture | SyA | 1-9 | 01-99 | 0 | 00 | 00 | |
| Software requirements | SwR | 1-9 | 01-99 | 1-9 | 01-99 | 00-99 | |
| | SwA | 0 | 01-99 | 0 | 00 | 00 | |
| Software | UD | 0 | 01-99 | 1-9 | 00 | 00 | |
| Software | UT | 0 | 01-99 | 1-9 | 01-99 | 00-99 | |
| Software | UIT | 0 | 01-99 | 0 | 01-99 | 00-99 |
Wherein, the process domain: defining a domain ID by English letter abbreviation; class (item): non-functional requirements and other requirements are contained in a system requirement and system architecture process domain, wherein 1 represents functional requirements, 2 represents non-functional requirements, and 3-9 represents other requirements; functional module (item): dividing the whole BMS system into a plurality of functional modules according to different functions, wherein each functional module corresponds to an ID number; unit (item): a functional module is divided into different subsystems according to different logic compositions, each subsystem is a unit, and each unit corresponds to an ID number; requirement (item): ID number definition of system requirement and software requirement; the addition (item) represents: 1. different test cases with the same requirement; 2. a functional module has different requirements in different projects, and the different requirements of the same module can be placed in the same library in additional projects. 0/00 (signatures) in the table indicate that such an ID is not required in this process domain.
As shown in fig. 4, the correspondence of the Identifier (ID) of one element to the process domain and sub-domain items can be clearly found, so that the tracing process can be performed according to the correspondence.
Having completed the ID definitions for each process domain, the identity between each ID can be determined, for example:
one of the system requirements ID isSyR1010 01 00If the number 01 requirement of the function requirement of the balancing module (defined as the balancing module in the function module 01) in the system requirement is represented, the corresponding similar items are as follows:
similarly, in the tracing method, all the same items can be found out based on the system requirements in the same manner, and according to the existing tracing relationship in the development flow of fig. 1, the bidirectional tracing relationship of the identifiers of the elements in each process domain, for example, the tracing relationship between part of the identifiers of the elements and the identifiers of the other elements, is established according to the same items.
The retroactive relationship formed by the embodiment of the invention has strict logic and high coverage, can clearly express the retroactive relationship of elements in each process domain, and avoids the problem in functional design caused by unclear requirements in the whole BMS development process; the definition and classification of the process domain ID are clear, the tracing relation of a certain requirement in the whole process from top to bottom can be quickly found out, great convenience is brought to problem troubleshooting, and the development efficiency is greatly improved; the ID definition mode can uniformly arrange all the requirements in a library form and can be applied to development of a plurality of projects.
Example 2
Based on embodiment 1, an embodiment of the present invention provides a tracing system, including:
a trace back module configured to have at least a function of indexing and retrieving the identifier of the aforementioned element and the aforementioned trace back relationship;
the tracing module can be provided with a data storage module which can be a relational database or a key value database and the like; the tracing module can also be linked with the data storage module through a packaging interface and has the authority of accessing and reading and writing the data storage module; the trace back module can also be configured with a search engine to quickly complete the search for all relevant development process domains and development elements based on the search characters.
Although the embodiments of the present invention have been described in detail with reference to the accompanying drawings, the embodiments of the present invention are not limited to the details of the above embodiments, and various simple modifications can be made to the technical solutions of the embodiments of the present invention within the technical idea of the embodiments of the present invention, and the simple modifications all belong to the protection scope of the embodiments of the present invention.
It should be noted that the various features described in the above embodiments may be combined in any suitable manner without departing from the scope of the invention. In order to avoid unnecessary repetition, the embodiments of the present invention do not describe every possible combination.
Those skilled in the art will understand that all or part of the steps in the method according to the above embodiments may be implemented by a program, which is stored in a storage medium and includes several instructions to enable a single chip, a chip, or a processor (processor) to execute all or part of the steps in the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In addition, any combination of various different implementation manners of the embodiments of the present invention is also possible, and the embodiments of the present invention should be considered as disclosed in the embodiments of the present invention as long as the combination does not depart from the spirit of the embodiments of the present invention.
Claims (10)
1. A method for constructing a retrospective relationship, the method comprising:
s1) defining identifiers of process domains in a plurality of process domains, determining the element type of each process domain, determining the mapping relation corresponding to the elements of different process domains in the plurality of process domains, and defining subdomain items and the identifiers of the subdomain items according to the mapping relation and the element type;
s2) obtaining identifiers of elements in the plurality of process domains by the identifiers of the sub-domain items, and then establishing a traceability relationship of a part of the identifier of any element in the plurality of process domains and an identifier of at least one element of the remaining elements.
2. A method for constructing a traceability relationship as claimed in claim 1, wherein in step S1), a sub-domain item is defined according to the mapping relationship and the element type, specifically:
respectively defining a plurality of subdomain items according to the element types of the same kind in the element types and the mapping relations of the same kind in the mapping relations, and configuring the hierarchies of the plurality of subdomain items relative to each process domain.
3. The method for constructing traceability relationships according to claim 1, wherein the subdomain entries and the identifiers of the subdomain entries in step S1) are defined as follows:
defining a plurality of sub-domain items, and corresponding each process domain to all the sub-domain items;
and defining identifiers of the sub-domain items, wherein a partial process domain is selected, and the identifiers of the partial sub-domain items corresponding to the partial process domain are configured into the same characteristic characters or the same type of characteristic characters.
4. The method for constructing traceability relationships according to claim 1, wherein the subdomain entries and the identifiers of the subdomain entries in step S1) are defined as follows:
and respectively defining a plurality of subdomain items and identifiers of each subdomain item at least by combining the functional module and the functional requirements corresponding to the functional module, and configuring the hierarchy of the plurality of subdomain items and the number of the identifiers of each subdomain item relative to each process domain.
5. Method for constructing a retrospective relationship according to any one of claims 1 to 4, wherein the identifiers of the subdomain entries in step S1) are defined as follows:
the identifier types of any two subdomain items are defined to be the same, and the identifier type of any one subdomain item is different from the identifier type of any one process domain in the plurality of process domains.
6. The method for constructing a retrospective relationship according to claim 1, wherein the subdomain entries defined in the step S1) include:
a class item configured as a set of identifiers corresponding to at least functional and non-functional requirements of a portion of the plurality of process domains;
a functional module item configured as a set of identifiers corresponding to functional modules of a developed system, wherein a requirement definition of a functional module of the developed system corresponds to a requirement description of the functional requirement;
a unit item configured as an identifier set corresponding to a component of the function module;
a requirement item configured as a set of identifiers corresponding to at least identifiers of a portion of the plurality of process domains.
7. The method for constructing a retrospective relationship according to claim 6, wherein the sub-field entries defined in the step S1) further include:
an additional item configured as a set of identifiers of test cases corresponding to the requirement item;
the additional item is further configured as a set of identifiers corresponding to different requirements definitions of the functional module in a plurality of items.
8. The method for constructing traceability relationship according to claim 1, wherein the step S2) of obtaining identifiers of elements in the plurality of process domains by using the identifiers of the sub-domain entries comprises:
configuring a selected portion of an identifier of a current element to inherit an identifier of a process domain to which the current element belongs;
and configuring the rest part of the identifier of the current element to be consistent with the identifier of the sub-domain item relative to the selected part, and obtaining the identifier of the current element.
9. The method for constructing a retrospective relationship according to claim 1, wherein the step S2) of establishing the retrospective relationship between the part of the identifier of any element in the plurality of process domains and the identifier of at least one element in the remaining elements includes:
determining different parts of the identifiers of any elements in the multiple process domains, and establishing a traceability relation between the part of the identifiers belonging to the sub-domain items or the part of the identifiers belonging to any process domain in the different parts and the identifier of at least one element in the rest elements.
10. A tracing method is characterized by comprising the following steps:
obtaining identifiers of elements in a process domain, selecting parts of the identifiers, and obtaining identifiers of elements having the same parts as the selected identifiers in connection with the selected parts of the identifiers by means of the traceability relationship of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010066407.XA CN112214555B (en) | 2020-01-20 | 2020-01-20 | Method for constructing tracing relation and tracing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010066407.XA CN112214555B (en) | 2020-01-20 | 2020-01-20 | Method for constructing tracing relation and tracing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112214555A true CN112214555A (en) | 2021-01-12 |
| CN112214555B CN112214555B (en) | 2022-05-17 |
Family
ID=74058575
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010066407.XA Active CN112214555B (en) | 2020-01-20 | 2020-01-20 | Method for constructing tracing relation and tracing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214555B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653443A (en) * | 2015-12-21 | 2016-06-08 | 中电科航空电子有限公司 | Method for satisfying test tracing target of DO-178C standard |
| CN110688381A (en) * | 2019-09-25 | 2020-01-14 | 东方蓝天钛金科技有限公司 | Software product and software method for product process record tracing |
-
2020
- 2020-01-20 CN CN202010066407.XA patent/CN112214555B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653443A (en) * | 2015-12-21 | 2016-06-08 | 中电科航空电子有限公司 | Method for satisfying test tracing target of DO-178C standard |
| CN110688381A (en) * | 2019-09-25 | 2020-01-14 | 东方蓝天钛金科技有限公司 | Software product and software method for product process record tracing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214555B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112256558B (en) | Test case generation method and device, computer equipment and storage medium | |
| Collofello et al. | Towards automatic software fault location through decision-to-decision path analysis | |
| CN104462169A (en) | Method and a system for merging data into a database table | |
| CN106294128B (en) | A kind of automated testing method and device exporting report data | |
| CN113220588A (en) | Automatic testing method, device and equipment for data processing and storage medium | |
| CN107609179A (en) | A kind of data processing method and equipment | |
| CN112214555B (en) | Method for constructing tracing relation and tracing method | |
| KR101334806B1 (en) | Method of proudcing input sets of test case in test case generating system | |
| CN112988215A (en) | Method and device for realizing evaluation rule and evaluating user data and electronic equipment | |
| CN108829969A (en) | A kind of new and old circuit meshwork list comparison method and system based on circuit layout verifying | |
| CN115409416A (en) | Method and device for analyzing relevance degree of quality problem of aerospace product | |
| CN113850035A (en) | Chip verification method, device and equipment and readable storage medium | |
| CN112860570A (en) | Software and hardware hybrid system combined test profile construction method based on combined test | |
| CN113434596A (en) | Method and device for generating test data of distributed database | |
| CN112199294A (en) | Automatic software testing method and device | |
| CN114048084B (en) | Method and device for generating test case schema of schematic diagram and storage medium | |
| CN111813665A (en) | Big data platform interface data testing method and system based on python | |
| CN114665986B (en) | Bluetooth key testing system and method | |
| CN113254328B (en) | White box testing method, system, mobile terminal and storage medium | |
| CN113495831B (en) | Method, system, equipment and medium for generating test case based on keywords | |
| CN114819565B (en) | Verification method of system specification description file, control equipment and intelligent substation | |
| Zhan et al. | An SG-CIM Verification Method Based on Schema Comparison | |
| CN116521499A (en) | Performance verification method and system for industrial Internet identification analysis integrated machine | |
| Yang et al. | Database design for error searching system based on keyword priority | |
| CN112115148A (en) | Method, device and equipment for determining data comparison result |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |