Technologies for code failure proneness estimation

Data processing: software development – installation – and managem – Software program development tool – Testing or debugging

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C717S128000, C717S130000

Reexamination Certificate

active

07926036

ABSTRACT:
The present examples provide technologies for estimating code failure proneness probabilities for a code set and/or the files that make up the set. The code set being evaluated is typically comprised of binary and/or source files that embody the software for which the estimates are desired. The estimates are typically based on a set of selected code metrics, the code metrics typically selected based on corresponding failures of a previous version of the software. A historically variant metric feedback factor may also be calculated and code metric values classified relative to a baseline code set embodying the previous version of the software.

REFERENCES:
patent: 5414809 (1995-05-01), Hogan et al.
patent: 5729746 (1998-03-01), Leonard
patent: 5915114 (1999-06-01), McKee et al.
patent: 5960196 (1999-09-01), Carrier et al.
patent: 5970246 (1999-10-01), Moughani et al.
patent: 6192511 (2001-02-01), Johnston et al.
patent: 6219805 (2001-04-01), Jones et al.
patent: 6477666 (2002-11-01), Sanchez et al.
patent: 6516460 (2003-02-01), Merks et al.
patent: 6721941 (2004-04-01), Morshed et al.
patent: 6785848 (2004-08-01), Glerum et al.
patent: 6986124 (2006-01-01), Field et al.
patent: 7240335 (2007-07-01), Angel et al.
patent: 7322026 (2008-01-01), Ahluwalia et al.
patent: 7401323 (2008-07-01), Stall et al.
patent: 7685574 (2010-03-01), Brumme et al.
patent: 7725881 (2010-05-01), Bhat et al.
patent: 7797684 (2010-09-01), Prakash
Michael, “Using evolution constraints to access the failure proneness of evolving software”, IEEE, pp. 48-51, 1997.
Gitzel et al, “Towards a software failure cost impact model for the customer”, ACM PROMISE, pp. 1-9, 2010.
Schroter et al, “Predicting component failure at design time”, ACM ISESE, pp. 18-27, 2006.
Nagappan et al, “The influence of organizational structure on software quality: An emprical case study”, ACM ICSE, pp. 521-530, 2008.
V.R. Basili, et al; “A Validation of Object Orient Design Metrics as Quality Indicators”; IEEE Transactions on Software Engineering; pp. 751-761; 1996.
L.C. Briand, et al; “Exploring the Relationship Between Design Measures and Software Quality in Object Oriented Systems”; Journal of Systems and Software; pp. 245-273, 2000.
L.C. Briand, et al; “Investigating Quality Factors in Object-Oriented Designs: An Industrial Case Study”; Proceedings of International Conference on Software Engineering; pp. 345-354, 1999.
S.R. Chidamber, et al; “A Metrics Suite for Object Oriented Design”; IEEE Transactions on Software Engineering; pp. 476-493; 1994.
N.I. Churcher, et al; “Comments on 'A Metrics Suite for Object-Oriented Design”; IEEE Transactions on Software Engineering; pp. 263-265; 1995.
G. Denaro, et al: “An Empirical Evaluation of Fault-Proneness Models”; Proceedings of International Conference on Software Engineering; pp. 241-251; 2002.
K. El Emam; et al; “The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics”; IEEE Transactions on Software Engineering; pp. 630-650; 2001.
S.M. Henry, et al; “Software Structure Metrics Based on Information Flow”; IEEE Transactions on Software Engineering; pp. 510-518; 1981.
T. J. McCabe; “A Complexity Measure”; IEEE Transactions on Software Engineering; pp. 308-320; 1976.
N. Nagappan, et al; “Mining Metrics to Predict Component Failures”; Proceedings of International Conference on Software Engineering; pp. 452-461; 2006.
R. Subramanyam; “Empirical Analysis of CK Metrics for Object-Oriented Design Complexity: Implications for Software Defects”; IEEE Transactions on Software Engineering, vol. 29.; pp. 297-310; 2003.
M.H. Tang, et al; “An Empirical Study on Object-Oriented Metrics”; Proceedings of Sixth International Software metrics Symposium; pp. 242-249; 1999.

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Technologies for code failure proneness estimation does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Technologies for code failure proneness estimation, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Technologies for code failure proneness estimation will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2657682

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.