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

Entradas más populares de este blog

Software Craftsmanship

Software Craftsmanship can be seen as a methodology in order to create good software, which has strong key elements that established the measures and techniques to create professional software development. It is the strong and complete philosophy to practice and helping others learn this craft, and as the Software Craftsmanship Manifesto ( http://manifesto.softwarecraftsmanship.org/ ) established some “rules” that completes this task. Such as the work on software that has to be performed to a well-crafted software, the response to change and the steadily adding value, the relationship between individuals and interactions and through the community of professionals developing software and finally customer collaboration with also productive partnership. Software Craftsmanship has a strong structure that can help the software industry in order to produce software quality, this philosophy can be applied in other topics. During the podcast with Bob Martin, or well known as “Uncle Bo...

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...

The Elephant and the Blind Programmers + 4.6 SEM: 4+1 view into software architeture + Six Blind Men

4+1 view, displays the use-case view scenarios for a whole project, it is segmented in 4 counterparts: Logical View, Development View, Process View, and Physical View; with all this view it is possible to view the relations between each stage of the software development, and how it goes the requirements and data through each one of the process for developing software. Performing an analytical architecture. With this structure is possible to actually know what the software is doing. The point of view determine the abstraction of what is observed, defines with certain knowledge what the observed is. The creation of simple models and techniques allows the comprehension of some topics to be easier, and manages to avoid misunderstanding and have a vast scope and complete vision of the whole entity. In the programming criteria perception is an important key factor that creates interpretation by understanding what is observable. Without any resources to analyze the observed is imposs...