Industrial Project: course site proposal

Trial results, cost and risks

Confidentiality trials (November 2026)

Each tool was installed and a logged-in student tried every route found to read mentor feedback, including the API directly.

ToolResult
NocoBase 2.2Failed. Direct access was refused, but a student could read all feedback by requesting it as part of a related record.
Frappe Framework 16Passed. Direct access, search, reports, joined queries, comments, change history and file attachments were all refused.

Two limits found in Frappe, and how the design avoids them

Feature checks

CheckResult
Mentors cannot see each other's scores; customers isolated from each otherPass, once "strict user permissions" is switched on
Workflow states restricted by rolePass
Approve a report from an e-mail linkThe link works only after the recipient logs in
PDFs of records (merged feedback, reports)Pass, after changing the PDF generator and giving the server a URL it can reach; access rules apply to PDFs too
E-mail (sign-off requests)Pass, with the scheduler running
Milestone Gantt across all teamsRenders (it had not been seen on screen before this prototype); see the tour
Kanban, number cards, team-by-week gridPass (grid with fixed week columns)
Save and restore a checkpointAbout 5 seconds to save, 20 to restore
Open the site as another user (administrator)Pass; the user is notified

Learned while building the prototype

Cost and effort

ItemCost
Software licencesNone. Frappe Framework is open source (MIT) with no paid edition
HostingNone additional: the coordinator's existing server. Frappe used about 550 MB of memory when idle in the trial
AI usageAn estimated $50-150 per semester for 10 teams over 15 weeks on a mid-tier model. The prototype itself spent nothing: its AI outputs are recorded

Effort, as rough estimates: starting a new semester about half a day; operating it one to two hours a week for the coordinator, more around presentation days.

Risks

RiskMitigation
Student data sits on a personally run serverDaily backups, a documented restore, a handover note; move to university hosting if it becomes available
The process depends on one coordinatorEverything is in two places that can be handed over: the site's database and the playbook repository
Frappe takes more setup than simpler tools; its staff screens are plainAccept for the pilot; students and customers see only simple portal pages
A later change opens a confidentiality holeThe scripted test runs every semester and after every upgrade
AI summaries are wrongSource links on every statement; a mentor approves anything that reaches students
Customers give requirements away or forget what was agreedA one-page playbook; the sealed specification is versioned and the customer can see it
Mentors skip the weekly check-inIt takes two minutes; the dashboard shows when one is missing