FlowMint Functional Requirements Specification
| Property | Value | |---|---| | Version | 0.1 | | Status | Draft, requirement collection | | Rule | Only confirmed requirements are captured here. New product ideas must not be added without explicit approval. |
Source of truth This FRS is the baseline document for FlowMint. PRD, database design, API design, and frontend/backend implementation should be derived from this document after requirement freeze.
1. Product Overview
FRS-001 Product Name
The product name is FlowMint.
FRS-002 Product Type
FlowMint is a collaborative workflow platform.
FRS-003 Initial Purpose
The first production use case of FlowMint is HackSpire.
The platform will replace Google Forms, Google Drive, and spreadsheet-based submission management used in HackSpire.
FRS-004 Long-term Goal
After HackSpire, the platform will become a standalone SaaS product under Mentitup.
2. Event System
FRS-005 Event Creation
An organizer can create an event.
FRS-006 Workflow Ownership
Every workflow belongs to an event.
FRS-007 Event Registration
Participants can register for an event.
3. Team System
FRS-008 Team Membership
Participants can create or join a team.
FRS-009 Team Members
Each team contains multiple members.
FRS-010 Event Boundary
All members of a team belong to the same event.
FRS-011 Team Leader
Every team has one team leader.
4. Workflow
FRS-012 Event Workflows
Every event contains one or more workflows.
FRS-013 Workflow Tasks
Every workflow contains multiple tasks.
FRS-014 Required Member Completion
All team members must complete every individual task assigned in the workflow.
5. Individual Tasks
FRS-015 Individual Completion
Every team member must complete assigned tasks individually.
FRS-016 Member Responses
Every member submits their own responses.
FRS-017 Proof Uploads
Every member uploads the required proof, such as screenshots, for their own tasks.
6. Shared PPT Submission
FRS-018 Single Shared PPT
Each team has exactly one shared PPT submission.
FRS-019 Team-level Ownership
The PPT belongs to the team, not to an individual member.
FRS-020 Duplicate PPT Prevention
The platform must prevent duplicate PPT uploads from multiple team members.
FRS-021 Team Visibility
The uploaded PPT must be visible to all members of the team.
7. Team Progress
FRS-022 Team Completion Visibility
Every member can view the completion status of all members within the team.
FRS-023 Incomplete Member Visibility
Members can identify which team members have not completed their assigned tasks.
8. Review System
FRS-024 Organizer Review
Organizers can review submitted tasks.
FRS-025 Task Decision
Each submitted task can be approved or rejected.
FRS-026 Individual Review
Approval or rejection is performed individually for each task.
9. Resubmission
FRS-027 Rejected Task Resubmission
Rejected tasks can be submitted again.
FRS-028 Approved Task Lock
Approved tasks cannot be modified.
FRS-029 Rejected Task Editing
Only the rejected task becomes editable during the resubmission period.
10. Submission Phases
FRS-030 Submission Period
The event supports a submission period.
FRS-031 Review Period
The event supports a review period.
FRS-032 Resubmission Period
The event supports a resubmission period.
FRS-033 Final Lock
The event supports a final lock.
11. Final Lock
FRS-034 Submission Lock
After the final lock, submissions cannot be modified.
FRS-035 File Lock
After the final lock, uploaded files cannot be replaced.
12. Storage
FRS-036 Duplicate Storage Reduction
The system should minimize duplicate file storage.
FRS-037 Single PPT Storage
Only one PPT should be stored per team.
FRS-038 Individual Attachment Ownership
Individual task attachments remain associated with the submitting member.
13. Current Scope
This document contains only the confirmed requirements discussed so far.
Additional requirements will be added only after discussion and explicit approval.