A second sprint: Academic integrity and professional ethics

Through reading the law of construction and the examples of teachers, I fully appreciate the role of a programmer to the society and the mistakes of the world's harm, with the development of the world, the popularization of information technology, human life more and more inseparable from the network software, A small network or software errors often lead to a region or even the world wide loss, it is far-reaching, for a company, a group with the network trade, a small irresponsible, dishonest behavior is likely to cause irreparable loss, or even bankruptcy, Therefore, a company, a software engineer's academic integrity and professional ethics is very important, so the network, software-related engineers to remember the principle:

• Principle 1: Public

1. be fully responsible for your own duties
2. Consider the interests of software engineers, employers, customers, users and the general public
3. The software is safe, conforms to the norm, through the appropriate test, does not reduce the quality of life, does not violate the privacy, does not harm the environment, only if the above conditions can be fully confirmed, only to recognize the software. The ultimate utility of software should be public welfare
4. inform the relevant person or expert of any harm that may be caused to the user, the public, and any external personnel associated with the software and related documents.
5. In all statements relating to the software or related documents, methods and tools, especially in those public statements, be fair and avoid fraud.
6. Encourage the voluntary use of professional skills for public welfare and promote the development of public-sector education.

• Principle 2: Clients and employers

1. Illegal or unethical software that is obtained or retained is not intentionally used.
2. Use the assets of the customer or employer only after proper authorization, and in the knowledge and permission of the customer or employer.
3. To protect the interests of the employer or client as much as possible, unless for a higher ethical consideration, in which case the employer or the appropriate authority is reflected in the moral issue.

• Principle 3: Products

1. Strive for quality, acceptable costs and reasonable plans; Identify all the tradeoffs you make and make sure that they are accepted by employers and customers, and that your plans are available to users and the public.
2. For any project you work or propose, make a realistic and quantifiable assessment of costs, schedules, personnel, quality and outputs, and give an estimate of the uncertainty about your assessment.
3. Ensure that you have sufficient testing, commissioning and review of the program and documentation for the project you are doing.
4. Develop software and documentation that respects user privacy.

• Principle 4: Judging

1. Only sign and endorse such documents: either under their own control or within their own terms of reference and have reached consensus in the industry.
2. Do not participate in bribery, duplication of fees and other improper economic behavior.

• Principle 5: Management

1. Ensure good management of the projects it engages in, including effective means to improve quality and mitigate risks;
2. When hiring a software engineer, you need to be realistic about the conditions of employment;
3. To provide fair and reasonable remuneration;
4. It is fair to prevent a person from achieving a position that is competent;
5. To provide a formal hearing process in case of allegations of violation of employer's interests or moral values;
6. Do not require the software engineer to do anything contrary to the code of ethics;

• Principle 6: Occupation

1. Not to seek self-interest at the expense of occupation, client or employer's interests;
2. Compliance with all regulatory practices, except where such requirements are inconsistent with the public interest;
3. Responsible for detecting, correcting and reporting errors in the software and related documentation;
4. In the event of a clear violation of this specification, the parties concerned should be expressed their concerns, except where it is not possible to affect production or risk;

• Principle 7: Colleagues

1. Encourage colleagues to uphold this principle.
2. Help colleagues during the development process.
3. Indicate the source of references to other people's work and resist unsolicited references.
4. Do not interfere with a colleague's work improperly. However, from the boss's point of view, if the previous article is in conflict with corporate or public interests, software engineers can question their colleagues ' work.

• Principle 8: Self

1. Strengthen all aspects of the ability-analysis, standardization, design, development, maintenance, testing, writing documents, managing the project process and so on.
2. Improve the ability to achieve safe, reliable and high-quality software in a reasonable amount of time, using reasonable expenses.
3. No injustice to anyone because of prejudice.

See because of the mistakes caused so many tragedies and unnecessary loss, but also deeply responsible, I want to take seriously the mission of the professional, seriously treat their occupation, make a commitment:

1. Respect the achievements of others ' intellectual knowledge
2. Resolutely resist doing things that endanger society and human beings, and obey the law.
3. Do not seek personal benefit at the expense of the user and the company
4. In the development process of dedicated, serious and responsible
5. Do not have illegal retention and access to user information software
6. Take responsibility for the mistakes of your own software
7. Respect the privacy of our customers
8. Maintain network security order, create a good network environment, promote the healthy development of network

Second Sprint: Academic integrity and ethics