Our project is to implement an
application which any user can be used to reduce their anger and depression.
Several steps are added according to both content and it will guide you to have
freedom from those problems.
Here it is mentioned that how the ACM
code of ethics will guide us to do a software ethically concerning all parties related
to the process.
1: PUBLIC
1.01 Accept full responsibility for their own work.
·
As the
developer of the application we are responsible for the product that we have
implemented.
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.
·
Public have its
own freedom to use as they feel safe. But the intention of the developer is
always to do good to the public.
1.05. Cooperate in efforts to address
matters of grave public concern caused by software,
·
This is a web
based application. The user can simply log into the site using the URL and then
use the service. Its maintenance is totally done by the development group and the
UI is made very simply that any novice user can be understood it very easily.
1.07. Consider issues of physical
disabilities, allocation of resources, economic
Disadvantage and other factors that can
diminish access to the benefits of software.
·
This service is
totally free and anyone can access it. It is no barriers to access to the site
(initial payments etc.) and the output also free. Anyone who can handle simple
computer abilities such as mouse clicking can use this.
1.08. Be encouraged to volunteer
professional skills to good causes and contribute to public
·
Any developer can use these free resources to contribute to the public
making good Causes.
2: CLIENT AND EMPLOYER
We haven’t had
any particular client as we proposed and developed the site ourselves to do
good to the public. But some resources have been advised us how to carry the
implementation according to give a positive impact on the user.
2.01. Provide service in their areas of
competence, being honest and forthright about any limitations of their
experience and education.
·
Experience and
the education of the developers was well enough for implementation process.
2.02. Not knowingly use software that is
obtained or retained either illegally or unethically.
·
All tools and
methods used are open source components.
2.08. Accept no outside work detrimental to
the work they perform for their primary employer.
·
During the
implementation time, the team was only concern about the project. We have
reserved time that every member can be given his/her full attention to the
task.
3: PRODUCT
This is a free
product that anyone can be used as their will and anyone can simply access to
the product and use it. No one is forced to use the product so the user has the
full freedom to choose this among the number of the other products which are
available in the market.
3.03. Identify, define and address ethical,
economic, cultural, legal and environmental
Issues related to work projects.
·
Simple market
research has been carried out since this is a small scale project and specially
ethical and environmental issues have been identified related to the
scope. Concerning those circumstances,
the product design was implemented.
3.04. Ensure that they are qualified for any
project on which they work or propose to work by an appropriate combination of
education and training, and experience.
·
With the
current knowledge and experience what we have, we can work on up to a limit,
Education and training is needed to do more.
3.05. Ensure an appropriate method is used
for any project on which they work or propose to work.
·
With the experience
we have got and the guidance we have, it is the best and most suitable method
that we have used.
3.10. Ensure adequate testing, debugging,
and review of software and related documents on which they work.
·
Initially the
product has tested by us to find out bugs and those were debugged. Then as the
next step some random users are invited to use the product and feedback us, it
was helpful to improve the usability of the product.
3.13. Be careful to use only accurate data
derived by ethical and lawful means, and use it only in ways properly
authorized.
·
Highly reliable
resources were selected to take content and details which will be published in
the product. Those are famous and recommended sources in the internet approved
by thousands of users.
3.14. Maintain the integrity of data, being
sensitive to outdated or flawed occurrences.
·
The way data
are presented to the user is simple and the content of it is true to past
present and future since those are approved treatment methods that have been
carried out for a long time. If any necessary changes, we are responsible to
maintain and change it appropriately.
3.15 Treat all forms of software maintenance
with the same professionalism as new development.
·
Each phase is
treated equally and as the way it should be because we are well understood that
every step connected to the others.
4: JUDGMENT
4.01. Temper all technical judgments by the
need to support and maintain human values.
- · Usability- Color usage, placement of buttons and content is carefully designed and implemented because it is properly studied and judged that these features will affect the user directly.
- · Frameworks- a MVC JavaScript framework has been used to architecture the product. This judgment is so accurate for small scale applications.
- · HTML5/CSS3- with these technologies, it is easily possible to make applications in less time without affecting the quality or the functionalities. These will smoothly collaborate with JavaScript frameworks.
4.02 Only endorse documents either prepared
under their supervision or within their areas of competence and with which they
are in agreement.
·
Technical
documents have been prepared under developer’s supervision. The other documents
are supervised by authorized professionals in the relevant field.
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.02. Ensure that software engineers are
informed of standards before being held to them.
·
As
professionals they are bound to behave according to the ACM code of ethics for
software engineers.
5.12. Not punish anyone for expressing
ethical concerns about a project.
·
In this project,
every idea / opinions were welcome and those were considered on how to use
effectively to make the development process efficiently. Those ideas are well
treated.
6: PROFESSION
6.02. Promote public knowledge of software
engineering.
·
New
technologies that come in to the field and existing ones will be preferred to
tell others, in our case, we shared our knowledge among our friends even though
we are not professionals in the field yet. We believe that public will gain the
knowledge from us.
6.08. Take responsibility for detecting,
correcting, and reporting errors in software and associated documents on which
they work.
·
Each member in
the project honestly and quickly informed if there were any fault or thing to
be changed. Some informal meetings brief everyone about bugs and solutions are
discussed and found.
7: COLLEAGUES
7.01. Encourage colleagues to adhere to this
Code.
·
As we will be
professionals in the future, we are responsible to carry out our practices
according to the code of conduct. In the same time I help my friends and advise
them as we can to work along with these circumstances.
7.02. Assist colleagues in professional
development.
·
I enjoy helping
to others with new technologies and I believe that will help them to improve
their knowledge in the field. In the same time my colleagues will help me in
the same way.
7.03. Credit fully the work of others and refrain
from taking undue credit.
·
As they work
hard I appreciate them and encourage them to do more.
7.05. Give a fair hearing to the opinions,
concerns, or complaints of a colleague.
·
Every idea was
equally mattered to take the final decision and make the product. Some ideas
are rejected with reasoning and some of those are implemented with adjustments.
Though eventually everyone in the team were satisfied that they got a chance to
express their opinions.
7.08. In situations outside of their own
areas of competence call upon the opinions of other professionals who have
competence in that area.
·
Especially for
this project, we need to get experts view in psychological field. Reliable
medical reviews had to use to put the content in the application.
8: SELF
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.
·
The experience
of what we gain from this project will be a matter to improve our technical knowledge
and working in a team and more management skills development.it is very
important to identify the role of a software engineer and work according to
that.
8.02. Improve their ability to create safe,
reliable, and useful quality software at reasonable cost and within a
reasonable time.
·
The practice
and experience we receive with the time can be used to create reliable
softwares. Long term Experience in the specific platforms (.net, j2ee) will be
helpful to identify bugs quickly and solutions can be implemented in less time.
8.05. Improve their knowledge of relevant
standards and the law governing the software and related documents on which
they work.
·
Experience in
the field will help to identify different environments and adapt to them will
be easy. Working under different regulations in different companies, but it is
a must that you always follow the standard code of ethics.
Positiverun.esy.es is our URL of the web application.
