This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello, In my assignment they state the following: "Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a control scheme that will support this with minimal disruption to the users when this occurs. " What do they mean with this. If extra funcionality needs to be implemented the user may not be disrupted? If anyone can give a more clear explanation of this I would certainly appreciate it. thanx, Manuel
This is what they call Encapsulation, Extensibility, Maintainability, and Decoupling in OOP. By seperating this apart and keeping the inner workings of a class private, allows you to make changes to these areas, without a major disruption. If you make an interface that has all the methods of the Data class, and then have multiple implementations of this interface, you will find that I can remove, change anything from the Data class, recompile it and only, and all the other classes, like those on the clientside, does not know that you changed it, and it doesn't care, it still runs and works the same without modifications. That is what they mean by that. Mark