Software Architecture

For developing a very efficient system, it has to me modulated, in a way each module has its own functions and communicates with other modules through the whole system. In order to maintain the efficiency of this system is by analyzing every module at its own way. Seeing each and every module as a black box, that receives information from other modules to perform a very complex task, the way of looking to all modules as a black box is in point of view from seeing the whole complete system. But like a microscope, by observing each module will give the information of that special feature each modules performs. By mentioning modules it also comes the term component, in a well designed system, it has to have a balance between modules and component, trying to assure low coupling and high cohesion. Depending on the systems problem complexity, it as a certain type of architecture, such as, layered architecture, pipe and filter architecture, client server architecture, component based architecture, and frameworks.

Every model that applies to software architecture is based or inspired on human history, for instance the Roman Empire.

Is like seeing the whole system as a EuroRack synthesizer, each module controls certain functions and performs oscillations and filters, the way they communicate between modules is the Control Voltage, with certain Voltages it can control the oscillation and each filter in order to perform such beautiful algorithmic melodies.

Architecture is important because we say is important, it is important to have a structure in the creation of technology, is the structure is well defined, it is easy to manage and control, defects and failures will be less, and we could manage to add more complexity on everything we are working. Therefor architecture is important, it is the column of out entire creation.

http://34.212.143.74/apps/s201911/tc3049/activity_software_architecture/

Comentarios

Entradas más populares de este blog

Who needs an Architect?

“We have met the enemy, and he is us.” Human beings are symbolic animals, we give an interpretation of our observation, recognizing everything as a symbol, creating concepts in order to give meaning to our existence. At first creating certain laws that rule our reality because each concept and law we created makes sense in our own interpretation, from that we continued creating more and more concepts and laws which are based in our preview interpretation, being the architecture of our whole understanding. Society has become the architect of every brick that constructs reality, and the architect is the one who makes the important decisions in order to continue the construction. With one building which has an established basis, and with the expansion during the course of time, it is difficult or even impossible to make changes into the functionality and shape, it could have slightly modifications but it will never change the structure at its roots, the complexity of this system is

WarGames

How far technology can go? It is an often question everyone ask, including such philosophical questions about we humans and our creations, just like our Frankenstein Monster, our creation could bring chaos to ourselves. We have the power to create and the limit of our creation could be bypass by that same creation. This movie called War Games, bring this topic and it is an actual matter, and now even more because now a days technology had reached tremendous power and capacity that is very impressive, some tasks that we humans cannot do, or maybe as fast, are done by our own creation. Just like the arguments of the Android David in the movies Prometheus and Alien Covenant, David reached a conscious level that defined him to be as he was and committing every action during the movie. It is that self evolution that keeps growing and it hasn’t the same limits as human interpretation has. Another example is this classic movie 2001 A Space Odyssey, from S. Kubrik, HAL 9 000, who has e

Understanding the SOLID Principles

T here exist some principles that make a procedure easier to perform, with this resource, it is viable to create clean products. In programming, exist something called SOLID principles that ensure quality and good performance while developing code, this acronym SOLID are the 5 widely accepted principles: S - S ingle Responsibility Principle A class should have exactly one responsibility. O - O pen/Closed Principle A class or a function should be open for extension but closed for modification. L - L isvok Substitution Principle Keep the relationship between classes and functions. I – I nterface Segregation Principle Avoiding interfaces that overloads classes with responsibilities that this classes don’t actually need. D – D ependency Inversion Principle “ Depend upon abstractions not upon concretions.” By understanding each one of this SOLID Principles, we could manage to create good code, and by good code I mean cleaner code that is maint

s/w design and architecture 201911

Buscar este blog