Read the requirements once for the big picture, then line by line for classes, attributes and associations.

Analysis: each requirement → the classes, attributes and associations it implies (e.g. Movie, PhysicalMovie, DigitalMovie, Customer, Member, Rental, Reservation, Review).

Solution: Movie generalizes into physical and digital movies; Rental and Reservation link customers to physical copies.

Common errors: modelling actions as classes, putting methods in a domain model, missing multiplicities, attributes that should be classes (and vice versa).