The models you've created serve multiple purposes, so don't throw them away! These requirements will not only help you identify candidate packages but also will become the basis for evaluating the candidates. To test how well candidate COTS products will deliver your high-priority features, data, and rules, have vendors execute your scenarios in demos. Remember to grade the candidates on both user and nonfunctional requirements.
Also use your shopping list of requirements when implementing the selected COTS package. Use it to structure your project plan, placing early emphasis on interfaces with other systems. Your requirements models, especially the scenarios and business rules, should be the basis for preparing test cases. Study your "as is" and "to be" process flows to identify where and how users' work will change. This analysis will help you make plans for easing the inevitable challenges that users face when first utilizing new software.
Save yourself aggravation and thrashing by being a savvy COTS shopper. Set the context for your shopping expedition, and use business and user requirements to find products, select the best fit, and implement your COTS solution.
- Gorman, Mary. " Events to the Rescue ," StickyMinds Original, October, 2006.
- Gorman, Mary. " Ready, Fire, Aim: How Timely Interface Analysis Reduces Risk in Software Projects ," StickyMinds Original, November, 2007.
- Gottesdiener, Ellen. The Software Requirements Memory Jogger . Goal/QPC, 2005.