Principle 8: SELF - 8.02

8.02. Improve their ability to create safe, reliable, and useful quality software at reasonable cost and within a reasonable time.

As the intended software was done for a client according to agreement it was agreed to deliver the product within a limited time. The cost was negotiated with discussion with the client as according to the features he requested and the effort and resources that would require to implement them.

The major challenge was to develop the website within the agreed time period with the expected level of quality, features, safety and reliability requirements. The team worked in accordance to achieve the target and we were able to produce a high quality product within the specified limitations of time while meeting the requirements as requested.

The experience was a huge support for the team members in improving the ability to deliver a high quality product at a reasonable cost within a reasonable time period. And as per the difficulties that were faced during implementation and issues that we had to undergo, it was indeed an exercise to provide much better and quality service in the future with similar activities. The entire team was able to enhance their abilities and knowledge on the specified areas with the experience gained by involving in the project.

Read More [...]

Posted in Principle 8: SELF

Principle 8: SELF - 8.01

8.01. Further their knowledge of developments in the analysis, specification, design, development, maintenance and testing of software and related documents, together with the management of the development process.

With the involvement in the designing and implementation of the website we have gone through the necessary life cycle in building a quality product, from the requirement gathering phase to analysis of the requirements, designing the website, implementation of it, testing and finally undertaking the responsibility of its maintenance.

With the experience gained in requirement specification and analysis stage, we have been able to further our knowledge in how to deal with clients and to write a proper and a well-organized requirement specification document. The analysis and understanding of the exact requirements of the client made it possible to get real life experience of what was studied as theory in the classes.

With the designing of the site, the team was able to enhance knowledge on database structuring, use cases and activity diagrams and proper planning of how an implementation is actually done.

The development phase was much supportive in further strengthening the knowledge on programming and to learn new methodologies and techniques that we had to use in order to fulfil the customer requirements. In testing, several techniques were followed and learned theories were put into practice through that phase.

Apart from the enhanced knowledge on programming, document writing and requirement specification we have been able to learn how to manage the development process of a software. The team members had to divide the workload among themselves and manage the work with the limited time available which was a critical task. With all that, as a team we have been able to further enhance our knowledge in the software engineering industry through involvement in the aforesaid project. 

Read More [...]

Posted in Principle 8: SELF

Principle 7: COLLEAGUES - 7.01

7.01. Encourage colleagues to adhere to this Code.

In the process of designing and implementing the website for our client, each of the team members made sure that every other colleague follow the code of ethics and take measures to minimize or avoid completely the inappropriate effects to other parties through the product delivered.

All three of us followed the six principles mentioned in code of ethics while designing the website and whenever any misclarification was done by a team member, we discussed and solved the issue ensuing the final decision adheres to the code. From the point of serving the client with the best possible product up to every choice that was made in the process of implementation it was ensured that each of us encouraged others not to violate the code and to maintain the standard of the final outcome.

In deciding how the details of the external sources should be displayed several ideas were put forward and finally it was decided to display the link to the actual site or the blog article so that the due credit is given to the actual author of the article. How the quality of the website should be maintained and to satisfy the client’s needs to the maximum possible level were results of encouraging the colleagues to follow the code of ethics.

Read More [...]

Posted in Principle 7: COLLEAGUES

Principle 6: PROFESSION - 6.11

6.11. Recognize that violations of this Code are inconsistent with being a professional software engineer.

Being in the path to become professionals in the field of software engineering, we as the team who designed the aforementioned software have understood clearly the need and importance of adhering to the Code of Ethics in the process. The code of ethics which includes every aspect a software engineer should be thinking of such as the concern for the public, client and employer, product, judgment, management, profession, colleagues and one self, precisely identifies the qualities a professional software engineer should possess.

Being a software engineer it is important that he acts consistently with the public. If the productions he would produce are not going to be consistent or particularly inappropriate or useless to the public, the effort and the resources put into building the software would be wasted. Hence he should understand the general public in order to become a profession in the field and violation of that would lead to the creation of a useless software engineer. We have understood this through research of what kind of users would be using the website and taking measures to ensure that maximum comfortability is provided for them through all measures.

The client and the employer needs to be the key concerns for a professional software engineer. Providing the best possible service to the client while being honest about one’s competencies and following ethical procedures when interacting with the client as well as the employer are important issues to be considered. The client was considered as the main concern in our project and we have followed the necessary procedures to satisfy him in the best possible way by implementing the system so as to fulfill his requirements.

It is the software engineer’s duty to ensure that the product he delivers meet the highest standards possible. If the quality of the product is not up to the standards or if the required specifications are not being met, he would obviously not be considered a professional in the field. Therefore it is important that he knows what he produces and how he does it. We have made sure that this too is fulfilled by keenly adhering to every standard requirement and specially the code of ethics.

Maintaining the integrity and independence in their professional judgment is another key issue that a professional software engineer might want to understand. And also following an ethical approach in management of software development and maintenance and finally advancing the integrity and reputation of the profession consistent with the public interest are equally important. Also being supportive of the colleagues and engaging in lifelong learning regarding their profession makes a much better professional out of him. And we have been supportive of other team members throughout the implementation process and being in line with the code of ethics all the time have learnt the importance of engaging in the learning process. In the procedures followed in designing, implementing and managing the development process of the website, our team has learnt and understood that violation of the above points would be inconsistent with being a professional software engineer.

Read More [...]

Posted in Principle 6: PROFESSION

Principle 3: PRODUCT - 3.13

3.13. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.

Since the intended system was a website and especially since it had to be informative, the above mentioned code was more crucial in the context of our project. The data that were used in the site were mainly from the company itself. The mission, goal, objectives and the details regarding their company and the other information relevant to the equipment the company trade were directly obtained from the sources of the client and hence those data are properly authorized and ensured to be obtained in a properly authorized manner.

Apart from those details, we have taken measures to include more details about sustainability, ethical trading and several other related fields as requested by the client. The details to be included in such cases had to be obtained from external sources and it was important that corrective ethical and lawful means were followed in acquiring those. Several videos that are published on the site were taken from the YouTube site which allows sharing of the video with no restrictions. Hence the acquiring of those did not raise any ethical issue.

Most of the other details were directly taken from other sites or articles from blogs that were available on the internet. Hence clear precautions were taken to avoid any unethical procedure in sharing those details in our site. The direct link to those sites were provided each time the details were shared and due credits have been awarded to the original authors of the articles which we have taken details from. The issue was given high consideration and attention since any unlawful mean of obtaining data from external sources would bring up unnecessary issues for the client as well as for us being the developers.

It was guaranteed that the details used within the site were accurate and up to date. The external sources from which the article links were obtained were examined and proper research was made to assure that the obtained information is true and accurate. Hence every necessary measures were followed by the team to adhere to the above mentioned code in order to provide the customer with the most reliable and accurate information.

Read More [...]

Posted in Principle 3: PRODUCT

Principle 3: PRODUCT - 3.07

3.07. Strive to fully understand the specifications for software on which they work.

With regard to the website we are intended to design, we have taken the maximum effort in understanding the domain and specifications as required by the client. Apart from the first meeting with the client when only a brief introduction to the system was given, several rounds of client meetings were held during the implementation. These meetings were considered the main source of information to comprehend the desired product. Hence, the client was shown the finished product at each iteration and his ideas and suggestions were taken into consideration in improving the website further.

Other than the client meetings, the specifications were understood by studying similar websites of parallel industrial companies and also research through internet helped a lot in understanding the exact requirement of the customer. Discussions among the group members on which features to be improved and added were also much supportive in understanding the required specifications and designing a perfect and a useful website for the client.

Read More [...]

Posted in Principle 3: PRODUCT

Principle 3: PRODUCT - 3.03

3.03. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.

With regard to the website we are concerned with, we have identified the issues that are related with it and measures are being taken during implementation to avoid or minimize the effect of them.

When addressing the ethical issues that are to be faced, the main concern was that whether the client who is a telecommunication equipment trading partner follow the ethical practices in trading procedures and whether the traded equipment are made adhering to them. It was emphasized by our client not only that they follow the ethical practices but also encourage their stakeholders on ethical use of resources considering that as one of the key goals of the company. Driving the telecom equipment manufacturers and supporting the customers for ethical consumption is deliberated by them as vital objectives to be achieved. Hence it was clearly observable that the ethical issues were properly addressed and no further measures were needed in that context.

Regarding the cultural issues the website does not really impact the culture of the related parties or create any significant issue in that concern. Since the intended project is only an informative website related to the promotion of our client’s product which would be telecommunication equipment trading, it has no impact on the culture in whatever the aspect.

The major legal issues faced would be the client’s practices followed when trading the equipment. Hence before the request to design the website was accepted, the relevant parties were consulted and measures were taken to identify the exact procedure of trading and the company’s trading policies in order to arrive at the conclusion that the project has no legal issues whatsoever. The type of the stakeholders of the company and how qualified the manufacturers are and also how the legal sides of the trading is handled was taken into consideration at that stage.

The company makes sure that they not only trade telecommunication equipment just for their profits but that they follow a green business initiative. Green technology and clean manufacturing are two of their significant considerations. Hence it would ensure that the company follows a business strategy which has minimal negative impact on the local or global environment, community, society or economy. And that would provide sufficient evidence that the supposed site would adhere to the above mentioned code of ethics.

Read More [...]

Posted in Principle 3: PRODUCT

Principle 1: PUBLIC - 1.07

1.07. Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.

In the point of view of the specifications of the project that we are undertaking, the ultimate product would be a website which would necessarily provide information regarding sustainable telecommunication and providing a platform (probably through a forum) to discuss any issues related to company, career opportunities and most importantly regarding the services they render to the community through their green concept and ethical manufacturing standards.

Hence if physical disabilities are taken into consideration, the majority of the community have no issues in accessing or getting the benefits out of the intended website. Fairly a small amount who have inabilities to view the site (issues with eyesight) or to use a computer or a device (physically handicapped) would be the ones that will not benefit out of the system. As the project team we have taken maximum effort to resolve issues that are possible to be given solutions such as using colours which are visible for colour blind people as well in the site.

The ultimate product would not cause a larger number of users to refrain from being used due to any economical disadvantage. Since the output would be a website, any user with a device (desktop or mobile device) with internet access can easily use the site. Only a few who do not have access to the above mentioned resources would be unable to use the product.

When the above factors were analyzed it was decided that the issues which would diminish access to the benefits of the website are minimal and the ultimate product would be important and useful to majority of the community.

Read More [...]

Posted in Principle 1: PUBLIC

Principe 1: PUBLIC - 1.03

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.

This code specifies that the website we are intended to design should ensure that it would not harm or affect the general public in immoral ways. Hence before accepting the request to design the website our group analyzed the requirements and the effects of the final outcome in order to guarantee that it adhere to the above requirements.

The requirement of the client was to design an informative website where it will not have much interactive functionalities with the users. Hence it is ensured that none of the users of the site would be facing any safety issues with regard to any matter. At the same time, this would make sure that the site would not diminish privacy of any party involved since user interaction is much less in this case.

In the point of meeting specifications, the group discussed and finalized all the specifications in terms of the user requirements as well as legal, technical specifications and also the adherence to the code of ethics.

Since the intended system is a website it was clear enough that the site would pass the appropriate tests which would mainly be load testing and primarily testing for errors and bugs which are relatively smaller issues.

The main purpose of the site is to promote sustainable telecommunication and acknowledge the customers about ethical consumption while encouraging all the stakeholders to follow the righteous practices. Hence it is ensured that the product will not diminish quality of life but instead would enhance it.

Environment responsible trading and manufacturing is one of the main considerations of the company. The client’s expectation was that the site would cover each and every aspect of green business initiative, ethical use of resources and environment protection. Therefore it guarantees the site nor would the content in the site contribute in any aspect to harm the environment.

Finally it was decided that the ultimate effect of the work would be for public good and that the site adhere to the code 1.03 of the Code of Ethics.

Read More [...]

Posted in Principle 1: PUBLIC

Principle 1: PUBLIC - 1.01

1.01.  Accept full responsibility for their own work.

Being the developers of the website and involving in the requirement gathering, through design to implementation, testing and maintenance of the website, we would take the sole responsibility of the work we have done. It is vital that we assure the client as well as the public that any kind of adverse implications which may be caused by the deliverables are avoided and any questions regarding such issues will be answered with responsibility.

As according to the request by our client HyperJet Technologies (Pvt) Ltd. the relevant requirements and specifications were analyzed before the acceptance of the request and it was made sure that the compliances are adhering to the legal and ethical standards. It was then implemented with all due precautions and according to the respective standards so as the final product meet the required quality measures. And the site has been tested for errors and bugs and ensured to be free of faults and any issues regarding that matter will be considered as our responsibility.

Apart from any technical issue our team is also responsible for the ethical standards of the site created. It is designed adhering to the code of ethics and measures were taken at each stage to avoid violation of them. Therefore any clarifications regarding such disputes would be our responsibility to be answered to and make necessary amendments if necessary. The product is assured to be consistent with the public as well as the client and any violation of code of ethics or legal or technical concerns are being avoided to the best of our knowledge.

Read More [...]

Posted in Principle 1: PUBLIC

Software Engineering Code of Ethics and Professional Practice(5.2)

The International Standard for Professional Software 

Development and Ethical Responsibility

As recommended by the IEEE-CS/ACM Joint Task Force on Software Engineering Ethics and Professional Practices  and jointly approved by the ACM and the IEEE-CS as the standard for teaching and practicing software engineering.

Short Version

PREAMBLE

The short version of the code summarizes aspirations at a high level of abstraction. The clauses that are included in the full version give examples and details of how these aspirations change the way we act as software engineering professionals. Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become high sounding but empty; together, the aspirations and the details form a cohesive code.

Software engineers shall commit themselves to making the analysis, specification, design, development, testing and maintenance of software a beneficial and respected profession. In accordance with their commitment to the health, safety and welfare of the public, software engineers shall adhere to the following Eight Principles:

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

Full Version

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 direct participation or by teaching, to the analysis, specification, design, development, certification, maintenance and testing of software systems. Because of their roles in developing software systems, software engineers have significant opportunities to do good or cause harm, to enable others to do good or cause harm, or to influence others to do good or cause harm. 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. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.

The Code contains eight Principles related to the behavior of and decisions made by professional software engineers, including practitioners, educators, managers, supervisors and policy makers, as well as trainees and students of the profession. 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 in 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.

It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission. The list of Principles and Clauses is not exhaustive. The Clauses should not be read as separating the acceptable from the unacceptable in professional conduct in all practical situations. The Code is not a simple ethical algorithm that generates ethical decisions. In some situations, standards may be in tension with each other or with standards from other sources. These situations require the software engineer to use ethical judgment to act in a manner which is most consistent with the spirit of the Code of Ethics and Professional Practice, given the circumstances.

Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations. These Principles should influence software engineers to consider broadly who is affected by their work; to examine if they and their colleagues are treating other human beings with due respect; to consider how the public, if reasonably well informed, would view their decisions; to analyze how the least empowered will be affected by their decisions; and to consider whether their acts would be judged worthy of the ideal professional working as a software engineer. In all these judgments concern for the health, safety and welfare of the public is primary; that is, the "Public Interest" is central to this Code.

The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur. However, even in this generality, the Code provides support for software engineers and managers of software engineers who need to take positive action in a specific case by documenting the ethical stance of the profession. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.

The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function. As this Code expresses the consensus of the profession on ethical issues, it is a means to educate both the public and aspiring professionals about the ethical obligations of all software engineers.
PRINCIPLES

Principle 1 PUBLIC Software engineers shall act consistently with the public interest. In particular, software engineers shall, as appropriate:

1.01.  Accept full responsibility for their own work.

1.02.  Moderate the interests of the software engineer, the employer, the client and the users with the public good.

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.

1.04.  Disclose to appropriate persons or authorities any actual or potential danger to the user, the public, or the environment, that they reasonably believe to be associated with software or related documents.

1.05.  Cooperate in efforts to address matters of grave public concern caused by software, its installation, maintenance, support or documentation.

1.06.  Be fair and avoid deception in all statements, particularly public ones, concerning software or related documents, methods and tools.

1.07.  Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.

1.08.  Be encouraged to volunteer professional skills to good causes and to contribute to public education concerning the discipline.

Principle 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. In particular, software engineers shall, as appropriate:

2.01. Provide service in their areas of competence, being honest and forthright about any limitations of their experience and education.

2.02. Not knowingly use software that is obtained or retained either illegally or unethically.

2.03. Use the property of a client or employer only in ways properly authorized, and with the client's or employer's knowledge and consent.

2.04. Ensure that any document upon which they rely has been approved, when required, by someone authorized to approve it.

2.05. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.

2.06. Identify, document, collect evidence and report to the client or the employer promptly if, in their opinion, a project is likely to fail, to prove too expensive, to violate intellectual property law, or otherwise to be problematic.

2.07. Identify, document, and report significant issues of social concern, of which they are aware, in software or related documents, to the employer or the client.

2.08. Accept no outside work detrimental to the work they perform for their primary employer.

2.09. Promote no interest adverse to their employer or client, unless a higher ethical concern is being compromised; in that case, inform the employer or another appropriate authority of the ethical concern.

Principle 3 PRODUCT Software engineers shall ensure that their products and related modifications meet the highest professional standards possible. In particular, software engineers shall, as appropriate:

3.01. Strive for high quality, acceptable cost, and a reasonable schedule, ensuring significant tradeoffs are clear to and accepted by the employer and the client, and are available for consideration by the user and the public.

3.02. Ensure proper and achievable goals and objectives for any project on which they work or propose.

3.03. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.

3.04. Ensure that they are qualified for any project on which they work or propose to work, by an appropriate combination of education, training, and experience.

3.05. Ensure that an appropriate method is used for any project on which they work or propose to work.

3.06. Work to follow professional standards, when available, that are most appropriate for the task at hand, departing from these only when ethically or technically justified.

3.07. Strive to fully understand the specifications for software on which they work.

3.08. Ensure that specifications for software on which they work have been well documented, satisfy the users' requirements and have the appropriate approvals.

3.09. Ensure realistic quantitative estimates of cost, scheduling, personnel, quality and outcomes on any project on which they work or propose to work and provide an uncertainty assessment of these estimates.

3.10. Ensure adequate testing, debugging, and review of software and related documents on which they work.

3.11. Ensure adequate documentation, including significant problems discovered and solutions adopted, for any project on which they work.

3.12. Work to develop software and related documents that respect the privacy of those who will be affected by that software.

3.13. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.

3.14. Maintain the integrity of data, being sensitive to outdated or flawed occurrences.

3.15 Treat all forms of software maintenance with the same professionalism as new development.

Principle 4 JUDGMENT Software engineers shall maintain integrity and independence in their professional judgment. In particular, software engineers shall, as appropriate:

4.01. Temper all technical judgments by the need to support and maintain human values.

4.02 Only endorse documents either prepared under their supervision or within their areas of competence and with which they are in agreement.

4.03. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.

4.04. Not engage in deceptive financial practices such as bribery, double billing, or other improper financial practices.

4.05. Disclose to all concerned parties those conflicts of interest that cannot reasonably be avoided or escaped.

4.06. Refuse to participate, as members or advisors, in a private, governmental or professional body concerned with software related issues, in which they, their employers or their clients have undisclosed potential conflicts of interest.

Principle 5 MANAGEMENT Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance. In particular, those managing or leading software engineers shall, as appropriate:

5.01 Ensure good management for any project on which they work, including effective procedures for promotion of quality and reduction of risk.

5.02. Ensure that software engineers are informed of standards before being held to them.

5.03. Ensure that software engineers know the employer's policies and procedures for protecting passwords, files and information that is confidential to the employer or confidential to others.

5.04. Assign work only after taking into account appropriate contributions of education and experience tempered with a desire to further that education and experience.

5.05. Ensure realistic quantitative estimates of cost, scheduling, personnel, quality and outcomes on any project on which they work or propose to work, and provide an uncertainty assessment of these estimates.

5.06. Attract potential software engineers only by full and accurate description of the conditions of employment.

5.07. Offer fair and just remuneration.

5.08. Not unjustly prevent someone from taking a position for which that person is suitably qualified.

5.09. Ensure that there is a fair agreement concerning ownership of any software, processes, research, writing, or other intellectual property to which a software engineer has contributed.

5.10. Provide for due process in hearing charges of violation of an employer's policy or of this Code.

5.11. Not ask a software engineer to do anything inconsistent with this Code.

5.12. Not punish anyone for expressing ethical concerns about a project.

Principle 6 PROFESSION Software engineers shall advance the integrity and reputation of the profession consistent with the public interest. In particular, software engineers shall, as appropriate:

6.01. Help develop an organizational environment favorable to acting ethically.

6.02. Promote public knowledge of software engineering.

6.03. Extend software engineering knowledge by appropriate participation in professional organizations, meetings and publications.

6.04. Support, as members of a profession, other software engineers striving to follow this Code.

6.05. Not promote their own interest at the expense of the profession, client or employer.

6.06. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.

6.07. Be accurate in stating the characteristics of software on which they work, avoiding not only false claims but also claims that might reasonably be supposed to be speculative, vacuous, deceptive, misleading, or doubtful.

6.08. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.

6.09. Ensure that clients, employers, and supervisors know of the software engineer's commitment to this Code of ethics, and the subsequent ramifications of such commitment.

6.10. Avoid associations with businesses and organizations which are in conflict with this code.

6.11. Recognize that violations of this Code are inconsistent with being a professional software engineer.

6.12. Express concerns to the people involved when significant violations of this Code are detected unless this is impossible, counter-productive, or dangerous.

6.13. Report significant violations of this Code to appropriate authorities when it is clear that consultation with people involved in these significant violations is impossible, counter-productive or dangerous.

Principle 7 COLLEAGUES Software engineers shall be fair to and supportive of their colleagues. In particular, software engineers shall, as appropriate:

7.01. Encourage colleagues to adhere to this Code.

7.02. Assist colleagues in professional development.

7.03. Credit fully the work of others and refrain from taking undue credit.

7.04. Review the work of others in an objective, candid, and properly-documented way.

7.05. Give a fair hearing to the opinions, concerns, or complaints of a colleague.

7.06. Assist colleagues in being fully aware of current standard work practices including policies and procedures for protecting passwords, files and other confidential information, and security measures in general.

7.07. Not unfairly intervene in the career of any colleague; however, concern for the employer, the client or public interest may compel software engineers, in good faith, to question the competence of a colleague.

7.08. In situations outside of their own areas of competence, call upon the opinions of other professionals who have competence in that area.

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. In particular, software engineers shall continually endeavor to:

8.01. Further their knowledge of developments in the analysis, specification, design, development, maintenance and testing of software and related documents, together with the management of the development process.

8.02. Improve their ability to create safe, reliable, and useful quality software at reasonable cost and within a reasonable time.

8.03. Improve their ability to produce accurate, informative, and well-written documentation.

8.04. Improve their understanding of the software and related documents on which they work and of the environment in which they will be used.

8.05. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.

8.06 Improve their knowledge of this Code, its interpretation, and its application to their work.

8.07 Not give unfair treatment to anyone because of any irrelevant prejudices.

8.08. Not influence others to undertake any action that involves a breach of this Code.

8.09. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.

This Code was developed by the IEEE-CS/ACM joint task force on Software Engineering Ethics and Professional Practices (SEEPP):

Executive Committee: Donald Gotterbarn (Chair), Keith Miller and Simon Rogerson;

Members: Steve Barber, Peter Barnes, Ilene Burnstein, Michael Davis, Amr El-Kadi, N. Ben Fairweather, Milton Fulghum, N. Jayaram, Tom Jewett, Mark Kanko, Ernie Kallman, Duncan Langford, Joyce Currie Little, Ed Mechler, Manuel J. Norman, Douglas Phillips, Peter Ron Prinzivalli, Patrick Sullivan, John Weckert, Vivian Weil, S. Weisband and Laurie Honour Werth.

©1999 by the Institute of Electrical and Electronics Engineers, Inc. and the Association for Computing Machinery, Inc.

This Code may be published without permission as long as it is not changed in any way and it carries the copyright notice.

Read More [...]

Introduction to the Project

The intended project is to design and implement a website for HyperJet Technologies (Pvt) Ltd which is an emerging trading partner of telecommunication equipment. HyperJet is a manufacturer of telecommunication equipment and at the same time an industrial marketing company that offers telecom connectivity and surge protection solutions made by ethical manufacturers to telecom operators, industrial customers, systems integrators, contractors and project operators. The company is more concerned towards green business and inspiring the society to create a culture of ethical consumerism.

The main purpose of the site is to promote sustainable telecommunication and acknowledge the customers about ethical consumption while encouraging all the stakeholders to follow the righteous practices. Environment responsible trading and manufacturing is one of the main considerations of the company. It is expected that the site would cover each and every aspect of green business initiative, ethical use of resources and environment protection and present their intentions to the world while providing a platform (probably through a forum) to discuss any issues related to company, career opportunities and most importantly regarding the services they render to the community through their green concept and ethical manufacturing standards.

Other members of the group:

Prashan Madumal    http://hyperjetethicalissues.wordpress.com/

Naveen Deshan       http://professionalissues191.wordpress.com/

Read More [...]