Homework answers / question archive / Systems Diagrams and Visualization Project Create the following UML diagrams to visualize the process of completing the IT project from the previous exercise (providing IT services for a new building): • • • • Use Case diagram Activity diagram Communications diagram Data Flow diagram Assume the following basic processes: 1

Systems Diagrams and Visualization Project Create the following UML diagrams to visualize the process of completing the IT project from the previous exercise (providing IT services for a new building): • • • • Use Case diagram Activity diagram Communications diagram Data Flow diagram Assume the following basic processes: 1

Business

Share With

Systems Diagrams and Visualization Project Create the following UML diagrams to visualize the process of completing the IT project from the previous exercise (providing IT services for a new building): • • • • Use Case diagram Activity diagram Communications diagram Data Flow diagram Assume the following basic processes: 1. 2. 3. 4. 5. 6. 7. 8. 9. Procurement of all resources. Setup of PCs and network servers. Deployment and Testing of resources to the IT Area/Office. Deployment and Testing of resources to the Administrative Area. Deployment and Testing of resources to the Conference Room. Deployment and Testing of resources to the Meeting Room. Deployment and Testing of resources to the Individual Offices. Deployment and Testing of resources to the Computer Labs. Testing of all Other Locations. • Create a Use Case diagram to show all actors and the basic processes above o Procurement, Setup, Deployment & testing of each major location. • Create an Activity diagram to show the deployment and testing of resources into the Computer Labs o Network connectivity testing requires interaction between the PC and Network Specialist o Projector connectivity testing requires interaction between the PC and AV Specialist. • Create a Communications diagram to show collaboration between the PC Specialist, the Network Specialist and the AV Specialist during deployment and testing of resources into the Computer Labs. o If network connectivity issues arise, the PC Specialist will communicate with the Network Specialist. o If projector connectivity issues arise, the PC Specialist will communicate with the AV Specialist. • Create a Data Flow diagram to show the Procurement of all resources, based on this additional information: o The PC Specialist enters all purchases into the Purchase Application system once the resources are purchased. o The PC Specialists closes all purchases in the Purchase Application system once the resources are received. Systems Diagrams & Visualization (UML & Data Flow) Example Fast Food Restaurant System Diagrams & Visualization Example - Fast Food Restaurant • Create Data Flow and UML Diagrams to show the process of ordering food at a Fast-Food Restaurant. • • • • Who are the players in the process (customer, clerk, cooks...)? What automated systems are used in the process? What activities work well, and which do not? What changes have you noticed over the years to make the processes better (for the customer and for the business)? • What changes would you make to improve the processes and performance? • What data can be stored and used to analyze the performance of the systems (i.e. how can Analytics be used)? FastFood - Use Case Diagram Place Order Cashier Pay Order The Use Case diagram is a high-level diagram that identifies an Actor’s interactions with a system. It is not meant to get into details. Details are covered in other types of diagrams. Customer A Customer places an order with a Cashier (or Kiosk) and then pays the Cashier (or via the Kiosk). The Cashier then delivers the order to the Customer. Deliver Order Notice this does not try to show the different between a drive-in transaction versus a walk-in; Or a person or a kiosk (like Taco Bell or McDonalds) FastFood Activity Diagram Cashier Receive Order Order System Enter Order Payment System Cook Process Order The Activity diagram provides details on the activities of a process using “Swim Lanes”. In this case, the customer places the order with the Cashier who enters the order and receives details from the Order system and enters the payment and receives details from the Payment system. Display Order & Total Request Payment Process Payment Process Payment Confirm Payment & Refund Refund Difference Cook Items Process Order Note in this diagram that the actual order is not transmitted to the Cook until the transactions are processed. Stage Items NO Deliver Order Stage Order Order Complete? YES How might this diagram be different if the customer used a Kiosk rather than a Cashier? FastFood - Sequence Diagram Customer Payment System Order System Cashier placeOrder (orderList, exceptions) enterOrder (orderList, exceptions) confirmOrder (orderList, exceptions, totalCost) displayOrder (orderList, exceptions, totalCost) payBill (payment) processOrder (orderList, exceptions) processPayment (payment) confirmPayment (payment, refund) returnRefund (refund) stageOrder (preparedItems) deliverOrder (packagedItems) x x Cook The Sequence diagram shows the sequence of activities. The Customer places an order as a list of items (with exceptions) and the Cashier enters them into the Order system. The order is displayed back. The Customer makes a payment which triggers the order to the Cook and to the Payment system. The payment is displayed back, and the Cashier refunds any overpayment. The Cook stages the order items, and the Cashier gives them to the Customer when complete. Notice bars that extend down and represent the approximate time needed to satisfy an action. The X’s at the bottom represent the last actions. These just happen to end at the same time. FastFood - Communication Diagram 4. Confirm Order 9. Refund 11. Deliver Order Cook 6. Process Order Customer 1. Place Order 5. Pay Bill 10. Stage Order Cashier 3. Display Order 7. Process Payment 2. Enter Order 8. Confirm Payment :: paymentSystem :: orderSystem The Communication diagram shows the interaction of the actors/systems. Notice the numbers represent the sequence. Notice the symbols used to represent a system. FastFood Data Flow Diagram Level 0 1 Place Order Order List & Exceptions Item Price 2 Calculate Bill D1 Total Bill The Data Flow diagram shows how data flows within the process. Payment Amount Customer Temp Data Store 3 Payment This is Level 0 which is the highest level. Pay Bill Refund Order List & Exceptions 6 4 Packaged Order Deliver Order Prepare Order 5 Package Order Prepared Items A Temp Data Store is shown and could be incorporated in the next levels. FastFood - Statechart Diagram Customer Places Order Pending Order Customer Notified of Cost Request Payment Payment Made Confirmed Order Order sent to Cook for Processing Staged Order Items placed in Bag Packaged Order Order given to Customer Cooked Items placed in Bin Cook Order The Statechart diagram shows states (i.e. waiting for something) within the process. Once the Customer places the order, it is ‘pending’ approval (awaiting cashier data entry and system response). Once the Customer is told the cost, it is ‘pending’ customer acceptance and payment. Once payment is made, it is ‘pending’ acceptance by the cashier or card processor. Etc. Notice the loops indicating that all items are not finished cooking at the same time and are bagged as they are ready and discovered by the Cashier. Customer places Order Order delivered to Customer Order System orderList exceptions totalCost processOrder() displayOrder() FastFood - Class Diagram Cashier Enter into Confirms to orderList exceptions totalCost payment refund preparedItems packagedOrder receiveCustomerOrder() deliverOrderToCustomer() enterOrderInOrderSystem() placeOrderWithCook() receiveCustomerPayment() processPaymentInPaySystem() returnRefundToCustomer() Processes a Confirmed to Payment System payment refund The Class diagram shows the structure of a system. The top box provides the name of the class. The middle box contains the attributes (fields) of the class. The bottom box contains the operations the class can execute. processPayment() confirmPayment() Cook orderList exceptions preparedItems cookOrder() stageOrder() Lines connect and describe the actions taken (Cashier processes a Payment and the Payment is confirmed by the Cashier); etc.