Binary Spectrum Geeks at work

- Anjana.M 

We often see programmers jump to their seats and start coding as soon as they just hear any requirement. They may be able to complete the task, but may actually be lost in fixing the logical errors for a long time.

I have followed this approach that I am stating below, and yes, it worked well. I also believe that this is a stress free approach towards developing and implementing the requirement.

This is just doing object modeling in a well planned way. This surely can be achieved with UML tools. But paper work at times does prove to be quicker.

Let me know your thoughts on it and looking forward to know your development approaches as well.

Here are the 10 steps for a planned approach:

Step-1: Get requirement

Step-2: Don’t start development as soon as you get the requirement

Step-3: Lets follow the divide and rule approach - Divide the requirement into subtasks! We may have a list of subtasks

Step-4: Rule Them -Recognize the dependent task

Step-5: Create a class with requirement's name

Step-6: Make the subtasks as methods in the class

Step-7: Recognize the Inputs and Outputs for each method

Step-8: Build the DBQUERY

Step-9: Include the logic

Step-10: Unit test with SOP for each method in the class.

(The author, Anjana.M, is a Software Engineer at Binary Spectrum)