My own model code

Since the beginning of our major we have been taught to think to code as classes and more specifically as objects. This way to see the big picture have been known as paradigms and the more you research about this you’ll see that exists many ways to see and explain the behavior of our own code and even the process of for designing it.

At the beginning of my study in “computer science”, I got to see POO and if you have get to this point of my blog I think there is no need to explain the way this parading works.

Also we already have passed the UML part, and how this tool has been really helpful not only for our own understanding but for our relationships with subjects related with our work in the real world. The class that we already know how to design and be converted into code will be the goal for the actual implementation for the system.

Before we start implement in it, even before start comprehend it, we need to make sure that the diagram has enough quality to translate it, so you will receive a lot of useful information or not, then you could be officiated for i, or could be quite the oposite.

The method’s name gives you a hint for the code you can start implementing it, at the same time the inheritance are specified on the diagram, then you can choose your language that you feel confortable with, this is very important because the way you feel with the language depends your whole system.

As you can see I repeated and emphasized the language part because the productivity and performance that you do ir with are very important because you feel more free at the process of working on it, and the confidence it is very important.

As we can see, the hard part is already done when the analysis and design is finished. The implementation is just a translation of what we already know about the system.