Function requirement automatic construction method and device, equipment and storage medium
Through the automated functional requirements construction method, obtaining and matching functional requirements description information, the complex problem of functional requirements creation in the design and development of automotive electronic and electrical architectures is solved, improving the construction accuracy and efficiency, and avoiding manual errors.
Patent Information
- Application Number
- CN202411277121.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-12
- Publication Date
- 2025-01-03
AI Technical Summary
In the process of design and development of automotive electronic and electrical architectures, the creation of functional requirements, the establishment of hierarchical relationships, and the association with other components are complex, resulting in component creation errors, hierarchical construction errors or omissions, and the efficiency of importing functional requirements is low, resulting in inexpensive creation.
By obtaining the functional requirements description document, performing content traversal to obtain the requirements description information of the sub-function components, importing it into the target database, and traversing the model functional components in the development of the automotive electronic and electrical architecture, matching the sub-function components with their requirements description information, and realizing the functions Automatic construction of requirements to avoid manual participation.
It improves the accuracy and efficiency of functional requirements construction, reduces the probability of creation errors, hierarchical construction errors, and association errors or omissions, and improves development efficiency.
Smart Images
Figure CN119248240A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of automobile electrical architecture design and development, and in particular to a method, device, equipment and storage medium for automatically constructing functional requirements. Background Art
[0002] In the process of automotive electronic and electrical architecture design and development, the creation of functional requirements, the establishment of hierarchical relationships, and the association with other components are very complicated processes. If the functional requirements are imported and constructed manually, it will lead to component creation errors or hierarchical construction errors, association errors or omissions, and low creation efficiency. At the same time, the low efficiency of importing functional requirements will further lead to low efficiency in creating functional requirements. Summary of the invention
[0003] The present invention provides a method, device, equipment and storage medium for automatically constructing functional requirements to improve the accuracy and efficiency of functional requirement construction.
[0004] According to one aspect of the present invention, a method for automatically constructing functional requirements is provided, the method comprising:
[0005] Obtain functional requirement description document;
[0006] Traversing the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component;
[0007] Importing each of the sub-functional components and the corresponding requirement description information into a target database;
[0008] Performing component traversal on model functional components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-functional component;
[0009] Extract sub-functional components and their corresponding requirement description information from the target database, match each sub-functional component with each model sub-functional component to obtain a matching result, and update or construct the functional requirements of the model sub-functional components based on the matching result and the requirement description information of each sub-functional component.
[0010] According to another aspect of the present invention, there is provided a device for automatically constructing functional requirements, the device comprising:
[0011] Description document acquisition module, used to obtain functional requirement description documents;
[0012] A document content traversal module, used to traverse the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component;
[0013] A description information import module, used to import each of the sub-functional components and its corresponding requirement description information into a target database;
[0014] A component traversal module is used to traverse the model function components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-function component;
[0015] The component matching module is used to extract the sub-functional components and their corresponding requirement description information from the target database, and match each of the sub-functional components with each of the model sub-functional components to obtain a matching result, and according to the matching result and based on the requirement description information of each of the sub-functional components, update or construct the functional requirements of the model sub-functional components.
[0016] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:
[0017] at least one processor; and
[0018] a memory communicatively connected to the at least one processor; wherein,
[0019] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for automatically constructing functional requirements described in any embodiment of the present invention.
[0020] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for automatically constructing functional requirements described in any embodiment of the present invention when executed.
[0021] The technical solution of the embodiment of the present invention obtains the requirement description information of at least one sub-functional component by traversing the content of the functional requirement description document; importing each sub-functional component and its corresponding requirement description information into the target database, realizes the automatic import of the requirement function, improves the import efficiency, and facilitates the subsequent functional requirement construction. By traversing the model functional component in the process of developing the automotive electronic and electrical architecture, at least one model sub-functional component is obtained, the sub-functional component and its corresponding requirement description information are extracted from the target database, and each sub-functional component is matched with each model sub-functional component to obtain a matching result, and according to the matching result, based on the requirement description information of each sub-functional component, the functional requirements of the model sub-functional component are updated or constructed, realizing the automatic construction of the functional requirements of the sub-functional component, avoiding manual participation in the construction process, and improving the construction efficiency and construction accuracy. The probability of creation errors, hierarchical construction errors, and association errors or omissions in the manual construction process is reduced.
[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0024] Figure 1 is a flowchart of a method for automatically constructing functional requirements according to Embodiment 1 of the present invention;
[0025] Figure 2 is a schematic diagram of the structure of a device for automatically constructing functional requirements according to Embodiment 2 of the present invention;
[0026] Figure 3 It is a structural schematic diagram of an electronic device for implementing the method for automatically constructing functional requirements according to an embodiment of the present invention. DETAILED DESCRIPTION
[0027] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0029] Embodiment 1
[0030] Figure 1 This is a flow chart of a method for automatically constructing functional requirements provided in the first embodiment of the present invention. This embodiment is applicable to the automatic construction of functional requirements in the scenario of the design and development process of automotive electronic and electrical architecture. The method can be executed by an automatic construction device for functional requirements. The automatic construction device for functional requirements can be implemented in the form of hardware and / or software. The automatic construction device for functional requirements can be configured in an electronic device. Figure 1 As shown, the method includes:
[0031] S110. Obtain a functional requirement description document.
[0032] S120: Traverse the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component.
[0033] S130, importing each sub-functional component and its corresponding requirement description information into the target database.
[0034] S140, traversing the model functional components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-functional component.
[0035] S150, matching each sub-functional component with each model sub-functional component to obtain a matching result, and updating or constructing the functional requirements of the model sub-functional component according to the matching result and based on the requirement description information of each sub-functional component.
[0036] It should be noted that in the process of developing automotive electronic and electrical architecture, in the functional design and development stage, it is first necessary to evaluate which input requirements are taken over in the process of implementing a function or sub-function, so as to carry out functional design and development purposefully. The requirements that need to be associated or taken over are usually pre-determined by relevant technical personnel based on actual conditions, and the collected functional requirement items are imported into the database to achieve uniform storage of functional requirements, which is convenient for subsequent iterative updates. Therefore, it is necessary to pre-build a functional requirement description document containing functional requirement items.
[0037] Among them, the functional requirement description document can be a document pre-built by relevant technical personnel to describe the functional requirements of the component, and can specifically be an EXCEL document. The information contained in the functional requirement description document may include sub-function name, level one, level two, level three, functional requirement description, functional association relationship and functional association requirement use case. Among them, the sub-functional component is specifically a functional component based on the minimum functional unit of the automotive electronic and electrical architecture. Level one can represent different requirements associated with the sub-functional component, such as input requirements, control requirements and output requirements, etc. Level two is a subordinate item of different requirements of level one, and level three is a specific functional requirement item.
[0038] For example, the construction form of the functional requirement description document can be as shown in Table 1:
[0039] Table 1
[0040]
[0041] Exemplarily, the component name of the sub-function component may be vehicle start control, and the corresponding level 1 content may include preconditions, start process and postconditions. Among them, the level 2 content corresponding to the precondition may include users and cars; among them, the level 3 content corresponding to the user may include inserting the key, and the requirement description may be that the driver inserts the key into the steering column lock; the associated regulations may be "GB / T1234" ("Technical Specifications for Power Transformer Measurement"), and the associated requirement use case may be a vehicle start use case. The level 3 content corresponding to the car may be stationary and in neutral. Among them, the requirement description corresponding to stationary may be that the vehicle is stationary; the requirement description corresponding to neutral may be that the vehicle gear is in neutral; the associated regulations corresponding to the two are "GB / T1234", and the corresponding functional associated requirement use cases are vehicle start use cases. The level 2 content of the start process may include execution, and the subordinate level 3 content corresponding to the level 2 is vehicle power mode switching, and the corresponding requirement description is that the driver rotates the key to the START gear, and the corresponding associated regulations and functional associated requirement use cases are the same as above. The level 2 content corresponding to the postcondition may be state feedback, and its corresponding subordinate level 3 content may include engine start and instrument information feedback. Among them, the requirement description for engine start can be that the vehicle engine processes the start idle state; the requirement description for instrument information feedback can be that the instrument displays the engine speed as 500rpm, and the corresponding associated regulations and function-associated requirement use cases are the same as above.
[0042] Usually, the functional requirement items are imported into the database manually. However, in order to ensure that the functional requirement items can be saved in the database, data omissions will not occur due to manual creation, and to facilitate the changes in later requirements, the data can be automatically imported and automatically updated according to the changes in later requirements. Specifically, the content of the functional requirement description document can be traversed to obtain the requirement description information of at least one sub-functional component, that is, the functional requirement items and other information. Specifically, it can include the component name of the sub-functional component, the corresponding hierarchical relationship, including level one, level two and level three, the requirement description of the functional requirement items, the functional association relationship and the functional association requirement use case, etc.
[0043] The content extraction of the sub-functional component requirement description information is performed in an automated manner. In an optional embodiment, the content of the functional requirement description document is traversed to obtain the requirement description information of at least one sub-functional component, including: according to preset field keywords, the content of the functional requirement description document is traversed to obtain the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information of at least one functional component; for the associated regulatory information and the associated requirement use case information, according to preset key special characters, the sub-content contained in the associated regulatory information and the associated requirement use case information is extracted to obtain the associated regulatory information and the associated requirement use case information containing the sub-content; and the functional description information including the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information is generated.
[0044] The field keywords can be pre-set by relevant technical personnel according to the fields in the functional requirement description document. The field keywords can be set as "sub-function name". The associated regulatory information is also the functional association relationship.
[0045] Specifically, determine whether the cell in the column where the sub-function name is located is empty. If it is not empty, take the row where the column is located as the starting row, continue to traverse downward until the cell content is not empty again, and record the previous row of the row where the non-empty column is located as the ending row. Determine the name of the sub-function in the cell in the non-empty column. If it is sub-function component A, the hierarchical information, requirement description information, associated regulatory information, and associated requirement use case information of the sub-function component A are placed between the starting row and the ending row. Associate the component name of sub-function component A with the hierarchical information, requirement description information, associated regulatory information, and associated requirement use case information and store them in a pre-constructed blank array.
[0046] The hierarchical information, requirement description information, associated regulatory information, and associated requirement use case information between the set start and end rows are traversed through the FOR loop. Specifically, if the column where "Level 1" in the hierarchical information is located is empty, the number of rows is increased, and the cell traversal of the next row is continued until the cell content is not empty. Based on the same, the level 2 and level 3 as well as the requirement description information, associated regulatory information, and associated requirement use case information are obtained.
[0047] It should be noted that, since a sub-functional component can be associated with one or more functional associations and associated demand use case information at the same time, the contents of the cells in the "Functional Association" column and the "Associated Requirement Use Case Information" column need to be split according to the following principles: the line break " / n" and the semicolon ";" are used as the basis for judgment; when the condition is met, an association item / use case item is stored and the judgment continues, otherwise it is regarded as the content of the same association item / use case item. Through the above judgment, all association items and use case items are stored in the array corresponding to the corresponding sub-functional component.
[0048] Based on the above method, the requirement description information corresponding to the sub-function components with different names can be obtained and imported into the target database in the form of an array for storage, so as to facilitate the subsequent creation of functional construction. By automatically importing functional requirements into the database, the development efficiency is improved and it is convenient for later updates and iterations.
[0049] The model functional components in the process of automotive electronic and electrical architecture development are traversed to obtain at least one model sub-functional component. Based on the requirement description information of the sub-functional components in the target database, the model sub-functional components are automatically created to improve the creation efficiency and accuracy.
[0050] Extract sub-functional components and their corresponding requirement description information from the target database, match each sub-functional component with each model sub-functional component to obtain a matching result, and update or construct the functional requirements of the model sub-functional components based on the matching result and the requirement description information of each sub-functional component.
[0051] In an optional embodiment, each sub-functional component is matched with each of the model sub-functional components to obtain a matching result, and according to the matching result, based on the requirement description information of each sub-functional component, the functional requirements of the model sub-functional component are updated or constructed, including:
[0052] Step a1: Match each sub-functional component with each model sub-functional component to obtain successfully matched model sub-functional components and unmatched model sub-functional components that fail to match in the model sub-functional components.
[0053] Step a2: for the matched model sub-function component, determine whether the hierarchical information of the matched model sub-function component is consistent with the hierarchical information in the requirement description information of the sub-function component that has been successfully matched with it.
[0054] First, determine whether there is information of level one in the hierarchical information of the matched model sub-function component. If so, determine whether the name information of the existing level one is consistent with the name information of level one in the hierarchical information of the sub-function component in the requirement description information of the matched sub-function component. If they are consistent, there is no need to create level one. If they are inconsistent, update the hierarchical name of level one of the matched model sub-function construction according to the hierarchical information of level one in the requirement description information of the sub-function component. The specific creation method can be to create the name at the Name attribute in the General (attribute configuration) column of the matched sub-function component.
[0055] Based on the same method as the above-mentioned determination of the level information of level one, the level two and level three of the matched sub-function components are determined, and the level information of level two and level three is updated or created.
[0056] Step a3: If yes, determine whether the requirement description information, associated regulatory information and associated demand use case information of the matched model sub-function component are consistent with the requirement description information, associated regulatory information and associated demand use case information of the successfully matched sub-function component.
[0057] If the hierarchical information of the matched model sub-functional component is inconsistent with the hierarchical information in the requirement description information of the successfully matched sub-functional component, the requirement description information of the successfully matched sub-functional component is used to update the hierarchical information of the matched model sub-functional component to achieve the update of the functional requirements of the model sub-functional component.
[0058] Step a4: If not, then update or construct the functional requirements of the model functional subcomponent according to the requirement description information, associated regulatory information and associated requirement use case information in the requirement description information of the subfunctional component that successfully matches it.
[0059] Specifically, determine whether there is level information of level three under each level two requirement component of the matched model sub-function. If so, there is no need to create it, and determine whether the name of level three is consistent with the level name of level three of the matched model sub-function. If they are consistent, the requirement description content in the requirement description information constructed by the sub-function that is successfully matched with it is overwritten to the Description (description attribute) in the General property column of the requirement component corresponding to the matched model sub-function; if the name of level three is inconsistent with the level name of level three of the matched model sub-function, create a new component corresponding to level three, create the requirement name content in the requirement description information in the Name in the General property column of the newly created component, and add the "requirement description information" content to the Description in the General property column.
[0060] Similarly, the updating or creation of the associated regulatory information and the associated demand use case information is the same as the above-mentioned demand description information. The same method can be used to complete the updating or creation of the associated regulatory information and the associated demand use case information of the model function sub-component.
[0061] It should be noted that there are source functional components associated with sub-functional components in the associated regulatory information. Therefore, in the process of updating and creating functional requirements, the source functional components associated with the sub-functional components also need to be updated or created.
[0062] In an optional embodiment, for a matched model sub-functional component, a target source component having an association relationship with the matched model sub-functional component is determined; a reference source component is determined based on the associated regulatory information in the requirement description information of the sub-functional component that successfully matches the matched model sub-functional component; a consistency comparison is performed between the target source component and the reference source component to obtain a consistency comparison result; and based on the consistency comparison result, the target source component of the matched model sub-functional component is updated.
[0063] Specifically, the target source component is compared with the reference source component for consistency. If they are consistent, there is no need to re-create the construction association relationship; if they are inconsistent, in LINK (association attribute), the reference source component is added to the LINK attribute. If the current LINK attribute has a source component, it is deleted and the reference source component is added to the LINK attribute.
[0064] The technical solution of the embodiment of the present invention obtains the requirement description information of at least one sub-functional component by traversing the content of the functional requirement description document; importing each sub-functional component and its corresponding requirement description information into the target database, realizes the automatic import of the requirement function, improves the import efficiency, and facilitates the subsequent functional requirement construction. By traversing the model functional component in the process of developing the automotive electronic and electrical architecture, at least one model sub-functional component is obtained, the sub-functional component and its corresponding requirement description information are extracted from the target database, and each sub-functional component is matched with each model sub-functional component to obtain a matching result, and according to the matching result, based on the requirement description information of each sub-functional component, the functional requirements of the model sub-functional component are updated or constructed, realizing the automatic construction of the functional requirements of the sub-functional component, avoiding manual participation in the construction process, and improving the construction efficiency and construction accuracy. The probability of creation errors, hierarchical construction errors, and association errors or omissions in the manual construction process is reduced.
[0065] Furthermore, since the database of the automotive electronic and electrical architecture model is huge and complex, and the hierarchical contents of each sub-functional component are mutually inherited, after building the relevant component elements, the relevant component elements of the functional requirements are exported in the form of documents, and the existing automotive electronic and electrical architecture model cannot automatically export and automatically generate the functional requirements document according to the export format expected by the user. Therefore, based on this demand, the present invention also provides a method for automatically exporting and generating relevant documents of functional requirements,
[0066] In an optional embodiment, after matching each sub-functional component with each model sub-functional component to obtain a matching result, and updating or constructing the functional requirements of the model sub-functional component based on the matching result and the requirement description information of each sub-functional component, the method further includes:
[0067] Step b1: Select a target functional component from the model sub-functional components, and traverse the date-related information of the target functional component according to the preset first attribute key field to obtain document cover information.
[0068] Among them, the first attribute keyword can be "preparation date", "proofreading date" and "review date", etc., which can be pre-set according to actual needs.
[0069] Specifically, the cover design can include the component name of the target functional component, the compiler and date, proofreader and date, and auditor and date of the target functional component. This part of the content is established in the functional component data package of the corresponding target function in the electronic and electrical design tool model. Taking the PREEvision model as an example, this part of the content is under the Requirement Package component of the upper level of the target function Requirement component in the PREEvision model. The construction of the cover part of the content is completed by creating custom attributes. The construction name of the target functional component can be captured through requirement.getName() to lock the target function of the target functional component to be exported; then by traversing the custom attribute name of the upper level component, the "compilation date", "proofreading date" and "audit date" keyword strings are used to capture the compiler and date, proofreader and date, and auditor and date respectively, and place them in the cover position of the document template. Specifically, the position where the corresponding content is placed can be set in the Report model element.
[0070] Step b2: According to the preset second attribute key field, the terminology related information of the target functional component is traversed to obtain the document preface information.
[0071] The document preface information may include input design documents and professional term abbreviations, etc. The second attribute information may be "professional terminology", "abbreviation" and "related documents", etc.
[0072] Specifically, taking the PREEvision model as an example, the input design document is established in the model under the Requirement Package component, which is one level above the Requirement component of the target functional component. The component name of the target functional component is automatically captured through the requirement.getName() method, the functional component to be exported is locked, the custom attribute names of the components of the previous level are traversed, the document content under the "input design document" string is captured, and the location of the corresponding content is set in the Report model element, so as to place it in the preface position of the document template.
[0073] The abbreviations of professional terms are established in the model under the abbreviation library Requirement Package component. Requirement components are created based on controllers, and English abbreviations, English full names, and Chinese full names are established in the General of the component. By tracing the mapping of the target functional component, all professional term abbreviation requirement components involving the functional component are captured to form a new list and create a table. The professional term abbreviation of each controller occupies one row of the table, and the English abbreviation, English full name, and Chinese full name are filled in respectively. The position for placing the corresponding content is set in the Report model element, so that it is placed in the preface position of the document template.
[0074] Step b3: According to the preset third attribute key field, the function description information of the target function component is traversed to obtain the document function description information.
[0075] Among them, the third attribute key field can be information such as function introduction. Specifically, the functional characteristics description can include the component introduction of the target functional component and the benefits brought to the user / driver. Taking the PREEvision model as an example, in the Description under the Requirement component of the target functional component in the model, by grabbing the text content under the Description of the target functional component, the corresponding content placement position is set in the Report model element, so as to place it in the document function description of the document template.
[0076] Optionally, the requirement specification document may also include target function entry and / or exit conditions. The target function entry / exit conditions may include the prerequisites for the implementation of the function and the conditions for how the function is exited during implementation. Taking the PREEvision model as an example, both the entry conditions and exit conditions are established in the Description under the lower-level Requirement component of the target function component in the PREEvision model. By traversing the names of the lower-level components of the target function component, locking the requirement components named "entry conditions" and "exit conditions" strings, and grabbing the text content in the Description under these two components, set the location for the corresponding content in the Report model element, and place it in the document function description of the document template.
[0077] Optionally, the requirement specification document may also include the implementation scheme of the target function. Specifically, the implementation scheme of the target function may include the interaction relationship between different controllers. Taking the PREEvision model as an example, the controller model elements in the PREEvision model are all established in the SWC component of the next level of the software layer Root Composition. By tracing the mapping of the target function component, all the professional term abbreviation requirement components related to the function are captured to form a new list, and then by tracing the mapping pointing to SW in each professional term abbreviation requirement component, all the SWC components related to the function are captured to form a new list; at the same time, the SW port components that have established interaction relationships in all SWC components in the new list are packaged together, and a new table and a new legend are created. Each row of the table has three columns, and the content includes the SWport component name, the input SWC component name, and the output SWC component name. The legend shows the interaction relationship of all SWCs covered by the target function; the position of the legend is set in the Report model element, and the table is placed below the legend.
[0078] Step b4: Generate a functional requirement specification document based on the document cover information, document preface information and document function description information.
[0079] According to the document template corresponding to the preset functional requirement specification document, place different information in the corresponding position of the document to form a functional requirement specification document.
[0080] Embodiment 2
[0081] Figure 2 A schematic diagram of the structure of a device for automatically constructing functional requirements provided in the second embodiment of the present invention. The device for automatically constructing functional requirements provided in the embodiment of the present invention can be applied to the automatic construction of functional requirements in the scenario of the design and development process of automotive electronic and electrical architecture. The device for automatically constructing functional requirements can be implemented in the form of hardware and / or software, such as Figure 2 As shown, the functional requirement automatic construction device can be configured in an electronic device, and specifically includes: a description document acquisition module 201, a document content traversal module 202, a description information import module 203, a component traversal module 204 and a component matching module 205. Among them,
[0082] Description document acquisition module 201, used to acquire functional requirement description document;
[0083] A document content traversal module 202, configured to traverse the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component;
[0084] A description information importing module 203 is used to import each of the sub-function requirement components and the corresponding related requirement description information into a target database;
[0085] The component traversal module 204 is used to traverse the model function components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-function component;
[0086] The component matching module 205 is used to extract the sub-functional components and their corresponding requirement description information from the target database, and match each of the sub-functional components with each of the model sub-functional components to obtain a matching result, and according to the matching result and based on the requirement description information of each of the sub-functional components, update or construct the functional requirements of the model sub-functional components.
[0087] The technical solution of the embodiment of the present invention obtains the requirement description information of at least one sub-functional component by traversing the content of the functional requirement description document; importing each sub-functional component and its corresponding requirement description information into the target database, realizes the automatic import of the requirement function, improves the import efficiency, and facilitates the subsequent functional requirement construction. By traversing the model functional component in the process of developing the automotive electronic and electrical architecture, at least one model sub-functional component is obtained, the sub-functional component and its corresponding requirement description information are extracted from the target database, and each sub-functional component is matched with each model sub-functional component to obtain a matching result, and according to the matching result, based on the requirement description information of each sub-functional component, the functional requirements of the model sub-functional component are updated or constructed, realizing the automatic construction of the functional requirements of the sub-functional component, avoiding manual participation in the construction process, and improving the construction efficiency and construction accuracy. The probability of creation errors, hierarchical construction errors, and association errors or omissions in the manual construction process is reduced.
[0088] Optionally, the document content traversal module 202 includes:
[0089] A content traversal unit, used to traverse the content of the functional requirement description document according to preset field keywords, and obtain the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information of at least one functional component;
[0090] A sub-content extraction unit is used to extract sub-contents contained in the associated regulatory information and the associated demand use case information according to preset key special characters, so as to obtain the associated regulatory information and the associated demand use case information containing sub-contents;
[0091] A description information generating unit is used to generate functional description information including the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information.
[0092] Optionally, the component matching module 205 includes:
[0093] A component matching unit, used for matching each of the sub-functional components with each of the model sub-functional components, to obtain successfully matched model sub-functional components and unmatched model sub-functional components that failed to match in the model sub-functional components;
[0094] An information judgment unit, for judging, for the matched model sub-function component, whether the hierarchical information of the matched model sub-function component is consistent with the hierarchical information in the requirement description information of the sub-function component that has been successfully matched with it;
[0095] Other information judgment unit, used for judging whether the requirement description information, associated regulatory information and associated demand use case information of the matched model sub-function component are respectively consistent with the requirement description information, associated regulatory information and associated demand use case information of the successfully matched sub-function component if the hierarchical information is consistent;
[0096] The first component updating unit is used to update or construct the functional requirements of the model sub-functional component according to the requirement description information, associated regulatory information and associated requirement use case information in the requirement description information of the sub-functional component that successfully matches it, if there is inconsistency.
[0097] Optionally, the component matching module 205 further includes:
[0098] The second construction update unit is used to update the hierarchical information of the matched model sub-functional component using the requirement description information of the sub-functional component that has been successfully matched with it, if the hierarchical information of the matched model sub-functional component is inconsistent with the hierarchical information in the requirement description information of the sub-functional component that has been successfully matched with it, so as to realize the update of the functional requirements of the model sub-functional component.
[0099] Optionally, the component matching module 205 further includes:
[0100] A target source component determining unit, configured to determine, for the matched model sub-function component, a target source component associated with the matched model sub-function component;
[0101] A reference source component determination unit, configured to determine a reference source component according to associated regulatory information in the requirement description information of a sub-functional component that successfully matches the matched model sub-functional component;
[0102] A source component comparison unit, used for performing consistency comparison between the target source component and the reference source component to obtain a consistency comparison result;
[0103] The source component updating unit is used to update the target source component of the matched model sub-functional component according to the consistency comparison result.
[0104] Optionally, the device further comprises:
[0105] A cover information determination module is used for, after matching each of the sub-function components with each of the model sub-function components to obtain a matching result, and updating or constructing the functional requirements of the model sub-function components based on the matching result and the requirement description information of each of the sub-function components, selecting a target function component from the model sub-function components, and traversing the date-related information of the target function component according to a preset first attribute key field to obtain document cover information;
[0106] A preface information determination module, used to traverse the terminology related information of the target functional component according to a preset second attribute key field to obtain document preface information;
[0107] A description information determination module, used to traverse the function description information of the target function component according to a preset third attribute key field to obtain document function description information;
[0108] The specification document generation module is used to generate a functional requirement specification document according to the document cover information, the document preface information and the document function description information.
[0109] The device for automatically constructing functional requirements provided in the embodiment of the present invention can execute the method for automatically constructing functional requirements provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0110] Embodiment 3
[0111] Figure 3 A schematic diagram of the structure of an electronic device 30 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0112] like Figure 3As shown, the electronic device 30 includes at least one processor 31, and a memory connected to the at least one processor 31, such as a read-only memory (ROM) 32, a random access memory (RAM) 33, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 31 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 32 or the computer program loaded from the storage unit 38 to the random access memory (RAM) 33. In the RAM 33, various programs and data required for the operation of the electronic device 30 can also be stored. The processor 31, the ROM 32, and the RAM 33 are connected to each other through a bus 34. An input / output (I / O) interface 35 is also connected to the bus 34.
[0113] A number of components in the electronic device 30 are connected to the I / O interface 35, including: an input unit 36, such as a keyboard, a mouse, etc.; an output unit 37, such as various types of displays, speakers, etc.; a storage unit 38, such as a disk, an optical disk, etc.; and a communication unit 39, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 39 allows the electronic device 30 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0114] The processor 31 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 31 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 31 executes the various methods and processes described above, such as the automatic construction method of functional requirements.
[0115] In some embodiments, the function requirement automatic construction method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 38. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 30 via the ROM 32 and / or the communication unit 39. When the computer program is loaded into the RAM 33 and executed by the processor 31, one or more steps of the function requirement automatic construction method described above can be performed. Alternatively, in other embodiments, the processor 31 can be configured to execute the function requirement automatic construction method in any other appropriate manner (for example, by means of firmware).
[0116] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0117] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0118] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0119] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0120] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0121] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0122] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.
[0123] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A method for automatically constructing functional requirements, characterized in that: include: Obtain functional requirement description document; Traversing the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component; Importing each of the sub-functional components and the corresponding requirement description information into a target database; Performing component traversal on model functional components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-functional component; Extract sub-functional components and their corresponding requirement description information from the target database, match each sub-functional component with each model sub-functional component to obtain a matching result, and update or construct the functional requirements of the model sub-functional components based on the matching result and the requirement description information of each sub-functional component.
2. The method according to claim 1, characterized in that The step of traversing the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component includes: According to preset field keywords, the functional requirement description document is traversed to obtain hierarchical information, requirement description information, associated regulatory information and associated requirement use case information of at least one functional component; For the associated regulatory information and the associated demand use case information, extract the sub-contents contained in the associated regulatory information and the associated demand use case information according to preset key special characters to obtain the associated regulatory information and the associated demand use case information containing the sub-contents; Generate functional description information including the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information.
3. The method according to claim 1, characterized in that The matching of each of the sub-functional components with each of the model sub-functional components to obtain a matching result, and updating or constructing the functional requirements of the model sub-functional components according to the matching result and based on the requirement description information of each of the sub-functional components, includes: Matching each of the sub-functional components with each of the model sub-functional components to obtain successfully matched model sub-functional components and unmatched model sub-functional components that failed to match in the model sub-functional components; For the matched model sub-function component, determining whether the hierarchical information of the matched model sub-function component is consistent with the hierarchical information in the requirement description information of the sub-function component successfully matched therewith; If yes, determine whether the requirement description information, associated regulatory information and associated demand use case information of the matched model sub-function component are respectively consistent with the requirement description information, associated regulatory information and associated demand use case information of the sub-function component that has been successfully matched; If not, the functional requirements of the model sub-functional component are updated or constructed according to the requirement description information, the associated regulatory information and the associated requirement use case information in the requirement description information of the sub-functional component that successfully matches it.
4. The method according to claim 3, characterized in that The method further comprises: If the hierarchical information of the matched model sub-functional component is inconsistent with the hierarchical information in the requirement description information of the successfully matched sub-functional component, the requirement description information of the successfully matched sub-functional component is used to update the hierarchical information of the matched model sub-functional component to achieve the update of the functional requirements of the model sub-functional component.
5. The method according to claim 3, characterized in that: The method further comprises: For the matched model sub-function component, determining a target source component having an association relationship with the matched model sub-function component; Determine a reference source component according to the associated regulatory information in the requirement description information of the sub-functional component that successfully matches the matched model sub-functional component; Performing consistency comparison between the target source component and the reference source component to obtain a consistency comparison result; According to the consistency comparison result, the target source component of the matched model sub-function component is updated.
6. The method according to claim 1, characterized in that After matching each of the sub-function components with each of the model sub-function components to obtain a matching result, and updating or constructing the functional requirements of the model sub-function components based on the matching result and the requirement description information of each of the sub-function components, the method further includes: Select a target functional component from the model sub-functional components, and traverse the date-related information of the target functional component according to a preset first attribute key field to obtain document cover information; According to the preset second attribute key field, the terminology related information of the target functional component is traversed to obtain the document preface information; According to the preset third attribute key field, the function description information of the target function component is traversed to obtain the document function description information; A functional requirement specification document is generated according to the document cover information, the document foreword information and the document function description information.
7. A functional requirement automatic construction device, characterized in that: include: Description document acquisition module, used to obtain functional requirement description documents; A document content traversal module, used to traverse the content of the functional requirement description document to obtain requirement description information of at least one sub-functional component; A description information import module, used to import each of the sub-functional components and its corresponding requirement description information into a target database; A component traversal module is used to traverse the model function components in the process of developing the automotive electronic and electrical architecture to obtain at least one model sub-function component; The component matching module is used to extract the sub-functional components and their corresponding requirement description information from the target database, and match each of the sub-functional components with each of the model sub-functional components to obtain a matching result, and according to the matching result and based on the requirement description information of each of the sub-functional components, update or construct the functional requirements of the model sub-functional components.
8. The device according to claim 7, characterized in that The document content traversal module includes: A content traversal unit, used to traverse the content of the functional requirement description document according to preset field keywords, and obtain the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information of at least one functional component; A sub-content extraction unit is used to extract sub-contents contained in the associated regulatory information and the associated demand use case information according to preset key special characters, so as to obtain the associated regulatory information and the associated demand use case information containing sub-contents; A description information generating unit is used to generate functional description information including the hierarchical information, requirement description information, associated regulatory information and associated requirement use case information.
9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for automatically constructing functional requirements according to any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for automatically constructing functional requirements according to any one of claims 1 to 6 when executed.