| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\guidances\guidelines\example_analysis_mechanisms_descr.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: example_analysis_mechanisms_descr.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_4k_HsA4LEduibvKwrGxWxA CRC: 1738380325 -->Example Analysis Mechanism Descriptions<!-- END:presentationName,_4k_HsA4LEduibvKwrGxWxA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_4k_HsA4LEduibvKwrGxWxA CRC: 2073113338 -->Examples showing how to describe Analysis Mechanisms<!-- END:briefDescription,_4k_HsA4LEduibvKwrGxWxA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-CJ--jlBqXi3FzdOM_dw5_w CRC: 3244605955 --><p> The following shows how to capture information for <a class="elementLinkWithType" |
| href="file:///c|/documents%20and%20settings/rbalduino/my%20documents/tng/beacon/copyedit/structure_for_importing/openup_basic/openup_basic/guidances/concepts/analysis_mechanism,_0gvqomlgedmt3adzl5dmdw.html" |
| guid="_0gvqoMlgEdmt3adZL5Dmdw">Concept: Analysis Mechanism</a>. </p> |
| <h3> Persistence </h3> |
| <p>For all classes with instances that may become persistent, you need to identify: |
| |
| <ul> |
| <li> |
| <p><b>Granularity</b><strong>:</strong> What is the range of size of the objects |
| to keep persistent?</p> |
| </li> |
| <li> |
| <p><b>Volume</b><strong>: </strong>How many objects (number) do you need to |
| keep persistent?</p> |
| </li> |
| <li> |
| <p><b>Duration</b><strong>:</strong> How long does the object typically need |
| to be kept?</p> |
| </li> |
| <li> |
| <p><b>Retrieval mechanism</b><strong>: </strong>How is a given object uniquely |
| identified and retrieved? </p> |
| </li> |
| <li> |
| <p><b>Update frequency</b><strong>: </strong>Are the objects more or less |
| constant? Are they permanently updated? </p> |
| </li> |
| <li> |
| <p><b>Reliability</b><strong>: </strong>Do the objects need to survive a crash |
| of the process, the processor, or the whole system? </li> |
| </ul> |
| <h3>Communication </h3> |
| <p>For all model elements that need |
| to communicate with components or services that are running in other processes |
| or threads, you need to identify </p> |
| <ul> |
| <li> |
| <p><b>Latency</b><strong>: </strong>How |
| fast must processes communicate with another? </p> |
| </li> |
| <li> |
| <p><b>Synchronicity</b><strong>: |
| </strong>Asynchronous communication. </p> |
| </li> |
| <li> |
| <p><b>Size of message</b><strong>: |
| </strong>A spectrum might be more appropriate than a single number. </p> |
| </li> |
| <li> |
| <p><strong>Protocol:</strong> Flow control, buffering, |
| and so on.</p> |
| </li> |
| </ul> |
| <p> Notice that there is no design-level |
| information or specification here. Instead, this is more about collating and |
| refining architecturally significant requirements. </p><!-- END:mainDescription,-CJ--jlBqXi3FzdOM_dw5_w --> |
| </body> |
| </html> |
