8.01. Further their knowledge of developments in the analysis, specification, design, development, maintenance and testing of software and related documents, together with the management of the development process.


As it is conveyed in the Code of Conduct software engineers shall enhance their knowledge of every process that they would have to go through such as requirement gathering, analyzing, designing, development, maintenance and testing with related documentation as well as the management of the project. By not following this Code might not result any critical outcomes to either the developer or the product. But it is advised to adhere to this code in order to improve the self-knowledge and self-experience. If there are developers who do not concern much about improving their knowledge, which they should, will eventually be left behind in the field as the information and communication technology is kind of a field that has a rapid development and subjected to continuous change.

For undergraduates like us, this kind of projects provide maximum opportunity to touch the practical areas of web development and software engineering. Therefore we as a team put our best effort to learn and improve our knowledge in every stage of the development.

Requirement gathering phase was not very difficult as we had a client with a better understanding about our boundaries and experiences. There was not much difficult things to learn from that phase. That being said the analysis of the requirements we gathered wasn’t that much easy as previous. We had to make sure that all the specifications were analyzed and understood properly to get to the next stage which was designing. We had several discussions with client as well as team members towards identifying the requirements accurately.

The designing phase gave us the opportunity to get a real life experience by applying what we have learned through our course in a practical manner. This includes several practical scenarios such as handling of database, managing colors, designing user friendly interfaces and etc.

Implementation of the functionalities was helpful in strengthening our experience in programming and we had to learn new methodologies, coding practices so as to make sure the final product meet with the exact requirements provided by client. In testing also we had the chance to apply what we learned as theories practically.

As mentioned before the incremental development method was the development procedure we followed when working on the project. Working on the project using that method delivered us a great real life experience in how to manage our activities to furnish a quality product. Time management is one of the major experience which we had through working on this project. Although there was no documentation involved in the process we as a team had an excessive chance to further our knowledge in many extents.

2 comments:

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.

0 comments:

7.03. Credit fully the work of others and refrain from taking undue credit.


It is a vital fact that the software engineers and web developers shall give full credit to work of others and refrain from taking undue credit for work which they are not creditable. Although it is also unprofessional to take credit for other’s work, the code of conduct states that it is highly unethical more than unprofessional to undertake that kind of actions.

This code can be broken into several scenarios under how the work of others has to be credited. The possible scenarios are,

• Grant credit to each team member for their own work.

• Grant credit to information which we derived from websites, articles or books and etc.

• Grant credit to those who assist the team by providing information, knowledge as well as technical support.

First and foremost the team conceded to credit every member for their own work regarding the redesign and development of the ReputeU web site. The three members carried out different areas of development together. One member carried out the designing part, another the analyzing and data collecting part and next member most of the coding part. Apart from that all three members placed their contribution on finalizing the product. The credit to each and every function the members executed had been given consequently. No member tried to take credit on others work or abstained others from having credit to their own work.

We as university undergraduates accept that there are limitations to our knowledge. Therefore we took support from our superiors as well as our own colleagues in developing the functionalities required. We do not hesitate to give full credit to their support and the knowledge given.

Our team did not refer any books to obtain information mentioned in the site. But we went through several articles on few websites to clarify the accuracy of the information we possessed. We would not hesitate to grant necessary credit for those articles and websites for those information we got.

0 comments:

Contact Me

Name

Email *

Message *