Further develop the application scenario you chose in task $1$ and complete the

following subtasks:

a$)$ Create a context diagram with the essential entities and data flows.

b$)$ Create a use case diagram with at least $3$ actors and $5$ use cases.

c$)$ Select a non$-$trivial use case and create a use case specification for

it$.$ In addition to the main scenario, describe at least $1$ alternative and $1$

exception scenario.

d$)$ Create an analytical class diagram that represents the essential connections of

your application world. Implementation$-$related details such as visibility

and navigation directions are not required.

Make sensible use of the possibilities of UML $($e$.$g$.$ inheritance, include$/$

extend relationships, aggregation, $...)$ and adhere to its syntax rules.

The solution should meaningfully develop your own solution to the previous task. For example,

stakeholders and requirements from task $1$ can become actors and use cases here. As long

as this connection is clearly visible, your diagrams do not need any written explanations.

However, if you deviate from the previous solution $($for example because it does

not provide a good basis for the new task$),$ explain this briefly.