Description You will now be analyzing the desired behavior for the software system Gmail. You will do this by creating 3 UML diagrams: an Activity Diagram, a Sequence Diagram, and a Statechart Diagram. These diagrams needn't describe the entire functionality of the system, but should contain sufficient detail to demonstrate your knowledge of the three diagram types, and your ability to accurately represent an existing system Submit . The name and brief (2 to 3 sentence) description of the software system . One (1) Activity Diagram showing a set of activities that are part of using your selected software system. You will need to include multiple decision/merge points, at least one use of fork/join control, and must structure your diagram using swimlanes . One (1) Sequence Diagram showing the interactions of using your selected system through a number. of steps. You will need to include multiple message types (at least 4), at least 4 total objects (can include user/actor), and some use of looping . One (1) Statechart Diagram demonstrating the high-level states that your system can take during its usage, and the transitions between them. You will need to include the use of the following Statechart features: hierarchical states, transitions with triggers, guards, and resulting actions (as long.as all are sufficiently demonstrated), at least two concurrent statecharts, a history state, and at least one of each parent and child transitions Grading There will be a total of 40 marks available broken down as follows: . 12 Marks for the Activity Diagram: 6 marks for accurately capturing the flow of activities for the chosen system. 1 mark for correct usage of swimlanes. 2 marks for correct usage of decision and merge points (including guards). 3 marks for correct usage of synchronization (forks and joins) . 12 Marks for the Sequence Diagram: 6 marks for accurately capturing the interaction of objects for the chosen system. 2 marks for including multiple message types (at least 4-0.5 marks each. 2 marks for including at least four logical objects - 0.5 marks each. 2 marks for correct usage of looping in a sequence diagram . 16 Marks for the Statechart Diagram: 6 marks for accurately capturing the possible behavior of the chosen system. 2 marks for correct usage of hierarchal states. 2 marks for correct usage of transitions with triggers, guards, and resulting actions. 2 marks for correct usage of at least two concurrent statecharts. 2 marks for correct usage of a history state. 2 marks for correct usage of parent and child transitions