5.01 Ensure good management for any project on which they work, including effective procedures for promotion of quality and reduction of risk.
As Work break down we used following methodology. Since I and D.T.S.P. Madola are computer science undergraduates, we took the responsible for creating the proposed application. Since W.T.R. Epa is a information system undergraduate she took the responsible for requirement gathering. After gathering the Requirements we got together and discussed about how to improve the application. When we were building the application we created repository in github (click here) for version controlling purposes.
5.02. Ensure that software engineers are informed of standards before being held to them.
As software engineers we were well aware of what we have to create. Since we have no actual client we could not use any agile methodologies for the project. So we use the waterfall model as our software development methodology.
5.08. Not unjustly prevent someone from taking a position for which that person is suitably qualified.
When we considered of sharing work load we took the part that we are have potential with. No body forcefully others part by mentioning that it was easy or else. We had our respect to each other and we only had the professional affairs only.
Tuesday, June 16, 2015
Friday, June 12, 2015
Principal 6: PROFESSION
6.04. Support, as members of a profession, other software engineers striving to follow this Code.
We were about to start our career life and some point in our life we will hold the title "Software engineer". Therefor we should have the right to bear that title. So we should value the software code of conduct and follow it as best practice to gain out the best out of us. So this was a great opportunity for us to practice "software engineer code of conduct".
6.10. Avoid associations with businesses and organizations which are in conflict with this code.
We have used software, framework and technologies which have no license conflict with each others. Since we have published our code in github, it's inherently became open source code. We decided to publish this software under Apache license version 2.0 so any one interested can use the code as they will.
We were about to start our career life and some point in our life we will hold the title "Software engineer". Therefor we should have the right to bear that title. So we should value the software code of conduct and follow it as best practice to gain out the best out of us. So this was a great opportunity for us to practice "software engineer code of conduct".
6.10. Avoid associations with businesses and organizations which are in conflict with this code.
We have used software, framework and technologies which have no license conflict with each others. Since we have published our code in github, it's inherently became open source code. We decided to publish this software under Apache license version 2.0 so any one interested can use the code as they will.
Tuesday, June 9, 2015
Principal 7: COLLEAGUES
7.03. Credit fully the work of others and refrain from taking undue credit.
In our project we have mentioned about everything done by the members. Nobody has taken credit for others works.
7.05. Give a fair hearing to the opinions, concerns, or complaints of a colleague.
Different people have different views about a same thing. In our project everybody had a chance to express their ideas about the process. We used Facebook group chat and small meetings to discuss about the process. So everybody had a fair chance to give their opinions, and other members liked to hear them without ignorance.
In our project we have mentioned about everything done by the members. Nobody has taken credit for others works.
7.05. Give a fair hearing to the opinions, concerns, or complaints of a colleague.
Different people have different views about a same thing. In our project everybody had a chance to express their ideas about the process. We used Facebook group chat and small meetings to discuss about the process. So everybody had a fair chance to give their opinions, and other members liked to hear them without ignorance.
Tuesday, June 2, 2015
Principal 8: SELF
8.02. Improve their ability to create safe, reliable, and useful quality software at reasonable cost and within a reasonable time.
When we were developing the product, PhoneGap was the only unfamiliar technology we used. Since we are familiar with other technology we had the opportunity to create safe and useful product, within given time.
8.06 Improve their knowledge of this Code, its interpretation, and its application to their work.
This is the first time we got to follow the software engineering, code of ethics and I personally think this exposure will be a valuable when we go through our career life.
8.05. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.
When we were developing "Smart Finder", we get to know about software licenses and their usages. As we are going to be software engineers this knowledge will very helpful as Software engineers or we are going to start startup. Also since this product has a small bad consequences we studied about the laws that could relate to this through our friend in Faculty of Law, University of Colombo.
When we were developing the product, PhoneGap was the only unfamiliar technology we used. Since we are familiar with other technology we had the opportunity to create safe and useful product, within given time.
8.06 Improve their knowledge of this Code, its interpretation, and its application to their work.
This is the first time we got to follow the software engineering, code of ethics and I personally think this exposure will be a valuable when we go through our career life.
8.05. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.
When we were developing "Smart Finder", we get to know about software licenses and their usages. As we are going to be software engineers this knowledge will very helpful as Software engineers or we are going to start startup. Also since this product has a small bad consequences we studied about the laws that could relate to this through our friend in Faculty of Law, University of Colombo.
Monday, June 1, 2015
Apache License Version 2.0
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
- You must give any other recipients of the Work or Derivative Works a copy of this License; and
- You must cause any modified files to carry prominent notices stating that You changed the files; and
- You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
- If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Subscribe to:
Posts (Atom)