Softwaredesign
Den vigtigste del i indstillingen eller visualiseringen af enhedsdata fra en mobiltelefon (Android eller IOS) eller pc (Windows, Linux) er et program, der kommunikerer med enheden via USB, WIFI, BLE, Ethernet eller en anden protokol.
ContactNøglefunktioner
Sprog
Java / Kotlin / C# / C/C++ / Python / Java Script
Diagrammer
Blok / UML / Workflow / API'er
Grænseflader
USB/Ethernet
Protokoller
MQTT / HTTP / FTP / Modbus TCP/RTU / SNMP / TCP/IP / UDP/IP / DLMS / brugerdefinerede protokoller
Trådløs
BLE / WiFi / UWB
Sikkerhed
AES / SSL/TLS
Biblioteker og frameworks
GStreamer / Paho MQTT / WolfSSL (SSL/TLS) / Mbed TLS (SSL/TLS) / QT framework / .NET MAUI / Xamarin Forms og Maui / ASP.NET Core og webudvikling / React (udvikling af web-UI) / SQLite DB / FireBase DB / Mong DB / InfuxDB DB / Room / TensorFlow / Node.js
DU
Android / iOS / Linux / Windows
Værktøjer, vi bruger
QT
Visual Studio
GCC (Linux og Windows)
Android Studio
Projektproces
Requirements design
As the first step our team makes technical requirements of the software, it describes all technologies (database, communication protocols, Frameworks, GUI, architecture of each module) and logic of the work
Diagram design
At this stage, we do architecture design based on the requirements. It usually includes: a software block diagram, a workflow diagram (describe deep logic of the work), and a UML/API diagram(describe all files and code classes/modules)
Start code development
In this stage, we divide the scope of the work based on the UML/API into small sprints (usually 2 weeks each) and make planing with the delivery of each part. Each week make small delivery of the code based on the planning
Code review and testing
If the project has enough code size and budget (we have rules), a responsible engineer does a code review. After that’s QA engineer tests all the code files rather manually or by writing the tests.. For the current steps, we use the standard GIT mechanism with merge request and management schema from Jira
Code delivery
When some parts of the code is done and it’s agreed with the customer - we deliver (release) the software. Use usually for this GIT standard mechanism of the delivery/release code and GIT tags. The delivery includes full development of the current stage, code review, full regression testing and a demo project that shows how the current part of the code works
Finalizing code development
It’s the last stage of the development, on this stage we finish the development, code review and testing of the final code. we make sure that we fit the technical requirements and expectations with the customer. Especially, all our software are based on the device control(BLE, USB, CAN, WIFI, etc) and in this case, we need to make sure all works well and final testing was done with the last device version
Support and bug fixing
Each project has a support stage and bug fixing because after a final release, will need some improvements. We usually agree with the customer on a period of support. It could be how a few months and a few years (if a complicated project)

