Question
Clearly sourced
Expert knowledge for digital decisions
How does the acceptance of software take place?
Short answer
Based on pre-agreed criteria, not by feel. Common practice includes a test phase with real data and real users, a list of identified deviations classified by severity, and acceptance that does not block minor issues. Anyone discussing criteria only at acceptance time is negotiating at the worst possible moment.
What must be fixed in advance
- Criteria. Which processes must function for acceptance to occur?
- Test data. Test with real data, not with "Max Mustermann".
- Who tests. The people who will later use the system.
- Timeframe. Two weeks is standard, less than that is rare.
Classification of defects
| Level | Meaning | Blocks acceptance? |
|---|---|---|
| A | Process not executable | Yes |
| B | Process possible via workaround | No, with a deadline for correction |
| C | Cosmetic defect | No |
Without this classification, every minor detail becomes a point of contention. A misaligned text must not prevent acceptance; a non-functional process must.
Common errors
Acceptance conducted by people who will never use the system. They click through, find nothing, accept it – and three weeks later, real feedback arrives from daily use.
After acceptance
Warranty periods typically begin with acceptance. What is changed afterward is further development and is separately agreed. This also must be clarified in advance.
Key facts
- Before acceptance
- Agree on criteria and defect classification
- Test data
- Real data, not sample data
- Testers
- The future users, not the management
Sources
All external claims are backed by traceable sources.-
01
Bürgerliches Gesetzbuch (BGB) Bundesministerium der Justiz