| <?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>openup&#92;guidances&#92;supportingmaterials&#92;&#92;who_should_use_openup.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: who_should_use_openup.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_L6THwDY_EdyTZ9G7ByfQTw CRC: 1713881058 -->Who Should Use OpenUP<!-- END:presentationName,_L6THwDY_EdyTZ9G7ByfQTw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_L6THwDY_EdyTZ9G7ByfQTw CRC: 979984621 -->This supporting material explains who should use OpenUP.<!-- END:briefDescription,_L6THwDY_EdyTZ9G7ByfQTw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-1nEIK4O3laIt539DV6rQzA CRC: 889089999 --><p> |
| OpenUP is most useful for four primary groups of users: |
| </p> |
| <ul> |
| <li> |
| Software development practitioners (developers, project managers, analysts, and testers) working together as a |
| project team |
| </li> |
| <li> |
| Stakeholders |
| </li> |
| <li> |
| Software process engineers |
| </li> |
| <li> |
| Instructors |
| </li> |
| </ul> |
| <p> |
| Software development practitioners can find guidance on what is required of them in the roles defined by OpenUP. Each |
| role describes a set of activities and artifacts for which the role is responsible. Guidance is also given on how those |
| roles collaborate. |
| </p> |
| <p> |
| Stakeholders will find guidance on what they may expect from the software development team, and how the software will |
| be created. OpenUP also describes the stakeholders' responsibilities, and states how they can best work with the |
| development team to obtain software that meets their needs. |
| </p> |
| <p> |
| Software process engineers can use EPF Composer to extend and modify OpenUP. Modification may be as simple as altering |
| templates for work products, or as sophisticated as adding activities necessary for creating software in your specific |
| environment (such as audits for safety-critical systems). In addition to modifying method content, process engineers |
| can add, change, or remove process flows to add organization-specific capability patterns. |
| </p> |
| <p> |
| OpenUP is appropriate for academic organizations also. As an open source process, it can serve as the basis for |
| software engineering courses and, when combined with the EPF Composer, courses in software process engineering.<br /> |
| </p><br /><!-- END:mainDescription,-1nEIK4O3laIt539DV6rQzA --> |
| </body> |
| </html> |
