软件开发外文翻译

1RequirementsPhaseThechancesofaproductbeingdevelopedontimeandwithinbudgetaresomewhatslimunlessthemembersofthesoftwaredevelopmentteamagreeonwhatthesoftwareproductwilldo.Thefirststepinachievingthisunanimityistoanalyzetheclient’scurrentsituationaspreciselyaspossible.Forexample,itisinadequatetosay,“Theyneedacomputer-aideddesignsystembecausetheyclaimtheirmanualdesignsystem,thereislousy.“Unlessthedevelopmentteamknowsexactlywhatiswrongwiththecurrentmanualsystem,thereisahighprobabilitythataspectsofthenewcomputerizedsystemwillbeequally“lousy.“Similarly,ifapersonalcomputermanufactureriscontemplatingdevelopmentofanewoperatingsystem,thefirststepistoevaluatethefirm’scurrentoperatingsystemandanalyzecarefullyexactlywhyitisunsatisfactory.Totakeanextremeexample,itisvitaltoknowwhethertheproblemexistsonlyinthemindofthesalesmanager,whoblamestheoperatingsystemforpoorsales,orwhetherusersoftheoperatingsystemarethoroughlydisenchantedwithitsfunctionalityandreliability.Onlyafteraclearpictureofthepresentsituationhasbeengainedcantheteamattempttoanswerthecriticalquestion,Whatmustthenewproductbeabletodo?Theprocessofansweringthisquestioniscarriedoutduringtherequirementsphase.Acommonlyheldmisconceptionisthat,duringtherequirementsphase,thedevelopersmustdeterminewhatsoftwaretheclientwants.Onthecontrary,therealobjectiveoftherequirementsphaseistodeterminewhatsoftwaretheclientneeds.Theproblemisthatmanyclientsdonotknowwhattheyneed.Furthermore,evenaclientwhohasagoodideaofwhatisneededmayhavedifficultyinaccuratelyconveyingtheseideastothedevelopers,becausemostclientsarelesscomputerliteratethanthemembersofthedevelopmentteam.Toelicittheclient’sneeds,themembersoftherequirementsteammustbefamiliarwiththeapplicationdomain,thatis,thegeneralareainwhichtheproposedsoftwareproductistobeused.Forexample,itisnoteasytoaskmeaningfulquestionsofabankeroranursewithoutfirstacquiringsomefamiliaritywithbankingornursing.Therefore,oneoftheinitialtasksofeachmemberoftherequirementsanalysisteamistoacquirefamiliaritywiththeapplicationdomainunlessheorshealreadyhasexperienceinthatgeneralarea.Itisparticularlyimportanttousecorrectterminologywhencommunicatingwiththeclientandpotentialusersofthetargetsoftware.Afterall,itishardtobetakenseriouslybyapersonworkinginaspecificdomainunlesstheinterviewerusesthenomenclatureappropriateforthatdomain.Moreimportant,useofaninappropriatewordmayleadtoamisunderstanding,eventuallyresultinginafaultyproductbeingdelivered.Thesameproblemcanariseifthemembersoftherequirementsteamdonotunderstandthesubtletiesoftheterminologyofthedomain.Onewaytosolvetheproblemwithterminologyistobuildaglossary.Theinitialentriesareinsertedwhiletheteamlearnstheapplicationdomain.Thentheglossaryisupdatedwheneverthemembersoftherequirementsteamencounternewterminology.Notonlydoessuchaglossaryreduceconfusionbetweenclientanddevelopers,italsoisusefulinlesseningmisunderstandingsbetweenmembersofthedevelopmentteam.Oncetherequirementsteamhaveacquiredfamiliaritywiththedomain,thenextstepisforthemtostarttodeterminetheclient’sneeds,thatis,requirementselicitation.Elicitationtechniqueasfollows:21.Interviews.Themembersoftherequirementsteammeetwithmembersoftheclientorganizationuntiltheyareconvincedthattheyhaveelicitedallrelevantinformationfromtheclientandfutureusersoftheproduct.Therearetwobasictypesofinterview,structuredandunstructured.Inastructuredinterview,specific,preplanned,close-endedquestionsareposed.Inanunstructuredinterview,open-endedquestionsareasked,toencouragethepersonbeinginterviewedtospeakout.Someofthesefactsmightnothavecometolighthadtheinterviewbeenmorestructured.Atthesametime,itisnotagoodideaiftheinterviewistoounstructured.Therefore,questionsshouldbeposedinsuchawayastoencouragethepersonbeinginterviewedtogivewide-ranginganswersbutwithinthecontextoftheinformationneededbytheinterviewer.Conductingagoodinterviewisnotalwayseasy.First,theinterviewermustbefamiliarwiththeapplicationdomain.Second,thereisnopointininterviewingamemberoftheclientorganizationiftheintervieweralreadyhasmadeuphisorhermindregardingtheclient’sneeds.Nomatterwhatheorshepreviouslyhasbeentoldorlearnedbyothermeans,theinterviewermustapproacheveryinterviewwiththeintentionoflisteningcarefullytowhatthepersonbeinginterviewedhastosaywhilefirmlysuppressinganypreconceivednotionsregardingtheclientcompanyortheneedsoftheclientsandpotentialusesofthesoftwareproducttobebuilt.2.Scenarios.Ascenarioisawayausermightutilizethetargetproducttoaccomplishsomeobjective.Ascenariocanbedepictedinanumberofways.Onetechniqueissimplytolisttheactionscomprisingthescenario.Anothertechniqueistosetupastoryboard,aseriesofdiagramsdepictingthesequenceofevents.Theycandemonstratethebehavioroftheproductinawaythatiscomprehensibletotheuser.Thiscanresultinadditionalrequirementscomingtolight,asintheweight-lossplannerexample.Becausescenarioscanbeunderstoodbyusers,theutilizationofscenarioscanensurethattheclientandusersplayanactiverolethroughouttherequirementsanalysisprocess.Afterall,theaimoftherequirementsanalysisphaseistoelicittherealneedsoftheclient,andtheonlysourceofth