60 Important MCQs
MCQ 1
SDLC stands for:
A. Software Design Life Cycle
B. Software Development Life Cycle
C. System Development Level Cycle
D. Software Data Life Cycle
Answer: B
MCQ 2
Which phase determines what the software should do?
A. Coding
B. Requirement Analysis
C. Testing
D. Maintenance
Answer: B
MCQ 3
SRS stands for:
A. Software Requirement System
B. Software Requirements Specification
C. System Requirement Software
D. Software Resource Specification
Answer: B
MCQ 4
Which of the following is a functional requirement?
A. System should respond within 2 seconds
B. System should be highly secure
C. User can register an account
D. System should have 99.9% availability
Answer: C
MCQ 5
Which is a non-functional requirement?
A. User can log in
B. User can generate a report
C. System should respond within 2 seconds
D. Admin can delete a user
Answer: C
MCQ 6
Which feasibility examines whether required technology is available?
A. Economic
B. Technical
C. Operational
D. Legal
Answer: B
MCQ 7
Economic feasibility primarily evaluates:
A. Programming language
B. Cost and benefits
C. User interface
D. Database normalization
Answer: B
MCQ 8
Which document describes software requirements?
A. SRS
B. DFD
C. Gantt Chart
D. Source Code
Answer: A
MCQ 9
HLD stands for:
A. High-Level Design
B. Hardware-Level Data
C. High Logic Development
D. Hardware Logic Design
Answer: A
MCQ 10
LLD stands for:
A. Logical Link Design
B. Low-Level Design
C. Local Level Development
D. Low Logic Data
Answer: B
MCQ 11
Which design principle is generally desirable?
A. High coupling and low cohesion
B. Low coupling and high cohesion
C. High coupling and high cohesion
D. Low coupling and low cohesion
Answer: B
MCQ 12
Cohesion measures:
A. Dependency between modules
B. Relationship within a module
C. Project cost
D. Testing time
Answer: B
MCQ 13
Coupling measures:
A. Dependency between modules
B. Internal relationship of a module
C. Number of users
D. Number of test cases
Answer: A
MCQ 14
Which is generally considered the strongest form of cohesion?
A. Coincidental
B. Logical
C. Sequential
D. Functional
Answer: D
MCQ 15
UML stands for:
A. Unified Modeling Language
B. Universal Machine Language
C. Unified Machine Logic
D. User Modeling Language
Answer: A
MCQ 16
Which UML diagram represents actors and their interactions with a system?
A. Class diagram
B. Use Case diagram
C. Sequence diagram
D. Deployment diagram
Answer: B
MCQ 17
Which UML diagram shows interactions over time?
A. Class
B. Sequence
C. Component
D. Deployment
Answer: B
MCQ 18
Which diagram represents classes, attributes and methods?
A. Class diagram
B. Use Case diagram
C. Activity diagram
D. Sequence diagram
Answer: A
MCQ 19
Which SDLC model is sequential?
A. Waterfall
B. Agile
C. Spiral
D. Prototype
Answer: A
MCQ 20
Which model emphasizes risk analysis?
A. Waterfall
B. Spiral
C. V-Model
D. Incremental
Answer: B
MCQ 21
The Prototype Model is particularly useful when:
A. Requirements are completely fixed
B. Requirements are unclear
C. Testing is unnecessary
D. No user feedback is required
Answer: B
MCQ 22
Which model emphasizes verification and validation?
A. V-Model
B. Spiral
C. Prototype
D. Waterfall
Answer: A
MCQ 23
Agile development emphasizes:
A. No customer involvement
B. Responding to change
C. One-time delivery only
D. No testing
Answer: B
MCQ 24
Which is an Agile framework?
A. Scrum
B. Waterfall
C. V-Model
D. Big Bang
Answer: A
MCQ 25
A Scrum development cycle is called a:
A. Phase
B. Sprint
C. Loop
D. Stream
Answer: B
MCQ 26
Who is responsible for maximizing product value in Scrum?
A. Scrum Master
B. Product Owner
C. Tester
D. System Administrator
Answer: B
MCQ 27
Software testing primarily aims to:
A. Write source code
B. Identify defects and evaluate software
C. Design hardware
D. Create databases only
Answer: B
MCQ 28
Testing individual modules is called:
A. System testing
B. Integration testing
C. Unit testing
D. Acceptance testing
Answer: C
MCQ 29
Testing the interaction between modules is:
A. Unit testing
B. Integration testing
C. Acceptance testing
D. Regression testing
Answer: B
MCQ 30
Testing the complete integrated system is:
A. Unit testing
B. System testing
C. Module testing
D. Component testing
Answer: B
MCQ 31
Testing performed to determine whether software is acceptable to the customer is:
A. Unit testing
B. Acceptance testing
C. Integration testing
D. White-box testing
Answer: B
MCQ 32
Black-box testing focuses primarily on:
A. Internal code structure
B. Inputs and outputs
C. CPU architecture
D. Source-code optimization
Answer: B
MCQ 33
White-box testing focuses on:
A. Internal logic and code structure
B. User interface only
C. Customer satisfaction only
D. Hardware configuration
Answer: A
MCQ 34
Which is a white-box testing technique?
A. Boundary Value Analysis
B. Equivalence Partitioning
C. Branch Coverage
D. Decision Table
Answer: C
MCQ 35
Which is a black-box testing technique?
A. Statement coverage
B. Branch coverage
C. Path coverage
D. Equivalence partitioning
Answer: D
MCQ 36
Regression testing is performed to:
A. Test hardware
B. Ensure changes have not broken existing functionality
C. Create requirements
D. Estimate project cost
Answer: B
MCQ 37
Smoke testing is primarily used to:
A. Test every possible input
B. Check whether a build is stable enough for further testing
C. Replace system testing
D. Test only database performance
Answer: B
MCQ 38
Alpha testing is generally performed:
A. By random Internet users only
B. In a controlled environment by the development organization/internal testers
C. After software retirement
D. Only by hardware vendors
Answer: B
MCQ 39
Beta testing generally involves:
A. Selected external users
B. Only programmers
C. Only database administrators
D. Compilers
Answer: A
MCQ 40
"Are we building the product right?" refers to:
A. Validation
B. Verification
C. Debugging
D. Maintenance
Answer: B
MCQ 41
"Are we building the right product?" refers to:
A. Verification
B. Validation
C. Compilation
D. Integration
Answer: B
MCQ 42
Which process finds and fixes the cause of a software defect?
A. Testing
B. Debugging
C. Requirement analysis
D. Scheduling
Answer: B
MCQ 43
Corrective maintenance is used to:
A. Adapt software to a new OS
B. Fix defects
C. Add only new features
D. Prevent all future defects
Answer: B
MCQ 44
Adaptive maintenance deals with:
A. Changes in the environment
B. Fixing coding errors only
C. Removing requirements
D. Project scheduling
Answer: A
MCQ 45
Perfective maintenance generally focuses on:
A. Improving functionality/performance
B. Fixing hardware
C. Removing all documentation
D. Replacing testers
Answer: A
MCQ 46
Preventive maintenance aims to:
A. Improve maintainability and reduce future problems
B. Eliminate testing
C. Increase coupling
D. Remove documentation
Answer: A
MCQ 47
WBS stands for:
A. Work Breakdown Structure
B. Web-Based System
C. Work Base Schedule
D. Web Breakdown System
Answer: A
MCQ 48
WBS is used to:
A. Divide a project into manageable work packages/tasks
B. Encrypt software
C. Test source code
D. Design a database
Answer: A
MCQ 49
A Gantt chart is primarily used for:
A. Network security
B. Project scheduling
C. Source-code compilation
D. Database normalization
Answer: B
MCQ 50
PERT stands for:
A. Project Evaluation and Resource Technique
B. Program Evaluation and Review Technique
C. Program Engineering and Review Tool
D. Project Engineering Resource Tool
Answer: B
MCQ 51
The PERT expected-time formula is:
A. (O + M + P)/3
B. (O + 4M + P)/6
C. (O + 2M + P)/4
D. (O + M + 4P)/6
Answer: B
MCQ 52
If O = 2, M = 5 and P = 8, the PERT expected time is:
A. 4
B. 5
C. 6
D. 7
Answer: B
Calculation:
TE = (2 + 4×5 + 8)/6 = 30/6 = 5
MCQ 53
CPM stands for:
A. Critical Path Method
B. Computer Project Management
C. Critical Program Model
D. Computer Path Management
Answer: A
MCQ 54
The critical path determines:
A. Maximum number of programmers
B. Minimum project completion time
C. Number of requirements
D. Number of modules
Answer: B
MCQ 55
Activities on the critical path generally have:
A. Maximum float
B. Zero total float
C. Unlimited float
D. Negative cost
Answer: B
MCQ 56
Risk Exposure can commonly be calculated as:
A. Probability + Impact
B. Probability × Impact
C. Probability − Impact
D. Impact / Probability
Answer: B
MCQ 57
COCOMO was developed by:
A. Dennis Ritchie
B. Barry Boehm
C. James Gosling
D. Edsger Dijkstra
Answer: B
MCQ 58
COCOMO is primarily used for:
A. Software effort/cost estimation
B. Network routing
C. Database encryption
D. UI design
Answer: A
MCQ 59
In COCOMO, KLOC means:
A. Kilo Lines of Code
B. Key Lines of Computer
C. Kernel Lines of Code
D. Knowledge Level of Code
Answer: A
MCQ 60
Which combination represents good software design?
A. High coupling + low cohesion
B. Low coupling + high cohesion
C. High coupling + high cohesion
D. Low coupling + low cohesion
Answer: B
Bihar STET Most Important One-Liners
For quick revision, remember these:
- SDLC → Software Development Life Cycle
- SRS → Software Requirements Specification
- Functional requirement → What the system does
- Non-functional requirement → Quality/constraint of the system
- HLD → High-Level Design
- LLD → Low-Level Design
- Good design → High cohesion + Low coupling
- UML → Unified Modeling Language
- Use Case → Actors + System interactions
- Class Diagram → Classes, attributes, methods
- Sequence Diagram → Interaction over time
- Waterfall → Sequential model
- Spiral → Risk-oriented model
- Prototype → Useful when requirements are unclear
- V-Model → Verification + Validation
- Agile → Iterative + Incremental + adaptive
- Scrum → Agile framework
- Sprint → Fixed development iteration
- Unit Testing → Individual module
- Integration Testing → Interaction between modules
- System Testing → Complete system
- Acceptance Testing → Customer/user acceptance
- Black-box → No need to know internal code
- White-box → Internal code/logic
- Regression Testing → Checks impact of changes
- Smoke Testing → Basic build stability
- Debugging → Finds and fixes defect causes
- Verification → "Building the product right"
- Validation → "Building the right product"
- Corrective maintenance → Fix defects
- Adaptive maintenance → Environmental changes
- Perfective maintenance → Improve functionality/performance
- Preventive maintenance → Reduce future problems
- WBS → Work Breakdown Structure
- Gantt Chart → Project schedule
- PERT → Handles uncertain activity times
- CPM → Critical Path
- Critical path → Determines minimum project duration
- Risk Exposure → Probability × Impact
- COCOMO → Software cost/effort estimation
- KLOC → Thousand Lines of Code
