| <?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\delivery_process.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: delivery_process.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_EhgqwO8MEdmKSqa_gSYthg CRC: 569468565 -->Delivery Process<!-- END:presentationName,_EhgqwO8MEdmKSqa_gSYthg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_EhgqwO8MEdmKSqa_gSYthg CRC: 2532782997 -->A Delivery Process is a special Process describing a complete and integrated approach for performing a specific type of project.<!-- END:briefDescription,_EhgqwO8MEdmKSqa_gSYthg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_EijzoO8MEdmKSqa_gSYthg CRC: 951789511 --><p> |
| A Delivery Process is a special <a class="elementLink" |
| href="./../../../base_concepts/guidances/termdefinitions/process,_yQ5m2NnmEdmO6L4XMImrsA.html" |
| guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a> describing a complete and integrated approach for performing a specific |
| project type. <!--StartFragment-->It provides a complete lifecycle model that has been detailed by sequencing Method |
| Content in breakdown structures. It describes a complete project lifecycle end-to-end and is used as a reference for |
| running projects with similar characteristics. |
| </p> |
| <p> |
| A process engineer can define alternative Delivery Processes for software development projects that differ in the |
| scale of the engagement and staffing necessary, the type of the software application to be developed, the development |
| methods and technologies to be used, etc. Although, the Delivery Process aims to cover a whole project it keeps certain |
| decision that are too project specific open. For example, the breakdown structure defines which Breakdown |
| Elements have multiple occurrences or are repeatable via its specific attributes, but does not say how many occurrences |
| and how many repeats/iterations it will have. These decisions have to be done by a project manager when planning |
| a concrete project, project phase, or project iterations.<!--EndFragment--> |
| </p> |
| <h3> |
| <a id="Software Engineering Process" name="Software Engineering Process">Example</a> |
| </h3> |
| <p> |
| In software engineering, the goal is to build a software product or to enhance an existing one. The Delivery Process |
| for software could be an iterative process, where the product is built incrementally over time, or it could be a |
| traditional waterfall Delivery Process in which all requirements are specified up front, followed by design, |
| implementation, and test phases. |
| </p><!-- END:mainDescription,_EijzoO8MEdmKSqa_gSYthg --> |
| </body> |
| </html> |
