Having quickly formed a project team with relevant experience, we set to work. The customer provided an API that our specialists used to interact with the Mobile SMARTS server.
Mobile SMARTS has client-server architecture with a thick client* and capability for working in the absence of a server. The application mainly consists of tables: documents, nomenclatures, and reference guides. As part of our task, we implemented a function for adding, editing, and deleting records, either individually or several at once.
The table with which users interact is multifunctional, with various filters. The user is now conveniently able to fully customise it for themselves, changing the order of columns and setting various filters.
Per the agreement of the parties, we maintained round-the-clock communication with Cleverence representatives, responded instantly to different changes and offered various solutions to certain situations so that the customer received their desired end result.
The roles in the project were apportioned with the Cleverence representative acting as Product Owner and the OmegaLab project manager acting as Scrum Master. The entire process was wholly transparent, with the customer seeing how the tasks at hand were being solved on a daily basis. This allowed us to react swiftly to changes in the project and instantly suggest suitable options to optimise the tasks, while taking new information into account. We were even sometimes able to anticipate potential difficulties.
The customer requested that the user must be able to create a record identifier on their own. Previously, it was only possible to use data generated randomly by the system. Based on our experience from similar projects, we foresaw a potential bug: the user could create an identifier that already exists and "override" the original. Therefore, we immediately suggested an option to avoid this problem, by setting up validation.