SOFTWARE ENGINEERING BEST PRACTICES

•  SOLID
• Single responsibility (Each class will handle only one responsibility)

• Open-closed (A class is Open for extentions but closed for modifications)
• Liskov substitution (A reference to a class can be replaced by a sub class of same hierarchy)
• Interface segregation (Segregating functionality to different interfaces so the user is not forced to implement unwanted methods in the interface)
• Dependency inversion (Desinging high level functionality first and then go into detailed level implementations)
• Automated Unit Testing
• CI (Continuous Integration) (integrate code into a shared repository several times a day)