Marbles: Difference between revisions
No edit summary |
No edit summary |
||
| Line 87: | Line 87: | ||
#*gathering requirements of the project | #*gathering requirements of the project | ||
#*getting involved with Mentor in verifying and validating the requirements. | #*getting involved with Mentor in verifying and validating the requirements. | ||
#*Architectural design / Pseudo code. | #*Architectural design / Pseudo code. <br> | ||
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. | |||
<br>This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would | |||
| Line 97: | Line 96: | ||
#* actual coding, testing accordingly | #* actual coding, testing accordingly | ||
#* documenting code parallely | #* documenting code parallely | ||
#* periodically sharing information with mentors and community members | #* 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> | |||
<br> This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can | |||
#Testing Phase ( Time: July7- July 25 ) | #Testing Phase ( Time: July7- July 25 ) | ||
| Line 109: | Line 106: | ||
#* 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> 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> | ||
* 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. ) | ||
| Line 117: | Line 114: | ||
#* production of coverage reports, analysis, performance etc. | #* production of coverage reports, analysis, performance etc. | ||
#* discussions on limitations of software and beneficials. | #* discussions on limitations of software and beneficials. | ||
#* preparing final deployments for various systems. | #* preparing final deployments for various systems.<br> | ||
<br> Documentation stuffs would go in this phase | Documentation stuffs would go in this phase | ||
Time line: Seems very little time to do so many things, but I will try to give the best from my side. | Time line: Seems very little time to do so many things, but I will try to give the best from my side. | ||