-
Notifications
You must be signed in to change notification settings - Fork 0
Design
We have decided to go ahead with our primary topic: BeatDrop.
Problem Statement: Everyone has their own music taste, everybody has their own likes and dislikes. At times, people like to know what others are listening, explore new music or listen to music according to their moods, as it often gets boring to listen to the same songs over and over. People often go to social events/parties and there is a chance that they might not like the host’s songs/playlist. Hence, in order to eschew such situations, BeatDrop enables users to share playlists/songs with the host so that a common playlist can be generated based on previous data and some parameters like others’ likes, dislikes, number of times it has been played, etc.
Target Audience: Our target audience will be:
-
Users who can share their playlists with the host -
Users who are registered as hosts and can accept/reject playlists from other users and merge playlists -
Users who are registered as Artists and can upload their songs and playlists on the portal.
Solution Proposal: Users can create account and login. Users can create playlists, search songs, play songs, follow people, users can create private and public playlists. Hosts can Host party, create a playlist specific to party, can accept user requests to merge the songs, change the order. Artists can register themselves as music composers and can upload songs. Users can follow them.
Data Source(s): Spotify is a digital music service that gives you access to millions of songs. They provide their RESTful API for public use. https://beta.developer.spotify.com/documentation/web-api/ https://beta.developer.spotify.com/documentation/web-playback-sdk/
Class Diagram:
Sequence Diagram
User to User:
User to Domain:
Domain to Domain:
System to external api: