英語版——軟件工程復習題英語版——軟件工程復習題英語版——軟件工程復習題v1.0可編寫可改正natureofsoftwareapplicationscanbecharacterizedbytheirinformation( )plexityb.contentc.determinacyd.choices"b"and"c"2.Modernsoftwareapplicationsaresocomplexthatitishardtodevelopmutuallyexclusivecategorynames.( )TrueFalseSoftwaredeveloperssucceedmoreoftenthantheyfail,butsoftwarefailuresreceivemorepresscoverage.( )TrueFalseAddingmorepeopletoaprojectthatisalreadybehindscheduleisagoodwaytocatchup.( )TrueFalse5.ModernCASEtoolsaremoreimportantthanthenewesthardwareforachievinggoodsoftwarequalityandproductivity.( )TrueFalseChangecannotbeeasilyaccommodatedinmostsoftwaresystems,unlessasystemwasdesignedwithchangeinmind.( )TrueFalseAgeneralstatementofobjectivesisallthatisneededtobegindevelopingapieceofsoftware.( )1v1.0可編寫可改正TrueFalseTheformaltechnicalreviewisaninadequatesubstitutefortestingregardlessofnatureofthesoftwaredefect.( )TrueFalseWhatdopeoplemeanbytheexpression"softwarecrisis"Answer:Thisexpressionisintendedtodescribethechronicproblemsassociatedwithsoftwarefailures,howsoftwareisdeveloped,howthegrowingvolumeofsoftwareissupported,andthedifficultiesinmeetingthegrowingdemandformoresoftware.Explainwhatiswrongwiththenotionthatsoftwareengineeringistootimeconsumingandinterfereswithaprogrammer'sproductivity.Answer:Producingalotofcodequicklyisnottheobjectofsoftwaredevelopment.Thesoftwareneedstoperformcorrectlyoritwillneedtoberewritten.Mostsoftwareproductsmustbemaintainedformanyyearsaftertheyaredeveloped,thetimespentdocumentingaprogramandplanningforchangesiseasilyjustifiedovertheproduct'slifetime.Studieshaveshownthelaterachangeisintroducedinthedevelopmentprocess,themorecostlyitistoimplement.11.Whichoftheitemslistedbelowisnotoneofthesoftwareengineeringlayers( )ProcessManufacturingMethodsToolsWhatarethethreegenericphasesofsoftwareengineering( )definition,development,supportwhat,how,whereprogramming,debugging,maintenance2v1.0可編寫可改正d.analysis,design,testingWhichofthesetermsisalevelnameintheCapabilityMaturityModel( )a.Adhocb.Repeatablec.Reusabled.OrganizedCMM。它是關于軟件組織在定義、實行、胸懷、控制和改良其軟件過程的實踐中各個發展階段的描繪。CMM的核心是把軟件開發視為一個過程，并依據這一原則對軟件開發和保護進行過程監控和研究，以使其更為科學化、標準化、使公司可以更好地實現商業目標。CMM分為五個等級：一級為初始級，二級為可重復級，三級為已定義級，四級為已管理級，五級為優化級。Whichoftheseitemsshouldbeusedtoselectasoftwareprocessframework( )a.Peopleb.Productc.Projectd.Alloftheabove15.Inwhichsoftwaredevelopmentproblemsolvingstagearetheresultsdelivered( )a.Statusquob.Problemdefinitionc.Technicaldevelopmentd.Solutionintegration16.Thelinearsequentialmodelofsoftwaredevelopmentis( )a.Areasonableapproachwhenrequirementsarewelldefined.b.Agoodapproachwhenaworkingprogramisrequiredquickly.c.Thebestapproachtouseforprojectswithlargedevelopmentteams.d.Anoldfashionedmodelthatisrarelyusedanymore.Thelinearsequentialmodelofsoftwaredevelopmentisalsoknownasthe( )v1.0可編寫可改正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.Evolutionarysoftwareprocessmodels( )a.Areiterativeinnatureb.Caneasilyaccommodateproductrequirementschangesc.Donotgenerallyproducethrowawaysystemsd.AlloftheaboveTheincrementalmodelofsoftwaredevelopmentis( )a.Areasonableapproachwhenrequirementsarewelldefined.b.Agoodapproachwhenaworkingcoreproductisrequiredquickly.c.Thebestapproachtouseforprojectswithlargedevelopmentteams.d.Arevolutionarymodelthatisnotusedforcommercialproducts.Thespiralmodelofsoftwaredevelopment( )a.Endswiththedeliveryofthesoftwareproductb.Ismorechaoticthantheincrementalmodel4v1.0可編寫可改正c.Includesprojectrisksevaluationduringeachiterationd.Alloftheabove23.Theconcurrentdevelopmentmodelis( )a.Anothernamefortherapidapplicationdevelopmentmodel.b.Oftenusedforthedevelopmentofclient/serverapplications.c.Onlyusedfordevelopmentofparallelordistributedsystems.d.Usedwheneveralargenumberofchangerequestsareanticipated.Thecomponent-baseddevelopmentmodelis( )a.Onlyappropriateforcomputerhardwaredesign.b.Notabletosupportthedevelopmentofreusablecomponents.c.Dependentonobjecttechnologiesforsupport.d.Notcosteffectivebyknownquantifiablesoftwaremetrics.DescribethephasesoftheprototypingmodelforsoftwaredevelopmentAnswer:Requirementsaregatheredbyhavingthecustomeranddevelopermeetandidentifywhateverobjectivesandrequirementstheycan.Quickdesignfollows,focusingonrepresentationofthesoftwarethatwillbevisibletothecustomer.Aprototypeisconstructedbythedeveloperandevaluatedbythecustomerandusedtorefinetherequirements.Iterationoccursandtheprototypeistunedtosatisfythecustomer'sneeds.26.Describetheroleofriskanalysisinevolutionaryprocessmodelslikethespiralmodel.Answer:Aseachprototypeisenhancedbyiterationthroughtheprocesssteps,boththetechnicalandmanagementrisksareassessedtoseeifitisstillpossibletocompetetheprojectwhichitsrequiredfunctionalitywithacceptabletimeandcostconstraints.Effectivesoftwareprojectmanagementfocuseson( )a.people,performance,payoff,product5v1.0可編寫可改正b.people,product,performance,processc.people,product,process,projectd.people,process,payoff,productThefirststepinprojectplanningisto( )a.determinethebudget.b.selectateamorganizationalmodel.c.determinetheprojectconstraints.d.establishtheobjectivesandscope.Processframeworkactivitiesarepopulatedwith(estonesb.workproductsc.QApointsd.Alloftheabove30.Whichfactoristheleastimportantwhenchoosingtheorganizationalstructureforasoftwareteam( )a.degreeofcommunicationdesiredb.predictedsizeoftheresultingprogramc.rigidityofthedeliverydated.sizeoftheprojectbudget31.Oneofthebestwaystoavoidfrustrationduringthesoftwaredevelopmentprocessisto( )a.giveteammembersmorecontroloverprocessandtechnicaldecisions.b.giveteammemberslesscontroloverprocessandtechnicaldecisions.c.hidebadnewsfromtheprojectteammembersuntilthingsimprove.d.rewardprogrammersbasedontheirproductivity.32.Whichofthesesoftwarecharacteristicsisnotafactorcontributingtoprojectcoordinationdifficulties6v1.0可編寫可改正interoperabilityperformancescaleuncertaintyWhichofthesesoftwarecharacteristicsareusedtodeterminethescopeofasoftwareproject(context,linesofcode,functioncontext,function,communicationrequirementsinformationobjectives,function,performancecommunicationsrequirements,performance,informationobjectivesWhatactivitydoesasoftwareprojectmanagerneedtoperformtominimizetheriskofsoftwarefailuredoubletheprojectteamsizerequestalargebudgetallowabsolutelynoscheduleslippagedefinemilestonesandtrackprogress35.Whichoftheseisnotavalidreasonformeasuringsoftwareprocesses,products,andresourcesa.tocharacterizethemb.toevaluatethemc.topricethemd.toimprovethemProcessindicatorsenableasoftwareprojectmanagertoa.assessthestatusofanon-goingprojectb.trackpotentialrisksc.adjustworkflowortasksd.alloftheabove7v1.0可編寫可改正Whichofthefollowingitemsarenotmeasuredbysoftwareprojectmetricsa.inputsb.marketsc.outputsd.resultsWhichofthefollowingsoftwarequalityfactorsismostlikelytoaffectedbyradicalchangestocomputingarchitecturesa.operationb.transitionc.revisiond.noneoftheaboveWhichofthefollowingprovideusefulmeasuresofsoftwarequalitya.correctness,performance,integrity,usabilityb.reliability,maintainability,integrity,salesc.correctness,maintainability,size,satisfactiond.correctness,maintainability,integrity,usabilityTobeaneffectiveaidinprocessimprovementthebaselinedatausedmustbe:a.basedonreasonableguesstimatesfrompastprojectsb.measuredconsistentlyacrosssimilarprojectsc.collectedoverthepast6monthsd.basedonallpreviouslycompletedprojectsThesoftwareengineeringenvironment(SEE)consistsofwhichofthefollowinga.customersandusersb.developersandmanagersc.hardwareplatformsandsoftwaretoolsd.noneoftheaboveLOC-basedestimationtechniquesrequireproblemdecompositionbasedon8v1.0可編寫可改正cessactivitiesFP-cessactivitiesPjectscheduleandmilestonesc.softwarefunctionsandprocessactivitiesd.noneoftheaboveSoftwareriskalwaysinvolvestwocharacteristicsa.firefightingandcrisismanagementb.knownandunknownrisksc.uncertaintyandlossd.staffingandbudget46.Threecategoriesofrisksarea.businessrisks,personnelrisks,jectrisks,technicalrisks,businessrisksc.planningrisks,technicalrisks,personnelrisksd.managementrisks,technicalrisks,designrisksRiskprojectionattemptstorateeachriskintwowaysa.likelihoodandcostb.likelihoodandimpact9v1.0可編寫可改正c.likelihoodandconsequencesd.likelihoodandexposureRbabilityandexposureAneffectiveriskmanagementplanwillneedtoaddresswhichofthefollowingissuesa.riskavoidanceb.riskmonitoringc.contingencyplanningd.alloftheabove50.Wpartmentalizationb.marketassessmentc.timeallocationd.effortvalidation51.Atasksetisacollectionof

projecta.engineeringworktasks,milestones,deliverablesb.taskassignments,costestimates,estones,deliverables,metricsd.responsibilities,milestones,documents52.Adaptationcriteriaareusedtodeterminethea.costsofproductmaintenanceb.adjustmentstotheprojectschedule10v1.0可編寫可改正c.bestprojecttypeclassificationforasoftwareprocessd.recommendeddegreeofrigorforsoftwareprocess53.Forpurposesofdeterminingthemajorengineeringtasksanddistributingthemontheprojecttimeline,theprojectmanagershouldassumethattheprocessmodelusedisa.linearsequentialiterativeevolutionaryanyoftheaboveThepurposeofearnedvalueanalysisistodeterminehowtocompensatedevelopersbasedontheirproductivityprovideaquantitativemeansofassessingsoftwareprojectprogressprovideaqualitativemeansofassessingsoftwareprojectprogresssetthepricepointforasoftwareproductbasedondevelopmenteffortList3principlesforschedulingsoftwareprojects.Answer:Compartmentalization,interdependency,timeallocation,definedresponsibilities,definedoutcomes,definedmilestones

effort

validation,Vductqualityattributesd.alloftheaboveAkeyconceptofqualitycontrolisthatallworkproductsa.aredeliveredontimeandunderbudgetb.havecompletedocumentationfc.havemeasurablespeciicationsforprocessoutputs11v1.0可編寫可改正d.arethoroughlytestedbeforedeliverytothecustomer58.Statisticalqualityassuranceinvolvesa.usingsamplinginplaceofexhaustivetestingofsoftwareb.surveyingcustomerstofindouttheiropinionsaboutproductqualityc.tracingeachdefecttoitsunderlyingcause,isolatingthe"vitalfew"causes,andmovingtocorrectthemd.tracingeachdefecttoitsunderlyingcausesandusingtheParetoprincipletocorrecteachproblemfoundSoftwarereliabilityproblemscanalmostalwaysbetracedtoa.errorsinrequirementsgatheringb.errorsindesignandimplementationc.humanerrord.errorsinoperationWhatisaformaltechnicalreviewandwhyisoneconductedAnswer:ThepurposeofanFTRistohaveagroupofsoftwareengineersexamineadiscreteworkproductanddeterminewhetherornottheproductisfreeofdefectsusingthesoftwarespecificationsandstandardsasthereviewcriteria.Whichofthesearevalidsoftwareconfigurationitemsa.casetoolsb.documentationc.executableprogramsandtestdatad.alloftheaboveWhichofthefollowingtasksisnotpartofsoftwareconfigurationmanagementa.changecontrolb.reportingc.statisticalqualitycontrold.versioncontrol12v1.0可編寫可改正63.Use-casesarescenariosthatdescribea.howsoftwareistobeusedinagivensituation.b.howCASEtoolswillbeusedtoconstructthesystem.c.thebuildplanforasoftwareproduct.d.thetestcasesforasoftwareproduct.64.Informationflowrepresentsthemannerinwhichdataandcontrola.arerelatedtooneanother.b.changeseachmovesthroughthesystem.c.willbeimplementedinthefinaldesign.d.noneoftheabove.65.Inthecontextofrequirementsanalysis,twotypesofproblempartitioninga.bottom-upandtop-downb.horizontalandverticalc.subordinateandsuperordinated.noneoftheabove

areWhatarethefivephasesofsoftwarerequirementsanalysisAnswer:ProblemrecognitionEvaluationandsynthesisModelingSpecificationReviewWhatmodelsarecreatedduringtheanalysisphaseofasoftwaredevelopmentprocessWhatisthepurposeofeachAnswer:Datamodel-showsrelationshipsamongsystemobjectsFunctionalmodel-describesthefunctionsenablingthetransformationsofsystemv1.0可編寫可改正objectsBehavioralmodel-showsmannerthatsoftwarerespondstoeventsoutsideworld68.Whichofthefollowingisnotanobjectiveforbuildingananalysismodela.definesetofsoftwarerequirementsb.describecustomerrequirements

initiated

fromthec.developanabbreviated簡潔的solutionfortheproblemd.establishbasisforsoftwaredesignWjectscopeTplexityc.efficiencyd.qualityWhattypesofabstractionareusedinsoftwaredesigncontroldataproceduralalloftheaboveWhichofthesemodeltypesdoesnotrepresentasoftwarearchitecturedatadynamicprocess14v1.0可編寫可改正d.structuralWgramstructureAnarchitecturalstyleencompasseswhichofthefollowingelementsa.constraintsb.setofcomponentsc.semanticmodelsd.alloftheaboveThecriteriausedtoassessthequalityofanarchitecturaldesignshouldbebasedonsystema.accessibilityandreliabilityb.dataandcontrolc.functionalityd.implementationdetailsIntransactionmappingthefirstlevelfactoringresultsinthea.creationofaCFDb.derivationofthecontrolhierarchyc.distributionofworkermodulesd.refinementofthemoduleviewAcessingnarrativesforeachmodulev1.0可編寫可改正d.testcasesforeachmodule78.Whichofthefollowinginterfacedesignprinciplesreducetheuser'sa.defineintuitiveshortcutsb.discloseinformationinaprogressivefashionc.establishmeaningfuldefaultsd.alloftheabove79.Interfaceconsistencyimpliesthata.inputmechanismsremainthesamethroughouttheapplicationb.eachapplicationshouldhaveitsowndistinctivelookandfeelc.navigationalmethodsarecontextsen