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

Ethical Reflection on Ready Player One

Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120) (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized , as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Because reality is real.” (p. 364) It is an often topic that circulates now a days, about world domination, and what have we done to this planet we live in. Everyone has it’s own way to manipulate their reality and have different perspectives about the world. For some people it is video games, for other people is ...

Microservices

Adaptability is always the answer, depending on the environment is how everything else is going to adapt. In the case of micro services, it is known by a new model for the big monolith replacement, but it is not a replacement, is just another type of architecture that had its benefits because certain features it has, but ensuring that micro services is the only path to follow, causes a problem, this architecture is proper for specific scenarios. In the industry, the massive over use of a new technology is often, for newer creations comes the extended massive usage. At this point other creations or technology can be developed to enter the competition scenario, for now, the old monolithic model is left behind, while micro services models are more used and potential growth is heading that way. As mention before, for some scenarios is viable using micro services, but in not the only alternative, it always depend on what is being worked on. It is true that segmentation and modulation can d...

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