CN105868115A - Building method and system for software test model of software intensive system - Google Patents
Building method and system for software test model of software intensive system Download PDFInfo
- Publication number
- CN105868115A CN105868115A CN201610211548.XA CN201610211548A CN105868115A CN 105868115 A CN105868115 A CN 105868115A CN 201610211548 A CN201610211548 A CN 201610211548A CN 105868115 A CN105868115 A CN 105868115A
- Authority
- CN
- China
- Prior art keywords
- software
- ontology
- information
- fmea
- model
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a building method and system for a software test model of a software intensive system. The method comprises the steps that 1, a multi-ontology structure comprising a domain ontology, an application ontology, an ontology expression language and an ontology editing tool of software FMEA information is built; 2, various layers of ontologies of the software FMEA information are built for the multi-ontology structure, elements of software FMEA information ontologies are set, and the mapping relations between the ontologies in different layers are determined; according to the mapping relations, the element of each layer of ontology information is described, and a software FMEA information ontology model based on a domain is obtained; 4, a qualitative evaluation method is utilized for evaluating the quality level of the software FMEA information ontology model, and the quality measurement level of the domain ontology is determined. The software testing model meeting SISs test requirements is built, software FMEA quality is improved, and variability of an analysis result is reduced.
Description
Technical field
The present invention relates to software testing technology field, particularly relate to a kind of software intensive systems soft ware test model
Construction method and system.
Background technology
Software is enable factor and the driver of New Economy.Along with software product is in the extensive application of every field, its matter
Amount is also increasingly becoming focus of concern.Software test is the important means that software quality is effectively ensured.Statistics shows, in allusion quotation
In the development project of type, the workload of software test often accounts for more than the 40% of software development amount of work.With the U.S.
As a example by the average fund input of software development and production, it is common that " demand analysis " and " planning determines " respectively accounts for 3%, and " design " accounts for
5%, " programming " accounts for 7%, and " test " accounts for 15%, and " go into operation and safeguard " accounts for 67%.The status of software test has some idea of.Software is asked
Topic the most early finds, amendment cost is the lowest, and destructiveness is the least.So, as often as possible to pinpoint the problems before product is issued, solve to ask
Topic.And its means are exactly sufficiently to test planned and organizedly.
Software test is the activity a series of planned, systematic being closely related with software development, as software development
Having process model the same, software test is also required to corresponding test model and removes Guiding Practice.Software Testing Models describes software
Relation between main activity that test process is comprised and activity, and Activities and the software development process of software test are described
Other activities between relation.By test model, software test personnel and the relevant personnel it will be seen that when test starts, what
Time terminate, test process includes which is movable, need what resource etc..When software test is planned, be according to test purpose, institute
The developing process model used and organization condition etc. choose suitable test model.It is born between the decades of software development development
A lot of development models.But in these models, in general software test is only used as a stage of software development, is attached to
After development model.In recent years, along with the raising to software test understanding of importance, in succession occur in that some new test moulds
Type, the most representative includes: V model, W model, X model etc..
Additionally, due to the current information world is the brightest and the clearest with the trend that physical world, informationization and industrialization are merged, SISs
Progressively become the developing direction of large-scale complicated system.How to develop corresponding test model the test job of SISs is referred to
Lead, and then ensure that the requirement of its qualitative attribute is a problem demanding prompt solution.The usual structure of SISs is complicated, functional coverage is wide；
There is high reliability, high security requirement；Additionally, the opening of its local environment and uncertainty；Between system component and system
And complexity mutual between environment；And the unpredictability of relevant operating condition, scene and the environment of software and system all increases
The difficulty that SISs test model builds.For this kind of system, the most widely used test model is W model.But,
The These characteristics of SISs makes W model there is also deficiency.Although W model specify that demand, design phase are also required to carry out accordingly
Test activity, tester needs to participate in Project design and carries out testing ensureing pinpoint the problems as early as possible and correct simultaneously, but this
In current practice relatively difficult to achieve.This is mainly due to lacking effective knowledge between software developer and tester altogether
Enjoy bridge.In actual application, some software developers lack software system Problem Areas relevant knowledge, and therefore they will be according to certainly
Oneself understanding exploitation requirements specification, the partial content that is likely to result in demand by error understanding, is caused low quality demand to be advised by this
Generation about.And the domain knowledge that software test personnel are possessed and correlation experience due to and uncured get off, it is impossible to provide
Guidance is provided to software developer and for development activities.Additionally, the high complexity of SISs also exacerbates developer and test
The difficulty linked up between personnel.
As it is shown in figure 1, Fig. 1 is V software test model structure chart.The left side represents development process each stage, the right represent with
Test process each stage of correspondence.Test process is initial with unit testing, and test subsequently is followed successively by: integration testing, be
Unified test examination and Acceptance Test.V model is as a kind of relatively simple Software Testing Models, it is adaptable to non-secure software or quickly open
Send out, aid is developed and software test on a small scale.Its advantage is the different phase clearly designating test process, and clearly
Describe these test phases and the corresponding relation in development process each stage.
The shortcoming of V model is:
(1) in this model, Experience of Software Testing Work starts later.Under normal circumstances, test activity is just opened after coding completes
Beginning, be unfavorable for that the early stage of defect positions and corrects, this will be greatly improved the cost of software development.Additionally, also easily cause understanding
On mistake, software test is the last stage of software life-cycle to make people be interpreted as.
(2) user easily takes for software test is only the correctness testing code, have ignored demand and design rank
The test job of section, causes the defect that these non-codings stage produces not to be discovered in an early phase, and the Acceptance Test for the later stage is buried
Lower hidden danger.And it is big to find that when Acceptance Test these problems not only revise difficulty, and expense is compared and is greatly improved in early days, also increases
The big probability of project failure.
(3) group to be tested submits defect report to after software developer has encoded etc., revises the most on this basis
Program.This, by reducing the utilization rate of human resources, is also unfavorable between group that cooperate and know together reaches.
As in figure 2 it is shown, Fig. 2 is software test W model structure figure.Based on V model, increase and software each development phase
Synchronize corresponding test process and just define W model.W model is to supplement V model, the most double " V " model, and supplementing software needs
Ask the test job in each stage such as analysis phase, design phase, be explicitly shown demand analysis stage, the design phase is also required to
Carry out corresponding test activity.The feature of W model is " carrying out software test as soon as possible and constantly ", and it highlights tester
Participation to Project design and it needs to carry out completely and sufficiently testing to respective stage, to ensure that the defect in each stage can be to the greatest extent
Early find and be modified.It is due to integrity and the adequacy of the higher tune test job of W model, long at some software development cycles,
Software saferank requires to use in height or complex software project, can ensure project quality.
The shortcoming of W model is: (1) is although this model specify that demand, design phase to be also required to accordingly and tests
Activity, tester needs participation Project design to carry out testing to ensure pinpoint the problems as early as possible and correct simultaneously, but this is currently
Engineering practice in relatively difficult to achieve.This is mainly due to lacking effective knowledge sharing between software developer and tester
Bridge, the angle that can only each stand in self field understands problem.
(2) high complexity of SISs also exacerbates the difficulty linked up between developer and tester.It is said that in general, SISs
The domain knowledge comprised is abnormal abundant, even relates to multiple different disciplines.Using W model, this kind of system is entered
During row test, owing to not taking into full account and testing closely-related domain knowledge so that test effect is the most not fully up to expectations.
(3) being not through a kind of effective means solidification due to aforementioned domain knowledge, therefore test quality greatly relies on
In the experience of tester, it is easily caused test quality and there is bigger undulatory property.
As it is shown on figure 3, Fig. 3 is software test X model structure figure.X model is first " decomposition " by whole program, rear " integration ".
Usability of program fragments is tested, after having tested, is progressively integrated into fairly large program in machine code by various handing-over activities,
Whole target is all to be integrated into an executable software.As can be seen here, for comparing other models, X model is the most flexible,
It is also proposed the method for testing of this worth reference of exploratory testing.And this exploratory testing is not the spy planned sth. ahead
The test of different type so that test can be not limited to method of testing itself.
The shortcoming of X model includes:
(1) test may be caused the wave of human and material resources and financial resources by the essence of the feature of this model flexibility and exploration
Take, increase testing cost.
(2) proficiency level of tester is required higher.
(3) do not have to embody the test process movable to demand, design etc., for fail-safe software, do not possess test completeness
And adequacy.
In sum, existing test model is difficult to highlight the importance of domain knowledge, hinders between multiple stakeholder
Communication, it is necessary to propose a kind of be applicable to SISs test need Software Testing Models.
Summary of the invention
Based on this, it is necessary to for above-mentioned technical problem, it is provided that the structure of a kind of software intensive systems soft ware test model
Construction method and system, it is adaptable to the software test that SISs test needs, improve the quality of software test.
The construction method of a kind of software intensive systems soft ware test model, comprises the steps:
(1) build many body constructions of software FMEA information, including: domain body, applied ontology, Ontology specification languages and
Ontology Editing Tool；
(2) described many body constructions are constructed software FMEA information each layer body, set wanting of software FMEA Information Ontology
Element and determine the mapping relations between each layer body；
(3) according to described mapping relations, the key element of each layer ontology information is described, obtains software based on field
FMEA Information Ontology model；
(4) utilize qualitative evaluation method that the quality level of software FMEA Information Ontology model is evaluated, determine that field is originally
Weight metric levels.
A kind of constructing system of software intensive systems soft ware test model, including:
Framework establishment module, for building many body constructions of software FMEA information, including: domain body, applied ontology,
Ontology specification languages and Ontology Editing Tool；
Ontological construction module, for described many body constructions are constructed software FMEA information each layer body, sets software
The key element of FMEA Information Ontology and determine the mapping relations between each layer body；
Ontology definition module, for being described the key element of each layer ontology information according to described mapping relations, obtains base
Software FMEA Information Ontology model in field；
Ontology evaluation module, for utilizing qualitative evaluation method to comment the quality level of software FMEA Information Ontology model
Valency, determines domain body quality metric level.
The construction method of above-mentioned software intensive systems soft ware test model and system, by building software FMEA information
Many body constructions, construct software FMEA information each layer body, define its key element and determine the mapping relations between each layer body,
The key element of each layer ontology information is described, forms software FMEA Information Ontology model based on field, finally to software
The quality level of FMEA Information Ontology model is evaluated determining domain body quality metric level.This technical scheme constructs suitable
The Software Testing Models needed for SISs test, improves the quality of software FMEA and reduces the undulatory property of analysis result.
Accompanying drawing explanation
Fig. 1 is V software test model structure chart；
Fig. 2 is software test W model structure figure；
Fig. 3 is software test X model structure figure；
Fig. 4 is the Software Testing Models based on domain knowledge of an embodiment；
The construction method flow chart of the software intensive systems soft ware test model that Fig. 5 present invention provides；
Fig. 6 is the structure chart of FMEA many ontology knowledge structure；
Fig. 7 is that FMEA Information Ontology builds flow chart；
Fig. 8 is FMEA Information Ontology illustraton of model；
Fig. 9 is software FMEA ontology evaluation index schematic diagram；
Figure 10 is software FMEA quality evaluation flow chart；
Figure 11 is radar system basic block diagram；
Figure 12 is radar system schematic diagram of the function；
Figure 13 is certain type radar system functional hierarchy and layer of structure corresponding diagram；
Figure 14 is for drawing mission reliability block diagram；
Figure 15 is the exemplary plot that certain type task electronic system indenture level divides；
The constructing system structural representation of the software intensive systems soft ware test model that Figure 16 provides for the present invention.
Detailed description of the invention
The construction method of the software intensive systems soft ware test model of the present invention is illustrated below in conjunction with the accompanying drawings with embodiment
And system.
Technical scheme, is considered as the knowledge series being made up of a series of knowledge by software, and these knowledge are pressed
According to they processing modes to particular problem, being divided into a series of knowledge point, knowledge point is the elementary cell of composition software.
Fig. 4 is the Software Testing Models based on domain knowledge of an embodiment, can be referred to as Y model.This figure shows,
No matter the test in which stage, all comprise test definition, test design, test execution, test summary and acceptance phase.Meanwhile,
It is required for setting up domain knowledge ontology library and software FMEA ontologies in the test definition stage.Below with demand test phase
Its concrete grammar set up and process is introduced as a example by corresponding software FMEA ontologies.
Software FMEA refers to analyze all possible fault mode of software product and issuable impact thereof, and by each
A kind of reductive analysis method that the order of severity of fault mode generation impact and probability of happening thereof are classified.Its objective is to pass through
Analyze design defect and the weak link of software product, improve software product dependability, and for carry out changing of software product
Enter, retrofit or the offer foundation such as the development of new product and use and maintenance decision-making.
With reference to the construction method flow chart of the software intensive systems soft ware test model that Fig. 5, Fig. 5 present invention provides, bag
Include following steps:
Step (1), builds many body constructions of software FMEA information, including: domain body, applied ontology, ontology representation
Language and Ontology Editing Tool；
Concrete, on the basis of KADS (Knowledge Aided Design System), obtain software FMEA knowledge many
Body construction, retain KADS knowledge hierarchy and divide clear and have the good maintainable and advantage of reusability, it is to avoid knowledge
Level integraty difference and the incomplete shortcoming of domain knowledge.
With reference to shown in Fig. 6, Fig. 6 is the structure chart of FMEA many ontology knowledge structure, further, by knowledge in step (1)
Source information obtains domain body, and described domain body is carried out the applied ontology that instantiation obtains；
Described domain body includes that static body and dynamic ontology, static body include concept, attribute, relational factors
Description information；Dynamic ontology includes event, the description information of active operation stream；
Wherein, described knowledge source information includes:
1. the fault message extracted in Design of Reliability analysis, test and practical service environment；
2. the empirical and systematicness information obtained from experts database and specific software qualitative data；
3. the exemplary running software time/state FMEA information extracted from document；
4. the restrictive information extracted from industry standard, regulation.
Additionally, due to the existence form of software field knowledge is varied, including Explicit Knowledge and implicit knowledge, therefore lead to
Cross employing software field body by the implicit knowledge domination in field.
Described many body constructions are constructed software FMEA information each layer body by step (2), set software FMEA Information Ontology
Key element and determine the mapping relations between each layer body；
As an embodiment, as it is shown in fig. 7, Fig. 7 is FMEA Information Ontology builds flow chart, further, step (2)
Can include the following: based on above-mentioned many ontology knowledge structure, according to sequential configuration each layer body of " field layer-application layer ".Fixed
The justice key element such as the concept of each layer body, inheritance hierarchy, association, attribute, rule, example clear and definite, without ambiguous definition and each layer
Mapping relations between body.
(3) according to described mapping relations, the key element of each layer ontology information is described, obtains software based on field
FMEA Information Ontology model；
With reference to shown in Fig. 8, Fig. 8 is FMEA Information Ontology illustraton of model, as an embodiment, defines according to ontologies,
In conjunction with the own characteristic of software FMEA, the definition of its ontologies can be such that
1. software FMEA Information Ontology can be: SFMEA Ontology=< C, AC,R,AR, H, I >, wherein C is concept
Collection, ACFor the property set of each concept, R is set of relations, ARFor the property set of each relation, H is concept hierarchy, and I is example set.
Each concept C in the most described concept set CiFor representing a group objects of identical type, and with identical attribute
Collection is described；
For SISs, under the development trend that software and hardware is combined closely, local environment condition high by its complexity and be
The fault that the class that the most expected feature of system operation is caused is caused by software and hardware comprehensive function especially to draw attention, as
The fault etc. that fault that fault that electromagnetic interference causes, temperature stress cause, vibration stress cause.These faults are the most also with many
Kind of stress resultant or the stress form appearance comprehensive with operation.This kind of fault should be analysed in depth its mechanism of production, including leading
Cause the root that fault produces, communication process and generation environment, provide fault mode distribution.
The property set of the most described concept is AC(Ci), represent every attribute of fault mode example；As incipient fault consequence,
Severity grade (Severity), probability of happening (Occurrence Probabilities) and detection method (Detection
Mechanism) etc..
The most described relation is Ri(Cp,Cq), represent each relation in relation R, riRepresent concept CpAnd CqBetween binary
Associate, and the example of this relation is a pair conceptual object (Cp,Cq)。
The property set A of the most described relationR(ri) be used for representing relation riAttribute；In software FMEA body, between concept
Attribute of a relation has part-of, instance-of, attribute-of etc..
The most described concept hierarchy H, for representing the concept hierarchy of concept set C, and is one group of father and son between concept in C
Or " parent-subclass " relation；Such as, if CqIt is CpSubclass or sub-concept, then (Cp,Cq)∈H.It is true that concept hierarchy H is also
The inheritance between parent and subclass can be regarded as；If inheritance is defined as: in software FMEA ontologies concept class hierarchy
Subclass shares the mechanism of parent attribute and structure automatically.So subclass under non-terminal concept class constitutes inheritance with parent.
This shows to realize a new class on the basis of existing concept class, based on the content of existing class, and adds some new contents,
Inheritance in concept related is partial ordering relation.
7. example set I, represents the instantiation supporting concept with relation.
(4) utilize qualitative evaluation method that the quality level of software FMEA Information Ontology model is evaluated, determine that field is originally
Weight metric levels.
Carry out cutting and integration according to evaluation of ontology index, refer to as it is shown in figure 9, Fig. 9 is software FMEA ontology evaluation
Indicating and be intended to, in conjunction with conventional practical experience, ontology evaluation only focuses on the evaluation to body self, in not considering that body is built
Other indexs such as construction cost etc..
As an embodiment, can use qualitative evaluation method that software FMEA body quality level is evaluated, reference
Shown in Figure 10, Figure 10 is software FMEA quality evaluation flow chart, and step (4) may include that
(4-1) according to qualitative evaluation mapping rule, obtaining the qualitative score value of domain body quality level, structure passes judgment on square
Battle array；
Concrete, the qualitative scoring knot of domain body quality level according to certain qualitative evaluation mapping rule, can be obtained
Really, this process need to can include following step by expertise:
1. half trapezoidal profile and the membership function of trapezoidal profile structure credit rating { poor, in, good } are used；
If domain U={ is poor, in, good }, A is index fuzzy subset on domain U, structure membership function:
2. according to tolerance uiComputation measure uiThe qualitative evaluation integrated value of levelWherein, M is special
Family, k is that expert numbers；R (i) is substituted into membership function A1(r)、A2(r)、A3R (), calculates the horizontal mould of each metric
Stick with paste comprehensive evaluation result, described Fuzzy Comprehensive Evaluation result is normalized, obtain constructing Judgement Matrix.
(4-2) acquisition affects the weight of domain body quality metric level；
(4-3) according to described Judgement Matrix and weight and utilize Field Using Fuzzy Comprehensive Assessment to determine domain body quality metric water
Flat；
Formula in described Field Using Fuzzy Comprehensive Assessment can be such that
Wherein, RU (i) is domain body quality metric level.
Step (4-1) in above-mentioned ontologies constructing plan, the basic thought of (4-2) are carrying out body to different field
During structure equally applicable, differ only in the particular contents such as concept, attribute and association that different field relates to different, scheme
Middle step (4-3) basic definition also has universality.
In order to become apparent from the application of technical solution of the present invention, it is illustrated below in conjunction with an example.
As a example by radar system, provide a SISs based on body below run the application case of time/state FMEA method
Example.
First briefly introducing radar system, as shown in figure 11, Figure 11 is radar system basic block diagram.Radar is
A kind of special radio observation equipment, may be used to find the position of target to be measured.If its range is reduced, i.e.
It it is the radiotechnics instrument of a kind of azimuth-range measuring passive moving target (such as aircraft, warship).Its basic task is
Detect target interested, measure the state parameters such as the distance about target, Fang Wen, speed, mainly by antenna, transmitter, connect
The part composition such as receipts machine, signal processor, data process machine, indicator and display.
According to different criteria for classifications, radar can be divided into polytype.Additionally, according to practical experience at environment/reliable
Property test or outfield find based on run time/state radar dependent failure limited amount, far less than traditional type
Fault.Therefore, the radar of particular type is not made a distinction by the example of a FMEA given below, but for a certain kind
The class fault that stress is relevant is analyzed, and determines the impact on radar system resultant fault of this stress.
(1) system definition；
(1) functional analysis:
With reference to shown in Figure 12, Figure 12 is radar system schematic diagram of the function, the radar subsystem of certain type task electronic system
Function is detection target and measures the state parameters such as the distance about target, Fang Wen, speed.Task is detection target.Figure is watched
The empty wire frame representation not all radar of this part of dress system all has, and does not the most have servosystem such as phased-array radar, and
Indicator and display part are the most more often classified as the class in avionics system.
(2) functional block diagram, mission reliability block diagram are drawn:
As shown in figure 13, Figure 13 is certain type radar system functional hierarchy and layer of structure corresponding diagram；Draw functional block
Scheme certain type radar system functional hierarchy and layer of structure corresponding diagram.
With reference to shown in Figure 14, Figure 14 is for drawing mission reliability block diagram, the mission reliability block diagram of certain type radar system.
(2) indenture level；
As shown in figure 15, Figure 15 is the exemplary plot that certain type task electronic system indenture level divides, and initial indenture level is
Aircraft；Indenture level is radar system；Minimum indenture level is antenna (10), transmitter (20) ..., controller (60) etc..
(3) severity definition；
In general, the system on aircraft according to what the difference of the division of labor can be roughly classified into basic flight function is
System, such as power supply, electromotor, flight control system etc. and the system completing particular task, as task electronic system just include radar system,
The subsystem such as avionics system, electronic countermeasure.Although the system completing particular task in general will not be to basic flight function
Impact, but fighting efficiency can be exerted a decisive influence actual combat when, and then have influence on the reliability of aircraft system
And safety.Therefore, severity definition is given, as shown in table 1 based on fighting efficiency and basic service condition.
Table 1 severity classification and definition
(4) failure mode analysis (FMA)；
Radar system resultant fault pattern is mainly analyzed from for information about and is obtained.The ranking score of fault mode probability of happening
For A, B, C, D, E Pyatyi, it is specifically defined the regulation being shown in Table 2.
The grade classification of table 2 fault mode probability of happening
(5) FMEA table；
SISs FMEA method based on operation time/state is the expansion to traditional F MEA method.Risk index, risk
Level is shown in Table 3 and table 4 respectively.
Table 3 risk index defines
Table 4 risk level is classified
| Risk Assessment Code | Risk level | Interpretational criteria |
| 1-5 | High | Unacceptable |
| 6-9 | Seriously | It is not intended to (not accepting) |
| 10-17 | In | Acceptable (but need to be through evaluation) |
| 18-20 | Low | Acceptable |
Concrete analysis situation according to present case, fills in certain model radar system based on operation time/state comprehensive
FMEA table such as table 5.
Certain model radar system of table 5 is based on the comprehensive FMEA table running time/state
Initial indenture level: personnel: XXX approval: XXX analyzed by aircraft
Indenture level: radar system is audited: XXX
Date of filing: XXXX XX day month XX
Based on the fault data collected in practice, utilize FMEA method, identify all possible based on operation time/state
SISs fault mode, analyze fault mode Producing reason, analyze fault be likely to result in impact, determine danger seriousness
With probability (i.e. risk), eliminate or control the security critical product of dangerous fault, formulate and be efficiently modified measure, to improve
The reliability level of product.
Body gives concept and the association of specific area, is means and the instrument that domain knowledge carries out organizational integration.
Its quality height directly influences the effectiveness of the various application carried out on this basis, is therefore setting up software FMEA knowledge originally
Need after body it is evaluated, to obtain its quality information.
Above-mentioned qualitative evaluating method is used to carry out quality evaluation radar system software FMEA body below.
The span of each grade used herein is set as: poor 0.0,0.5}, in 0.5,0.7}, good
{0.7,1.0}；By calculated C1=0.25, C2=0.6, C3=0.85.Above-mentioned numerical value is substituted into the person in servitude of above-mentioned structure
Genus degree function formula, can obtain:
Expert estimation situation is as shown in table 6.
The table 6 expert estimation result to domain body quality metric index
Note: E represents expert
Then can obtain:
R1=0.698
R2=0.565
R3=0.605
Substituting into formula, the degree of membership obtaining above-mentioned metric levels is respectively as follows:
R correctness: A1(r)=0.02, A2(r)=1, A3(r)=0
R integrity: A1(r)=1, A2(r)=0.883, A3(r)=0
R concordance: A1(r)=0.95, A2(r)=1, A3(r)=0
This is i.e.:
Have after these three result is normalized:
Judgement Matrix by following for above three formula compositions:
If three quality evaluation index weights are 1/3, then:
The meaning of RU is: the fuzzy overall evaluation result of body quality level degree of membership in " poor " grade is 0.346,
" in " degree of membership in grade is 0.654, the degree of membership in " good " grade is 0.According to maximum membership grade principle, this field
The credit rating of body be " in ".
The present invention carries out the structure of test model based on W model.Owing to W model is based on V model, increase with
Software each development phase synchronizes corresponding test process and is formed, and therefore can avoid the deficiency of V model, and overcome simultaneously
X model does not embodies the test process movable to demand, design etc., does not possess test completeness and adequacy for fail-safe software
Shortcoming.
The modeling method of knowledge based body is employed herein, it is possible to the form with ontologies is solid by domain knowledge
Change is got off.This not only establishes effective knowledge sharing bridge between software developer and tester, advantageously reduces
The difficulty linked up between the two, simultaneously because the domain knowledge after Gu Hua to contain field concept, principle and test experience etc. many
Content, therefore tester can carry out highly efficient, high-quality test according to ontologies, and this will thoroughly change test at present
Quality depend heavilys on tester's experience, and has the present situation of larger fluctuation.This most fundamentally overcomes W model and exists
Lack effective knowledge sharing between multiple stakeholder and link up bridge and owing to lacking effective domain knowledge solidification hands
Section and cause testing quality and there is the deficiency of larger fluctuation.Additionally, due to ontologies is the accumulation of a kind of experience and knowledge,
Can persistently play its effect after foundation, overcome X model the most to a certain extent and the proficiency level of tester is wanted
Seeking the shortcoming that comparison is high, and saved human and material resources, this also avoids X model by the feature of model flexibility and exploration
Essence test may be caused the waste of human and material resources and financial resources, increase the drawback of testing cost.
With reference to shown in Figure 16, the constructing system knot of the software intensive systems soft ware test model that Figure 16 provides for the present invention
Structure schematic diagram, including:
Framework establishment module, for building many body constructions of software FMEA information, including: domain body, applied ontology,
Ontology specification languages and Ontology Editing Tool；
Ontological construction module, for described many body constructions are constructed software FMEA information each layer body, sets software
The key element of FMEA Information Ontology and determine the mapping relations between each layer body；
Ontology definition module, for being described the key element of each layer ontology information according to described mapping relations, obtains base
Software FMEA Information Ontology model in field；
Ontology evaluation module, for utilizing qualitative evaluation method to comment the quality level of software FMEA Information Ontology model
Valency, determines domain body quality metric level.
Each technical characteristic of embodiment described above can combine arbitrarily, for making description succinct, not to above-mentioned reality
The all possible combination of each technical characteristic executed in example is all described, but, as long as the combination of these technical characteristics is not deposited
In contradiction, all it is considered to be the scope that this specification is recorded.
Embodiment described above only have expressed the several embodiments of the present invention, and it describes more concrete and detailed, but also
Can not therefore be construed as limiting the scope of the patent.It should be pointed out that, come for those of ordinary skill in the art
Saying, without departing from the inventive concept of the premise, it is also possible to make some deformation and improvement, these broadly fall into the protection of the present invention
Scope.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (10)
1. the construction method of a software intensive systems soft ware test model, it is characterised in that comprise the steps:
(1) many body constructions of software FMEA information are built, including: domain body, applied ontology, Ontology specification languages and body
Edit tool；
(2) to described many body constructions construct software FMEA information each layer body, set software FMEA Information Ontology key element with
And determine the mapping relations between each layer body；
(3) according to described mapping relations, the key element of each layer ontology information is described, obtains software FMEA based on field letter
Breath ontology model；
(4) utilize qualitative evaluation method that the quality level of software FMEA Information Ontology model is evaluated, determine domain body matter
Metric level.
The construction method of software intensive systems soft ware test model the most according to claim 1, it is characterised in that step
(1), in, by knowledge source acquisition of information domain body, described domain body is carried out the applied ontology that instantiation obtains；
Described domain body includes that static body and dynamic ontology, static body include concept, attribute, the description of relational factors
Information；Dynamic ontology includes event, the description information of active operation stream.
The construction method of software intensive systems soft ware test model the most according to claim 1, it is characterised in that step
(1), in, described knowledge source information includes:
1. the fault message extracted in Design of Reliability analysis, test and practical service environment；
2. the empirical and systematicness information obtained from experts database and specific software qualitative data；
3. the exemplary running software time/state FMEA information extracted from document；
4. the restrictive information extracted from industry standard, regulation.
The construction method of software intensive systems soft ware test model the most according to claim 1, it is characterised in that step
(2) including:
Based on described many ontology knowledge structure, construct each layer body, definition according to the hierarchical sequence of " domain body-applied ontology "
Mapping relations between the concept of each layer body, inheritance hierarchy, association, attribute, rule, example, and each layer body.
The construction method of software intensive systems soft ware test model the most according to claim 4, it is characterised in that step
(3), in, software FMEA Information Ontology is: SFMEA Ontology=< C, AC,R,AR, H, I >, wherein C is concept set, ACFor often
The property set of individual concept, R is set of relations, ARFor the property set of each relation, H is concept hierarchy, and I is example set.
The construction method of software intensive systems soft ware test model the most according to claim 5, it is characterised in that described
Each concept C in concept set CiFor representing a group objects of identical type, and it is described with identical property set；
The property set of described concept is AC(Ci), represent every attribute of fault mode example；
Described relation is Ri(Cp,Cq), represent each relation in relation R, riRepresent concept CpAnd CqBetween binary association, and
And the example of this relation is a pair conceptual object (Cp,Cq)；
The property set A of described relationR(ri) be used for representing relation riAttribute；
Described concept hierarchy H, for representing the concept hierarchy of concept set C, and is one group of father and son between concept or " father in C
Class-subclass " relation.
The construction method of software intensive systems soft ware test model the most according to claim 5, it is characterised in that step
(4) including:
(4-1) according to qualitative evaluation mapping rule, obtain the qualitative score value of domain body quality level, construct Judgement Matrix；
(4-2) acquisition affects the weight of domain body quality metric level；
(4-3) according to described Judgement Matrix and weight and utilize Field Using Fuzzy Comprehensive Assessment to determine domain body quality metric level.
The construction method of software intensive systems soft ware test model the most according to claim 7, it is characterised in that step
(4-1) including:
1. half trapezoidal profile and the membership function of trapezoidal profile structure credit rating { poor, in, good } are used；
If domain U={ is poor, in, good }, A is index fuzzy subset on domain U, structure membership function:
2. according to tolerance uiComputation measure uiThe qualitative evaluation integrated value of levelWherein, M is expert, and k is
Expert numbers；R (i) is substituted into membership function A1(r)、A2(r)、A3R (), the horizontal blur calculating each metric is comprehensively commented
Valency result, is normalized described Fuzzy Comprehensive Evaluation result, obtains constructing Judgement Matrix.
The construction method of software intensive systems soft ware test model the most according to claim 7, it is characterised in that described
Formula in Field Using Fuzzy Comprehensive Assessment is as follows:
Wherein, RU (i) is domain body quality metric level.
10. the constructing system of a software intensive systems soft ware test model, it is characterised in that including:
Framework establishment module, for building many body constructions of software FMEA information, including: domain body, applied ontology, body
Representation language and Ontology Editing Tool；
Ontological construction module, for described many body constructions are constructed software FMEA information each layer body, sets software FMEA letter
Cease the key element of body and determine the mapping relations between each layer body；
Ontology definition module, for being described the key element of each layer ontology information according to described mapping relations, obtains based on neck
The software FMEA Information Ontology model in territory；
Ontology evaluation module, for utilizing qualitative evaluation method that the quality level of software FMEA Information Ontology model is evaluated,
Determine domain body quality metric level.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610211548.XA CN105868115A (en) | 2016-04-05 | 2016-04-05 | Building method and system for software test model of software intensive system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610211548.XA CN105868115A (en) | 2016-04-05 | 2016-04-05 | Building method and system for software test model of software intensive system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105868115A true CN105868115A (en) | 2016-08-17 |
Family
ID=56637021
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610211548.XA Pending CN105868115A (en) | 2016-04-05 | 2016-04-05 | Building method and system for software test model of software intensive system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105868115A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109871635A (en) * | 2019-03-05 | 2019-06-11 | 中国航空综合技术研究所 | Run-time scenario modeling method towards the capture of civil aircraft top-level demands |
| CN110727801A (en) * | 2019-04-04 | 2020-01-24 | 郑州师范学院 | Ontology-based fuzzy evaluation search engine advertisement optimization method |
| CN111858298A (en) * | 2020-05-29 | 2020-10-30 | 卡斯柯信号有限公司 | Software testing method based on 3V model |
| CN112463119A (en) * | 2020-12-02 | 2021-03-09 | 上海亚远景信息科技有限公司 | V flow work decomposition structure |
| CN114978595A (en) * | 2022-04-19 | 2022-08-30 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Threat model construction method and device and computer equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090077666A1 (en) * | 2007-03-12 | 2009-03-19 | University Of Southern California | Value-Adaptive Security Threat Modeling and Vulnerability Ranking |
| CN103020722A (en) * | 2012-11-20 | 2013-04-03 | 北京航空航天大学 | Cloud manufacturing capability description method supporting use on demand and sharing circulation of manufacturing capability |
| CN103324196A (en) * | 2013-06-17 | 2013-09-25 | 南京邮电大学 | Multi-robot path planning and coordination collision prevention method based on fuzzy logic |
-
2016
- 2016-04-05 CN CN201610211548.XA patent/CN105868115A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090077666A1 (en) * | 2007-03-12 | 2009-03-19 | University Of Southern California | Value-Adaptive Security Threat Modeling and Vulnerability Ranking |
| CN103020722A (en) * | 2012-11-20 | 2013-04-03 | 北京航空航天大学 | Cloud manufacturing capability description method supporting use on demand and sharing circulation of manufacturing capability |
| CN103324196A (en) * | 2013-06-17 | 2013-09-25 | 南京邮电大学 | Multi-robot path planning and coordination collision prevention method based on fuzzy logic |
Non-Patent Citations (1)
| Title |
|---|
| 胡璇等: "航电系统软件需求知识本体构建及评价", 《计算机工程》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109871635A (en) * | 2019-03-05 | 2019-06-11 | 中国航空综合技术研究所 | Run-time scenario modeling method towards the capture of civil aircraft top-level demands |
| CN109871635B (en) * | 2019-03-05 | 2022-06-24 | 中国航空综合技术研究所 | Operation scene modeling method for capturing top-layer requirements of civil aircraft |
| CN110727801A (en) * | 2019-04-04 | 2020-01-24 | 郑州师范学院 | Ontology-based fuzzy evaluation search engine advertisement optimization method |
| CN111858298A (en) * | 2020-05-29 | 2020-10-30 | 卡斯柯信号有限公司 | Software testing method based on 3V model |
| CN111858298B (en) * | 2020-05-29 | 2022-08-30 | 卡斯柯信号有限公司 | Software testing method based on 3V model |
| CN112463119A (en) * | 2020-12-02 | 2021-03-09 | 上海亚远景信息科技有限公司 | V flow work decomposition structure |
| CN112463119B (en) * | 2020-12-02 | 2023-11-17 | 上海亚远景信息科技有限公司 | Software development method based on V-process work decomposition structure |
| CN114978595A (en) * | 2022-04-19 | 2022-08-30 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Threat model construction method and device and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Yu et al. | Prediction of highway tunnel pavement performance based on digital twin and multiple time series stacking | |
| Supciller et al. | Selection of wind turbines with multi-criteria decision making techniques involving neutrosophic numbers: A case from Turkey | |
| Ramasso | Investigating computational geometry for failure prognostics. | |
| CN101093559B (en) | Method for constructing expert system based on knowledge discovery | |
| CN105868115A (en) | Building method and system for software test model of software intensive system | |
| CN106295692B (en) | Product initial failure root primordium recognition methods based on dimensionality reduction and support vector machines | |
| CN105608004A (en) | CS-ANN-based software failure prediction method | |
| Yue | Picture fuzzy normalized projection and extended VIKOR approach to software reliability assessment | |
| CN105893256A (en) | Software failure positioning method based on machine learning algorithm | |
| Henriksson et al. | Towards structured evaluation of deep neural network supervisors | |
| CN102208028A (en) | Fault predicting and diagnosing method suitable for dynamic complex system | |
| CN102622510A (en) | System and method for quantitative management of software defects | |
| CN108564207A (en) | Architectural engineering intelligence Authorize to Bid based on BIM manages system | |
| Liu et al. | Failure mode and effect analysis based on probabilistic linguistic preference relations and gained and lost dominance score method | |
| CN107632590A (en) | A kind of bottom event sort method based on priority | |
| Liu et al. | A concurrent fault diagnosis method of transformer based on graph convolutional network and knowledge graph | |
| Sangroya et al. | Guided-LIME: Structured Sampling based Hybrid Approach towards Explaining Blackbox Machine Learning Models. | |
| CN103902845A (en) | Method for evaluating risk of simulation system based on fuzzy FMEA | |
| Azimi et al. | A Layered Quality Framework for Machine Learning-driven Data and Information Models. | |
| Lin et al. | An HFM‐CREAM model for the assessment of human reliability and quantification | |
| Wang et al. | Reliability analysis of complex electromechanical systems: State of the art, challenges, and prospects | |
| CN105894138A (en) | Optimum weighted composite prediction method for shipment amount of manufacturing industry | |
| Zorn et al. | Replacing energy simulations with surrogate models for design space exploration | |
| Dhiman et al. | A Clustered Approach to Analyze the Software Quality Using Software Defects | |
| CN106202668A (en) | Complex equipment quality risk appraisal procedure based on quality problems data and reverse conduction neutral net |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into 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: 20160817 |