Expected output is not available in spite of putting all the efforts like SRS / SDD, data dictionary,
By Sanjay Tamboli | On February 22, 2007 | In Programming Tutorials and Articles | Rated 
DO:
1. Follow the company coding standard.
2. Read the SRS / SDD carefully and understand the forms.
3. Understand and write down the instruction of the functional and technical requirement of the form. This is very important since we are developing enterprise application for multiple branches and locations of different hierarchy.
4. Ask concerned PL in case of any doubt at any point of time so that problems / errors do not pop up during testing / implementation.
5. Find out the pre – requisite and post – requisite of the form.
6. Put the valid & sensible data into the required masters and transactions.
7. Do the coding such a way so that maintenance of the forms will be easier. I.e. If length of the field is changed then form should take care of it automatically.
8. Minimize the scrolling of the form.
9. Do proper alignment of all the controls.
10. Do not delete any data at any point of time.
11. In data search / find window give at least four to five columns which make sense to users with respect to the context of the field’s and form’s requirement.
12. Enable and disable the controls with respect to the context of the data. I.e. if application is forwarded to other location then do not enable edit or delete button.
13. Take the maximum advantages of database objects like triggers, functions and stored procedures.
14. Share your technical expertise when you achieve something which is abnormal in routine coding.
15. Avoid multiple trips to the database server.
16. Think of a copy of static data to the client side. I.e. District data / system parameter data are not changed very often so keep such data on the client side.
17. Load your changes on the test server and test your changes on test server without fail.
18. Set combo box width to the maximum length of the data being displayed in the list.
19. Same way, make sure that controls have enough space to display data when we take help of select / find window.
20. Height of the text box / combo box / list box should vary with respective labels. I.e. when labels occupy two lines.
21. Give meaningful message when any condition fails or any event takes place. Also message should be picked up from database according to the message no.
22. Understand the internal relation among the fields and enable / disable the field. Also accept the valid data with the context of data in the previous fields.
23. Have the complete environment for development. I.e. Install the font and required files.
24. Have code review with technical leaders and seniors and take care of all the points / suggestions / comments without fail.
25. For data maintenance have one sample program with all the possible conditions. I.e. For master / detail transaction have one sample program.
26. Get back to the concerned PL if you find any problem as per SRS / SDD.
DONT
In next sequence…….
www.semaphore-software.com
Conclusion:
In nut shell every programmer has to be analyst programmer. Do work with commitment. Check your work with all the possible combination of valid and invalid data. Do not assume that form will work 100 % right without 100 % test.
1. Follow the company coding standard.
2. Read the SRS / SDD carefully and understand the forms.
3. Understand and write down the instruction of the functional and technical requirement of the form. This is very important since we are developing enterprise application for multiple branches and locations of different hierarchy.
4. Ask concerned PL in case of any doubt at any point of time so that problems / errors do not pop up during testing / implementation.
5. Find out the pre – requisite and post – requisite of the form.
6. Put the valid & sensible data into the required masters and transactions.
7. Do the coding such a way so that maintenance of the forms will be easier. I.e. If length of the field is changed then form should take care of it automatically.
8. Minimize the scrolling of the form.
9. Do proper alignment of all the controls.
10. Do not delete any data at any point of time.
11. In data search / find window give at least four to five columns which make sense to users with respect to the context of the field’s and form’s requirement.
12. Enable and disable the controls with respect to the context of the data. I.e. if application is forwarded to other location then do not enable edit or delete button.
13. Take the maximum advantages of database objects like triggers, functions and stored procedures.
14. Share your technical expertise when you achieve something which is abnormal in routine coding.
15. Avoid multiple trips to the database server.
16. Think of a copy of static data to the client side. I.e. District data / system parameter data are not changed very often so keep such data on the client side.
17. Load your changes on the test server and test your changes on test server without fail.
18. Set combo box width to the maximum length of the data being displayed in the list.
19. Same way, make sure that controls have enough space to display data when we take help of select / find window.
20. Height of the text box / combo box / list box should vary with respective labels. I.e. when labels occupy two lines.
21. Give meaningful message when any condition fails or any event takes place. Also message should be picked up from database according to the message no.
22. Understand the internal relation among the fields and enable / disable the field. Also accept the valid data with the context of data in the previous fields.
23. Have the complete environment for development. I.e. Install the font and required files.
24. Have code review with technical leaders and seniors and take care of all the points / suggestions / comments without fail.
25. For data maintenance have one sample program with all the possible conditions. I.e. For master / detail transaction have one sample program.
26. Get back to the concerned PL if you find any problem as per SRS / SDD.
DONT
In next sequence…….
www.semaphore-software.com
Conclusion:
In nut shell every programmer has to be analyst programmer. Do work with commitment. Check your work with all the possible combination of valid and invalid data. Do not assume that form will work 100 % right without 100 % test.