Web Server Technology - Coursework 2: PHP/MySQL Database-driven Web Site - Online Music System
PHP/MySQL Database-driven Web Site - Online Music System
The aim of the project is to develop a fully functional Web site by working as a team with other students, 5 students per group. Each team should elect one team leader. As a small development team, you are going to develop a Web based song playing system, allowing user to create personal playlists of songs based on their musical tastes such as a user's favourite songs and moods. Songs could be rated by users. Users also have the option to turn on/off explicit lyrics while listening to the songs.
The online music website will be implemented using PHP, MySQL, XHTML and JavaScript when necessary.
The online Web site will be made available on your Apache Web Server. Objectives
• Manage the development and maintenance of Web Application.
• Develop server-side application.
• Interface application with a database.
• Design and implement basic database-driven websites appropriate to a given objective
Tasks
In order to evaluate your possible contribution, we would like each team to develop a number of database-driven web pages, using PHP programming language and MySQL database system, meeting at least the following criteria:
1. The system should support three type of users: Editor, Registered User and Guest user.
1.1. Editor, who is system administrator, can do anything on the system such as delete a user, add or delete playlist and songs. Editor’s login username is ‘root’ and default password is ‘localhost1’.
1.2. Registered user can only manage content related to his/her own account. For example, add, amend or delete his/her playlist.
2. A database should consist of various tables of songs, moods, users and playlist etc. It must include at least 50 different Chinese songs and at most 3 English songs of your own choice. Ideally the chosen songs should be your genuine favorite songs. At least 5 different Moods must be included. Each mood should link to at least 6 different songs. Each song might link to two or more moods. There are two type of playlists: user playlist and editor playlist. Editor playlist consists of pre-selected songs (at least 6 songs each). At least 7 editor playlists should be included. Songs between different playlist may be overlapping but cannot exceed 20% on each playlist. You can choose any name for the 7 editor playlists.
2.1. Song information must include, at least, song name (Chinese song should be in Pinyin and Chinese, songID, lyrics, playlist, duration, and locationID. You need a SongPool table to keep song location information.
2.2. Song track is in MP3 format.
2.3. The database should include all appropriate moods, editor playlist information, as well as appropriate information of users and their comments etc.
3. The song web site presents a home page with a menu bar on the top of the web page, which should include at least Home, Library, Playlist, Search and Login menu. You can choose your own Web site name.
3.1. Library and Editor’s playlists are displayed by default for all users all the time. Library should be able to show all songs based on the time the song was added in the database. For example, the last added song will be displayed on the top and played first.
3.2. Users can click a song from the Library or any playlist to play the song. Viewing number of the song is displayed. When the selected song finishes playing, the system will play the next song available in the Library or playlist automatically.
Advanced functions
You can implement many advanced functions in addition to what are listed below. The more the better. For examples:
- The Editor can put 3 songs at the top of Library all the time, can upload, add/remove songs, edit playlists/Library and songPool through online form. Editors can hide viewing number of songs, enable/disable visibility of songs in Editor’s playlist and Library in order to customize the visibility of certain songs to public and registered users.
- Editor can reverse and shuffle the order of songs displayed in the Library and Editor’s playlists
- Registered users have the option to turn on/off explicit lyrics while listening to songs.
- The Library shown to the registered users (VIP user) may contain more songs than the Library shown to the public.
- Provide an English version and Chinese version of the site, and users can have options to switch between two versions.
- Editor can customize the settings of the system such as web site name, editor username, password, database name, the max number of the playlist for different type of users. Is it possible reset it via a global configuration file which can update the whole system in one go?
- The same song could have multiple versions such as test version and production version. How to design the database to store and manage the relevant information as well as song location for different versions?
- User could rate a song on a 5-star, like/dislike (depending on one's preference) scale. How can the system use those ratings to create personalized lists of songs based on user’s favourite songs, moods or playlists?
- If a user has not participated in the rating system, how can the system recommend similar songs or even songs recommended by users with similar musical tastes?
Team Report
Each team needs to submit one team report via the module Moodle site and must include the following sections:
a) Cover page (Web site name, Team members’ student IDs and full names)
b) Table of contents
c) A team work report. The report must include the following as a minimum.
d) Design and implementation of the online music system
Describe the overall design of the online system, database and your code structure. You should explain how you implemented each main function/component, and any other details that you consider essential for understanding how your system works. You may use diagrams to help in your description. All components must be covered in detail. This should include details about the design and implementation. You should comment on how the components interact, how they are used and accessed and highlight features beyond the required specification.
e) Testing
You need to test your system thoroughly. All test procedures and results need to be fully documented.
f) Evaluation
You should include a critique of the overall system design along with suggestions for variations in the system. You will also need to provide a critique on the components. In writing this section, you need to consider the following:
g) Conclusions:
You should include a brief summary of the work done, analysis of your achievements and system limitations, suggestions for future work.
h) Appendix:
Instructions on how to install and run your system.
i) Program code:
This must include all the source code files and any other resources necessary to run your system. This must be submitted in a separate ZIP archive.
Your code should match your structure chart and report. In your source code, you are required to adhere to the following coding standards:
● You should use descriptive names for all of your variables and methods.
● You should include a good comment. You should include appropriate inline commenting in the code detailing its functions.
● You should use a consistent and readable scheme for indentation, spacing and blank lines.
System Demonstration
The SYSTEM DEMONSTRATION will consist of the following:
● Demonstration of installation – start from a zip file containing all song mp3 files, PHP/HTML, other scripts and MySQL database in a folder named using group leader’s studentID_last2digitsOfGroupMember1ID_last2digitsOfGroupMember2ID_last2digits OfGroupMember3ID_etc. For example, ‘sa202221011_12_13_14_15’ as the zip file name.
Then extract it and install it on a ‘clean’ system with only XAMPP as originally installed. And the web server on the running XAMPP should not require reconfiguration during the demonstration.
The site will be approached by http://localhost/sa202221011_12_13_14_15.
● The username of MySQL database is ‘root’ and no password is needed. The database name is the same as the folder name required as above.
● Demonstration of the working system – your system will be put through a number of test situations to see how your system reacts/handles them.
● Inspection of the program code and discussion of the code structure and design – you will be required to explain and discuss your program design, and to demonstrate your familiarity with the code.
