Difference between revisions of "AAN Final Wiki"
Viryap.2011 (talk | contribs) |
Viryap.2011 (talk | contribs) |
||
Line 50: | Line 50: | ||
|View Booking|| Completed || 1||✓ | |View Booking|| Completed || 1||✓ | ||
|- | |- | ||
− | |Edit Booking || Removed from functionalities under request of client || 1 || | + | |Edit Booking || Removed from functionalities under request of client || 1 || - |
|- | |- | ||
− | |Delete Booking|| | + | |Delete Booking|| Removed from functionalities under request of client || 1 || - |
|- | |- | ||
|Paying for Booking || Completed || 1 ||✓ | |Paying for Booking || Completed || 1 ||✓ |
Revision as of 15:51, 13 April 2014
Contents
Project Progress Summary
Progress
Project Timeline
Project Highlights
Project Management
Project Status
Project Status
Module | Function | Status | Confidence Level | Deployment status | |
CORE | Register for LMS | ||||
Register | Not Completed | 1 | × | ||
Sign in | |||||
Sign in | Completed | 1 | ✓ | ||
Booking Management | |||||
Add Booking | Completed | 1 | ✓ | ||
View Booking | Completed | 1 | ✓ | ||
Edit Booking | Removed from functionalities under request of client | 1 | - | ||
Delete Booking | Removed from functionalities under request of client | 1 | - | ||
Paying for Booking | Completed | 1 | ✓ | ||
Locker Management | |||||
Add Lockers | Completed | 1 | ✓ | ||
View Lockers | Completed | 1 | ✓ | ||
Edit Lockers | Completed | 1 | ✓ | ||
Delete Lockers | Completed | 1 | ✓ | ||
Search for Lockers | |||||
Search Lockers | Completed | 1 | ✓ | ||
Feedback Management | |||||
Report faulty locker | Completed | 1 | ✓ | ||
View faulty locker reports | Completed | 1 | ✓ | ||
Update faulty locker status | Completed | 1 | ✓ | ||
Submit feedback | Completed | 1 | ✓ | ||
View feedback | Completed | 1 | ✓ | ||
Update feedback | Completed | 1 | ✓ | ||
Delete feedback | Completed | 1 | ✓ | ||
Locker Maintenance Account Management | |||||
Add Maintenance team | Completed | 1 | ✓ | ||
View Maintenance team | Completed | 1 | ✓ | ||
Edit Maintenance team | Completed | 1 | ✓ | ||
Delete Maintenance team | Completed | 1 | ✓ | ||
Statistics Dashboard | |||||
View Dashboard | Completed | 1 | ✓ | ||
Booking Window Management | |||||
Set/Open/Close Booking Window timing | Completed | 1 | ✓ | ||
Set/Edit Booking Timeframe | Completed | 1 | ✓ | ||
Messaging Management | |||||
Send Message | Completed | 1 | ✓ | ||
Delete Message | Completed | 1 | ✓ | ||
SECONDARY | iPhone App Development | ||||
Add locker bookings | Completed | 1 | ✓ | ||
View Locker | Completed | 1 | ✓ | ||
Report faulty lockers | Completed | 1 | ✓ | ||
View map | Completed | 1 | ✓ | ||
Android App Development | |||||
Add locker bookings | Completed | 1 | ✓ | ||
View Locker | Completed | 1 | ✓ | ||
Report faulty lockers | Completed | 1 | ✓ | ||
View map | Completed | 1 | ✓ |
For more information of the respective functions, visit AAN_Project_Management#Project_Status here!
Project Schedule (Plan Vs Actual):
Project Metrics
Schedule Metrics
To know how we calculate our schedule metrics, please refer to this!
For more information regarding Team AAN's mitigation plan, please refer to here!
Bug Metrics
To know how we calculate our bug metrics, please refer to this!
For more information regarding Team AAN's exact bugs, please look here!
Project Risks
S/N | Risk Statement | Consequence | Likelihood | Impact | Level | Contingency Plan |
---|
For the complete set of risks we face since the conception of project, please visit here! More information regarding how we measure our risks can also be found on that page.
Technical Complexity
Usability
Scalability
Flexibility
Quality of product
Intermediate Deliverables
Stage | Specification | Modules |
Project Management | Minutes | |
Metrics | ||
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use Case | Use Case Diagram |
Screen Shots | Prototype | |
Design | ER Model | ER Model |
System Architecture Diagram | Architecture Diagram | |
Testing | Heuristic Testing | Heuristic Test Results |
Usability Test Plan | Test Plan | |
Usability Test 1 Results | UT1 Results | |
Usability Test 2 Results | UT2 Results |
Deployment
Testing
There are three tests conducted for our system; one Heuristics and two Usability Testing.
In the Heuristics Testing, we aim to find out user's view towards the design of our application so that we can make changes accordingly and ensure that the final product will be of high quality and well-received by everyone.
Heuristics Info:Heuristics Testing
For our first usability test, we will like to find out how well can users navigate our system. This will allow us to further improve on our system and ensure that the end product will be something that is close to dummy proof. Also, since we will be catering the system to the entire SMU, students from other schools participated in our UT too to ensure that we have a diverse and somewhat balanced opinion.
Usability Test 1 Info:Usability Test 1
After our first usability test, we made changes to some parts of the system based on the feedbacks that we have. Furthermore, there is the addition of certain functionalities as well as the iPhone app. Therefore, the second usability test allows us to finetune our project and ensure that our final product will be something that OSL finds satisfactory. Similar to the previous UT, the majority of participants are SMU students since they are the one who will be mainly using the system.
Usability Test 2 Info:Usability Test 2