7.04. Review the work of others in an objective, candid, and properly-documented way.
This is an impotent pint in the code of conduct. All the software
should be tested before publishing it or handing over to the client. Through
the software testing and reviewing we can identify the faults, failures and the
errors in the software. There are several testing and reviewing techniques such
as black box testing, white box testing, unit testion, integration testing, and
system testing user acceptance test and so on.
According to this code of conduct when we review code of
conduct in objective way. It should be unbiased process. To be unbiased we can
used predefined guidelines and standards for review. When we found such error
or fault in the software we should formally notified to the developer of the
software so he/she can correct it.
As I mention before there were three members in our group to
develop the “ReputeU” project and when we developed our owned assigned parts we
went through a peer reviewed process. This method was very useful because we
found many errors and in the other hand we were able to optimize the code. As
an example once when I written a code and show it to my friends they came up
with a better solution than the existing one. When we found an error three of
us discussed it and always tried to come up with a better solution. During this
peer review process we worked as in an objective way and we treat each other equally
without being biased to one person.
There for we were able to practice this code of conduct
during the implementation of the “ReputeU” project.
No comments:
Post a Comment