Local garage owner needs a database management system for managing the garage's operations, facilitating efficient customer service and maintenance of vehicle records and inventory. In this garage, normally customers bring their vehicles for repairs or maintenance. Each customer is given a unique CustomerID when they register in the system, and they also provide personal details such as name, address, and phone numbers. Customers may own one or more vehicles. Each vehicle identified by a VehicleID, its make and model. To keep track of the services, work orders are prepared. Each work order, identified by an OrderID, includes a description of the work to be done, its cost, and the date it was performed. Vehicles and their corresponding work orders are linked, as are customers and the respective work orders are associated. Parts, essential for performing various tasks, are stored in the system with a PartID, along with their names, part numbers, and costs. Work orders may involve the use of multiple parts, establishing a relationship between work orders and parts, which is managed through the WorkOrderPart intermediary entity.

at first i thought WorkOrderPart was an weak entity then i noticed it was said that it was a intermediary entity