CSSLP · Question #372
Why are system requirements regarded as primary project artifacts when beginning software work?
The correct answer is B. They define the operations and behaviors the application must perform. System requirements are foundational documents for any software project because they precisely articulate what the software needs to accomplish from a functional and non-functional perspective. These requirements guide all subsequent design, development, and testing activities.
Question
Why are system requirements regarded as primary project artifacts when beginning software work?
Options
- ACloud Security Command Center
- BThey define the operations and behaviors the application must perform
- CThey describe the adversarial and operational environment that could affect the application
- DThey prescribe the implementation techniques and development steps to be used
How the community answered
(32 responses)- A3% (1)
- B88% (28)
- C3% (1)
- D6% (2)
Why each option
System requirements are foundational documents for any software project because they precisely articulate what the software needs to accomplish from a functional and non-functional perspective. These requirements guide all subsequent design, development, and testing activities.
Cloud Security Command Center is a specific security management service (e.g., Google Cloud's product) and is irrelevant to the general concept of system requirements as project artifacts.
System requirements are primary project artifacts because they precisely define the specific operations, functions, and behaviors that the software application must perform to meet user needs and business objectives. They serve as the baseline for all development, design, and testing efforts.
Describing the adversarial and operational environment is typically part of threat modeling or a risk assessment, which informs security requirements, but it is not the core definition of system requirements themselves.
Prescribing implementation techniques and development steps falls under system design and architecture, not the initial system requirements which focus on what the system should do, not how.
Concept tested: Software system requirements
Topics
Community Discussion
No community discussion yet for this question.