Roster records can suggest useful software types, but converting data to classes is a design task. Ask which information an object should hold and which related objects it should be able to reach.
Here the software needs Player objects with a name and jersey number, each referring to one Team. Team objects have a name. The example assumes the software has already loaded and linked the data successfully.
Team record: T01, Wildcats
Player record: P007, Jordan, 7, T01
Player record: P001, Casey, 1, T01Each player row suggests the same Player type, not another class for Jordan or Casey. The repeated T01 values identify a shared team in the stored data. In the running object model, a Team reference can express that relationship directly.