Difference between revisions of "IS480 Team wiki: 2013T1 Marvel lous Final"
Line 140: | Line 140: | ||
==<div style="background: #000000; padding: 13px; font-weight: bold; line-height: 0.3em; text-indent: 20px;font-size:26px; font-family:Arial"><font color= #ffffff>Project Risks</font></div>== | ==<div style="background: #000000; padding: 13px; font-weight: bold; line-height: 0.3em; text-indent: 20px;font-size:26px; font-family:Arial"><font color= #ffffff>Project Risks</font></div>== | ||
− | ====<div style=" border-bottom: 1px dotted; background: #FFFFFF; padding: 12px; font-weight: bold; line-height: 0.5em"><font color= black size = 4>Risk | + | ====<div style=" border-bottom: 1px dotted; background: #FFFFFF; padding: 12px; font-weight: bold; line-height: 0.5em"><font color= black size = 4>Risk Categories</font></div>==== |
Revision as of 08:32, 3 December 2013
Contents
Final Immediate Deliverables
FYP Marvel-lous Final Presentation
Link to Administrative Site
Link to download application
Project Summary
Iterations
Completed 9 Iterations
Milestones
Milestones completed:
1. Proposal
2. Acceptance
3. User Test 1
4. Mid-Term
5. Poster
6. User Test 2
Milestones in progress:
1. Final
Milestones (future):
1. Transfer of project to client
Note: Transfer of Project and Manual --> 6th December 2013 Training --> 6th December 2013
Functionalities
Total number of functions: 52
Number of completed functions: 52
Percentage of project completed: 100%
Deployment
Deployments:
- Website deployed to Google App Engine
- Android Application deployed to Google Play Store
Total number of deployments: 24
Type of deployment: White label
Project Highlights
Project Schedule
Timeline
Schedule Breakdown
Note: To view our Schedule, please click here.
Planned vs Actual
Note: This section only displays breakdown for delayed iterations. To view our Schedule Metric breakdown, please click here.
Project Metrics
Schedule Metric
Bug Metric
Reason for Iteration 8:
1. Payment
2. Enhanced viewing
Action plan:
1. Stop current iteration and fix bugs
2. Team members not part of Payment and Enhanced Viewing team continued with Iteration 9 functions
Reason for Iteration 9:
1. Payment (In-app billing)
Action plan:
1. Do not implement feedback for UT 2
2. Use buffer period
Project Risks
Risk Categories
Risk Management
Technical Complexity
Google Endpoints
The team has diffculties at 2 stages with Google End Points:
1. Connection from data store to the application
2. Connection from the application to data store.
Quality of Product
Maintainability and Robustness
User Test 1
Intermediate Delivery
Stage | Document | Description |
---|---|---|
Project Management | Meeting Minutes | Iteration 1 to 7 - Internal, Supervisor & Client Meetings |
Project Metrics | Schedule and Bug Metric | |
Requirement Gathering | Market Research | Survey results and Research |
Analysis and Design | Diagrams | Use case diagram, ER diagram and Architecture Diagram |
Storyboard | Website | Website wire frames and screenshots |
Application | Application wire frames and screenshots | |
Testing | User Testing | User Testing 1 |
Submissions | Proposal | Proposal |
Acceptance | Acceptance presentation | |
Mid-Term | Mid-Term presentation |