Symptomatic Analysis for Software Maintenane SERC软件维护性分析电监会.pptVIP

* Most Complex Product Built by Humans Maintenance: (no health management) fixes and updates Cost of maintenance is very high. A system not designed for maintenance cannot have maintainability retrofitted later. Many different opinions of maintainability. Each organization develops their own definition and concentrates on efforts to develop mature production processes. Process maturity is not enough to guarantee the quality of a specific software product. Process evaluation should always be accompanied by product evaluation. PRODUCT CERTIFICATION IS ALMOST NON-EXISTENT ! Today’s Software Maintenance Realities What can be observed (learned) from health maintenance? Continuous Relies on a large number of facts obtained Reaches an accurate conclusion depending on the timing and the sequence of the symptoms Case history remains an important tool to determine the nature of an illness Future with Symptomatic Analysis for Software Maintenance A holistic infrastructure approach ( similar to Health Management) Continuously measures and evaluates software products through intelligent, automated diagnostic and prognostic programs Provides feedback to process and product improvement by imparting practitioners with an understanding of the condition of their software today and an assurance of its operational state tomorrow.? Based on the design metrics research of 18+ years through the SERC Design metric analysis Module Signatures Time-slices Clones Error (change) analysis The Foundations for the Symptomatic Analysis Process The design metrics have been computed on Raytheon defense systems CSC’s STANFINS project systems from the US Army Research Lab Magnavox’s AFATDS project Harris’ ROCC project three Northrop Grumman projects PBX system from Telcordia Technologies telecommunications systems from Motorola Results: The design metrics typically identify 90% of the fault-prone modules. Module Signature Algorithmic classification No incomplete or inconsistent data