Because implementation of e-business systems is more likely to involve incremental development, it's vital that code development and environment/installation planning be tightly controlled to ensure that defects don't creep into the various releases. Coding standards should be adhered to, code inspections/walkthroughs should be carried out regularly, and quality should be ensured through effective testing. Testing should be carried out in all supported browsers and with all PC (or other client) configurations/screen resolutions, and although there may be an emphasis on performance/stress/security/cross-system/cross-organizational testing, in general, the approach to testing should be much the same for e-business systems as it has been for traditional client/server systems. Configuration management and source code control can also be vital throughout the implementation phase.
Installation/delivery must still be thoroughly plannedan e-business system might be developed and working very effectively in-house, but deployment might involve fitting the code around a live environment provided by an ISP. Allow time in the schedule for ISP incompetence, as it's rife! Of course, the client side of e-business installations is often far easier than traditional client/server installations because all the user needs to run the system is a Web browser.