MEDIUM

Your project report should be a single document that includes UML diagrams in it$.$

Diagramming standard is UML $2\mathrm{.}0.$

PROBLEM

Your project should deliver the requirements model for a problem you have selected. The model includes $3$ types of diagrams

Use Case, Class, and Sequence

and textual specifications for the Scenarios $($Pseudo$-$code $-$ could be in tabular format$).$

$1-$ Draw the complete Use$-$Case Diagram$($s$)$

$2-$ Select $3$ most important use$-$cases and:

a$.$ Write Scenarios for each $($one scenario per use$-$case is sufficient, could be

more$)$

b$.$ For each scenario, draw a Sequence Diagram.

$3-$ Draw the Class Diagram$($s$)$ for the whole system

You can include minimal explanations. A specific report format is not necessary, however, your organization should be nice. Every item $($diagram$,$ scenario, etc.$)$ should have a title$/$caption$.$

REMINDERS for GRADING

$$ Title should correspond to model items with exact spelling $($case sensitive etc.$)$ as if they are $$variable$$ names in programming.

$$ Scenarios and corresponding sequence diagrams should carry a title$/$caption with the corresponding use$-$case name.

$$ A class name $($etc$.)$ should be spelled the same in different diagrams.

$$ Every activity $($instruction$)$ in the scenarios should correspond to at least one message in the sequence diagrams.

$$ Every message in the sequence diagrams should correspond to a method in the class diagram: with the exact same naming and at the correct class $($receiver$)$