Implementation PhaseSlide 2Implementation Planning & DesignCode & Unit TestQualityProposed System Test ScheduleDue June 26 Class6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 1Implementation PhaseInputs:Development strategy & planCompleted, inspected & baselined SRS & SDSStandards (e.g. coding, name glossary)Outputs:Completed, Inspected & Configuration Controlled Software ComponentsINS & LOGD forms for design & code inspectionsUnit test plans & support materialsUnit test & Integration test passed for all system software componentsCompleted & reviewed user documentationUpdated SUMP, SUMQ & LOGT formsUpdated project notebook6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 2Implementation PhaseInputs:System integrated and passes Unit Test & Integration TestCompleted, Inspected and Configuration controlled software componentsOutputs:LOGTEST Forms (System Tester)LOGD forms for all testing (Change Counter producer)Updated SUMP, SUMQ & LOGT formsUpdated project notebook6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 3Implementation Planning & DesignImplementation PlanningReview work & ensure all tasks are assignedDetailed design & design reviewPsuedo-code, comment blocks, your choicePersonal design reviewUnit test DevelopmentDevelop special unit-test code & facilities (e.g. unit test harness, stubs)Standard test coverage:Logic decisions & pathsLoop stepping & terminationVariables & parameters – nominal/middle, upper & lower boundariesError conditionsDetailed Design Inspection (Review)1-2 Developers, INS form & LOGDCoding & Code Review6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 4Code & Unit TestCoding & Code ReviewEstimate defects prior to personal code reviewCode & execute personal code reviewRecommend several passes – looking for different defects on each pass (see PSP checklist)Execute “buddy” code reviewPlan vs. Actual CheckDesign, Design Review, Code & Code Review time to quality planDefect Levels & Defect Rates to quality planQuality criteriaDesign time > coding timeDesign review time > 50% of design timeCode review time > 50% of coding timeCode review defects > 2x compile found defects3+ defects / review hour< 200 LOC / review hourExecute Unit Test per plan6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 5QualityNot just defect ratesReadability / Maintainability (e.g. good comment etiquette, indenting)Easy to understand design6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 6Proposed System Test ScheduleNote: Assumes system has already passed Integration TestFull feature to system test and instructor by COB June 25 including:Test environmentExecutableUser documentation (note: CCRs can be filed against user documentation)Source codeTester generates CCRs for all finds & fills out LOGTESTEmail to instructor when generated (see below)Development team updates LOGD referencing CCRsRequired turn-around times for fixes80% within 24 hours99% within 48 hoursRequired test coverage short of blocking issues80% First Pass Test Complete by June 28 100% First Pass Test Complete by June 30Regression Test Complete by July 3Daily test reports to instructor detailing test cases executed, results & CCRs6/19/2007 SE 652 - 2007_6_19_TSPImp_SVT_Lecture.ppt 7Due June 26 ClassDraft Measurment PlanAll Test Quality Records (LOGTEST, LOGD, CCRs, etc.)Unit & Integration TestUpdated Products (code components, SRS, HLD, User Documentation)Intermediate Products (e.g. Unit Test Plans)Key Metrics Presentation (10-15 minutes)No class on July 3Note: July 10 class will do a full cycle 1