Cold Code: Chain Tests Outside AppsCold Code: Chain Tests Outside Apps

Cold Stone Creamery, the fast-growing chain of premium ice-cream stores, doesn't develop its own software in-house.

Charles Babcock, Editor at Large, Cloud

May 27, 2005

2 Min Read
information logo in a gray background | information

Cold Stone Creamery, the fast-growing chain of premium ice-cream stores, doesn't develop its own software in-house. That makes the testing function particularly critical before applications, which are developed under contract outside of Cold Stone's IT department, are accepted and deployed for internal use.

"Ultimately, IT is responsible for what goes out to users," says Eric Parsons, business applications delivery manager for Cold Stone. Those applications are used in 1,000 franchise stores that average $405,000 a year in sales per store. Cold Stone plans to add 414 stores this year.

Cold Stone develops application requirements in SteelTrace Ltd.'s Catalyze, a next-generation requirements tool that lets both users and developers visualize how an application is supposed to function. Cold Stone business analysts develop what's known as the use case--or flow of user requirements that, translated into code, results in a functioning application. They then turn the use case over to one of two trusted outside development houses to produce the code. When Cold Stone gets the finished application back, it gives it to about 15 business users who follow a test plan generated by Catalyze to see whether it does what they want it to.

Before implementing Catalyze about a year ago, Parsons spent 14 hours developing such a test plan himself for a new application to sell ice-cream cakes. With Catalyze, he says he would have saved those 14 hours. Catalyze automatically converts an application's use-case requirements into a test plan. The test plan is a highly visual format that lets users see what button is clicked on in a particular step and what happens after doing so. The test process, Parsons says, gives users a sense that the sought-after functionality has been delivered as planned--or has failed to be delivered.

Return to the story:
Tools Help Squash Bugs

Read more about:

20052005

About the Author

Charles Babcock

Editor at Large, Cloud

Charles Babcock is an editor-at-large for information and author of Management Strategies for the Cloud Revolution, a McGraw-Hill book. He is the former editor-in-chief of Digital News, former software editor of Computerworld and former technology editor of Interactive Week. He is a graduate of Syracuse University where he obtained a bachelor's degree in journalism. He joined the publication in 2003.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights