Marbles: Difference between revisions

Line 87:

#*gathering requirements of the project

#*getting involved with Mentor in verifying and validating the requirements.

#*Architectural design / Pseudo code.This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would 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 community support on this very interesting project.

#*Architectural design / Pseudo code.

#*This phase, I would be communicating with people as much as possible, getting requirements and verifying with people or community. I would 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 community support on this very interesting project.

#Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )

#*divisions for coding timeline

Line 93:

Line 94:

#* actual coding, testing accordingly

#* documenting code parallely

#* periodically sharing information with mentors and community members~~ ~~

#* periodically sharing information with mentors and community members

This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can ~~devote~~ more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.~~ ~~

#* This phase will include actual coding. Since I already knew the related technologies and familiar to sugar development process. I can devote more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.

#Testing Phase ( Time: July7- July 25 )

#* full testing of system with different phases

Line 100:

Line 101:

#* fixing bugs if any

#* Last minute changes before final submission

#* finish any documentation steps if left.~~ ~~

#* finish any documentation steps if left.

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

#* 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

analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with~~ ~~

analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with

* 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~~ 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 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. )

#* review of code/ algorithm

Line 110:

Line 111:

#* discussions on limitations of software and beneficials.

#* preparing final deployments for various systems.

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.

@@ Line 87: / Line 87: @@
 #*gathering requirements of the project
 #*getting involved with Mentor in verifying and validating the requirements.
-#*Architectural design / Pseudo code.This phase, I would be communicating with people as much as possible, getting requirements and verifying <br> with people or community. I would also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project <br> development.I am sure to get community support on this very interesting project.
+#*Architectural design / Pseudo code.
+#*This phase, I would be communicating with people as much as possible, getting requirements and verifying <br> with people or community. I would also go to the pre-releases of similar softwares to get prons and cons and trying to improve in our project <br> development.I am sure to get community support on this very interesting project.
 #Coding Phase ( Time: May 25- July1 { This phase would be subdivided to different phases } )
 #*divisions for coding timeline
@@ Line 93: / Line 94: @@
 #* actual coding, testing accordingly
 #* documenting code parallely
-#* periodically sharing information with mentors and community members<br>
+#* periodically sharing information with mentors and community members
-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 devote<br> more time to coding and thus improving the project at each phases. I will share doubts with community if occurs.
 #Testing Phase ( Time: July7- July 25 )
 #* full testing of system with different phases
@@ Line 100: / Line 101: @@
 #* fixing bugs if any
 #* Last minute changes before final submission
-#* finish any documentation steps if left.<br>
+#* finish any documentation steps if left.
-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>
+analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with
-* 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 <br> familiar 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. )
 #* review of code/ algorithm
@@ Line 110: / Line 111: @@
 #* discussions on limitations of software and beneficials.
 #* preparing final deployments for various systems.<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.