source | link

Its never too easy trying to write readable and easily maintainable code, but its not to hard to write an easy & maintainable code.

OOAD is four letter word but it hard to understand in one go - follow object oriented Analysis & Design

  1. Always start with a good requirement gathering and the exact Problem statement

    • start with few use cases ie; System-user dialogue interaction
  2. You have to kept your objects loosely coupled and make sure your code won't repeat - follow DRY [Do not repeat yourself]

    • anytime you see a duplicate , look for a place to encapsulate
  3. your code is open for extension and closed for modification - OCP [Open-closed principle]
  4. When you change your code always remember - Don't Create problems to solve problems, IT simply states do not modify your existing functionality
  5. Unit test your code
    • always test your code when things go wrong
  6. While working on the functionality always remember to follow the basic OOP (object oriented principles) and techniques to make sure your application is well designed from the start
    • Objects should do what their name indicate
    • Each object should represent a single concept
  7. Always remember the problem statement of the system, and in which context/domain software works
  8. Do some paper work too- yeah that works for me
    • having some printouts of UI related stuff and UML diagrams always work
    • you can even have the screen shots of the brainstorming session from the White board too
  9. Architecture layouts
  10. Apply design principles if possible
  11. Documentation
    • always document your code
    • set indentation in the IDE and document that too
    Post Made Community Wiki by Narender Parmar