If necessary, a Client may carry out their own development in parallel with the project teams. To organize the development process, the Client can use any existing methodology, for example, PRINCE2.
1. General recommendations for Client development process organization
We recommend deploying one or more Client_D development environments for the Client. Please refer to the “Organizing a development environment” article in the Development Guide for more details.
Custom solution development is carried out in user packages. The development process can be divided into two stages: development and implementation.
Development is carried out in the main development environment (Project_D) (Fig. 40). All changes fall into the SVN repository of the Client. Functionality testing is performed in the Test Client environment. At the same time, package transferring between development and testing environments is possible both through the SVN repository of Client and as zip archives (Fig. 41). The use of SVN is recommended for intensive development by several developers. Use .zip archives to develop in the cloud.
Fig. 40 Client’s development process using SVN
Fig. 41 Client’s development process using .zip archives
The new functionality is implemented once both development and testing are done. Packages must be transferred to the pre-production environment first for final testing. If no errors are detected in the pre-production environment, the functionality can be transferred to the production environment.
We recommend using zip-archives to transfer packages with developed functionality to the pre-production and production environments.
2. Communication with project developers
Conflicts usually do not arise if Client functionality does not overlap with project solution functionality (i.e. no scheme / class inheritance, Client packages are not dependent on project solution packages, etc.).
A conflict may arise when project teams make changes if the Client’s functionality depends on project solution functionality. In this case, continuous communication between Clients’s and project teams is necessary.
See also
•Client environment location and licensing
See also
