How is the server part of the software and hardware device created?

Question

Programming

There is a fingerprint identification device. It is necessary to create a server part (software) that stores and creates users (id, full name, password) with interaction with this device. In what languages ​​is such a system written? What stages does it consist of? Is it possible to create this in a short time (3 months) for a teapot?

Answer 1

In what languages ​​is such a system written?

In any general purpose programming languages.

What stages does it consist of?

From different.

Is it possible to create this in a short time (3 months) for a teapot?

Depends on the kettle. Most probably not.

Answer 2

Each device has its own supplier.
In the projects in which I took part, the vendor provided some software package that gives access to a set of functions with which you can communicate with the device. As a rule, an additional, engineering input is described for debugging software, access to which is either using a special connector or through a well-known standard (for example, I2C)
. In what languages ​​the supplier provides input to the device is usually described in the technical documentation. Typically, machine access protection devices have an output through C++ libraries, this is due to the requirements for integration with I/O devices that are traditionally written for this language.
3 months is an acceptable period for a project where everyone is in place, including a team of professionals, and a new component needs to be implemented.
If you need to write a secure storage for passwords, if you need to write an integration tier with a tier of secure digital products that encrypt and protect content, if there is a (high) probability of changes in other machine components, with which, in turn, this sensor needs to somehow work together, then some external dependencies will take a good 2 months to shrink - truss, that is, I do not recommend taking the responsibility to do everything in 1 month in such a situation.
If the task is simply to establish an exchange of information with a new device, then everything is different. On our project, changing the built-in encryption device to an external network one took 2 weeks from the request to the release of the product on the line and flawless operation.
Much depends on what needs to be done.