On This Page

This set of Software Engineering Multiple Choice Questions & Answers (MCQs) focuses on Software Engineering Set 2

Q1 | In planning a software project one would
  • find ways to produce results using limited resources
  • pad the schedule to accommodate errors
  • overestimate the budget
  • structure the team to prevent administrative interference
Q2 | A systematic approach to software development, as epitomized by the various life-cycle models, is useful in
  • helping us understand the nature of the software product
  • convincing the customer that we know what we are doing
  • filling texts on software engineering
  • managing the various activities necessary to get the job done
Q3 | A process view in software engineering would consider which of the following
  • product performance
  • staffing
  • functionality
  • reliability
Q4 | What would be investigated during Requirements analysis?
  • system performance , test scheduling, organizational structure
  • languages , platforms, competition
  • system context , user populations, user tasks
  • verification, formal methods, accuracy
Q5 | Which of the following is not a description of planning?
  • planning is used to find credible ways to produce results with limited resources and limited schedule flexibility
  • planning is finding new personnel resources to support labor intensive development
  • planning is identifying and accommodating the unforeseen
  • planning is blending the efforts of many people to produce a product that satisfies the customer’s need
Q6 | The information we need to capture during requirements analysis not include
  • hiring authority
  • communication paths
  • synchronization
  • temporal dependencies
Q7 | Which among the following measures how strongly the elements within a module are related?
  • coupling
  • cohesion
  • aggregation
  • inheritance
Q8 | What do you call, when the elements of a module, all operate on the same data?
  • functional cohesion
  • temporal cohesion
  • procedural cohesion
  • communicational cohesion
Q9 | Which tests are designed to confront the program with abnormal situations?
  • recovery testing
  • security testing
  • stress testing
  • performance testing
Q10 | Which is not involved in software development process?
  • people
  • problem
  • practice
  • process
Q11 | How does a software project manager need to act to minimize the risk of software failure?
  • double the project team size
  • request a large budget
  • form a small software team
  • track progress
Q12 | To be an effective aid in process improvement the baseline metrics used must be
  • based on reasonable estimates from failed projects
  • measured consistently across projects
  • drawn from large projects only
  • based only on successful projects
Q13 | Empirical estimation models are typically based on
  • expert judgment based on past project experiences
  • refinement of current project estimation
  • regression models derived from historical project data
  • trial and error determination of the parameters and coefficients
Q14 | Which of the following is not the guiding principle of software project scheduling?
  • compartmentalization
  • market assessment
  • time allocation
  • effort validation
Q15 | PERT.
  • both (i) and (iii) above
  • both (i) and (iv) above
  • both (ii) and (iv) above
  • both (ii) and (iii) above
Q16 | The purpose of earned value analysis is to
  • determine how to compensate developers based on their productivity
  • provide a quantitative means of assessing software project progress
  • provide a qualitative means of assessing software project progress
  • set the price point for a software product based on development effort
Q17 | The rapid application development model is
  • same as component-based development
  • a useful approach when a customer cannot define requirements clearly
  • a high-speed adaptation of the linear sequential model
  • same as incremental model
Q18 | Which of the following is not an objective for building analysis models?
  • define set of software requirements that can be validated
  • describe customer requirements
  • develop a solution for the problem
  • establish basis for software design
Q19 | The entity relationship diagram
  • depicts relationships between data objects
  • depicts functions that transform the data flow
  • indicates how data are transformed by the system
  • indicates system reactions to external events
Q20 | Which of the following is not an area of concern in the design model?
  • architecture
  • data design
  • interfaces design
  • project scope
Q21 | Coupling is a qualitative indication of the degree to which a module
  • can be written more compactly
  • focuses on just one thing
  • is able to complete its function in a timely manner
  • is connected to other modules
Q22 | Provide an on-line tutorial
  • only (i) above
  • only (ii) above
  • only (iii) above
  • (i), (ii) and (iii) above
Q23 | Black box testing is also called
  • specification-based testing
  • structural testing
  • verification
  • unit testing
Q24 | Which configuration objects would not typically be found in the project database?
  • design specification
  • marketing data
  • executable code
  • test plans
Q25 | Statistical quality control.
  • only (i) above
  • only (ii) above
  • only (iii) above
  • both (i) and (ii) above