Well Written Documnet

8.03. Improve their ability to produce accurate, informative, and well-written documentation.

Documentation is an important part in an web development project. Because it will help clients and team members to get information about   how project is going on and evaluate the work , detect errors and useful for future similar projects . so it is important to developers to use accurate , informative and well written documentation.

The developers always need to use true and accurate information. Because all the decisions are taking about project based on the information provided by developers. if project is deviating from its target the information help to keep project back on target. so it is important that  the accuracy of documentation.

Provide informative documentation is also a important part.  Clients can read these documentation and get some understanding about how the project is carried out and it helps clients to change some feature if they want. This helps  developers  to easily  identify  if  a occurs and to make solutions for that without conceding many time.

Well written documentation is also an important part. by using well written documentation it can be used for future similar  web development projects for schools. As the errors occurred in this project can be mitigated in future projects. This helps to reduce costs and time.
So due to these reasons it is important for software developer to improve their ability to  produce accurate, informative, and well-written documentation

Read More

Correcting Errors

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

As the persons entirely responsible for the ultimate software product or site, it’s the software engineer’s duty to detect, correct and report errors in it or any document we write which is related to it. Since our Journal entirely consists of documentation written by numerous persons, the responsibility of assuring they are in order and consist of no errors falls upon the shoulders of our group members. This is one task we paid attention to immensely.

When conducting the project there  were some errors occurred due to quick implementation of the project. But in the testing part we detect those  errors and able to correct them. As result of we were doing unit testing ,  alpha testing , beta testing  we  were able to identify these errors before the software is delivered to the clients.

From the starting of the project we kept out up to date records of the project . so after detecting the errors it will easy for us to find where the actual error happens. By looking at them we able to  correct those errors kept the project in right track . This will help to save our time and costs.After correcting these errors we  recorded them too. because in  future when we are conducting  a similar projects we can consider more attention on the errors happened areas.  This will help us to conduct  future projects  more efficient and effective way.

Not only that, If user get error or some matter to do there works immediately user can report it. It’s out responsibility to correct it.

Read More

Credit The Work

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

Read More

Understand Specifications

3.07. Strive to fully understand the specifications for software on which they work.

As it is conveyed in the code of conduct, software engineers should endeavor to understand the specifications of the software that they are currently working on or they are going to develop in the future. It is very important that they completely understand the requirements given by the client to reach the expected results. If failed to identify the specifications completely it would eventually lead to several unfavorable effects such as wrong outputs from functions, inappropriate designs, unsatisfied clients and users and etc. Therefore the complete understanding of specifications is considered essential with regard to developing of the software.
Pertaining to our web application, we are responsible for what we understand from the specification and what we develop accordingly. Hence we put our maximum effort to comprehend the specifications of the application and its domain. In order to do so our team had several meetings with the client in every stage of the development. In our meetings the discussions took place on clarifying the problems arose and to make sure that the client is well aware of our work and its progress. The client viewed the work and placed his comments and suggestions with regard to the functionalities as well as design of the application. Those suggestions and comments were taken into consideration for improving the site further.
Apart from those meetings, we had team meetings on every week in order to discuss the issues each member had and those were also supportive in understanding the specifications clearly. It was not necessary to use requirement gathering techniques such as questionnaires or interviews as the specifications were clear and well understood after several meetings with the client. To gain a better understanding on how to implement several functionalities our team studied and researched websites with similar functionalities and went through some tutorials wish provide us a great benefit.

Read More

Team Power

6.04. Support, as members of a profession, other software engineers striving to follow this Code.

This closure is important when working with a team. Because this closure promotes team members to work with each other in a more ethical way. A software engineer should support other software engineers who are trying to follow the software engineering code of ethics. As software engineers we should always try to follow the conducts mentioned in this ACM code of conduct. Because it promotes a healthy development environment that would ensure to produce better relationships between clients, employers and also employees. It also helps to develop a better quality software.

When a software engineer who is following this code of conduct sees another fellow developer who wants to follow these rules he should always help. Because by promoting this conduct we can guarantee to obtain the above mentioned goals. If the other fellow software engineers are not following this code or doesn’t know about them you can encourage them to follow it and introduce them to it. If they have any hard time following a closure mentioned in the conduct you as a person who follows the conduct should tell the proper way of following it.

By doing so in a team there is a very less probability of any of the team members doing something that is deemed unethical by this code. If everyone in the team acts like that there won’t be any ethical issues that would arise during the development of the product. Also as it encourages of using better standards of coding and also improving the skills there is also the advantage of being able to deliver a superior product.

The closure is there for the betterment of all the software developers. Because by doing unethical work the developers are the ones who is going to take the black mark. Sometimes without even knowing an unethical conduct may happen due to not properly knowing what is in this conduct. If a developer is fully aware of this code of conduct that person is able to reason an act according to this conduct before he do it. By promoting this code of conduct like this there is the possibility of majority of developers following this code which lead to a better development community as a whole.

Read More

Project Management

5.01 Ensure good management for any project on which they work, including effective procedures for promotion of quality and reduction of risk.

Proper future vision is the most important successive factor for any project. Because of that, at the beginning of the project the group members themselves allocated the role that we are going to perform throughout the project.

After having few discussion, we quickly allocated the work among the three members and after that we design a timeline for the project and started requirement gathering process.

Requirement gathering process took time than we expected and because of that we have to reschedule some activities that we have planned to finish.

As the given time was limited to the web application developing project. We have to finish several activities simultaneously. Because of that a proper monitoring on the activities that we perform was needed and we review the project progress once a week or twice a week according to the sudden needs that may occurs.

Proper project management is the key success point with regard to a particular system and because of that we focus more on proper documentation and project management activities.We also review the key features whenever a completion was happened and we also contacted some expertise personnel after a questionable action happened.

Read More

Document Management

2.07. Identify, document, and report significant issues of social concern, of which they are aware, in software or related documents, to the employer or the client.

Despite certain software being of great importance to society, many an occasion has been reported where the content of functionality of such software had not been in par with the beliefs of certain social groups, thus resulting in calamity. If we make an in-depth inquiry as to the reason behind such incidents, more often than not, it becomes evident that the ignorance of the employee and lack of keenness software engineers have shown to enlighten them of social concerns is the basis for it. Following this code is of immense importance in avoiding such conflicting situations, and in refraining from getting involved in unnecessary issues in future.

Even though public discussion regarding the matter respect to morality has become the norm in the current society, it must be stated that such topics are not always met with an equal amount of enthusiasm by all groups. Since a application which is exclusively dedicated to such a topic is by far more effective than a random speech regarding the same issue, the fervor with which it’s accepted or rejected too tends to multiply by the dozen. Hence, groups which may believe that consumption of beef is actually a right of theirs may express great displeasure towards a project as this, and they would no doubt readily get the backing of parties which are directly involved in slaughter of animals. This was a major concern of ours since the very commencement of the project, of which we had to constantly make our client aware and get his personal opinion of how precisely he intends to handle such matters should any conflicts occur in future. 

Existence of a code which dictates the necessity of identifying and reporting such social concerns to the employer helps them get prepared to encounter those in a much effective manner should they ever occur.

Read More