Musicology Warehouse $($MW$)$ is a hub for the diverse world of music, an art form that

has existed since immemorial. With various genres such as Gospel, Hip Hop, and

Reggae, the music industry thrives with many interests and intentions.

True to its name, "warehouse," the establishment serves as a distribution centre for

retail music platforms like Spotify, Deezer, etc., ensuring the supply of different music

genres across the globe.

Besides online platforms, MW has physical stores with branches strategically located

throughout South Africa where customers can conveniently procure their preferred

music.

Musicology Warehouse $($MW$)$ is seeking a solution from you, a web developer, to

address two key requirements. The first requirement is a way for admin staff to handle

stock levels. Each branch has a driver who delivers items to customers, a branch has

stock items or different music genres. The admin staff will need to track how many

physical copies of CDs are available. An Album$\_$type in MW must be one of the

following: non$-$promo, promotional, on$-$discount. The album$\_$category is the genre the

album belongs to$.$ The admin must be able to add albums and track the number of

CDs available.

The second requirement is the development of the CSTCS$,$ or Customer Search To

Checkout System. This system aims to provide customers with a seamless

experience, allowing them to search for albums, add selected items to their cart, and

have the flexibility to view or update the cart as needed.

Required:

$1.$ Develop an online STOCK INVENTORY SYSTEM and CSTCS using PHP$,$ HTML$,$

CSS$,$ JavaScript, jQuery, and MySQL to provide an interface for Admin staff in

each branch

The system must use frontend validation on key data fields.

$3.$ Use a MySQL database to store data in this application

HINTS:

$$ Use a Password log$-$in routine, Menus, Buttons, etc., in your GUI to simplify

user interaction with the system.

$$ The system must have formal login and logout routines.

$$ The Username for the system admin who has access to all functionalities must

be $$Myuser$,$ and the password must be $$SA$1$@$123.$

$$ You must create separate roles for each type of user, i$.$e$.$ advisor, nurse, doctor,

etc.

$$ At each stage of application processing, appropriate screen layouts, prompts,

and messages must be used to assist the user. For example, a student may

receive a message that they have been accepted$/$rejected$.$

$$ For consistency, use CSS stylesheets to define common interface features

such as colour, fonts, and menus