Music Management System

Task is to make a Desktop Application that helps users to manage their music collections more effectively. The stories that have been explained below the functionality must be available in the music management system. Any other ideas that may come up please embed these. Story 1 As a user of the music management system I will need to be able to run a program that will read and upload various music files and playlists that are stored on my computer. The whole purpose of this system is to control, manage and read music files and playlists. I need it to also action various other functions. Story 2 As a user of the music management system I want to be able to list different types of audio files. When the application starts the console should give me an option to select a button to upload audio file/files. This should then list the audio file in a list within the program. Story 3 Being able to create certain playlists is essential as myself and other users like to personalize certain audio files in certain categories. This should be achievable when I load the application and click on a create play list button the interface of the program. Furthermore the option of checking certain audio files as favorites should be available which should then put them in a certain playlist available to users. Story 4 When my application has been loaded I would like to be able to rename certain playlists expect those pre-set i.e. Favourites. Story 5 As a user of the music management system I want to be able to search for duplicate audio files. It is very common that reoccurring audio files appear in playlists and having the option available it will let me see how many singular audio files are in the actual playlist/music management system. This will be during the second iteration as this will list audio files in an ascending order according to the their naming conventions. Test Data: - The programmer may work with audio files (e.g. mp3), or playlist files (m3u) or other data to do something useful. - A test data repository will be available. Technology that you may consider using, includes (but is not limited to): - The Files and Paths packages to inspect and manipulate the file system - Storage of data in text, JSON or xml formats. - A command line user interface that allows the user to get things done by issuing parameterized commands - A graphical user interface that allows the user to access the functionality you provide with a mouse (and keyboard). - Components that consume music meta-data web services, such as Music Brainz, Discogs, Decibel, 7Digital, [login to view URL] and the Echo Nest. - Java Media Framework components for analysis of media files. Marks will be assigned as follows: User Stories: 15 marks - Presentation of top level stories and also of smaller, specific stories, and a plan that describes what system functionality was attempted (and what was successful). Notes that describe the success of each development iteration, i.e. which stories were attempted, and which attempts were successful. Evidence of Iterative Development: 35 marks - A GIT log that shows iterative development in practice, i.e. evidence of at least three iterations regularly submitted throughout the development lifecycle that tackle selected user stories, some continuity and evolution of code. Test suites: 15 marks - Unit Tests and / or functional tests for your application (and its components). Marks will be awarded to reflect the extent and effectiveness of the tests you provide. All test artifacts should be included, e.g. test files Final Functionality achieved: 35 marks - The User Stories you have completed will be tried out, using your software, on a similar archive of music meta-data. Marks will be awarded on the quality, effectiveness and scope of your software. All source code to be annotated and explained what it does in simple plain English.