软件工程选择题题库(共10页).doc

《软件工程选择题题库(共10页).doc》由会员分享，可在线阅读，更多相关《软件工程选择题题库(共10页).doc（10页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、精选优质文档-倾情为你奉上1、 Software is a set of items or objects that form a “configuration” that includes （D） D. all of the above2、The nature of software applications can be characterized by their information (D) A. complexity B. content C. determinacy D. choices b and c3、Which of the items listed below is no

2、t one of the software engineering layers(b) a. Process b. Manufacturing c. Methods d. Tools 4、What are the three generic phases of software engineering(a) a. definition, development, support b. what, how, where c. programming, debugging, maintenance d. analysis, design, testing5、Which of these terms

3、 is a level name in the Capability Maturity Model(b) a. Ad hoc b. Repeatable c. Reusable d. OrganizedCMM。它是对于软件组织在定义、实施、度量、控制和改善其软件过程的实践中各个发展阶段的描述。CMM的核心是把软件开发视为一个过程，并根据这一原则对软件开发和维护进行过程监控和研究，以使其更加科学化、标准化、使企业能够更好地实现商业目标。CMM分为五个等级：一级为初始级，二级为可重复级，三级为已定义级，四级为已管理级，五级为优化级。6、In which software development p

4、roblem solving stage are the results delivered(d) a. Status quo b. Problem definition c. Technical development d. Solution integration 7、The linear sequential model of software development is(a) a. A reasonable approach when requirements are well defined. b. A good approach when a working program is

5、 required quickly. c. The best approach to use for projects with large development teams. d. An old fashioned model that is rarely used any more. 8、The linear sequential model of software development is also known as the (a) a. Classical life cycle model b. Fountain model c. Spiral model d. Chaos mo

6、del 9、The prototyping model of software development is (b) a. A reasonable approach when requirements are well defined. b. A useful approach when a customer cannot define requirements clearly. c. The best approach to use for projects with large development teams. d. A risky model that rarely produce

7、s a meaningful product.10、The rapid application development model is (c) a. Another name for component-based development. b. A useful approach when a customer cannot define requirements clearly. c. A high speed adaptation of the linear sequential model. d. All of the above.11、Evolutionary software p

8、rocess models (d) a. Are iterative in nature b. Can easily accommodate product requirements changes c. Do not generally produce throw away systems d. All of the above 12、The incremental model of software development is (b) a. A reasonable approach when requirements are well defined. b. A good approa

9、ch when a working core product is required quickly. c. The best approach to use for projects with large development teams. d. A revolutionary model that is not used for commercial products.13、The spiral model of software development (c) a. Ends with the delivery of the software product b. Is more ch

10、aotic than the incremental model c. Includes project risks evaluation during each iteration d. All of the above14、The component-based development model is(c) a. Only appropriate for computer hardware design. b. Not able to support the development of reusable components. c. Dependent on object techno

11、logies for support. d. Not cost effective by known quantifiable software metrics.15、 Effective software project management focuses on(c) a. people, performance, payoff, product b. people, product, performance, process c. people, product, process, project d. people, process, payoff, product 16、The fi

12、rst step in project planning is to (d) a. determine the budget. b. select a team organizational model. c. determine the project constraints. d. establish the objectives and scope.17、Which factor is the least important when choosing the organizational structure for a software team (d) a. degree of co

13、mmunication desired b. predicted size of the resulting program c. rigidity of the delivery date d. size of the project budget 18、One of the best ways to avoid frustration during the software development process is to (a) a. give team members more control over process and technical decisions. b. give

14、 team members less control over process and technical decisions. c. hide bad news from the project team members until things improve. d. reward programmers based on their productivity. 19、Which of these software characteristics is not a factor contributing to project coordination difficulties (b) a.

15、 interoperability b. performance c. scale d. uncertainty 20、Which of these software characteristics are used to determine the scope of a software project (c) a. context,lines of code, function b. context, function, communication requirements c. information objectives, function, performance d. commun

16、ications requirements, performance, information objectives 21、What activity does a software project manager need to perform to minimize the risk of software failure (d) a. double the project team size b. request a large budget c. allow absolutely no schedule slippage d. define milestones and track p

17、rogress 22、Which of these is not a valid reason for measuring software processes, products, and resources (c) a. to characterize them b. to evaluate them c. to price them d. to improve them 23、Process indicators enable a software project manager to (d) a. assess the status of an on-going project b.

18、track potential risks c. adjust work flow or tasks d. all of the above 24、Which of the following items are not measured by software project metrics (b) a. inputs b. markets c. outputs d. results 25、Which of the following software quality factors is most likely to affected by radical changes to compu

19、ting architectures (d) a. operation b. transition c. revision d. none of the above 26、Which of the following provide useful measures of software quality (d) a. correctness, performance, integrity, usability b. reliability, maintainability, integrity, sales c. correctness, maintainability, size, sati

20、sfaction d. correctness, maintainability, integrity, usability 27、To be an effective aid in process improvement the baseline data used must be: (b) a. based on reasonable guesstimates from past projects b. measured consistently across similar projects c. collected over the past 6 months d. based on

21、all previously completed projects 28、The software engineering environment (SEE) consists of which of the following (c) a. customers and users b. developers and managers c. hardware platforms and software tools d. none of the above 29、LOC-based estimation techniques require problem decomposition base

22、d on (c) a. information domain values b. project schedule c. software functions d. process activities30、FP-based estimation techniques require problem decomposition based on (a) a. information domain values b. project schedule c. software functions d. process activities 31、Process-based estimation t

23、echniques require problem decomposition based on (c) a. information domain values and data objects b. project schedule and milestones c. software functions and process activities d. none of the above 32、Software risk always involves two characteristics (c) a. fire fighting and crisis management b. k

24、nown and unknown risks c. uncertainty and loss d. staffing and budget 33、Three categories of risks are (b) a. business risks, personnel risks, budget risks b. project risks, technical risks, business risks c. planning risks, technical risks, personnel risks d. management risks, technical risks, desi

25、gn risks 34、Risk projection attempts to rate each risk in two ways (c) a. likelihood and cost b. likelihood and impact c. likelihood and consequences d. likelihood and exposure 35、Risk tables are sorted by (b) a. probability and cost b. probability and impact c. probability and consequences d. proba

26、bility and exposure 36、An effective risk management plan will need to address which of the following issues (d) a. risk avoidance b. risk monitoring c. contingency planning d. all of the above 37、Which of the following is not one of the guiding principles of software project scheduling (b) a. compar

27、tmentalization b. market assessment c. time allocation d. effort validation 38、A task set is a collection of (a) a. engineering work tasks, milestones, deliverables b. task assignments, cost estimates, metrics c. milestones, deliverables, metrics d. responsibilities, milestones, documents 39、Adaptat

28、ion criteria are used to determine the (d) a. costs of product maintenance b. adjustments to the project schedule c. best project type classification for a software process d. recommended degree of rigor for software process 40、For purposes of determining the major engineering tasks and distributing

29、 them on the project time line, the project manager should assume that the process model used is (d) a. linear sequential b. iterative c. evolutionary d. any of the above 41、The purpose of earned value analysis is to (b) a. determine how to compensate developers based on their productivity b. provid

30、e a quantitative means of assessing software project progressc. provide a qualitative means of assessing software project progress d. set the price point for a software product based on development effort42、A key concept of quality control is that all work products (c) a. are delivered on time and u

31、nder budget b. have complete documentation c. have measurable specifications for process outputs d. are thoroughly tested before delivery to the customer43、Software reliability problems can almost always be traced to (b) a. errors in requirements gathering b. errors in design and implementation c. h

32、uman error d. errors in operation44、Which of these are valid software configuration items (d) a. case tools b. documentation c. executable programs and test data d. all of the above 45、Which of the following tasks is not part of software configuration management (c) a. change control b. reporting c.

33、 statistical quality control d. version control 46、Use-cases are scenarios that describe (a) a. how software is to be used in a given situation. b. how CASE tools will be used to construct the system. c. the build plan for a software product. d. the test cases for a software product. 47、Information

34、flow represents the manner in which data and control (b) a. are related to one another. b. changes each moves through the system. c. will be implemented in the final design. d. none of the above. 48、In the context of requirements analysis, two types of problem partitioning are (b) a. bottom-up and t

35、op-down b. horizontal and vertical c. subordinate and superordinate d. none of the above49、Which of the following is not an objective for building an analysis model (c) a. define set of software requirements b. describe customer requirements c. develop an abbreviated简短的 solution for the problem d. e

36、stablish basis for software design 50、Which of the following is not an area of concern in the design model (d) a. architecture b. data c. interfaces d. project scope 51、The importance of software design can be summarized in a single word (d) a. accuracy b. complexity c. efficiency d. quality 52、What

37、 types of abstraction are used in software design (d) a. control b. data c. procedural d. all of the above 53、Which of these model types does not represent a software architecture (a) a. data b. dynamic c. process d. structural 54、Which of the following is not part of software architecture (a) a. al

38、gorithm details b. databases c. data design d. program structure 55、An architectural style encompasses which of the following elements (d) a. constraints b. set of components c. semantic models d. all of the above 56、The criteria used to assess the quality of an architectural design should be based

39、on system (b) a. accessibility and reliability b. data and control c. functionality d. implementation details 57、In transaction mapping the first level factoring results in the (b) a. creation of a CFD b. derivation of the control hierarchy c. distribution of worker modules d. refinement of the modu

40、le view 58、A necessary supplement to transform or transaction mapping needed to create a complete architectural design is (c) a. entity relationship diagrams b. the data dictionary c. processing narratives for each module d. test cases for each module 59、Which of the following interface design princ

41、iples reduce the users memory load (d) a. define intuitive shortcuts b. disclose information in a progressive fashion c. establish meaningful defaults d. all of the above 60、Interface consistency implies that (d) a. input mechanisms remain the same throughout the application b. each application shou

42、ld have its own distinctive look and feel c. navigational methods are context sensitive d. answers a and b 61、Which of these are objectives for software testing (d) a. determine the productivity of programmers b. eliminate the need for future program maintenance c. eliminate every error prior to rel

43、ease d. uncover software errors 62、Black-box testing attempts to find errors in which of the following categories (d) a. incorrect or missing functions b. interface errors c. performance errors d. all of the above 63、What is the normal order of activities in which software testing is organized (c) a

44、. unit, integration, system, validation b. system, integration, unit, validation c. unit, integration, validation, system d. none of the above 64、The first step in any OOA process model are to (c) a. build an object-relationship model b. define collaborations between objects c. elicit customer requi

45、rements d. select a representation language 65、UML (unified modeling language) analysis modeling focuses on the (d) a. behavioral model and environment model b. behavioral model and implementation model c. user model and environmental model d. user model and structural model1. Modern software applic

46、ations are so complex that it is hard to develop mutually exclusive category names.(a) a. True b. False2. Software developers succeed more often than they fail, but software failures receive more press coverage.(a) a. True b. False3. Adding more people to a project that is already behind schedule is a good way to catch up. (b) a. True b. False4. Modern CASE tools are more important than the newest hardware for achieving good software quality and productivity.(a) a. True b. False 5. Change cannot be easily accommodated in most software systems, unless a system was designed