CN101551750A - Method of detecting software process reliability and system of using the same - Google Patents
Method of detecting software process reliability and system of using the same Download PDFInfo
- Publication number
- CN101551750A CN101551750A CNA2009100839970A CN200910083997A CN101551750A CN 101551750 A CN101551750 A CN 101551750A CN A2009100839970 A CNA2009100839970 A CN A2009100839970A CN 200910083997 A CN200910083997 A CN 200910083997A CN 101551750 A CN101551750 A CN 101551750A
- Authority
- CN
- China
- Prior art keywords
- credible
- data
- software
- confidence level
- software process
- 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
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention discloses a method of detecting software process reliability and a system of using the same, belonging to software engineering field. The method includes following steps: an evidence data acquisition module collecting actual item data in specify software process according to credibility index set; the evidence acquisition module comparing the collected data with the set process credible index baseline and getting metric data; a reliability detecting module providing reliability detecting value of the software under the principle of credibility according to the metric data; credible level of the software process is provided. The system of the invention collects actual item data for choosing credible level automatically in normal software developing process, and using the actual item data as evidence, using baseline data to judge credibility of the item process instead of using experts or appraisers to judge the implementation of the process, which assuring objectivity and creditability of the software process.
Description
Technical field
The present invention relates to a kind of detection method and system of software process credibility, relate generally to the metric framework of believable software process and detect credible other method and system of level, belong to the computer software engineering field.
Background technology
Since computing machine was born, it used each field such as space flight, finance, manufacturing, communication, the energy, medical treatment, education that have been deep into, and people's work relies on computer software more and more with life.People not only need computer software to realize more function, are also had higher requirement in aspects such as the ease for use of software, reliability, security, user experience.For satisfying people computer software is got more and more and more and more higher demand, soft project is arisen at the historic moment.
Software process is defined by a series of partial order process steps, each step generally comprises product, personnel, computer resource, institutional framework, constraint etc. (please refer to document Carlo Montangero, Jean-Claude Derniame, Badara AliKaba, and Brian Warboys.The software process:Modelling and technology.In Derniame et al.[126] .Pages 1-14. and CMMI Product Team.Cmmi for development, version 1.2-improvingprocesses for better products.Technical Report CMU/SEI-2006-TR-008, SEI, CMU, 2006.).One software process can be explained by various data, and the data of these reflection software process can be stored in the software process management database, forms the history item data and (please refer to document Jones 2000, ISBSG; Capers Jones, Software Assessments, Benchmarks, and Best Practices, Addison-Wesley Professional, 2000, ISBSG, www.isbsg.org).Therefore, software process can be for being stored in the quantifiable objective process in the software process management database.
Under internet environment, the credibility of software process no longer is confined to security, but comprises mass propertys such as functional, reliability, availability, validity, maintainability, portability.Progressively become the research focus of association area in recent years about the credible Method and kit for that guarantees of software process.
Some researchs (please refer to document: Mary Beth Chrissis as the CMMI/TSP/PSP series model of U.S. CMU-SEI, Mike Konrad, Sandy Shrum, " CMMI Guidelines for Process Integration and ProductImprovement ", Second Edtion, Anddison-Wesley, 2007), ISO series standard 9000,9126 frameworks that all provided software process and software quality (please refer to document: ISO/IEC TR 9126-4:2004, http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_det ail.htm? csnumber=39752), believable notion is not still proposed clearly; Other (please refer to document: " Common Criteria forInformation Technology Security Evaluation " as Common Criteria, version 3.1, reversion 1, Sep.2006), SSE-CMM (please refer to document: " Security System Engineering Capability Maturity Model (SSE-CMM) " version 3.0,2003.), the ISO27002 standard (please refer to document: ISO/IEC 27002:2005, " Information Technology-Security Techniques-Code Practice for InformationSecurity Management ", http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_det ail.htm? csnumber=50297), the FAA-CMMI extended model (please refer to document: Linda Ibrahim, Joe Jarzombek, Matt Ashford, et al, " Safety andSecurity Extensions for Integrated Capability Maturity Models ", United States Federal AviationAdministration, Sep., 2004.) etc., only be confined on the security credible.
With reference to TSM (trusted software methodology), the credibility of software process can be defined as: software product satisfies the confidence degree of particular demands.The most of credible research of present stage mainly is from user's angle software product to be carried out credibility evaluation, and in fact the credibility of the raising of the credibility of software product and software process is closely-related.Trusted products (as work product, software product etc.) is meant the product that satisfies based on the credible target of set demand.Trusted processes is meant the competent process that can produce a series of credible work products.
Develop believable product, the credibility of product quality feature can only be obtained and ensures by believable performance history and practice.An important method that guarantees the software development process credibility is exactly that performance history is carried out credible detection.
Therefore set up the detection system of a software process credibility, help ensureing the credibility of software development process, help improving the credibility of software product.
CMMI thinks and Software Production process decision software quality from industry experience, has proposed to contain 22 process domains of SDLC, instructs developer's management development process, allows the product of customer satisfaction thereby develop.CMMI is divided into five ranks according to software process capability with software process, and each rank all has specific process domain, judges ability with the assessment software performance history with this.CMMI is the software process grading standard of present main flow, but because versatility, CMMI is the evaluation to software process maturity, and (not please refer to document: Mary BethChrissis, Mike Konrad, Sandy Shrum at the grading of software credibility specially, " CMMI Guidelines for Process Integration and ProductImprovement ", Second Edtion, Anddison-Wesley, 2007).
The TSM methodology is defined as software credibility " the confidence degree that software satisfies set demand ", and this definition has been emphasized credible to implementing the high dependency of management decision, technology decision-making and the set requirements set of developing life cycle.Simultaneously, TSM has proposed (to please refer to document: E.Amoroso et al. for 44 credible principles of software development reference and corresponding demand from the angle of software development process, " Toward An Approach to Measuring Software Trust; " Proc.IEEESymp.Research in Security and Privacy, May 1991, pp.198-218.Edward Amoroso, CarolTaylor, et al., " A Process-Oriented Methodology for Assessing and Improving SoftwareTrustworthiness ", Conference on Computer and Communications Security, Proceedings of the2nd ACM Conference on Computer and communications security, 1994, Page39-50.J.Watsonand E.Amoroso, " A Trusted Software Development Methodology; " Proc.13th Natl.ComputerSecurity Conf, Oct.6,1990, pp.717-727.).But the tolerance that provides among the TSM and assess the foundation of these credible principles lacks the consideration to credible risk and trusted processes tolerance, and a large amount of in practice decision-makings depend on personnel's subjectivity.But the definition of the software trust that TSM proposed and credible principle appraisal framework are for ensureing that from the process angle software trust has huge reference value.Credibility requires a processor-oriented angle, and the behavior of software product and state are measurable and control in its life cycle.
Utilize the achievement of CMMI and TSM, carry out the exploitation of trusted software, need be in conjunction with software process and process data, in the tolerance of trusted software and evaluation model, introduce the procedure attribute and the evaluation index of more targeted and objectivity, with more early stage, more timely, reach the detection of finishing the software process credibility more objectively.
Summary of the invention
In order to address the above problem, the object of the present invention is to provide a credible detection system of the software process based on the process data evidence and method, be used for the credibility of the software process of appointment is detected and draw grade, with management and the improvement of instructing believable software process.
Method of the present invention is summarized as follows:
The credible detection method of a kind of software process may further comprise the steps:
1) the evidence data acquisition module forms confidence level figureofmerit data according to the automatic real data of setting of gathering designated software process correspondence of confidence level figureofmerit set;
2) the evidence data processing module with the process credible indexes baseline of the data of gathering in the above-mentioned set and setting relatively obtains metric data, and described process credible indexes baseline comprises the base-line data and the corresponding inter-trust domain of confidence level figureofmerit;
3) credible detection module draws the credible detected value under each credible principle of described software process according to above-mentioned metric data;
4), draw the confidence level of described software process according to the credible detected value under each credible principle.
Described confidence level figureofmerit set comprises the confidence level figureofmerit of influence process credibility in each process.
Described base-line data and inter-trust domain generate and adjust according to practical experience value in the industry or analysis of history project data.
Described step 2) Bi Jiao process is overseas for the may command that the confidence level figureofmerit data of gathering drop on base-line data, represents with 0, otherwise represents with 1.
Described step 3) is by obtaining the credible detected value under this credible principle to the metric data sum-average arithmetic corresponding with described credible principle.
Described step 4) draws the confidence level of described software process according to the grading standard of TSM.
Wherein, the credible detected value of minimum rank is set at 0.5, and other increases progressively with credible level, and credible principle detected value increase or that strengthen demand increases progressively 0.1.
The credible detection system of a kind of software process comprises evidence data acquisition module, evidence data processing module, credible detection module, wherein:
Described evidence data acquisition module is gathered the confidence level figureofmerit data in the designated software process automatically; The evidence data processing module compares the data of collection and the process credible indexes baseline of setting, obtains metric data; Credible detection module draws the credible detected value under each credible principle of described software process according to above-mentioned metric data; Draw the confidence level of described software process.
In the credible detection system of described software process, execution along with software process, automatically it is as follows the credibility of this process to be detected other main process prescription of level: as shown in Figure 1, whole credible detection system is divided into three big modules: evidence data acquisition module, evidence data processing module and credible detection module.
The evidence data acquisition module: in order to guarantee the just and objectivity of detection system, the detection of being done decision-making must be based on certain evidence, and these evidence data should be the true real data of tested process.Therefore before process being carried out the credibility detection, need to gather relevant real data.Gather which type of data and be directly connected to credible other reliability of level and accuracy.
Determine the metric of software process confidence level according to the practical experience of the research of academia and industry member.In order to understand these indexs better, we correspond to procedure incarnation with them again, the process behavior, and process product and quality are credible, and cost is credible, on two dimensions that progress is credible.Therefore in system's evidence data acquisition module, set confidence level and detect needed process measurement index set classification (index in the set can in the light of actual conditions add and delete) as shown in table 1.
Table 1
The confidence level figureofmerit that this set comprised all is suitable for for each software project, and they are confidence level figureofmerits of influence process credibility in each process of entire software development.Because the function of software project process management that the evidence data acquisition module is integrated, therefore in the normal performance history of software project, the evidence data acquisition module can obtain relevant actual items data automatically according to the set of confidence level figureofmerit, form confidence level figureofmerit data, provide input for further the evidence data being handled.
Evidence data processing module:, therefore need handle, to produce the data set that to support credible detection module to gathering the project data that comes because the actual items data of confidence level figureofmerit can't be applied directly to credible testing process.For the ease of supporting credible detection, set a process credible indexes baseline in the evidence data processing module, what comprise in the baseline is at the base-line data of confidence level figureofmerit and corresponding data inter-trust domain.For a comparatively ripe software development organization, base-line data and inter-trust domain be to set according to the history item data of this tissue self by this tissue.And for not having or the software development organization of history item rareness, the evidence data processing module can provide a default base-line data and data inter-trust domain according to the practical experience in the industries such as CSBSG (Chinese software process reference user group) data.
For a specific tissue, base-line data is not unalterable, and along with the accumulation and the increase of history item data, tissue can be adjusted base-line data at any time to reach credible detection of software process that is fit to organize particular requirement.
Generation metric data after the actual items data of gathering are compared with base-line data.Final structure through the later data acquisition of evidence data processing, D={d as follows
1, d
2..., d
44, d wherein
i(i=1,2 ..., 44) and expression is corresponding to the evidence data set of 44 credible principles that are used to detect (credible principle by TSM method definition), d
i={ m
I1, m
I2..., m
Ij, m wherein
IjMetric data after the processing of corresponding certain the evidence collection of expression, m
Ij=0 or 1 (0 these data of expression drop on outside the inter-trust domain of base-line data, support that then the i process is insincere, and vice versa).For d
iThe value system handle according to following algorithm: d
i=(m
I1+ m
I2+ ... + m
Ij)/j, 0＜=d
i＜=1, j is the m of each credible principle correspondence
IjNumber.
Credible detection module: D is input in the credible detection module of process and detects as handling later data set.Preestablish the credible criterion that detects of process according to the TSM methodology in the module, promptly 44 data of D set the inside have been judged, worked as d
i＜0.5 expression does not reach i credible principle; Work as d
i＞=0.5, represent that i credible principle reaches, and represents that promptly the activity in this principle is believable.At first count the d value more than or equal to 0.5 the institute on evidence the collection, if judge that according to the grading standard of TSM these evidence energy collectings enough support the credible principle of confidence levels T1 among the TSM (T0 is without any need for credible principle support), illustrate that then this software process has reached the T1 level of confidence levels at least.Further consider higher confidence level on this basis.Whether this evidence collection d of credible principle correspondence that need judge the credible principle that newly adds of T2 class requirement or strengthen demand according to the regulation in the TSM method is more than or equal to 0.6, if whether the evidence collection d of credible principle correspondence that does not have extra demand satisfy above-mentioned requirements then reaches T2 rank more than or equal to 0.5.And the like, whenever the evidence collection d that credible principle correspondence new or that strengthen demand is arranged requires to increase progressively 0.1.TSM for credible principle new or the enhancing demand does not provide concrete explanation, in our system, then react the trend of this increase with the increase of the value of d.Final system is exported the credible grade of this software process according to the credibility of 44 data among the D, and six grades increase progressively successively from T0 to T5.The credible flow process that detects of concrete software process as shown in Figure 2.
Compared with prior art, the invention has the beneficial effects as follows: 1) do not need manual intervention, middle system in normal executive software performance history gathers the actual items process data that is used for credible detection automatically, has saved manpower and time, has also reduced the high error rate that artificial image data occurs; 2) utilize base-line data to judge the credibility of software process, as evidence, rather than subjectively the process implementation status is carried out whether believable judgement, guaranteed the objectivity and the credibility of testing process by expert or appraiser with the real process data; 3) support an evidence data set by a plurality of metric datas, an evidence data set is corresponding to a credible principle, derive whether reach certain credible principle by the method for sum-average arithmetic, rather than only to have be that non-judgement decides, guaranteed credible comprehensive.4) for the confidence level that increases progressively, no longer be to consider qualitatively whether demand newly-increased or that strengthen satisfies in the credible principle, but quantitatively,, avoided the fuzzy uncertain and the subjectivity of artificial judgement with the corresponding newly-increased or demand requirement that strengthens of increasing progressively of the numerical value of evidence collection.
Description of drawings
Fig. 1 is the block diagram of the credible detection system of software process
Fig. 2 is the credible flow process that detects of software process
Embodiment
The present invention will be further described below by the embodiment to a development project Project1 of Beijing basic software company, but be not construed as limiting the invention.
The first step, the data of collection actual items process.The project team member of company has installed the credible detection system of software process before project initiation, in the process of project exploitation, the program member executes the task according to the requirement of project management in the system, and obtains the credible needed actual items metric data that detects by the separate sources such as characteristic information of multiple report form such as debriefing, problem report and project.For example collect instrument confidence level, platform credible degree, automated tool usage degree, effectively management tool, development system mobility, platform mobility, demand evaluation amount ratio, demand evaluation find that the data of reports such as workload that data such as defective efficient, demand evaluation efficient, demand evaluation defect concentration can be submitted to by program member in the characteristic information of project, the project implementation process, defective are by calculating.All metric that comprise above-described various metric have plenty of with the form of classification and represent to have plenty of actual numeric data.No matter be classification or numeric data, representation all should be consistent with the representation in the base-line data, and this assurance is finished by system automatically by turning in a report.These data leave in the set of confidence level figureofmerit by system acquisition is unified later on, and are used as next step input.What table 2 was represented is the part actual items process data of project Project1:
Table 2
| The metric title | Metric type | Data value | Unit |
| The instrument confidence level | Classification | High | Level |
| The platform credible degree | Classification | Nominal | Level |
| The automated tool usage degree | Classification | Nominal+ | Level |
| Effective management tool | Classification | Very?High | Level |
| The development system mobility | Classification | Low | Level |
| The platform mobility | Classification | Low | Level |
| Demand evaluation amount ratio | Numerical value | 5.46％ | Percentage |
| Defective efficient is found in the demand evaluation | Numerical value | 2.87 | Individual/man-hour |
| Demand evaluation efficient | Numerical value | 12.9 page or leaf/man-hour | Scale unit/man-hour |
| Demand evaluation defect concentration | Numerical value | 3.85 it is individual/page or leaf | Individual/scale unit |
What wherein, scale unit's page table of demand evaluation showed is the requirements specification document of A4 scale.Above actual items data and in task that item characteristic information and program member fill in, problem report, gathered automatically corresponding to the data in other metric set, and be kept in the database, with input as data processing module.
In second step, the actual items data that collect are handled, to support data demand to the credible detection of process.Because the credibility of final software process detects the grading mode with reference to TSM, promptly the mode that is performed situation with 44 credible principles judging among the TSM comes the credibility of process is detected.Though the credible mode of detection of the present invention is with reference to the grading mode of TSM, but because the evaluation whether each credible principle is satisfied of TSM relies on people's subjective judgement mostly, lack genuine and believable evidence support, therefore make final confidence level lack objectivity.In order to address this problem, in the credible detection system of software process of the present invention, to have introduced base-line data and solved this problem.Use base-line data and credible control domain to judge that the actual items data of evidence data collecting module collected are whether in believable scope.Still as an example, with ten data in the first step system according to certain software development organization its to determine that believable project data has been set their base-line data and corresponding control domain as shown in table 3:
Table 3
| The metric title | Base-line data | Credible control domain |
| The instrument confidence level | High | Rank is more than or equal to High |
| The platform credible degree | High | Rank is more than or equal to High |
| The automated tool usage degree | High | Rank is more than or equal to Nominal+ |
| Effective management tool | Nominal | Rank is more than or equal to Nominal |
| The development system mobility | Nominal | Rank is lower than and equals Nominal |
| The platform mobility | Low | Rank is lower than and equals Low |
| Demand evaluation amount ratio | 4.92％ | Domain of walker+-0.8% |
| Defective efficient is found in the demand evaluation | 2.56 it is individual/man-hour | More than or equal to 2.56/man-hour |
| Demand evaluation efficient | 12 pages/man-hour | Domain of walker is+-2 |
| Demand evaluation defect concentration | 3.25 it is individual/page or leaf | Smaller or equal to 3.4/page |
In credible base-line data and the credible control domain, be a scope for demand evaluation amount ratio and demand evaluation efficient.The reason of She Zhiing is that the ratio of demand evaluation amount ratio in whole workload is the believable scope of assurance demand evaluation course between 4.12% to 5.72% like this, when ratio less than this scope, the workload that means the demand evaluation is not enough, may make the defective in the demand not to be examined out fully, this will cause the sharp increase of the do over again workload and the cost in later stage; And when demand evaluation amount is excessive, the workload waste may appear, the consequence that disfigurement discovery efficient reduces.Credible scope for demand evaluation efficient also is same reason.
The actual items data with base-line data relatively before, earlier need be according to above-mentioned evidence disposal route, practical experience according to the research of academia and industry member corresponds to these metric in 44 evidences set, and each evidence set is the credible principle data that provide support.Therefore preceding 6 metric in the table 1 correspond to the 10th evidence collection, and back 4 metric correspond to the 19th evidence collection.Wherein the 10th the credible principle of TSM is " selection of environment and instrument ", and the credible principle of the 19th TSM is " demand analysis evaluation ".With the metric data m after actual items data and the processing that obtains the corresponding evidence collection of credible principle after base-line data compares
IjWith table 1 and table 2 as an example, the grade of instrument confidence level should be higher than and equals High, and the actual items data are High, therefore, and m
10,1=1; The grade of platform credible degree is with the same requirement of instrument confidence level, but the actual items data have only Nominal+, so m
10,2=0, the data that can obtain the 10th evidence collection successively are d
10=1,0,1,1,1,1}.Decide because each credible principle is the evidence collection data by correspondence, and the evidence collection comprises several metric datas, therefore need be processed into the data that can support that credible principle is judged to metric data.Here we have adopted the method for asking average, guarantee that the factor of each metric data correspondence has influence to the process credibility.According to the algorithm of summary of the invention part, d
10Numerical value=(1+0+1+1+1+1)/same reason of 6=0.833. can be used for the 19th evidence collection, actual items data and credible base-line data can be got d after relatively
19={ 1,1,1, so 0} is d
19Numerical value=(1+1+1+0)/4=0.75. the confidence level figureofmerit that same judgment mode is used for other just can be obtained the value of 44 d, thereby finally be used for the credible data set D that detects of process.
In the 3rd step, detect according to the value of data set D credibility to software process.Here the principle of judging credible grade is to illustrate that these evidence collection data are to support corresponding credible principle when the value of d more than or equal to 0.5 the time, if less than 0.5 then the data of this evidence collection of explanation can not be supported corresponding credible principle.After the data of 44 evidence collection being carried out credible judgement, can obtain the credible grade of software process according to the grading standard of TSM.In the project data of Project1, last evidence collection more than or equal to 0.5 is respectively: d
9, d
10, d
13, d
15, d
16, d
19, d
20, d
22, d
26, d
27, d
32, d
33, d
39, d
40Correspond respectively to credible principle " management ", " environment and instrument are selected ", " safety policy ", " software reuse ", " plan ", " demand analysis evaluation ", " demand analysis document ", " demand trackability ", " design review ", " design documentation ", " source code evaluation ", " source code document ", " test evaluation ", " test document ".Therefore judge that according to the grading standard of TSM the performance history credibility of this project is T1.Because after the requirement of having satisfied T1, the situation that shows for the real data that requires this project of T2 can not satisfy, so the detection task termination of system, and the credible grade of the software process of output Project1 is the T1 level.
Claims (8)
1, the credible detection method of a kind of software process may further comprise the steps:
1) the evidence data acquisition module forms confidence level figureofmerit data according to the automatic real data of setting of gathering designated software process correspondence of confidence level figureofmerit set;
2) the evidence data processing module with the process credible indexes baseline of the data of gathering in the above-mentioned set and setting relatively obtains metric data, and described process credible indexes baseline comprises the base-line data and the corresponding inter-trust domain of confidence level figureofmerit;
3) credible detection module draws the credible detected value under each credible principle of described software process according to above-mentioned metric data;
4), draw the confidence level of described software process according to the credible detected value under each credible principle.
2, the method for claim 1 is characterized in that, described confidence level figureofmerit set comprises the confidence level figureofmerit of influence process credibility in each process.
3, the method for claim 1 is characterized in that, described base-line data and inter-trust domain generate and adjust according to practical experience value in the industry or analysis of history project data.
4, the method for claim 1 is characterized in that, described step 2) relatively process is overseas for the may command that the confidence level figureofmerit data of gathering drop on base-line data, and represent with 0, otherwise represent with 1.
As claim 1 or 4 described methods, it is characterized in that 5, described step 3) is by obtaining the credible detected value under this credible principle to the metric data sum-average arithmetic corresponding with described credible principle.
6, the method for claim 1 is characterized in that, described step 4) draws the confidence level of described software process according to the grading standard of TSM.
7, the method for claim 1 is characterized in that, the credible detected value of minimum rank is set at 0.5, and other increases progressively with credible level, and credible principle detected value increase or that strengthen demand increases progressively 0.1.
8, the credible detection system of a kind of software process is characterized in that, comprises evidence data acquisition module, evidence data processing module, credible detection module, wherein:
Described evidence data acquisition module is gathered the confidence level figureofmerit data in the designated software process automatically; The evidence data processing module compares the data of collection and the process credible indexes baseline of setting, obtains metric data; Credible detection module draws the credible detected value under each credible principle of described software process according to above-mentioned metric data; Draw the confidence level of described software process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2009100839970A CN101551750A (en) | 2009-05-15 | 2009-05-15 | Method of detecting software process reliability and system of using the same |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2009100839970A CN101551750A (en) | 2009-05-15 | 2009-05-15 | Method of detecting software process reliability and system of using the same |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101551750A true CN101551750A (en) | 2009-10-07 |
Family
ID=41156003
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2009100839970A Pending CN101551750A (en) | 2009-05-15 | 2009-05-15 | Method of detecting software process reliability and system of using the same |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101551750A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102043718A (en) * | 2010-12-29 | 2011-05-04 | 南京航空航天大学 | Software trustworthiness evaluation implementation method supporting customization of evidence model and attribute model |
| CN102479150A (en) * | 2010-11-25 | 2012-05-30 | 神州数码信息系统有限公司 | Method for evaluating credibility of software |
| CN103677849A (en) * | 2013-12-26 | 2014-03-26 | 北京控制工程研究所 | Embedded software credibility guaranteeing method |
| CN104636258A (en) * | 2015-03-13 | 2015-05-20 | 上海交通大学 | Confidence testing method facing reconfigurable support software |
| CN106779366A (en) * | 2016-12-02 | 2017-05-31 | 华北计算技术研究所 | project management process performance model and its construction method and performance model management system |
| CN108521405A (en) * | 2018-03-20 | 2018-09-11 | 咪咕文化科技有限公司 | A kind of risk management and control method, device and storage medium |
| CN109614769A (en) * | 2013-08-15 | 2019-04-12 | 微软技术许可有限责任公司 | The secure operating system starting encapsulated according to reference platform inventory and data |
| CN110427016A (en) * | 2019-08-05 | 2019-11-08 | 上海无线电设备研究所 | A kind of method for testing reliability of phase array antenna beam control system |
| CN111191346A (en) * | 2019-12-11 | 2020-05-22 | 上海航天控制技术研究所 | Method and medium for restoring on-orbit operation instance data of spacecraft software |
-
2009
- 2009-05-15 CN CNA2009100839970A patent/CN101551750A/en active Pending
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102479150A (en) * | 2010-11-25 | 2012-05-30 | 神州数码信息系统有限公司 | Method for evaluating credibility of software |
| CN102043718A (en) * | 2010-12-29 | 2011-05-04 | 南京航空航天大学 | Software trustworthiness evaluation implementation method supporting customization of evidence model and attribute model |
| CN109614769A (en) * | 2013-08-15 | 2019-04-12 | 微软技术许可有限责任公司 | The secure operating system starting encapsulated according to reference platform inventory and data |
| CN103677849A (en) * | 2013-12-26 | 2014-03-26 | 北京控制工程研究所 | Embedded software credibility guaranteeing method |
| CN103677849B (en) * | 2013-12-26 | 2015-04-15 | 北京控制工程研究所 | Embedded software credibility guaranteeing method |
| CN104636258B (en) * | 2015-03-13 | 2018-03-06 | 上海交通大学 | Towards the credible method of testing of restructural support programs |
| CN104636258A (en) * | 2015-03-13 | 2015-05-20 | 上海交通大学 | Confidence testing method facing reconfigurable support software |
| CN106779366A (en) * | 2016-12-02 | 2017-05-31 | 华北计算技术研究所 | project management process performance model and its construction method and performance model management system |
| CN108521405A (en) * | 2018-03-20 | 2018-09-11 | 咪咕文化科技有限公司 | A kind of risk management and control method, device and storage medium |
| CN108521405B (en) * | 2018-03-20 | 2020-12-11 | 咪咕文化科技有限公司 | Risk control method and device and storage medium |
| CN110427016A (en) * | 2019-08-05 | 2019-11-08 | 上海无线电设备研究所 | A kind of method for testing reliability of phase array antenna beam control system |
| CN111191346A (en) * | 2019-12-11 | 2020-05-22 | 上海航天控制技术研究所 | Method and medium for restoring on-orbit operation instance data of spacecraft software |
| CN111191346B (en) * | 2019-12-11 | 2023-09-29 | 上海航天控制技术研究所 | Method and medium for restoring on-orbit running instance data of spacecraft software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101551750A (en) | Method of detecting software process reliability and system of using the same | |
| Zhou et al. | Empirical analysis of object-oriented design metrics for predicting high and low severity faults | |
| Elberzhager et al. | Reducing test effort: A systematic mapping study on existing approaches | |
| Attri et al. | Interpretive structural modelling (ISM) approach: an overview | |
| CN110174883B (en) | System health state assessment method and device | |
| Cheng et al. | GA‐based multi-level association rule mining approach for defect analysis in the construction industry | |
| CN109408359A (en) | A kind of software test procedure quality metric method and system | |
| CN102117443A (en) | Analyzing anticipated value and effort in using cloud computing to process a specified workload | |
| Tawfek et al. | Assessment of the expected cost of quality (COQ) in construction projects in Egypt using artificial neural network model | |
| CN113807747A (en) | Enterprise budget management maturity evaluation system | |
| CN102262663A (en) | Method for repairing software defect reports | |
| Pietrantuono | On the testing resource allocation problem: Research trends and perspectives | |
| Kbaier et al. | Determining the threshold values of quality metrics in BPMN process models using data mining techniques | |
| Biancone et al. | Data quality methods and applications in health care system: a systematic literature review | |
| Kuutila et al. | Daily questionnaire to assess self-reported well-being during a software development project | |
| Rodriguez et al. | A taxonomy for whole building life cycle assessment (WBLCA) | |
| Zou et al. | An empirical study of bug fixing rate | |
| Li et al. | Preliminary results of a systematic review on requirements evolution | |
| Tran et al. | How good are my search strings? Reflections on using an existing review as a quasi-gold standard | |
| Sehestedt et al. | Towards quantitative metrics for architecture models | |
| Saydemir et al. | On the use of evolutionary coupling for software architecture recovery | |
| Nadi et al. | Cost-effective optimization strategies and sampling plan for Weibull quantiles under type-II censoring | |
| CN111915188A (en) | Enterprise system performance test method, device and equipment | |
| Puzis et al. | A particle swarm model for estimating reliability and scheduling system maintenance | |
| Kostakis et al. | Integrating activity‐based costing with simulation and data mining |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20091007 |