Hoosier Burger Case: Part I

Apply the SDLC approach to Hoosier Burger.

According to our text, the four steps of the systems development life cycle are planning and selection, analysis, design, and implementation and operation (Valacich, George, and Hoffer, pg. 3). For Hoosier Burger, Bob and Thelma would need to utilize the SDLC for the implementation of an electronic system. They would need to plan out what their new electronic system would need to be able to do (inventory control, point of sales, financial tracking, etc.).

They would then need to analyze their current workflow. They would need to go over what part of their workflow is currently not working and how they could change this to work more fluidly. This may require them to go back to the planning phase and make adjustments to their electronic system plan. There could be some parts of their workflow that they would like to keep in their new system, and even that could require them to change their planning.

Design would require Bob and Thelma to take the information they have gathered in the analysis phase and design their new system based off the plan they put together. The design phase can end up taken the longest time because there is so much they could factor in to the timeframe. There could be changes that may surface that push Bob and Thelma back to the planning phase, as well as the analysis phase. A timeframe for the design phase can be planned out, but sometimes there are factors that come up, that cannot be avoided.

Finally, Bob and Thelma would implement their new electronic system. Once a go-live date has been set and the new system is live, Hoosier Burger would then be able to see how their new system works. Most likely, it will take some time for the new system to show signs of improvement to their workflow, but it is part of the SDLC. As before, there could be issues that arise during the go-live that could require adjustments to the design of the system, but this is why the SDLC is illustrated in a...