It’s brevity that I’m after, as these will be labels on columns, or buttons, or total boxes - and so on - there is a need for a really concise term for the function that is being performed.
It’s to be an all-purpose system for embodying a large set of inter-related technical roadmaps, managed changes, resource and cost budgets, and organisational constraints and requirements.
All of these relationships can be anything from extremely specific (System X requires version Y of supporting technology Z to be implemented no earlier than date P and no later than date Q), or quite general/categorised (this planned process has potential impact on all objects that are in a category ‘extended operating hours’).
I’ve more or less got a design in mind for managing the structure of all this information; this is just about finding a memorable, logical terminology for it.
I see. I was thinking in terms of wording for a system design document. But simplicity is still your friend; both concepts you describe and that I quoted from the Microsoft example can be described in a single word, both rooted in “depend”…
“the following system components depend on this service” lists dependents.
“this service depends on the following system components” lists dependencies.