Frequent Shopper Case Study: Kudler Fine Foods

Frequent Shopper Program Part 1

Kudler Fine Foods (KFF) is a local upscale specialty food store that is committed to providing customers with the finest selection of specialty foods. In addition, KFF would like to reward their customers for their loyalty by incorporating a frequent shopper program. KFF is planning on developing a system that tracks customer purchases and awards loyalty points for redemption. The system will assist KFF in satisfying their most valued customers. Smith Systems Consulting Firm has been contracted for the development of the system. Smith Systems Consulting has been serving clients since 1994 with high value web and business application services. In this proposal,
KFF currently has a broad range of requirements and every detail is not known. As the project progresses, more details may become known; which could cause the project to be stopped and re-imagined. The second disadvantage is that there is no feedback of the system by stakeholders until after the testing phase. KFF has no way of knowing if the program meets their requirements because the “waterfall” process does not facilitate intermediate versions. The second method that will be proposed is the agile methodology. The agile methodology proposes alternatives to traditional project management. Agile development focuses on keeping code simple, testing often, and delivering functional bits of the application as soon as they are ready (TechTarget, 2014). One goal of agile development is to build upon small-client-approved parts as the project progresses, as opposed to delivering one large application at the end of the
Testing is conducted differently depending on which software model is used. Since the waterfall method follows a sequential approach, the testing is done so also. The flexibility of the agile method also allows flexibility for the testing process. Using the waterfall method testing would begin during the implementation stage. The work would be divided into modules and the coding would begin after receiving the system design documents. The frequent shopper program would be developed into small programs called units. As an example, there would be a program that handles the input from the customer and another program that would track the employee’s reward points. Each unit is developed and then tested for functionality. Unit testing verifies if the units meet the specifications. The units are then integrated into a complete system during the integration phase and tested to see if all units coordinate between each other and the system functions as a whole per the specification (Onestoptesting, 2014). After testing of the frequent shopper program is successful, the software is delivered to the customer. If problems are found after deployment they are solved immediately. This is referred to be maintenance and sometimes that process is virtually never