Description of the processes supporting the software life cycle
1. About RUBIN-T
RUBIN-T software is intended for vehicle monitoring and for transport security at observation sites: monitoring vehicle location, speed compliance, distance travelled, adherence to routes and visits to predefined places, and recording vehicle passages by registration plate.
RUBIN-T is used by organisations and institutions that manage commercial, passenger, freight and specialised transport.
RUBIN-T automates fleet management and reduces operating costs.
2. System requirements
Requirements depend on the volume and content of the data RUBIN-T will work with.
Table 1 — Minimum system requirements
| User workstations | Server hardware | |
|---|---|---|
| Operating system | Any OS supporting current browsers | Ubuntu 24.04 |
| Processor | 2 cores | 4 cores at 2.4 GHz or faster |
| Memory | 4 GB or more | 32 GB or more |
| Disk | 50 GB or more | 1 TB SSD or more |
| Browser | Yandex Browser, Google Chrome, Mozilla Firefox, Microsoft Edge (no more than one year old) | — |
3. The processes supporting the RUBIN-T life cycle
The processes supporting the RUBIN-T life cycle are based on GOST R ISO/IEC 12207-2010 "Information technology. System and software engineering. Software life cycle processes".
The life cycle is supported through development, maintenance and technical support, and includes upgrades carried out both to the vendor's own improvement plan and in response to user requests.
3.1 Development processes
RUBIN-T is developed using agile methodologies for IT projects — Scrum and Agile — and proceeds by versions and sprints according to the planned project and product development tasks.
Development is carried out by a development team comprising the following groups:
- project and product management;
- analysis;
- UX/UI design;
- backend development;
- frontend development;
- testing (QA);
- documentation.
Work proceeds task by task, split into groups — analysis, design, development, testing and documentation — using Redmine for task tracking and control, with a fully defined development process and task status transitions.
Source code is managed in the GitLab version control system.
All development documentation for RUBIN-T is kept in an internal corporate wiki holding everything needed: development details, task statements, test cases, analysis materials, algorithms, architecture and more.
3.2 Maintenance processes
RUBIN-T maintenance covers two directions:
- Technical support for users — gathering feedback and making improvements accordingly.
- Internal audit and product development planning.
Maintenance is run as a separate Redmine task queue covering maintenance, support, request handling and product development, aligned with the development plans for internal products and for external customer projects.
The procedure for contacting technical support is described under Technical support.
3.3 Improvement and update processes
RUBIN-T is continuously developed and updated, both from user requests raised through technical support and through internal audit and the update and development plans.
Users can influence the development of RUBIN-T directly by sending suggestions to help@zone-it.studio or by raising a request in the technical support system.
Every user suggestion is reviewed and registered. If a suggestion is judged effective it is added to the development plan and the corresponding changes appear in a new version of RUBIN-T.
The procedure for installing updates on the customer's side is given under Installation.
4. Required user proficiency
RUBIN-T users need general computer literacy at ordinary user level.
To work with RUBIN-T a user should study the User manual, published at https://docs.rubin-t.ru/ and also supplied with the rest of the documentation on purchase.
5. The personnel supporting the RUBIN-T life cycle
The RUBIN-T life cycle is supported by the development team. Its composition and qualifications are given in table 2.
Table 2 — Personnel supporting the RUBIN-T life cycle
| No. | Area of work | Qualifications | Count |
|---|---|---|---|
| 1 | Project management | Knowledge of budgeting fundamentals, systems analysis, and project management standards and best practice. Understanding of modern information systems and software. Skills in organising team work and managing personnel. | 1 |
| 2 | Backend developer | Knowledge of database management systems at the level of data structure design, function development, administration and optimisation (PostgreSQL, ClickHouse, Redis and others). Command of Ruby, Python and Java. At least 5 years of commercial development experience. | 1 |
| 3 | Web developer | Command of JavaScript. Knowledge of modern frontend frameworks (React and/or Vue). At least 5 years of web application development experience. | 1 |
| 4 | Interface designer | Experience in user interface design. Command of graphics editors and prototyping tools. Knowledge of the Figma interface design system. | 1 |
| 5 | Lead systems engineer | Experience administering web servers, proxy servers and message brokers. Confident knowledge of Ubuntu-family operating systems and containerisation technologies (Docker). Experience designing, deploying and maintaining computer networks and IT infrastructure across the whole system life cycle. | 1 |
| 6 | Tester (QA engineer) | Experience developing automated tests and performing functional and load testing of software. | 1 |
| 7 | Business analyst | Knowledge of software analysis and development methodologies. Command of business process notation. Experience with API testing tools (for example Postman). | 1 |
| 8 | Technical writer | Command of office suites (MS Office), documentation management systems (for example Confluence), the Markdown markup language and documentation generation tools (for example Docusaurus). Experience producing technical documentation to the GOST 19 and GOST 34 standards. | 1 |
| 9 | Technical support staff | Experience administering web servers (Nginx), proxy servers (Squid) and message brokers (RabbitMQ, Kafka). Confident knowledge of Ubuntu operating systems and Docker containerisation. | 1 |
6. Physical address of the development infrastructure, developers and support service
Apt. 280, 1 Proletarsky Prospekt, Moscow, 115522, Russia.
7. How to contact technical support, and its working hours
Requests are accepted through the technical support system at https://help.zone-it.studio/ or by email to help@zone-it.studio.
Requests are accepted around the clock, but they are processed and errors fixed on working days per the official calendar, from 9:00 to 18:00 Moscow time.
Technical support provides the following services:
- assistance with configuration and administration;
- fixing faults found in operation;
- general advice on use;
- provision of documentation;
- upgrading and improving the software.
The detailed procedure for raising a request is given under Technical support.
Printable version
The PDF edition of this document is available in Russian:
⬇ Download PDF (RU)