Poor software characteristics are
-
Only Project Risks
-
Only Product Risks
-
Project Risks and Product Risks
-
Project Risks or Product Risks
According to ISTQB risk categorization, poor software characteristics like poor performance, poor usability, or poor security are classified as Product Risks. Product risks are risks that the software will not meet its quality characteristics. Project Risks are different - they're about schedule, budget, resources, and organizational issues. Options A, C, D are incorrect because poor software quality is specifically a product risk, not a project risk.
To answer this question, we need to understand the characteristics of poor software.
Option A) Only Project Risks - This option is incorrect. Poor software characteristics are not limited to project risks alone. There are other factors that contribute to poor software.
Option B) Only Product Risks - This option is correct. Poor software characteristics primarily refer to risks or issues related to the product itself. This can include bugs, crashes, security vulnerabilities, poor performance, and usability issues.
Option C) Project Risks and Product Risks - This option is incorrect. While project risks can contribute to poor software, the main focus is on the product itself.
Option D) Project Risks or Product Risks - This option is incorrect. Poor software characteristics typically refer to product risks, but it doesn't exclude the possibility of project risks contributing to poor software as well.
The correct answer is B) Only Product Risks. This option is correct because poor software characteristics primarily refer to risks or issues related to the product itself.