I understand the concepts of OO programming and the benefits but I often have trouble conceptualizing proper design. Most often I have difficulty when writing classes for integrations, like Quickbooks for example.
I need to write a class for an accounting software integration that uses web services to transfer data.
I'd be making calls like CreateCustomer, UpdateCustomer, CreateInvoice, GetStock, etc.
The way I'm looking at it now, I would create a class with a constructor that took no parameters. Then I'd simply call each method as I needed it and pass the necessary data to each method.
So CreateCustomer would take an array with necessary fields, and then pass that off to internal methods which would generate the xml and send it and handle the response.
My problem and the reason I think I'm doing something wrong is because when I start coding this I feel like I'm writing a library of methods. It doesnt seem like I'm writing a class.
I'm just looking for clarification on it. Is this proper OO design?