Denis Urs Rudolph
39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Payment recording
|
|
The system SHALL record payment details for event registrations.
|
|
|
|
#### Scenario: Record cash payment
|
|
- **WHEN** organizer records cash payment for registration
|
|
- **THEN** system stores payment amount, date, and method
|
|
- **AND** updates registration payment status
|
|
|
|
#### Scenario: Record online payment
|
|
- **WHEN** system receives payment confirmation from payment processor
|
|
- **THEN** system records transaction ID, amount, and timestamp
|
|
- **AND** marks registration as paid
|
|
|
|
### Requirement: Payment status tracking
|
|
The system SHALL track payment status for each registration.
|
|
|
|
#### Scenario: Unpaid registration
|
|
- **WHEN** registration has no recorded payment
|
|
- **THEN** system displays status "unpaid"
|
|
|
|
#### Scenario: Partial payment
|
|
- **WHEN** registration has payment less than required amount
|
|
- **THEN** system displays status "partial"
|
|
- **AND** shows remaining balance
|
|
|
|
#### Scenario: Fully paid
|
|
- **WHEN** registration payment equals or exceeds required amount
|
|
- **THEN** system displays status "paid"
|
|
|
|
### Requirement: Payment reporting
|
|
The system SHALL generate payment reports for organizers.
|
|
|
|
#### Scenario: Event payment summary
|
|
- **WHEN** organizer requests payment report for event
|
|
- **THEN** system displays total collected, pending, and outstanding amounts
|
|
- **AND** lists all registrations with payment status
|