One of the key roles of an analyst is to clearly identify the way a new software process is going to work. Activity diagrams are process models. They are used to corroborate with the user department that the process flow is correct, as well as communicate the logic for the development team. They are not technical in nature. They show activity and logic. Create a process model for the scenario below. Use these symbols, shown below, as discussed in this weeks lecture. You can also review an accessible version of the Activity Diagram Symbol guide . Activity Diagram Symbol Guide Scenario Current state: you have just successfully logged into an ATM and are looking at the menu. You begin by selecting the withdrawal button. Your next action is to enter a dollar amount. The ATM system logic checks to see if the amount is greater than the daily limit. If it is, it displays a message that says its cash limit is $500 and sends you back up to enter another dollar amount. Once you enter the amount again, the system logic checks to see whether your account balance is greater than what you are asking for. If it is not, it displays an appropriate message, and you are prompted to enter the amount again. If your balance is greater than what you ask for, the system approves the withdrawal by displaying a Dispensing" message on the ATM screen and then dispensing the cash. Next, the system asks if you want a printed receipt. If you say yes, it prints the receipt. End state: The ATM displays Take your card on the screen; the transaction is over. Instructions Create your activity diagram in PowerPoint, or by creating a free trial account on www.lucidcharts.com. Do not use Word or Excel. Save your PowerPoint or Lucidchart diagram as a PDF file and upload into Moodle below. Retain your PowerPoint or Lucidchart diagram until I have returned grades. Best Practices Please Read Adhering to best practices is important. The following will apply to this assignment: o Decision boxes must have a yes and a no path. o Be consistent and keep the yes and no logic on the same side of every decision box (for example, all yes paths might be on the left side of the decision boxes). o Logic can go up as well as down. Down means the system is moving on to the next step. Up indicates the system (or the user) is/are going to re-enter or re-process something. o Only one process/action statement or decision statement in each box. o Statements in the boxes should be very brief (just a few words). Enter amount instead of Please enter the amount of cash you want, for example. o Use the proper symbols for processes and decisions; remember to use arrows appropriately.