Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I haven’t coded in java for a long time, and after coding in C, I’m having issued organizing my code for OOP. More specifically I’m not sure when to create a new method, and when to create a new class, and when to just lump everything together.
Are there some general rules or guidelines on how it should be done?
First of all, never just lump everything together.
Try to identify the objects first. Build a class for each object your program will work with. If you’re building an application for truck drivers, you will need a class for the driver, the truck, the load he’s hauling, there’s really no limit to how far you can break these bigger objects down. As for the methods, a method handles an action for the object. Truck.Start() would start the truck. Drive() would start it driving, etc… Maybe the Drive method takes a Route object for an argument which contains the roads to drive on. In short, create a method when an object needs to do something and create a class when you want to deal with another type of object.