Hoosier Burger Case: Part 2Robert DeanINF340: Business Systems Analysis (BQJ620DS)Instructor: David PittmanDateHoosier Burger Case AnalysisIntroductionAfter great consideration, the Hoosier Burger Restaurant is in urgent need of a computerized solution to its problems. During peak hours, customers have been waiting for a long time to place orders and receive their order. Secondly, low-in-stock inventory items are often not reordered in a time, therefore creating problems with the food preparation. The management has therefore emphasized the importance of improving Hoosier Burger’s inventory control, customer ordering, and management reporting systems. Demand for Hoosier Burger food is at an all-time high, and this increased demand is creating problems for Hoosier Burger’s staff, creating stock-out problems, and impacting sales. This document will look at the Systems Development Life Cycle (SDLC) approach to Hoosier Burger, discuss the subcomponents of the system, the selection criteria, the requirement identification process, the diagrams and the data model.System OverviewSystems Development Life Cycle (SDLC) The System Development Life Cycle (SDLC) contains four parts, which the system should follow; the planning, analysis, creating, testing, and deploying the system.