The overall concern of transition is with changing the business and its systems together to support a new set of business requirements.
Although transition is still some way off at this point, you should consider the transition strategy now. If a strategy has already been produced during analysis, it should be reviewed and revised.
The following transition issues are critical:
Duplicate maintenance may be required to synchronize the old and new databases, and possibly to integrate them, which will also require maintenance. Such duplicate maintenance could be handled dynamically, or synchronization transactions may be batched.
The decisions are largely dependent on the organization, but the intent here is to fire the imagination to consider transition issues.
These considerations may yield a requirement for some special procedures to be designed for transition, or may point out some special transition logic to be addressed during procedure logic design.
Identifying and addressing transition issues at this point helps you avoid later unpleasant surprises for the user.
Copyright © 2013 CA.
All rights reserved.
|
|