Question: How can you explain the statement Implicit requirements can also be unknown unknowns? There are matters that should be , but are not, elicited through
How can you explain the statement "Implicit requirements can also be unknown unknowns"?
There are matters that should be but are not, elicited through the elicitation process. They exist, but they are not realized. This includes issues such as security requirements.
During the SRS process, customers should always be required to spell out their unknown unknowns.
An unknown unknown cannot be known and therefore we can not make them explicit requirements.
Step by Step Solution
There are 3 Steps involved in it
1 Expert Approved Answer
Step: 1 Unlock
Question Has Been Solved by an Expert!
Get step-by-step solutions from verified subject matter experts
Step: 2 Unlock
Step: 3 Unlock
