Table of Requirements
ID |
Requirements |
Rating |
Completed? |
Contributors |
RQ1 |
The application must be a data dictionary editor |
Must Have |
Complete |
Matt and Pius |
RQ2 |
The application must be able to create a data dictionary (logical and physical) for the required system e.g. for a customer system or for a payroll system |
Must Have |
Complete |
Matt and Pius |
RQ3 |
The application should be able to load the data dictionary for OpenEyes into the application |
Could Have |
Complete |
Matt and Pius |
RQ4 |
The application should ensure that the data dictionaries can handle the versioning of systems |
Should Have |
Complete |
Matt and Pius |
RQ5 |
The application should ensure that the data dictionary items can be mapped to other items of another system or version |
Should Have |
Complete |
Matt and Pius |
RQ6 |
The application should allow the extraction of data dictionary data The client decided that they no longer required this feature |
Should Have |
N/A |
N/A |
RQ7 |
The application should be able to compare data models |
Should Have |
Complete |
Matt and Pius |
RQ8 |
The application could be able to load XML schema data The client opted to stick with manual input and focus on the main functionality of the application |
Could Have |
N/A |
N/A |
RQ9 |
The application should allow a data dictionary to be mapped to other data dictionaries |
Should Have |
Complete |
Matt and Pius |
RQ10 |
The application must have a screen for loading data dictionaries |
Must Have |
Complete |
Matt and Pius |
RQ11 |
The application must have a screen that enables the maintenance of a single data dictionary (adding and removal of columns) |
Must Have |
Complete |
Matt and Pius |
RQ12 |
The application must have a screen for loading data |
Must Have |
Complete |
Matt and Pius |
RQ13 |
The application must have a screen that gives access to the default mapping tool |
Must Have |
Complete |
Matt and Pius |
Work Packages
Reporting
Work Package |
Category |
Contributors |
Bi-weekly report 1 Term 2 |
Report Writing |
All |
Bi-weekly report 2 Term 2 |
Report Writing |
All |
Bi-weekly report 3 Term 2 |
Report Writing |
All |
Bi-weekly report 4 Term 2 |
Report Writing |
All |
Bi-weekly report 5 Term 2 |
Report Writing |
All |
Elevator Pitch |
Reporting |
All |
Website Design |
Reporting |
Matt |
Team Video |
Video Report |
Matt |
Technical Presentation |
Reporting |
All |
Poster |
Reporting |
Pierce |
Client Liaison
Work Package |
Category |
Contributors |
1st Client Meeting of Term 2 |
Client Liaison |
Matt and Pius |
2nd Client Meeting of Term 2 |
Client Liaison |
All |
3rd Client Meeting of Term 2 |
Client Liaison |
All |
4th Client Meeting of Term 2 |
Client Liaison |
All |
Final Client Meeting |
Client Liaison |
Matt and Pius |
Emailing and Updating Client |
Client Liaison |
Matt |
Research
Work Package |
Category |
Contributors |
Ruby and MySQL research |
Research |
All |
Platform Research |
Research |
Matt |
CSV file upload research |
Research |
Matt and Pius |
Rails model, controller research |
Research |
Matt and Pius |
Nested Routing Research |
Research |
Pius |
Mapping Research |
Research |
Matt and Pius |
Editing values in table (best in place gem) |
Research |
Matt |
CSS styling and gems research |
Research |
Matt and Pius |
Forms |
Research |
Pius |
Flash and error message |
Research |
Pius |
Testing research |
Research |
All |
Testing
Work Package |
Category |
Contributors |
User acceptance tests |
Testing |
Matt |
Unit testing |
Research |
Pius |
Integration Testing |
Research |
Pius |