Changes

Q10.  ''' What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

Q10.  ''' What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

# Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

Ans.

Ans.

#. Preparation phase

#Preparation phase

  Time : April 25 - may25

Time : April 25 - may25

 

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

    

    

   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.

   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

#Coding Phase

   Time: May 25- July1 ( This phase would be subdivided to different phases )

   Time: May 25- July1 ( This phase would be subdivided to different phases )

 

#*divisions for coding timeline

  * divisions for coding timeline

#* decide approach for programming

  * decide approach for programming

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

   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

#Testing Phase

   Time: July7- July 25

   Time: July7- July 25

  * full testing of system with different phases

#* full testing of system with different phases

  * use coverage analysis to know the redundance code and improving it further

#* use coverage analysis to know the redundance code and improving it further

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

   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

   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

b) 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.

b) 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

#Finalizing phase / Revision

  Time: from August 1 to END.

Time: from August 1 to END.

 

#* review of code/ algorithm

  * review of code/ algorithm

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

  Documentation stuffs would go in this phase

  Documentation stuffs would go in this phase