$1.$ Write a scenario for the "withdraw" usecase given in the use case diagram below.

$2.$ create a UML class diagram $($or write code in any language for only declaring classes $/$ equivalent to a class diagram with attributes and methods.

Notes: Diagram can be hand$-$drawn $($neatly$).$ Any tool to draw is better: suggested: starUML. If you prefer to

submit code, try to include $$relations $($UML Associations$)$ in the diagram or in the form of $$pointers $($if using

Java, provide a variable$/$object as an attribute$)$ with a meaningful name. Your scenario should be around half

a page long $($this is not a limitation$,$ just to give you an idea$).$ Remember: you can have if$/$goto or loop kind of

structures in y scenario as a pseudo$-$code format, as we do in algorithm design.