BS Information Systems · Systems Analysis & Design

Unit 3: Requirements Elicitation MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Requirements Elicitation Concepts within Requirements Elicitation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt is only a collection of computers and excludes people and processes.
  2. BIt automatically creates business value whenever new technology is purchased.
  3. CIt can be designed without understanding organizational context.
  4. DIt should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Show answer
Answer: D. It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Report a mistake

Q2. What is the primary purpose of Requirements Elicitation Concepts in an information-systems environment? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt guarantees competitive advantage without organizational change.
  2. BIt supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
  3. CIts purpose is always to maximize the number of applications.
  4. DIt eliminates the need for business processes and management decisions.
Show answer
Answer: B. It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Report a mistake

Q3. An organization is working with Requirements Elicitation Concepts. Which approach is most appropriate? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. APurchase technology before identifying the business problem.
  2. BIgnore users because technical implementation alone determines success.
  3. CSkip outcome verification once the system is installed.
  4. DClarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Show answer
Answer: D. Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Report a mistake

Q4. Which consideration best supports alignment of Requirements Elicitation Concepts with organizational needs? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIgnore stakeholder and process requirements when technology is modern.
  2. BConnect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
  3. CChoose systems only because competitors use them.
  4. DMeasure alignment solely by the number of software licenses.
Show answer
Answer: B. Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Report a mistake

Q5. Which information or data consideration is most important when applying Requirements Elicitation Concepts? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ACollect all possible data regardless of relevance or governance.
  2. BAssume information is accurate because it is stored electronically.
  3. CIgnore timeliness and provenance when reports look professional.
  4. DEnsure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Show answer
Answer: D. Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Report a mistake

Q6. Which control or governance principle is most relevant to Requirements Elicitation Concepts? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ATreat accountability as unnecessary when tasks are automated.
  2. BUse clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
  3. CGive every user administrator access to reduce support requests.
  4. DAvoid audit trails so processes remain flexible.
Show answer
Answer: B. Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Report a mistake

Q7. How should an organization evaluate the effectiveness of Requirements Elicitation Concepts? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AMeasure only implementation cost and ignore outcomes.
  2. BAssume user adoption proves business value.
  3. CUse metrics unrelated to the original objective.
  4. DUse service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Show answer
Answer: D. Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Report a mistake

Q8. When changing a system involving Requirements Elicitation Concepts, what should be prioritized? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AModify many unrelated processes simultaneously without testing.
  2. BAssess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
  3. CChange production systems without impact analysis.
  4. DAvoid communicating changes to affected users.
Show answer
Answer: B. Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Report a mistake

Q9. Which trade-off should be assessed when selecting an approach to Requirements Elicitation Concepts? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AOnly acquisition price matters in every system decision.
  2. BIntegration and maintainability never affect enterprise systems.
  3. CAlways maximize technical complexity regardless of business value.
  4. DBalance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Show answer
Answer: D. Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Report a mistake

Q10. Which example best represents professional practice involving Requirements Elicitation Concepts? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AUse personal preference instead of evidence and organizational objectives.
  2. BDocument objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
  3. CMake undocumented changes whenever convenient.
  4. DExclude stakeholders to speed up requirements work.
Show answer
Answer: B. Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Concepts: Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Report a mistake

Q11. Which statement best describes Requirements Elicitation Components within Requirements Elicitation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt can be designed without understanding organizational context.
  2. BIt should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
  3. CIt is only a collection of computers and excludes people and processes.
  4. DIt automatically creates business value whenever new technology is purchased.
Show answer
Answer: B. It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Report a mistake

Q12. What is the primary purpose of Requirements Elicitation Components in an information-systems environment? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIts purpose is always to maximize the number of applications.
  2. BIt eliminates the need for business processes and management decisions.
  3. CIt guarantees competitive advantage without organizational change.
  4. DIt supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Show answer
Answer: D. It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Report a mistake

Q13. An organization is working with Requirements Elicitation Components. Which approach is most appropriate? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ASkip outcome verification once the system is installed.
  2. BClarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
  3. CPurchase technology before identifying the business problem.
  4. DIgnore users because technical implementation alone determines success.
Show answer
Answer: B. Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Report a mistake

Q14. Which consideration best supports alignment of Requirements Elicitation Components with organizational needs? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AChoose systems only because competitors use them.
  2. BMeasure alignment solely by the number of software licenses.
  3. CIgnore stakeholder and process requirements when technology is modern.
  4. DConnect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Show answer
Answer: D. Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Report a mistake

Q15. Which information or data consideration is most important when applying Requirements Elicitation Components? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIgnore timeliness and provenance when reports look professional.
  2. BEnsure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
  3. CCollect all possible data regardless of relevance or governance.
  4. DAssume information is accurate because it is stored electronically.
Show answer
Answer: B. Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Report a mistake

Q16. Which control or governance principle is most relevant to Requirements Elicitation Components? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AGive every user administrator access to reduce support requests.
  2. BAvoid audit trails so processes remain flexible.
  3. CTreat accountability as unnecessary when tasks are automated.
  4. DUse clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Show answer
Answer: D. Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Report a mistake

Q17. How should an organization evaluate the effectiveness of Requirements Elicitation Components? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AUse metrics unrelated to the original objective.
  2. BUse service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
  3. CMeasure only implementation cost and ignore outcomes.
  4. DAssume user adoption proves business value.
Show answer
Answer: B. Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Report a mistake

Q18. When changing a system involving Requirements Elicitation Components, what should be prioritized? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AChange production systems without impact analysis.
  2. BAvoid communicating changes to affected users.
  3. CModify many unrelated processes simultaneously without testing.
  4. DAssess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Show answer
Answer: D. Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Report a mistake

Q19. Which trade-off should be assessed when selecting an approach to Requirements Elicitation Components? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AAlways maximize technical complexity regardless of business value.
  2. BBalance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
  3. COnly acquisition price matters in every system decision.
  4. DIntegration and maintainability never affect enterprise systems.
Show answer
Answer: B. Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Report a mistake

Q20. Which example best represents professional practice involving Requirements Elicitation Components? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AMake undocumented changes whenever convenient.
  2. BExclude stakeholders to speed up requirements work.
  3. CUse personal preference instead of evidence and organizational objectives.
  4. DDocument objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Show answer
Answer: D. Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Components: Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Report a mistake

Q21. Which statement best describes Requirements Elicitation Modeling within Requirements Elicitation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt is only a collection of computers and excludes people and processes.
  2. BIt automatically creates business value whenever new technology is purchased.
  3. CIt can be designed without understanding organizational context.
  4. DIt should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Show answer
Answer: D. It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Report a mistake

Q22. What is the primary purpose of Requirements Elicitation Modeling in an information-systems environment? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt guarantees competitive advantage without organizational change.
  2. BIt supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
  3. CIts purpose is always to maximize the number of applications.
  4. DIt eliminates the need for business processes and management decisions.
Show answer
Answer: B. It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Report a mistake

Q23. An organization is working with Requirements Elicitation Modeling. Which approach is most appropriate? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. APurchase technology before identifying the business problem.
  2. BIgnore users because technical implementation alone determines success.
  3. CSkip outcome verification once the system is installed.
  4. DClarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Show answer
Answer: D. Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Report a mistake

Q24. Which consideration best supports alignment of Requirements Elicitation Modeling with organizational needs? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIgnore stakeholder and process requirements when technology is modern.
  2. BConnect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
  3. CChoose systems only because competitors use them.
  4. DMeasure alignment solely by the number of software licenses.
Show answer
Answer: B. Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Report a mistake

Q25. Which information or data consideration is most important when applying Requirements Elicitation Modeling? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ACollect all possible data regardless of relevance or governance.
  2. BAssume information is accurate because it is stored electronically.
  3. CIgnore timeliness and provenance when reports look professional.
  4. DEnsure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Show answer
Answer: D. Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Report a mistake

Q26. Which control or governance principle is most relevant to Requirements Elicitation Modeling? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ATreat accountability as unnecessary when tasks are automated.
  2. BUse clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
  3. CGive every user administrator access to reduce support requests.
  4. DAvoid audit trails so processes remain flexible.
Show answer
Answer: B. Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Report a mistake

Q27. How should an organization evaluate the effectiveness of Requirements Elicitation Modeling? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AMeasure only implementation cost and ignore outcomes.
  2. BAssume user adoption proves business value.
  3. CUse metrics unrelated to the original objective.
  4. DUse service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Show answer
Answer: D. Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Report a mistake

Q28. When changing a system involving Requirements Elicitation Modeling, what should be prioritized? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AModify many unrelated processes simultaneously without testing.
  2. BAssess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
  3. CChange production systems without impact analysis.
  4. DAvoid communicating changes to affected users.
Show answer
Answer: B. Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Report a mistake

Q29. Which trade-off should be assessed when selecting an approach to Requirements Elicitation Modeling? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AOnly acquisition price matters in every system decision.
  2. BIntegration and maintainability never affect enterprise systems.
  3. CAlways maximize technical complexity regardless of business value.
  4. DBalance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Show answer
Answer: D. Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Report a mistake

Q30. Which example best represents professional practice involving Requirements Elicitation Modeling? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AUse personal preference instead of evidence and organizational objectives.
  2. BDocument objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
  3. CMake undocumented changes whenever convenient.
  4. DExclude stakeholders to speed up requirements work.
Show answer
Answer: B. Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Modeling: Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Report a mistake

Q31. Which statement best describes Requirements Elicitation Evaluation within Requirements Elicitation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt can be designed without understanding organizational context.
  2. BIt should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
  3. CIt is only a collection of computers and excludes people and processes.
  4. DIt automatically creates business value whenever new technology is purchased.
Show answer
Answer: B. It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Report a mistake

Q32. What is the primary purpose of Requirements Elicitation Evaluation in an information-systems environment? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIts purpose is always to maximize the number of applications.
  2. BIt eliminates the need for business processes and management decisions.
  3. CIt guarantees competitive advantage without organizational change.
  4. DIt supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Show answer
Answer: D. It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Report a mistake

Q33. An organization is working with Requirements Elicitation Evaluation. Which approach is most appropriate? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ASkip outcome verification once the system is installed.
  2. BClarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
  3. CPurchase technology before identifying the business problem.
  4. DIgnore users because technical implementation alone determines success.
Show answer
Answer: B. Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Report a mistake

Q34. Which consideration best supports alignment of Requirements Elicitation Evaluation with organizational needs? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AChoose systems only because competitors use them.
  2. BMeasure alignment solely by the number of software licenses.
  3. CIgnore stakeholder and process requirements when technology is modern.
  4. DConnect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Show answer
Answer: D. Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Report a mistake

Q35. Which information or data consideration is most important when applying Requirements Elicitation Evaluation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIgnore timeliness and provenance when reports look professional.
  2. BEnsure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
  3. CCollect all possible data regardless of relevance or governance.
  4. DAssume information is accurate because it is stored electronically.
Show answer
Answer: B. Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Report a mistake

Q36. Which control or governance principle is most relevant to Requirements Elicitation Evaluation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AGive every user administrator access to reduce support requests.
  2. BAvoid audit trails so processes remain flexible.
  3. CTreat accountability as unnecessary when tasks are automated.
  4. DUse clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Show answer
Answer: D. Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Report a mistake

Q37. How should an organization evaluate the effectiveness of Requirements Elicitation Evaluation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AUse metrics unrelated to the original objective.
  2. BUse service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
  3. CMeasure only implementation cost and ignore outcomes.
  4. DAssume user adoption proves business value.
Show answer
Answer: B. Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Report a mistake

Q38. When changing a system involving Requirements Elicitation Evaluation, what should be prioritized? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AChange production systems without impact analysis.
  2. BAvoid communicating changes to affected users.
  3. CModify many unrelated processes simultaneously without testing.
  4. DAssess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Show answer
Answer: D. Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Report a mistake

Q39. Which trade-off should be assessed when selecting an approach to Requirements Elicitation Evaluation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AAlways maximize technical complexity regardless of business value.
  2. BBalance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
  3. COnly acquisition price matters in every system decision.
  4. DIntegration and maintainability never affect enterprise systems.
Show answer
Answer: B. Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Report a mistake

Q40. Which example best represents professional practice involving Requirements Elicitation Evaluation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AMake undocumented changes whenever convenient.
  2. BExclude stakeholders to speed up requirements work.
  3. CUse personal preference instead of evidence and organizational objectives.
  4. DDocument objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Show answer
Answer: D. Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Evaluation: Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Report a mistake

Q41. Which statement best describes Requirements Elicitation Applications within Requirements Elicitation? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt is only a collection of computers and excludes people and processes.
  2. BIt automatically creates business value whenever new technology is purchased.
  3. CIt can be designed without understanding organizational context.
  4. DIt should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Show answer
Answer: D. It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: It should be understood through its business purpose, information flows, people, processes, technology, and organizational context.
Report a mistake

Q42. What is the primary purpose of Requirements Elicitation Applications in an information-systems environment? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIt guarantees competitive advantage without organizational change.
  2. BIt supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
  3. CIts purpose is always to maximize the number of applications.
  4. DIt eliminates the need for business processes and management decisions.
Show answer
Answer: B. It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: It supports a defined organizational objective by improving information, coordination, control, service, or decision-making.
Report a mistake

Q43. An organization is working with Requirements Elicitation Applications. Which approach is most appropriate? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. APurchase technology before identifying the business problem.
  2. BIgnore users because technical implementation alone determines success.
  3. CSkip outcome verification once the system is installed.
  4. DClarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Show answer
Answer: D. Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Clarify business requirements and stakeholders, model the process and information needs, implement deliberately, and verify outcomes.
Report a mistake

Q44. Which consideration best supports alignment of Requirements Elicitation Applications with organizational needs? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AIgnore stakeholder and process requirements when technology is modern.
  2. BConnect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
  3. CChoose systems only because competitors use them.
  4. DMeasure alignment solely by the number of software licenses.
Show answer
Answer: B. Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Connect the system capability to measurable business objectives, stakeholder needs, processes, and governance requirements.
Report a mistake

Q45. Which information or data consideration is most important when applying Requirements Elicitation Applications? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ACollect all possible data regardless of relevance or governance.
  2. BAssume information is accurate because it is stored electronically.
  3. CIgnore timeliness and provenance when reports look professional.
  4. DEnsure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Show answer
Answer: D. Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Ensure information is relevant, accurate, timely, appropriately governed, and fit for the decisions or processes it supports.
Report a mistake

Q46. Which control or governance principle is most relevant to Requirements Elicitation Applications? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. ATreat accountability as unnecessary when tasks are automated.
  2. BUse clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
  3. CGive every user administrator access to reduce support requests.
  4. DAvoid audit trails so processes remain flexible.
Show answer
Answer: B. Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Use clear accountability, least necessary access, documented policies, traceability, and review proportional to risk.
Report a mistake

Q47. How should an organization evaluate the effectiveness of Requirements Elicitation Applications? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AMeasure only implementation cost and ignore outcomes.
  2. BAssume user adoption proves business value.
  3. CUse metrics unrelated to the original objective.
  4. DUse service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Show answer
Answer: D. Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Use service, process, user, information-quality, risk, and business-value measures tied to the stated objectives.
Report a mistake

Q48. When changing a system involving Requirements Elicitation Applications, what should be prioritized? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AModify many unrelated processes simultaneously without testing.
  2. BAssess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
  3. CChange production systems without impact analysis.
  4. DAvoid communicating changes to affected users.
Show answer
Answer: B. Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Assess dependencies and stakeholder impact, control the change, communicate it, test it, and confirm adoption and outcomes.
Report a mistake

Q49. Which trade-off should be assessed when selecting an approach to Requirements Elicitation Applications? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AOnly acquisition price matters in every system decision.
  2. BIntegration and maintainability never affect enterprise systems.
  3. CAlways maximize technical complexity regardless of business value.
  4. DBalance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Show answer
Answer: D. Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Balance business value with cost, usability, security, integration, scalability, maintainability, and organizational change.
Report a mistake

Q50. Which example best represents professional practice involving Requirements Elicitation Applications? Context: BS Information Systems / Systems Analysis & Design / Requirements Elicitation.

  1. AUse personal preference instead of evidence and organizational objectives.
  2. BDocument objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
  3. CMake undocumented changes whenever convenient.
  4. DExclude stakeholders to speed up requirements work.
Show answer
Answer: B. Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.Systems Analysis & Design → Requirements Elicitation → Requirements Elicitation Applications: Document objectives and decisions, involve relevant stakeholders, implement controlled changes, and retain evidence of results.
Report a mistake