computer codes of pratice

here's a sample of a code of practice for a business. feel free to adapt adapt and use it for your own organization. ensure that you check it with your legal department or legal advisor before establishing and issuing a code of practice, as this type of document will almost certainly have contractual implications for your organization. involving customers in the drafting of a code practice is also useful.

during world war ll, the germans used enigma, a cipher machine, to develop unbreakable codes for sending messages. enigma's settings offered 158,000,000,000,000,000,000 possible solutions yet the allies were eventually able to crack code.

Accesss

  • computing facilities are provided by uodit for the university as a whole and by schools and departments for their members
  • access to facilities is normally arranged by the allocation of a unique user identifier (often called a username or login name). for some facilities the presentation of a university ID card or other form of identification may be required
  • on most computer systems a password is required in order to gain access. you should choose a password that is secure and not easily gussed. you are responsible for keeping passwords secret at all times and should not give passwords to other people.
  • unauthorised access to any computer facilities is prohibited and a criminal offence
  • you will be held responsible for any other person, even other authirused users, to access computing facilities using your username.
  • you will be held responsible for any and all activity on computing facilities which is initiated by your username.
  • if you suspect that someone is gaining unauthorised access to facilities you should report the matter as soon as possible to UoDit or departmental computing staff
  1. public - sofware engineers shall act consistently with the public interest.
  2. client and employer - software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.
  3. product - software engineers shall ensure that their products and related modifications meet the highest professional standards possible
  4. judgment - software engineers shall maintain integrity and independence in their professional judgment.
  5. management - software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance
  6. profession - software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
  7. colleagues - software engineers shall be fair to and supporttive of their colleagues.
  8. self - software engineers shall participate in lifelong learning regarding the pracice of their profession and shall promote an ethical approach to the practice of the profession.

Comments

Popular posts from this blog

lo4, be able to use it tools to produce management information

freedom of information act 2000