| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-Vvu-cdC2cq5fpcrKGNE3fw" |
| name="developing_a_method_proof_of_concept,_dEp88AqQEd2ffKRm_DXTyQ" guid="-Vvu-cdC2cq5fpcrKGNE3fw" |
| changeDate="2008-10-14T08:29:48.515-0700" version="7.2.0"> |
| <mainDescription><p>
 |
| The proof-of-concept of a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/method_DEA76035.html"
 |
| guid="_VFAQwAw7Ed2Dzp6jX9I91Q">method</a>&nbsp;should be done using the implementation environment you plan to use to
 |
| author the actual method. That way you can test the technical feasibility of your architectural ideas in the actual
 |
| implementation environment.
 |
| </p>
 |
| <p>
 |
| The following are some things that you may want to test out:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Your proposed library structure, including the types of plug-ins you are considering creating, their relationships
 |
| and the types of configurations you are considering creating.
 |
| </li>
 |
| <li>
 |
| Strategy for defining navigation views, identifying any common navigation elements that you may want to share
 |
| between views and configurations
 |
| </li>
 |
| <li>
 |
| Strategy for handling copyrights and release information
 |
| </li>
 |
| <li>
 |
| and so on.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| As you develop the proof-of-concept, it is important to document any issues and risks that you encounter so that these
 |
| can be addressed when more formally defining the method.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
