IS480 Team wiki: 2015T1 Hexa Midterm Wiki

From IS480
Jump to navigation Jump to search

Cheng logo.png

Main Wiki Midterm Wiki Final Wiki

Project Progress Summary

View our deployed I-Wealth Web Application here
View our midterms presentation slides here !

Project Proposal
To understand more about our scope of, click here to read about our project description!


TEAMHEXA Project Management Overview Mid Term.png

Current Iteration 9: 21 Sept 2015 to 9 Oct 2015

  • Till date 2 Oct 2015, we have completed 90% of our project
  • Next iteration starts on 12 Oct 2015
  • Completed all core modules to be available for Web Beta Release
  • All core modules except Social Module to be available for Mobile Beta Release

Project Highlights:

  • Steep learning curve
  • More use-cases identified during development phase.
  • Team members too busy with other work
  • Attended Sponsor's seminar to market I-Wealth to public.
  • List of requirement changes
    • Change in data visualization libraries after acceptance for some functions. i.e Chart.js to d3.js to display stacked graphs for loan calculator comparisons.
    • Financial Education Module added
    • Retirement Planning Calculator added under Manage Personal Finance Module
  • Completed 3 UT tests with a total of 50 users.

Milestones Completed

  • Proposal Submission
  • User Test 1
  • User Test 2
  • User Test 3
  • Web Release 1
  • Mobile Release 1
  • Sponsor Seminar event

Milestones Remaining

  • Midterms
  • Web Release 2
  • Mobile Release 2
  • User Test 4
  • Final Web and Mobile Release
  • Final Presentation
  • Poster day

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Status:

2015T1 TEAMHEXA Project Status MIDTERMS.png

Project Schedule (Plan Vs Actual):

Summary of Planned vs Actual Schedule

2015T1 TEAMHEXA Schedule Planned vs Actual.png

Schedule Changes

2015T1 TEAMHEXA Schedule Changes Summary.png
  • Change 1: Admin Module (CRUD Users) shifted from Iteration 6 to Iteration 7 due to lack of time as we identified more use-cases than planned.
  • Change 2: Manage Personal Finance Module (CRUD Insurances) shifted from Iteration 7 to Iteration 8 as there were too many tasks in Iteration 7.
  • Change 3: Admin Module (Statistics of Community) and User Profile Module (Export PDF Report) shifted from Iteration 8 to Iteration 10. This was because of new additions of tasks in Iteration 8.
  • Change 4: User Test 3 was pushed earlier to Iteration 9 from Iteration 10. This is to test our application once more before Mid-terms presentation.
  • Change 5: Financial Health Module (Predictive Analysis of Credit Worthiness) shifted from Iteration 9 to Iteration 11. This is an Optional function. As new higher priority features were added, this optional task was pushed to a later iteration.

Scope Changes

2015T1 TEAMHEXA Midterm Scope.png

Project Metrics:

Schedule Metrics

Click here for details on how we calculate our schedule metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Schedule Metrics Iter8.png

Task Metrics

Click here for details on how we calculate our task metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Task Metrics Iter8.png

Bug Metrics

Click here for details on how we calculate our bug metrics and what are the respective plans of action to take when necessary.

2015T1 TEAMHEXA Bug Metrics MidTerm.png

Iteration 8

  • 3 high severity bugs – new users were not able to update database when they navigate from the homepage
  • Due to changes made to the database

Project Risks:

Click here to see how we identify risks, decide on the risk levels and action plans to take when necessary.

These are our top 3 risks:

Risk Type Risk Description Impact Likelihood Impact Category Mitigation Plan Status
Project Management Risk Most team members are doing internship and are only free to meet outside office hours with clients and supervisors. Delay in settling important decisions that require sponsor/supervisors' briefing. High High A PM to keep steady communication with our sponsor through emails so that the whole team can be in the loop. Also, could call the client as we realised that the client prefers calls however this would lead to difficulty in conveying full information to members as sometimes there might be too many information to recall in one phone conversation. Mitigated
Project Requirement Risk Sponsor adding new functionality on ad-hoc basis Project schedule will be affected and team has to brainstorm on solution to achieve end goal of Sponsor's request High Medium A Communicate and discuss with sponsor to negotiate scope, timeline and resources. Mitigated
Project Development Risk New use-cases that were only realized during development and not in planning phase. Change in development schedule. High Medium A Lead developer to discuss with PM immediately when situation arises. PM to re-schedule development and use buffer days if needed. Mitigated

Technical Complexity:

2015T1 TEAMHEXA TechComplexity 1.png
  • Another outstanding issue is angular-ui route feature is not compatible with the Chart.js

But other features from angular-ui are working fine with the app. 2015T1 TEAMHEXA TechComplexity 3.png

Open-sourced libraries lack documentation

  • Limited documentation available for some libraries
  • Difficult to find solutions online and thus, have to spend longer time to debug
  • Example:

2015T1 TEAMHEXA TechComplexity 2.png

  • When icons are shifted out of the toolbar i.e in an event of a narrow screen, the icons are immediately inactive and cannot be used. This issue will happen for smaller screen sizes e.g mobile phones.
  • Using a library that is well-documented and with clear known issues/bugs, it will be less complex to debug and integrate to our application. As compared to when a library has little documentation on how to customize the features, any issues will need to be resolved by the community since it is open source. In such instances where there is a lack of documentation and only a small number of developers utilize this library, we will have to look through the code of the library itself to find the cause of the issue. This is time consuming and we might not be able to find a solution if the codes within the library are complex and messy and might have to source for other libraries instead.

Quality of product

Intermediate Deliverables:

Stage Specification Links
Project Management Minutes Meeting Minutes for Internal, Sponsor, Supervisor Meetings
Metrics Schedule Metrics

Task Metrics
Bug Metrics

Requirements Story cards Project Motivation, Scenario Storyboard
Analysis Use case Use Case Diagram
Architecture Diagram Architecture Diagram
Prototype Designs Prototype Designs
Testing Heuristic Evaluation Tests HE1, HE2
User Tests UT1, UT2, UT3
Internal Testing Internal Test Documents


Click here to enter our Beta Web Application


User Test Date of User Test Objectives No of Participants Link
User Test 1
13/08/2014 to 14/08/2014
  • Gather feedback regarding user interface of developed functions for Web App
  • How easy is it for user to use
  • Which features is of importance to user
  • How good is the user experience
  • Detect usability issues based on user behavior
  • To use UT results to improve our web application
10 (Age range 18 - 35) User Test 1
User Test 2
17/09/15 3:00 pm - 20/09/15 11:59 pm
  • Gather feedback regarding user interface of developed functions for Web App
  • Detect usability issues based on user behavior
  • Find out if user interface is intuitive
  • Test success rate of users completing assigned tasks
  • Discover any usability issues
  • To use UT results to improve our web application for Beta Release
20 User Test 2
User Test 3
06/10/15 9:00 am - 08/10/15 01:00 am
  • Gather feedback regarding user interface of developed functions for both WEB and MOBILE App
  • Detect usability issues based on user behaviour
  • Find out if new users are able to easily learn and use the application
  • Test success rate of users completing assigned tasks
  • Find out which developed functions are the most important & provides the best user experience
  • To use UT results to improve our Web Application / Mobile Application
20 User Test 3


Team Reflection:

During the development of I-Wealth, the team has been exposed to more financial knowledge such as Financial Ratios and the impact of managing one's wealth.
Not only that, we learned about each other's working styles and learned to maximise our potential through understanding and adjusting accordingly to one other's styles. For example, Mon and Izzuddin likes to work in the morning, while Winnie and Zu Cheng prefers working at night. So, knowing that we know when to expect a task to be completed.
As a team, during development we utilized a framework called Ionic Framework for our mobile application that is not found in the Wiki Knowledge base. Hence, our team has contributed to the knowledge base for Ionic Framework.

Individual Reflection

2015T1 TEAMHEXA Midterm Learning Outcome.png