University of Southern California Center for Systems and Software Engineering Core Capability Drive-Through (CCD) Feedback Pongtip Aroonvatanaporn CSCI 577b Spring 2010 March 31, 2010 April 1, 20091

University of Southern California Center for Systems and Software Engineering Outline Grading criteria Highlights IKIWISI Problem Suggestions Q & A April 1, 20092

University of Southern California Center for Systems and Software Engineering Grading Criteria Total of 20 points –Progress as plan (3) –Quality of CCD Completeness of functionalities (10) –Team readiness Quality of documents (3) Test data/Scenarios (3) People readiness (1) April 1, 20093

University of Southern California Center for Systems and Software Engineering Highlights Generally done well Responded well to dramatic changes Some clients knew the system very well Most teams followed the plan well –With some exceptions Most teams are on the right track Every team prepared some test scenarios and data April 1, 20094

University of Southern California Center for Systems and Software Engineering The IKIWISI What IKIWISI stands for Classic problem that occurs in software development Understanding of client’s perspective –Requirements knowledge –Asking the “What about…” question –Consider all scenarios April 1, 20095

University of Southern California Center for Systems and Software Engineering Suggestions (1) Understanding the purpose of CCD –Client –Developers Collaboration with DR/Programmer Eager to direct client –Not intuitive? April 1, 20096

University of Southern California Center for Systems and Software Engineering Suggestions (2) Take UI into considerations –Think in the perspective of end users –How to make it user friendly –“We developed this based on the requirements” –Productive to use the system? –Always verify with the client. No surprises Many lack collaboration with client User’s manual should not be overwhelming April 1, 20097

University of Southern California Center for Systems and Software Engineering Suggestions (3) Completeness of functionalities –Most are not 100% –Determine most critical capabilities –Should reflect what the plan says Respect client’s suggestions –Key to success –May have suggestions that differ from the initial requirements –Be flexible April 1, 20098

University of Southern California Center for Systems and Software Engineering Suggestions (4) Set up –HW, SW, etc. Testing –Run tests prior to CCD –Use same machine April 1, 20099

University of Southern California Center for Systems and Software Engineering Questions? April 1,