Music Library Management System

Project Highlights

• Dual Role Permissions: After logging in, enter different main interfaces according to your role.

• Complete process on the user side: Search tracks, add to cart, place orders, manage orders, pay and view invoices.

• Admin Management: Track/Customer/Order CRUD, Inventory Maintenance, Sales Report & Export.

• Multi-dimensional sales report: Statistics by type (Genre), city (City), and date (Date), including average, sum, maximum value, and minimum value.

• Built-in Music Player: Supports playlist, progress, volume, up and down song switching, and cover display.

• One-click export TXT: Supports exporting Tracks / Customers / Orders / Users / Chart Data.

Technology Stack

• Language: Java 25

• UI：JavaFX (controls, fxml, media)

• Build Tools: Maven

• Database: MySQL 8.x (JDBC: 'mysql-connector-j')

• Test: JUnit 5

• Modular: JPMS ('module-info.java')

System Architecture

• UI / Controller layer: Handles JavaFX page events and interaction logic
• LoginController
• UserMainController
• OrderManagementController
• AdminMainController
• MusicPlayerController

• DAO Layer: Encapsulates database CRUD
• UserDao, TrackDao, CustomerDao, OrderDao, OrderItemDao

• Service tier: Aggregate business transactions
• 'OrderService' (order placement, inventory deduction, line item write)

• Model Layer: Entity object
• User, Track, Customer, Order, OrderItem

• Session and Tool Layer:
• 'SessionManager' (login state)
• 'TrackMediaResolver' (Audio/Cover Asset Analysis)
• 'DBConnectionManager' (database connection)

Table of Contents Description

Feature List

1) Login and Registration

• Login verifies username and password, and error message is prompted when failed.

• New users can be registered (default role 'USER').

• After successful login, enter different homepages according to your role.

Admin:

• account: 'admin'

• password: 'admin'

User:

• account: 'user1'

• password: 'user1'

2) User

• Browse and search for tracks (titles/artists) on sale.

• Select the quantity to add to the cart (including inventory check).

• Support deleting, emptying, and settling in the shopping cart.

• View My Orders and Order Details.

• Order payment (card number, cardholder, expiration date, CVV input check, including simulated payment result).

• View the order invoice.

• Edit your profile (email/phone format verification).

• Open the built-in music player to listen to it.

3) Admin

• Tracks: Add/edit/soft-delete tracks, support uploading cover and audio assets.

• Customers: Add, delete, modify, and check customer information.

• Orders: View the full order and edit the status and modify the delivery city.

• Reports：
• Summary overview (number of active tracks, number of customers, number of orders, total sales)
• Sales by Genre / City / Date Statistics
• Pie chart visualization + metric statistics (avg/sum/max/min)

• Data Export: Supports exporting multiple modules as '.txt'.

Get started quickly

1. Environmental requirements

• JDK 25 (consistent with 'maven.compiler.release=25' in 'pom.xml')

• Maven 3.9+

• MySQL 8.x

2. Initialize the database

Contains the underlying test data (user, customer, track) within the script.

3. Configure the database connection

• 'URL' default: 'jdbc:mysql://localhost:3306/music_library?serverTimezone=UTC'

• 'USER' default: 'root'

• 'PASSWORD' default: empty string

4. Start the project

• It is also possible to run the configuration using the in-repository JetBrains: '.run/Music Library (Maven).run.xml'.

• Or run the main class 'MusicLibraryApp.java' directly.

Default test account

• Admin: 'admin' / 'admin'

• Normal user: 'user1' / 'user1'

The current project is in the form of coursework, and the password is saved in plaintext, which is only used for learning and demonstration scenarios.

Testing

• UserDaoTest

• TrackDaoTest

• CustomerDaoTest

• OrderServiceTest

These tests rely on a local MySQL database that is available and initialized with a 'music_library' database.

Export and resource file description

• The management side and report pages can export text files (including headers, timestamps, and alignment formats).

• The track cover and audio upload logic write:
• src/main/resources/images/tracks/
• src/main/resources/musics/

Known Limitations (Recommended)

• The current DB configuration is written dead in code, so it is recommended to change it to an environment variable or configuration file.

• Upload resources directly to 'src/main/resources', which is more suitable for development environments. If you need to publish, it is recommended to have a separate external storage directory.

References

• JavaFX Documentation: https://openjfx.io/

• MySQL Connector/J Documentation: https://dev.mysql.com/doc/connector-j/8.

• JUnit 5 User Guide: https://junit.org/junit5/docs/current/user-guide/

• Maven Documentation: https://maven.apache.org/guides/index.html

• JPMS (Java Platform Module System) Guide: https://openjdk.org/projects/jigsaw/quick-start

• Music Library: http://www.999ttt.com/

• Icons images: https://www.iconfont.cn/

License