Neuentwicklung der EUginius-Datenbankanwendung (EUginius-2.0) inkl. Pflegeleistungen

The contract has an overall duration of 36 months from the award of the contract. There is a one-time option for a contract extension of 12 months.

The start date is stated as "ab Zuschlag" (from the award of the contract), but a specific date is not provided. The end date is 36 months after the contract award.

Key milestones and their estimated durations are:

• Requirement gathering for the EUginius 2.0 database-based web application (MS 1-3): 2 months.
• Completion of the Minimal Viable Product (MVP) including data migration (MS 4-9): 10 months.
• Completion of the EUginius 2.0 database-based web application including data migration (MS 10-11): 15 months.
• Successful tests and acceptance of the provision of the EUginius 2.0 database-based web application (MS 12-15/VE): 18 months.

Additional specific milestones mentioned are:

• Milestone 1: Kick-off-Meeting conducted and documented.
• Milestone 2: Product Backlog including MVP scope, defined and approved by the client.
• Milestone 3: Design documents submitted by the contractor and prototype approved by the client.
• Milestone 12: Completion of all tests and acceptance of EUginius 2.0.
• Milestone 13: EUginius 2.0 deployed.
• Milestone 14: Completion and handover of all relevant project documentation to the client.
• Milestone 15: Project completion and handover of EUginius 2.0 into operation and maintenance.

The maintenance period is expected to be 18 months, commencing either the day after the expiry of the limitation period for claims for defects or the day after acceptance. It ends 36 months after the contract award, irrespective of the acceptance date. The duration of maintenance is the difference between the total 36-month runtime (from award) and the actual development time until acceptance.

The core scope of work and statement of work for this tender involves the development and implementation of the "EUginius 2.0" database-based web application.

Key aspects and deliverables include:

• Project Methodology: The project will utilize a hybrid "Water-Scrum-Fall" methodology, combining agile and classical methods, based on the V-Modell XT Bund (Version 2.3) and agile Scrum project management.
• Initial Project Phases:
• Kick-off Meeting: To establish roles, clarify vision and goals, define project scope and timeframe, and agree on tools and communication channels.
• Product Backlog: All requirements are to be captured, documented, and prioritized in a structured product backlog through a digital workshop, with a clear definition of the Minimum Viable Product (MVP) scope.
• Prototype: Provision of a prototype and potentially wireframes to illustrate central design elements of the web application for early stakeholder feedback.
• Data Migration: This is part of the initial phase and continues with the completion of the MVP.
• Development and Delivery:
• First Functional Increment (Sprint 1): Creation of an initial runnable system state of EUginius 2.0, integrating prioritized requirements from the Product Backlog and establishing the technical basic structure and system architecture.
• Completion of Minimum Viable Product (MVP): Including data migration.
• Completion of the full EUginius 2.0 Database-based Web Application: Including data migration.
• Successful Testing and Acceptance: Of the developed web application.
• Software and Artifact Delivery: This encompasses a reliable version of the complete source code (including DB scripts) in digital form, ensuring it can be imported into Eclipse or IntelliJ IDEA and necessary artifacts (jar, war, ear files) can be generated using MAVEN. Comprehensive source code documentation is also required, along with any additional software needed for installation and basic configuration.
• Documentation: Detailed application documentation, including test protocols, must be provided for operational handover after acceptance.
• Post-Acceptance Services:
• Maintenance: Addressing bugs and delivering new program versions.
• Further Development and Adaptation: Through Change Requests.
• Other specified services: As detailed in Annex C, beyond standard maintenance.
• Tools and Compliance: An open-source Git repository will be used for source code management, and a formal ticketing system (e.g., Jira) for all communication, problem reporting, tracking, and resolution between contractual parties. The entire development must adhere to the client's IT guides and concepts, such as the Online Styleguide, specified in Annex B.