blob: 46b23af0c229583bc7a1ae98bdba953eef89f842 [file] [log] [blame]
<?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\analyze_arch_reqs_vm.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: analyze_arch_reqs_vm.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-I-2SvZtjELUYDQO0jvdxEA CRC: 3143792575 --><h4>
Capture architectural decisions (Visual Modeling)
</h4>
<p>
You will find it useful to develop these three Unified Modeling Language (UML) diagrams at this stage:
</p>
<ul>
<li>
<strong>Layer map</strong> (represented as a class diagram using packages) that describes the upper-level layers of
the architecture
</li>
<li>
<strong>Draft deployment diagram</strong> that outlines the&nbsp;expected network topology
</li>
<li>
<strong>Simple class diagram</strong> that shows the key abstractions and any obvious relationships among them
</li>
</ul><!-- END:mainDescription,-I-2SvZtjELUYDQO0jvdxEA -->
</body>
</html>