For a long time, the ERP vendors in the software development process of choosing a version of the development. This is also the software industry as a conventional development model, so that extreme of course, is Microsoft's windows series. But the agile development model is to adapt to ERP software development model? Version of the development and there what kind of problem?
1, the development cycle is too long: Version of the development, will inevitably require a longer cycle, a large version (NC5.5, EAS6.0) generally required more than six months and even longer time to complete the development. But the market is changing very fast, a longer development cycle makes the new features is difficult in a short time in response to market and waste fighter.
2, maintenance costs continue to increase: the more software version, it means that software vendors need to support the version of the more maintenance. Research and development, implementation, technical support must be given constant input. In order to support the version of the maintenance.
3, R & D costs remained high: In more developed version of the maintenance costs should be the highest. Not only need to maintain all versions of the client's software development needs and patches. Also need new features among different versions of continuous synchronization feature to ensure consistency in all versions. The cost is very scary.
4, the difficulty of upgrading:ERP Software the complexity is very high, the manufacturer's R & D level is far unable to meet Microsoft's level. Version of the upgrade is also no way to be completely smooth upgrade, the customer's individual requirements, as well as the differences between versions are often of the version to upgrade to a customer brings great difficulties. The difficulty is not the technology to upgrade the key. Upgraded the stability and functional correctness of the customer the most anxiety and concern factors. Upgrade once an accident occurs, the impact of the client side to carry out daily operations is important.
Can we eliminate the concept version, based on a stable version or the patch package features the development of model? To go to a version of the development mode. Such benefits include:
1, you can quickly respond to market demands, in a relatively short period to provide customers with capabilities to meet the customer's business needs
2, lower maintenance costs, only need to maintain a version of the larger lower maintenance costs
3, for R & D, the need to maintain multiple versions, and need not constantly in a multi-version of the synchronization and development of the same functional 4, the difficulty in upgrading solved, features package installation and upgrade patch to install than the risk of multiple smaller. For the customer's daily business issues affecting little, even if unforeseen circumstances, the solution has a lower degree of difficulty, timeliness can be increased dramatically.
Of course, to the version of the development there is a problem is that when faced major technological change, does not adapt. For example, a web framework for significant changes in the underlying structure of the major changes and so on. But I think on the current ERP research is to release the development from a cost-oriented and market response is capable of greater benefits.
|
