# Dependencies - looking for the right word

**URL:** <https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612>\
**Category:** Factual Questions\
**Created:** [January 24, 2014, 3:00pm UTC](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612 "2014-01-24T15:00:45Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Mangetout](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mangetout/32/19_2.png) [@Mangetout](https://boards.straightdope.com/u/Mangetout)\
**Post date:** [January 24, 2014, 11:25pm UTC](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612/21 "2014-01-24T23:25:26Z")

</div>

> [@wolfpup](#):
>
> Not really sure what you’re trying to say with regard to a “new instance of A”, but I would translate that sentence along the lines of: if there is a new instance of A (say, one with different interfaces), then obviously all its dependent components are affected. Sometimes simple language leads to greatest clarity, even if more words are involved.

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.

---

<div class="post-metadata">

**Author:** ![Topologist](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/topologist/32/3208_2.png) [@Topologist](https://boards.straightdope.com/u/Topologist)\
**Post date:** [January 25, 2014, 1:02am UTC](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612/22 "2014-01-25T01:02:38Z")

</div>

How about “is necessary for”?

B is dependent upon A.  
A is necessary for B.

---

<div class="post-metadata">

**Author:** ![randompattern](https://avatars.discourse-cdn.com/v4/letter/r/7993a0/32.png) [@randompattern](https://boards.straightdope.com/u/randompattern)\
**Post date:** [January 25, 2014, 1:13am UTC](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612/23 "2014-01-25T01:13:34Z")

</div>

Indentured ?

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [January 25, 2014, 3:18am UTC](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612/24 "2014-01-25T03:18:40Z")

</div>

> [@Mangetout](#):
>
> 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.

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**.

[Previous page](https://boards.straightdope.com/t/dependencies-looking-for-the-right-word/679612.md?page=1)