Answer these 100+ Software Engineering MCQs and assess your grip on the subject of Software Engineering. Scroll below and get started!
A. black box
B. white box
C. exhaustive
D. None of the above
A. second generation
B. third generation
C. fourth generation
A. Bottom-Up Integration Testing
B. Top-Down Integration Testing
C. Big-Bang Integration Testing
D. Mixed/Sandwich Integration Testing
A. It should be concise.
B. It should specify the implementation and issues in it.
C. It should show conceptual integrity
D. It should be structured
A. inheritance, aggregation
B. association, inheritance
C. aggregation, composition
D. composition, association
A. Error correction
B. Error prevention
C. Both a and b
D. None of the above
A. Understandability
B. Rigidity
C. Efficiency
D. Maintainability
E. Complexity
A. Shortage of programming languages
B. Shortage of rapid progress in software engineering
C. Increased problem size
D. All of the above
A. feasibility study
B. requirement analysis and specification
C. design
D. testing
A. It helps in systematic and disciplined development of software products.
B. It helps in defining an entry and exit criteria only for the first and last phase of the software development.
C. It helps in monitoring progress of the project.
D. A software life cycle model is a brief introduction of the software life cycle.
A. Conditions
B. Requirements
C. Actions
D. Result
A. Regression testing
B. Volume testing
C. Usability testing
D. Maintenance testing
E. Compatibilty testing
A. abstraction, decomposition
B. abstraction and jump
C. decomposition and exploratory programming
D. exploratory programming and abstraction
E. exploratory programming and jump
A. i
B. ii
C. iii
D. None of the above
A. ad-hoc
B. white-box
C. black-box
D. exhaustive
A. Software configuration management
B. Validation
C. Design and implementation
D. Test case design
E. Software specifications
F. Evolution
G. Documentation
A. static
B. dynamic
C. both static and dynamic
A. Functions in a system
B. Data items that flows between the processing stations
C. Design of control structure
D. Sequence of execution of instructions
E. None of the above
A. verification, validation
B. validation, verification
C. validation, validation
D. verification, verification
A. Compatibility testing
B. Volume testing
C. Regression testing
D. Stress testing
A. coding
B. system testing
C. designing
D. unit testing
A. inheritance
B. association
C. aggregation
D. composition
A. a test team within the developing organization
B. a test team outside the developing organization
C. actual customers or a selected group of friendly customers.
D. a selected group of developers
A. Program Slicing
B. Brute Force
C. Backtracking
D. Cause Elimination
A. difficult to underStand
B. easy to implement
C. less expensive to develop
D. all of the above
A. Software specification
B. Software designing
C. Software validation
D. Software evolution
E. All of the above
A. testing is performed in the end, after the entire project is developed
B. initially a prototype is developed and tested, and then a second testing is performed after the completion of a project
C. coding is performed incrementally. A new increment is started only after the successful testing of the previous increment
D. requirements are tested and documented
A. high, high
B. high, low
C. low, high
D. low, low
A. Development tools
B. Technical processes of software development
C. Development of methods and theories
D. Hardware maintenance
E. Networking
A. recovery
B. compatibility
C. volume
D. regression
A. implementation phase
B. testing phase
C. feasibility study phase
D. coding phase
A. Model-Oriented
B. Property-Oriented
C. Both a and b
A. software failure
B. software fault
A. Single-entry and single-exit constructs should be used as much as possible.
B. Information hiding should not be done at all.
C. The use of user-defined data types should be avoided as much as possible.
D. The level of nesting should not be too deep.
A. An actor in a use case diagram can participate in one use case only.
B. In a use case diagram, one use case is independent of the other use case.
C. All the views should be constructed for a given problem using all the diagrams that are provided by the UML.
D. The static structure of a system is described by class diagram.
A. V-Shaped model
B. Prototype Model
C. Spiral Model
D. Waterfall Model
A. DFDs represent data flow in the system as well as function performed by the system.
B. Control aspects are very precisely defined by DFDs.
C. DFDs are simple to understand and use.
D. The order of operation of processes is captured by a DFD
A. different modules are coded then combined together in one step and then tested as a whole unit.
B. different components are integrated one by one and tested at each level of integration.
C. different components are integrated one by one but tested only as a whole system.
D. system is divided into modules and each module is tested in isolation.
A. the shadows that lurk in the back of a character's mind
B. the clues in the narrative that give an indication of or preempt the future plot or story
C. the tying up of all loose ends at the end of the story
D. the rebels in a gothic horror story
E. None of the above
A. Readers expect more from short stories.
B. The characters and plot must be introduced and developed quickly rather than over a period of time.
C. Short stories have more characters.
D. All of the above
E. None of the above
A. Dialogue shares information by narrating the story.
B. Dialogue is less important than other aspects of story-telling such as setting, theme, and characterization.
C. Dialogue propels the plot forward through a character's actions rather than through his words.
D. Dialogue reflects the speaking voice of the character.
A. a character from the past
B. a character who is larger than life
C. a character whose behavior or mannerisms are exaggerated for comic relief, as in a visual cartoon
D. a drawing of the main character
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. Why does computer hardware cost so much?
B. Why does computer hardware cost so much?
C. Why does it cost so much to develop a piece of software?
D. Why can’t software errors be removed from products prior to delivery?
A. Software suffers from exposure to hostile environments.
B. Defects are more likely to arise after software has been used often.
C. Multiple change requests introduce errors in component interactions.
D. Software spare parts become harder to order.
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. ProcessProcess
B. Manufacturing
C. Methods
D. Tools
A. communication, planning, modeling, construction, deployment.
B. communication, risk management, measurement, production, reviewing.
C. analysis, designing, programming, debugging, maintenance.
D. analysis, planning, designing, programming, testing.
A. True
B. False
A. True
B. False
A. True
B. False
A. . Concurrent process flow.
B. Iterative process flow.
C. Linear process flow
D. Spiral process flow.
E. E. both b and c
A. Concurrent process flow.
B. Iterative process flow.
C. Linear process flow.
D. Spiral process flow.
E. both b and c
A. SEI
B. SPICE
C. ISO 9000.
D. ISO 9001
E. both b and d
A. True
B. False
A. True
B. False
A. A reasonable approach when requirements are well defined.
B. A good approach when a working program is 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.
A. A reasonable approach when requirements are well defined.
B. A good approach 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.
A. Are iterative in nature.
B. Can easily accommodate product requirements changes.
C. Do not generally produce throwaway systems.
D. . All of the above.
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 produces a meaningful product.
A. Ends with the delivery of the software product.
B. Is more chaotic than the incremental model
C. Includes project risks evaluation during each iteration.
D. All of the above.
A. Another name for concurrent engineering.
B. Defines events that trigger engineering activity state transitions.
C. Only used for development of parallel or distributed systems.
D. Used whenever a large number of change requests are anticipated.
A. Another name for concurrent engineering.
B. Defines events that trigger engineering activity state transitions.
C. Only used for development of parallel or distributed systems.
D. Used whenever a large number of change requests are anticipated.
E. Both a and b
A. Only appropriate for computer hardware design.
B. Not able to support the development of reusable components.
C. Dependent on object technologies for support.
D. Not cost effective by known quantifiable software metrics.
A. Define the specification for computer-based systems.
B. Develop defect free computer-based systems.
C. Verify the correctness of computer-based systems
D. All of the above.
A. Inception phase.
B. Elaboration phase.
C. Construction phase
D. Validation phase.
A. Emphasizes personal measurement of work product.
B. Practitioner requires careful supervision by the project manager.
C. Individual practitioner is responsible for estimating and scheduling.
D. . Practitioner is empowered to control quality of software work products.
A. Accelerate software process improvement.
B. Allow better time management by highly trained professionals.
C. Build self-directed software teams. D. Show managers how to reduce cost
D. Both b and c
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. Eliminate the use of project planning and testing.
B. Only essential work products are produced.
C. Process allows team to streamline tasks.
D. Uses incremental product delivery strategy.
A. Requirements gathering must be conducted very carefully.
B. Risk analysis must be conducted before planning takes place.
C. Software increments must be delivered in short time periods.
D. Software processes must adapt to changes incrementally.
E. Both c and d
A. analysis, design, coding, testing.
B. planning, analysis, design, coding.
C. planning, analysis, coding, testing.
D. planning, design, coding, testing.
A. What did you do since the last meeting?
B. What obstacles are you encountering?
C. What is the cause of the problem you are encountering?
D. What do you plan to accomplish be the next team meeting?
A. Analysis
B. Design
C. Coding
D. Testing
E. Both a and b
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. True
B. False
A. Attentive to detail
B. Brutally honest.
C. Follows process rule dogmatically.
D. Resilient under pressure.