There is requirements specification which has certain Completeness properties:
- No "To be done" phrases
- No references to non-existing items
- No missing items
- No missing functions
- No missing products
The first two of these properties form a subset of the completeness properties which are called "closure" properties.
I am trying to understand why is that? The only thing I can think of is that these "work" with the existing items and are known (I could count the number of TBDs or wrong references), while I cannot know whether something is missing. Am I on the right track?