Specificity of the development and improvements on the “1C: Enterprise” platform
A huge advantage of the technology platform “1C: Enterprise” is the openness of the program code. Almost all standard 1C software products can be modified to meet customer requirements. At the same time, it is very important to conduct development based on the typical functionality of the product so as not to violate its business logic and updatability. That is why our 1C developers always evaluate improvements together with consultants, which allows us to offer balanced decisions on changing typical configurations.
HOW WE IMPLEMENT 1C SYSTEM SOFTWARE IMPROVEMENTS
Stage No. 1. Formalizing business requirements and preparing development requirements specification. To assess the task of drawing up development specifications, communication is carried out with the direct customers of the functionality, and such communication can be either remote or conducted as a personal meeting. Be sure to analyze the existing 1C base to be finalized in the future. Next, an assessment of the writing of the development specifications and the development itself is performed. The writing of development specifications is carried out in strict accordance with the requirements of 1C and is agreed with the customer in stages.
Stage No. 2. Programming.
- Development and testing of new functionality is usually carried out in several stages. At the beginning, the test circuit is deployed on our own resources. It is an exact copy of the Customer’s configuration on which the development will be carried out. If desired, the test circuit can be deployed on the Customer’s resources.
- Next, development of the functionality according to the development specifications within the framework of the test circuit is performed directly. After development, our consultants conduct testing and internal acceptance of the work.
- The product’s functionality in the form of a test base is transferred to the Customer for testing. The Customer shall carry out testing and acceptance of work within the specified and agreed deadlines.
- After accepting it as a test base, we transfer the product’s functionality to a working base, taking into account minimal consequences for the current operations. If the development results are transferred by a large package, then it makes sense to use the so-called release approach. That is, only after preparing the release description, instructions for working with the new functionality, and user training, the functionality can be transferred to the working configuration.
Stage No. 3. Warranty period operation
For all the works in connection with the improvements, we give a warranty period of 1 year. If there are errors that are actually associated with incorrect code operation and deviation from the development specifications, we will eliminate them at our expense. The software code that we are developing comes with documentation.
It is very important to understand what objects of the system were modified, including the time and the scope of their modification. Of course, the preparation of such documentation is an additional labor, but it is justified when it comes to system maintainability and future projects for the transition to a new generation of the systems.
