Friday, July 17, 2015

Well Written Documnet

Posted by  On 
8.03. Improve their ability to produce accurate, informative, and well-written documentation. Documentation is an important part in an web development project. Because it will help clients and team members to get information about   how project is going on and evaluate the work , detect errors...

Correcting Errors

Posted by  On 
6.08. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work. As the persons entirely responsible for the ultimate software product or site, it’s the software engineer’s duty to detect, correct and report errors in it or any...

Credit The Work

Posted by  On 
7.03. Credit fully the work of others and refrain from taking undue credit. It is a vital fact that the software engineers and web developers shall give full credit to work of others and refrain from taking undue credit for work which they are not creditable. Although it is also unprofessional...

Understand Specifications

Posted by  On 
3.07. Strive to fully understand the specifications for software on which they work. As it is conveyed in the code of conduct, software engineers should endeavor to understand the specifications of the software that they are currently working on or they are going to develop in the future. It is...

Monday, July 13, 2015

Team Power

Posted by  On 
6.04. Support, as members of a profession, other software engineers striving to follow this Code. This closure is important when working with a team. Because this closure promotes team members to work with each other in a more ethical way. A software engineer should support other software engineers...

Thursday, June 18, 2015

Document Management

Posted by  On 
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. Despite certain software being of great importance to society, many an occasion has been reported where the content of functionality...

How we achive Collaboration

Posted by  On 
7.05 Give a fair hearing to the opinions, concerns, or complaints of a colleague. Finally this is a team work after all to develop the system according to the client specifications. So when a team member or a relevant party to the project has a suggestion, complain, a new idea or a different...

Tuesday, June 16, 2015

How We Provide Our Best Service

Posted by  On 
2.01. Provide service in their areas of competence, being honest and forthright about any limitations of their experience and education. This code emphasis that it’s necessary to being honest and forthright about any limitations of client’s education and experience when offering developer’s services....

Monday, June 15, 2015

How we achieve a good quality in our application

Posted by  On 
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. In short, a high quality application is one that provides relevant, useful content and a good user experience, however, there are many individual factors that...

Friday, June 12, 2015

Identify the Responsibility

Posted by  On 
1.01.Accept full responsibility for our own work. The very first of the code of conduct conveys that developing a website or any software product on behalf of someone makes you responsible for the work you have authorized to do. After client handed over the work to you he/she expect a proper...
Subscribe to: Posts (Atom)