A requirement where the measure(s) can (and should) be apportioned between the allocation target’s constituent parts. A non-allocable requirement must be passed to the subordinate parts in its entirety. This term disappeared somewhere in the late 1980’s, probably because it was too easily confused with the concept of “requirement allocation”. That was too bad, because it helped avoid “…shall support…” requirements in subordinate CI’s.
The classic example of an “allocable requirement” is a requirement for maximum weight, which can be subdivided into the weights of constituent parts. Many timing requirements can be similarly subdivided.