As the lead analyst for the Hoosier Burger project, you have worked closely with Bob and Thelma Mellankamp. Having completed the systems analysis phase, you are now ready to begin designing the new Hoosier Burger information system. As the lead analyst on this project, you are responsible for overseeing the development of the forms, reports, and databases required by the new system. Because the inventory system is being automated and a new delivery system is being implemented, the Hoosier Burger system requires the development of several forms and reports. Using your data-flow diagrams and entity-relationship diagrams, you begin the task of identifying all the necessary forms and reports. You readily identify the need for a Delivery Customer Order Form, a Customer Account Balance Form, a Low-in-Stock Report, and a Daily Delivery Summary Report. The Delivery Customer Order Form will capture order details for those customers placing delivery orders. Bob will use the Customer Account Balance Form to look up a customer's current account balance. The Low-in-Stock Report will be generated daily to identify all food items or supplies that are low in stock. The Daily Delivery Summary Report will summarize each day's delivery sales by menu item sold. As the lead analyst on the Hoosier Burger project, you have had the opportunity to learn more about the systems development process, work with project team members, and interact with the system's end users, especially with Bob and Thelma. You have just completed the design work for the various forms and reports that will be used by Bob, Thelma, and their employees. Now it is time to prepare logical and physical database designs for the new Hoosier Burger system. During a meeting with Hoosier Burger project team members, you review the four steps in logical database modeling and design. It will be your task to prepare the logical models for the Customer Order Form, Customer Account Balance Form, Daily Delivery Sales Report, and Inventory Low-in- Stock Report. At the next meeting, the E-R model will be translated and a final logical model produced. The development of Hoosier Burger's information system is nearing completion. At recent project meetings, the types of testing, training, documentation, and installation strategies appropriate for Hoosier Burger have been discussed. The end users have little computer experience and thus require several types of training and supporting documentation. Fred Jones, one of the project's team members, has recommended using a direct installation approach. Because Hoosier Burger's information system is relatively small, he feels that the direct approach is the best installation strategy to pursue. The new system could be installed at the beginning of the week and be up and running for the weekend traffic. However, Paula Freeman does not like this idea. She feels that a parallel approach is more appropriate. She worries that if the system crashes, it may be difficult to return to the old system. Here is a start for you on the project: 1. Decompose Hoosier Burger into its major subsystems and write a description of each subsystem. (hbsubsystems.docx) A sample of the subsystem would be the inventory control. So do a brief description of it as it is. The customer ordering, do a brief description of it as it is. How orders are taken, processed, and then cashed out as it is. 2. List the users of the system and describe their interaction with the system. (hbusers.docx) Describe the roles of the owners, Thelma and Bob Describe the roles of the cooks Describe the roles of the waitresses Describe the roles of the customers 3. Develop a Project Charter for the project. (projectcharter.docx) Take a look on page 55. This is a ten thousand foot view prepared by you to the customer, Thelma and Bob, that describes what the project you are proposing will do for them. You need to outline the key elements. For instance you should outline they need to lose the cash register, put in a point of sale database and computer system to track better the orders and the inventory..On page 56 is a sample of this document and I would use this if I were you. 4. Develop a Service Request Form for use by Hoosier Burger personnel to request future changes or corrections to the system. (hbsrf.docx) Take a look at the Systems Service Request form on page 95. Make up something that looks like that. 5. Prepare a Gantt chart using MS Project or Open Project for the Hoosier Burger project. Using the following information. Assume the project is set to start on September 1, 2011. (hbgantt.mpp) or (hbgantt.pod) Using the sample on page 65. Create a Gantt chart using Project Libre 6. Prepare a Network diagram using MS Project or Open Project for the HoosierBurger project using the information above. (hbnetwork.mpp) or (hbnetwork.pod) Using Lucid Charts in your Gmail account, create a Network diagram of the information on the project hand out that is similar to the one at the bottom of the page 68. 7. Develop a Communications Plan answering the questions on page 58 of your text in it (hbcp.docx) As it indicates, develop a plan to communicate with Thelma and Bob and other staff as necessary as outlined by the questions on page 58. 8. Develop a Project Communication Matrix for the project. (hbcom.docx) Take a look on page 62. Develop this matrix based on the information you've developed. For instance, you have a Gnatt chart, so this will help populate some of this information, such as Date Due, perhaps Stakeholder and Team Contact. 9. Develop a Use-Case diagram for the Hoosier Burger project. (hbuc.docx or hbuc.pdf or you may submit any type of image file called hbuc) Go to Appendix A, page 370 for the definition and sample of a diagram on page 371. You are to develop a system, then show how the users will use the elements of the proposed system. For instance, show who will use the new Point of sale system to input orders into the system (probably the waitress or waiter.) 9. Develop a Use-Case diagram for the Hoosier Burger project. (hbuc.docx or hbuc.pdf or you may submit any type of image file called hbuc) 10. Develop a list of each object class that will need to be stored in the Hoosier Burger database and under each class put a sublist of the attributes of each class. (hbclass.docx) A sample object class would be a customer. So what data do you want to store on the customer. Well if it is delivery, you better have address, cell number, maybe business address if they are a business customer. 11. Develop a UML Class diagram showing the relevant classes, attributes, operations and relationships for the Hoosier Burger project. (hbuml.docx or hbuml.pdf or you may submit any type of image file called hbuml) So suppose you created an object class from 10 for the staff. So the staff has a name, DOB, Start of employment, address, cell number. The relationship would be to the type of job they have: cook, waitress/waiter, host/hostess, and other. See page 374 for a sample of this diagram. 12. Draw a state diagram that shows all the possible states of an order object. (hbstate.docx or or hbstate pdf or you may submit any type of image file called hstate) Using Lucid Chart, draw a diagram from when an order is placed by the customer, taken by the waitress/waiter, the cook prepares the food, the food is delivered by the waitress/waiter, the customer pays for the food. Food needs to be taken from inventory and then shown to be ordered. There are probably other relationships that need to be considered and shown