Yuriy Tomaev
Key roles ←

Systems Analyst

I translate business needs into technical specifications, data models and API contracts. I define system logic, component interactions and error scenarios, analyse existing solutions, support development and verify that implementation meets requirements.

Contact View résumé
Systems Analyst

What I can take on

Detail requirements for development

  • I specify system functions, scenarios, rules and constraints. I clarify data and operation conditions so developers receive an agreed technical specification.

Design data models

  • I define entities, attributes, relationships, keys and integrity constraints. I design new database structures and changes to existing ones, considering module evolution and data exchange.

Model system logic and behaviour

  • I model scenarios, object states, operation sequences and component interactions. I use UML Use Case, Class, Collaboration, Activity, Sequence and Statechart diagrams to clarify complex logic and identify contradictions before implementation.

Design APIs and integrations

  • For internal interfaces, I define requests, responses, attributes and validation rules. For external services, I analyse existing contracts and design their interaction with the system.

Define error handling and access rules

  • I specify alternative scenarios for failures, invalid responses and repeated requests. I define the access, logging and error-handling rules needed by the system.

Analyse existing systems

  • I reconstruct data structures and solution logic, including undocumented systems. I investigate tables and fields, identify dependencies and design changes for new requirements.

Support implementation and validate results

  • I refine specifications during development and investigate discrepancies. I test APIs and data, write SQL test scenarios and compare results with expected system behaviour.

Experience and results

2024

Cezyo

I designed an e-commerce system, from functional specifications and seller data imports to a multi-warehouse cart, delivery and localization. I documented component interactions and alternative scenarios and supported implementation by developers.

View project →

Functions

  • Requirements decomposition and documentation
  • Multi-warehouse order design
  • Integration and error-handling design
  • Integration and data-quality requirements
  • Localization design

Results

  • The food-delivery service integration was implemented, tested and deployed, including handling of failures and invalid responses.
  • Seller data imports and delivery selection worked; the multi-warehouse cart was validated with test data. Integrations with major carriers, including CDEK, were exercised in a test environment.
  • My specifications were used to implement localization with dynamic language addition, translator interfaces, developer-entered translations and loading of keys and translations into the database.
2007

TIK Region

Contributed to selected requirements for SMEV and ESIA integrations, distributed access, personal data protection and increased load. Aligned product needs with platform capabilities. The technical director and specialist team owned architecture and its development. The team used Java and Oracle for production development.

View project →

Functions

  • Requirements decomposition and documentation
  • Electronic data exchange requirements
  • System behaviour modelling
  • Integration and error-handling design
  • SQL scenario testing

Results

  • Implemented ESIA sign-in for system staff and citizens.
  • Implemented interagency exchange and staff access confirmation for a citizen’s case file using a code sent to the citizen’s phone.
2017

Hobby Express

Investigated an off-the-shelf product with no documentation: examined its database structure and relationships, reconstructed the data model and worked out changes with developers. Adapted reference data, product cards and seller accounts, and redesigned the frontend and forms. Specified seller data imports and connections with internal 1C and accounting, the selected bank and delivery processes. The technical team used JavaScript, PHP and MySQL; my responsibilities were analysis, requirements and implementation coordination.

View project →

Functions

  • Existing database reverse engineering
  • Seller process and data-source discovery
  • Data model design
  • Business rules and calculation algorithms
  • Integration and data-quality requirements

Results

  • Reconstructed the database structure and relationship logic of an undocumented off-the-shelf solution. Adapted reference data and domain-specific product attributes, expanded seller accounts and supported dispatch from sellers' own warehouses.
  • Bulk product-data imports from multiple sources replaced manual entry of individual product cards.
  • Imports through APIs, Excel and 1C integration were used with sellers’ actual product data.
2019

GuideInfo.ge

Using my knowledge of the shared system architecture, prepared database structure specifications based on user needs and compatibility requirements with Sweet Georgia. Defined guide, excursion, reference and availability data so users could work in both services with one account and information changes would be available in both. Developers and DevOps implemented the changes. The Sweet Georgia portal published the same guides and excursions and used the same guide availability calendar as GuideInfo.

View project →

Functions

  • User Scenarios / Use Cases
  • System behaviour modelling
  • Data model design
  • Interface, access and logging design
  • SQL scenario testing

Results

  • GuideInfo and Sweet Georgia worked together through a single user account, consistent guide and excursion data, shared reference data and an availability calendar. Information and its updates were used in both services.
  • Guides published excursions with photographs, schedules, prices, group conditions and dates. Travellers could choose a guide or excursion, message the provider and place an advance order; agencies contacted guides directly. Audio tours and remote consultations called 'Give me advice' were available.
  • The service used JavaScript, Framework7, Vite, Cordova and MySQL. The backend initially used PHP and was later migrated to Python/FastAPI, earlier than in Sweet Georgia. The technical team implemented the agreed scenarios and requirements.
2014

Sweet Georgia

Prepared implementation documentation myself: scenarios, use cases, actors, class models, entities, attributes and relationships. Worked out the data structure and created UML models in Rational Rose, supported by diagrams, tables and examples from real trips. Specified the use of partner data: exchange rates from the central bank of Georgia and TBC Bank, information from Aviasales and Booking.com, and fuel prices from a partner filling station network.

View project →

Functions

  • Data model design
  • System behaviour modelling
  • Functional decomposition

Results

  • Developers received detailed functional specifications and data models for implementation. The system used updated service prices and exchange rates to calculate trip costs.
1997

Ivacon

Personally developed most of the software in VBA using Microsoft Access, with data storage and SQL queries in Microsoft SQL Server; used ODBC to connect Access to the server database. Implemented warehouse accounting, material movements, order and cost accounting, exports to BEST and imports of calculation data from CAD software. Developed material consumption and waste formulas with production technologists and built daily, ten-day, monthly and quarterly reports.

View project →

Functions

  • Data model design
  • Software development
  • Integration and data-quality requirements

Results

  • Employees entered source data at their workstations for shared accounting. Direct costs, overheads and selling expenses were collected by order, and data was exported to the BEST accounting software.
  • The economic planning department, accounting department and management received reports and analysis from a shared database. Local data was updated as it was entered, while branch data arrived daily, giving management the previous day’s results.

Competencies and tools

Analysis and requirements: 13 · Development and AI: 16

Analysis and requirements

Planning and management

Data and databases

Integrations

Analysis and design artifacts

Development and AI

Ways to work together

Staff role

I join a team building or evolving an information system, taking responsibility for system requirements, data models, integrations and implementation support.

Project engagement

I design a system or subsystem: specifications, data, APIs and algorithms. I support handover to development and validation of the agreed outcome.

Consulting and system review

I help analyse an existing solution and identify gaps and contradictions in requirements, data and integrations. I prepare recommendations for changes and technical specifications.

Publications

Testimonials and recommendations

I have known Yuri since the development of the E-city project. I know him to be a successful manager and organizer. When the need arose, I brought him on board to help bring the first release of our project to its production-ready version. I would like to highlight his accuracy in estimating timelines—the actual timeframes matched his projections exactly. I also want to note his ability to manage communication across the board—engaging effectively with the owner, senior management, business units, external partners, and the development team. Thanks to him, many tasks were completed almost seamlessly and within a very tight timeframe.
Павел Баканов Executive Director, Hobby-Express 2017-2018
e-CityHobby Express

Let’s discuss the task

None of these roles is an exact match? Write to me — we can discuss your task and choose a suitable way to work together.

Contact →
info@syscreator.org