<?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="-aN0zy068ovKHgmkkoYqoYQ" name=",_zGqO0MDpEduTGJ8i4u8TMw" guid="-aN0zy068ovKHgmkkoYqoYQ" changeDate="2007-02-20T08:56:57.450-0500">
  <mainDescription>&lt;p&gt;
    To fully understand the system's purpose, you must know who the system is for, that is: Who will use the system? The
    answer to this question is: the Actors.
&lt;/p&gt;
&lt;p&gt;
    An Actor is a role that a person or external system plays&amp;nbsp;when interacting with the system.&amp;nbsp; Instances of an
    Actor can be an individual or an external system, however each Actor&amp;nbsp;provides a
    unique&amp;nbsp;and&amp;nbsp;important&amp;nbsp;perspective on the system that is shared by every instance of the Actor.
&lt;/p&gt;
&lt;p&gt;
    This difference between an actor and an instance of an actor is illustrated below.&amp;nbsp;&amp;nbsp;Figure 1 shows a case in
    which Ivar and Mark are operators of a recycling machine. When they are using the machine in this capacity, each is
    represented by an instance of the actor called Operator that expects certain functionality of the system (Print Daily
    Reports in this example).
&lt;/p&gt;
&lt;p&gt;
    &lt;img height=&quot;322&quot; alt=&quot;&quot; src=&quot;./resources/md_acto2.gif&quot; width=&quot;396&quot; /&gt;&amp;nbsp;
&lt;/p&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    &lt;p&gt;
        &lt;strong&gt;Figure 1:&amp;nbsp;Example Actor with multiple instances&lt;/strong&gt;&amp;nbsp;
    &lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
    Conversely, the same user can act as several actors (that is, the same person can take on different roles). In Figure
    2, Charlie uses the Depot-Handling System primarily as Depot Manager, but sometimes he also uses the Depot-Handling
    System as an ordinary Depot Staff member. Each of these actors expects different functionality of the system.
&lt;/p&gt;
&lt;p&gt;
    &lt;img height=&quot;139&quot; alt=&quot;&quot; src=&quot;./resources/md_acto3.gif&quot; width=&quot;367&quot; /&gt;
&lt;/p&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    &lt;p&gt;
        &lt;strong&gt;Figure 2: Example of user playing different roles&lt;/strong&gt;&lt;br /&gt;
    &lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
    Actors help you to identify external interfaces and to determine the scope the system (what is in the system, vs. what
    is outside the system boundary).&amp;nbsp; Each&amp;nbsp;Actor has associated use cases which describe what that
    particular&amp;nbsp;actor expects of the system.&amp;nbsp; It will be very difficult, if not impossible,&amp;nbsp;to assess the
    completeness of the set of Use Cases without the context provided by the associated Actors. Furthermore, missing an
    actor may result in&amp;nbsp;missing important stakeholder perspectives, resulting&amp;nbsp;in a solution that does not meet
    all&amp;nbsp;stakeholder needs.
&lt;/p&gt;
&lt;p&gt;
    Hence, identifying the Actors for the system&amp;nbsp;should be done early in the lifecycle.&amp;nbsp;&amp;nbsp;Actors are
    captured, including their names, brief descriptions, and relationships to use cases,&amp;nbsp;in the &lt;a
    class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup_basic/workproducts/uc_model,_W2SgEDR5EdutE_HNDTJk5Q.html&quot;
    guid=&quot;_W2SgEDR5EdutE_HNDTJk5Q&quot;&gt;Artifact: Use-Case Model&lt;/a&gt;.
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>