Brief Introduction for Code of Ethics

The Software Engineering Code of Ethics and Professional Practice is the international standard for professional software development and ethical responsibility. It was recommended by the IEEE-CS/ACM Joint Task Force on Software Engineering Ethics and Professional Practices. It was jointly approved by the ACM and the IEEE-CS as the standard for teaching and practicing software engineering.

Preamble

Computers have a central and growing role in commerce, industry, government, medicine, education, entertainment and society at large. Software engineers are those who contribute by directly to develop, design, testing and etc of software systems. Software engineers can do good or cause harm, to enable others to do good or cause harm, or to influence others to do good or cause harm because of there are rolls in software developing. To ensure, as much as possible, that their efforts will be used for good, software engineers must commit themselves to making software engineering a beneficial and respected profession. The Code contains eight Principles related to the behavior of and decisions made by professional software engineers, including practitioners, educators, managers, supervisors and policymakers. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships. The Clauses of each Principle are illustrations of some of the obligations included in these relationships. These obligations are founded in the software engineer’s humanity, in special care owed to people affected by the work of software engineers, and the unique elements of the practice of software engineering. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer. 

 

Principles

Principle 1: Public Software engineers shall act consistently with the public interest.

Principle 2: Client & Employee Software engineers shall act in a manner that is in the best interests of their client and employer, consistent with the public interest.

Principle 3: Product Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.

Principle 4: Judgement Software engineers shall maintain integrity and independence in their professional judgement.

Principle 5: Management Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.

Principle 6: Profession Software engineers shall advance the integrity and reputation of the profession consistent with the public interest. 

Principle 7: Colleagues Software engineers shall be fair to and supportive of their colleagues.

Principle 8: Self Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.

How we apply Code of ethics to Student Management System project.

This project we developed for the Weeraketiya central college to manage there students details properly. This describes how we manged to overcome the difficulties we faced and how we overcame those difficulties.

Brief introduction about our project & about me

Before we decide or select a project, all the group members gather and discuss about how we are going to help for society using our knowledge and skills we had. Team members give different different project ideas but we finally selected one project idea. It was Student Management System System for weeraketiya central collage.  Weeraketiya central collage was situated in Hambantota District. More than 4000 students studied in that school and It was one of major school in that area. After we selected our project idea, we decide to go to that school and discuss about our project idea with authorities.  They agreed with the project ides. So we decided to develop that project for Weeraketiya school.  

We are from University of Colombo School of Computing(UCSC)

I am R.K.J.P.Rathnayake
12001201
2012CS120

1.03. Approve software only if they have a well-founded belief that it is safe, meets specifications, passes appropriate tests, and does not diminish quality of life, diminish privacy or harm the environment. The ultimate effect of the work should be to the public good.

Before we delivery our application to Weeraketiya school, we done several things to ensure that our application was what they want. During the developing we done unite testing. Doing unit testing we can improve time-to-deliver, quality, and flexibility of the software. The key idea is that each piece of code needs its own tests and the best person to test that code is the developer working on it. Enabling developers to test their code as they write it ensures that quality is built in from the start. Having unit tests makes it easier and safer to modify the code because the tests document and protect the intended behavior and will instantly catch any regressions. Next we did integration test. Main purpose was to done this detect any inconsistencies between the software units that are integrated together. 
After the we completed integration testing successfully, we design to do system testing. It focuses to test whole the system. Using system testing results we can verify the functional requirements and technical requirements meets successfully. Also focus about security in the application. because we are working with very sensitive data like student's private information, teacher's private information and etc. So we give full guaranty about data security. finally pass the approval test. we proof our application does not diminish quality of life, diminish privacy or harm the environment. our final effect to do something for the public good.