Software Engineering MCQ Quiz

  1. “Software engineers shall -
  2. “Software engineers should not use their technical skills to misuse other people’s computers.”Here the term misuse refers to:
  3. What is a Software ?
  4. Which of these software engineering activities are not a part of software processes ?
  5. The fundamental notions of software engineering does not account for ?
  6. Which one of the following models is not suitable for accommodating any change?
  7. SDLC stands for
  8. The spiral model was originally proposed by -
  9. If you were to create client/server applications, which model would you go for?
  10. Infrastructure software are covered under ?
  11. Build and Fix model has?
  12. White box testing, a software testing technique is sometimes called ?
  13. Structured programming codes includes ?
  14. The document listing all procedures and regulations that generally govern an organization is the ?
Software Engineering MCQ

Take Software Engineering Quiz to Test Your Knowledge 

We have listed below the best Software Engineering MCQ Questions that check your basic knowledge of Software Engineering. This Software Engineering Test contains the 35 best Software Engineering MCQ. You have to select the right answer to every question for the best preparation of your exam/interviews. You can also download the Software Engineering MCQ PDF completely from the given link below.

Also, Read the Best Software Engineering Interview Questions.

  • act consistently with the public interest.”
  • act in a manner that is in the best interests of his expertise and favour.”
  • ensure that their products only meet the SRS.” d) all of the mentioned
  • all of the mentioned
View Answer
  • Unauthorized modification of computer material
  • Unauthorized access to computer material
  • Dissemination of viruses or other malware
  • All of the above
View Answer
  • Software is documentation and configuration of data
  • Software is set of programs
  • Software is set of programs, documentation & configuration of data
  • None of the mentioned
View Answer
  • Software development
  • Software dependence
  • Software validation
  • Software specification
View Answer
  • Software Security
  • Software reuse
  • Software processes
  • Software Validation
View Answer
  • Prototyping Model
  • RAD Model
  • Build & Fix Model
  • Waterfall Model
View Answer
  • System Development Life cycle
  • Software Design Life Cycle
  • Software Development Life Cycle
  • System Design Life Cycle
View Answer
  • Barry Boehm
  • Pressman
  • Royce
  • Pressman
View Answer
  • Concurrent Model
  • Spiral Model
  • WINWIN Spiral Model
  • Incremental Model
View Answer
  • Customised Products
  • Generic and Customised Products
  • Generic Products
  • None of the above
View Answer
  • 1 Phases
  • 2 Phases
  • 3 Phases
  • 4 Phases
View Answer
  • Graph Testing
  • Basic path
  • Glass box testing
  • Dataflow
View Answer
  • alteration & iteration
  • multiple exit from loops
  • sequencing
  • only 1 and 3
View Answer
  • Organizing manual
  • Personal poling bank
  • Administration policy manual
  • Procedure log
View Answer
  • Non-Functional Requirements
  • Goals of Implementation
  • Functional Requirements
  • Algorithms for Software Implementation
View Answer
  • constructive cost Model
  • common control Model
  • composition cost Model
  • consumed cost Model
View Answer
  • Errors per KLOC
  • Defects per KLOC
  • $ per KLOC
  • Pages of documentation per KLOC
View Answer
  • Direct measures
  • Coding
  • Indirect measures
  • None of the above
View Answer
  • 6
  • 5
  • 4
  • 3
View Answer
  • track potential risk
  • help in assessment of status of ongoing project.
  • both 1 and 2
  • none of the mentioned
View Answer
  • Effort Applied
  • Efficiency
  • Effort Applied
  • All of the mentioned
View Answer
  • number of user inputs
  • number of lines of code
  • number of Functions
  • amount of memory usage
View Answer
  • Time required to become moderately efficient in system usage
  • Net increase in productivity
  • Intellectual skill to learn the system
  • All of the mentioned
View Answer
  • Software functionality
  • Software maintainability
  • Software development
  • Both Software functionality & maintainability
View Answer
  • Actively involve system users in the analysis, design, and development phases
  • Focus initially on creating a prototype that looks and acts like the desired system
  • Accelerate collecting the business requirements through an interactive and iterative construction approach
  • All of the above
View Answer
  • The importance of self-organizing teams as well as communication and collaboration between team members and customers.
  • Recognition that change represents opportunity.
  • Emphasis on rapid delivery of software that satisfies the customer.
  • Having a separate testing phase after a build phase.
View Answer
  • Unambiguous
  • Distinctly specified
  • Functional
  • All of these
View Answer
  • Management Myths
  • Customer Myths
  • Practitioner Myths
  • All of the above
View Answer
  • Customer involvement
  • Embrace change
  • Incremental delivery
  • Following the plan
View Answer
  • Prototyping
  • Iterative
  • Timeboxing
  • Glassboxing
View Answer
  • Pareto analysis is a statistical method used for analyzing causes, and is one of the primary tools for quality management.
  • Reliability of a software specifies the probability of failure-free operation of that software for a given time duration.
  • The reliability of a system can also be specified as the Mean Time To Failure (MTTF).
  • In white-box testing, the test cases are decided from the specifications or the requirements.
View Answer
  • Stereotype is used for extending the UML language
  • Stereotyped class must be abstract
  • The stereotype indicates that the UML element cannot be changed
  • UML profiles can be stereotyped for backward compatibility
View Answer
  • Ability to undergo change
  • Adaptability to new environments
  • Operational characteristics
  • Production costs and scheduling
View Answer