SoftwaredevelopmentPlanThisdocumentoutlineisbasedontheIEEEStandard1058.1-1987forSoftwareProjectManagementPlans.Thisisthecontrollingdocumentformanagingasoftwareproject,anditdefinesthetechnicalandmanagerialprocessesnecessarytodelivertheprojectrequirements.Theparagraphswritteninthe“Comment”styleareforthebenefitofthepersonwritingthedocumentandshouldberemovedbeforethedocumentisfinalized.VERSIoN:DRAFT25APRIL,2022[AUTHORS]REVISIONCHARTThischartcontainsahistoryofthisdocument'srevisions.Theentriesbelowareprovidedsolforpurposesofillustration.Entriesshouldbedeleteduntiltherevisiontheyrefertohasactuallybeencreated.Thedocumentitselfshouldbestoredinrevisioncontrol,andabriefdescriptionofeachversionshouldbeenteredintherevisioncontrolsystem.Thatbriefdescriptioncanberepeatedinthissection.Revisionsdonotneedtobedescribedelsewhereinthedocumentexceptinasmuchastheyexplainthedevelopmentplanitself.VersionPrimaryAuthor(s)DescriptionofVersionDateCompletedDraftTBDInitialdraftcreatedfordistributionandreviewcommentsTBDPreliminaryTBDSeconddraftincorporatinginitialreviewcomments,distributedforfinalreviewTBDFinalTBDFirstcompletedraft,whichisplacedunderchangecontrolTBDRevision1TBDReviseddraft,revisedaccordingtothechangecontrolprocessandmaintainedunderchangecontrolTBDRevision2TBDReviseddraft,revisedaccordingtothechangecontrolprocessandmaintainedunderchangecontrolTBDetc.TBDTBDTBDPREFACECONTENTSNewparagraphsformattedasHeading1,Heading2,andHeading3willbeaddedtothetableautomatically.ToupdatethistableofcontentsinMicrosoftWord,putthecursoranywhereinthetableandpressF9.Ifyouwantthetabletobeeasytomaintain,donotchangeitmanually.TOC\o"1-5"\h\zINTRODUCTION 6\o"CurrentDocument"PROJECTOVERVIEW 6\o"CurrentDocument"PROJECTDELIVERABLES 6\o"CurrentDocument"EVOLUTIONOFTHESOFTWAREPROJECTMANAGEMENTPLAN 6\o"CurrentDocument"REFERENCEMATERIALS 6\o"CurrentDocument"DEFINITIONSANDACRONYMS 7PROJECTORGANIZATION 8\o"CurrentDocument"PROCESSMODEL 8\o"CurrentDocument"ORGANIZATIONALSTRUCTURE 8\o"CurrentDocument"ORGANIZATIONALBOUNDARIESANDINTERFACES 9\o"CurrentDocument"PROJECTRESPONSIBILITIES 10\o"CurrentDocument"MANAGERIALPROCESS 11\o"CurrentDocument"MANAGEMENTOBJECTIVESANDPRIORITIES 11\o"CurrentDocument"ASSUMPTIONS,DEPENDENCIES,ANDCONSTRAINTS 11\o"CurrentDocument"RISKMANAGEMENT 11\o"CurrentDocument"MONITORINGANDCONTROLLINGMECHANISMS 11\o"CurrentDocument"STAFFINGPLAN 12TECHNICALPROCESS 13\o"CurrentDocument"METHODS,TOOLS,ANDTECHNIQUES 13\o"CurrentDocument"SOFTWAREDOCUMENTATION 13\o"CurrentDocument"PROJECTSUPPORTFUNCTIONS 145.WORKPACKAGES,SCHEDULE,ANDBUDGET 15\o"CurrentDocument"WORKPACKAGES 15\o"CurrentDocument"DEPENDENCIES 15\o"CurrentDocument"RESOURCEREQUIREMENTS 15\o"CurrentDocument"BUDGETANDRESOURCEALLOCATION 15\o"CurrentDocument"SCHEDULE 156.ADDITIONALCOMPONENTS 167.INDEX 178.APPENDICES 18ListofFiguresNewfiguresthataregivencaptionsusingtheCaptionparagraphstylewillbeaddedtothetableautomatically.ToupdatethistableofcontentsinMicrosoftWord,putthecursoranywhereinthetableandpressF9.Ifyouwantthetabletobeeasytomaintain,donotchangeitmanually.Thissectioncanbedeletedifthedocumentcontainsnofiguresorifotherwisedesired.Error!Notableoffiguresentriesfound.INTRODUCTIONThissectionshoulddescribetheprojectandthesoftwareproductbeingtobebuilt.Notextisnecessarybetweentheheadingaboveandtheheadingbelowunlessotherwisedesired.ProjectOverviewGiveashortsummaryoftheprojectobjectives,thesoftwaretobedelivered,majoractivities,majordeliverables,majormilestones,requiredresources,andtop-levelscheduleandbudget.Describetherelationshipofthisprojecttootherprojects,ifappropriate.ProjectDeliverablesListallofthemajoritemstobedeliveredtothecustomer(externalcustomer,in-houseuser,etc.).Listthedeliverables,deliverydates,deliverylocations,deliverymethod(email,FTP,CD,etc.),andquantitiesnecessarytosatisfytheproject'srequirements.EvolutionoftheSoftwareProjectManagementPlanDescribehowyouexpectthisdocumenttoevolveovertime.Thissectionshouldbeverysimilartothe“RevisionChart”earlierinthedocument.Therevisionchartshouldlistwhathasalreadybeendonetothisdocument.Thissectionshouldlistwhatisexpectedtobedonetothisdocument.Thischartcontainsaplanforthedocument'srevisions.Theentriesbelowareprovidedforpurposesofillustration.Theprogressionfrom“Draft”to“Preliminary”to“Final”andthenthroughasectionof“Revisions”isonetypicalapproach.VersionPrimaryAuthor(s)DescriptionofVersionDateExpectedDraftTBDInitialdraftcreatedfordistributionandreviewcommentsTBDPreliminaryTBDSeconddraftincorporatinginitialreviewcomments,distributedforfinalreviewTBDFinalTBDFirstcompletedraft,whichisplacedunderchangecontrolTBDRevision1TBDReviseddraft,revisedaccordingtothechangecontrolprocessandmaintainedunderchangecontrolTBDetc.TBDTBDTBDReferenceMaterialsListallthedocumentsandothermaterialsreferencedinthisdocument.Thissectionislikethebibliographyinapublishedbook.DefinitionsandAcronymsProvidedefinitionsorreferencestoallthedefinitionsofthespecialtermsandacronymsusedwithinthisdocument.2.PROJECTORGANIZATIONInthissection,describetheprocessmodel(e.g.,lifecyclemodel),theorganizationalstructure(e.g.,chainofcommandormanagementreportingstructure),andresponsibilitiesofindividualsontheproject.Notextisnecessarybetweentheheadingaboveandtheheadingbelowunlessotherwisedesired.ProcessModelDescribethefollowingitems:?Theproject'slifecyclemodel(e.g.,waterfallmodel,spiralmodel,evolutionaryprototypingmodel,etc.)?Theproject'smajormilestones(contentanddates/timing).ThisshouldincludeatextdescriptionofthemeaningofeachmilestoneplusaGanttchartorotherhigh-leveldescriptionoftheproject'sschedule.?Majorworkproducts,includingcontentandtiming.Theseshouldbelistedinatablelikethefollowingone:WorkProductNamePlannedCompletionDatePlacedUnderChangeControl?DeliverabletoCustomer?PeopleWhoMustSignOffontheWorkProductSoftwareProjectManagementPlanThisisthecontrollingdocumentformanagingasoftwareproject,anditdefinesthetechnicalandmanagerialprocessesnecessarytodelivertheprojectrequirements.TBDYesNoProjectManager,EngineeringLead,QALead,DocumentationLeadTBDTBDTBDTBDTBDYoushouldconsiderincludingallofthetop-levelworkproductsdescribedinSPSG,including:?ChangeControlPlan?ChangeProposals?Visionstatement?Top10RisksList?SoftwareDevelopmentPlan,includingprojectcostandscheduleestimates?UserInterfaceStyleGuide?UserManual/RequirementsSpecification?QualityAssurancePlan?SoftwareArchitecture?SoftwareIntegrationProcedure?StagedDeliveryPlan?IndividualStagePlans,includingminiaturemilestoneschedules?CodingStandard?DetailedDesignDocuments?SoftwareConstructionPlans?DeploymentDocument(CutoverHandbook)?ReleaseChecklist?ReleaseSign-OffForm?SoftwareProjectLog?SoftwareProjectHistoryDocumentTheitemsinthissection(and,ingeneral,inthisdocument)canbefullydescribedhere,or,iftheyaredescribedinsufficientdetailelsewhere,thatdescriptioncansimplybereferencedhere.OrganizationalStructureDescribetheinternalmanagementstructureoftheproject.Useorgcharts,matrixdiagrams,orotherappropriatenotationstodescribethelinesofauthority,responsibility,andcommunicationwithintheproject.OrganizationalBoundariesandInterfacesDescribetherelationshipsbetweentheprojectandeachofthefollowingorganizations:?Parentorganization(uppermanagement)?Customerorganization(internalorexternal)?Subcontractingorganization(s)(ifany)?QAorganization,ifseparate?Documentationorganization,ifseparate?End-usersupportorganization,ifseparate?AnyotherorganizationstheprojectinteractswithThislistshouldincludeadescriptionofaspecificpersonorprojectrolethatisresponsibleformaintainingtheinterfacebetweentheprojectandeachoftheseotherorganizations.Besuretoidentifythepersonwhohasultimatedecision-makingauthorityovertheproject.

ProjectResponsibilitiesIdentifyanddescribeeachmajorprojectfunctionandactivity,andidentifytheperson(s)responsibleforeachfunctionandactivity.Youmightuseatableliketheonebelow:ResponsibilityPersonsresponsibleOverallProjectManagerTBDEngineeringManagerTBDQualityAssuranceManagerTBDEnd-UserDocumentationManagerTBDRequirementsDevelopmentTBDSoftwareArchitectureTBDTechnicalSelf-ReviewsTBDEtc.TBD3?ManagerialProcessDescribemanagementobjectives,priorities,projectassumptions,dependencies,constraints,riskmanagementtechniques,monitoringandcontrollingmechanisms,andthestaffingplan.Notextisnecessarybetweentheheadingaboveandtheheadingbelowunlessotherwisedesired.ManagementObjectivesandPrioritiesDescribethephilosophy,goals,andprioritiesformanagementduringtheproject.Considerincludingthefollowingitems:?kindofstatusreporting?relativeprioritiesamongfunctionality,schedule,andbudget?riskmanagementprocedures?approachtoacquiringthirdpartysoftware?approachtomodifyingorusingexistingsoftwareAssumptions,Dependencies,andConstraintsDescribetheassumptionsuponwhichtheprojectplansarebased,thedependenciesoftheprojectplans,andtheconstraintsupontheprojectplans(e.g.,schedule,budget,quality,functionality,etc.)RiskManagementDescribethemajorriskstotheproject,whichtheprojectplanhasbeendesignedtoaddress.Describehowriskswillbetrackedandmonitored—usingaTop10Riskslist,riskofficer,orsoon.MonitoringandControllingMechanismsDescribehowprojectcost,schedule,quality,andfunctionalitywillbetrackedthroughouttheproject.Considerdescribingthefollowing:?Reportcontents/formats?Reportingstructureandfrequency?Auditmechanisms?Projectwebsite?TimeaccountingStaffingPlanDescribethenumbersandtypesofpersonnelneededtoconducttheproject.Describetherequiredskilllevels,starttimes,durationontheproject,methodofobtainingthepersonnel,trainingrequired,andphasingoutofprojectpersonnel.TECHNICALPROCESSThissectiondescribesthetop-leveltechnicalprocessesusedontheprojectincludingthetechnicalmethods,tools,andtechniques;majorsoftwaredocuments;andsupportingactivitiessuchasconfigurationmanagementandqualityassurance.Notextisnecessarybetweentheheadingaboveandtheheadingbelowunlessotherwisedesired.Methods,Tools,andTechniquesDescribethefollowing:?Thecomputingsystemenvironmentincludinghardwareandoperatingsystemenvironment;?Softwaretoolsincludingdesigntools,sourcecodecontrol,timeaccounting,compilerorIDE,debuggingaids,defecttracking,andsoon?Developmentmethodologiesincludingrequirementsdevelopmentpractices,designmethodologiesandnotations,programminglanguage,codingstandards,documentationstandards,systemintegrationprocedure,andsoon(thesewillnotallbedefinedwhenthefirstdraftoftheprojectplaniscreated;thesectionshouldbeupdatedastheplansbecomemoredetailed)?Qualityassurancepracticesincludingmethodsoftechnicalpeerreview,unittesting,steppingthroughcodeinadebugger,systemtesting,automatedregressiontests,andsoonSoftwareDocumentationListthedocumentsthatwillbedevelopedfortheproject,includingmilestones,reviews,andsignoffsforeachdocument.Thedocumentationlistmightincludethefollowdocuments:?ChangeControlPlan?ChangeProposals?Visionstatement?Top10RisksList?SoftwareDevelopmentPlan,includingprojectcostandscheduleestimates?UserInterfaceStyleGuide?UserManual/RequirementsSpecification?QualityAssurancePlan?SoftwareArchitecture?SoftwareIntegrationProcedure?StagedDeliveryPlan?IndividualStagePlans,includingminiaturemilestoneschedules?CodingStandard?DetailedDesignDocuments?SoftwareConstructionPlans?DeploymentDocument(CutoverHandbook)?ReleaseChecklist?ReleaseSign-OffForm?SoftwareProjectLog?SoftwareProjectHistoryDocumentProjectSupportFunctionsDescribeorgivereferencestootherdocumentsthatdescribetheplansforfunctionsthatsupportthesoftwaredevelopmenteffort,includingconfigurationmanagement,qualityassurance,andenduserdocumentation.Whetherincludedinthisdocumentordescribedelsewhere,theplansforthesesupportingfunctionsshouldbedevelopedinasmuchdetailastheplansforthesoftwareitselfare.(Thisincludesresponsibilities,resourcerequirements,schedule,budget,andsoon.)WORKPACKAGES,SCHEDULE,ANDBUDGETNotextisnecessarybetweentheheadingaboveandtheheadingbelowunlessotherwisedesired.5.1WorkPackagesDescribetheworkpackage(i.e.,taskorcollectionoftasks)thatmustbecompletedtocompletethesoftware.Identifyeachworkpackagewithauniquenumber,andprovideadiagramshowingthebreakdownofworkpackagesintosub-packages.DependenciesDescribethedependenciesbothamongworkpackagesandbetweentheproject'sworkpackagesandexternalevents.ResourceRequirementsDescribetheresourcesrequiredfortheprojectweekbyweekormonthbymonth,dependingonthelengthoftheproject.Describethenumbersandtypeofpersonnelthatareused,numberofcomputersandsoftwareused,officefacilitiesused,trainingneeded,budgetused,andsoonoverthewholecourseoftheproject.BudgetandResourceAllocationDescribetheportionoftheproject'sbudgetallocatedtodifferentfunctions(e.g.,engineering,qualityassurance,documentation,management).Describehowthebudgetwillbeexpendedoverthecourseoftheproject.ScheduleDescribethescheduleforthevariousprojectfunctions,activities,andtasks,takingintoaccountthevariousdependenciesandrequiredmilestonedatesanddeliverabledates.Youcanexpressscheduleseitherasabsolutecalendardatesorastimesrelativetokeyprojectmilestones(e.g.,“requirementssignedoff+60days”).ADDITIONALCOMPONENTSIncludeadditionalcomponentsneededtomanageyourspecificproject.Possibilitiesincludesubcontractormanagementplans,securityplans,trainingplans,hardwareprocurementplans,facilitiesplans,installationplans,cutoverplans,andsoftwaremaintenanceplans.7.INDEXThein