Is an automated functionality is a Use Case?
<p>My questions is simple as that. (In the title)</p>

<p>Lets see this example:</p>

<p>An app has a functionality: </p>

<p>The user can schedule an event through an API from the app. This event schedules an <strong>alarm to be fired</strong> on the phone. So like a simple alarm clock scheduling pulled from a server.</p>

<p>Is the very <strong>function of "firing alarm"</strong> is a <strong>Use Case</strong>?</p>

<p>It is an automated routine that will happen without the interaction of the user. (If it is already scheduled ofc)</p>

<p>Do I have to add this "automated alarm firing" as a <strong>Use Case</strong> and link it to an <strong>Actor</strong> in my <strong>Use Case Diagram</strong>?</p>

<p>I know that scheduling an alarm is a Use Case, and also the removing or time modification both Use Cases, <strong>but how can I mark such an automated - no interaction needed function?</strong> </p>

<p>I mean <strong>it has to be a USAGE</strong> of the application it does something that the user can see (hear) and make a reaction to it like do another usage, another Use Case, right? Or maybe I'am wrong, </p>

<p>Please help if you can.</p>