6.08. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.

By being professionals in the field of software engineering and web developing we shall take responsibility for identifying, correcting and reporting errors or faults in the software or website we develop including the errors in documentation. In other words this could state as improving the quality of the product by removing any unnecessary or faulty behaviors which will arise in the usage of the product and by delivering a professional documentation.

When developing and redesigning the web site ReputeU a considerable weight was given to detect any errors or faults it had. The errors associated with the product can be categorized into two sections. They are,

• Errors of previous work

• Errors of our own work

There were some errors of previous work which we distinguished within the period of analyzing. All the errors which were discovered were noted down with relevant details and later taken into discussions on how to correct those errors. These discussions took place with client as well as team members. The necessary steps had been taken to correct those errors as a result of those meetings and discussions.

Within the testing period of our own developments discovered numerous errors. As it dictates in this very own code we took responsibility of detecting those errors and correcting them in best possible ways. I and my colleagues as a team did not violate this code by not correcting or hiding errors which was revealed during the testing process.

The relevant documentations were not taken into consideration when developing specific functionalities and redesigning the web site. Hence it was not possible for the project team to identify any kind of errors regarding the documentation. Furthermore the project team didn’t deliver any sort of new documentation with the redesigned product.