WEEK 1 TEMPLATE: Project Idea Finalization & Team Registration
Section A – Group Information & Monitoring Log
Field Details
Week 1
Milestone Project Idea Finalization & Team Registration
Group ID / Team Name
Student Names, Roll Numbers, 1. Aryan Suri, 2210991390, 9872786282,
Mobile No. and Email ID: aryan1390.be22@[Link]
[Link] Singla, 2210991215, 6284577645,
akashdeep1215.be22@[Link]
Project Supervisor/ Guide Preeti Sharma, [Link]@[Link],
Name with email and Mobile 8396900418
Number
Initial Comments by Guide (if
any)
Guide Approval ☐ Approved ☐ Revisions Needed
Resubmission Date (if any)
Section B – Project Idea Submission (To be filled by Student Team)
Field Student Input
1. Domain/Field Web and Mobile Application
2. Project Title CodeSync
3. Problem
Statement
4. Inputs Users will input code snippets or entire source code files through the
collaborative editor interface. Inputs include real-time text/code edits,
cursor movements, chat messages, and file management commands.
User authentication data will also be required to maintain personalized
sessions and track contributions.
5. Outputs The system will display real-time synchronized code updates from all
collaborators, highlighting active cursors and selections. It will provide
version history, syntax highlighting, error notifications, and chat
messages among collaborators. Users can also download the final edited
code files.
6. Functionalities Real-time collaborative code editing with conflict resolution
(Minimum 6)
Syntax highlighting for multiple programming languages
User authentication and session management
In-app chat for team communication
Version control with undo/redo and history tracking
File upload/download and project management
Multi-cursor support to indicate collaborators’ positions
Responsive UI for both desktop and mobile devices
7. Use Cases Student groups working on coding assignments can simultaneously edit
and review their code from different locations.
Developers in a team can brainstorm and debug code collaboratively in
real time without needing to switch between different tools.
Mentors or teachers can monitor students’ coding progress live and
provide instant feedback through chat.
8. Tools & Frontend: [Link], Tailwind CSS
Technologies
Backend: [Link] with [Link]
Real-time Communication: [Link]
Database: MongoDB for user data and project storage
Authentication: JWT (JSON Web Tokens)
Code Editor Integration: Monaco Editor (the same used in VSCode)
9. Expected Aryan Suri: Frontend development (React UI, Monaco Editor
Team Roles integration)
(follow same Akashdeep Singla: Backend development ([Link], [Link] for real-
order as per time communication)
Student Names &
Roll Numbers)
10. Methodology The system will follow a client-server architecture with real-time
synchronization implemented via WebSockets ([Link]). Conflict
resolution will be handled using Operational Transformation algorithms
to ensure consistent document states across clients. The development
approach will be iterative with frequent testing and feedback loops.
Faculty Feedback / Notes
(To be filled during weekly review session or submitted in shared tracker)
..............................................................................................................................
..............................................................................................................................