Agile development methodologies incorporate testing throughout the development process such as what is found in eXtreme Programming (XP).  Ambler (2002) stated that testing frequently and often can significantly reduce the cost of development. 

Beck claims that the costs are relatively flat when using the eXtreme Programming methodology (Ambler, 2002).The thought process is that if an error is found during the requirements phase it is relatively easy to change.  For the scale, this is about $1 of a developer’s time. 

The design stage is more expensive because both the analysis and design need changing.  This is given a value of $10.  If the issue is not found until programming then the analysis and design not only require changing but portions of the code must be thrown out or scrapped.  The monetary value at this time is $100.  They estimate that correcting a problem once it reaches the traditional testing phase is estimated at $1000.

Finally, once the issue ends up in a production environment not only does the analysis, design, and code need changed, but also the database must be fixed, data must be restored, and training or user manual reprinted.  The cost is estimated at $10,000. 

Do you believe you would be able to convince your organization to ensure a solid test schedule given this information?  Explain.

———————————————————————————————————————————–

Write a 200- to 300-word short answer to the following questions:

• Is testing a distinct phase of the project or is it part of multiple phases of the project? Explain.
• What components help testing quality and effectiveness?

—————————————————————————————————————————————

This is a team assignment only the highlighted part is mine to do.

Review the Service Request SR-kf-013 for Kudler Fine Foods.

Resource: Virtual Organizations link under Academic Resources for Kudler Fine Foods and Service Request.

Draft the next 4- to 6-page section of the paper, due in Week Five.

Include the following:

• Preliminary design model: Provide a diagram that illustrates the overall logical information architecture.
• Design trade-off approach: Specify the tradeoffs among cost, schedule, and performance. For example, a fast, inexpensive solution may not address performance requirements adequately.
• Detailed design process and design specifications: Specify separate recommended decisions for software design, hardware, and networks. Include resolution of HCI considerations.
• Physical model of the system: Illustrate the recommended decisions in information architecture diagrams.

Prepare presentation slides for the Week Four Learning Team topics. Update the Microsoft® PowerPoint® presentation from the previous week incorporating any feedback from the facilitator.

Submit your assignment using the Assignment Files tab