Analysis and development of digital e-waybill register used for documenting timber transport.
Since 2006, a waybill must be created for every timber transport. In order to eliminate the physical paperwork, a primary digital waybill information system was developed between 2008-2011, named ELVIS. Due to the high usage, there was soon the demand for a more sophisticated system. Developing an up-to-date engine from scratch instead of patching the primary system seemed a more sustainable way to move forward. For reference – there were 364 251 new waybills created in 2019, and the numbers keep growing each year.
The goal of the new E-Waybill Register (EVR) was to cope with the growing usage of the digital register. The solution was to develop an API with which corresponding organizations could interact (request information regarding or create waybills). Furthermore, the API could be used by supervisory bodies via X-Road.
An additional feature of the solution was also an administrative user interface, which could be used by the system administrators to authorize organizations, manage classifiers and generate various waybill-related reports. The administrative user interface could additionally be used by the organizations’ representatives to manage internal accesses.
The project started with an analysis stage, during which we used the existing system to map the requirements for the final solution. This first stage led to detailed user stories and an architectural model of the desired system. We also developed a prototype for the administrative user interface during the analysis stage.
In order to spot and tackle the potential complications early on, we opted to start the development from the API.
Agile development principles were followed throughout the project. Regular deliveries every 2-4 weeks gave the client the opportunity to test the various features of the solution.
The codebase was kept modular and optimized throughout the development. A well-thought-out architectural design led to a secure and robust solution, which can handle a voluminous amount of data, yet at the same time is easily interpretable and, if necessary, expandable.
The fact that the main focus of the system was a new API made the project exciting, as modern technologies and methodologies could be applied throughout testing. An experienced product owner who had extensive domain knowledge and who was constantly reachable made the whole experience pleasant.
Well-structured work processes and an experienced product owner led to efficient communication throughout the project. This provided a smooth development process which in turn allowed us to keep up with the various intermediary deadlines. Furthermore, constant external and internal feedback strengthened the team spirit.
The most exciting technical challenge involved creating an efficient reporting algorithm based on the big amount of relatively large data models.