Case Study: Kudler Fine Foods Frequent Shopper Program

4568 Words19 Pages
Kudler Fine Foods Frequent Shopper Program Sylvia Manriquez, Jeffrey Edwards, Tanya Stewart, Kevin Knapp BSA 375 May 6, 2013 Dr. Todd Feuerherm Kudler Fine Foods Frequent Shopper Program Project Scope and Goals Kudler Fine Foods is in the business of providing specialty foods that cannot be found in grocery stores such as Wal-Mart or Albertson’s. The ideal plan of Kudler Fine Foods is to increase revenue; therefore Kuldler is planning on creating a Frequent Shopper Program. This program will track shopping patterns giving Kudler the ability to satisfy customers better. The program will include three major steps with sub-contents to gather all necessary information to complete the Frequent Shopper Program. Kudler Fine Foods ultimate…show more content…
The stored data includes personal information about each customer, such as: name, address, birth date, and anniversaries (University of Phoenix, 2013). Taking this into account, it is easily feasible to track each customer’s purchases and share this information with external companies in partnership with Kudler. Storing this additional information within the current database would require minimal set-up. An initial investment for a new centralized database server would be required as well as installation of all the same software at each location. Keeping a local database is quite a bit different to manage then one which is being shared with external companies and this is where costs arise. More security features will need to be installed at the server level for protection of customer and company information when being accessed from outside companies in partnership with Kudler. Training will need to be implemented for staff to understand how to access the database from their location and authentication software will need to be implemented as well as user access…show more content…
Everything involving technical details, theories of operation, maintenance, and design specifications needs to be provided in the documentation. If custom hardware is used, every part of its design and operation should be documented so that it can be serviced. External hardware will come with documentation that needs to be saved and incorporated into the systems overall document library. Future and current employees will use the system documentation to research for upgrades, upkeep, and even repair. The documentation needs to be high in quality so that extra work does not have to be done to reverse engineer any part of the system in order to provide support of any
Open Document