Information Technology Reference
In-Depth Information
for professional and proper conduct. The following are the eight key principles
according to the ACM (
2009
):
1. Public—Software 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, and be consistent with the public interest.
3. Product—Software engineers shall ensure that their products and related
modifications meet the highest professional standards possible.
4. Judgement—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 that is consistent with the public interest.
7. Colleagues—Software engineers shall be fair to, and supportive of their
colleagues.
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.
13.4 Phase IV: Implementation
Implementation can by far be one of the most enjoyable phases of the development
process. Coding is a very simple activity when the specification is correctly
completed and there are no or very few ambiguities left to overcome. Imple-
mentation hazards such as complex languages, ambiguous error messages and
large API's can be overcome easily with modern practices and tools. Use the
following guide as a reference to correct implementation practices.
• There is much coding that can be completed autonomously. Autonomous sys-
tems are able to translate UML or other high level documentation to code. These
tools should be used as often and completely as possible as they are capable of
creating concise implementations of specifications.
• Create consistent style. All team members working on implementation should
follow the same coding style which should contain rules and structure as
explained in the implementation chapter. Whatever style is chosen, it should be
enforced to retain consistency and it should be clear and verbose.
• Changes should be logged, not only in work logs and external documentation,
but within the source code for auditors to review.
