Back Office UAT — iDARMS Frontend¶
Integrated District Assembly Revenue Management System Phase 3 – Segment 1
This controlled documentation supports business-led User Acceptance Testing for the iDARMS Back Office application (iDARMS Frontend), including menu navigation, sidebar controls, module functionality, admin panel, infrastructure, and end-to-end journeys.
Document status
Version: 1.0 Status: Ready for UAT execution Classification: Controlled UAT Copy Credentials: Not included
Coverage¶
| Area | Test series | Cases |
|---|---|---|
| System Infrastructure Setup | INF |
12 |
| Frontend Admin Panel | ADM |
20 |
| Back Office menu destinations | BO |
90 |
| Back Office sidebar/access controls | BO-NAV |
8 |
| iDARMS Frontend Overview & Sidebar | IDA-NAV |
8 |
| iDARMS Frontend Authentication | IDA-AUTH |
8 |
| iDARMS Frontend Dashboard | IDA-DSH |
8 |
| iDARMS Frontend Property Management | IDA-PRP |
8 |
| iDARMS Frontend Rate Payer Information | IDA-RTP |
6 |
| iDARMS Frontend GIS Mapping | IDA-GIS |
4 |
| iDARMS Frontend Communication | IDA-COM |
8 |
| iDARMS Frontend Bill Management | IDA-BIL |
9 |
| iDARMS Frontend Payment Management | IDA-PAY |
5 |
| iDARMS Frontend Accounting & Finance | IDA-ACC |
10 |
| iDARMS Frontend Dispute Resolution | IDA-DSP |
8 |
| iDARMS Frontend Entity Management | IDA-ENT |
8 |
| iDARMS Frontend Block Management | IDA-BLK |
2 |
| iDARMS Frontend User Management | IDA-USR |
10 |
| iDARMS Frontend System Setup | IDA-SET |
12 |
| iDARMS Frontend Account Settings | IDA-PRO |
5 |
| End-to-End Journeys | E2E |
10 |
| Total | 239 |
How to use this site¶
- Review the UAT scope, roles, entry criteria, environment, and evidence rules.
- Validate the Back Office sidebar, routes, and permission visibility.
- Assign acceptance-test pages to the appropriate business testers.
- Execute each test against the recorded release/build and controlled data.
- Record result, actual outcome, evidence, and defect reference.
- Retest fixes and execute affected regression cases.
- Complete the final acceptance decision and sign-off.
Result values¶
| Result | Meaning |
|---|---|
PASS |
Expected business outcome achieved with acceptable evidence. |
FAIL |
Actual outcome materially differs from the expected result. |
BLOCKED |
Execution cannot continue because a prerequisite or dependency is unavailable. |
NOT RUN |
Case has not yet been executed. |
N/A |
Case is not applicable and includes an approved justification. |