The following shows how to capture information for &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/arch_mech_2932DFB6.html&quot; guid=&quot;_mzxI0A4LEduibvKwrGxWxA&quot;>Architectural Mechanism&lt;/a>s. This example shows two possible mechanisms: Persistence and Communication.&#xD;

&lt;/p>&#xD;

&lt;h3>&#xD;

Persistence&#xD;

&lt;/h3>&#xD;

&lt;p>&#xD;

For all classes with instances that may become persistent, you need to identify:&#xD;

&lt;/p>&#xD;

&lt;ul>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Granularity&lt;/b>&lt;b>:&lt;/b> What is the range of size of the objects to keep persistent?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Volume&lt;/b>&lt;b>:&lt;/b> How many objects (number) do you need to keep persistent?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Duration&lt;/b>&lt;b>:&lt;/b> How long does the object typically need to be kept?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Retrieval mechanism&lt;/b>&lt;b>:&lt;/b> How is a given object uniquely identified and retrieved?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Update frequency&lt;/b>&lt;b>:&lt;/b> Are the objects more or less constant? Are they permanently updated?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Reliability&lt;/b>&lt;b>:&lt;/b> Do the objects need to survive a crash of the process, the processor, or&#xD;

the whole system?&#xD;

&lt;/p>&#xD;

&lt;/li>&#xD;

&lt;/ul>&#xD;

&lt;h3>&#xD;

Communication&#xD;

&lt;/h3>&#xD;

&lt;p>&#xD;

For all model elements that need to communicate with components or services that are running in other processes or&#xD;

threads, you need to identify:&#xD;

&lt;/p>&#xD;

&lt;ul>&#xD;

&lt;li>&#xD;

&lt;p>&#xD;

&lt;b>Latency&lt;/b>&lt;b>:&lt;/b> How fast must processes communicate with another?&#xD;