OpenUP/OpenUP_SP/library/openup_basic/guidances/guidelines/example_analysis_mechanisms_descr.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="-CJ--jlBqXi3FzdOM_dw5_w" name="new_guideline,_V4qNUAn_Edu0OeEVPFogVA" guid="-CJ--jlBqXi3FzdOM_dw5_w" changeDate="2006-07-10T15:10:58.826-0700">
  <mainDescription>&lt;p&gt; The following shows how to capture information for &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;file:///c|/documents%20and%20settings/rbalduino/my%20documents/tng/beacon/copyedit/structure_for_importing/openup_basic/openup_basic/guidances/concepts/analysis_mechanism,_0gvqomlgedmt3adzl5dmdw.html&quot;
    guid=&quot;_0gvqoMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Analysis Mechanism&lt;/a&gt;. &lt;/p&gt;
&lt;h3&gt; Persistence &lt;/h3&gt;
&lt;p&gt;For all classes with instances that may become persistent, you need to identify: 
  
&lt;ul&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Granularity&lt;/b&gt;&lt;strong&gt;:&lt;/strong&gt; What is the range of size of the objects 
      to keep persistent?&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Volume&lt;/b&gt;&lt;strong&gt;: &lt;/strong&gt;How many objects (number) do you need to 
      keep persistent?&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Duration&lt;/b&gt;&lt;strong&gt;:&lt;/strong&gt; How long does the object typically need 
      to be kept?&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Retrieval mechanism&lt;/b&gt;&lt;strong&gt;: &lt;/strong&gt;How is a given object uniquely 
      identified and retrieved? &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Update frequency&lt;/b&gt;&lt;strong&gt;: &lt;/strong&gt;Are the objects more or less 
      constant? Are they permanently updated? &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Reliability&lt;/b&gt;&lt;strong&gt;: &lt;/strong&gt;Do the objects need to survive a crash 
      of the process, the processor, or the whole system? &lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Communication &lt;/h3&gt;
&lt;p&gt;For all model elements that need 
  to communicate with components or services that are running in other processes 
  or threads, you need to identify &lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Latency&lt;/b&gt;&lt;strong&gt;: &lt;/strong&gt;How 
      fast must processes communicate with another? &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Synchronicity&lt;/b&gt;&lt;strong&gt;: 
      &lt;/strong&gt;Asynchronous communication. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;b&gt;Size of message&lt;/b&gt;&lt;strong&gt;: 
      &lt;/strong&gt;A spectrum might be more appropriate than a single number. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;&lt;strong&gt;Protocol:&lt;/strong&gt; Flow control, buffering, 
      and so on.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; Notice that there is no design-level 
  information or specification here. Instead, this is more about collating and 
  refining architecturally significant requirements. &lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>