Difference between revisions of "IS480 Team wiki:"

From IS480
Jump to navigation Jump to search
m (Updated Link to User Test and Results)
m (Remove Sub Tabs from reflection)
Line 169: Line 169:
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 | knowledge base]] and linked here.
===Benjamin Gan Reflection:===
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.

Revision as of 01:37, 25 February 2015














Project Progress Summary

MidTerm Presentation Slides File:Midterm BeeSkilled.pptx
Website 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

Project Timeline Initial.png

Actual Timeline

Project Timeline Latest.png

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:

ScheduleMetrics6.png SM6.png BugMetrics6.png BM6.png

Project Risks:

Mitigated Risk.png UpcomingRisk.png

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


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