Scribd
Upload
46 views

Programming Check List

This document provides a checklist for various tasks related to a ticketing system project. It includes guidelines for project discussions, status updates, coding standards, testing procedures, handling payroll issues, backups, and prioritizing critical issues. Adherence to procedures around coding, testing, and backups is emphasized to ensure quality and avoid problems. Timely support and responsibility for resolving issues, especially those involving payroll, purchase orders, and contracts, is also stressed.

Uploaded by

peratchiselvam_1985
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
46 views

Programming Check List

This document provides a checklist for various tasks related to a ticketing system project. It includes guidelines for project discussions, status updates, coding standards, testing procedures, handling payroll issues, backups, and prioritizing critical issues. Adherence to procedures around coding, testing, and backups is emphasized to ensure quality and avoid problems. Timely support and responsibility for resolving issues, especially those involving payroll, purchase orders, and contracts, is also stressed.

Uploaded by

peratchiselvam_1985
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

CHECK LIST

TICKETING SYSTEM:

MAKE SURE WHENEVER WE ARE DISCUSSING ABOUT THE PROJECTS/


UNDERSTAND CLEAR/ CREATE STRUCTURE/ DISCUSS ANY CLARIFICATION/
START WORKING ON THE PROJECT.
UPDATE ALL THE RELATED THINGS IN THE CONTACT.VOLUMECOCOMO.COM
AS PROJECTS APPLICATION OR PROGRAMMING DAILY SUPPORT.
UPDATE THE STATUS ON DAILY BASIS. PROJECT LEAD/ MANAGEMENT WILL
REVIEW THOSE UPDATES AND REPLY COMMENTS ON THE SAME.
TRY TO UPDATE THE COMMUNICATION EMAIL REGARDING DAILY SUPPORT
ISSUES SO THAT EVEN IF WE ARE ABSENT OTHER PROGRAMMERS CAN TAKE A
LOOK AT THE ISSUE AND GIVE SOLUTION OR HAVE CLEAR PICTURE.

CODING:
* USE SIMILAR NAMING CONVENTION FOR WINDOW/DATAWINDOW/FN/SP/VARIABLES
* WHENEVER CREATING DATAWINDOW FOR CODE TABLE NAME IS SAME AS TABLE,
SO THAT WE CAN FIND EASY.
* MENTION THE CODE CHANGE HISTORY WITH THE DATE/NAME/REASON FOR
CHANGES.
* IF WE ARE INCLUDING NEW COLUMNS IN THE DW, CHECK FOR ROWSCOPY/MOVE
AND SHAREDATA FUNCTION. AVOID NOT WORKING BECAUSE OF THOSE.
* UPDATE PROPERTIES - CHECK AGAIN
* TAB ORDER - CHECK
* SHOULD BE IN THE PRINTABLE FORMAT AND IN A SINGLE PAGE.
* REPORT SHOULD BE IN READABLE FORMAT - PRESENT AS GOOD AS POSSIBLE.
* CHECK FOR THE DATA INTEGRITY
* TRY TO WRITE PERFECT SQL QUERIES TO RETRIEVE THE DATA IN SHORT TIME
WHEN DESIGN REPORTS.
* CHECK THE KEYS/ INDEX WHEN JOINING TABLES.

TESTING:
* USER MANUAL CREATING

* UPDATE THE MANUAL IN THE GENERAL PATH


* COMMUNICATE TO THE USERS
* MAKE SURE THEY UNDERSTAND BY CONDUCTING MEETING WITH THEM AND
CONFIRM UNDERSTANDING
* CHECK FOR THE DATA AFTER 1 WEEK OR 2 WEEKS. MAKE SURE USER USES NEW
DEVELOPMENTS OR NOT, IF NOT TRY TO COMMUNICATE THE PROBLEM AND FIX.

PAYROLL:
* DON'T TOUCH THE PAYROLL SOFTWARE DURING PAYROLL GENERATION. IT MAY
AFFECT OTHER EMPLOYEES WHICH CAN'T BE FOUND DURING GENERATION.
BECAUSE OF THIS PAYROLL USER TRY TO GET GOOD NAME ESCLATE THE ISSUES
AND MAKE PROGRAMMERS IDIOT.
* ONCE PAYROLL GENERATED, GIVE THE AMOUNT TO MR. ANDREW. IF IT IS MAJOR
AND VARIATION OF AMOUNT IS HIGH, DISCUSS WITH MR. ANDREW/ MR. CHRIS AND
ADJUST IN THE SAME MONTH.IF NOT NEXT MONTH.
* CHECK THE NIGHT SHIFT PERSONS SALARY ONCE AGAIN. ALSO DOUBLE CHECK
THOSE GETTING CONTRACT PAY DURING THE MONTH. (CONTRACT CALCULATION
WRITTEN DIRECT IN THE BACKEND)
* CHECK THOSE EMPLOYEES WHO TRANSFER TO OTHER LOCATION OR TRANSFER
WITH IN THE MONTH FROM DAY SHIFT TO NIGHT SHIFT OR NIGHT SHIFT TO DAY
SHIFT.
* DONT TOUCH PAYROLL CODE, IF YOU ARE IN BAD MOOD.

BACKUP:

MAKE SURE SOUCE BACK IS PERFECT. TRY TO CHECK ONCE IN 15 DAYS


ABOUT THE BACKUP
MAKE SURE TO CHECK THE DATABASE BACK UP ABOUT THE PROZIA/ A1/
WINFASHION. ALL BACKUP ARE ALREADY RUNNING AS AUTOJOB. EVEN
THOUGH PLEASE MAKE SURE THERE IS SPACE IN THE BACKUP SERVER AND
ATLEAST LAST 3 BACKUP EXISTING.

CRITICAL ISSUES:

DONT GIVE A REASON THAT WE FOLLOW PROCEDURE AND AVOID SOLVING


ISSUES. TRY TO GIVE TIMELY SUPPORT TO THE USERS. TAKE RESPONSIBILITY.
ESPECIALLY PAYROLL ISSUES/ PO ISSUES/ CONTRACT ISSUE SHOULD BE GIVEN
HIGHEST PRORITY.

You might also like