Growth through Partnership Customer-driven Measures Quality and Innovation

Fueling Thought, Igniting Action

Development Ethics
310

Relationship

Follow coding practices/standards Understanding the business requirements Plan your development task Raise your doubts in requirements then & there

Discuss with other developers who does interdependent tasks

Purpose of unit testing? Why junit test cases? Review your own code once the task/sub-task is finished Do peer review before you comit the code to SVN Be proud for developing a bug free module/screen
2
Infoview Confidential

Reward

Contents
Trust

Relationship

Follow coding practices/standards

Understanding the requirements

Go through online tutorials Go through java and other coding standards Do some sample exercises on new frameworks

Functional leads are responsible for making the developers understand the business requirements correctly Individual developers are equally responsible in understanding the requirements
Infoview Confidential

Reward

Trust

Relationship

Plan your development task

Raise your doubts in requirements then & there

Split the development activity into various sub tasks Do a flow diagram of various tasks If possible write a pseudo code This will raise various missing spec even before starting coding

Raising the doubts then and there will save developer lot of time (will avoid code rewriting) Functional leads should address them ASAP

Infoview Confidential

Reward

Trust

Relationship

Discuss with other developers who does interdependent tasks

Purpose of unit testing?

Have good rapport with other developers and your ideas and views This will avoid different developers doing the same task

Unit test is done by the developer in development stage itself Developer should run all possible test cases Ensure bug free module

Infoview Confidential

Reward

Trust

Relationship

Why junit test cases? Improve code quality It will ensure testing of all possible scenarios Avoid minor bugs when testing by testers Regression testing can be done easily

Review your own code once the task/sub-task is finished Review will lead to improved code quality See difference of each modified file before commit Resolve conflicts if any before commit Commit task/subtask wise instead of individual files

Do peer review before you commit the code to SVN Compulsory external code review before commit Fix code review bugs if any

Infoview Confidential

Reward

Trust

Relationship

Be proud for developing a bug free module/screen

Infoview Confidential

Reward

Trust

Lets improve our code quality...

Thank You

Growth through Partnership

Customer-driven Measures
Quality & Innovation