Professional Documents
Culture Documents
Music Player Document
Music Player Document
Music Player Document
BZ music player is a web application for online music player.The application is designed with MVC pattern.The
application uses NoSql database.
Features:
● Login page to authenticate the user
● Application to load player and resume the last played song if it exists
● User can able to sort songs with Song title,Album and Rating
● In case of a new user, first song will be selected
● On user logout or close application, current played song info will be stored to resume on next login.
Technology Stack:
Web HTML,CSS
REST JAVA,jersey
DB Mongodb
Container Apache Tomcat
Note
:Application is tested in Google chrome.Testing and Implementation for other browsers like firefox is not
done.
Architecture Diagrams
Class Diagram:
User Rest Sequence Diagram:
Song Rest Sequence Diagram
Pseudo Code:
start
if (credentials not valid) then
alert(Invalid credentials);
else
if (lastPlayedSong available) than
load(lastPlayedSong)
else
load(all songs)
select(firstSong)
end
end
Analytics of the application
Below listed are some analytics in music player,
Custom Analytics:
● Basic on songs played by user in a time, we can predict the mood of user and create ads according to
mood [Romantic songs means romantic gift ads].
● We can suggest the user about new songs based on number of times a particular type of song is
played[Genre based suggestion].
● Analyze user activity to predict which user are more likely to spend money on purchases and also when
user ready spent[High purchase received last time].
Log Analysis using ELK:
● Music player logs are analyzed using logstash and indexed in elasticsearch.
● Using indexed data in elasticsearch, we can find most traffic time, user online time and input for above
custom analysis by custom query in kibana.
● Using Kibana we can see analysis data charts ,statistics,line diagram,etc.
Penetration Testing:
Possible Security threats
● Crack user credentials
● Unauthorized access to resources
● Fake payment transaction or recharge wallet
● Tap network to steal transaction info
● DOS attacks
● Download songs using plugin or access resource
Security Measures:
● Encrypt data passed in network
● Stored sensitive data should be encrypted [passwords,card info]
● Implement security to maintain session ids [Oauth] to validate authorization effectively
● Implement SSL for sensitive transactions[payments]
● Configure load balancer to restrict number of request from one server