You can create you own custom classes for everything. Here's an example of a cheap (as in cheaply made) pseudo contacts app:
Model - should be the place for the actual data/information, which handles all properties, storage, etc.
MyPersonGroup (NSMutableArray?)MyPerson (NSMutableDictionary?)name => @"John Doe"
birthdate => [NSDate dateWithTimeIntervalSinceReferenceDate: -600000000] // some time in the 80s if I'm not mistaken
whatever
View - the highest level of user interaction. Should do all the drawing and (partly) event handling
MyPotentialCustomViewForWhateverCustomDrawingINeed ToDo
UIView
UITableView
...
Controller - the bridge between Model and View. The controller is responsible for delivering the view the correct information and reflecting changes from the view in the model (and vice-versa)
UIViewController
MyPersonViewController
MyPersonGroupViewController
Check out Apple's Core Data Books example; it should be relatively easy to understand.
Hope I clarified the difference between M/V/C for you a little!