Student projects/Integrated bug tracker: Difference between revisions
From MoodleDocs
Line 21: | Line 21: | ||
==Implementation== | ==Implementation== | ||
*Create database, tables, etc. | |||
*Create bug database access library | |||
**Getter, setters, etc. | |||
*Create bug submission form | |||
*Submit to database | |||
*Create View bug form | |||
*Incorporate Moodle Authentication | |||
==Testing== | ==Testing== |
Revision as of 07:07, 5 June 2006
Integrated Moodle Bug Tracker
System Features
- Uses Moodle authentication and user accounts to login/report bugs/assign bugs/resolve bugs
- Able to display HTML/PHP/Javascript/other Web code without error
- Able to link related/dependent bugs and the status of related/dependent bugs
- Able to view a particular bug as an external user (not logged in) using a simple URL (e.g. http://moodle.org/mod/tracker/view.php?issue=3455)
- All fields capable of using Moodle rich text editor as appropriate
- Easily subscribe/unsubscribe to receive bug emails
System Development Lifecycle
Analysis
Data Flow Diagrams
Entity-Relationship Diagrams
Design
Structure Chart
Database Schema
Use Cases
Look and Feel
Design Specs
Implementation
- Create database, tables, etc.
- Create bug database access library
- Getter, setters, etc.
- Create bug submission form
- Submit to database
- Create View bug form
- Incorporate Moodle Authentication
Testing
Tentative Timeline / Milestones
June 28, 2006
- First Deliverable - Prototype
July 7, 2006 - July 14, 2006
- User Testing
- Accessibility Compliance?
July 14, 2006
- Start migrating old Moodle Bugs
July 28, 2006
- Second Deliverable - Prototype 2
July 28, 2006 - August 14, 2006
- QA & Fix bugs
August 7 - August 21, 2006
- Documentation
August 21, 2006
- Final Deliverable - Finished Product