HeaderSIS.jpg

IS480 Team wiki: 2015T1 Hexa Final Wiki

From IS480
Jump to navigation Jump to search

Cheng logo.png

HOME   ABOUT US   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION
Main Wiki Midterm Wiki Final Wiki

Project Progress Summary

View our deployed I-Wealth Web Application here
Click here to view our app on Play Store
View our final presentation slides here !

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

Overview

2015T1 TEAMHEXA Final Project Management Overview.png

Current Iteration 12: 23 Nov 2015 to 3 Dec 2015

  • Till date 22 Nov 2015, we have completed 100% of our project
  • Completed all modules to be available for Web Release and Mobile 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 4 UT tests with a total of 70 users.

Milestones Completed

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

Milestones Remaining

  • 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 FINALS.png

Project Schedule (Plan Vs Actual):

Summary of Planned vs Actual Schedule

2015T1 TEAMHEXA FINALS Expected Vs Actual Schedule.png


Schedule Changes

Acceptance Schedule

2015T1 TEAMHEXA Acceptance Timeline.png


Midterms Schedule

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.

Finals Schedule

2015T1 TEAMHEXA Final Schedule.png
  • Change 1: Added new tasks
  • Change 2: Removed optional functions and modules tasks

Scope Changes

Acceptance Scope

2015T1 TEAMHEXA FINALS Acceptance Scope.png


Midterms Scope

2015T1 TEAMHEXA FINALS Midterms Scope.png


Finals Scope

2015T1 TEAMHEXA Finals 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 FINALS Schedule Metrics.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 FINALS Task Metrics.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 FINALS Bug Metrics.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 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 Mobile Development encounters unforeseeable issues due to Ionic Framework even though both Web and Mobile utilizes AngularJS. Delay in development progress Medium High A Mobile Developer to communicate with Web Developers to highlight issues that are appearing on Mobile and not Web dev to prevent same issue from arising again. Mitigated
Project Overall Risk Members falling sick at the same time Unable to complete tasks in time Low Medium C PM to re-assign tasks if members are completely incapable of completing tasks or activate buffer days. Mitigated

Technical Complexity:

Linking Data Fields Across Modules

  • Different modules have different functions but all functions manipulate the same data field.
2015T1 TEAMHEXA Linking Data Fields.png


2015T1 TEAMHEXA Linking Data Fields Example.png


2015T1 TEAMHEXA Linking Data Fields Example2.png


  • This leads to the next issue of having many use cases that we have to consider for.
2015T1 TEAMHEXA Many Use Cases.png


2015T1 TEAMHEXA Many Use Cases2.png

Converting Web codes to Mobile Framework

2015T1 TEAMHEXA Mobile to Web2.png
  • Due to the large number of functionalities, we used Ionic to develop a Mobile application
  • Ionic is in javascript but it calls the Web’s back-end to process functions and even though it’s the same language, we need to bridge the different frameworks together (AngularJS vs IonicJS)
2015T1 TEAMHEXA Mobile to Web.png

Tracking of friendships and requests in database

  • In the social module, users are allowed to add friends, accept friend requests and be friends with other users.
  • Multiple users' records and different data tables
2015T1 TEAMHEXA Sending a friend request.png
  • Below shows how data tables are updated for a friend request to be successfully accepted.
2015T1 TEAMHEXA Sending a friend request2.png

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, UT4
Internal Testing Internal Test Documents
Project Closure Documents Project Closure Agreement Project Closure Agreement Document
User Guide Manual User Manual Guide

Deployment:

Click here to enter our Beta Web Application
Click here to view our app on Play Store

Testing:

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
User Test 4
06/10/15 9:00 am - 08/10/15 01:00 am
  • Gather feedback regarding user interface of developed functions
  • Detect usability issues based on user behavior
  • 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
22 (web) and 10 (mobile) User Test 4

Reflection

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 Finals Learning Outcome.png