Quality assurance for
3-Year Bug Warranty
New custom software projects include a three-year bug warranty from acceptance for reproducible defects attributable to the original delivery. Work extending existing software is excluded from this standard entitlement. Operations, new features, and environment changes have separate terms.
Wavesteam · Software Quality Assurance
Applies to accepted new custom projects in supported environments; excludes extensions to existing software.
Thirty-six months from acceptance for reproducible bugs attributable to the originally delivered code.
Scope · New custom projects; existing-system extensions excluded
Bug warranty, new work, and operations are different
| Issue type | Typical example | Default classification | Evidence needed |
|---|---|---|---|
| Original delivery bug | An accepted workflow produces the wrong result under the supported environment | Bug warranty if reproducible and attributable to delivered code | Acceptance baseline, reproduction steps, logs, and affected version |
| New or changed requirement | New approval rule, report, role, or integration | New development request | Change description, business value, scope, and estimate |
| Third-party or environment change | Platform API, OS, browser, certificate, or cloud policy changed | Adaptive maintenance; assess responsibility and effort | Change notice, support matrix, impact analysis |
| Operations incident | Capacity exhaustion, expired account, misconfiguration, attack, or data restore | Operations / SLA matter, not automatically a code warranty | Monitoring, change log, account owner, backup and incident record |
Warranty Boundaries
Define what the bug warranty includes and excludes
The three-year warranty starts at acceptance for new custom projects and covers original-delivery defects. Extensions to existing software are excluded. Operations, environment changes, and enhancements have separate service scopes.
Covered Software Defects
An accepted function fails reproducibly in a supported environment because of the originally delivered code.
- Issue detection: online chat, feedback forms and auto log collection across multiple channels
- Diagnosis & localisation: debugging tools, log analysis, database and code review
- Fix delivery: unit + integration + regression tests to ensure fixes introduce no regressions
Environment & Policy Adaptation
Changes caused by operating systems, databases, third-party APIs, or regulation are handled as separate adaptation work.
- Tech-environment adaptation: track OS and database updates, adjust code for new APIs
- Regulatory compliance: monitor policy changes and update data-handling modules accordingly
New & Optimisation Work
New features, changed business rules, performance improvements, and experience optimisation form part of continuing development.
- Feature enhancement: build optimisation backlog from user / market / business needs
- Performance tuning: profile bottlenecks, refactor code, optimise indexes and resources
- UX improvement: iterate UI and interaction based on user research
Operations & Preventive Work
Monitoring, backups, capacity, security inspection, and operational-risk handling belong to the DevOps service.
- Code health check: static analysis to find redundancies and risky modules
- Monitoring & alerting tuning: multi-dimensional thresholds to catch problems early
Standard Process
Four-phase maintenance workflow
01 Intake
Single entry point with triage, classification and priority (High/Medium/Low).
02 Planning
Analyse requirements, estimate effort/resources/time and create a phased plan for approval.
03 Execution
Execute according to plan, log progress and issues, adjust as blockers arise.
04 Acceptance
Submit test report, QA accepts against standards, deploy and collect feedback.
Companion Services
Hands-on support with a dedicated contact
Defect intake and triage
A single intake process records reproduction steps, affected scope, logs, and versions, then assigns priority according to business impact.
Dedicated technical contact
Every project is assigned a Project Manager + Tech Lead as the single point of contact, with severity-based response and handling.
Service coverage
Remote tickets, logs, and release records are the default. On-site work, specific coverage hours, or dedicated on-call require a separate agreement.
Documentation
Full traceability of every maintenance step
Maintenance log
Detailed record of requests, process, owners and timing.
Technical documents
Design docs, user docs and API docs are kept in sync with every software change.
Service scope
- ISO/IEC/IEEE 14764:2022: the published standard covers software-maintenance processes and types, while distinguishing software operation such as backup and system administration.
- System operations are covered separately on the DevOps service page; they are not presented as part of the three-year bug warranty.
- The project proposal and contract define acceptance, supported environments, service coverage, response targets, and delivery arrangements.
Have specific maintenance needs or custom-term questions?
Contact us