S/W Design and Architecture - JP

Wow, I can't believe this is my last blog entry for an Ariel Ortiz class. One more semester and I'll be receiving my engineering degree. It has been quite a journey, but as everything, it all comes to an end. For this last post I'll  talk about a book that really caught me, Ready Player One. The plot is quite simple, it talks about a kid called Wade Watts, in a world were the actual "real world" is kind of a huge disaster for not saying other words, probably a dystopia (really similar to what we have seen in movies like The Hunger Games), but in the book there's also another world, a virtual one called the Oasis, were almost everyone from the real world plays it, because it was a whole new world, not only a videogame, in there people can have jobs, meet people, study in schools. Basically, they live more in the virtual than the reality itself. The creator of the Oasis was James Halliday, and I say was because in the book he is dead, and after his dead he ...

Even though I believe the movie is a dramatized representation of the events, I also believe that, at the time, at least some people at NASA came to that realization. In the movie it is shown very explicitly when Katherine has to tell Al Harrisson (the boss - already on the moon guy) where she goes for forty minutes a day, and why she does it. Nowadays it can be observed in highly productive environments such as big companies, and organizations alike, where non-oppresion organically becomes part of the culture (like it happens in the movie, but maybe not that dramatically). I'm not sure how or why exactly, but I have a feeling that an one can use the fact that an oppresive culture slows down progrss as an argument for proving human equality to a certain extent. The body of the argument or it's specifiications are content for some other, much longer blog post (maybe even another medium). On an entirely different topic, another thing that I liked about the m...

Today I'll talk about the the 4+1 view model, which basically consists in four sections and an extra section which is the +1 part, that allows us to make better software architecture. I will explain these sections in order to understand better this concept. This fourth section is the logical view, the development view, the process view and the physical view. The extra one is called: Use-Case View/Scenarios. The Logical view talks about class diagrams, communication diagram, sequence diagram, state machine diagram, and an object diagram. All of these in order to obtain an object model, what components will be made and how will the behave. The development view is about, component diagram and package diagram, all to the make the organization of the assets during the development work, in other words, which belongs to what. The process view is about concurrency and synchronized aspects. These mean activity diagram and ...

Hi everyone! In this week, we'll talk about SOLID principles. So let's get to it. The first principle called "Single Responsibility Principle" is one of the easiest to understand but at the same time one of the hardest to apply. To get a class to have only one responsibility, there has to be a very good software design, but developers must also devote time to code analysis (especially those that are dedicated to maintenance). Otherwise, programmers will simply do what is faster and simpler: Add code wherever it is going to work (Apparently) what was requested by clients. The principles with which I do not agree at all are "Open / Closed Principle" and "Liskov Substitution Principle" since I believe that the base classes should have the flexibility to be modified as long as the repercussions of the modification are understood. On the other hand, I think that classes must certainly be made to be extended or replaced by functions, si...