IS480 Team wiki: 2015T2 BeeSkilled Midterm
Revision as of 21:01, 10 April 2015 by Shujia.chan.2012 (talk | contribs) (Created page with "300px|center <br> <!--Header Start--> {|style="background-color:#ffff00; color:#F8F8F8; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="...")
Project Progress Summary
Midterm slides
Deployed Link: SMU tBank Automated Clearing House
Milestones Achieved | Explanation |
---|---|
7 Iterations | Completed 7 iterations with a average SM Score of 103 |
User Testing | 1 Heuristics Evaluation 1 User Testing |
Project Highlights:
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Completed Functions
Outstanding Functions
Project Schedule (Plan Vs Actual):
Planned Timeline
Actual Timeline
Iteration | Issues Faced | Solutions | Mitigation |
2 | 'Functionality:Create Gateway' took a longer time than expected to be stable and ready for use in the Payment Orchestration | After researching and talking to our Project Sponsor, it has been decided that we would spend extra time to re-construct the gateways and spend more time in testing to ensure that both Automated Clearing House (ACH) and Payments Service Hub (PSH) Gateways are tested and ready to be integrated with upcoming functionalities. | 'Functionality: Payment Orchestration' will be pushed back to subsequent iteration as both Gateways are the supporting foundation and should be thoroughly tested |
4 | Underestimated time required for 'Functionality: Payment Orchestration' | Continue with development of 'Functionality: Payment Orchestration' and push back other fuctionalities to subsequent iterations. Concurrently, Payment Orchestration was broke up into 2 phases for development and separated into 2 interations | Reschedule next iteration with added functionalities and milestones |
Project Metrics:
Project Risks:
Technical Complexity:
Quality of product
Intermediate Deliverables:
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Management | Minutes | Meeting Minutes |
Metrics | Bug metrics | |
Metrics | Schedule metrics | |
Requirements | Design Specifications | Project Scope |
Analysis | Use case | Use Case Diagram |
Architecture Diagram | Architecture Diagram | |
Testing | User test plan | User Test Results |
Testing:
2 User Test was conducted which covered overlapping functions.
The User Test was conducted in a Scenario-Based Environment where users will assume different roles in the Banking Environment.
Result of the test can be viewed here