Develop System Requirements ISSEP Practice Questions (Page 4)

Questions 16–17

1. 16application · medium

   A system engineer is reviewing the security requirements for a new financial trading platform. She notices that one requirement states 'the system shall protect all data' but does not specify which data, from whom, or for how long. She also finds that this requirement cannot be traced to any specific business objective. What is the most appropriate action?

   • AAccept the requirement as is because it is broad enough to cover all data.
   • BRewrite the requirement to be specific, measurable, and traceable to a business objective.
   • CRemove the requirement because it is too vague to be useful.
   • DAdd a note that the requirement is understood and move on.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A project team is developing a new inventory management system. The security requirements baseline has been created, but during a review, a stakeholder points out that one requirement is not feasible with the current budget. What should the team do?

   • ARemove the requirement entirely to avoid budget issues.
   • BKeep the requirement as is and request additional funding later.
   • CIgnore the stakeholder's concern because the baseline is already approved.
   • DRevise the requirement to align with budget constraints and document the change.
   Reveal Solution Discussion Select an answer first