軟件工程專業(yè)英語-Unit 03 Planning the Project 項目策劃

Unit3PlanningtheProject項目策劃ContentsPart1ListeningandSpeakingDialogue:SoftwareProjectPlanningListeningComprehension:SoftwareProjectPlanningDictation:FourVariablesinProjectsPart2ReadingandTranslatingSectionA:SoftwareProjectPlanSectionB:AI-poweredProjectManagementintheNearFuturePart3SimulatedWriting:SoftwareProjectPlan1.1Dialogue:SoftwareProjectPlanningExercisesWorkinagroup,andmakeupasimilarconversationbyreplacingthestatementswithotherexpressionsontherightside.1.1Dialogue:SoftwareProjectPlanningWordsdeployment[di?pl?im?nt]n.

調(diào)度，部署debug[?di??b?ɡ]v.

調(diào)試indispensable[?indi?spens?bl]adj.不可缺少的，必需的configuration[k?n?fiɡ??rei?n]n.

配置note[n?ut]v.

記錄

1.1Dialogue:SoftwareProjectPlanningPhrasesarchitecturaldesign 體系結(jié)構(gòu)設(shè)計，概要設(shè)計detaileddesign

詳細(xì)設(shè)計accountfor

（在數(shù)量、比例方面）占Ganttchart

甘特圖referto提到1.2ListeningComprehension:SoftwareProjectPlanningListentothearticleandanswerthefollowing3questionsbasedonit.Afteryouhearaquestion,therewillbeabreakof15seconds.Duringthebreak,youwilldecidewhichoneisthebestansweramongthefourchoicesmarked(A),(B),(C)and(D).Questions1.Howmanykindsofplanningphilosophiesarementionedinthearticle?(A)Two(B)Three(C)Four(D)Five1.2ListeningComprehension:SoftwareProjectPlanningQuestions2.HowmanyquestionsarestatedinBoehm'sprincipleforleadingprojectplanning?(A)Three(B)Five(C)Six(D)Seven1.2ListeningComprehension:SoftwareProjectPlanningQuestions3.Whichpointofviewisthemostaccordantwiththeideaofthisarticleontheprojectplanning?(A)Planningeveryactivityintheprojectasdetailedaspossiblefortheirforeseeableability(B)Carryingoutasearlyaspossibleregardlessofplanning,becauseeventhebestplanningcanbeobviatedbyuncontrolledchangeastheworkproceeds(C)Adjustingdifferentlevelsofdetailsforactivitiesaccordingtotheirdifferentlocationsintheprojecttimeline(D)Makingaperfectplanwhichcanevadechangesthatmaycomeaboutduringthework1.2ListeningComprehension:

SoftwareProjectPlanningWordsphilosophy[f??l?s?fi]n.方法minimalist[?minim?list]n.

最低限要求者 argue[?ɑ?ɡju?]v.

主張，認(rèn)為，表明，論證obviate[??bvieit]v.

排除，避免traditionalist[tr??di??n?list]n.傳統(tǒng)主義者，墨守成規(guī)者 agilist[??d?ailist]n.

敏捷主義者，機敏者1.2ListeningComprehension:

SoftwareProjectPlanningWordsfruitless[?fru?tl?s]adj.徒勞的，無用的 recipe[?res?pi]n.

訣竅chaos[?kei?s]n.

混亂paper[?peip?(r)]n.

論文，文章state[steit]v.

陳述，說明milestone[?mailst?un]n.里程碑resultant[ri?z?lt?nt]adj.因此而產(chǎn)生的managerial[?m?n??d?i?ri?l]adj.管理的1.2ListeningComprehension:

SoftwareProjectPlanningPhrasesroadmap 線路圖，（一步一步的）詳盡計劃inmoderation

適中地scaledown按比例減少，按比例縮小AbbreviationsW5HH Why,What,When,Who,Where,How,Howmuch為什么，什么，什么時候，誰，在哪里，如何，有多少1.2ListeningComprehension:SoftwareProjectPlanning1.3Dictation:FourVariables

inProjectsThisarticlewillbeplayedthreetimes.Listencarefully,andfillinthenumberedspaceswiththeappropriatewordsyouhaveheard.1.3Dictation:FourVariables

inProjectsWordsfinite[?fainait]adj.有限的，限定的endeavor[in'dev?]n.努力，盡力 stress[stres]n.壓力，緊迫 suffer[?s?f?(r)]v.受損失，受害saying[?seii?]n.諺語，格言 embrace[im?breis]v.掌握，接受，擁抱 consciously[?k?n??sli]adv.有意識地 ultimately[??ltim?tli]adv.最后，終于，根本1.3Dictation:FourVariables

inProjectsPhraseseXtremeProgramming極限編程Notes[1]極限編程（eXtremeProgramming，簡稱XP）是一種軟件工程方法學(xué)，是敏捷軟件開發(fā)中可能是最富有成效的幾種方法學(xué)之一。如同其他敏捷方法學(xué)，極限編程和傳統(tǒng)方法學(xué)的本質(zhì)不同在于它更強調(diào)可適應(yīng)性能性以及面臨的困難，適用于小團隊開發(fā)。Wordsingredient[in?ɡri?di?nt]n.因素，成分staff[stɑ?f]v.

配置職員tailor[?teil?(r)]v.

剪裁，適應(yīng)suit[su?t;sju?t]v.

適合，合乎…的要求breakup['breik?p]n.

分解identify[ai?dentifai]v.

確認(rèn)，說明身份live [laiv]adj.

生動的2.1SectionA:SoftwareProjectPlanWordsitem[?ait?m]n.項prioritize [prai??r?taiz]v.

把...區(qū)分優(yōu)先次序mitigation[?miti?ɡei?n]n.緩解，減輕mechanism[?mek?niz?m]n.

機制defect[di?fekt;di'fekt]n.

缺陷course[k??s]n.過程，進程arise[??raiz]v.

出現(xiàn)，產(chǎn)生，上升2.1SectionA:SoftwareProjectPlanPhraseswithrespectto 就…而論，關(guān)于layout 劃定（路線），布置，安排inplace適當(dāng)，就位，（法律、政策、行政體系等）正在運作2.1SectionA:SoftwareProjectPlanAbbreviationsV&V

VerificationandValidation

驗證和確認(rèn)2.1SectionA:SoftwareProjectPlanNotes[1]Original:Thedetailedscheduleisoneinwhichthetasksarebrokenintosmaller,schedulabletasks,andthenassignedtospecificteammembers,whilepreservingtheoverallscheduleandeffortestimates.Translation:詳細(xì)進度是指，在保持總體進度和工作量估算的條件下，將任務(wù)分解為更小的、可安排的任務(wù)，然后將其分派給特定的團隊成員。2.1SectionA:SoftwareProjectPlanExercisesI.Readthefollowingstatementscarefully,anddecidewhethertheyaretrue(T)orfalse(F)accordingtothetext.1.Therearesevenimportantactivitiesintheprojectplanning.2.Generally,therearetwomainstepsinvolvedinprocessplanning,thatisselectingaproperprocessmodelandtailoringtheprojecttosuitthemodelchosen.3.Insoftwareengineering,theterm"activity"isinthelevelwithmoredetailsthantheterm"task"is.4.Boththeeffortestimateandthestaffinglevelinaprojectarethebasesoftheoverallscheduleandthemajormilestonesoftheproject.5.Statusreportsisoneofthemechanismsthatareoftenusedinprojectmonitoring.2.1SectionA:SoftwareProjectPlanII.Choosethebestanswertoeachofthefollowingquestionsaccordingtothetext.1.Whichstatementisrightabouttheprojectplanning?(A)Planningisanimportantingredientforasuccessfulproject,soitmustbedoneattheverybeginning,beforeanyotheractivitiesintheproject.(B)Projectplanningarrangesthepaththeprojectshouldfollowinordertoachievetheprojectobjectives.(C)Establishingagoodprojectplanisthemostessentialforimplementingtheplansuccessfully.(D)Becauseofthepotentialrisksbroughtbychanges,agoodprojectplanalwaysavoidschanges,sothatthingsalwaysworkasplanned.2.1SectionA:SoftwareProjectPlan2.Whatdoestheword"live"meansinthecontextof“Thedetailedscheduleisthemostlivedocumentofprojectplanning”inthethirdparagraph?(A)Involvingteammemberswhoarephysicallypresent,becausethetasksmustbeassignedtospecificteammembersinthedetailedschedule.(B)Guidable,becausethedetailedscheduleliststhetasksthathavetobedone,astheguidanceofthedailywork.(C)Operative,becausethedetailedschedulemustconsideranychangesintheprojectplansuitably.(D)Notspecific,becausethedetailedscheduledoesnothavetobemadeduetothepotentialfrequentchanges.2.1SectionA:SoftwareProjectPlan3.Whichstatementiswrongaboutthefollowingdifferentactivitiesintheprojectplan?(A)Modelsthatcanbeusedinprocessplanningandscheduleplanningaredifferent.(B)Configurationmanagementisusedtocontrolthechangesthatoccurduringtheproject.(C)Riskmitigationplansaremadeandperformedasthesubsequenceoftheriskmanagementplan.(D)Measurementisamostimportantmechanismformonitoringtheperformanceofaprojectwithrespecttoitsplan.2.1SectionA:SoftwareProjectPlanIV.TranslatethefollowingpassageintoChineseInaccuracyinEffortEstimationNaturally,theimportanceanddifficultyofprojectplanningandespeciallyeffortestimationvariesbyteams,companiesandprojects.ComparedtoAgileplanning,whereteamsusuallyonlyplanthenextshortsprint(andareevenabletousefeedbackfromprevioussprintsorreleases),planninganentireWaterfallSDLCprocesscanbeachallengingtask.2.1SectionA:SoftwareProjectPlanIV.TranslatethefollowingpassageintoChineseBiasfromprice-sensitiveclients,relyingonsubjectivejudgement(howeverexpertitmaybe)orestimatesfromasinglesourceasopposedtoseveralsources,andmainlythelackofhistoricaldataareallfactorsthatnegativelyimpactestimationaccuracy.Whilesomeoftheseriskscanbemitigatedbyorganizationalchangesandrevisedmanagementmethods,thelatteralsorequirestheuseofsuitabletools.Collectingandorganizinghistoricaldata,andanalyzingittoimprovetheaccuracyofestimatesforfutureprojectscanonlybeefficientlyperformedbyusingsoftwaretoolsthatsupporttheseprocesses.2.1SectionA:SoftwareProjectPlan

2.2SectionB:AI-poweredProjectManagementintheNearFutureWordsscript[?skript]n.腳本routine[ru??ti?n]adj.常規(guī)的，日常的log[l?ɡ]n.日志vulnerability[?v?ln?r?'bil?ti]n.弱點，脆弱性recur[ri?k??(r)]v.循環(huán)drastically[?dr?stikli;?drɑ?stikli]adv.徹底地delegate[?deliɡ?t,?deliɡeit]v.委托，授（權(quán)），把……委托給他人2.2SectionB:AI-poweredProjectManagementintheNearFutureWordstask[tɑ?sk]v.派給某人（任務(wù)）superior[su??pi?ri?(r);sju??p?ri?(r)]n.上級，高手augmented[??ɡ'mentid]adj.增強的insight[?insait]n.洞察力engagement[in?ɡeid?m?nt]n.參與度2.2SectionB:AI-poweredProject

ManagementintheNearFuturePhrasesjustabout幾乎，差不多figureout想出，理解，斷定inhaste急忙地，草率地，慌張地inflatedcost濫計成本，虛列成本dedicateto把（時間、精力等）用于keytakeaway關(guān)鍵點，關(guān)鍵信息，重要信息2.2SectionB:AI-poweredProjectManagementintheNearFutureExercisesI.Readthefollowingstatementscarefully,anddecidewhethertheyaretrue(T)orfalse(F)accordingtothetext.1.AI-drivensystemswilllikelyreplacemosthigher-levelrolesanddutiesaltogether.2.WithAIassistancethefunctionofhumanresourcewithinprojectmanagementwillbeimproved.3.Dataanalystswilldelegatesecond-lineanalysistaskstodeeplearningsystemsandfocusonlow-levelarchitecturedesignandsupport.4.Withmachinelearningprojectplanningcanbeoptimized.5.Moreprojectsfailthankstopredictiveanalytics.2.2SectionB:AI-poweredProjectManagementintheNearFutureII.Choosethebestanswertoeachofthefollowingquestionsaccordingtothetext.1.HowmanywayscanAIimproveprojectmanagementinthenearfuture?(A)Atleastoneway(B)Atleasttwoways(C)Atleastthreeways(D)Noneoftheabove2.Whichofthefollowingiswrongaboutmachinelearningregardingaproject?(A)Machinelearningallowscomputerstouseprojectdataandsophisticatedalgorithmsforpredictingoutcomesandidentifyingpossibilitiesofthreatsandvulnerabilitiesaffectingyourproject.(B)Machinelearningwillhelpreplacemosthigher-levelrolesanddutiesaltogether.(C)Projectplanningcanbeoptimizedwithmachinelearning.(D)Machinelearningcanreducetheprojectfailurerate.2.2SectionB:AI-poweredProjectManagementintheNearFuture3.Whichofthefollowingiswrongaccordingtothistext?(A)WithAIassistancethefunctionofhumanresourcewithinprojectmanagementwillbeimproved.(B)Lessprojectsfailthankstopredictiveanalytics.(C)Dataanalystswilldelegatesecond-lineanalysistaskstodeeplearningsystemsandfocusonlow-levelarchitecturedesignandsupport.(D)AI-drivensystemswilllikelyreplacemostlower-levelrolesanddutiesaltogether.2.2SectionB:AI-poweredProjectManagementintheNearFutureIV.TranslatethefollowingpassageintoChinese.ProjectManagerandAIAIwillassist,notreplace,projectmanagers.Aswitheverytechnology,AIalonewillnotguaranteesuccess.However,deployedpurposefully,AIcanbeadistinctiveacceleratorandgamechangerforprojectmanagersandthushelpincreaseprojectsuccessrates.Theprojectmanagerswhosucceedwilllikelybethosewhomanagetoseebeyondtheboundsof'human'imagination,andanswerquestionsabouthowthistechnologycanaddrealvalueanddrivepositivechangeinprojectmanagementandbusinesstransformations.Thiswillensurethestrategicvalueofprojectmanagement.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlanTocommunicateriskanalysisandmanagement,projectcostestimates,schedule,andorganizationtoourcustomers,weusuallywriteadocumentcalledaprojectplan.Theplanputsinwritingthecustomer'sneeds,aswellaswhatwehopetodotomeetthem.Thecustomercanrefertotheplanforinformationaboutactivitiesinthedevelopmentprocess,makingiteasytofollowtheproject'sprogressduringdevelopment.Wecanalsousetheplantoconfirmwiththecustomeranyassumptionswearemaking,especiallyaboutcostandschedule.SoftwareProjectPlanAgoodprojectplanincludesthefollowingitems:1.jectstandards,procedures,andproposedtechniquesandtools6.qualityassuranceplan7.configurationmanagementplan3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan8.documentationplan9.datamanagementplan10.resourcemanagementplan11.testplan12.trainingplan13.securityplan14.riskmanagementplan15.maintenanceplan3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlanThescopedefinesthesystemboundary,explainingwhatwillbeincludedinthesystemandwhatwillnotbeincluded.Itassuresthecustomerthatweunderstandwhatiswanted.Theschedulecanbeexpressedusingaworkbreakdownstructure,thedeliverables,andatimelinetoshowwhatwillbehappeningateachpointduringtheprojectlifecycle.AGanttchartcanbeusefulinillustratingtheparallelnatureofsomeofthedevelopmenttasks.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlanTheprojectplanalsoliststhepeopleonthedevelopmentteam,howtheyareorganized,andwhattheywillbedoing.Aswehaveseen,noteveryoneisneededallthetimeduringtheproject,sotheplanusuallycontainsaresourceallocationcharttoshowstaffinglevelsatdifferenttimes.Writingatechnicaldescriptionforcesustoanswerquestionsandaddressissuesasweanticipatehowdevelopmentwillproceed.Thisdescriptionlistshardwareandsoftware,includingcompilers,interfaces,andspecial-purposeequipmentorsoftware.Anyspecialrestrictionsoncabling,executiontime,responsetime,security,orotheraspectsoffunctionalityorperformancearedocumentedintheplan.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlanTemplateSoftwareProjectPlanfor<NameofProject><author><date>3.SimulatedWriting:SoftwareProjectPlan3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlanTableofContentsBuildthetableofcontentshere.Insertitwhenyoufinishyourdocument.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan1.Introduction

ThissectionoftheSoftwareProjectPlan(SPP)providesanoverviewoftheproject.

（1.1）ProjectOverviewIncludeaconcisesummaryoftheprojectobjectives,majorworkactivities,majormilestones,requiredresources,andbudget.Describetherelationshipofthisprojecttootherprojects,ifappropriate.

Provideareferencetotheofficialstatementofproductrequirements.（1.2）ProjectDeliverablesListtheprimarydeliverablesforthecustomer,thedeliverydates,deliverylocations,andquantitiesrequiredsatisfyingthetermsoftheprojectagreement.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan1.Introduction

（1.3）EvolutionoftheSPPDescribehowthisplanwillbecompleted,disseminated,andputunderchangecontrol.

Describehowbothscheduledandunscheduledupdateswillbehandled.（1.4）ReferenceMaterialsProvideacompletelistofalldocumentsandothersourcesofinformationreferencedintheplan.Includeforeachthetitle,reportnumber,date,author,andpublishingorganization.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan1.Introduction

（1.5）DefinitionsandAcronymsDefineorprovidereferencestothedefinitionofalltermsandacronymsrequiredtoproperlyinterprettheSPP.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan2.ProjectOrganization

Thissectionspecifiestheprocessmodelfortheprojectanditsorganizationalstructure.

（2.1）ProcessModelSpecifythelifecyclemodeltobeusedforthisprojectorrefertoanorganizationalstandardmodelthatwillbefollowed.Theprocessmodelmustincluderoles,activities,entrycriteriaandexitcriteriaforprojectinitiation,productdevelopment,productrelease,andprojecttermination.（2.2）OrganizationalStructureDescribetheinternalmanagementstructureoftheproject,aswellashowtheprojectrelatestotherestoftheorganization.Itisrecommendedthatchartsbeusedtoshowthelinesofauthority.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan2.ProjectOrganization

（2.3）OrganizationalInterfacesDescribetheadministrativeandmanagerialinterfacesbetweentheprojectandtheprimaryentitieswithwhichitinteracts.

Table3-1maybeausefulwaytorepresentthis.OrganizationLiaisonContactInformationCustomer:<name><name><phone,email,etc.>Subcontractor:<name>

SoftwareQualityAssurance

SoftwareConfigurationManagement

<etc.>

Table3-1OrganizationalInterfaces3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan2.ProjectOrganization（2.4）ProjectResponsibilitiesIdentifyandstatethenatureofeachmajorprojectfunctionandactivity,andidentifytheindividualswhoareresponsibleforthosefunctionsandactivities.

Table3-2maybeusedtodepictprojectresponsibilities.RoleDescriptionPersonProjectManagerLeadsprojectteam;responsibleforprojectdeliverables<name>TechnicalTeamLeader(s)

<defineaslocallyused><name><etc.><etc.>Table3-2ProjectResponsibilities3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

ThissectionoftheSPPspecifiesthemanagementprocessforthisproject.

（3.1）ManagementObjectivesandPrioritiesDescribethephilosophy,goals,andprioritiesformanagingthisproject.Aflexibilitymatrixmightbehelpfulincommunicatingwhatdimensionsoftheprojectarefixed,constrainedandflexible.

Eachdegreeofflexibilitycolumncancontainonlyone"X"(Table3-3).ProjectDimensionFixedConstrainedFlexibleCost

X

ScheduleX

Scope(functionality)

XTable3-3FlexibilityMatrix3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.2）Assumptions,Dependencies,andConstraintsStatetheassumptionsonwhichtheprojectisbased,anyexternaleventstheprojectisdependentupon,andtheconstraintsunderwhichtheprojectistobeconducted.

Includeanexplicitstatementoftherelativeprioritiesamongmeetingfunctionality,schedule,andbudgetforthisproject.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.3）RiskManagementDescribetheprocesstobeusedtoidentify,analyze,andmanagetheriskfactorsassociatedwiththeproject.

Describemechanismsfortrackingthevariousriskfactorsandimplementingcontingencyplans.

Riskfactorsthatshouldbeconsideredincludecontractualrisks,technologicalrisks,risksduetosizeandcomplexityoftheproduct,risksinpersonnelacquisitionandretention,andrisksinachievingcustomeracceptanceoftheproduct.Thespecificrisksforthisprojectandthemethodsformanagingthemmaybedocumentedhereorinanotherdocumentincludedasanappendixorbyreference.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.4）MonitoringandControllingMechanismsDefinethereportingmechanisms,reportformats,reviewandauditmechanisms,andothertoolsandtechniquestobeusedinmonitoringandcontrollingadherencetotheSPP.

Projectmonitoringshouldoccuratthelevelofworkpackages.Includemonitoringandcontrollingmechanismsfortheprojectsupportfunctions(qualityassurance,configurationmanagement,documentationandtraining).3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.4）MonitoringandControllingMechanismsAtablemaybeusedtoshowthereportingandcommunicationplanfortheproject.Thecommunicationtablecanshowtheregularreportsandcommunicationexpectedoftheproject,suchasweeklystatusreports,regularreviews,oras-neededcommunication.

Theexacttypesofcommunicationvarybetweengroups,butitisusefultoidentifytheplannedmeansatthestartoftheproject(Table3-4).3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.4）MonitoringandControllingMechanismsInformationCommunicatedFromToTimePeriodStatusReportProjectTeamProjectManagerWeeklyStatusReportProjectMangerSoftwareManager,ProjectTeamWeeklyProjectReviewProjectTeamSoftwareManagerMonthly<etc.>

Table3-4CommunicationandReportingPlan3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan3.ManagerialProcess

（3.5）StaffingApproachDescribethetypesofskillsrequiredfortheproject,howappropriatepersonnelwillberecruited,andanytrainingrequiredforprojectteammembers.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

Thissectionspecifiesthetechnicalmethods,tools,andtechniquestobeusedontheproject.

Italsoincludesidentificationoftheworkproductsandreviewstobeheldandtheplansforthesupportgroupactivitiesinuserdocumentation,training,softwarequalityassurance,andconfigurationmanagement.

（4.1）Methods,Tools,andTechniquesIdentifythecomputingsystem(s),developmentmethod(s),standards,policies,procedures,teamstructure(s),programminglanguage(s),andothernotations,tools,techniques,andmethodstobeusedtospecify,design,build,test,integrate,document,deliver,modifyormaintaintheprojectdeliverables.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

（4.2）SoftwareDocumentationSpecifytheworkproductstobebuiltforthisprojectandthetypesofpeerreviewstobeheldforthoseproducts.

Itmaybeusefultoincludeatablethatisadaptedfromtheorganization'sstandardcollectionofworkproductsandreviews.

Identifyanyrelevantstyleguide,namingconventionsanddocumentationformats.

Ineitherthisdocumentationplanortheprojectscheduleprovideasummaryofthescheduleandresourcerequirementsforthedocumentationeffort.Toensurethattheimplementationofthesoftwaresatisfiestherequirements,thefollowingdocumentationisrequiredasaminimum:3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

（4.2）SoftwareDocumentation4.2.1

SoftwareRequirementsSpecification(SRS)TheSRSclearlyandpreciselydescribeseachoftheessentialrequirements(functions,performances,designconstraints,andattributes)ofthesoftwareandtheexternalinterfaces.

Eachrequirementisdefinedsuchthatitsachievementiscapableofbeingobjectivelyverifiedandvalidatedbyaprescribedmethod,forexample,inspection,analysis,demonstration,ortest.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

（4.2）SoftwareDocumentation4.2.2

SoftwareDesignDescription(SDD)TheSDDdescribesthemajorcomponentsofthesoftwaredesignincludingdatabasesandinternalinterfaces.4.2.3

SoftwareTestPlanTheSoftwareTestPlandescribesthemethodstobeusedfortestingatalllevelsofdevelopmentandintegration:requirementsasexpressedintheSRS,designsasexpressedintheSDD,codeasexpressedintheimplementedproduct.

Thetestplanalsodescribesthetestprocedures,testcases,andtestresultsthatarecreatedduringtestingactivities.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

（4.3）UserDocumentationDescribehowtheuserdocumentationwillbeplannedanddeveloped.

(Thismaybejustareferencetoaplanbeingbuiltbysomeoneelse.)

Includeworkplannedforonlineaswellaspaperdocumentation,onlinehelp,networkaccessiblefilesandsupportfacilities.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan4.TechnicalProcess

（4.4）ProjectSupportFunctionsProvideeitherdirectlyorbyreference,plansforthesupportingfunctionsforthesoftwareproject.

Thesefunctionsmayinclude,butarenotlimitedto,configurationmanagement,softwarequalityassurance,andverificationandvalidation.

PlansforprojectsupportfunctionsaredevelopedtoalevelofdetailconsistentwiththeothersectionsoftheSPP.

Inparticular,theresponsibilities,resourcerequirements,schedulesandbudgetsforeachsupportingfunctionmustbespecified.

Thenatureandtypeofsupportfunctionsrequiredwillvaryfromprojecttoproject,however,theabsenceofasoftwarequalityassurance,configurationmanagement,or,verificationandvalidationplanmustbeexplicitlyjustifiedinprojectplansthatdonotincludethem.3.SimulatedWriting:SoftwareProjectPlanSoftwareProjectPlan5.WorkPackages,Schedule,andBudget

Specifytheworkpackages,dependencyrelationships,resourcerequirements,allocationofbudgetandresourcestoworkpackages,andaprojectschedule.

Muchofthecontentmaybeinappendicesthatarelivingdocuments,updatedas