Difference between revisions of "IS480 Team wiki: 2012T2 ElderLove Midterm"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 40: | Line 40: | ||
rect 639 273 822 287 [[ IS480_Team_wiki:_2012T2_ElderLove_Midterm#Quality_of_Product]] | rect 639 273 822 287 [[ IS480_Team_wiki:_2012T2_ElderLove_Midterm#Quality_of_Product]] | ||
rect 637 296 751 316 [[ IS480_Team_wiki:_2012T2_ElderLove_Midterm#Reflection]] | rect 637 296 751 316 [[ IS480_Team_wiki:_2012T2_ElderLove_Midterm#Reflection]] | ||
+ | |||
+ | rect 928 184 993 211 [[ IS480_Team_wiki:_2012T2_ElderLove_Final]] | ||
+ | rect 934 222 1101 258 [[ IS480_Team_wiki:_2012T2_ElderLove_Final#Project_Progress_Summary]] | ||
+ | rect 926 273 1136 287 [[ IS480_Team_wiki:_2012T2_ElderLove_Final#Project_Management]] | ||
+ | rect 928 297 1114 314 [[ IS480_Team_wiki:_2012T2_ElderLove_Final#Quality_of_Product]] | ||
+ | rect 927 319 1037 336 [[ IS480_Team_wiki:_2012T2_ElderLove_Final#Reflection]] | ||
+ | |||
</imagemap> | </imagemap> | ||
Line 517: | Line 524: | ||
==<div style="background-color:#fdea71; padding:5px;width: 1150px; text-align: left;font-size: 150%;"><span style="color:#53291f"><font face="Cambria"> '''Reflection'''</font></span></div>== | ==<div style="background-color:#fdea71; padding:5px;width: 1150px; text-align: left;font-size: 150%;"><span style="color:#53291f"><font face="Cambria"> '''Reflection'''</font></span></div>== | ||
− | <div><font face="Cambria" size=" | + | <div><font face="Cambria" size="3%" color="#53291f"> |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Line 562: | Line 569: | ||
|} | |} | ||
</font></div> | </font></div> | ||
+ | |||
+ | [[IS480_Team_wiki:_2012T2_ElderLove_Midterm#Project Progress Summary|Back To Top]] |
Latest revision as of 16:21, 19 April 2013
Contents
Project Progress Summary
Description | Link |
---|---|
Powerpoint slides | Elderlove-Midterm_V5.pptx |
Mobiplore | http://elderlove.mobicaresocial.com/ |
Project Highlights
- Took 4 days to learn deployment
- Took 2 weeks to learn the framework (Django)
- Took 1 week to do simple modifications of the framework (Django)
- Major UI overhaul after considerations from supervisor, sponsor and UT session
Project Management
Project Scope
Completed | Incomplete | In-progress |
---|---|---|
Calendar | RSS | Patient Analysis |
Manage Event | Virtual Friend | Game |
Account | ||
Broadcast | ||
Feedback | ||
Manage Friend | ||
Newsfeed | ||
Profile Management | ||
Patient Management | ||
Notifications | ||
Appointment |
Project Status
Iteration | Task | Status | Confident Level (0-1) | Comment |
---|---|---|---|---|
1 | Sponsor confirmation | 100% | 1 | Mobipiazza and LARC |
2 | Project requirement gathering | 100% | 1 | |
3 | UI design paperprototyping | 100% | 1 | |
4 | Account setups (Log in/Log out) | 100% | 1 | Admin, doctor, patient, family member Fully deployed and tested 100% |
4 | Proposal submission | 100% | 1 | |
5 | Profile | 100% | 1 | Admin, doctor, patient, family member Fully deployed and tested 100% |
5 | Broadcast | 100% | 1 | Patient Fully deployed and tested 100% |
6 | UI design | 100% | 1 | |
7 | Broadcast | 100% | 1 | Fully deployed and tested 100% |
8 | Feedback, Manage friend, Newsfeed | 100% | 1 | Fully deployed and tested 100% |
9 | Patient management, Patient analysis | 100% | 1 | For that iteration we have done what we are supposed to. And also tested within our group. |
10 | Game | 50% | 1 | Fully deployed and tested 100% for the other two games except for puzzle game. |
11 | Calendar, Event | 100% | 1 | Fully deployed and tested 100% |
12 | Patient management | 100% | 1 | Fully deployed and tested 100% |
13 | Patient analysis | 45% | 0.85 | Research on relevant analysis for patients, Consultation with sponsor and client Currently the graphs for mood (overall mood and also mood Tired and Sick is being tracked)and events. We are still working on this now. |
14 | RSS, Virtual friend | 0% | 0.90 | We have a rough idea how we are going to do the thing already. Did some basic research on it. |
15 | UT 3, UT 4 | 0% | 0.85 | |
16 | Final presentation | 0% | 1 |
Project Schedule
- Revision #1
- Description : stretched across 3 iterations.
- Reason : cannot be completed due to front-end difficulties (CSS), as well as changing requirements with additional completed modules later on.
- Solution : shifted Sarah from a back-end role to a front-end role.
- Revision #2
- Description : shifted Game from iteration 9 to iteration 10.
- Reason : sponsor prioritized UI changes over completion of game module.
- Revision #3
- Description : delayed from iteration 12.
- Reason : supervisor requested a more professional layout change and there were a change of features due to change of business rules.
- Revision #4
- Description : additional UT 2 added.
- Reason : due to inability to gather real users before midterms, we conducted a UT with users between the age of 50-60 years old in order to get more accurate usability feedbacks.
- Revision #5
- Description : RSS is pushed back, Virtual Friend is an additional module.
- Reason : sponsor prioritized core functions over RSS, both RSS and Virtual Friend are good-to-have.
Links :
Project Metrics
- Spike in iteration 9
- Reason : we are 3 days late according to the schedule. The delay was due to the need to change our module structure to be relevant to our analysis. With a schedule index of 3, our action plan is to do immediate adjustment to our overall project schedule.
- Spike in iteration 13
- Reason : we were delayed by a change in our analysis for patients in order to make more sense of user data. Our front-end leader developer, who was away in China, had problems using the required data tables due to the firewall.
Links :
- Iteration 9 :
- Reason : in iteration 8, we developed feedback, manage friend and newsfeed, which are more intensive modules.
- Iteration 10 :
- Reason : there was major UI overhaul and there was preparation for UT 1, hence much more in-dept testing.
- Iteration 12 :
- Reason : we fixed bugs from UT 1 and developed calendar, appointment and game, which are also intensive modules.
Links :
Project Risks
S/N | Risk | Probability | Impact | Mitigation |
---|---|---|---|---|
1 | Not proficient in integrating third-party API. | High | High | Lead developers will undergo intensive learning to ensure good grasp of the APIs and thereafter, guide the group if needed. |
2 | Real patient data is highly confidential, hence client may not be able to release sufficient information for simulation purposes. | High | High | Ensure regular meetings with sponsor and client so as to constantly check validity of simulated data. Both parties to update each other and clarify any doubts or changes. |
3 | Lead front-end developer away for 2 weeks due to family matters. | High | Medium | Ensure regular online meetings with a personalized schedule for task completion. Constant communication with PM and lead back-end developer. |
Risk update #3:
- Constant communication is important in ensuring that project progress is not affected too greatly, if not, at all.
- Team member must take full responsibility of his/her assigned tasks.
Links :
Technical Complexity
S/N | Complexity | Description | Component |
---|---|---|---|
1 | Django framework | Django is a high-level python web framework that handles database query, modeling and back-end and front-end communication. The learning curve is steep as Django has a lot of features that are different from the normal python. | Entire project. |
2 | Bootstrap | This is the default CSS settings that come from the pinax framework. We needed to modify it to work with multiple browsers and resolutions and add in our own customizations. | *Patient functions *Doctor functions |
3 | Integration with Django application | django_notification - this is a notification module widely leveraged by other modules. django_friends - this is a friendship module that handles user relationships. Both these modules have no documentations and are difficult to understand. |
*Notification *Friends |
4 | Open-source Javascript libraries | These include jQuery, jQuery plug-ins; D3.js, etc. We have to make sure that they don't conflict with each other and customize the look to suit our application. | Entire project. |
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Storyboarding | |
Analysis | Use case | |
Design | System Architecture Diagram | |
ER diagram | ||
Testing | User Test |
Deployment
Stage | Specification |
---|---|
Development Environment | Application deployed on Site5. |
Database | Database deployed on Site5. |
Handover | Instructions : https://docs.google.com/document/d/1CbwSrmlJRL9kf_7pQ6u1TRJHe0oQQFS0rCl0USfUt4s/edit |
Testing
UT 1
Area | Description |
---|---|
Objective |
|
Details |
|
Method | Users are given several test cases to follow and the freedom to explore the application by themselves. |
Data Collection | Users will fill in a google doc form regarding the workability of test cases and comments regarding UI. |
Scope of Features Tested |
|
Results | UT 1 Results |
UT 2
Area | Description |
---|---|
Objective |
|
Details |
|
Method | Users are given several test cases to follow and the freedom to explore the application by themselves. |
Data Collection | Users will fill in a word doc regarding the workability of test cases and comments regarding UI. |
Scope of Features Tested |
|
Results | UT 2 Results |
Reflection
Name | Reflection |
---|---|
Wong Cai Ling |
|
Celestine Goh |
|
Cai Zejun |
|
Sarah Chu |
|
Liu Rongxuan |
|
Quan Ke |
|