Ir al contenido principal

Is design dead?

Design is one of the key elements to make a project succeed, design is a good practice in everything, sometimes without design, goals are unreachable. In software development is sometimes kind of difficult to reach a good design, there are a lot of reasons behind it, one of them is the lack of standards that are now even used during the design process. Methodologies gain an important role in software design, but depends on how the methodology is implemented or ever if this methodology is worth enough to the requirements of the whole project. Modulation comes in hand while talking about design implementation, dividing the big problem into little parts is easier to manage, process and maintain. Sometimes during implementation of certain project phases, comes changes, and this changes could determine the project success, it comes to my mind the warship Vasa, which suffered a lot of changes during the elaboration and planning process that made the ship finally sink.



Some problems presented in software development is to implement design when the software is already being tested, some phases had to be precise and in order, because having changes from previous phases in an advanced stage is chaotic. It always leads into software disfunctionality and lack of quality.



Some software developers have the “ability” to skip the design process, but this is nor general, some of these programmers are very experienced and the concept of the problem is very well defined and clarified. But missing the software design may lead into disaster.



The elaboration and creation of software has to be very precise, and has to follow a certain methodology in order to success, this methodology is adequate to the project requirements, this process hasn’t to be very dogmatic. It depends on the project’s team on which methods to use to create a proper solution to a problem.

Comentarios

Publicar un comentario

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
Publicar un comentario
Leer más

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
Publicar un comentario
Leer más

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
Publicar un comentario
Leer más