Student projects/Integrated bug tracker
Bug Tracker Module
System Features
- Use Moodle authentication and user accounts to login/report bugs/assign bugs/resolve bugs
- Display HTML/PHP/Javascript/other Web code without error
- Link related/dependent bugs and the status of related/dependent bugs
- 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
- Subscribe/unsubscribe to receive bug emails
- Generate bug reports by user/severity/build/status
- Generate Release Notes
- Create and save common reports/queries
System Development Lifecycle
Analysis
Data Flow Diagrams
Entity-Relationship Diagrams
Design
Structure Chart
Database Schema
Use Cases
Look and Feel
Design Specs
Page flow
- Report a Bug Page
- View Page
- Browse
- Search
- Reports
- Admin Page
In an effort to make the bug tracker as generic and customizable as possible, administrating the bug tracker is similar to administrating a quiz. In a quiz, there are three parts: the quiz body, the quiz category, and the quiz questions. In the bug tracker, there are two parts: the bug tracker and the bug category.
The bug tracker is analogous to the quiz body in that both contain settings that are considered common to all bug trackers and quiz bodies respectively.
The Admin Page will allow instructors of a course to administrate the bug tracker. The page will allow instructors to create new bug categories.
- Profile
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
July 14, 2006
- Start migrating old Moodle Bugs
July 28, 2006
- Second Deliverable - Prototype 2
July 28, 2006 - August 14, 2006
- QA & Fix bugs
- Accessibility Compliance?
August 7 - August 21, 2006
- Documentation
August 21, 2006
- Final Deliverable - Finished Product
