Internal TestingInternal Testing& Product Freeze& Product FreezeCEE 373RoadmapSANDBOXModeling concepts,scales and approachesSANDBOXProgramminglanguages, softwareengineering &numerical methodsDESIGNIMPLEMENTATIONExamination ofEquilibrium-basedCodeIMPLEMENTATIONExamination ofReaction Rate-basedCodeIMPLEMENTATIONExamination ofExisting Models forComplex SystemsProject ProposalIMPLEMENTATIONVisualization, InterfaceDesign and UsabilityREADINESSInternal Testing andCode FreezeRELEASEFinal Presentations("Rollout")Software EngineeringSKELETONDefine the logic, dataand shell structures.No features included.PROTOTYPINGProof-of-conceptcode. Primitivefeatures.DEVELOPMENTα CANDIDATESFeatures are stableenough for testing.β CANDIDATESWhole package isstable enough fortesting.FINAL CANDIDATESWhole package isstable enough forcompatibility testing.Development offeatures as stated inrequirementsdocuments.GM CANDIDATESWhole package meetsrequirements forproduction.FROZEN PRODUCTPackage is designatedas to be sent intomass production.RELEASED PRODUCTProduct that isreleased to users.Software Quality AssuranceDESIGN TESTINGTesting design ideas.WHITE BOX TESTINGUse understandingand access to thesource code todevelop test cases.BLACK BOX TESTINGTest planningAcceptance testingInitial stability assessmentFunction test, system test, verification, andvalidationBeta testingIntegrity and release testingFinal acceptance testing and certificationREGRESSION TESTINGMake sure that a fix does what it's supposed to do.Make sure that the change didn't disturb anything else.BugsREPORTING & ANALYZINGTESTERExplain how to reproduce the problem.Analyze the error so you can describe it in aminimum number of steps.Write a report that is complete, easy to understand,and non-antagonistic.Assigns severity rating.PROJECT MANAGERAssigns bug to a programmer.Assigns priority rating and current status.TRACKINGTeam members can track the status of a bug.Project Manager produces periodic bug reports.Project Manager leads bug review meetings to decidewhether bugs are fixed, not fixed, causing a newproblem, irreproducible, deferred, or not a bug.Deferrals are used to "close" all lingering bugs so aproduct can ship to a user.Tracking system metrics is used to compare growingnumber of bugs versus rate of closure.Bug TrackingLet's Test Your Product1. What's your test plan?2. Let's start going through the plan.3. Record the bugs.4. Fix the bugs.5. Keep track of bug metrics.6. Scrub the bugs.7. How far are you from code freeze?Putting it in the hands of the user1. Code Freeze - when engineering is over.2. BOM - assembling the parts.3. Staging - your release practice run.4. Readiness - last look over.5. Release - opening the gate.6. Publicity - getting attention.7. Support and response - keeping