英語(yǔ)版-軟件工程復(fù)習(xí)題

英語(yǔ)版——軟件工程復(fù)習(xí)題英語(yǔ)版——軟件工程復(fù)習(xí)題英語(yǔ)版——軟件工程復(fù)習(xí)題英語(yǔ)版——軟件工程復(fù)習(xí)題編制僅供參考審核批準(zhǔn)生效日期地址：電話：傳真:郵編:natureofsoftwareapplicationscanbecharacterizedbytheirinformation()plexityb.contentc.determinacyd.choices"b"and"c"2.Modernsoftwareapplicationsaresocomplexthatitishardtodevelopmutuallyexclusivecategorynames.()a.Trueb.False3.Softwaredeveloperssucceedmoreoftenthantheyfail,butsoftwarefailuresreceivemorepresscoverage.()a.Trueb.False4.Addingmorepeopletoaprojectthatisalreadybehindscheduleisagoodwaytocatchup.()a.Trueb.False5.ModernCASEtoolsaremoreimportantthanthenewesthardwareforachievinggoodsoftwarequalityandproductivity.()a.Trueb.False6.Changecannotbeeasilyaccommodatedinmostsoftwaresystems,unlessasystemwasdesignedwithchangeinmind.()a.Trueb.False7.Ageneralstatementofobjectivesisallthatisneededtobegindevelopingapieceofsoftware.()a.Trueb.False8.Theformaltechnicalreviewisaninadequatesubstitutefortestingregardlessofnatureofthesoftwaredefect.()a.Trueb.False9.Whatdopeoplemeanbytheexpression"softwarecrisis"Answer:Thisexpressionisintendedtodescribethechronicproblemsassociatedwithsoftwarefailures,howsoftwareisdeveloped,howthegrowingvolumeofsoftwareissupported,andthedifficultiesinmeetingthegrowingdemandformoresoftware.10.Explainwhatiswrongwiththenotionthatsoftwareengineeringistootimeconsumingandinterfereswithaprogrammer'sproductivity.Answer:Producingalotofcodequicklyisnottheobjectofsoftwaredevelopment.Thesoftwareneedstoperformcorrectlyoritwillneedtoberewritten.Mostsoftwareproductsmustbemaintainedformanyyearsaftertheyaredeveloped,thetimespentdocumentingaprogramandplanningforchangesiseasilyjustifiedovertheproduct'slifetime.Studieshaveshownthelaterachangeisintroducedinthedevelopmentprocess,themorecostlyitistoimplement.11.Whichoftheitemslistedbelowisnotoneofthesoftwareengineeringlayers()a.Processb.Manufacturingc.Methodsd.Tools12.Whatarethethreegenericphasesofsoftwareengineering()a.definition,development,supportb.what,how,gramming,debugging,maintenanced.analysis,design,testing13.WhichofthesetermsisalevelnameintheCapabilityMaturityModel()a.Adhocb.Repeatablec.Reusabled.OrganizedCMM。它是對(duì)于軟件組織在定義、實(shí)施、度量、控制和改善其軟件過(guò)程的實(shí)踐中各個(gè)發(fā)展階段的描述。CMM的核心是把軟件開(kāi)發(fā)視為一個(gè)過(guò)程，并根據(jù)這一原則對(duì)軟件開(kāi)發(fā)和維護(hù)進(jìn)行過(guò)程監(jiān)控和研究，以使其更加科學(xué)化、標(biāo)準(zhǔn)化、使企業(yè)能夠更好地實(shí)現(xiàn)商業(yè)目標(biāo)。CMM分為五個(gè)等級(jí)：一級(jí)為初始級(jí)，二級(jí)為可重復(fù)級(jí)，三級(jí)為已定義級(jí)，四級(jí)為已管理級(jí)，五級(jí)為優(yōu)化級(jí)。14.Whichoftheseitemsshouldbeusedtoselectasoftwareprocessframework()a.Peopleb.Productc.Projectd.Alloftheabove15.Inwhichsoftwaredevelopmentproblemsolvingstagearetheresultsdelivered()a.Statusquob.Problemdefinitionc.Technicaldevelopmentd.Solutionintegration16.Thelinearsequentialmodelofsoftwaredevelopmentis()a.Areasonableapproachwhenrequirementsarewelldefined.b.Agoodapproachwhenaworkingprogramisrequiredquickly.c.Thebestapproachtouseforprojectswithlargedevelopmentteams.d.Anoldfashionedmodelthatisrarelyusedanymore.17.Thelinearsequentialmodelofsoftwaredevelopmentisalsoknownasthe()a.Classicallifecyclemodelb.Fountainmodelc.Spiralmodeld.Chaosmodel18.Theprototypingmodelofsoftwaredevelopmentis()a.Areasonableapproachwhenrequirementsarewelldefined.b.Ausefulapproachwhenacustomercannotdefinerequirementsclearly.c.Thebestapproachtouseforprojectswithlargedevelopmentteams.d.Ariskymodelthatrarelyproducesameaningfulproduct.19.Therapidapplicationdevelopmentmodelis()a.Anothernameforcomponent-baseddevelopment.b.Ausefulapproachwhenacustomercannotdefinerequirementsclearly.c.Ahighspeedadaptationofthelinearsequentialmodel.d.Alloftheabove.20.Evolutionarysoftwareprocessmodels()a.Areiterativeinnatureb.Caneasilyaccommodateproductrequirementschangesc.Donotgenerallyproducethrowawaysystemsd.Alloftheabove21.Theincrementalmodelofsoftwaredevelopmentis()a.Areasonableapproachwhenrequirementsarewelldefined.b.Agoodapproachwhenaworkingcoreproductisrequiredquickly.c.Thebestapproachtouseforprojectswithlargedevelopmentteams.d.Arevolutionarymodelthatisnotusedforcommercialproducts.22.Thespiralmodelofsoftwaredevelopment()a.Endswiththedeliveryofthesoftwareproductb.Ismorechaoticthantheincrementalmodelc.Includesprojectrisksevaluationduringeachiterationd.Alloftheabove23.Theconcurrentdevelopmentmodelis()a.Anothernamefortherapidapplicationdevelopmentmodel.b.Oftenusedforthedevelopmentofclient/serverapplications.c.Onlyusedfordevelopmentofparallelordistributedsystems.d.Usedwheneveralargenumberofchangerequestsareanticipated.24.Thecomponent-baseddevelopmentmodelis()a.Onlyappropriateforcomputerhardwaredesign.b.Notabletosupportthedevelopmentofreusablecomponents.c.Dependentonobjecttechnologiesforsupport.d.Notcosteffectivebyknownquantifiablesoftwaremetrics.25.DescribethephasesoftheprototypingmodelforsoftwaredevelopmentAnswer:Requirementsaregatheredbyhavingthecustomeranddevelopermeetandidentifywhateverobjectivesandrequirementstheycan.Quickdesignfollows,focusingonrepresentationofthesoftwarethatwillbevisibletothecustomer.Aprototypeisconstructedbythedeveloperandevaluatedbythecustomerandusedtorefinetherequirements.Iterationoccursandtheprototypeistunedtosatisfythecustomer'sneeds.26.Describetheroleofriskanalysisinevolutionaryprocessmodelslikethespiralmodel.Answer:Aseachprototypeisenhancedbyiterationthroughtheprocesssteps,boththetechnicalandmanagementrisksareassessedtoseeifitisstillpossibletocompetetheprojectwhichitsrequiredfunctionalitywithacceptabletimeandcostconstraints.27.Effectivesoftwareprojectmanagementfocuseson()a.people,performance,payoff,productb.people,product,performance,processc.people,product,process,projectd.people,process,payoff,product28.Thefirststepinprojectplanningisto()a.determinethebudget.b.selectateamorganizationalmodel.c.determinetheprojectconstraints.d.establishtheobjectivesandscope.29.Processframeworkactivitiesarepopulatedwith(estonesb.workproductsc.QApointsd.Alloftheabove30.Whichfactoristheleastimportantwhenchoosingtheorganizationalstructureforasoftwareteam()a.degreeofcommunicationdesiredb.predictedsizeoftheresultingprogramc.rigidityofthedeliverydated.sizeoftheprojectbudget31.Oneofthebestwaystoavoidfrustrationduringthesoftwaredevelopmentprocessisto()a.giveteammembersmorecontroloverprocessandtechnicaldecisions.b.giveteammemberslesscontroloverprocessandtechnicaldecisions.c.hidebadnewsfromtheprojectteammembersuntilthingsimprove.d.rewardprogrammersbasedontheirproductivity.32.Weroperabilityb.performancec.scaled.uncertainty33.Whichofthesesoftwarecharacteristicsareusedtodeterminethescopeofasoftwareproject(a.context,linesofcode,functionb.context,function,rmationobjectives,function,municationsrequirements,performance,informationobjectives34.Whatactivitydoesasoftwareprojectmanagerneedtoperformtominimizetheriskofsoftwarefailurea.doubletheprojectteamsizeb.requestalargebudgetc.allowabsolutelynoscheduleslippaged.definemilestonesandtrackprogress35.Whichoftheseisnotavalidreasonformeasuringsoftwareprocesses,products,andresourcesa.tocharacterizethemb.toevaluatethemc.topricethemd.toimprovethem36.Processindicatorsenableasoftwareprojectmanagertoa.assessthestatusofanon-goingprojectb.trackpotentialrisksc.adjustworkflowortasksd.alloftheabove37.Whichofthefollowingitemsarenotmeasuredbysoftwareprojectmetricsa.inputsb.marketsc.outputsd.results38.Whichofthefollowingsoftwarequalityfactorsismostlikelytoaffectedbyradicalchangestocomputingarchitecturesa.operationb.transitionc.revisiond.noneoftheabove39.Whichofthefollowingprovideusefulmeasuresofsoftwarequalitya.correctness,performance,integrity,usabilityb.reliability,maintainability,integrity,salesc.correctness,maintainability,size,satisfactiond.correctness,maintainability,integrity,usability40.Tobeaneffectiveaidinprocessimprovementthebaselinedatausedmustbe:a.basedonreasonableguesstimatesfrompastprojectsb.measuredconsistentlyacrosssimilarprojectsc.collectedoverthepast6monthsd.basedonallpreviouslycompletedprojects41.Thesoftwareengineeringenvironment(SEE)consistsofwhichofthefollowinga.customersandusersb.developersandmanagersc.hardwareplatformsandsoftwaretoolsd.noneoftheabove42.LOC-cessactivities43.FP-cessactivities44.Pjectscheduleandmilestonesc.softwarefunctionsandprocessactivitiesd.noneoftheabove45.Softwareriskalwaysinvolvestwocharacteristicsa.firefightingandcrisismanagementb.knownandunknownrisksc.uncertaintyandlossd.staffingandbudget46.Threecategoriesofrisksarea.businessrisks,personnelrisks,jectrisks,technicalrisks,businessrisksc.planningrisks,technicalrisks,personnelrisksd.managementrisks,technicalrisks,designrisks47.Riskprojectionattemptstorateeachriskintwowaysa.likelihoodandcostb.likelihoodandimpactc.likelihoodandconsequencesd.likelihoodandexposure48.Rbabilityandexposure49.Aneffectiveriskmanagementplanwillneedtoaddresswhichofthefollowingissuesa.riskavoidanceb.riskmonitoringc.contingencyplanningd.alloftheabove50.Wpartmentalizationb.marketassessmentc.timeallocationd.effortvalidation51.Atasksetisacollectionofa.engineeringworktasks,milestones,deliverablesb.taskassignments,costestimates,estones,deliverables,metricsd.responsibilities,milestones,documents52.Adaptationcriteriaareusedtodeterminethea.costsofproductmaintenanceb.adjustmentstotheprojectschedulec.bestprojecttypeclassificationforasoftwareprocessd.recommendeddegreeofrigorforsoftwareprocess53.Forpurposesofdeterminingthemajorengineeringtasksanddistributingthemontheprojecttimeline,theprojectmanagershouldassumethattheprocessmodelusedisa.linearsequentialb.iterativec.evolutionaryd.anyoftheabove54.Tvideaqualitativemeansofassessingsoftwareprojectprogressd.setthepricepointforasoftwareproductbasedondevelopmenteffort55.List3principlesforschedulingsoftwareprojects.Answer:Compartmentalization,interdependency,timeallocation,effortvalidation,definedresponsibilities,definedoutcomes,definedmilestones56.Vductqualityattributesd.alloftheabove57.Akeyconceptofqualitycontrolisthatallworkproductsa.aredeliveredontimeandunderbudgetb.havecompletedocumentationfc.havemeasurablespeciicationsforprocessoutputsd.arethoroughlytestedbeforedeliverytothecustomer58.Statisticalqualityassuranceinvolvesa.usingsamplinginplaceofexhaustivetestingofsoftwareb.surveyingcustomerstofindouttheiropinionsaboutproductqualityc.tracingeachdefecttoitsunderlyingcause,isolatingthe"vitalfew"causes,andmovingtocorrectthemd.tracingeachdefecttoitsunderlyingcausesandusingtheParetoprincipletocorrecteachproblemfound59.Softwarereliabilityproblemscanalmostalwaysbetracedtoa.errorsinrequirementsgatheringb.errorsindesignandimplementationc.humanerrord.errorsinoperation60.WhatisaformaltechnicalreviewandwhyisoneconductedAnswer:ThepurposeofanFTRistohaveagroupofsoftwareengineersexamineadiscreteworkproductanddeterminewhetherornottheproductisfreeofdefectsusingthesoftwarespecificationsandstandardsasthereviewcriteria.61.Whichofthesearevalidsoftwareconfigurationitemsa.casetoolsb.documentationc.executableprogramsandtestdatad.alloftheabove62.Whichofthefollowingtasksisnotpartofsoftwareconfigurationmanagementa.changecontrolb.reportingc.statisticalqualitycontrold.versioncontrol63.Use-casesarescenariosthatdescribea.howsoftwareistobeusedinagivensituation.b.howCASEtoolswillbeusedtoconstructthesystem.c.thebuildplanforasoftwareproduct.d.thetestcasesforasoftwareproduct.64.Informationflowrepresentsthemannerinwhichdataandcontrola.arerelatedtooneanother.b.changeseachmovesthroughthesystem.c.willbeimplementedinthefinaldesign.d.noneoftheabove.65.Inthecontextofrequirementsanalysis,twotypesofproblempartitioningarea.bottom-upandtop-downb.horizontalandverticalc.subordinateandsuperordinated.noneoftheabove66.WhatarethefivephasesofsoftwarerequirementsanalysisAnswer:ProblemrecognitionEvaluationandsynthesisModelingSpecificationReview67.WhatmodelsarecreatedduringtheanalysisphaseofasoftwaredevelopmentprocessWhatisthepurposeofeachAnswer:Datamodel-showsrelationshipsamongsystemobjectsFunctionalmodel-describesthefunctionsenablingthetransformationsofsystemobjectsBehavioralmodel-showsmannerthatsoftwarerespondstoeventsinitiatedfromtheoutsideworld68.Whichofthefollowingisnotanobjectiveforbuildingananalysismodela.definesetofsoftwarerequirementsb.describecustomerrequirementsc.developanabbreviated簡(jiǎn)短的solutionfortheproblemd.establishbasisforsoftwaredesign69.Wjectscope70.Tplexityc.efficiencyd.quality71.Wcedurald.alloftheabove72.Wcessd.structural73.Wgramstructure74.Anarchitecturalstyleencompasseswhichofthefollowingelementsa.constraintsb.setofcomponentsc.semanticmodelsd.alloftheabove75.Thecriteriausedtoassessthequalityofanarchitecturaldesignshouldbebasedonsystema.accessibilityandreliabilityb.dataandcontrolc.functionalityd.implementationdetails76.Intransactionmappingthefirstlevelfactoringresultsinthea.creationofaCFDb.derivationofthecontrolhierarchyc.distributionofworkermodulesd.refinementofthemoduleview77.Acessingnarrativesforeachmoduled.testcasesforeachmodule78.Whichofthefollowinginterfacedesignprinciplesreducetheuser'smemoryloada.defineintuitiveshortcutsb.discloseinformationinaprogressivefashionc.establishmeaningfuldefaultsd.alloftheabove79.Interfaceconsistencyimpliesthata.inputmechanismsremainthesamethroughoutthe