CN107741843A - A kind of inspection method and check device of embedded software Specification - Google Patents
A kind of inspection method and check device of embedded software Specification Download PDFInfo
- Publication number
- CN107741843A CN107741843A CN201710936607.4A CN201710936607A CN107741843A CN 107741843 A CN107741843 A CN 107741843A CN 201710936607 A CN201710936607 A CN 201710936607A CN 107741843 A CN107741843 A CN 107741843A
- Authority
- CN
- China
- Prior art keywords
- external interface
- output
- module
- list
- inspection
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of inspection method of embedded software Specification, wherein, including：Obtain the document information of embedded software Specification；Rule is checked according to the list of function input interface, fuction output interface list, external interface input list and the generation of external interface output listing；Document information is checked, obtains the first inspection result；Whether the title according to specified in software development document General Requirement inspection document information with software development document General Requirement corresponding to section number meets regulation, obtains the second inspection result；Check each demand entry whether demand properties, qualification attribute, criticality attribute and priority attribute content it is whether complete, obtain the 3rd inspection result；Outgoing inspection result.The invention also discloses a kind of check device of embedded software Specification.The inspection method of embedded software Specification provided by the invention, which has, checks that speed is fast, the high advantage of accuracy rate.
Description
Technical field
The present invention relates to the Examined effect field of Specification, more particularly to a kind of embedded software requirement specification
The inspection method of specification and a kind of check device of embedded software Specification.
Background technology
From the point of view of soft project, it is that software needs to determine one of embedded software Project Success whether principal element
Ask, the carrier of software requirement is Software Requirements Specification (also called requirements analysis), it is therefore desirable to Software Requirements Specification (also called requirements analysis) is checked, carried
The quality of high Software Requirements Specification (also called requirements analysis), foundation is provided for the activity such as follow-up Software for Design, realization and checking.
At present, the inspection for Software Requirements Specification (also called requirements analysis) is mainly that project personnel are entered by the method for hand inspection
OK, time-consuming and easily produces mistake for this kind of method.
Therefore, how Software Requirements Specification (also called requirements analysis) quickly and accurately check and turn into those skilled in the art
Technical problem urgently to be resolved hurrily.
The content of the invention
It is contemplated that at least solves one of technical problem present in prior art, there is provided a kind of embedded software demand
The inspection method of description and a kind of check device of embedded software Specification, to solve in the prior art
The problem of.
As the first aspect of the invention, there is provided a kind of inspection method of embedded software Specification, its
In, the embedded software Specification includes multiple demand entries, and each demand entry has unique mark
Knowledge number, the inspection method includes：
The document information of embedded software Specification is obtained, wherein the document information includes：Function input interface
List, fuction output interface list, external interface input list, external interface output listing, section number and title list；
According to the function input interface list, fuction output interface list, external interface input list and external interface output
List generation checks rule；
Check that rule is checked the document information according to described, obtain the first inspection result；
Checked according to software development document General Requirement in the document information with being advised in the software development document General Requirement
Whether the title corresponding to fixed section number meets regulation, obtains the second inspection result；
Check whether in demand properties, qualification attribute, criticality attribute and priority attribute of each demand entry
Whether appearance is complete, obtains the 3rd inspection result；
Export first inspection result, second inspection result and the 3rd inspection result.
Preferably, the inspection rule includes：
Check whether each external interface input variable is inputted by function to use；
Check whether each external interface output variable is produced by fuction output；
Check whether each function input variable is produced by the fuction output of external interface input or remaining functional module；
Check whether each fuction output variable is inputted by the function of external interface output or remaining functional module to use；
Check whether the function input variable of each functional module is used in the module；
Check whether the fuction output variable of each functional module is used in the module；
Check in same " function input " or " external interface input " entry with the presence or absence of the interface variables repeated；
Check in same " fuction output " or " external interface output " entry with the presence or absence of the interface variables repeated.
Preferably, first inspection result includes：
Each external interface input variable is inputted by function to be used, or at least one external interface input variable is not by function
Input uses；
Each external interface output variable is produced by fuction output, or at least one external tapping output variable is not by function number
Go out to produce；
Each function input variable is inputted by external interface or the fuction output of remaining functional module produces, or at least one work(
Fuction output of the energy input variable not by external interface input or remaining functional module produces；
Each fuction output variable is exported by external interface or the function of remaining functional module is inputted and used, or at least one work(
Energy output variable is not inputted by the function of external interface output or remaining functional module and used；
The function input variable of each functional module is used in the module, or the function input of at least one functional module
Variable is not used in the module；
The fuction output variable of each functional module is used in the module, or the fuction output of at least one functional module
Variable is not used in the module；
The interface variables repeated, or same " function in same " function input " or " external interface input " entry be present
The interface variables repeated are not present in input " and " external interface input " entry；
The interface variables repeated, or same " function in same " fuction output " or " external interface output " entry be present
The interface variables repeated are not present in output " and " external interface output " entry.
Preferably, the 3rd inspection result includes：
Each demand entry whether demand properties, qualification attribute, criticality attribute and priority attribute content it is equal
For sky, or at least one demand entry whether demand properties, qualification attribute, criticality attribute and priority
At least one property content in property content is sky.
Preferably, when at least one demand entry whether demand properties, qualification attribute, criticality attribute and
At least one property content in priority attribute content is space-time, and it is endless that the identification number of the demand entry is added into attribute setting
Whole the results list.
Preferably, the software development document General Requirement is included in the document information of the Software Requirements Specification (also called requirements analysis)
The title of 32 specified chapters and sections, it is described according to software development document General Requirement check in the document information with it is described soft
Whether the title specified in part exploitation document General Requirement corresponding to section number, which meets regulation, includes being specified according to 32
The titles of chapters and sections check in the document information with the software development document General Requirement specified in 32 section numbers
Whether corresponding title meets regulation.
Preferably, second inspection result includes：
In the document information with the software development document General Requirement specified in title name corresponding to 32 section numbers
Claim the regulation for meeting the title of 32 specified chapters and sections, or lead in the document information with the software development document
The title corresponding at least one section number in title specified in requiring corresponding to 32 section numbers is not
Meet the regulation of the title of 32 specified chapters and sections.
As the second aspect of the invention, there is provided a kind of check device of embedded software Specification, its
In, the embedded software Specification includes multiple demand entries, and each demand entry has unique mark
Knowledge number, the check device includes：
Acquisition module, the acquisition module is used for the document information for obtaining embedded software Specification, wherein described
Document information includes：The list of function input interface, fuction output interface list, external interface input list, external interface output
List, section number and title list；
Rule generation module is checked, the inspection rule generation module is used for according to the function input interface list, function number
Outgoing interface list, external interface input list and the generation of external interface output listing check rule；
First checks module, and the first inspection module is used to check that rule checks the document information according to described,
Obtain the first inspection result；
Second checks module, and described second checks that module is used to check the document information according to software development document General Requirement
In with the software development document General Requirement specified in title corresponding to section number whether meet regulation, obtain
Two inspection results；
3rd checks module, the 3rd inspection module be used to checking each demand entry whether demand properties, qualified
Whether property attribute, criticality attribute and priority attribute content are complete, obtain the 3rd inspection result；
Output module, the output module are used to export first inspection result, second inspection result and the 3rd inspection
As a result.
The inspection method of embedded software Specification provided by the invention, by Software Requirement Specification
Book carries out the inspection of systematicness, obtains inspection result, and supporting item personnel analyze the reasonability of demand, and this inspection method can
Inspection result is quickly and accurately drawn, and avoids the generation that hand inspection produces error situation.
Brief description of the drawings
Accompanying drawing is for providing a further understanding of the present invention, and a part for constitution instruction, with following tool
Body embodiment is used to explain the present invention together, but is not construed as limiting the invention.In the accompanying drawings：
Fig. 1 is the flow chart of the inspection method of embedded software Specification provided by the invention.
Fig. 2 is that demand provided by the invention writes exemplary plot.
Fig. 3 is the flow chart of the document information of acquisition Software Requirements Specification (also called requirements analysis) provided by the invention.
Fig. 4 is the structure chart of the check device of embedded software Specification provided by the invention.
Embodiment
The embodiment of the present invention is described in detail below in conjunction with accompanying drawing.It should be appreciated that this place is retouched
The embodiment stated is merely to illustrate and explain the present invention, and is not intended to limit the invention.
As the first aspect of the invention, there is provided a kind of inspection method of embedded software Specification, its
In, the embedded software Specification includes multiple demand entries, and each demand entry has unique mark
Knowledge number, as shown in figure 1, the inspection method includes：
S110, the document information for obtaining embedded software Specification, wherein the document information includes：Function inputs
Interface list, fuction output interface list, external interface input list, external interface output listing, section number and title
List；
S120, list and external interface inputted according to the function input interface list, fuction output interface list, external interface
Output listing generation checks rule；
S130, according to it is described check rule the document information is checked, obtain the first inspection result；
S140, according to software development document General Requirement check in the document information with the software development document General Requirement
Specified in title corresponding to section number whether meet regulation, obtain the second inspection result；
S150, check each demand entry whether demand properties, qualification attribute, criticality attribute and priority category
Whether property content is complete, obtains the 3rd inspection result；
S160, output the first inspection result, second inspection result and the 3rd inspection result.
The inspection method of embedded software Specification provided by the invention, by Software Requirement Specification
Book carries out the inspection of systematicness, obtains inspection result, and supporting item personnel analyze the reasonability of demand, and this inspection method can
Inspection result is fast and accurately drawn, and avoids the generation that hand inspection produces error situation.
Specifically, the inspection rule includes：
Check whether each external interface input variable is inputted by function to use；
Check whether each external interface output variable is produced by fuction output；
Check whether each function input variable is produced by the fuction output of external interface input or remaining functional module；
Check whether each fuction output variable is inputted by the function of external interface output or remaining functional module to use；
Check whether the function input variable of each functional module is used in the module, that is, check that the function input of extraction becomes
The necessity of amount；
Check whether the fuction output variable of each functional module is used in the module, that is, check that the fuction output of extraction becomes
The necessity of amount；
Check in same " function input " or " external interface input " entry with the presence or absence of the interface variables repeated, that is, check and carry
The redundancy of the input interface taken；
Check in same " fuction output " or " external interface output " entry with the presence or absence of the interface variables repeated, that is, check and carry
The redundancy of the output interface taken.
It is understood that after above-mentioned inspection rule is generated, according to automatic one of inspection rule then pair of one
The document information is checked that not only quick but also accuracy rate is high.
Specifically, first inspection result includes：
Each external interface input variable is inputted by function to be used, or at least one external interface input variable is not by function
Input uses；
Each external interface output variable is produced by fuction output, or at least one external tapping output variable is not by function number
Go out to produce；
Each function input variable is inputted by external interface or the fuction output of remaining functional module produces, or at least one work(
Fuction output of the energy input variable not by external interface input or remaining functional module produces；
Each fuction output variable is exported by external interface or the function of remaining functional module is inputted and used, or at least one work(
Energy output variable is not inputted by the function of external interface output or remaining functional module and used；
The function input variable of each functional module is used in the module, or the function input of at least one functional module
Variable is not used in the module；
The fuction output variable of each functional module is used in the module, or the fuction output of at least one functional module
Variable is not used in the module；
The interface variables repeated, or same " function in same " function input " or " external interface input " entry be present
The interface variables repeated are not present in input " and " external interface input " entry；
The interface variables repeated, or same " function in same " fuction output " or " external interface output " entry be present
The interface variables repeated are not present in output " and " external interface output " entry.
It should be noted that after checking the document information, obtained the first inspection result include it is above-mentioned its
In two kinds of results in a situation any one combination of any one with two kinds of results in other, therefore,
One inspection result includes a variety of situations.
Specifically, the 3rd inspection result includes：
Each demand entry whether demand properties, qualification attribute, criticality attribute and priority attribute content it is equal
For sky, or at least one demand entry whether demand properties, qualification attribute, criticality attribute and priority
At least one property content in property content is sky.
Further specifically, when at least one demand entry whether demand properties, qualification attribute, criticality category
Property and priority attribute content at least one of property content be space-time, the identification number of demand entry addition attribute is set
Put imperfect the results list.
Specifically, the software development document General Requirement is included in the document information of the Software Requirements Specification (also called requirements analysis)
The title of 32 specified chapters and sections, it is described according to software development document General Requirement check in the document information with it is described soft
Whether the title specified in part exploitation document General Requirement corresponding to section number, which meets regulation, includes being specified according to 32
The titles of chapters and sections check in the document information with the software development document General Requirement specified in 32 section numbers
Whether corresponding title meets regulation.
Further specifically, second inspection result includes：
In the document information with the software development document General Requirement specified in title name corresponding to 32 section numbers
Claim the regulation for meeting the title of 32 specified chapters and sections, or lead in the document information with the software development document
The title corresponding at least one section number in title specified in requiring corresponding to 32 section numbers is not
Meet the regulation of the title of 32 specified chapters and sections.
On realizing the inspection method of the embedded software Specification, it is preferable that can be by demand
Write in management tool DOORS softwares and management software Specification is realized.Realizing the instrument of the program can make
With DXL Programming with Pascal Language complete, after the completion of instrument run in DOORS softwares.
Below to be write in DOORS softwares and management software Specification, and completed by DXL Programming with Pascal Language
The inspection method of the embedded software Specification is illustrated exemplified by the instrument.
Software Requirement Specification is write in DOORS softwares, the example of write method is as shown in Figure 2：
First, the entry of demand, " must [SHALL] " keyword must be included in the content of text of entry；
The interface of function input is write in an entry, and form is as " function inputs：Function input interface A, function input interface B,
Function input interface C ", between each interface variables with ", " separate, end not add "." etc. symbol；
The interface of fuction output is write in an entry, form such as " fuction output：Fuction output interface A, fuction output interface B,
Fuction output interface C ", between each interface variables with ", " separate, end not add "." etc. symbol；
" function treatment：" want an independent entry；
The content of six key elements description will be present in the functional module of minimum, i.e., " the function input " of One function module is to " about
6 parts between beam condition " can not have title；
External interface is described relative to software configuration item, including external interface input and external interface output, outside
Interface inputs and the describing mode of external interface output is similar to function input and fuction output, the description inputted such as external interface
Form is " external interface inputs：Interface A, interface B, interface C ".
Acquisition for the document information of the Software Requirements Specification (also called requirements analysis), with reference to shown in Fig. 3, particular content is as follows：
Sequence of positions traversal requirements specification where entry object according to demand, for each demand entry pair
As being handled as follows：
a）The content of text for obtaining entry object first is that " Object Text " attributes, the ID number where entry are " Absolute
Number " attributes, " Object Number " property contents, the title content i.e. " Object of entry object of entry object
Heading " attributes；
b）Judge entry " Object Text " property contents whether there is keyword " function input ", if it is present according to
Comma indicates to separate, by " function input interface name is arrived in each interface variables title storage in Object Text " property contents
Claim list, by entry object " Absolute Number " attributes storage arrive function input interface ID number list, continue executing with down
The acquisition of information of one entry object；If it does not, perform step c）；
c）Judge entry " Object Text " property contents whether there is keyword " fuction output ", if it is present according to
Comma indicates to separate, by " fuction output interface name is arrived in each interface variables title storage in Object Text " property contents
Claim list, by entry object " Absolute Number " attributes storage arrive fuction output interface ID number list, continue executing with down
The acquisition of information of one entry object；If it does not, perform step d）；
d）Judge entry " Object Text " property contents whether there is keyword " external interface input ", if it does,
Then indicated according to comma to separate, by " external interface is arrived in each interface variables title storage in Object Text " property contents
Input list, by entry object " Absolute Number " attributes storage to external interface input ID number list, continue executing with
The acquisition of information of next entry object；If it does not, perform step e）；
e）Judge entry " Object Text " property contents whether there is keyword " external interface output ", if it is present
Indicated according to comma to separate, by " each interface variables title storage in Object Text " property contents is defeated to external interface
Go out list, by entry object " Absolute Number " attributes storage to external interface output ID number list, continue executing with down
The acquisition of information of one entry object；If it does not, perform step f）；
f）Judge whether entry is title, if " symbol "-" is not present in Object Number " attributes, the entry is mark
Topic, by " section number list is arrived in the storage of Object Number " property contents, and " title name is arrived in the storage of Object Heading " attributes
Claim list, otherwise the entry is not title, without any processing.Continue executing with the acquisition of information of next entry object.
As the second aspect of the invention, there is provided a kind of check device of embedded software Specification, its
In, the embedded software Specification includes multiple demand entries, and each demand entry has unique mark
Knowledge number, as shown in figure 4, the check device 10 includes：
Acquisition module 110, the acquisition module 110 are used for the document information for obtaining embedded software Specification, its
Described in document information include：The list of function input interface, fuction output interface list, external interface input list, outside connect
Mouth output listing, section number and title list；
Check rule generation module 120, it is described inspection rule generation module 120 be used for according to the function input interface list,
Fuction output interface list, external interface input list and the generation of external interface output listing check rule；
First checks module 130, and described first checks that module 130 is used to check that rule carries out the document information according to described
Check, obtain the first inspection result；
Second checks module 140, and described second checks that module 140 is used to check the text according to software development document General Requirement
In shelves information with the software development document General Requirement specified in title corresponding to section number whether meet regulation,
Obtain the second inspection result；
3rd check module 150, it is described 3rd inspection module 150 be used for check each demand entry whether demand category
Whether property, qualification attribute, criticality attribute and priority attribute content are complete, obtain the 3rd inspection result；
Output module 160, the output module are used to export first inspection result, second inspection result and the 3rd inspection
Come to an end fruit.
The check device of embedded software Specification provided by the invention, by Software Requirement Specification
Book carries out the inspection of systematicness, obtains inspection result, and supporting item personnel analyze the reasonability of demand, and this inspection method can
Inspection result is fast and accurately drawn, and avoids the generation that hand inspection produces error situation.
It is understood that the principle that embodiment of above is intended to be merely illustrative of the present and the exemplary implementation that uses
Mode, but the invention is not limited in this.For those skilled in the art, the essence of the present invention is not being departed from
In the case of refreshing and essence, various changes and modifications can be made therein, and these variations and modifications are also considered as protection scope of the present invention.
Claims (8)
- A kind of 1. inspection method of embedded software Specification, it is characterised in that the embedded software demand rule Lattice specification includes multiple demand entries, and each demand entry has unique identification number, and the inspection method includes：The document information of embedded software Specification is obtained, wherein the document information includes：Function input interface List, fuction output interface list, external interface input list, external interface output listing, section number and title list；According to the function input interface list, fuction output interface list, external interface input list and external interface output List generation checks rule；Check that rule is checked the document information according to described, obtain the first inspection result；Checked according to software development document General Requirement in the document information with being advised in the software development document General Requirement Whether the title corresponding to fixed section number meets regulation, obtains the second inspection result；Check whether in demand properties, qualification attribute, criticality attribute and priority attribute of each demand entry Whether appearance is complete, obtains the 3rd inspection result；Export first inspection result, second inspection result and the 3rd inspection result.
- 2. the inspection method of embedded software Specification according to claim 1, it is characterised in that the inspection Looking into rule includes：Check whether each external interface input variable is inputted by function to use；Check whether each external interface output variable is produced by fuction output；Check whether each function input variable is produced by the fuction output of external interface input or remaining functional module；Check whether each fuction output variable is inputted by the function of external interface output or remaining functional module to use；Check whether the function input variable of each functional module is used in the module；Check whether the fuction output variable of each functional module is used in the module；Check in same " function input " or " external interface input " entry with the presence or absence of the interface variables repeated；Check in same " fuction output " or " external interface output " entry with the presence or absence of the interface variables repeated.
- 3. the inspection method of embedded software Specification according to claim 2, it is characterised in that described One inspection result includes：Each external interface input variable is inputted by function to be used, or at least one external interface input variable is not by function Input uses；Each external interface output variable is produced by fuction output, or at least one external tapping output variable is not by function number Go out to produce；Each function input variable is inputted by external interface or the fuction output of remaining functional module produces, or at least one work( Fuction output of the energy input variable not by external interface input or remaining functional module produces；Each fuction output variable is exported by external interface or the function of remaining functional module is inputted and used, or at least one work( Energy output variable is not inputted by the function of external interface output or remaining functional module and used；The function input variable of each functional module is used in the module, or the function input of at least one functional module Variable is not used in the module；The fuction output variable of each functional module is used in the module, or the fuction output of at least one functional module Variable is not used in the module；The interface variables repeated, or same " function in same " function input " or " external interface input " entry be present The interface variables repeated are not present in input " and " external interface input " entry；The interface variables repeated, or same " function in same " fuction output " or " external interface output " entry be present The interface variables repeated are not present in output " and " external interface output " entry.
- 4. the inspection method of embedded software Specification according to claim 1, it is characterised in that described Three inspection results include：Each demand entry whether demand properties, qualification attribute, criticality attribute and priority attribute content it is equal For sky, or at least one demand entry whether demand properties, qualification attribute, criticality attribute and priority At least one property content in property content is sky.
- 5. the inspection method of embedded software Specification according to claim 4, it is characterised in that when at least One demand entry whether in demand properties, qualification attribute, criticality attribute and priority attribute content extremely One item missing property content is space-time, and the identification number of the demand entry is added into attribute sets imperfect the results list.
- 6. the inspection method of embedded software Specification as claimed in any of claims 1 to 5, it is special Sign is, is specified for 32 in document information of the software development document General Requirement including the Software Requirements Specification (also called requirements analysis) The title of chapters and sections, it is described according to software development document General Requirement check in the document information with software development text Whether the title specified in shelves General Requirement corresponding to section number, which meets regulation, includes the mark according to 32 specified chapters and sections Inscribe described in Name check in document information with the software development document General Requirement specified in corresponding to 32 section numbers Whether title meets regulation.
- 7. the inspection method of embedded software Specification according to claim 6, it is characterised in that described Two inspection results include：In the document information with the software development document General Requirement specified in title name corresponding to 32 section numbers Claim the regulation for meeting the title of 32 specified chapters and sections, or lead in the document information with the software development document The title corresponding at least one section number in title specified in requiring corresponding to 32 section numbers is not Meet the regulation of the title of 32 specified chapters and sections.
- A kind of 8. check device of embedded software Specification, it is characterised in that the embedded software demand rule Lattice specification includes multiple demand entries, and each demand entry has unique identification number, and the check device includes：Acquisition module, the acquisition module is used for the document information for obtaining embedded software Specification, wherein described Document information includes：The list of function input interface, fuction output interface list, external interface input list, external interface output List, section number and title list；Rule generation module is checked, the inspection rule generation module is used for according to the function input interface list, function number Outgoing interface list, external interface input list and the generation of external interface output listing check rule；First checks module, and the first inspection module is used to check that rule checks the document information according to described, Obtain the first inspection result；Second checks module, and described second checks that module is used to check the document information according to software development document General Requirement In with the software development document General Requirement specified in title corresponding to section number whether meet regulation, obtain Two inspection results；3rd checks module, the 3rd inspection module be used to checking each demand entry whether demand properties, qualified Whether property attribute, criticality attribute and priority attribute content are complete, obtain the 3rd inspection result；Output module, the output module are used to export first inspection result, second inspection result and the 3rd inspection As a result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710936607.4A CN107741843A (en) | 2017-10-10 | 2017-10-10 | A kind of inspection method and check device of embedded software Specification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710936607.4A CN107741843A (en) | 2017-10-10 | 2017-10-10 | A kind of inspection method and check device of embedded software Specification |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107741843A true CN107741843A (en) | 2018-02-27 |
Family
ID=61237161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710936607.4A Pending CN107741843A (en) | 2017-10-10 | 2017-10-10 | A kind of inspection method and check device of embedded software Specification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107741843A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112381370A (en) * | 2020-11-03 | 2021-02-19 | 中国直升机设计研究所 | Demand distribution automation method based on DOORS system |
| WO2023284108A1 (en) * | 2021-07-12 | 2023-01-19 | 卡斯柯信号有限公司 | Demand conformity analysis method and system, and electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110255784A1 (en) * | 2010-01-15 | 2011-10-20 | Copanion, Inc. | Systems and methods for automatically extracting data from eletronic documents using multiple character recognition engines |
| CN102880926A (en) * | 2012-07-09 | 2013-01-16 | 华迪计算机集团有限公司 | Business information data auditing method and device |
| CN104965956A (en) * | 2015-07-16 | 2015-10-07 | 北京航空航天大学 | RUCM based demand verification method |
| CN106033392A (en) * | 2015-03-13 | 2016-10-19 | 上海爱韦讯信息技术有限公司 | Method and device for detecting based on inspection word requirement |
-
2017
- 2017-10-10 CN CN201710936607.4A patent/CN107741843A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110255784A1 (en) * | 2010-01-15 | 2011-10-20 | Copanion, Inc. | Systems and methods for automatically extracting data from eletronic documents using multiple character recognition engines |
| CN102880926A (en) * | 2012-07-09 | 2013-01-16 | 华迪计算机集团有限公司 | Business information data auditing method and device |
| CN106033392A (en) * | 2015-03-13 | 2016-10-19 | 上海爱韦讯信息技术有限公司 | Method and device for detecting based on inspection word requirement |
| CN104965956A (en) * | 2015-07-16 | 2015-10-07 | 北京航空航天大学 | RUCM based demand verification method |
Non-Patent Citations (1)
| Title |
|---|
| 中华人民共和国国家质量监督检验检疫总局 中国国家标准化管理委员会: "《计算机软件文档编制规范》", 30 September 2006, 中国标准出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112381370A (en) * | 2020-11-03 | 2021-02-19 | 中国直升机设计研究所 | Demand distribution automation method based on DOORS system |
| WO2023284108A1 (en) * | 2021-07-12 | 2023-01-19 | 卡斯柯信号有限公司 | Demand conformity analysis method and system, and electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9141521B2 (en) | Method and apparatus for automatically generating a test script for a graphical user interface | |
| US9720811B2 (en) | Unified model for visual component testing | |
| Li et al. | A framework for automatic DFA system development | |
| CN103310315A (en) | Automatic process approval tool based on workflows | |
| Yang et al. | The perimeter loop-based method for the automatic isomorphism detection in planetary gear trains | |
| Bettenburg et al. | A lightweight approach to uncover technical artifacts in unstructured data | |
| CN107741843A (en) | A kind of inspection method and check device of embedded software Specification | |
| Digmayer et al. | Employee Empowerment in the Context of domain-specific Risks in Industry 4.0 | |
| CN103631710A (en) | Software specification development supporting method and device | |
| Braun et al. | A methodology for the detection of functional relations of mechatronic components and assemblies in brownfield systems | |
| US7853442B2 (en) | Printed circuit board design instruction support method and device | |
| Bezsmertnyi et al. | Behavior driven development approach in the modern quality control process | |
| CN109298686A (en) | System and method for using business intelligence for rule-based design and manufacture technology | |
| CN108008700A (en) | Information processor | |
| CN104216986A (en) | Device and method for improving data query efficiency through pre-operation according to data update period | |
| CN104764455B (en) | A kind of data in navigation electronic map processing method and processing device | |
| US11327471B2 (en) | Building and tracking of an automation engineering environment | |
| CN109872080A (en) | A kind of aircraft assembly coordination rule knowledge management method and system | |
| CN110275707A (en) | A kind of PLC variable input method of compatible table input and text input | |
| US8661399B1 (en) | Built-in-self-test (BIST) organizational file generation | |
| Nopanen | Unifying cybersecurity requirements in Automation Projects | |
| Saunders et al. | Identifying measurement knowledge and its relationship to engineering design | |
| Hood et al. | A fast, complete method for automatically assigning causality to bond graphs | |
| Abbas et al. | Keywords-based test categorization for Extra-Functional Properties | |
| CN110807282B (en) | Method and apparatus for defining materials and properties in finite element pre-processing |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180227 |