| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription 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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-kQg7MSGPB3RPjrplyxwimQ" |
| name="uc_model,_W2SgEDR5EdutE_HNDTJk5Q" guid="-kQg7MSGPB3RPjrplyxwimQ" changeDate="2008-08-14T12:30:35.711-0400" |
| version="1.0.0"> |
| <purpose><p> |
| This artifact presents an overview of the system's intended behavior.&nbsp;It&nbsp;is the basis for agreement |
| between&nbsp;stakeholders and the project team regarding the intended functionality for the system. It also helps to |
| guide the various tasks in the software development lifecycle. |
| </p></purpose> |
| <impactOfNotHaving>Without this artifact it will be more difficult to determine all of the relationships between actors and use cases as well
 |
| gain an understanding of how the different use cases relate to each other.</impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| If the overall set of use cases is fairly small with no complex relationships between them then this artifact may not
 |
| be required.&nbsp;&nbsp;
 |
| </p>
 |
| <p>
 |
| If an alternative approach is being used to document functional requirements then this artifact is not needed.
 |
| </p></reasonsForNotNeeding> |
| <representationOptions><p>
 |
| Representation options include: reports and diagrams from UML modeling tools, graphical representations created using
 |
| drawing tools, drawings on whiteboards. Most of the information in the use-case model is captured in the use-case
 |
| specifications.
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
