Requirements & QA for Accounting System
Requirements & QA for Accounting System
During my internship, I worked on requirements gathering and flow analysis for an internal accounting application that was replacing the company's previous accounting software. I met with business users, documented their needs, and translated them into flowcharts to guide the development team.
The biggest challenge was the system's interconnected General Ledger: every transaction type (sales, purchases, returns, receipts, payments, inventory adjustments) posts to multiple linked accounts at once, and some processes, like asset depreciation, span several transactions across different menus that all had to stay consistent with each other. Validating that logic took a lot of back-and-forth with business users and the development team.
My role was on the requirements and QA side rather than development: I wrote automated test scripts and ran User Acceptance Testing (UAT) with the business users before each release. I didn't have access to the codebase or the system's internal implementation, so this case study covers the requirements and testing process rather than technical architecture.
Let's Work Together
Let’s start to capture the wonderful moments of your life.
Process & Deliverables
The internship followed a requirements-to-UAT cycle, producing:
- Business requirements gathered from users
- Flowchart
- Validation of interconnected General Ledger transaction flows
- Automated test scripts
- User Acceptance Testing (UAT)
My involvement was limited to requirements, flow documentation, and testing. I did not have access to the system's codebase, database, or repository. Company details have been generalized to respect confidentiality.