SoftwareProcessesObjectivesTopicscoveredProcessactivitiesSoftwarespecificationTherequirementsengineeringprocessSoftwaredesignandimplementationDesignprocessactivitiesThesoftwaredesignprocessStructuredmethodsProgramminganddebuggingThedebuggingprocessSoftwarevalidationThetestingprocessTestingStagesTestingphasesSoftwareevolutionSystemevolutionMidpointreviewGenericsoftwareprocessmodelsWaterfallmodelWaterfallmodelproblemsEvolutionarydevelopmentEvolutionarydevelopmentEvolutionarydevelopmentComponent-basedsoftwareengineeringReuse-orienteddevelopmentProcessiterationIncrementaldeliveryIncrementaldevelopmentIncrementaldevelopmentadvantagesExtremeprogrammingSpiraldevelopmentSpiralmodel-BoehmSpiralmodelsectorsTheRationalUnifiedProcessRUPphasesRUPgoodpracticeTheSEIprocessmaturitymodelKeyprocessareasItfocusesonprojectmanagementratherthanproductdevelopment.Itignorestheuseoftechnologiessuchasrapidprototyping.ItdoesnotincorporateriskanalysisasakeyprocessareaItdoesnotdefineitsdomainofapplicabilityWhereverpossible,quantitativeprocessdatashouldbecollectedVerydifficultwhereorganisationsdon’thaveclearlydefinedprocessstandards,asyoudon’tknowwhattomeasure-aprocessmayhavetobedefinedbeforeanymeasurementispossible.ProcessmeasurementsshouldbeusedtoassessprocessimprovementsTheimprovementsdriveristheorganizationalobjectives,notthemeasurements.Timetakenforprocessactivitiestobecompleted-e.g.Calendartimeorefforttocompleteanactivityorprocess.Resourcesrequiredforprocessesoractivities-e.g.Totaleffortinperson-days.Numberofoccurrencesofaparticularevent-e.g.Numberofdefectsdiscovered.KeypointsKeypoints