On today’s entry we are going to talk about the article “Is design dead?”,
which talks about how the design has been changing through the years and how the
good practices were developed in order to create a good design.
Is no lie that for all the people that develops software, is kind of
difficult to come up with a good design because of the lack of and standards to
create it, other areas may have standards or even a methodology, but not us.
Because of these needs, developers have created a bunch of good practices, not
to create, but to reach a good design probably in a 85% of success. For
example, a good practice is a that the code we create has to be modular in
order to make corrections or complete alterations in a easier, this changes may
occur for many reasons, manteinance, update the information or just to simply
chage the entire code to something more efficient, the same goes to the design,
but the problem is that a design is more difficult to modify when is already
done or even half way through it.
One of the most terrible errors is to create the design when the
software functionality is already being tested, because it can result in a
software with no quality and so the project needs to be delayed and have bugs
in its majority. Because of this, the design needs to be created before everything
so the development team can focus more in important problems that needs immediate
response and not to worry over little things like a mismatch on the design.
The process to create software does not need to be complicated, that is
why the development part is for, the project team needs to be focused on the
important things like the results of the project needs to give, and for the
design.
Comments
Post a Comment