NSCT – Software Requirements Engineering MCQs 20 min Score: 0 Attempted: 0/20 Subscribe 1. . Software requirements engineering is concerned with: (A) Designing software architecture (B) Eliciting, analyzing, documenting, and validating software requirements (C) Coding only (D) CPU schedulingShow All Answers 2. . The first step in requirements engineering is: (A) Requirement elicitation (B) Design (C) Testing (D) Maintenance 3. . Requirement elicitation involves: (A) Writing code (B) Scheduling CPU (C) Gathering requirements from stakeholders (D) Allocating memory 4. . Functional requirements describe: (A) What the system should do (B) System performance (C) Security features only (D) CPU utilization 5. . Non-functional requirements describe: (A) System behavior, performance, and quality attributes (B) Only functionality (C) CPU scheduling (D) File storage 6. . A SRS (Software Requirement Specification) document: (A) Only describes hardware (B) Contains all functional and non-functional requirements (C) Only schedules CPU (D) Only allocates memory 7. . Requirement validation ensures: (A) Files are deleted (B) CPU speed is maximized (C) Memory is allocated (D) Requirements are correct, complete, and feasible 8. . Requirement analysis involves: (A) Scheduling CPU (B) Coding (C) Memory allocation (D) Refining and resolving conflicts in gathered requirements 9. . Stakeholders include: (A) Only software developers (B) Only testers (C) CPU and memory (D) Users, customers, managers, and developers 10. . Techniques for requirement elicitation include: (A) Memory allocation (B) CPU scheduling (C) File management (D) Interviews, questionnaires, observation, and prototyping 11. . Requirements can be categorized into: (A) Hardware and software requirements (B) File system requirements only (C) Memory and CPU requirements (D) Functional and non-functional requirements 12. . A use case describes: (A) Hardware allocation (B) Interactions between a user (actor) and the system to achieve a goal (C) CPU scheduling (D) Memory allocation 13. . Requirements traceability ensures: (A) Memory is allocated properly (B) CPU is utilized fully (C) Each requirement is linked to design, code, and tests (D) Files are organized 14. . Prototyping is used in requirements engineering to: (A) Allocate memory (B) Write final code (C) Validate requirements and gather feedback (D) Manage CPU 15. . Requirements change management is important because: (A) CPU scheduling changes (B) Requirements are often volatile and evolve over time (C) Memory allocation changes (D) File locations change 16. . Functional requirements are usually: (A) Optional (B) Mandatory for system operation (C) Irrelevant (D) Only for testing 17. . Non-functional requirements include: (A) File storage only (B) CPU scheduling only (C) Memory allocation only (D) Performance, reliability, usability, security, and maintainability 18. . The main goal of requirements engineering is to: (A) Ensure that software meets stakeholder needs and is of high quality (B) Manage CPU only (C) Allocate memory only (D) Delete files automatically 19. . Ambiguous requirements can lead to: (A) Clear software design (B) Misunderstandings, defects, and project failure (C) Increased CPU speed (D) File deletion 20. . The final outcome of requirements engineering is: (A) Memory allocation table (B) CPU scheduling table (C) Software Requirement Specification (SRS) document (D) File system layout