Skip to content

Commit

Permalink
chore(docs/core): 2024-12-15 19:42:15
Browse files Browse the repository at this point in the history
Affected files:
content/Projects/GC/About the Product/PRD.md
content/Projects/GC/Abstract/Birth of the Idea.md
  • Loading branch information
zakhaev26 committed Dec 15, 2024
1 parent 62d0dfe commit c38b14c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 15 deletions.
3 changes: 1 addition & 2 deletions content/Projects/GC/About the Product/PRD.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,14 +73,13 @@ The platform offers a public view system for Audience , allowing users to explor
# Admin Flows

Admins can :

#### **Match Listings**

Admins have full control over match listings, allowing them to add, update, or remove matches as needed. They can configure match details such as date, time, teams involved, venue, and other relevant information. The system ensures that the correct match information is displayed for both players and the audience, and admins can make real-time adjustments as necessary to keep everything up-to-date.

#### **Squad Listings**

Admins can manage team squads, ensuring that all teams are accurately represented and up to date. This includes adding or removing players from squads, updating team compositions, and verifying the integrity of squad rosters. This flow ensures that each team is properly represented in the system and ready for match participation.
Admins can manage [[Team]] squads, ensuring that all teams are accurately represented and up to date. This includes adding or removing players from squads, updating team compositions, and verifying the integrity of squad rosters. This flow ensures that each team is properly represented in the system and ready for match participation.

#### **Team Listings**

Expand Down
16 changes: 3 additions & 13 deletions content/Projects/GC/Abstract/Birth of the Idea.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,5 @@
We (the authors of this document) have always been drawn to the intricacies of real-time systems and the challenges posed by big data ingestion and management software. These fields represent a confluence of complexity and scalability, offering ample opportunities for innovation. As we delved into these domains, we sought out meaningful projects within our college ecosystem that could serve as a practical ground for applying our knowledge. During this time, we also explored the legacy of past PSoc members, whose remarkable contributions are documented in the PSociety GitHub organization. Their work inspired us to envision a project that could make a tangible impact while pushing the boundaries of what we, as a technical community, could achieve.
The idea for our broadcast system project emerged from our observations of live cricket tournaments at our college. While third-party apps like _CricHeroes_ were used for real-time scores, they failed to meet the specific needs of our tournaments. We saw an opportunity to build a custom solution that would align with our college's technical identity and foster innovation. The project aims to create a real-time, scalable platform for streaming live scores, with role-based access for players, organizers, and spectators. It will also include tools for tournament management and analytics.

The idea of a broadcast system took root during our observations of the ongoing cricket tournaments in our college. We noticed the frequent use of _CricHeroes_, a third-party application, to stream real-time scores and updates of live matches. While the app fulfilled its purpose, its use highlighted a broader issue. In a college that prides itself on its technical foundation, the reliance on external solutions for something as visible and significant as live match streaming felt misaligned with our identity. As a technical institute, we should embody a philosophy of self-reliance, striving to develop our own solutions, not just as an exercise in technical capability but as a commitment to real-world innovation and application.
This project offers a unique learning experience, involving backend and frontend development, real-time data processing, and system architecture. It aligns with our ethos of self-reliance and would demonstrate our community's technical capabilities. Beyond just streaming scores, the platform will integrate with other college systems, contributing to our campus infrastructure.

Beyond the ideological motivation, the reliance on a third-party application presented practical limitations. Such tools, built for a general audience, often fail to address the specific needs of our tournaments. They lack customization options that could cater to our unique requirements, whether it be integrating with college-specific systems or providing features tailored to the needs of organizers, players, and spectators. Additionally, using external software limits our control over the data and the user experience, something we could overcome by building our own platform.

We realized that developing a broadcast system from scratch would not only address these limitations but also create an invaluable learning experience for everyone involved. The project would require collaboration across various domains—backend and frontend development, real-time data processing, user experience design, and scalable system architecture. It would serve as a live testbed for experimenting with cutting-edge technologies like WebSockets, message queues, and distributed systems, while also giving students hands-on experience in designing, deploying, and maintaining a software product.

Moreover, this project would align perfectly with the ethos of a technical college. By building and deploying a broadcast system for live matches, we could showcase the capabilities of our student community, fostering a culture of innovation and self-reliance. The system would not only solve an immediate problem but also serve as a legacy project, inspiring future students to tackle real-world challenges with their own creative solutions.

Our vision for the broadcast system extends far beyond merely streaming live scores. We aim to create a robust and scalable platform that provides real-time updates with minimal latency, offers role-based access for players, organizers, and viewers, and includes comprehensive tools for tournament management and analytics. This system could eventually integrate with other college systems for authentication and data management, making it a cornerstone of our campus infrastructure.

The journey to develop such a system will undoubtedly present challenges. Designing for real-time performance and scalability requires careful planning and the right choice of technologies. Testing the system in live tournaments will demand adaptability and resilience. Yet, these challenges are also opportunities to learn, grow, and prove our capabilities. By tackling them head-on, we aim to not only build a software solution but also a stronger, more collaborative technical community.

In essence, this broadcast system represents more than just a technical endeavor. It is a step towards fostering a culture of innovation and collaboration within our college. By solving a real problem with a homegrown solution, we hope to demonstrate what is possible when technical expertise meets a clear purpose. This project is not just about the software we will build but about the legacy we will leave behind—a legacy of ingenuity, teamwork, and a belief in the power of technology to solve real-world problems.
By tackling the challenges of real-time performance and scalability, this project will foster a culture of collaboration and innovation. It will not only solve a current problem but also create a legacy of technical achievement, teamwork, and the belief that technology can solve real-world problems.

0 comments on commit c38b14c

Please sign in to comment.