HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T1 Hexa Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 194: Line 194:
 
|align="center"| Stage  
 
|align="center"| Stage  
 
|align="center"| Specification
 
|align="center"| Specification
|align="center"| Modules
+
|align="center"| Links
 
|-
 
|-
  
 
|rowspan="2"| Project Management
 
|rowspan="2"| Project Management
 
|| Minutes
 
|| Minutes
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
+
|| [[IS480 Team wiki: 2015T1 Hexa Meeting Minutes|Meeting Minutes for Internal, Sponsor, Supervisor Meetings]]
 
|-
 
|-
  
 
|| Metrics
 
|| Metrics
|| Bug metrics
+
|| [[IS480 Team wiki: 2015T1 Hexa Schedule Metrics|Schedule Metrics]]<br>
 +
[[IS480 Team wiki: 2015T1 Hexa Task Metrics|Task Metrics]]<br>
 +
[[IS480 Team wiki: 2015T1 Hexa Bug Metrics|Bug Metrics]]<br>
 
|-
 
|-
  
 
|| Requirements
 
|| Requirements
 
|| Story cards
 
|| Story cards
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
+
|| [[IS480 Team wiki: 2015T1 Hexa Project Overview#motivation|Project Motivation]], [[IS480 Team wiki: 2015T1 Hexa Design Documents#Scenarios|Scenario Storyboard]]
 
|-
 
|-
  
|rowspan="4"| Analysis
+
|rowspan="3"| Analysis
 
|| Use case
 
|| Use case
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
+
|| [[IS480 Team wiki: 2015T1 Hexa Documentation#Use Case|Use Case Diagram]]
 
|-
 
|-
  
|| System Sequence Diagram
+
|| Architecture Diagram
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
+
|| [[IS480 Team wiki: 2015T1 Hexa Documentation#Architectural Diagram|Architecture Diagram]]
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
+
|| Prototype Designs
|| Here
+
|| [[IS480 Team wiki: 2015T1 Hexa Design Documents#Prototype|Prototype Designs]]
 
|-
 
|-
  
|| Screen Shots
+
|rowspan="3"| Testing
|| CRUD Customer, Trend Analysis
+
|| Heuristic Evaluation Tests
 +
|| [[Media:2015T1 TEAMHEXA Heuristics Evaluation 1.docx|HE1]], [[Media:2015T1 TEAMHEXA Heuristics Evaluation 2 v2.docx|HE2]]
 
|-
 
|-
  
|rowspan="2"| Design
+
|| User Tests
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
+
|| [[IS480 Team wiki: 2015T1 Team Hexa User Test 1|UT1]], [[IS480 Team wiki: 2015T1 Team Hexa User Test 2|UT2]], [[IS480 Team wiki: 2015T1 Team Hexa User Test 3|UT3]]
|| 1, 2, 3
 
 
|-
 
|-
  
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
+
|| Internal Testing
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
+
|| [[IS480 Team wiki: 2015T1 Hexa Test Documents|Internal Test Documents]]
|-
 
 
 
 
 
|| Testing
 
|| User test plan
 
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
 
 
|}
 
|}
 
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
 
  
 
===Deployment:===
 
===Deployment:===

Revision as of 19:53, 2 October 2015

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
View our midterms presentation slides here!

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

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
  • 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
  • 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:
  • Change 2:
  • Change 3:
  • Change 4:
  • Change 5:

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 5

  • Only 1 high severity bug for Milestones Module
  • The rest were 10 low severity bugs that was fixed during buffer period

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:

Backend has many different dependencies


Social Module API

  • Many different use-cases to consider.
  • Complexity occurs when different permutations occurs for each case.


Linking data fields from across different Modules

  • Complexity occurs when user wants to manipulate his data. System has to be robust to be able to handle different scenarios. E.g User going back 5 months ago to edit Loan Balance under his Manage Debt function. The new loan balance has to be carried forward to the months following after.

Quality of product

Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.

Intermediate Deliverables:

There should be some evidence of work in progress.

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

Deployment:

In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.

Testing:

Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.

Reflection

In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.

Team Reflection:

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Individual Reflection:

You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.