MCQs / Computer Science / NSCT: Software Engineering
NSCT: Software Engineering MCQs — Computer Science (page 3) 117 multiple-choice questions on NSCT: Software Engineering from Computer Science, each with the correct answer and, where available, a teacher's explanation. Read through them to revise the chapter, then practise the same questions one by one to test yourself.
51. A risk has a probability of 0.1 and an impact of Rs. 500,000. What is its risk exposure? Rs. 100,000 Rs. 5,000,000 Rs. 50,000 Rs. 500,000 Answer: C) Rs. 50,000
Explanation: Risk exposure = probability × impact. Lesson 5.5 · Software Engineering
Discuss this question
52. A function contains 6 independent decision points (if/while). What is its cyclomatic complexity? 6 8 12 7 Answer: D) 7
Explanation: V(G) = decisions + 1 = 7. Lesson 5.5 · Software Engineering
Discuss this question
53. Gathering requirements through interviews, questionnaires and observation is called: Requirements elicitation Deployment Implementation Requirements validation Answer: A) Requirements elicitation
Explanation: Elicitation discovers what stakeholders need. Lesson 5.3 · Software Engineering
Discuss this question
54. A UML diagram showing messages exchanged between objects in time order is a: Class diagram State diagram Component diagram Sequence diagram Answer: D) Sequence diagram
Explanation: Time flows downward. Lesson 5.3 · Software Engineering
Discuss this question
55. A form accepts a age from 18 to 60 (inclusive). Using boundary value analysis, which set of test values is best? 17, 18, 60, 61 39 18, 60 19, 59 Answer: A) 17, 18, 60, 61
Explanation: Test just below, on, and just above each boundary. Lesson 5.5 · Software Engineering
Discuss this question
56. A form accepts a password length from 8 to 20 (inclusive). Using boundary value analysis, which set of test values is best? 7, 8, 20, 21 8, 20 14 9, 19 Answer: A) 7, 8, 20, 21
Explanation: Test just below, on, and just above each boundary. Lesson 5.5 · Software Engineering
Discuss this question
57. Adding a dark-mode feature requested by users is: Corrective maintenance Emergency maintenance Adaptive maintenance Perfective maintenance Answer: D) Perfective maintenance
Explanation: It improves or extends functionality. Lesson 5.5 · Software Engineering
Discuss this question
58. Project tasks: A (3 days); B (4 days, after A); C (2 days, after A); D (5 days, after B & C); E (1 day, after D). Which is the critical path? E–D–C–B–A A–B–C–D–E A–B–D–E A–C–D–E Answer: C) A–B–D–E
Explanation: It is the longest path (13 days). Lesson 5.5 · Software Engineering
Discuss this question
59. Customers keep adding features after the scope is agreed, without adjusting time or budget. This is called: Regression Scope creep Technical debt Refactoring Answer: B) Scope creep
Explanation: Uncontrolled growth of scope. Lesson 5.3 · Software Engineering
Discuss this question
60. A startup's requirements change weekly based on user feedback. The best approach is: V-model Big-bang Agile Waterfall Answer: C) Agile
Explanation: Agile embraces change with short iterations. Lesson 5.1 · Software Engineering
Discuss this question
61. Fixing a bug reported by users is: Corrective maintenance Perfective maintenance Adaptive maintenance Preventive maintenance Answer: A) Corrective maintenance
Explanation: It corrects faults. Lesson 5.5 · Software Engineering
Discuss this question
62. An architecture where an application is built as many small, independently deployable services is: Monolithic Peer-to-peer file sharing Microservices Pipe-and-filter only Answer: C) Microservices
Explanation: Each service owns its data and API. Lesson 5.4 · Software Engineering
Discuss this question
63. Making an old payment API work with a new interface without changing either is done with the: Singleton pattern Iterator pattern Adapter pattern Strategy pattern Answer: C) Adapter pattern
Explanation: Adapters convert one interface into another. Lesson 5.4 · Software Engineering
Discuss this question
64. Which is a non-functional requirement? The admin can delete accounts The system generates invoices The user can add items to a cart The system must be available 99.9% of the time Answer: D) The system must be available 99.9% of the time
Explanation: Availability is a quality attribute. Lesson 5.3 · Software Engineering
Discuss this question
65. A pattern that provides one simple interface to a complex subsystem is: Observer Prototype Decorator Facade Answer: D) Facade
Explanation: Like a single "Place order" call hiding many services. Lesson 5.4 · Software Engineering
Discuss this question
66. A Scrum team completed 150 story points in 5 sprints. The backlog has 300 points in total. At the same velocity, how many more sprints are needed? 5 10 4 6 Answer: A) 5
Explanation: Velocity = 150 ÷ 5 = 30; remaining 150 ÷ 30 → 5 sprints. Lesson 5.2 · Software Engineering
Discuss this question
67. Project tasks: A (3 days); B (4 days, after A); C (2 days, after A); D (5 days, after B & C); E (1 day, after D). What is the minimum project duration? 15 days 13 days 16 days 11 days Answer: B) 13 days
Explanation: The critical path A–B–D–E takes 13 days. Lesson 5.5 · Software Engineering
Discuss this question
68. A Scrum team completed 54 story points in 2 sprints. The backlog has 90 points in total. At the same velocity, how many more sprints are needed? 4 3 1 2 Answer: D) 2
Explanation: Velocity = 54 ÷ 2 = 27; remaining 36 ÷ 27 → 2 sprints. Lesson 5.2 · Software Engineering
Discuss this question
69. Automatically building and testing code every time it is pushed is: Big-bang integration Code freeze Manual QA Continuous integration Answer: D) Continuous integration
Explanation: CI catches integration problems early. Lesson 5.2 · Software Engineering
Discuss this question
70. Velocity in Scrum is: Lines of code per day Number of bugs per sprint The number of story points completed per sprint Speed of the server Answer: C) The number of story points completed per sprint
Explanation: It helps forecast future sprints. Lesson 5.2 · Software Engineering
Discuss this question
71. Low coupling between modules means: Modules depend on each other as little as possible Modules are tightly integrated Modules share global variables heavily Every module calls every other module Answer: A) Modules depend on each other as little as possible
Explanation: Low coupling eases change and testing. Lesson 5.4 · Software Engineering
Discuss this question
72. "As a student, I want to reset my password so that I can log in again" is a: Use-case diagram Test case User story Risk register entry Answer: C) User story
Explanation: Format: As a <role, I want <goal so that <benefit. Lesson 5.2 · Software Engineering
Discuss this question
73. The Scrum Master mainly: Approves the budget Assigns tasks to each developer Writes all the code Removes impediments and coaches the team on Scrum Answer: D) Removes impediments and coaches the team on Scrum
Explanation: The Scrum Master is a servant-leader. Lesson 5.2 · Software Engineering
Discuss this question
74. Testing based on the internal code structure is: White-box testing Acceptance testing Usability testing Black-box testing Answer: A) White-box testing
Explanation: Also called glass-box or structural testing. Lesson 5.5 · Software Engineering
Discuss this question
75. Project tasks: A (2 days); B (6 days, after A); C (3 days, after A); D (4 days, after C); E (2 days, after B & D). What is the minimum project duration? 14 days 11 days 17 days 9 days Answer: B) 11 days
Explanation: The critical path A–C–D–E takes 11 days. Lesson 5.5 · Software Engineering
Discuss this question
Previous Page 3 of 5 Next
Practise NSCT: Software Engineering MCQs
More Computer Science chapters