Document Platform Logic & Use Cases
Budget: $750 – $1,500 CAD
Our product is a web-based solution running a Java back-end, an Angular front-end, a MySQL database and AWS infrastructure. I need a clear, two-part knowledge base that captures exactly how everything fits together.
First, I want a business-level report that walks through every core use case: who uses each feature, what problem it solves, and the high-level flow a stakeholder would recognise.
Second, I need a technical companion that inventories the system in depth—every stored procedure, REST or internal API, UI screen and the code logic that powers it. Page by page, describe what the user sees, what happens in the controllers and services, and how data is read or written. The goal is to let any new developer or analyst open this document and understand immediately how a particular task is accomplished, right down to the database call.
Please base your analysis on the current codebase and schema, inspect the AWS environment where relevant, and surface anything unusual (dead code paths, duplicate queries, etc.) that might matter to performance or future refactoring.
Deliverables:
• Business Use-Case Report (searchable PDF or Markdown).
• Technical Inventory & Flow Document with diagrams where helpful (draw.io, Lucidchart or similar).
• A short hand-off call or recorded walkthrough so the team can ask follow-up questions.
I’ll provide repository access, database credentials and an AWS read-only account as soon as we start.
First, I want a business-level report that walks through every core use case: who uses each feature, what problem it solves, and the high-level flow a stakeholder would recognise.
Second, I need a technical companion that inventories the system in depth—every stored procedure, REST or internal API, UI screen and the code logic that powers it. Page by page, describe what the user sees, what happens in the controllers and services, and how data is read or written. The goal is to let any new developer or analyst open this document and understand immediately how a particular task is accomplished, right down to the database call.
Please base your analysis on the current codebase and schema, inspect the AWS environment where relevant, and surface anything unusual (dead code paths, duplicate queries, etc.) that might matter to performance or future refactoring.
Deliverables:
• Business Use-Case Report (searchable PDF or Markdown).
• Technical Inventory & Flow Document with diagrams where helpful (draw.io, Lucidchart or similar).
• A short hand-off call or recorded walkthrough so the team can ask follow-up questions.
I’ll provide repository access, database credentials and an AWS read-only account as soon as we start.