Frequent Shopper Program, Part I

Only available on StudyMode
  • Download(s) : 152
  • Published : February 22, 2013
Open Document
Text Preview
Frequent Shopper Program: Part I
The Frequent Shopper Program identifies, determines, and tracks customers' purchasing behavior. The program is applied by retailers to attract long-term customers that demonstrate a loyal relationship between both parties (Iterative and Incremental Development Testing, 2008). This paper discusses the methods that can be used in the development of the Frequent Shopper Program by Smith Systems Consulting. Waterfall model

Waterfall Model operates in a waterfall process tree. It has various phases such as requirement, design, implementation, verification, and maintenance that provide a successful execution to any system development. This model can be used in the development of frequent shopper program (Nicholls, 2005). The waterfall model's requirement phase will help Smith Systems Consulting to develop a program according to the need of Kudler Fine Foods. This model's other phases facilitate deep analysis of every aspect that provides appropriate development of the program. Each phase can be proceeded after the proper completion of the previous phase. This model facilitates Smith Systems Consultant’s advance knowledge about success or failure of the program, which helps to reduce failure risk. On the other hand, the waterfall model cannot facilitate the ability to update. In this model, information can be gathered after the process rather than during the process. This reduces flexibility to change pertaining to change in requirements. This aspect can make a faulty development as a result because it cannot be developed within the changing requirement of Kudler Fine Foods and relative environment. This may fail the whole program (Nicholls, 2005). Waterfall method testing

Kudler Fine Foods would test the waterfall method regarding quality and functional aspects of the Frequent Shopper Program. First, testing would start with coding of test goals, in which basic functionality of the system is checked to implement design in the form of coding. These codes would be written and modified to execute in the testing. Second, all software and hardware is analyzed to determine different ways of costumer use (Petersen, Wohlin & Baca). Additional tests are performed that will check test outcomes to understand deviations among a variety of hardware and software components. These varieties can be reviewed on the basis of quality and time within the Frequent Shopper Program to make a better decision. Further, the functional code executed is tested in 1st and 2nd steps of the process. Finally, defining whether the Frequent Shopper Program is in sync with the client needs completes the test process. Iterative and incremental development

This method eliminates the weaknesses of the Waterfall model. It works in a cyclic process and starts with initial planning and ends with deployment. This model can also be used in the development of Frequent Shopper Program (Datta, 2007). This method facilitates software with various levels or sub-parts. It is very useful to develop this program because it can be change at any time according to users and changes in requirements. Simple accessibility makes management an advantage. It will provide a facility of feedback that can help Kudler Fine Foods to deliver food according to consumers' need. It only has one disadvantage; each phase of this method is rigid and do not overlap each other. This may create conflict between systems and users, which can result in the failure of the program. This failure may affect Smith Systems Consulting and Kudler Fine Foods both in terms of rigidity (Datta, 2007).

Iterative and incremental development testing
Kudler Fine Foods could use the iterative and incremental development method to develop its Frequent Shopper Program. This method would start with breaking the entire program into several small parts and iterations that will make it easy for programmers in the testing phases. Each part and iteration of the program is tested at the end...
tracking img