In corporate people also take the help of this rule frequently. In Computer Science Design of Algorithm classes it is one of technique to attack a problem.
Mostly when we plan for enterprise software previous experience says that maintenance is more costlier than developing. With time requirements, business rules change for which maintenance is really necessary. As Change is the only constant in this world, we can not avoid the situation. So maintainability is the highest precedence while designing or developing an application. That is the reason Object Oriented languages (Java, C#, C++ etc.) are popular. They have the feature to mange the complexity of software better than procedural language. So basically OO design means managing the complexity. Divide the complex functionality into integration of smaller/maintainable component. How to and what extend to divide ... These are some decision which designer has to take to have a optimum solution.
So next time we face a problem this will be an handy technique to approach it ......
This is basically the SOA(Service Oriented Architecture) Approach or implementation wherein the reusable components and blocks are identified and placed either in the ESB Layer or exposed as WS, to be leveraged for the Enterprise level implementation. It reduces a lot of overhead and improvizes the performance too!!...
ReplyDeleteEvery damn product we here these days...just try to foll the same footsteps...to make life easy for the developers involved in hardcore coding and manual intensive job!!.- Though i totally agree to ur statement that C/Java are still very popular.
Keep posting!!
M a lay man dud. Still it looks nice to me. Doesn't it violate "United we stand divided we fall" :)))
ReplyDelete@Dullal Thanks dear :) As long as anything (above rule) is done with right intention to solve some problem, I think its ok. Some time it is necessary also.
ReplyDelete