This type of requirement is used to flow an upper-tier (parent) requirement topic to a lower-tier (child) specification when the System Engineer either does not understand how the requirement can (or should) be portioned between the subordinate (child) CI’s, or is afraid to commit under contract.
Requirements written in this form are essentially useless: either they are entirely unverifiable (having no actual meaning) or are highly contentious. Or, both.