| <?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" epf:version="1.0.0" xmi:id="-QRnsN2e6IQlSMaRts-wFNw" name="new_custom_category,_57_ZMEmbEdu0xduwSKie-w" guid="-QRnsN2e6IQlSMaRts-wFNw" changeDate="2006-09-29T14:16:21.596-0400" version="1.0.0"> |
| <mainDescription><p> |
| The intent sub-process deals with how to channel the intent of stakeholders to the rest of the development team, to |
| ensure that validated builds with incremental capabilities reflect stakeholder intents. This is done by capturing and |
| communicating the <a class="elementLinkWithUserText" href="./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">vision</a>&nbsp;to all team members, and by translating the vision into test cases and |
| requirements of different types to allow the team to understand what capabilities needs to be delivered to address |
| stakeholder intent. |
| </p> |
| <p> |
| You find the most tasks for the intent sub-process in the <strong>Requirements</strong> discipline, and the task Create |
| Test Cases in the <strong>Test</strong> discipline. The corresponding work products are found under |
| <strong>Requirements</strong> and <strong>Test</strong> domains. |
| </p> |
| <p> |
| The intent sub-process is built upon the foundational <a class="elementLink" href="./../../openup_basic/customcategories/collab_commun_subprocess,_r8cVIEmbEdu0xduwSKie-w.html" guid="_r8cVIEmbEdu0xduwSKie-w">Collaboration and Communication</a><a class="elementLinkWithUserText" href="./../../openup_basic/customcategories/collab_commun_subprocess,_r8cVIEmbEdu0xduwSKie-w.html" guid="_r8cVIEmbEdu0xduwSKie-w">&nbsp;</a>layer. That layer constitutes the backbone of OpenUP in order to reflect the |
| following: |
| </p> |
| <ul> |
| <li> |
| all roles in OpenUP are involved in intent development to ensure that as a minimum, all team members properly |
| understand stakeholders’ intent. |
| </li> |
| <li> |
| make sure that the best practices for collaborative development provided in the collaboration layer guides any work |
| related to intent. |
| </li> |
| </ul> |
| <p> |
| The intent sub-process is written in such a way that your organization can modify it to fit your style of development |
| and stakeholder collaboration, without necessarily impacting how you deal with the other sub-processes of <a class="elementLink" href="./../../openup_basic/customcategories/management_subprocess,_Aoz2gEmcEdu0xduwSKie-w.html" guid="_Aoz2gEmcEdu0xduwSKie-w">Management</a><a class="elementLinkWithUserText" href="./../../openup_basic/customcategories/management_subprocess,_Aoz2gEmcEdu0xduwSKie-w.html" guid="_Aoz2gEmcEdu0xduwSKie-w">&nbsp;</a>and <a class="elementLink" href="./../../openup_basic/customcategories/solution_subprocess,_HEVvgEmcEdu0xduwSKie-w.html" guid="_HEVvgEmcEdu0xduwSKie-w">Solution</a><a class="elementLinkWithUserText" href="./../../openup_basic/customcategories/solution_subprocess,_HEVvgEmcEdu0xduwSKie-w.html" guid="_HEVvgEmcEdu0xduwSKie-w">&nbsp;</a>development . |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |