Before delivery of the final version of each subproject:
- the code must be in Github.com/divvun, with all tests passing
- the code must build on all platforms specified for each subproject
- the code must have been built with all tests passing on at least one of the computers of the Divvun group
- the code, possible API's, setup/configuration and all functionality must be documented
- if relevant, also user documentation must be written in English (the Divvun group will make translations to other relevant languages)
- the code must meet specifications
- the code must follow linting standards agreed upon at contract signing time, or at start-up time for each project
- further acceptance requirements may be specified in each subproject
All tools should by definition support any human language that can be identified with a BCP47 code, unless otherwise specified.
- All code should have an open licence selected by Divvun
- the delivered code must be © UiT
The requirements in the table of requirements form the basis for the Supplier’s description of its solution specification, cf. Bilag 2. The Supplier must give an extensive description of all requirements so that the Parties will have a common understanding of what is to be delivered, or which can give the Buyer alternative perspectives to the requirements expressed in the Buyer’s requirements specification.
The different requirements have different priority.
- Priority A = Absolute requirements that must be fulfilled. Tenders that do not fulfil all the absolute requirements will be rejected.
- Priority B = Important requirements that should be fulfilled, but it is not an absolute requirement. Answers will be of great importance for the evaluation of the tender. The requirements are weighted higher than C-requirements.
- Priority C = Conditional requirements that should be fulfilled, but it is not an absolute requirement. Answers will be of importance for the evaluation of the tender. The requirements are weighted lower than B-requirements.
When filling out the tables of requirements the Supplier shall mark an (X) in the column for yes, partly or no under “the Supplier’s fulfilment”. Reference to relevant documentation and any additional comments shall be made in the column “Comment”. It is reminded that it is the duty of the Supplier to document that it fulfils the set requirements. Any missing documentation will result in the requirement being considered as not fulfilled.
There is one table each for Contract Area 1 and Contract Area 2.
The Supplier shall offer a project team consisting of a project manager and 3-5 other project team members. The offered competence shall be documented by filling out Bilag 2a, one for each of the team members. 3-5 reference projects shall be specified for each of the team members.
| Requirement no. | Priority | Description | The Supplier’s fulfilment (Yes / Partly / No) | Comment |
|---|---|---|---|---|
| 1 | Must-have requirements for project manager | |||
| 1.1 | A | Experience with natural language technology and finite state machines and transducers | ||
| 1.2 | A | Experience with working with minority languages and/or multiple natural languages | ||
| 2 | Must-have requirements for project team members | |||
| 2.1 | A | Solid C/C++ programming experience | ||
| 2.2 | A | Solid Windows, Android, macOS and iOS programming experience | ||
| 2.3 | A | Knowledge about and experience with locales and keyboards in CLDR, Windows, macOS and other relevant platforms | ||
| 2.4 | A | Solid CI and CD experience | ||
| 3 | Should-have requirements | |||
| 3.1 | B | solid mobile keyboards and keyboard apps programming experience | ||
| 3.2 | B | solid desktop keyboards programming experience | ||
| 3.3 | B | solid Objective C/Swift programming experience | ||
| 3.4 | B | solid Rust programming experience | ||
| 3.5 | B | solid Python programming experience | ||
| 4 | Preferable requirements | |||
| 4.1 | C | solid Inno installer programming experience | ||
| 4.2 | C | solid Linux programming experience | ||
| 4.3 | C | solid API & REST design experience |
The Supplier shall offer a project team consisting of a project manager and 3-5 other project team members. The offered competence shall be documented by filling out Bilag 2a, one for each of the team members. 3-5 reference projects shall be specified for each of the team members.
| Requirement no. | Priority | Description | The Supplier’s fulfilment (Yes / Partly / No) | Comment |
|---|---|---|---|---|
| 1 | Must-have requirements for project manager | |||
| 1.1 | A | Experience with natural language technology and finite state machines and transducers | ||
| 1.2 | A | Experience with working with minority languages and/or multiple natural languages | ||
| 2 | Must-have requirements for project team members | |||
| 2.1 | A | Solid C/C++ programming experience | ||
| 2.2 | A | Solid Windows, Android, macOS and iOS programming experience | ||
| 2.2 | A | Solid GUI design experience | ||
| 2.3 | A | Knowledge about and experience with locales and keyboards in CLDR, Windows, macOS and other relevant platforms | ||
| 3 | Should-have requirements | |||
| 3.1 | B | solid mobile keyboards and keyboard apps programming experience | ||
| 3.2 | B | solid desktop keyboards programming experience | ||
| 3.3 | B | solid Objective C/Swift programming experience | ||
| 3.4 | B | solid Rust programming experience | ||
| 3.5 | B | solid Python programming experience | ||
| 3.6 | B | solid Java programming experience | ||
| 4 | Preferable requirements | |||
| 4.1 | C | solid NodeJS and JavaScript programming experience | ||
| 4.2 | C | solid Inno installer programming experience | ||
| 4.3 | C | solid Linux programming experience | ||
| 4.4 | C | solid XQuery programming experience | ||
| 4.5 | C | solid web-app programming experience |
In addition, the Supplier shall also fill out Bilag 2b with a solution description of the three first projects in work package 1, one description for each project. The description shall contain:
- Project plan with milestones and deadlines
- Specification of what is expected as input or deliverables from the Divvun group, with deadlines
- An overview of the organisation of the project team, and the role of the team members and interaction with the Divvun group