Bettering Hoosier Burger
Bob and Thelma Mellankamp wanted to open their ain concern. They came across Myrtle’s Family Restaurant and saw a mark that said it was for sale. Bob and Thelma bought the eating house and their ain eating house was brought to life Hoosier Burger Restaurant. The thought was one that everyone dreams of having their ain concern but do non understand all the behind the scenes undertakings that make a concern successful. Yes. they have been in concern for over 30 old ages but even they understand that their dream needs some betterment to go on in the market they are in. Bob and Thelma have discussed the thought of a computing machine system but do non cognize where to get down so Bob wants to convey in a adviser to turn to some of their weak countries and do suggestions to better Hoosier Burger. They inform the adviser on how concern is ran. This eating house is behind the curve when it comes to engineering. They still do paper trail on every facet of the eating house from bringings. stock lists. and point of sale ( Valacich. George. & A ; Hoffer. 2009 ) .
Even though paper was what many companies started out with. it is no longer an sanctioned manner to make concern. Paper allows excessively many human mistakes to come into drama where as an electronic record maintaining system eliminates a bulk of these mistakes but as with any data…you get out of it what you put into it. All this means that if you put inaccurate informations into the system so the information you get from the system will besides be inaccurate. Hoosier Burger has learned this lesson oh excessively good. Particularly. since they did non order adequate vanilla ice pick to cover their ain special so they had to run to the food market shop to seek to acquire plenty for the gross revenues they were making on the particular ( Valacich et Al. . 2009 ) . Bob and Thelma agreed that it would be valuable to buy an information system to help them in the countries of stock list direction. selling. client service. nutrient readying. and point of sale ( Valacich et al. ) . Now that it has been decided on what needs to be addressed with this new information system.
The systems development life rhythm ( SDLC ) begins ( Valacich et Al. . 2009 ) . The four chief stairss of this procedure are ( 1 ) planning and choice. ( 2 ) analysis. ( 3 ) design. and ( 4 ) execution and operation. The first stage is to be after the system out and so choose the appropriate system for occupation. This state of affairs a good point of sale system would give this company the system they need for day-to-day operations and growing. A good POS covers all facets of the eating house from the dining country to the kitchen and even the storage countries. With any system. you have subsystems that are called constituents. Components by themselves do non do a system but when put together they make a complete system. In the instance of Hoosier Burger one of the constituents of the system would be an stock list log or database. This subsystem would track uses and bringings to guarantee that stocks are maintain at the properly degree for day-to-day operation of the concern. The undertaking development squad that Hoosier Burger selected was based on the failings of the organisation.
The focal point of the new system will be on ways to better stock list direction. client service. and direction coverage. Any one of these failings could stultify the organisation. The squad needs to acquire every bit much information as possible to guarantee that they are constructing the correct system for this organisation. I would utilize the interview procedure to acquire every bit much information from the staff as possible and I would utilize questionnaire to client input. Besides. I would garner as many studies and logs that I could for back uping certification but with the current procedures. This type of information may non be readily available or available at all. After garnering this information. the procedure of developing a system to rectify their failings begins. You would besides desire to happen out if the company has any ascents planned so that you could integrate that into the system. In this instance. they want to spread out to bringing services and a thrust through operation. These enlargements do non necessitate a batch of ascents to the edifice so these will travel into consequence instantly to increase gross for the company. The diagram figure 1 shows the flow of information for the new system. Fig 1.
As you can see from figure. the information system that need is robust in nature but simple. The system analyst now needs to interrupt down the different entities the company needs to hive away information about. These entities have peculiar features that require information to be stored. There are regulations used when trying to put an identifier for each entity. The diagram will demo the alterations and stipulate the component’s needed for each relationship.
In the text. an entity is a individual. object. topographic point. construct. or event in the user environment of which an organisation wants to hive away informations ( Valacich. George. & A ; Hoffer. 2009 ) . Person entities are normally your employees but can be your client. Topographic point entities are fundamentally the location i. e. provinces. parts. states. Object entities include the machines you use. edifices your work out of. merchandises you produce. and vehicles. Event entities can be considered gross revenues. reclamations. enrollments. Concept entities include classs. histories. or work centres.
Hoosier Burger needs the ability to hive away information about their single entities. The chief entity is the client that frequents the eating house on a regular footing. They besides need to hive away information about what merchandises the client is buying. Hoosier Burger besides needs the ability to hive away information about the company itself and topographic point entities which are the concerns that order repasts from the company.
We will now discourse properties. Attributes harmonizing to the text are named belongingss or features of entities that are of involvement to the organisation ( Valacich et Al. . 2009 ) . The undermentioned properties should be used for the client: client name. client reference. client phone figure. customer’s figure of orders. and client specific orders. These properties can besides be assigned to the concern entity by exchanging out client with concern. Properties can besides be assigned to the terminal merchandise such as ingredients. monetary value. and sum sold.
Identifying the entities require delegating alone placing features for the entity type. For illustration when covering the with client entity. you would utilize an identifier that is easy to utilize i. e. Customer ID. Customer Name. Customer Address. and Customer Phone. The key when covering with placing points is doing it user friendly. Once all of these have been put into topographic point. the system analyst now needs to construct three working solutions to this company’s weaknesses. The three solutions as discussed in the text are low. medium. and high degree. The difference in the three degrees normally equates to be but it besides includes how much attempt the user has to set into the system and the type of engineering used. Time is money and if your employees are holding to pass more clip with the system than the client so Hoosier Burger will lose money.
All of these factors come into drama when developing a system for an organisation. The key to success of Hoosier Burger and the undertaking development squad is communicating and cooperation. The more clip these two entities communicate with each the easier it will be for the undertaking squad to turn to the demands of the client and client addresses the demands of the undertaking squad. It is a two manner street. In the terminal. the occupation of the system analyst is to develop a system that addresses the wants and demands of the client while keeping within the budget. You do non desire to sell the client a “Corvette” when a “Camaro” would hold done what is needed.
Valacich. J. S. . George. J. F. . & A ; Hoffer. J. A. ( 2009 ) . Necessities of Systems Analysis and Design ( 4th ed. ) . Upper Saddle River. New jersey: Prentice Hall.