System and method for software test analysis
US-2024419581-A1 · Dec 19, 2024 · US
US8959487B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-8959487-B2 |
| Application number | US-201313938518-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 10, 2013 |
| Priority date | Jul 11, 2012 |
| Publication date | Feb 17, 2015 |
| Grant date | Feb 17, 2015 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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).
Opening claim text (preview).
What is claimed is: 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 e…
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Related publications grouped by family.
Free tools are coming soon. Tell us what you want to track and we'll notify you.
Answers are generated from the same data shown on this page.