实用商务经典模板17.pptVIP

PASTE at Microsoft Manuvir Das Talking the talk … Program analysis technology can make a huge impact on how software is engineered The trick is to properly balance research on new techniques with a focus on deployment The Center for Software Excellence (CSE) at Microsoft is doing this (well?) today … walking the walk Program Analysis group in June 2005 Filed 7000+ bugs Automatically added 10,000+ specifications Answered hundreds of emails (one future version of one product) We are program analysis researchers but we live and breathe deployment adoption and we feel the pain of the customer Context The Nail (Windows) Manual processes do not scale to “real” software The Hammer (Program Analysis) Automated methods for “searching” programs The Carpenter (CSE) A systematic, heavily automated, approach to improving the “quality” of software What is program analysis? grep == program analysis program analysis == grep syntax trees, CFGs, instrumentation, alias analysis, dataflow analysis, dependency analysis, binary analysis, automated debugging, fault isolation, testing, symbolic evaluation, model checking, specifications, … Roadmap (part of) The engineering process today (some of) The tools that enable the process (a few) Program analyses behind the tools (too many) Lessons learned along the way (too few) Suggestions for future research Engineering process Methodology Root cause analysis Understand important failures in a deep way Every MSRC bulletin Beta release feedback Watson crash reports Self host Bug databases Design and adjust the engineering process to ensure that these failures are prevented Measurement Measure everything about the process Code quality Code velocity Tools effectiveness Developer productivity Tweak the process accordingly Process – Build Architecture Process – Quality Gates Lightweight tools run on developer desktop team level branches issues tracked within the program artifacts Enforced by rejection at gate Process – Automated Bug Filing H