Draw an activity diagram for a login system. The system initially

starts by $`$asking username and password$`$ which then forks

into $`$validate username$`$ and $`$validate password$`$ concurrent

activities. Decide whether validation is correct or not $($this is a

decision$).$ If validation is not correct, set the activity diagram to

its initial state.

$$ On the other hand, if validation is correct, go to $`$logged in as

member$`$ activity. From here, $`$order product$`$ and $`$edit profile$`$

activities can take place as individual activities $($these are not

concurrent tasks, they are decisions$).$ These two activities $($i$.$e$.$

order product and edit profile$)$ shall merge and the system

goes to $`$logout$`$ activity $-$ where it reaches to its final state.

Notice that the user can order and$/$or edit product as

individual activities as many times as they want.