What steps do you take when confronted with a problem, which should be converted into O.O Design? I know that on the basis of perspective, it can be subjective and different for each, but I am sure that after breaking a problem statement in the objects and classes, every good designer will have to follow and further Solid Design Just trying to put me, the process of adhering me to a new bee designer says that I like it.
Suggest the following steps 1. Write the usage case. This will help you to understand the problem, it should have basic execution flow (correct path) and alternative path. 2. Perform linguistic analysis and find classes and methods. (This is optional if you know any other good method, use it.) 3. Use solid principal to design your classes. 4. Keep in mind the encapsulation, heritage, polymorphism. If you do not remember that they have to write on paper or have to leave it on your desk 5. One more thing should be kept in mind that "how it changes". 6. Use design patterns when they are necessary Do not apply design patterns in your code Try to map your design problem in a design pattern.
I will also suggest the book "Head First Ooid" This is a very good book for OOAD tilt.
Comments
Post a Comment