C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009

C O N F I D E N T I A L 22-Oct-15 2 Agenda Quarterly Engineering top priorities Shanghai Engineering team weekly update – 5 minutes – Releases schedule overview – Unit Test weekly progress chart – Rally Iteration Weekly status – Engineering Operation Metrics – QA metrics Special Topics – 10 minutes – Complete Agile progress in SM – Leslie – Code review process - Justin Q&A

C O N F I D E N T I A L 22-Oct-15 3 Engineering Q1/09 Top 3 Priorities (aligned) PriorityDescriptionBusiness BenefitProjects Involved 1 Performance, Stability and Quality -Customer Satisfaction and Adoption -Improved performance under increased load from grow growth and migration -Improved quality with increased usage from growth and migration -Reduce long term operation cost -SM -MarketView -CBS – Search/UAS -Mpoint.com -Reporting 2 Migration -Customer retention -Reduced complexity -Strategic advantage to single suite -Spend Mgmt -Attendee Mgmt -MarketView -Reporting 3 New Revenue - By new features or new projects -By enhanced features -New product / services -Attendee Mgmt (Event Marketing) -Reporting (Buyer, Supplier) -SM -StarCite Express -MKV -More … Absolutely has to happen – put best effort and team to meet the metrics and dates

C O N F I D E N T I A L 22-Oct-15 4 Performance, Stability and Quality – Why, What and How Why? To improve internal quality to enhance both the functional and non- functional quality of our products to satisfy customers To gain business benefits What to do? 1.Effective code review including design review 2.Unit test coverage and effectiveness 3.SQL profiling 4.Code re-factoring How? To re-enforce code review, unit test and SQL profiling; to make them as part of the development work To provide guideline and good examples, to build good practice, To be measurable; to know where we are today; to set near- and long- term target; to track progress;

C O N F I D E N T I A L 22-Oct-15 5 Release Schedule in Q1/2009 ProjectRelease DateVersion SM Feb 18, 2009 March 29, Reporting Feb 20, G2 AM Feb 17, 2009 Feb 24, 2009 March 28, hotfix MKV Feb 25, 2009 March 25, 2009 MKV86 MKV87 Mpoint.com March 9, 2009 (Target date)Mpoint.com CBS – Search Feb 2, 2009Search

C O N F I D E N T I A L 22-Oct-15 6 Unit Test Objectives PriorityDescriptionBusiness Benefit 1 Quality improvement Improved quality level for all products. Reduction in regressions and customer issues 2 Predictable, aggressive, re- factoring Reduces risk and potential impact in aggressive performance and maintainability improvements 3 Overhead reduction for development and testing Shorter release cycles, more stories per sprint 4 Fail fast development Failures found sooner in development cycle. Allows faster course correction and more predictability in product delivery

C O N F I D E N T I A L 22-Oct-15 7 Current Unit Test Coverage Numbers – by last Friday ProjectClassesLine Coverage Branch Coverage Complexity Mpoint.com 34087%90% MarketView 61349%54%1.709 Spend Management %11% CBS – UAS* 0*0* (92%)0* (81%) CBS - Search* 10575%65% * Newly started project, has no unit test coverage yet

C O N F I D E N T I A L 22-Oct-15 8 QA Automation – Accomplished in 2008 ProductCategory Q42008 QTP QTP % SM smoke % SM UAT % Maintenance % MKV smoke % UAT - RFP WF % UAT - non RFP WF % Maintenance % G2AM smoke % UAT % Configuration Test % Reporting Smoke % UAT %

C O N F I D E N T I A L 22-Oct-15 9 QA Automation – Q Target ProductCategory Q QTP SMUAT 77% MKV UAT RFP WF 80% UAT - non RFP WF 80% G2 AM UAT 100% Configuration Test 100% Reporting smoke 100% UAT 58% 100% Smoke test script get updated

C O N F I D E N T I A L 22-Oct Engineering Operation metrics *3 customer discovered S0 – due to server out of memory. Total Open/Closed Level1 (Last 7 days)

C O N F I D E N T I A L 22-Oct Engineering Operation metrics (cont.) Level1 Status and Assignment (Last 7 days)

C O N F I D E N T I A L 22-Oct QA metrics – Q release review

C O N F I D E N T I A L 22-Oct QA metrics – Q release review

C O N F I D E N T I A L 22-Oct QA metrics – Q release review

C O N F I D E N T I A L 22-Oct QA metrics – Q release review

C O N F I D E N T I A L 22-Oct Special Topics – Complete Agile SM – sprint 1 SM – sprint 2 Big improvement is evident by comparing the iteration burn down charts -- SM – sprint 2 shows healthier burn down chart than the SM – sprint 1 -- SM – sprint 2 accomplished much more story points by last day of the iteration

C O N F I D E N T I A L 22-Oct Special Topics – Code Review process Cross Code Review Purpose: promote a culture “team excellent” of 2009 goals from Yang, and an attitude “I DO welcome anyone reviewing my codes and it can help me grow faster“. Focus: most important technique hotspots: 1.Out-of-memory issue identified by operation team 2.Unexpected server restart identified by operation team 3.Very long DB operations identified by SQL profiling log and app Log 4.Legacy codes need re-factor and the new codes 5.Other important issues identified by Team Peer Code Review Purpose: improve code quality by regular code review activities Focus: 1.All new codes have to be reviewed and the activities must be tracked on Rally. 2.Legacy codes are encouraged to have more code reviews and related action plans

C O N F I D E N T I A L 22-Oct Special Topics – Code Review process Encourage Plan 1.Performance bonus: code review efficiency (including frequency and quality) will be treated as one very important performance metric of team member. 2.Recognition: we will recognize the best engineers for the contribution on code review activities and the detailed plan will be decided later. 3.Leaning Credits: the engineers with good contribution on code review activities will get extra leaning credits to get encouraged. Introduce a web based tool for code review: Review Board which developed by Vmvare( Evaluation is underway. If anyone is interested, please come forward and talk to Justin

C O N F I D E N T I A L 22-Oct Mr. Q&A