Accenture Interview Question Java Developers
Country: India
Interview Type: In-Person
Comment hidden because of low score. Click to expand.
Comment hidden because of low score. Click to expand.
0
of 0 votes
Also:
> DRY(Don't Repeat Yourself)
- Use the existing code through inheritance,association, aggregation or composition instead of rewriting it.
>Code should be written for interface
>Proper exception handling , handling the error or throwing it to the caller according to the requirements
>The name of the packages,classes,variables,interfaces etc. should be meaningful and according the organisation standard.
>
Open Close Principle
- ttoommbb@126.com August 25, 2014Software entities like classes, modules and functions should be open for extension but closed for modifications.
Dependency Inversion Principle
High-level modules should not depend on low-level modules. Both should depend on abstractions.
Abstractions should not depend on details. Details should depend on abstractions.
Interface Segregation Principle
Clients should not be forced to depend upon interfaces that they don't use.
Single Responsibility Principle
A class should have only one reason to change.
Liskov's Substitution Principle
Derived types must be completely substitutable for their base types.