Software Design and Architecture

The important question after reading the article "Who Needs an Architect?" is what is the real definition of what is architecture and all of its connotations that architecture involves. Architecture has two different meanings: It is when all the expert developers working on that project have a shared understanding of the system design. This shared understanding is called "architecture", this understanding includes how the system is divided into components and how the components interact through interfaces. Architecture is the set of decisions that you wish you could get right early in a project (but that you are not necessarily more likely to get them right than any other. Having this in mind, one of the principal differences between building architecture and software architecture is that in the building architecture you have got physical constraints; also, a lot of decisions about a building are hard to change. In the other hand, if you pick any one aspect o

It is incredible the importance of the software architecture. Sometimes (certainly most of the times), this step in the software development, we tend to not pay the correct attention to this step and that will lead our development to critical points (in the future). It is important to take the time you need to accomplish this step in order to develop programs that has the opportunity to scale and become bigger and bigger with the less programming work adapting the classes in order to deliver the new functionality that the client asked. Also, it is important to know all the different kind of architecture that exists in order of being able to select the right one depending of the software project you are working in. Some of this different software architectures are the following ones: No architecture: Yes, it is weird to consider this, but it has a reason why to consider it. In this architecture you do not count with no architecture, this is a horrendous mistake because if y

It is wonderful to know all the limitations that existed when we talk about programming that used to have so little space to be stored and that its memory was so small that programs that were robust enough will leaded the computer to a memory overflow. In the case of the documentary, they talk a lot of these limitations that it was necessary to had in mind because if something (anything) went wrong, it will make fail the whole mission and condemning the astronauts to a certain dead. The project of getting the man to the moon was given to the MIT, when I saw that, I though "Omg, what kind of pressure the students and teachers had in that moment, because knowing that a simple error would be devastating". One of the first problems that they found was that they needed an automatic navigation system that had the ability to orient automatically the spacecraft and allowing the astronauts to make the trip to the moon successfully. It was a whole new challenge to make that de

Hi everyone, my name is Fabián Camp Mussa. Being completely honest, I really don't have an expectation about this course but I'm pretty sure that with this course I will learn a lot of interesting and challenging things. I think that one of that challenging things will be learning Ruby language (hope won't happen). Talking about me I like a lot to spend my free time reading a novel, playing video games, writing stories or poetry and listening to music. Also, I spend my time watching The Witcher series I think the Netflix adaptation its pretty good, so I recommend it. Finally, I will put all my effort to learn all the things the teacher has to teach us and being able to use this knowledge someday in the future.