Skip to main content

Functional Requirements

These are the capabilities live in the DeSIC Platform today, derived directly from stakeholder interviews and process observation at the Centre. Every item below is implemented, not planned — for what's still ahead, see Roadmap.

Authentication

Role-aware login for innovators, mentors, and administrators, with error feedback distinguishing invalid credentials from an invalid role for the requested area.

Innovator profiles

Registration and profile management scoped to an innovator's current incubation stage, with restricted access to their own data only.

Application management

Administrators filter, review, and decide on incubation and event applications, with decisions reflected immediately in the applicant's dashboard.

Mentor assignment

Mentors are matched and assigned to innovators based on incubation level and domain, with the assignment logged for auditability.

Notifications

Automated notifications, including grouped notifications sent to sets of users at once, across in-app, email, and SMS channels.

Reporting

Downloadable CSV reports and a filterable analytics view for tracking incubation activity over a chosen date range.

Primary use cases​

The functional design centers on three actors — Innovator, Mentor, and Administrator — and the following primary use cases, all implemented:

  • Innovator registration and profile management
  • Incubation program application
  • Event registration and management
  • Mentor assignment and management
  • Progress tracking and reporting
  • Notification and communication

Key workflows​

Application review​

  1. An administrator opens the pending applications queue and filters by status or incubation domain.
  2. The system surfaces each application's details and history for review.
  3. The administrator approves or rejects the application.
  4. The applicant receives an automated notification of the decision.
  5. On approval, the system automatically provisions an innovator account, which the new innovator uses to complete their profile.

Mentor assignment​

  1. An administrator opens the innovator management panel.
  2. The system suggests mentors based on domain matching against the innovator's stated interest area.
  3. The administrator confirms a suggestion or selects a mentor manually.
  4. Confirming an assignment updates the database and triggers parallel notifications to both the mentor and the innovator.
  5. The assignment is recorded in an audit trail for later review.
All primary use cases implemented