Architecting a Solution
We first developed an architecture diagram presenting technologies, workflows and outputs. The solution was reviewed with the client’s main stakeholders to verify the path forward, and consensus was reached.
Addressing Stability Concerns
One area of concern the client brought to us was in avoiding ‘flavor of the month’ technology. They needed stable, best-of-breed, established technology that would meet the needs of their end users, as well as be simpler to maintain. For this reason, we chose to build a simple Electron app with an HTML React front-end on an expandable platform for future work. The inputs would be captured, which would lead to the Python process being spawned with the JSON inputs as an argument.
Documentation
The client wanted to have a collaborative working relationship with us that allowed their development team to learn from our expertise in the field. To this end, regular code reviews and demonstrations of progress were held, and documentation was created and consistently updated. Not only did this guarantee that we were working toward the same end-goal as the client, but it also enabled us to improve the skills of the client’s development team. Final markdown documentation was provided so the client could add it to their Git repo.
