<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="--tqPUXmxo3QaK9LmJ7FzHg" name="new_guideline,_yXWi4MVBEe65TabjuNR1iQ" guid="--tqPUXmxo3QaK9LmJ7FzHg">
  <mainDescription>&lt;p>&#xD;
    Model Problem &amp;amp; Solution domain.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    We insist on using UML class diagram to model structure of solution domain. Although we suggest this model for analysis&#xD;
    domain, but it is not necessary. but we should model structure in implementations.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    In analysis domain, we are not forcing team to model structure, but highly recommand it. In solution domain, it is&#xD;
    necessary.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
