Agri-Energy
Connect
Individual ASP.NET Core project modelling farmer and employee workflows and product management.
- My role
- Individual Academic Developer
- Build window
- 2025
- Evidence state
- Public repository
- Result proof
- 77% (PD)
- Primary stack
- ASP.NET Core MVC
What was delivered
An individual academic capstone that models farmer and employee product workflows, community activity and accountable system records.
- Farmer-facing product creation and management flow
- Employee and Admin paths for relevant farmer and product administration
- Forum, dashboard visualisations and language switching for English, Afrikaans and isiZulu
Developer view
A role-aware ASP.NET Core MVC application on .NET 9.0 with EF Core, SQLite, Identity and an auditable service boundary.
- Used controller and Identity boundaries to separate Farmer, Employee and Admin workflows
- Persisted domain records through EF Core and SQLite, with audit activity connected to product changes
- Configured English (South Africa), Afrikaans and isiZulu resources for the user-facing interface
Project context
My individual academic capstone modelled how farmers and employees could manage products and accountable system activity in one application.
An individual ASP.NET Core MVC academic project modelling farmer and employee workflows, product management, a community forum, dashboard visualisations and audit activity. The public repository documents ASP.NET Core Identity roles, Entity Framework Core with SQLite and language switching for English, Afrikaans and isiZulu.
Individual academic capstone project (POE) with publicly inspectable implementation and demonstration material.
My contribution Designed and built an inspectable ASP.NET Core MVC project demonstrating role-based workflows, data persistence and localisation.
Contribution and Evidence
Awarded 77% (PD) for the individual academic project
Developed an ASP.NET Core MVC solution targeting .NET 9.0 with EF Core and SQLite
Implemented Farmer and Employee roles using ASP.NET Core Identity
Built product management, forum, dashboard and audit-activity functionality documented in the repository
Implemented language switching for English, Afrikaans and isiZulu
Engineering reflection
- The repository pattern adds upfront complexity but pays off when the data layer needs to change
- Localisation should be planned from the start — bolting it on later doubles the work
Technical Stack
Architecture Note
Role-aware MVC application
Inspected source shows a structured ASP.NET Core application with role-gated workflows, persisted domain records and auditable product activity.
- Layer01
Access
ASP.NET Core Identity establishes Farmer, Employee and Admin role paths.
- Layer02
Workflows
MVC controllers handle products, farmer records, forum discussion and audit-log review.
- Layer03
Persistence
EF Core with SQLite stores farmers, products, forum replies, audit logs and notifications.
- Layer04
Cross-cutting
Product changes call AuditService, while resources configure English (South Africa), Afrikaans and isiZulu support.
Farmer product creation workflow
- 01
Farmer identity
An authenticated farmer enters the role-scoped product route.
- 02
Controller guard
ProductController checks that the submitted farmer belongs to the signed-in user.
- 03
Data write
EF Core saves the product record against the farmer relationship.
- 04
Activity trace
AuditService records creation and ProductNotifier triggers its registered observer.
An isolated validation run passed 18/18 xUnit and WebApplicationFactory tests without compiler warnings on 28 May 2026 after repairing the MVC cookie/JWT authentication split, Identity Razor Page tag-helper imports and source-quality warnings.
Derived from source inspected on 27-28 May 2026. This describes implemented boundaries and isolated local validation, not live production operation.
Project Identity
