| 摘要 |
Whether or not an integration test between or among software components is necessary is judged. Corresponding information between features is acquired, which configures a feature model expressing characteristics of a group of products produced by the software product line, and a type and variations of each software component. For each software component, a set of state variables of all of the features corresponding to the software components is produced based on the corresponding information. For each software component, a specific logical formula is produced. Two or more software components are designated. A necessity judgment formula is produced by logical-product combining all the specific judgment formulas, for the software components designated. It is judged that the integration test is necessary when the necessity judgment formula always shows FALSE (inconsistent formula) and not necessary when the necessity judgment formula shows unclearness as to TRUE or FALSE, or always shows TRUE (valid formula). |
| 主权项 |
1. A method of judging whether or not an integration test between or among software components is necessary, the software component being reusable software which can be used as a core asset for a software product line, the method comprising:
a first step of acquiring corresponding information between a feature, which configures a feature model expressing characteristics of a group of products produced by the software product line, and a type and variations of each of the software components; a second step of producing, for each of the software components Sij a set of state variables Cij of all of the features corresponding to the software components Sij, by using the corresponding information acquired in the first step,
where i denotes the types of each of the software components and i=1 to M wherein M is a total number of the types of the software components, j denotes the variations of the software components and j=1 to Nj wherein Ni is a total number of the software component specified by the type i, and the Sij denotes one of the software components which is specified by the type i and the variation j, andwhere each of the state variables Cij is prepared for each of the features and is TRUE when the feature is selected and to FALSE when not selected, a third step of producing, for each of the software components Sij, a specific judgment formula IS(Cij) which is a logical formula composed of a logical product between a logical formula H(Cij) and each of Ni−1 logical formulas NH(Cit),
where Six denotes a group of the software components composed of Nj software components specified by i,where t denotes Nj−1 variations which are other than variations specified by j among Six, wherein t does not equal j,the logical formula H(Cij) is obtained by logical-product combining all elements of the Cij, andthe logical formula NH(Cij) is obtained by logically denying the logical formula H(Cij), a fourth step of designating two or more software components to be subjected to judgment for necessity of performing an integration test; and a fifth step of producing a necessity judgment formula by logical-product combining all the specific judgment formulas produced in the third step, for the software components designated in the fourth step; and a six step of judging whether or not the integration test is necessary, based on the necessity judgment formula such that the integration test is necessary when the necessity judgment formula is always FALSE and the integration test is not necessary when the necessity judgment formula shows unclearness as to TRUE or FALSE, or always shows TRUE. |
