122
edits
Changes
no edit summary
#*getting involved with Mentor in verifying and validating the requirements.
#*getting involved with Mentor in verifying and validating the requirements.
#*Architectural design / Pseudo code. <br>
#*Architectural design / Pseudo code. <br>
<nowiki> This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would <br> also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project development.I am sure to get <br> community support on this very interesting project.</nowiki>
<nowiki> This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would <br> also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project development.I am sure to get <br> community support on this very interesting project.</nowiki><br>
#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )
#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )
#*divisions for coding timeline
#*divisions for coding timeline
#* periodically sharing information with mentors and community members<br>
#* periodically sharing information with mentors and community members<br>
This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can <br> devote more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.<br>
This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can <br> devote more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.<br>
#Testing Phase ( Time: July7- July 25 )
#Testing Phase ( Time: July7- July 25 )
#* full testing of system with different phases
#* full testing of system with different phases
#* fixing bugs if any
#* fixing bugs if any
#* Last minute changes before final submission
#* Last minute changes before final submission
#* finish any documentation steps if left.
#* finish any documentation steps if left.<br>
After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and really love to <br>
<br> After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and really love to <br> analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with<br>
analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with<br>
* coverage
* coverage
* I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and familiar<br> with different tweaks to modify run time such as psycho module. This will help in increasing the robustness and stability of program.
* I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and familiar<br> with different tweaks to modify run time such as psycho module. This will help in increasing the robustness and stability of program.
#Finalizing phase / Revision ( Time: from August 1 to END. )
#Finalizing phase / Revision ( Time: from August 1 to END. )
#* review of code/ algorithm
#* review of code/ algorithm