E2 õppija kõnelemisoskuse hindamist toetav kõnetuvastus- ja analüüsilahendus ning võrdlustesti väljatöötamine

The contract timeline includes the following:

• Contract start readiness: The performer must be ready to commence contract fulfillment within one week of the contract signing, unless an alternative agreement is reached.
• Total duration: The final deadline for the work is determined by the time and activity schedule provided in the offer, but it must not exceed 24 months from the date the contract is signed.
• Key milestones/phases: Payments are structured in four stages, each corresponding to 25% of the contract price upon successful completion of the respective stage.

• UTF-8 encoding
• Consistent line ending encoding (Windows CR+LF or Linux/Unix LF)
• Internet Date/Time formats (RFC 3339)
• Unix epoch format for time representation (for certain standards like OpenID Connect, W3C web interfaces)
• Software marked with a license
• MIT license (as a default for software development)
• Openness and free source code principle for software development
• Explicitly stated external dependencies for applications
• Resilience to external system failures
• Technical decomposition of applications (separate versioning and installation for components)
• Separate installation of the database from the application
• Clear separation of public service interface from other interfaces
• HTTP REST machine interfaces (APIs) described in OpenAPI format
• English language for source code documentation, source code, and log messages
• Unit test coverage for source code
• Security testing before production deployment
• Automated tests reporting results in human- and machine-readable formats (e.g., JUnit XML, HTML)
• Application must be agnostic to table partitioning changes
• Application server (e.g., Tomcat) for database connection management (JDBC) using JNDI
• Structured JSON format for logging events
• OpenTelemetry (OTel) standard for log entry content
• English language for logs (excluding user-facing messages)
• Separate configurable security log for critical events
• CNCF OpenTelemetry specifications for telemetry collection
• No special user rights required for database/schema installation
• E-ITS medium security level compliance for systems
• No user access to system operational information (e.g., full file names, stack traces)
• All public network traffic must be encrypted
• TLS environment parameters controlled by administrator
• Unencrypted data transfer allowed only if no confidential/personal data and integrity ensured (signed or timestamped)
• OWASP Top 10 recommendations to be followed
• Secure and http-only session cookies
• SBOM (Software Bill of Materials) list creation
• Accepted SBOM formats: CycloneDX or SPDX (CycloneDX preferred)
• Selection of cryptographic algorithms and methods based on RIA cryptographic algorithm lifecycle study
• Cryptographic algorithms must be replaceable with minor changes
• Key management measures to prevent secrets in source code, logs, or public locations
• Personal data protection requirements (e.g., right to be forgotten)
• Fast browser loading for applications
• High availability capability, with components installable in multiple instances
• Session management solution agreed at project start for high-availability applications
• Session storage in shared file systems (e.g., NFS) is not allowed
• Functional scope defined and documented with explicit use cases
• Language technological analysis (as an experience requirement)
• Language technological experiments (as an experience requirement)
• Development of language technological solutions (as an experience requirement)
• AI application in language learning (as an example of language technological solution)
• Speech technology integration (as an example of language technological solution)
• Language data analysis (as an example of language technological solution)