| <?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>\base_concepts\guidances\concepts\phase.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: phase.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,__7xOEC7aEdqHMdmRzC0-2g CRC: 1887238607 -->Phase<!-- END:presentationName,__7xOEC7aEdqHMdmRzC0-2g --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,__7xOEC7aEdqHMdmRzC0-2g CRC: 924176065 -->This guidance introduces the concept of a phase and its purpose within a project.<!-- END:briefDescription,__7xOEC7aEdqHMdmRzC0-2g --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-bhzuf6RMHP3d-AHkoKDg7g CRC: 848605003 --><h3> |
| What is a Phase? |
| </h3> |
| <p> |
| While the entire purpose of a project is to produce a product, the specific goals of the team will vary substantially |
| throughout the project. In the beginning, there usually is considerable latitude in the requirements for the product. |
| It may not be clear whether the project is feasible or even if it is likely to be profitable. At that time, it is |
| critical to bring an answer to these questions, and of little to no value to start developing the product in |
| earnest. Towards the end of the project, the product itself is usually complete, and issues of quality, delivery, |
| and completeness then take center stage. At different points in time, tasks are undertaken in new ways and work |
| products will have new content. |
| </p> |
| <p> |
| To coordinate the team’s efforts in a manner that takes these fundamental observations into account, the project |
| lifecycle should be divided into a sequence of phases. Each phase has a defined set of goals, its own iteration style |
| and customized <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/concepts/task,7.624729048911575E-305.html" |
| guid="7.624729048911575E-305">tasks</a> and <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/concepts/work_product,4.804531471620803E-306.html" |
| guid="4.804531471620803E-306">work products</a> to address the unique needs of the project at that point in time. |
| </p> |
| <p> |
| We recommend dividing the project lifecycle into four phases: Inception, Elaboration, Construction and |
| Transition. |
| </p> |
| <h3> |
| Iteration and Phases |
| </h3> |
| <p> |
| Each phase is divided into iterations. An iteration is a complete development loop resulting in a build (internal or |
| external) of an executable system, usually a subset of the final product under development, which grows incrementally |
| from iteration to iteration to become the final product.<br /> |
| </p><!-- END:mainDescription,-bhzuf6RMHP3d-AHkoKDg7g --> |
| </body> |
| </html> |
