Vienotas sabiedriskā un kravu transporta pārvaldības, pārvadātāju administrēšanas, un lietotāju apziņošanas informācijas sistēmas izstrāde un ieviešana

The contract timeline indicates that the developer must prepare and agree on a project management and time plan with the Client within two weeks after the contract signing date, or by a term otherwise agreed with the Client. The implementation of the system development work is recommended to be planned and executed in several releases, delivering functionality realized within sprints. The developer is to plan and propose the start of each release and the sequence of work within it, with all releases being subject to the terms outlined in requirement ORG-7 concerning system implementation and general conditions. While the documents mention a "contract validity period (from – to)" in the context of contract versioning and a list of executed contracts, the specific start date, end date, or total duration for *this* contract are not explicitly stated.

The core scope of work for this tender involves the comprehensive development and implementation of a system, guided by a structured project management methodology. Key activities include project management, system architecture definition, software requirements analysis, system design and development (including inter-system interfaces), various types of system testing (functional, integration, usability, security, performance), and the administration of test and pre-production environments. The tender also requires providing training for system administrators and users, and ensuring the operational functionality and data exchange interfaces as specified.

The Statement of Work summary and core deliverables encompass both tangible software components and extensive documentation:

• Project Planning & Management: Development and ongoing maintenance of a Project Management and operational time plan, and project execution according to an internationally accepted project management methodology.
• System Development: This includes the creation of a system architecture description, software requirements analysis documented as user stories, detailed system design and development, and the provision of necessary third-party software licenses.
• Testing and Quality Assurance: Functional, integration, usability, security, and performance testing of the system.
• Deployment and Administration: Administration of test and pre-production environments, and ensuring automated delivery and installation of software to both test and production environments.
• Training: Training for system administrators and users.
• Documentation Deliverables: A comprehensive set of documents including Project Management and Time Plan, Architecture Description, Software Requirements Specification, Software Design Description, Requirements Traceability Matrix, Data Migration Plan, Testing Plan, Testing Summary Report, Acceptance Testing Scenarios and Test Cases, Administrator Manual, User Manual, System Interface Design Descriptions, and any other agreed training or graphical materials.
• Software Deliverables: Delivery of the developed software, including source code, executable files, configuration files, and necessary software licenses, with version identification and control.
• Release Management: The work is planned in multiple releases, with each release incorporating sprint-realized functionality, user and administrator training, documentation delivery, and acceptance testing.
• Sprint Activities: Each sprint involves identifying backlog items, planning, analysis, development, testing, functionality demonstrations, delivery to test environments, customer testing, bug fixing, and re-testing.