Skip to content

Latest commit

 

History

History
113 lines (83 loc) · 3.13 KB

Intial_Proposal.md

File metadata and controls

113 lines (83 loc) · 3.13 KB
Raw
title author theme
Project Proposal
Group 2
CambridgeUS

Table of Contents

  1. Project Description
  2. Project Team
  3. List of Functional Requirements
  4. System Architecture
  5. Technologies
  6. Quality Control and Testing
  7. Project Delivery Schedule and Phases
  8. Contact Details

Project Description

Scope

  1. A 24/7 radio taking request from users and playing music at client side.
  2. To make current playing song available to multiple nodes.
  3. There aren't many good and interactive web-clients for local songs. DiveSong will use local music files and make it available to a remote user.
  4. It will be a FOSS application.

Outcome

An Internet radio which takes requests from users, saves history of users, the rating of the songs on there platform, takes feedback of users and tells them when there requested song is going to be played so that they could tune up.

Project Team

  1. Varun Chhangani - Backend and Project Planning
  2. Mohamed Moosa - Testing and Project Designing
  3. K Chandra Canth - Database and Server handling
  4. Alivelu Sree Vidya - Database and API management
  5. A.N. Vaishnavi - Frontend
  6. Matla Sujala - API and Integration

Functional Requirements

  1. Should be playing random songs when nothing in queue based on the previous likes and dislikes.
  2. Authenticate users and take inputs like likes, dislikes and requests to play songs.
  3. Requested songs list should be sorted based on number of requests, time of requesting and likes/dislikes
  4. Users who requested for song to receive a mail of information when their track is going to be played in 5 minutes or less.
  5. The UI should be interactive.
  6. Songs should categorized based on language, artists, albums and more.

Functional Requirements (Contd.)

  1. Songs could be searched via a search bar.
  2. Songs could be downloadable.
  3. Most heard song list.
  4. History of songs played till 100 tracks.
  5. Forgot password implementation.
  6. Can face and recover tracks queue and continue playing after a power outage.

System Architecture

![System Architecture](/home/varun/UG-Course/Sem3/ASE/Project/System Architecture.png)

Technologies

  1. HTML5
  2. JavaScript
  3. Node Framework on JS
  4. React Libraries for Frontend
  5. MySQL
  6. Apache
  7. SSL encryption
  8. SMTP
  9. RESTful API

Quality Assurance and Testing

  1. Unit Testing
  2. Alpha Testing
  3. Integration Testing
  4. Interface Testing
  5. End to End Testing
  6. Load Testing
  7. Monkey Testing

Project Delivery Schedule

  1. 2 Weeks - Initial Tests written
  2. 4 Weeks - DiveSong Music Server
  3. 5 Weeks - APIs and interface with DiveSong Music Server
  4. 6.5 Weeks - DiveSong WebClient
  5. 7 Weeks - Testing Complete

Contact Details

  1. Varun Chhangani : [email protected]
  2. Mohamed Moosa: [email protected]
  3. K Chandra Canth: [email protected]
  4. Alivelu Sree Vidya: [email protected]
  5. A.N. Vaishnavi: [email protected]
  6. Matla Sujala: [email protected]

\begin{center}

\LARGE{Thank You}

\end{center}