All the required functions with respect to device control and visualization will be realized inside the Laboperator Application. For standard use cases, these UI components already exist, whereas customizations might require additional components. Other interfaces are connected devices and barcode readers as input devices and for visual feedback according to their respective support of such functionality.
The web application is fully responsive, meaning it can be viewed and used on any output device independent of the screen size or resolution.
The Laboperator system supports any number of languages and will be deployed with German (DE) and English (EN-US) by default. Additional translations have to be planned individually.
The Connector Box supports up to four devices which are connected to the available USB ports. All other interfaces will be mapped to USB using appropriate adapters provided by Laboperator. Each connector box requires a dedicated power supply. The appropriate power adapters are in the scope of delivery of every connector box. Each connector box will be connected to the customer's network using a 100 Mbit/s Ethernet cable or a Wi-Fi connection.
Database, Cashes & Messaging
For each project, the required third-party dependencies will be bundled with the image provided by Laboperator. All interfaces are part of the image.
All application programming interfaces are HTTP based and usually are RESTful services. All interfaces require authentication and authorization using an access token. Authentication and authorization follow the OAuth 2.0 standard. The Laboperator server offers an extensive API which is documented using the Open API standard version 2.0. Individual messages might be specified and validated using the JSON Schema standard.
The client provides a valid server certificate for the FQDN of the Laboperator server in the client’s infrastructure. The hostname is predefined as “Laboperatorserver”. The client also provides the CA’s root certificate as DER encoded file.
Software Quality Attributes
Any software developed as part of any project will be developed in accordance with Laboperator’s internal quality assurance process. Laboperator combines the risk-based approach to the V-Model with aspects of agile development for flexibility during early phase developments and long-term reliability and robustness.
Low-level quality assurance mechanisms:
- Complete versioning and traceability
- Automated unit tests
- Automated integration tests
- Automated code quality metrics
- Automated environment builds
- Separated test environments for development, staging feature tests and production systems
Some functions make use of email notifications. The server needs the corrects email server settings in order to function correctly. If emails should be delivered via Laboperator’s cloud email server, the client’s server network needs an outgoing internet connection. If the client provides access to a local SMTP server, this internet connection is not necessary to deliver emails.
An outgoing internet connection, which allows SSH tunneling via port 22 to the Laboperator cloud environment might be used for remote maintenance or setup activities by Laboperator, if desired by the client. Otherwise, a VPN connection needs to be provided by the client to allow Laboperator to dial-in via SSH to the virtual machine.