Voice Timeplan

Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.

Project

• 14th May - 20th May: Analysis (1 week)
  • Extract requirements: study Moodle output and code to choose what to make voice enabled
    • Identify navigation(links) to be voice enabled.
    • Identify forms to be voice enabled.
    • Identify Text to be converted to speech to convey information through speech.
  • Begin project webpage, documentation and logs
• 21th May - 3rd June: Design (2 weeks)
  • Make an Architectural Design
  • Make an Implementation Proposal
• 4th June - 5th August: Implementation (9 weeks)
  • Implement Navigational Links (5 weeks)
    • Learn implementation intricacies VoiceXML(1 week)
    • Subtasks (to be decided in analysis phase)(4 week)
  • Implement forms to be voice enabled(4 weeks)
• 6th August - 17th August: Documentation (2 weeks)
  • Beta testing
  • Developer documentation
  • Moodle administrator documentation
  • Future roadmap and design plans
• 18th August - 31th August: Revision and Documentation

Mentor

• 16th April - 27th April: teach the student about the community (about 30 mins per day)
• 28th April - 13th May: create basic documentation about the project and tools to be used (about 1 hour per day)
• 14th May - 17th August (about 1-2 hours per day)
  • Solve student questions
  • Improve project design
  • Code quality assurance
  • Commit to Moodle CVS
  • Beta testing
• 20th August - 31th August: Marketing (1-2 hours per day)

Student

• 16th April - 27th April: learn about the community (about 30 mins per day)
• 14th May - 17th August: the project itself (about 7-8 hours per day)
• 20th August - 31th August: revision and marketing (2 hours per day)

Others

• Google Summer of Code 2007 Timeplan