Farm Expense Tracking System
A simple tool for recording farm costs, income, and seasonal profitability.
Feasibility
82
Uniqueness
70
Research
72
Complexity
44
Overview
Problem background: This topic is relevant because it addresses farm expense tracking is often handled manually or with fragmented tools, causing delays, errors, and weak visibility. with a practical academic scope.
Problem statement: Farm Expense Tracking is often handled manually or with fragmented tools, causing delays, errors, and weak visibility.
Aim: To investigate, design, or validate a realistic solution around farm expense tracking system.
Scope: Keep the first version limited to a defined institution, community, or user group.
Expected outcome: A validated proposal direction, prototype or research findings, and supervisor-ready documentation.
Objectives
- Analyse current workflow challenges
- Design a usable digital solution
- Implement core modules
- Evaluate the prototype with target users
Research Questions
- What workflow problems affect current users?
- Which features are most important for a minimum viable solution?
- How usable is the prototype for the target users?
Modules or Features
- Expenses
- Sales
- Season reports
- Export
Tools or Methodology
- Next.js
- PostgreSQL
- Prisma
- Tailwind CSS
- Agile prototyping
- User interviews
- Usability testing
Database Entities or Study Variables
- Expenses records
- Sales records
- Season reports records
- Export records
Possible Diagrams to Generate
- Use case diagram
- System flow diagram
- ERD plan
- Gantt chart
- Methodology flow
- Presentation structure
Proposal Outline
- Background
- Problem statement
- Aim and objectives
- Methodology
- Timeline
Chapter One Outline
- Introduction
- Background
- Problem statement
- Aim
- Objectives
- Scope
- Significance
Presentation Outline
- Problem
- Proposed approach
- Expected output
- Timeline
- Risks