$1.$ Imagine you are an IS analyst working for a startup that has recently launched a telemedicine platform. A hospital in your city wants to replace their legacy system with your system. a$.$ The current platform$$s user interface is well$-$designed. b$.$ Services like drug delivery and patient registration are working fine. c$.$ Operations like appointment scheduling, prescription and report management, refund processing, and customer support are inefficient. d$.$ This had led to loss of customers for the hospital. You are tasked with redesigning the system using Data Flow Diagrams $($DFDs$).$ Create a context diagram $($Level $0)$ and a detailed Diagram $0($Level $1)$ of the current system. These diagrams should show the problems of the old system. Then, propose a new DFD structure that optimizes the process, and focuses on improving communication between subsystems.

$2.$ Your company uses an outdated Customer Relationship Management $($CRM$)$ software for customer management. The company is growing, and this system is no longer scalable. You need to move to a cloud based CRM system. You have hired an IS analyst, who is tasked with overseeing this transition. The analyst presented a proposed solution. Prepare a detailed comparison between the existing CRM and the proposed CRM system. What are the key differences that you noticed between the systems? As your company transitions to cloud, what are some challenges that the company might face? What are your measures to face those challenges?

$3.$ You recently opened several branches of a popular restaurant chain in Edmonton. To handle influx of customers in peak hours $($dine$-$in$,$ take outs, online orders$),$ you plan to introduce an Order Management System. This is your first time trying to work with something at a big scale $($data wise$).$ You have to integrate data from various subsystems to ensure an efficient flow. Moreover, the requirements are not entirely clear, so you decide to go for a prototyping approach. Which type of prototyping $($patched$-$up$,$ non$-$operational, first$-$of$-$a$-$series, or selected features$)$ would you use for this project? Justify your choice with example scenarios and explain how you would gather user feedback during the prototyping process to refine the system

$4.$ Your company is wanting to adopt object$-$oriented analysis for a new employee management system project. Do you think an object oriented approach would be a better option for this project? Provide examples of where object$-$oriented principles like abstraction$,$ inheritance, encapsulation, or polymorphism would be advantageous $($or not$).$

$5.$ A government organization wants to develop a $$Smart City$$ information system to manage traffic, waste disposal, and ensure public safety. You are leading the systems analysis team. Create a high$-$level DFD for the Smart City system, detailing the interactions between external entities $($citizens and government$)$ and system processes. Do processes share data between each other? If yes, how are these processes interrelated? Suggest your ways to partition the larger system into manageable subsystems and mention them. Show the new system structure using a use$-$case diagram.

$6.$ Your company uses a long standing file sharing system to share files between employees. It has been operational for more than $15$ years and requires frequent maintenance. Recent data shows that more than $70\%$ of IT resources are spent on the system maintenance rather than developing new applications. Conduct a feasibility analysis $($technical$,$ economic, operational$)$ of continuing to maintain the existing system versus developing a new cloud based system. According to the analysis, would you recommend staying with the existing system or developing a new one? What factors would you consider in making your recommendation?