Developing and Deploying Siebel Business Applications > Guidelines for Testing a Deployment > Process of Modifying Siebel Objects >

Guidelines for Continuous Improvement


It is recommended that you use the following guidelines during continuous improvement:

  • Use a repeatable, measurable, and documented process. For more information, see Figure 28.
  • After the initial deployment, Oracle delivers periodic configuration changes in new releases. You must test these configuration changes.
  • Identify a suite for your regression test. To identify regression problems that might be introduced, this suite provides an abbreviated set of test cases that you can run with each delivery. Streamlining the regression test process helps you to incorporate changes in the Siebel application at a much lower cost.
  • Review the testing strategy and objectives. A full review of the open and closed problems can help calibrate the risk assessment you perform earlier in the product development lifecycle.
  • Measure the observed risk that specific components cause. For example, identify the component that introduces the largest number of problems.
  • Perform a final review meeting. This post-mortem meeting allows you to identify future improvements you can make.
  • Review test plans and test cases. Update test cases to include testing scenarios during testing that were not previously identified.

Figure 28 illustrates the continuous improvement process.

Figure 28. Continuous Improvement Process
Click for full size image
Developing and Deploying Siebel Business Applications Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.