The feeling of academic honesty and professional ethics and the commitment to future study and work in honesty and morality

By reading the law of construction p384~391 and reading the link given by Teacher Du, an important conclusion is drawn: The professional ethics of software engineers is essential. The software engineer has made great contribution to the society by taking part in the practice of analyzing, explaining, designing, developing, authorizing, maintaining and testing the software system. Because of their important role in software system development, software engineers have a great opportunity to benefit or endanger society, and have the ability to promote or influence others to benefit or endanger society. To ensure that these effects are beneficial to society as much as possible, software engineers must commit themselves to a career that benefits society and is respected by the public. This commitment requires software engineers to comply with the following "Standards of professional ethics and practice". This specification includes eight guidelines for the conduct and determination of professional software engineers, involving practitioners in software engineering, educators, managers, supervisors, decision makers, and related trainees and students. These guidelines point to the ethical responsibility of individuals, groups and groups involved in software engineering, and the primary responsibility in these relationships. The code is not a simple moral algorithm that can produce all the moral decisions. In some cases, some standards may contradict each other or with standards elsewhere. In this case, it is required that software engineers can use their own moral judgment ability, in specific circumstances to make the most consistent with the code of conduct. The best way to solve the moral conflict is to think about the basic principles comprehensively, rather than blindly relying on specific items. The Code records the ethical stance and standards of the industry. So even for such universal requirements, the code still provides support for software engineers and their managers. The code provides a moral basis for both the individual in the team and the team itself. The code also provides for morally inappropriate requirements for software engineers or their teams. Here are a few of the criteria I have been impressed by reading the code:

• 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.

In addition, I see the No. 387 page of the law of construction on performance evaluation, whether the team will appear "bad money to expel good money" or "dare not make mistakes" phenomenon, which cited an example: NBA star Kobe Bryant's shot is the history of the first, beyond the majority of NBA players all the shots. Should I punish so many shots? Would Kobe Bryant or the team have better results if they were to be punished harshly? In my opinion, Kobe Bryant in the number of "iron" in the NBA history of the first, such a record is a bit embarrassing, but can not simply rely on this data to say that Kobe Bryant is a "God." In fact, Kobe Bryant has the full basketball ability, won the team's trust, he has the opportunity to vote so many goals, only chance to "iron" so many times, from this point of view, this is tantamount to its ability of a recognition. If he didn't throw more balls in the game, people would question why he didn't vote. Because of his adventurous spirit, Kobe is able to drive the team to make himself and his team more aggressive and persistent, and it is because Kobe has the ability to ask him to shoot more. Therefore, I think as a software engineering personnel should also have the spirit of risk-taking, dare to make mistakes, but also should do a good job of risk analysis, to solve the problem after the response measures. Performance must be driven by individuals or even groups of people, so we can monitor and record data, feed back the current situation, adjust our status or team status.

here is my own commitment to the future of learning and work in good faith and ethics :

1. Without permission, do not copy other people's intellectual achievements
2. If you reprint someone else's file, take the initiative plus reference
3. Resolutely resist doing things that endanger society and humanity.
4. Do not seek personal benefit at the expense of the user and the company
5. Help each other with colleagues during the development process
6. Do not have illegal retention and access to user information software
7. Take responsibility for the mistakes of your own software
8. Respecting user's privacy and protecting user's privacy
9. Protect the interests of employers and users as much as possible

The feeling of academic honesty and professional ethics and the commitment to future study and work in honesty and morality