Difference between revisions of "IS480 Team wiki: 2013T1 Altitude/Midterm"
(7 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
|- | |- | ||
!style="text-align:center" |[[Image:Altitude_logo_black.jpg|600px]] | !style="text-align:center" |[[Image:Altitude_logo_black.jpg|600px]] | ||
+ | |} | ||
+ | {| <!-- table start, define style here --> | style="background-color:#000;" width="100%" cellspacing="0px" cellpadding="12px" border="0" | ||
+ | |- | ||
+ | ! style="background: #000; color: #FFF; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #f0ab00; font-face:Century Gothic; color:#FFFFFF"|<span style="font-size:2.5em; padding-left:24px">O</span>verview | ||
+ | ! colspan = 2 style="background: #000; color: #FFF; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #f0ab00; font-face:Century Gothic; color:#FFFFFF"|<span style="font-size:2.5em">P</span>roject Management | ||
+ | ! colspan=3 style="background: #000; color: #FFF; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #f0ab00;font-face:Century Gothic; color:#FFFFFF"|<span style="font-size:2.5em">D</span>ocumentation | ||
+ | |- | ||
+ | ! style="color: #FFF; border-bottom:solid 4px #f0ab00; text-align: left; font-size:1.2em; padding-left: 48px; line-height:0.8em;"| | ||
+ | * [[IS480_Team_wiki:_2013T1_Altitude | <span style="color:#FFF">Updates</span>]] | ||
+ | * [[Altitude Project Description | <span style="COLOR:#FFF">Project Description</span>]] | ||
+ | * [[Altitude Project Stakeholders | <span style="COLOR:#FFF">Stakeholders</span>]] | ||
+ | ! style="color: #FFF; border-bottom:solid 4px #f0ab00; text-align: center; font-size:1.2em; padding-left: 32px;"| | ||
+ | [[Altitude Project Schedule | <span style="COLOR:#FFF; font-size:1.85em;">Schedule<br/>—<br/>Scope</span>]] | ||
+ | ! style="co85or: #FFF; border-bottom:solid 4px #f0ab00; text-align: left; font-size:1.2em; line-height:0.8em;"| | ||
+ | * [[Altitude Project Metrics | <span style="COLOR:#FFF">Metrics</span>]] | ||
+ | * [[Altitude Project Risk Management | <span style="COLOR:#FFF">Risk Management</span>]] | ||
+ | * [[Altitude Project Management Framework | <span style="COLOR:#FFF">Framework</span>]] | ||
+ | ! style="color: #FFF; border-bottom:solid 4px #f0ab00; text-align: left; font-size:1.2em; padding-left: 24px; line-height:0.8em;"| | ||
+ | *[[Altitude Project Meeting Minutes | <span style="COLOR:#FFF">Meeting Minutes</span>]] | ||
+ | *[[Altitude Project Resources | <span style="COLOR:#FFF">Resources</span>]] | ||
+ | *[[Altitude Project Diagrams | <span style="COLOR:#FFF">Diagrams</span>]] | ||
+ | ! style="color: #FFF; border-bottom:solid 4px #f0ab00; text-align: left; font-size:1.2em; padding-left: 24px; line-height:0.8em;"| | ||
+ | *[[Altitude User Testing | <span style="COLOR:#FFF">User Testing</span>]] | ||
+ | *[[Altitude User Interfaces | <span style="COLOR:#FFF">UIs</span>]] | ||
+ | *[[Altitude Learning Outcomes | <span style="COLOR:#FFF">Reflections</span>]] | ||
|} | |} | ||
<big><p style="text-align: left; font-size: 150%;"><center> | <big><p style="text-align: left; font-size: 150%;"><center> | ||
− | [[IS480_Team_wiki:_2013T1_Altitude|<font color="#000000" face=""><ins>''' MAIN WIKI'''</ins></font>]] [[IS480_Team_wiki:_2013T1_Altitude|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]] </center></p></big><br> | + | [[IS480_Team_wiki:_2013T1_Altitude|<font color="#000000" face=""><ins>''' MAIN WIKI'''</ins></font>]] [[IS480_Team_wiki:_2013T1_Altitude/Final|<font color="#000000" face=""><ins>''' FINAL WIKI'''</ins></font>]] </center></p></big><br> |
[[Image:coverphoto.jpg|650px|right]] | [[Image:coverphoto.jpg|650px|right]] | ||
Line 24: | Line 49: | ||
|1 | |1 | ||
|align="center"| Presentation Slide | |align="center"| Presentation Slide | ||
− | |align="center"| [ | + | |align="center"| [https://www.dropbox.com/s/yvhq96u8e0cyh90/Altitude_Mid_Presentation%20%5B04102013%5D.pdf# Click here] |
|- | |- | ||
|} | |} | ||
Line 402: | Line 427: | ||
|scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | |scope="row" width="1200" style="text-align: left; background: #F5F5F5"| | ||
− | Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the | + | Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the [https://wiki.smu.edu.sg/is480/Altitude_Project_Risk_Management Risk Management Table] |
+ | |||
{| class="wikitable" style="text-align: center; height:80px" | {| class="wikitable" style="text-align: center; height:80px" | ||
Line 505: | Line 531: | ||
|} | |} | ||
− | |||
− | |||
==== Change Request Management ==== | ==== Change Request Management ==== |
Latest revision as of 21:37, 5 November 2013
Overview | Project Management | Documentation | |||
---|---|---|---|---|---|
Presentation Materials
S/N | Description | Link |
---|---|---|
1 | Presentation Slide | Click here |
Overview
Current Project Sprint : 7The following features will be presented for our mid term presentation:
Features |
---|
|
Project Status
Altitude has completed 6 sprints and there are 5 more sprints to work on. We are in sprint 7 which started on 16 September and will end on 4th October.
Project Timeline
Project Highlights
EVENT | HIGHLIGHT / ISSUE | MITIGATION/CONTINGENCY PLAN |
---|---|---|
Sprint 2 | Implementation of Take in requirements for proposal took longer than expected
The team needs more time to explore on the few unfamiliar technologies therefore the implementation was not able to complete on time |
PM have to reschedule the sprint and every member have to work hard and completed all the uncompleted tasks by the end of sprint |
Sprint 3 | Delay in previous sprint
Due to the sprint delay in sprint 2, the team had a shorter period of time to finish match options. |
After reviewing with the client, we decided to reschedule generate proposal, review and edit proposal to be implemented after acceptance. PM also have to review all the future sprint schedule for the team |
Sprint 5 | No prior knowledge on how ontology should be designed
The team spend long hours exploring on how ontology should be designed. After a session with our end users, we realized that we took a wrong approach to design our ontology. |
We decided to consult prof Lim Ee Peng for better understanding on how ontology can be created. The team put on more man hours to make sure that the uncompleted tasks can finished on time.
|
Technical Complexity
The technical complexities of our tools employed are in the following descending order:
COMPLEXITY | DESCRIPTION |
---|---|
SAPUI5 |
|
Ontologies Framework |
|
Project Status
Features | Status | Confidence Level (0-1) | Member In-Charge |
---|---|---|---|
Login | 100% developed and deployed | 1 | Justin |
Take in Requirements from RFP | 100% developed and deployed | 1 | Kenneth |
Download PDF | 100% developed and deployed | 1 | Si min |
Design ontology | 100% developed and deployed | 1 | Kenneth |
Enhance take in RFQ inputs | 100% developed and deployed | 1 | Yao zong |
Generate Proposal | 100% developed and deployed | 1 | Max |
Review and Edit Proposal | 100% developed and deployed | 1 | Max |
Recommended Options | 100% developed and deployed | 1 | Yao zong |
Modify Recommended Options | 100% developed and deployed | 1 | Max and Si min |
Dashboard | Not Started | 0 | Max and Si min |
Adjust Pricing | Not Started | 0 | Kenneth and Yao zong |
Enhance Edit Proposal | Not Started | 0 | Justin |
State Save | Not Started | 0 | Max |
Approve Proposal | Not Started | 0 | Kenneth |
Furnish Proposal | Not Started | 0 | Yao Zong |
Delete Proposal | Not Started | 0 | Si min |
Project Scope (Planned Vs Mid Term)
Project Scope
|
---|
Current Scope
Schedule (Planned vs Actual till Mid Term)
Features changes
Project Metrics
Schedule Metric
The diagram below shows the burn-down charts of the 7 sprints we have completed thus far: Key Issues
Release Burn-down Chart
|
Number | Description | Links |
---|---|---|
1 | Schedule Metric Calculation | Schedule Metric Calculation Link |
2 | Schedule Metric Documentation | Schedule Metric Documentation for Sprint Number: |
Bug Metric
Bug Log ChartFor sprint 6, the team have to do more vigorous testing for UT 1 preparation. However, due to the lack of time, 4 bugs was carried over from sprint 6 to 7. The team faced the most number of bugs in sprint 7 due to the user feedback on UT1, the team spend extra man-hours to solve the difficult bugs and ensure that all usability features can function properly before mid term presentation.
Bug Metric Severity Chart
|
Risk Management
Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the Risk Management Table
|
Change Request Management
|
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | User Interface Mockups and Videos | |
Analysis | Use case | |
Design | Deployment Diagram | |
System Architecture Diagram |
| |
ER diagram | ||
Testing |
Deployment
Area | Details |
---|---|
Development Environment |
|
Database |
|
Web Links |
User Testing 1
Changes made
Requirements Gathering
During Acceptance | Latest version |
---|---|
Display Recommended Options
During Acceptance | Latest version |
---|---|
Review and Edit Proposal
During Acceptance | Latest version |
---|---|
Team Reflection
|