Free Getter/Setter Methods Article Review Sample

I agree with the author when he says that getter and setter methods are bad and evil. According to the author of this article, he refers this two methods; getter and setter as evil methods that should not be accepted at all costs. He says that despite the fact that getter or setter methods are commonplace in Java, he says that they are not particularly object oriented. (OO). He says that getter and setter methods have the ability to damage someone’s code’s maintainability. Further, the author argues out by saying that the presence of these methods, the getter and setter methods in numerous number can be a red flag that the program may not necessarily be well designed from the object oriented perspective.
The static object model has a purpose of capturing the associated information that is the information between classes that corresponds to the message flow. The association between this two classes will exist if and only if the objects of one class will send the messages to the objects in the other class. For this reason, when a static model needs to be built, one needs to identify the difference that exists between the two classes.
On the other hand, dynamic object model results when the designers design an incorrect class hierarchy thus producing unexpected results. This not considered as the best approach in designing. The dynamic model is the necessary tool for using the class’s objects. They are used in the accessor methods to wind up the model. An example is when designing the Unified Modeling Language (UML) using both the dynamic and static model. Care must be taken so that the data are not misplaced in any way.
For one to write a software with few getters and setters, the application or software which is set to be designed or written should be executable. The first thing that one needs to know for him or her to write a software using getter and setter is to understand the basic encapsulations that are required in the software that is to be written. The next step, that one needs to understand, is the user interface construction,
User interface construction is an essential thing that will also enable one to write a software with few getter and setter methods. Then one should perform the activities that comprise the use case. After these, the collaborator is then added to the CRC card. One should have minimal interaction with the collaborator during this process. The writing process of the software by the use of a few getter and setter is the recommended process when coming up with a good software that has minimal errors especially on the object oriented system. Therefore, getter and setters needs to be minimally used.