SoftwareProjectManagementPlan
Version200
SoftwareEngineeringProject
EindhovenUniversityofTechnology.Eindhoven
SvenBego0550191
RoelCoset0548132
RobertLeeuwestein0546746
MaartenLeijten0547649
IvovanderLinden0547632
JoeryMens0547515
MarcelMoreaux0499480
TimMuller0547961
Manager:T.M.G.Kleijkers0515015
SoftwareProjectManagementPlanversion200
A.Abstract
ThisistheSoftwareProjectManagementPlan(SPMP)fortheSPINGRIDproject.Thisprojectisoneoftheseven
assignmentsforthecourse2IP40atEindhovenUniversityofTechnology.Thisdocumentcomplieswiththe
SPMPfromtheSoftwareEngineeringStandard,assetbytheEuropeanSpaceAgency[ESA].TheSPMPisused
bytheProjectManager(PM)toguidetheprojectandtocometoanagreementwiththecustomeraboutbudgets
andplanning.ThePMusestheSPMPtoorganizetheprojectindifferentphases,i.e.toarrangetheteamsand
theirtasksandtosetdeadlines.Thisdocumentisrelatedto[SQAP],whichdescribesallphasesoftheproject.
Monday,June12,2006
Page2of24
SoftwareProjectManagementPlanversion200
B.Tableofcontents
10
15
20
25
30
35
40
45
50
A.Abstract ...............................................................................................................................................................................2
B.Tableofcontents.................................................................................................................................................................3
C.DocumentStatusSheet......................................................................................................................................................5
D.DocumentChangeRecordSincePreviousIssue...........................................................................................................6
1.Introduction.........................................................................................................................................................................7
1.1.Projectoverview...........................................................................................................................................................7
1.2.Projectdeliverables......................................................................................................................................................7
1.3.EvolutionoftheSPMP ................................................................................................................................................7
1.4.Listofdefinitions .........................................................................................................................................................8
1.5.Listofreferences ..........................................................................................................................................................8
2.ProjectOrganization...........................................................................................................................................................9
2.1.ProcessModel...............................................................................................................................................................9
2.2.OrganizationalStructure ..........................................................................................................................................10
2.3.BoundariesandInterfaces ........................................................................................................................................10
2.4.Projectresponsibilities...............................................................................................................................................10
3.ManagerialProcess...........................................................................................................................................................12
3.1.ObjectivesandPriorities ...........................................................................................................................................12
3.2.Assumptions,DependenciesandConstraints .......................................................................................................12
3.3.RiskManagement ......................................................................................................................................................12
3.3.1.Riskswithrespecttotheworktobedone.......................................................................................................12
3.3.2.Riskswithrespecttomanagement...................................................................................................................13
3.3.3.Riskswithrespecttoresources .........................................................................................................................13
3.3.4.Riskswithrespecttothecustomer ...................................................................................................................14
3.3.5.Summary ..............................................................................................................................................................14
3.4.MonitoringandControllingMechanisms ..............................................................................................................14
3.5.StaffPlan .....................................................................................................................................................................15
4.TechnicalProcess ..............................................................................................................................................................16
4.1.Methods,ToolsandTechniques ..............................................................................................................................16
4.2.SoftwareDocumentation ..........................................................................................................................................16
4.3.ProjectSupportFunctions.........................................................................................................................................16
5.Workpackages,Schedule,Budget .................................................................................................................................17
5.1.Workpackages ...........................................................................................................................................................17
5.2.Dependencies .............................................................................................................................................................17
5.3.ResourceRequirements.............................................................................................................................................18
5.4.BudgetandResourceAllocation .............................................................................................................................18
5.5.Schedule ......................................................................................................................................................................18
5.6.UnavailabilityOverview...........................................................................................................................................19
AppendixA:URPhase ........................................................................................................................................................20
A.1OutputsURPhase .....................................................................................................................................................20
A.2Teamsandworkpackages .......................................................................................................................................20
AppendixB:SRPhase..........................................................................................................................................................21
B.1OutputsSRPhase .......................................................................................................................................................21
B.2Teams,workpackagesandplanning ......................................................................................................................21
AppendixC:ADPhase ........................................................................................................................................................22
C.1OutputsADPhase .....................................................................................................................................................22
C.2Planningfortherestoftheproject ..........................................................................................................................22
AppendixD:DDPhase........................................................................................................................................................23
Monday,June12,2006
Page3of24
SoftwareProjectManagementPlanversion200
D.1OutputsDDPhase .....................................................................................................................................................23
D.2Teams,workpackagesandplanning......................................................................................................................23
55
Monday,June12,2006
Page4of24
SoftwareProjectManagementPlanversion200
C.DocumentStatusSheet
DocumentTitle
DocumentIdentification
Author(s)
DocumentStatus
DocumentHistory
Version
001
010
011
60
SoftwareProjectManagementPlan
SPINGRID\Documents\Management\SPMP\0.1.0
T.M.G.Kleijkers
Draft/InternallyAccepted/ConditionallyApproved/Approved
Date
Reasonforchange
08122005
Firstversion
23122005
InternallyAccepted
22012006
Removedanerrorinparagraph2.2
Monday,June12,2006
Page5of24
SoftwareProjectManagementPlanversion200
D.DocumentChangeRecordSincePreviousIssue
DocumentTitle
DocumentIdentification
DateofChanges
Page
SoftwareProjectManagementPlan
SPINGRID\Documents\Management\SPMP\1.0.0
N/A
Paragraph
Reasonforchange
Monday,June12,2006
Page6of24
SoftwareProjectManagementPlanversion200
1. Introduction
65
1.1. Projectoverview
IntheSPINGRIDprojectasystemhastobedesignedtosupportgridcalculations.Thesoftwaretobemade
consistsofatleastthreeapplications,whichmustinteractusingtheinternet.Dispatchersgatherjobsfrom
variousSubmittersanddispatchthemtosocalledAgents.Theentiresystemhastobedeveloped(inJAVA)ina
waythatitiseasytomaintainandextend.
70
75
1.2. Projectdeliverables
Duringthecourseoftheproject,severaldocumentshavetobeproducedanddeliveredtothecustomerandto
theSM.AllthesedocumentshavetobewrittenaccordingtotheESAsoftwareengineeringstandards[ESA].All
productsthatwillbedeliveredtotheSMand/orthecustomerarementionedinthetablebelow,togetherwith
thephasesforwhichtheyrepresentoutputs.TheprojectmanagerwillsendmetricstotheSMonaweeklybasis.
Ifthereisaprogressmeeting,thisinformationisdeliveredinaprogressreport,otherwiseametricssheetissent.
Phase
Deliverables
Towhom
Format
UR
URD
ATP
SPMP
SCMP
SQAP
SVVP
SM/customer
SM/customer
SM
SM
SM
SM
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
SR
SRD
STP
SM/customer
SM/customer
Paperandelectronicform
Paperandelectronicform
AD
ADD
ITP
SM/customer
SM/customer
Paperandelectronicform
Paperandelectronicform
DD
DDD
UTP
SUM
STD
Sourcecode
SM/customer
SM/customer
SM/customer
SM/customer
SM/customer
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
Paperandelectronicform
Electronicform
1.3. EvolutionoftheSPMP
80
85
Thisdocumentissubjecttochanges.Theassumptions,dependenciesandconstraintsfortheproject,thedetailed
timeandresourceplanningforeachphase(seeappendices)canchangeduringtheproject.Changesinthis
informationwillleadtoanewSPMPwithanewversionnumber,butwiththesamestatus.However,ifthese
changesleadtochangesinthemilestonesplanningoftheproject,describedinsection5.5,thesechangesare
discussedwiththeSMfirst,beforetheyareincorporatedinthedocument.Thiswillbedoneduringprogress
meetings.Thedetailedplanningforeachphaseisdescribedintheappendicesofthisdocument.These
appendicesareupdatedatdifferentmomentsintimeduringtheproject,butbeforethestartofthephasethey
referto.
Monday,June12,2006
Page7of24
SoftwareProjectManagementPlanversion200
1.4. Listofdefinitions
AD
ADD
ATP
Client
CM
Customer
DD
DDD
Dispatcher
ITP
Monitor
PM
QAM
SCMP
SM
SPMP
SQA
SQAP
SR
SRD
STD
STP
Submitter
SUM
SVVP
TR
UR
URD
UTP
VPM
VQAM
ArchitecturalDesign
ArchitecturalDesignDocument
AcceptanceTestPlan
Monitor,AgentorSubmitter
ConfigurationManagement
DutchSpaceB.V.
DetailedDesign
DetailedDesignDocument
ApplicationthatdispatchesjobstoAgents
IntegrationTestPlan
Applicationthateithermonitorsdispatchers
ProjectManager
QualityAssuranceManager
SoftwareConfigurationManagementPlan
SeniorManagement
SoftwareProjectManagementPlan(thisdocument)
SoftwareQualityAssurance
SoftwareQualityAssurancePlan
SoftwareRequirements
SoftwareRequirementsDocument
SoftwareTransferDocument
SoftwareTestPlan
Applicationthatsubmitsjobstodispatchers
SoftwareUserManual
SoftwareVerificationandValidationPlan
TransferPhase
UserRequirements
UserRequirementsDocument
UnitTestPlan
ViceProjectManager
ViceQualityAssuranceManager
1.5. Listofreferences
[SPMP]
[SCMP]
[SVVP]
[SQAP]
[ESA]
SoftwareProjectManagementPlan
SPINGRIDProject
T.M.G.Kleijkers
SoftwareConfigurationManagementPlan
SPINGRIDProject
SoftwareVerificationandValidationPlan
SPINGRIDProject
SoftwareQualityAssurancePlan
SPINGRIDProject
ESASoftwareEngineeringStandards(ESAPSS050Issue2)
ESABoardforSoftwareStandardizationandControl(BSSC),1991
Monday,June12,2006
Page8of24
SoftwareProjectManagementPlanversion200
2. ProjectOrganization
90
2.1. ProcessModel
TheprocessmodelusedfortheSPINGRIDprojectisthewaterfallmodel.WeusethesocalledVmodel:
95
100
105
Theprojectisdividedinfivephases,whichmayslightlyoverlap.Thesephasesare:
UR(userrequirements)phase
SR(softwarerequirements)phase
AD(architecturaldesign)phase
DD(detaileddesign)phase
TR(transfer)phase
TheURphaseinvolvescreatingthemanagementdocuments(SPMP,SCMP,SVVPandSQAP)andtheURD.
Further,theCMteamhastomakesureallnecessaryhardwareandsoftwareisavailable.
TheDDphaseinvolvescreatingthesourcecodeandtheunit,integrationandsystemtests.Acceptancetestsare
performedduringtheTRphase.
AlthoughtheESASoftwareEngineeringstandardprescribesasixthphase(themaintenancephase)weallow
ourselvestoomitthisphasebecausetheSPINGRIDprojectisterminatedaftertheTRphasehasbeencompleted.
Monday,June12,2006
Page9of24
SoftwareProjectManagementPlanversion200
2.2. OrganizationalStructure
110
115
Inthefollowingtable,theroleswhicharedistinguishedandtheperson(s)assignedtoeachrolearegiven.Roles
withinthegrouparedescribedinsection3.5.
Role
Name
Room
Phone
SeniorManagement
(SM)
L.Somers
Lou.somers@oce.nl
HG7.83 (040247)2805/2733
SeniorManagement
(SM)
T.Punter
t.punter@tue.nl
HG5.71 (040247)3735/2526
Advisor
Y.Usenko
y.s.usenko@tue.nl
HG5.71 (040247)3519/2526
Customer
HansdeWolf
h.de.wolf@dutchspace.nl
Customer
MarkterLinden m.ter.linden@dutchspace.nl
TheTU/eemploystheSMandtheadvisor.AllotherpersonsaremembersoftheSPINGRIDprojectteam.
CommunicationtotheSMisalwaysdonethroughthePM.OnlytheQAMcancontacttheSMdirectlyincasehe
isconcernedaboutthefunctioningofthePM.WhenthePMisunavailableforaperiodtime,theVPMfulfillshis
duties.
2.3. BoundariesandInterfaces
120
125
Duringtheproject,theSPINGRIDprojectteaminteractswithseveralothergroups.Theseare:
TheSM.CommunicationtotheSMprimarilytakesplacethroughthePM.Insomecases,theVPMorthe
QAMcancontacttheSM;
TheAdvisor.Hewillattendsomeweeklymeetingsandmaybeconsultedfortechnicaladvicebyevery
groupmember;
TheCustomer.TheVPMtakescareofthecontactswiththecustomer.
2.4. Projectresponsibilities
130
135
140
ProjectManager
Task:Produceandmaintainaprojectmanagementplanandleadtheprojectaccordingtothisplanthus
ensuringthattheproductisdeliveredontimeandasspecifiedintheURD.ThePMsmanagementtaskincludes
butisnotlimitedto:
Motivatingteammembers;
Formingteamsandassigningtasks;
Checkingprogress;
Managingthetimebudget;
Definingworkpackagesandgoals;
ProvidingfeedbacktotheSMthroughprogressreports.
ViceProjectManager
Task:AssistthePMandreplacethePMwhenthePMisnotavailable.
QualityAssuranceManager
Task:Guaranteethattheproductwillbedeliveredasagreedandthatitisofgoodquality.Thisincludesbutis
notlimitedto:
WritingtheSQAPandtheSVVP;
Monday,June12,2006
Page10of24
SoftwareProjectManagementPlanversion200
145
150
155
160
165
170
VerifyingthatproceduresandstandardswhicharedefinedintheSQAPandSVVPareadheredto;
Checkingthatallprojectdocumentsareconsistent;
Arrangingformalreviews;
Monitoringandreviewingalltestingactivities.
ConfigurationManager
Task:Performversionmanagementfordocumentsandcode.Thisincludesbutisnotlimitedto:
WritingtheSCMP;
Creatingarepositoryforalldocumentsandcode;
Checkingthattherepositoryisusedappropriate(thatisaccordingtotheSCMP)byallteammembers;
MaintainingtherepositoryaccordingtotheSCMP.
TeamLeader
Task:Performallnecessaryactivitiestoensurethatataskassignedtoateamisperformedwellandontime.
Thisincludesbutisnotlimitedto:
Planningandcoordinatingteamactivities;
ProvidingfeedbackaboutteamprogresstothePM;
Motivatingteammembers;
Chairingreviewsoftheitemsmadebyhisteam.
TeamMember
Task:Performallnecessaryactivitiestoensurethatataskassignedtoateamisperformedwellandontime.
Thisincludesbutisnotlimitedto:
AssistingtheTeamLeaderorProjectManagerbysignalingproblemsinanearlystage;
ExecutingplansmadebytheTeamLeaderandbytheProjectManager;
Keepingtrackoftimespentonvarioustasks;
Followingproceduresandplans.
Monday,June12,2006
Page11of24
SoftwareProjectManagementPlanversion200
3. ManagerialProcess
3.1. ObjectivesandPriorities
175
Themanagementobjectiveistodelivertheproductintimeandofhighquality.ThePMandQAMwork
togethertoachievethisbyrespectivelycheckingthatprogressismadeasplannedandmonitoringthequalityof
theproductatvariousstages.
3.2. Assumptions,DependenciesandConstraints
180
Inthisprojectplan,anumberoffactorsaretakenintoaccount.Fortheseseechapter5.5.
DuetothedeadlineofJune14th,runningoutoftimewillhaveitsreflectionontheproduct,andnotonthe
durationoftheproject.Byassigningaprioritytoeveryuserrequirement,aselectioncanbemadeofuser
requirementsthatmaybedroppedoutiftimerunsout.
3.3. RiskManagement
185
190
195
200
205
210
Thissectionmentionsanumberofpossiblerisksfortheproject.Also,actionsormeasuresaredescribedto
preventortoreducetherisks.
Fourcategoriesofrisksareidentified:
1. Riskswithrespecttotheworktobedone;
2. Riskswithrespecttothemanagement;
3. Riskswithrespecttotheresources;
4. Riskswithrespecttothecustomer.
Therisksforeachcategoryarelistedbelow.Foreachrisk,adescription,aprobabilitytooccur,theaction
associatedandtheimpactoftheriskaregiven.
3.3.1. Riskswithrespecttotheworktobedone
Weonlydiscussthemostimportantrisks.
1.Miscommunication
Probability:Medium
Prevention:Afterameeting,onegroupmembercreatesaninterviewreport.Everyparticipantandeveryperson
whoshouldhavebeenaparticipantofthemeetingshouldgetacopyofthisreport.Teammembersshouldnot
hesitatetoaskandreaskquestionsifthingsareunclear.
Correction:Whenitbecomesclearthatmiscommunicationiscausingproblems,theteammembersinvolvedand
thecustomeraregatheredinameetingtoclearthingsup.
Impact:High
2.Timeshortage
Probability:High
Prevention:Careistakentoplanenoughsparetime.
Correction:Whentasksfailtobefinishedintimeorwhentheyarefinishedearlierthanplannedtheproject
planningisadjusted.Iftimeshortagebecomessevere,userrequirements,whichhavelowpriority,aredropped
afterconsultationwiththeSMandthecustomer.
Impact:High
Monday,June12,2006
Page12of24
SoftwareProjectManagementPlanversion200
215
220
225
230
235
3.DesignErrors
Probability:Medium
Prevention:Thedesignshouldbereviewedverycritically.Theadvisorshouldbeconsultedfrequentlyonhis
opinionaboutthefeasibilityandthecorrectnessofcertaindesigndecisions.
Correction:Whenerrorsinthedesignarenoticedtheadvisorshouldbeconsultedtohelpcorrectthedesign
errorsassoonaspossible.Alsoallthework,thatdependsonthefaultydesign,shouldbehalteduntiltheerror
iscorrected.
Impact:High
4.Illnessorabsenceofteammembers
Probability:High
Prevention:TeammembersshouldwarntheirteamleaderorthePMtimelybeforeaplannedperiodofabsence.
Correction:Byensuringthatknowledgeissharedbetweenteammembers,workcanbetakenoverquicklyby
someoneelseifapersongetsill.Whenworkneedstobetakenoverbysomeonearedivisionismadeofhis
othertaskssothattheworkloaddoesnotgettoohigh.Plannedabsenceisdealtwithintheplanning.
Impact:Medium
5.Servercrash
Probability:Low
Prevention:Allproductsarestoredintheprojectrepository,whichisbackedupregularlybytheCM.
Correction:Whenaproductgetslostfromitsworkingstoreitisrecoveredfromthemostrecentbackup.
Impact:Medium
3.3.2. Riskswithrespecttomanagement
240
245
6.Illnessorsuddenabsenceoftheprojectmanager
Probability:Low
Prevention:ThereareveryfewthingsinwhichthepresenceofthePMcannotbemissedforashortperiodof
time.NeverthelessthePMwillinformtheVPMofaplannedperiodofabsenceintimesothattheVPMcan
preparetotakeover.
Correction:BykeepingtheVPMuptodateontheprojectstatushewillhaveenoughknowledgetotakeoverin
caseofillnessorabsenceofthePM.
Impact:Low
3.3.3. Riskswithrespecttoresources
250
255
7.Unavailabilityofthetechnicaladvisorwhenneeded
Probability:Medium
Prevention:Meetingswiththetechnicaladvisorcanbeplannedinadvanceandtimehasbeenreservedinhis
scheduleforcounselingtheteam.
Correction:Adifferentappointmentismade,oranotherexpertisconsulted.
Impact:Medium
Monday,June12,2006
Page13of24
SoftwareProjectManagementPlanversion200
3.3.4. Riskswithrespecttothecustomer
260
265
270
8.Thecustomerchangeshismindabouttherequirements
Probability:High
Prevention:Itisobviouslyexplainedtothecustomer,thatafterhehasacceptedaversionoftheURD,theURD
cannotbechangedbythecustomerswishonly.
Correction:IfthecustomerchangeshismindduringtheURphasehisnewrequirementscanbeincorporatedin
theURD.Proceduresdescribedin[SQAP]detailhowtheURDmaybechangedafterapproval,andhowto
implementthesechanges.
Impact:Low
9.Thecustomerisnotavailablewhenneeded
Probability:Medium
Prevention:Meetingswiththecustomercanbeplannedwellinadvance.Thecustomerhasbeengivenroomin
hisscheduleforhisSoftwareEngineeringrelatedwork.
Correction:Whenthecustomerisnotavailable,meetingsmayhavetoberescheduled.
Impact:Medium
3.3.5. Summary
275
280
Itisobviousthatproblemswilloccurduringtheproject.Toavoidproblemsthefollowingrulesshouldbe
followedbyallteammembers:
TrytosignalproblemsasearlyaspossibleandreportthemtothePM,sothatactioncanbetaken;
Payattentiontocommunicationandmakesureeverybodyunderstandsthethingsthesameway;
Focusontheagreeduserrequirements,whichexpressthewishesofthecustomer;
Minimizefrictionbetweenpeoplebyhelpingandsupportingeachother;
Followguidelinesthatareposedin[SQAP]and[SCMP]toaidcoordinationandtoensureproduct
quality.
3.4. MonitoringandControllingMechanisms
285
290
295
300
ThemonitoringofprogressisdonebythePMusingthefollowingmeans:
WeeklyProjectGroupMeetings
Theprojectgroupmeetingstakeplaceintheprojectroom.ProjectgroupmeetingsusuallytakeplaceonMonday
at9:15inHG5.14,althoughthistimemaybesubjecttochange,emailswillbesendaboutthetimeifitchanges.
Thesemeetingsaremeanttoinformeachotheroftheprogressmadeonvarioustasks.Newtasksareassigned
bythePMonthesemeetings.Beforethemeeting,allmembersreadminutesofpreviousmeeting.ThePMtakes
careoftheagendaandpresidesthemeeting.
ProgressMeetings
Thesemeetingsarescheduledbiweeklyat12:20.OnthesemeetingsthePMandtheVPMorQAMmeetwiththe
SM.Beforeprogressmeetingsthefollowingthingsneedtobedone:
Writeaprogressreportaftertheexampleofthepreviousreports;
Readtheminutesofthepreviousmeeting;
DeliverthereporttotheSMhalfanhourbeforethestartofthefirstmeetingonthatday.
Monday,June12,2006
Page14of24
SoftwareProjectManagementPlanversion200
305
310
315
Projectmetrics
Everyweek,theworkdonebythemembers,needstobeadministrated.Eachteammemberhastofillintheir
hoursonawebbasedlog.ThislogneedstobefilledineveryMondaybefore12:00.AweekstartsatMondayand
endsatSunday.Everyentryinaloghastobelongtooneofthefollowingworkpackages:
SPMP,SVVP,UTP,ITP,STP,ATP,SCMP,SQAP,URD,SRD,Prototype,Research,ADD,DDD,Code,IT,ST,AT,
STD,Formalreviews,MeetingsorPresentations.
ThePMsendsanemailtotheSMeveryweek,containingthehoursspendonthedifferentworkpackagesand
thehoursspendonfollowingcategories:Nonprojectrelated,Generalprojectrelated,Documentation,
specification,design,Sourcecode,Testing,verification,consolidationandrework.Further,foreverywork
package,anestimationofremaininghoursisadded.
Teamleadermeetings
WheneverthePMorQAMfindsitnecessaryhecanarrangeateamleadermeeting.Teamleadermeetingsare
ratherinformalandinfrequentandthetasksrequiredforonedependonthepurposeofthemeeting.
3.5. StaffPlan
ThefollowingtablecontainscontactinformationaboutthemembersoftheSPINGRIDprojectgroup:
Name
Kleijkers,TMG
t.m.g.kleijkers@student.tue.nl 0644642081
PM
Bego,SCH
s.c.h.bego@student.tue.nl
0646445710
VQAM
Coset,RPJ
r.p.j.coset@student.tue.nl
0618194569
Leeuwestein,R
r.leeuwestein@student.tue.nl 0618044463
VPM
Leijten,MCG
m.c.g.leijten@student.tue.nl
0630509901
Linden,vd,I
i.v.d.linden@student.tue.nl
0647054703
QAM
Mens,JCJ
j.c.j.mens@student.tue.nl
0633746597
VCM
Moreaux,ML
m.l.moreaux@student.tue.nl 0615341191
CM
Muller,TJC
t.j.c.muller@student.tue.nl
ManagerExternalContacts
Monday,June12,2006
Phone
0624538894
Function
Page15of24
SoftwareProjectManagementPlanversion200
4. TechnicalProcess
320
4.1. Methods,ToolsandTechniques
Themethods,toolsandtechniquesusedduringthecourseoftheprojectarelistedinthe[SCMP].
4.2. SoftwareDocumentation
325
330
Duringtheproject,documentsshouldconformtoanumberofaspects:
Documentsmustbeofgoodquality.
Thestandardsalldocumentsarerequiredtomeetaredocumentedinthe[SCMP]withrespecttostyleandin
[SQAP]withrespecttocontent.
Documentsmustbereviewed.
Themannerinwhichdocumentreviewsareperformedisdescribedinthe[SVVP].
Thepurposeofdocumentreviewsistogetdocsofhighquality.
Therequirementswhichapplytotheapprovalofdocumentsaregiveninthe[SVVP].
4.3. ProjectSupportFunctions
335
340
345
350
BesidesProjectManagement,threeothermanagementfunctionsarepresent.Belowashortdescriptionofeach
ofthemisgiven.
ConfigurationManagement
Thepurposeofsoftwareconfigurationmanagementistoplan,organize,controlandcoordinatetheidentification,storage
andchangeofsoftwarethroughdevelopmentandtransfer.([ESAPSS0508,Section2.1]).TheCMwritestheSCMPin
whichplansareoutlinedforperformingthesetasks.
VerificationandValidation
SoftwareVerificationandValidationactivitiescheckthesoftwareagainstitsspecifications.([ESAPSS0509,Section
2.1]).TheQAteamwritestheSVVP.Inthisdocumenttheverificationandvalidationactivitiesaredescribed.
QualityAssurance
ESAPSS050definesSoftwareQualityAssurance(SQA)asaplannedandsystematicpatternofallactionsnecessaryto
provideadequateconfidencethattheitemorproductconfirmstoestablishedtechnicalrequirements.([ESAPSS0510,
Section2.1]).TheQAMoutlinesplansandproceduresneededforperformingthistaskintheSQAP.
Monday,June12,2006
Page16of24
SoftwareProjectManagementPlanversion200
5. Workpackages,Schedule,Budget
5.1. Workpackages
355
TheworkpackagesareprescribedbytheSM.Allworkpackageswiththeirmanagersandestimatedtimeare
listedbelow:
WorkPackageManager
SPMP
Hoursestimated
PM
50
SVVP
QAM
20
UTP
30
ITP
QAM
30
STP
QAM
30
ATP
QAM
30
SCMP
CM
80
SQAP
QAM
30
URD
90
SRD
126
Prototype
130
Research
150
ADD
120
DDD
120
Code
520
SUM
60
IT,ST,AT
QAM
STD
Formalreviews
QAM
100
Meetings
PM
280
Presentations
120
40
60
5.2. Dependencies
360
365
FortheURandtheSRphase,adependencychartisnotnecessaryasdependenciesaretrivial.TheURDmustbe
moreorlessreadybeforeworkontheSRDcanstart.However,itisunavoidablethat,whileworkingonthe
SRD,newquestionsariseabouttheuserrequirements.SotheSRDdoesnotstrictlydependoftheURD.
LikewiseworkingontheADDcanleadtochangestotheSRDandsoon.
TheprototypemustnotbelaterthantheSRDsinceitispartofit.IntheADphasetherearefewdependencies
betweentasks.WithintheADphasenoworkpackagesaredependentoneachother.Whenthefirstresultsof
theADphasearethere,theDDphasecommences.Workpackagesdontdependoneachothersinceinterfaces
betweencomponentshavebeendefinedinpreviousphases.TheTRphaseisthelastphase.Obviously,itisnot
possibletotransfertheproductbeforeitisready.ThereforetheDDphasemustbecompletedbeforetheTR
phasestarts.
Monday,June12,2006
Page17of24
SoftwareProjectManagementPlanversion200
5.3. ResourceRequirements
370
Themostimportantresourcesduringtheprojectarehumanresources.Anoverviewofresourceutilization
duringthevariousprojectphasesisgiveninsection5.4.Otherresourcesneededincludedevelopmentstations,a
serverwheredocumentsandinformationcanbestored,aprinter,networkconnectivity,aworkingandmeeting
roomwithsufficienttablesandchairsandatelephone.Duringtheprojectsoftwareisrequired.Forexamplea
programminglanguageandatexteditorarenecessary.[SCMP]describesthesoftwarethatisusedduringthe
project.
5.4. BudgetandResourceAllocation
375
ForeachphaseasdescribedinthisSPMP,abudgethasbeenestimated.Inallofthebudgetestimatesthetime
spentbythePMandAdvisorisnottakenintoaccountandworkpackagesassignedtothePMarenotspecified
Phase
Estimate (man hours)
UR
SR
AD
DD
TR
Margin
300
350
420
996
150
368
Total
380
385
2464
Thisbudgetisextendedbytheavailabilityof:
Asufficientlyfurnishedworkroom;
AprintersuppliedbyTU/e;
Awhiteboard(pluswhiteboardmarkers);
8(relativelyslow)notebookcomputers;
AservertosupportCMtasks;
Twocomputersfordevelopmentpurposes(oneofwhichistheserver).
Furthermoreintheappendicesadetailedphasebudgetisgivenforeachphaseastheprojectmoveson.
5.5. Schedule
390
395
400
Thefollowingtabledepictsthewaymilestonesarecoupledtovariousprojectphasesandwhentheyare
scheduled:
Theteambudgetof8personsx308hours=2464hours;
ThePMbudgetof80hours;
TheprojectdeadlineofJune14th
ThefinalpresentationofJune12th
TheintermediatepresentationofFebruary13th
ThepeerevaluationdeadlineofApril3th
AholidayfromDecember26thtillJanuary6th
AholidayfromFebruary27thtillMarch3th
OtherdaystheTU/eisclosed(April14th,April17th,May5th,May25th,May26th,June5th).
Monday,June12,2006
Page18of24
SoftwareProjectManagementPlanversion200
Phase
Milestone
Description
Planneddate
UR
Managementdocumentsapproved
December23th
M1
URDapproved
January16th
SR
Prototypeapproved
February20th
M2
SRDapproved
February24th
AD
M3
ADDapproved
April10th
DDDapproved
April25th
DD
Codingcomplete
May16rd
TR
M4/M5
M6
Producthandovercomplete
June14rd
405
5.6. UnavailabilityOverview
Inthefollowingtablewelllistwhichofthegroupmemberswillbeunavailiableforsomeperoideoftime,
outsideexamweeksandholidays.
Name
Date
Function
Kleijkers,TMG
27February3March2006
PM
Bego,SCH
VQAM
Coset,RPJ
Leeuwestein,R
VPM
Leijten,MCG
Linden,vd,I
27January20063February2006
QAM
Mens,JCJ
VCM
Moreaux,ML
20December28December
CM
Muller,TJC
27January20063February2006
ManagerExterneContacten
Monday,June12,2006
Page19of24
SoftwareProjectManagementPlanversion200
AppendixA:URPhase
410
A.1OutputsURPhase
415
TheURphasecanbecalledtheproblemdefinitionphase.UserrequirementsaredocumentedintheURD,
givingthecustomersviewoftheproblem.ThemainoutputsoftheURphasearethe:
URD;
SPMP,SPMP/UR,SPMP/SR;
SCMP,SCMP/UR,SCMP/SR;
SQAP,SQAP/UR,SQAP/SR;
SVVP,SVVP/UR,SVVP/SR;
ATP.
420
A.2Teamsandworkpackages
Team
Members
Workpackages
ProjectManagement
TMGKleijkers(PM)
RLeeuwestein(VPM)
SPMP
QualityAssurance
Iv.d.Linden(QAM)
SCHBego(VQAM)
SQAP,SVVP,ATP
ConfigurationManagement
MLMoreaux(CM)
JCJMens(VCM)
SCMP
Userrequirements
URDTeam
URD
All
Meetings,research
Monday,June12,2006
Page20of24
SoftwareProjectManagementPlanversion200
AppendixB:SRPhase
425
IntheSRphasethemainfocusisonthedefinitionofthesoftwarerequirements.BesidestheURDthe
managementdocumentsaremodifiedfortheADphase.
B.1OutputsSRPhase
430
435
TheinputtotheSRphaseistheURDandtheESAsoftwareengineeringstandard.Thedeliverablesare:
SRD
Prototype
SPMP/AD
SCMP/AD
SQAP/AD
SVVP/AD
STP
B.2Teams,workpackagesandplanning
WorkPackages,tasks
SPMP
SPMP/AD
Projectmanagementmeetings
Progressmeetings
Projectmetrics
SCMP
SCMP/AD
Servermaintenance
SQAP
SQAP/AD
Internalreview(s)SRD
Externalreview(s)SRD
SVVP
SVVP/AD
STP
SRD
Firstdraftversion
Internallyapprovedversion
Externallyapprovedversion
Prototypefirstversion
Prototypeexternallyapprovedversion
Various
Presentation
Meetings
Research
440
Members(responsible)
Deadline
T.Kleijkers
T.Kleijkers
T.Kleijkers/I.v.d.Linden
T.Kleijkers
Februari 24
CMmembers
CMMembers
QAM/VQAM
QAM/VQAM
QAM/VQAM
QAM/VQAM
QAM/VQAM
SRDteam
SRDteam
SRDteam
SRDteam
SRDteam
February24
I.v.d.Linden,T.Muller
All
All
February13
February24
February24
February6
February13
February20
February13
February20
Monday,June12,2006
Page21of24
SoftwareProjectManagementPlanversion200
AppendixC:ADPhase
IntheADphasethemainfocusisonthedefinitionofthecomponentsoftheproductandtheinteraction
betweenthosecomponents.BesidestheADDthemanagementdocumentsaremodifiedfortheDDphase.
445
C.1OutputsADPhase
450
TheinputtotheADphaseistheSRDandtheESAsoftwareengineeringstandard.Thedeliverablesare:
ADD
ITP(specifictestsarenotformulateduntiltheDDphase)
SPMP/DD
SCMP/DD
SQAP/DD
SVVP/DD
455
C.2Planningfortherestoftheproject
WorkPackages,
tasks
DDAppendices
ADD
DDD
STP
UTP
ITP
ATP
STD
SUM
Monday,June12,2006
Remarks
Members
Deadline
Forthelargestpartcomparable
totheADD,butfeatures:
Standardsand
conventions
Buildprocedure
Sourcecodelistings
TestthesystemagainsttheSRD
Testthesystemagainstthe
unitsoftheADD
Testthesystemintegrationas
alsodescribedinagainstthe
DDDworks
TestagainstURDfinaltest
Thisdocumentdescribeshowto
installthesystem
Softwareusermanual
Membersoftherespectiveplans
M.Leijten,R.Leeuwenstein,S.Bego
All.
April10
April10
R.Leeuwenstein,S.Bego
M.Leijten,R.Leeuwenstein
Week18
Week18
J.Mens,R.Leeuwestein
Week18
J.Mens,R.Leeuwestein
R.Leeuwenstein,S.Bego
Week18
Week18
R.Leeuwenstein,M.Leijten,S.Bego
Week19
Page22of24
SoftwareProjectManagementPlanversion200
AppendixD:DDPhase
460
IntheDDphasethecomponentsoftheADphasearedesignedinfulldetail.Whenthedesigniscompletely
finished,thecomponentwillbeimplemented.Afterthis,theunittestisdone.Obviouslythedesigntakesmost
ofthetime.Ifadesignisofhighquality,thecodingandtestingcanbedonefast.
Duringthisphase,theplansofthetransferphasewillbeinsertedintothemanagementdocuments.
D.1OutputsDDPhase
465
470
TheinputtotheDDphaseistheADDandtheESAsoftwareengineeringstandard.
Thedeliverablesare:
DDD
SUM
Aworkingversionofthesoftware
SPMP/TR
UTP
Testreportsofunitandintegrationtestingprocedures
D.2Teams,workpackagesandplanning
475
WorkPackages,tasks
SPMP
SPMP/TR
Projectmanagementmeetings
Progressmeetings
Projectmetrics
SCMP
Backup
Servermaintenance
SQAP
Internalreview(s)DDD
Externalreview(s)DDD
Internalreview(s)SUM
Externalreview(s)SUM
SVVP
Documentchecking
DDD
Firstdraftversion
Internallyapprovedversion
Externallyapprovedversion
Detaileddesign
Designing/documenting
Coding
Testing
Sum
Firstdraftversion
Monday,June12,2006
Members
T.Kleijkers
T.Kleijkers
T.Kleijkers
T.Kleijkers
CM
CM
QAM
QAM
QAM
QAM
QAM
All
All
All
All
All
All
R.Leeuwestein,S.Bego
Deadline
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week24
Week21
Week22
Week24
Week21
Page23of24
SoftwareProjectManagementPlanversion200
Externallyapprovedversion
Various
Meetings
Research
Monday,June12,2006
R.Leeuwestein,S.Bego
All
All
Week24
Page24of24