title: Should access to properties of other classes through association be made explicit or are they implicit?
body: <p>I'm working on a project where I'm using an SDK that provides things I need via some classes. I've named these <code>ProviderProvider</code> and <code>Provider</code>, that grant access to <code>OneThing</code> that is an <code>IThing</code>.<br>
  An example is shown here</p>
  
  <p><img src="https://i.stack.imgur.com/sQAyB.png" alt="shown here">.</p>
  
  <p>My question is: What is the correct (or best) way to show that the <code>Model</code> provides the list of <code>OneThing</code>s to the <code>View</code> through those classes?</p>
  
  <ol>
  <li>Do you show this explicitly as in my example, by drawing a dependency arrow from <code>Model</code> to <code>OneThing</code>? That doesn't seem right to me and quickly becomes visually cluttered.</li>
  <li>Do you not explicitly define that relationship, but is it simply implicitly defined through the other relationships?</li>
  <li>Do you define that relationship semi-explicitly through attributes, notes or some other way?</li>
  </ol>
  
  <p>What relations and attributes should I add/remove specifically and why?</p>