Moon Machines

The video talks about the engineers and technicians that made possible to travel to the moon the first time (approximately 400,000). It's interesting to know that the first Apollo contract was made to develop the rocket's navigation system, not the rocket itself. Also, it wonders me, how the test to the microchips were developed, the idea to take in that little weight difference as a test is an interesting idea. 

In other hand, the "wire programming method", is weird, I never heard before anything about it, but I think it's barely related to the modern arduino cards in certain way if I'm not wrong. I can perceive another important points to demark from the video that I've seen in other classes, for example the test part to delete the major part of the existent bugs, or the need to develop a good teamwork program or the way the leader need to motivate the teammates to work properly and be aware of the current needs of the project and the problems that need to be fixed in order to accomplish the objective of the team. 

I'm very happy to see that at this point of the career, many of the knowledge of multiple classes is being joined. Finally, I conclude that the video is closely related to the topic we saw today, the components, the guidance system was all constructed with components, and all the necessary to work together to meet the goal, it was needed all, from the inertia guidance system, to the priority schedule jobs management, radio signal guidance, and microchips to fully complete the requirements for the system, also the guidance system was a component for the rocket itself. This task required a huge effort to be carried out. The video was very interesting and the subject was very well explained.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

The movie was interesting, this was the first time I heard about it. The plot is simple, but interesting. The movie remind me to one of the articles we’ve previously read, about the software development to reach the moon. It was interesting to know a little bit more about the process that the NASA took to archive this. Notwithstanding that the movie plot doesn’t focused on something closely related to the software development or architecture (even if there’s some exploration about an IBM mainframe) , I think the important thing  is to reflex about  the difficult process that some projects need to get through. In this case, the project needed to analyze and take decisions as soon as possible, because the data became obsolete really fast. Also the data that needed to be reviewed was a lot, and in that time it was really hard due to the low processing power of the computers. In other hand, the movie talks about an important topic of our era, the racism. It’s wonderful to see...
Leer más

Microservices

The reading starts explaining the definition of "microservices", and as I understood the Microservices architecture is similar to the modular architecture. Let me explain, the author's describes that microservices architecture is a set of independently deployable services, this sounds like the "partion of funcionality inside modules". The author continues explaining why this approach is being more used nowadays and the advantages of this model against the monolothic one.  Later on, the article talks about how the developers are trying to build systems the same way we craft things in the real world, plugging together components (little parts that are there to perform some functionality and that together will conform a new thing). An interesting addition to this definition is that a component is a piece that can be "upgraded and replaced". Something interesting is that this architecture as I understand is designed to be implemented in cloud-based ap...
Leer más

The 4+1 View Model

The topics of the two videos are related with the article topic. Starting with the 4+1 video, I think this video information is like the topics of my class of software quality and tests. I’ve worked with some of the mentioned diagrams in the video. The new “scope” is the view encapsulation according to the different type of information that the diagram represents. But it makes sense to divide the diagrams with these criteria, because maybe the needed information may be different for whom is requesting it. And this scope will reduce and define properly the work to produce and deliver the diagrams. In other hand, the other video is a metaphor of the problem that is to design or select a paradigm to develop something, specially when the work is handled by a group. This is a result of the different approaches that each developer takes when defining or implementing requisites, each’s mind works and abstract the information differently. In this case the metaphor uses an elephant as the ...
Leer más