GSoC Requirements Gathering

Owned by Former user (Deleted)
Last updated: Aug 18, 2010Version comment
1 min read
  • We need to develop air-tight requirements for each project.
    • Functional requirements (what the system is required to do)
    • Use cases (workflow for each functional requirement)
    • Non-functional requirements (performance-related, etc)
    • Test cases
    • User interface design (mockups) - IMHO, this might be a huge undertaking, but is well worth it
    • Timeline/milestones
    • Coding conventions
    • JUnit testing requirements
    • Request for proposal (basically, just packaging up all this stuff and asking the student for a submission).
  • We also need to put together review material for the students to peruse before the project begins (or at project onset)
    • Related source code
    • Sample code - stubs
    • Research projects and papers that discuss the problem (i.e. name matching must have a hefty amount of research material)
    • Links to related-projects (for reporting: BIRT, Pentaho, etc)
    • Books that might be helpful to review