Software Development Life Cycle (SDLC)
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
2. Which SDLC phase primarily determines what the software should do?
A. Coding
B. Requirement Analysis
C. Testing
D. Maintenance
Answer: B
3. SRS stands for:
A. Software Requirement System
B. Software Requirements Specification
C. System Requirement Software
D. Software Resource Specification
Answer: B
4. Which of the following is a functional requirement?
A. System should respond within 2 seconds
B. System should have 99.9% availability
C. User can register an account
D. System should use encrypted communication
Answer: C
5. Which of the following 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
6. Which type of feasibility examines whether the required technology and technical resources are available?
A. Economic feasibility
B. Technical feasibility
C. Operational feasibility
D. Legal feasibility
Answer: B
7. Economic feasibility primarily evaluates:
A. Programming language
B. Costs and expected benefits
C. User interface design
D. Database normalization
Answer: B
8. Which document formally describes the software requirements?
A. SRS
B. DFD
C. Gantt Chart
D. Source Code
Answer: A
Software Design and UML
9. HLD stands for:
A. High-Level Design
B. Hardware-Level Data
C. High Logic Development
D. Hardware Logic Design
Answer: A
10. LLD stands for:
A. Logical Link Design
B. Low-Level Design
C. Local Level Development
D. Low Logic Data
Answer: B
11. Which combination is generally desirable in good software design?
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
12. Cohesion measures the:
A. Dependency between modules
B. Degree of relatedness among elements within a module
C. Project cost
D. Number of test cases
Answer: B
13. Coupling measures the:
A. Dependency between modules
B. Internal relatedness of a module
C. Number of users
D. Number of test cases
Answer: A
14. Which is generally considered the strongest form of cohesion?
A. Coincidental cohesion
B. Logical cohesion
C. Sequential cohesion
D. Functional cohesion
Answer: D
15. UML stands for:
A. Unified Modeling Language
B. Universal Machine Language
C. Unified Machine Logic
D. User Modeling Language
Answer: A
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
17. Which UML diagram shows interactions between objects in a time-ordered sequence?
A. Class Diagram
B. Sequence Diagram
C. Component Diagram
D. Deployment Diagram
Answer: B
18. Which UML diagram represents classes, attributes, and operations (methods)?
A. Class Diagram
B. Use Case Diagram
C. Activity Diagram
D. Sequence Diagram
Answer: A
SDLC Models and Agile
19. Which SDLC model follows a predominantly sequential approach?
A. Waterfall
B. Agile
C. Spiral
D. Prototype
Answer: A
20. Which SDLC model explicitly emphasizes risk analysis?
A. Waterfall
B. Spiral
C. V-Model
D. Incremental Model
Answer: B
21. The Prototype Model is particularly useful when:
A. Requirements are completely fixed
B. Requirements are unclear or evolving
C. User feedback is unnecessary
D. Testing is not required
Answer: B
22. Which SDLC model emphasizes the relationship between development activities and corresponding testing activities?
A. V-Model
B. Spiral Model
C. Prototype Model
D. Waterfall Model
Answer: A
23. Agile development emphasizes:
A. No customer involvement
B. Responding to changing requirements
C. One-time delivery only
D. Testing only at the end
Answer: B
24. Which of the following is an Agile framework?
A. Scrum
B. Waterfall
C. V-Model
D. Big Bang Model
Answer: A
25. In Scrum, a fixed-length development cycle is called a:
A. Phase
B. Sprint
C. Stream
D. Milestone
Answer: B
26. Who is primarily responsible for maximizing product value in Scrum?
A. Scrum Master
B. Product Owner
C. Tester
D. System Administrator
Answer: B
Software Testing
27. The primary purpose of software testing is to:
A. Write source code
B. Identify defects and evaluate software quality
C. Design computer hardware
D. Create database tables
Answer: B
28. Testing individual units or modules of software is called:
A. System Testing
B. Integration Testing
C. Unit Testing
D. Acceptance Testing
Answer: C
29. Testing the interaction between integrated modules is called:
A. Unit Testing
B. Integration Testing
C. Acceptance Testing
D. Regression Testing
Answer: B
30. Testing the complete integrated software system is called:
A. Unit Testing
B. System Testing
C. Module Testing
D. Component Testing
Answer: B
31. Testing performed to determine whether software meets user/customer acceptance criteria is:
A. Unit Testing
B. Acceptance Testing
C. Integration Testing
D. White-Box Testing
Answer: B
32. Black-box testing primarily focuses on:
A. Internal code structure
B. Inputs, outputs, and externally observable behavior
C. CPU architecture
D. Source-code optimization
Answer: B
33. White-box testing primarily focuses on:
A. Internal logic and code structure
B. User interface only
C. Customer satisfaction only
D. Hardware configuration
Answer: A
34. Which of the following is a white-box testing technique?
A. Boundary Value Analysis
B. Equivalence Partitioning
C. Branch Coverage
D. Decision Table Testing
Answer: C
35. Which of the following is a black-box testing technique?
A. Statement Coverage
B. Branch Coverage
C. Path Coverage
D. Equivalence Partitioning
Answer: D
36. Regression testing is performed to:
A. Test computer hardware
B. Ensure that changes have not adversely affected existing functionality
C. Create software requirements
D. Estimate project cost
Answer: B
37. Smoke testing is primarily performed 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
38. Alpha testing is generally performed:
A. By random Internet users
B. In a controlled environment by the development organization
C. After software retirement
D. Only by hardware vendors
Answer: B
39. Beta testing generally involves:
A. Selected external users
B. Only programmers
C. Only database administrators
D. Software compilers
Answer: A
Verification, Validation and Debugging
40. The question "Are we building the product right?" is associated with:
A. Validation
B. Verification
C. Debugging
D. Maintenance
Answer: B
41. The question "Are we building the right product?" is associated with:
A. Verification
B. Validation
C. Compilation
D. Integration
Answer: B
42. Which process involves finding and fixing the cause of a software defect?
A. Testing
B. Debugging
C. Requirement Analysis
D. Scheduling
Answer: B
Software Maintenance
43. Corrective maintenance is performed to:
A. Adapt software to a new operating environment
B. Fix defects and errors
C. Add only new features
D. Improve hardware performance
Answer: B
44. Adaptive maintenance deals primarily with:
A. Changes in the operating or external environment
B. Fixing coding errors only
C. Removing software requirements
D. Project scheduling
Answer: A
45. Perfective maintenance generally focuses on:
A. Improving functionality, performance, or usability
B. Fixing computer hardware
C. Removing documentation
D. Replacing testers
Answer: A
46. Preventive maintenance aims to:
A. Improve maintainability and reduce the likelihood of future problems
B. Eliminate software testing
C. Increase coupling
D. Remove documentation
Answer: A
Software Project Management
47. WBS stands for:
A. Work Breakdown Structure
B. Web-Based System
C. Work Base Schedule
D. Web Breakdown System
Answer: A
48. The primary purpose of a Work Breakdown Structure (WBS) is to:
A. Divide a project into manageable deliverables and work packages
B. Encrypt software
C. Test source code
D. Design a database
Answer: A
49. A Gantt chart is primarily used for:
A. Network security
B. Project scheduling and tracking
C. Source-code compilation
D. Database normalization
Answer: B
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
51. The commonly used 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
52. If Optimistic Time (O) = 2, Most Likely Time (M) = 5, and Pessimistic Time (P) = 8, the PERT expected time is:
A. 4
B. 5
C. 6
D. 7
Answer: B
Calculation:
TE = (O + 4M + P) / 6
TE = (2 + 4×5 + 8) / 6
TE = 30 / 6 = 5
53. CPM stands for:
A. Critical Path Method
B. Computer Project Management
C. Critical Program Model
D. Computer Path Management
Answer: A
54. In project scheduling, the critical path determines the:
A. Maximum number of programmers
B. Minimum project completion time
C. Number of software requirements
D. Number of modules
Answer: B
55. Activities on the critical path generally have:
A. Maximum float
B. Zero total float
C. Unlimited float
D. Negative cost
Answer: B
56. Risk Exposure is commonly calculated as:
A. Probability + Impact
B. Probability × Impact
C. Probability − Impact
D. Impact ÷ Probability
Answer: B
Software Estimation – COCOMO
57. COCOMO was developed by:
A. Dennis Ritchie
B. Barry Boehm
C. James Gosling
D. Edsger Dijkstra
Answer: B
58. COCOMO is primarily used for:
A. Software effort and cost estimation
B. Network routing
C. Database encryption
D. User interface design
Answer: A
59. In COCOMO, KLOC refers to:
A. Kilo Lines of Code
B. Key Lines of Computer
C. Kernel Lines of Code
D. Knowledge Level of Code
Answer: A
60. Which combination generally indicates 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 – Software Engineering Quick Revision
SDLC → Software Development Life Cycle
SRS → Software Requirements Specification
Functional Requirement → Specifies what the system should do
Non-Functional Requirement → Specifies quality attributes or constraints
Technical Feasibility → Checks technical viability and resources
Economic Feasibility → Evaluates costs and benefits
HLD → High-Level Design
LLD → Low-Level Design
Good Software Design → High cohesion + Low coupling
Cohesion → Relatedness within a module
Coupling → Dependency between modules
UML → Unified Modeling Language
Use Case Diagram → Actors and system interactions
Class Diagram → Classes, attributes, and methods/operations
Sequence Diagram → Interactions in time sequence
Waterfall → Sequential development model
Spiral → Risk-oriented development model
Prototype Model → Useful when requirements are unclear
V-Model → Verification and validation-oriented model
Agile → Iterative, incremental, and adaptive development
Scrum → Agile framework
Sprint → Fixed-length development cycle in Scrum
Product Owner → Maximizes product value
Unit Testing → Tests individual units/modules
Integration Testing → Tests interactions between modules
System Testing → Tests the complete integrated system
Acceptance Testing → Determines whether software meets acceptance criteria
Black-Box Testing → Focuses on external behavior without relying on internal code structure
White-Box Testing → Focuses on internal code/logic
Branch Coverage → White-box testing technique
Equivalence Partitioning → Black-box testing technique
Regression Testing → Checks whether changes affect existing functionality
Smoke Testing → Checks basic build stability
Alpha Testing → Controlled testing within/development organization
Beta Testing → Testing by selected external users
Verification → "Are we building the product right?"
Validation → "Are we building the right product?"
Debugging → Finds and fixes the cause of defects
Corrective Maintenance → Fixes defects
Adaptive Maintenance → Adapts software to environmental changes
Perfective Maintenance → Improves functionality, performance, or usability
Preventive Maintenance → Reduces future maintenance problems
WBS → Work Breakdown Structure
Gantt Chart → Project scheduling and tracking
PERT → Program Evaluation and Review Technique
PERT Expected Time → (O + 4M + P) / 6
CPM → Critical Path Method
Critical Path → Determines minimum project duration
Critical Path Activities → Generally have zero total float
Risk Exposure → Probability × Impact
COCOMO → Software effort/cost estimation
KLOC → Thousand Lines of Code
