软件工程选择题题库.docx
《软件工程选择题题库.docx》由会员分享,可在线阅读,更多相关《软件工程选择题题库.docx(19页珍藏版)》请在冰点文库上搜索。
软件工程选择题题库
1、Softwareisasetofitemsorobjectsthatforma“configuration”thatincludes(D)
D.alloftheabove
2、Thenatureofsoftwareapplicationscanbecharacterizedbytheirinformation(D)
A.complexity
B.content
~
C.determinacy
D.choices"b"and"c"
3、Whichoftheitemslistedbelowisnotoneofthesoftwareengineeringlayers(b)
a.Process
b.Manufacturing
c.Methods
d.Tools
4、Whatarethethreegenericphasesofsoftwareengineering(a)
·
a.definition,development,support
b.what,how,where
c.programming,debugging,maintenance
d.analysis,design,testing
5、WhichofthesetermsisalevelnameintheCapabilityMaturityModel(b)
a.Adhoc
b.Repeatable
c.Reusable
&
d.Organized
CMM。
它是对于软件组织在定义、实施、度量、控制和改善其软件过程的实践中各个发展阶段的描述。
CMM的核心是把软件开发视为一个过程,并根据这一原则对软件开发和维护进行过程监控和研究,以使其更加科学化、标准化、使企业能够更好地实现商业目标。
CMM分为五个等级:
一级为初始级,二级为可重复级,三级为已定义级,四级为已管理级,五级为优化级。
6、Inwhichsoftwaredevelopmentproblemsolvingstagearetheresultsdelivered(d)
a.Statusquo
b.Problemdefinition
c.Technicaldevelopment
d.Solutionintegration
7、Thelinearsequentialmodelofsoftwaredevelopmentis(a)
&
a.Areasonableapproachwhenrequirementsarewelldefined.
b.Agoodapproachwhenaworkingprogramisrequiredquickly.
c.Thebestapproachtouseforprojectswithlargedevelopmentteams.
d.Anoldfashionedmodelthatisrarelyusedanymore.
8、Thelinearsequentialmodelofsoftwaredevelopmentisalsoknownasthe(a)
a.Classicallifecyclemodel
b.Fountainmodel
c.Spiralmodel
—
d.Chaosmodel
9、Theprototypingmodelofsoftwaredevelopmentis(b)
a.Areasonableapproachwhenrequirementsarewelldefined.
b.Ausefulapproachwhenacustomercannotdefinerequirementsclearly.
c.Thebestapproachtouseforprojectswithlargedevelopmentteams.
d.Ariskymodelthatrarelyproducesameaningfulproduct.
10、Therapidapplicationdevelopmentmodelis(c)
a.Anothernameforcomponent-baseddevelopment.
;
b.Ausefulapproachwhenacustomercannotdefinerequirementsclearly.
c.Ahighspeedadaptationofthelinearsequentialmodel.
d.Alloftheabove.
11、Evolutionarysoftwareprocessmodels(d)
a.Areiterativeinnature
b.Caneasilyaccommodateproductrequirementschanges
c.Donotgenerallyproducethrowawaysystems
d.Alloftheabove
|
12、Theincrementalmodelofsoftwaredevelopmentis(b)
a.Areasonableapproachwhenrequirementsarewelldefined.
b.Agoodapproachwhenaworkingcoreproductisrequiredquickly.
c.Thebestapproachtouseforprojectswithlargedevelopmentteams.
d.Arevolutionarymodelthatisnotusedforcommercialproducts.
13、Thespiralmodelofsoftwaredevelopment(c)
a.Endswiththedeliveryofthesoftwareproduct
b.Ismorechaoticthantheincrementalmodel
{
c.Includesprojectrisksevaluationduringeachiteration
d.Alloftheabove
14、Thecomponent-baseddevelopmentmodelis(c)
a.Onlyappropriateforcomputerhardwaredesign.
b.Notabletosupportthedevelopmentofreusablecomponents.
c.Dependentonobjecttechnologiesforsupport.
d.Notcosteffectivebyknownquantifiablesoftwaremetrics.
15、Effectivesoftwareprojectmanagementfocuseson(c)
·
a.people,performance,payoff,product
b.people,product,performance,process
c.people,product,process,project
d.people,process,payoff,product
16、Thefirststepinprojectplanningisto(d)
a.determinethebudget.
b.selectateamorganizationalmodel.
c.determinetheprojectconstraints.
@
d.establishtheobjectivesandscope.
17、Whichfactoristheleastimportantwhenchoosingtheorganizationalstructureforasoftwareteam(d)
a.degreeofcommunicationdesired
b.predictedsizeoftheresultingprogram
c.rigidityofthedeliverydate
d.sizeoftheprojectbudget
18、Oneofthebestwaystoavoidfrustrationduringthesoftwaredevelopmentprocessisto(a)
a.giveteammembersmorecontroloverprocessandtechnicaldecisions.
·
b.giveteammemberslesscontroloverprocessandtechnicaldecisions.
c.hidebadnewsfromtheprojectteammembersuntilthingsimprove.
d.rewardprogrammersbasedontheirproductivity.
19、Whichofthesesoftwarecharacteristicsisnotafactorcontributingtoprojectcoordinationdifficulties(b)
a.interoperability
b.performance
c.scale
d.uncertainty
)
20、Whichofthesesoftwarecharacteristicsareusedtodeterminethescopeofasoftwareproject(c)
a.context,linesofcode,function
b.context,function,communicationrequirements
c.informationobjectives,function,performance
d.communicationsrequirements,performance,informationobjectives
21、Whatactivitydoesasoftwareprojectmanagerneedtoperformtominimizetheriskofsoftwarefailure(d)
a.doubletheprojectteamsize
b.requestalargebudget
\
c.allowabsolutelynoscheduleslippage
d.definemilestonesandtrackprogress
22、Whichoftheseisnotavalidreasonformeasuringsoftwareprocesses,products,andresources(c)
a.tocharacterizethem
b.toevaluatethem
c.topricethem
d.toimprovethem
23、Processindicatorsenableasoftwareprojectmanagerto(d)
、
a.assessthestatusofanon-goingproject
b.trackpotentialrisks
c.adjustworkflowortasks
d.alloftheabove
24、Whichofthefollowingitemsarenotmeasuredbysoftwareprojectmetrics(b)
a.inputs
b.markets
c.outputs
【
d.results
25、Whichofthefollowingsoftwarequalityfactorsismostlikelytoaffectedbyradicalchangestocomputingarchitectures(d)
a.operation
b.transition
c.revision
d.noneoftheabove
26、Whichofthefollowingprovideusefulmeasuresofsoftwarequality(d)
a.correctness,performance,integrity,usability
@
b.reliability,maintainability,integrity,sales
c.correctness,maintainability,size,satisfaction
d.correctness,maintainability,integrity,usability
27、Tobeaneffectiveaidinprocessimprovementthebaselinedatausedmustbe:
(b)
a.basedonreasonableguesstimatesfrompastprojects
b.measuredconsistentlyacrosssimilarprojects
c.collectedoverthepast6months
d.basedonallpreviouslycompletedprojects
-
28、Thesoftwareengineeringenvironment(SEE)consistsofwhichofthefollowing(c)
a.customersandusers
b.developersandmanagers
c.hardwareplatformsandsoftwaretools
d.noneoftheabove
29、LOC-basedestimationtechniquesrequireproblemdecompositionbasedon(c)
a.informationdomainvalues
b.projectschedule
:
c.softwarefunctions
d.processactivities
30、FP-basedestimationtechniquesrequireproblemdecompositionbasedon(a)
a.informationdomainvalues
b.projectschedule
c.softwarefunctions
d.processactivities
31、Process-basedestimationtechniquesrequireproblemdecompositionbasedon(c)
~
a.informationdomainvaluesanddataobjects
b.projectscheduleandmilestones
c.softwarefunctionsandprocessactivities
d.noneoftheabove
32、Softwareriskalwaysinvolvestwocharacteristics(c)
a.firefightingandcrisismanagement
b.knownandunknownrisks
c.uncertaintyandloss
`
d.staffingandbudget
33、Threecategoriesofrisksare(b)
a.businessrisks,personnelrisks,budgetrisks
b.projectrisks,technicalrisks,businessrisks
c.planningrisks,technicalrisks,personnelrisks
d.managementrisks,technicalrisks,designrisks
34、Riskprojectionattemptstorateeachriskintwoways(c)
a.likelihoodandcost
、
b.likelihoodandimpact
c.likelihoodandconsequences
d.likelihoodandexposure
35、Risktablesaresortedby(b)
a.probabilityandcost
b.probabilityandimpact
c.probabilityandconsequences
d.probabilityandexposure
]
36、Aneffectiveriskmanagementplanwillneedtoaddresswhichofthefollowingissues(d)
a.riskavoidance
b.riskmonitoring
c.contingencyplanning
d.alloftheabove
37、Whichofthefollowingisnotoneoftheguidingprinciplesofsoftwareprojectscheduling(b)
a.compartmentalization
b.marketassessment
*
c.timeallocation
d.effortvalidation
38、Atasksetisacollectionof(a)
a.engineeringworktasks,milestones,deliverables
b.taskassignments,costestimates,metrics
c.milestones,deliverables,metrics
d.responsibilities,milestones,documents
39、Adaptationcriteriaareusedtodeterminethe(d)
a.costsofproductmaintenance
b.adjustmentstotheprojectschedule
c.bestprojecttypeclassificationforasoftwareprocess
d.recommendeddegreeofrigorforsoftwareprocess
40、Forpurposesofdeterminingthemajorengineeringtasksanddistributingthemontheprojecttimeline,theprojectmanagershouldassumethattheprocessmodelusedis(d)
a.linearsequential
b.iterative
c.evolutionary
)
d.anyoftheabove
41、Thepurposeofearnedvalueanalysisisto(b)
a.determinehowtocompensatedevelopersbasedontheirproductivity
b.provideaquantitativemeansofassessingsoftwareprojectprogress
c.provideaqualitativemeansofassessingsoftwareprojectprogress
d.setthepricepointforasoftwareproductbasedondevelopmenteffort
42、Akeyconceptofqualitycontrolisthatallworkproducts(c)
a.aredeliveredontimeandunderbudget
|
b.havecompletedocumentation
c.havemeasurablespecificationsforprocessoutputs
d.arethoroughlytestedbeforedeliverytothecustomer
43、Softwarereliabilityproblemscanalmostalwaysbetracedto(b)
a.errorsinrequirementsgathering
b.errorsindesignandimplementation
c.humanerror
d.errorsinoperation
—
44、Whichofthesearevali