We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

See Pricing

What's Your Topic?

Hire a Professional Writer Now

The input space is limited by 250 symbols

What's Your Deadline?

Choose 3 Hours or More.
2/4 steps

How Many Pages?

3/4 steps

Sign Up and See Pricing

"You must agree to out terms of services and privacy policy"
Get Offer

Eating habits french

Hire a Professional Writer Now

The input space is limited by 250 symbols

Deadline:2 days left
"You must agree to out terms of services and privacy policy"
Write my paper

The frequent shopper program will store customer purchase behavior, anemographic information, which will assist in any promotions and store events, and add customer contact information helping Cuddle to offer the best experience to their customers. Smith systems consulting would like to explore different methods in order to complete the Cuddle fine foods frequent shopper program. The following methods will go over the advantages and disadvantages of the frequent shopper program.

Market research will be conducted by Cuddle Fine Foods in the field of development and testing to make a correct decision about, which program will be developed by smith systems consulting.

Don't use plagiarized sources. Get Your Custom Essay on
Eating habits french
Just from $13,9/Page
Get custom paper

Throughout the testing process smith systems are looking at several development methods for the frequent shopper program (Millionaire, 2006). The first method under consideration is the waterfall development method (Millionaire, 2006). Waterfall development is a software development model, which comprises of a phased succession of actions leading to the delivery of a software product.

In essence, it is a framework for software development in, which development continues successively through a cycle of phases, opening with system requirements analysis and advancing up to product delivery and maintenance (Millionaire, 2006).

Feedback loops subsist between every stage, so that as additional information is revealed or problems are exposed, it is feasible to go over a phase and make suiTABLE changes (Millionaire 2006). Progress moves from one juncture to the next, a lot like the waterfall that provides the model its name.

The waterfall method moves through six stages, which are requirements analysis, design, implementation, testing, installation and maintenance (Millionaire, 2006). The advantages of using the waterfall method are numerous. Primarily, the staged development cycle implements control: every segment has a distinct begin and end stage, and growth can be irrefutably known via the use of milestones by both vendor and client (Millionaire, 2006). The importance on necessities and design prior to writing a single line of code guarantees negligible depletion of time and effort.

Furthermore, it decreases the possibility of schedule slippage, or of client hopes not being met (Millionaire, 2006). Notwithstanding the apparently clear advantages, the waterfall model has come in for a reasonTABLE share of critique in current times (Millionaire, 2006). The most important analysis circles around the reality that very often, clients don’t actually know what they require up-front. Nevertheless, what they desire appear out of continual two- way relations over the path of the project.

In this state, the waterfall model, with its importance on open necessities gain and create, is perceived as fairly impractical and inapt for the vagaries of the real world (Millionaire, 2006). Furthermore, considering the vague spirit of customer requests, guessing time and costs With any level of precision is frequently really tricky (Millionaire, 2006). Thus, the model is suggested for use merely in projects, which are fairly secure and where client requirements can be visibly acknowledged at an initial stage (Millionaire, 2006).

Whilst the model has critics, it remains functional for definite kinds of projects and can, generate considerTABLE cost and time reserves. Whether smith systems consulting ought to use it or not depends mostly on how well the company comprehends the patrons’ needs, and how much instability is expected as the project progresses (Millionaire, 2006). It’s important to say that for more fickle projects, auxiliary frameworks exist for thoughts regarding project management, pa articulacy the spiral model (Millionaire, 2006).

The Spiral Life Cycle Model is a kind of iterative footwear development model which is normally put into practice in extreme risk projects (“Spiral,” n. D. ). In this system development method the aspects of both, waterfall model and prototype model are united. In the spiral development model the activities can be arranged in the form of a spiral (“Spiral,” n. D. ). There are many advantages to the spiral development model. Spiral Life Cycle Model is one of the most adapTABLE software development lifestyle models in use (“Spiral,” n. . ). Development stages can be established by the project manager, according to the difficulty of the project. Furthermore, observing the project is incredibly simple and efficient. Every stage, including each loop, involves a assessment from worried people (“Spiral,” n. D. ). This makes the spiral development model extra translucent. Risk management is another of the features Included in the model, which means it is extra fascinating to weigh against other models (“Spiral,” n. D. ).

Moreover, any alterations could be made later in the life cycle the project manger can copy these changes whenever necessary. The spiral development method is great for high risk projects were the business needs are improper. The spiral development method has some disadvantages as well. One such disadvantage in this model is extreme cost (“Spiral,” n. D. ). The skills needed to assess and examine the project necessitate expertise. However, meeting budgetary and preparation necessities is hard when this development process is followed (“Spiral,” n. . ). Lastly the amount of documentation required for certain stages makes managing projects very complicated. Another software development method is the agile development method (“agile,” 2009). In view of the fact that agile methodology is so commonly used t is vital to comprehend the advantages and disadvantages of agile development to decide if it is the greatest match for your project deliverTABLEs (“agile,” 2009). Agile development methodology has an adapTABLE group, which can react to the shifting requirements.

The team does not have to devote time and energy to ultimately uncover that when they distributed the product, the condition of the client changed. Face to face contact and nonstop feedback from client spokesperson leaves no room for speculation (“agile,” 2009). Furthermore, any documentation used in agile development is for the purpose of saving time. The ending effect is the high value of software in the smallest amount of time possible and pleased clients. The disadvantages of the agile development method start with the effort needed for some deliverTABLEs in certain cases (“agile,” 2009).

There is lack of importance on the essential planning and documentation. Only higher-ranking programmers are competent of making the type of choices necessary through the development process (“agile,” 2009). For this reason it has no place for beginning programmers, except when united with skilled resources (“agile,” 2009). When running a great project which entails many offshore groups and necessities which won’t change, then the other software development methodologies would be better for delivering the necessary process of software development (“agile,” 2009).

As soon as smith systems consulting have evaluated these software development methodologies they can decide what method is best for Cuddle fine foods frequent shopper program. Because the frequent shopper programs are small it is recommended that smith systems consulting use the agile development method. Thanks to the close teams working in the agile method they will be better at the project and ensure its success. Finally in the agile method the customer has input on the program. References Millionaire, C. (2006).

Cite this Eating habits french

Eating habits french. (2018, Feb 07). Retrieved from https://graduateway.com/essay-kudler-fine-foods-frequent-shopper-program/

Show less
  • Use multiple resourses when assembling your essay
  • Get help form professional writers when not sure you can do it yourself
  • Use Plagiarism Checker to double check your essay
  • Do not copy and paste free to download essays
Get plagiarism free essay

Search for essay samples now

Haven't found the Essay You Want?

Get my paper now

For Only $13.90/page