Software Engineering MCQ Questions and Answers for Practice

1. The level at which the software uses scarce resources is

1. efficiency
2. portability
3. reliability
4. all of the above

2. The most important feature of spiral model is

1. risk management
2. quality management
3. requirement analysis
4. configuration management

3. Which is not a step of requirement engineering?

1. Requirements analysis
2. Requirements design
3. Requirements elicitation
4. Requirements documentation

4. Structured charts are a product of

1. requirements analysis
2. design
3. requirements gathering
4. coding

5. Modules X and Y operate on the same input and output data, then the cohesion is

1. Communicational
2. Procedural
3. Sequential
4. Logical

6. Site for Alpha Testing is

1. Installation place
2. Any where
3. Software Company
4. None of the above

7. IEEE 830-1993 is a IEEE recommended standard for

1. Software design
2. Testing
3. Software requirement specification
4. Both (A) and (B)

8. SRD stands for

1. Structured requirements definition
2. Software requirements diagram
3. Software requirements definition
4. Structured requirements diagram

9. Output comparators are used in

1. dynamic testing of single module
2. static testing of single and multiple module
3. static testing of single module
4. dynamic testing of single and multiple module

10. ER model shows the

1. Functional view
2. Dynamic view
3. Static view
4. All the above

11. Which of the following quality of SRS document ensures to compare the results of a phase with another phase ?

1. Verifiable
2. Traceable
3. Structured
4. Concise

12. Who writes the Software Requirement Specifications Document(SRS)?

1. System Tester
2. System Analyst
3. System Developer
4. None of these above

13. Requirements can be refined using

1. prototyping model
2. the evolutionary model
3. The waterfall model
4. the spiral model

14. What is the goal of the requirements analysis and specifications phase of software development life cycle ?

1. Analyzing the cost of development
2. Determining scope of the software
3. Understanding the customer requirements and organize them in an informal document
4. None of these above

15. One of the fault base testing techniques is

1. beta testing
2. Stress testing
3. unit testing
4. mutation testing