1 / 34

T-76.4115 Implementation I Presentation

T-76.4115 Implementation I Presentation. braZil Payment Framework 12.12.2007 18:00 – 19:00. Project status (15 min) achieving the goals of the iteration project metrics Work results (20 min) presenting the iteration’s results documents Used work practices (6 min) Questions (6 min).

quade
Download Presentation

T-76.4115 Implementation I Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.4115 Implementation I Presentation braZil Payment Framework12.12.200718:00 – 19:00

  2. Project status (15min) achieving the goals of the iteration project metrics Work results (20 min) presenting the iteration’s results documents Used work practices (6 min) Questions (6 min) Presentation agenda

  3. Project Status • Introduction • Goals of first implementation phase • Some metrics

  4. Payment Framework for Mobirox Ltd. Simple payment interface Multiple content providers Hides payment method complexities Multiple payment methods SMS Online credit card Online bank Introduction to the project

  5. General goals Deliverables ready in time Project team motivated, workload equally divided Defined working practices are followed Product Transactions Online bank payments go through the framework Online credit card payments go through the framework SMS-payments go through the framework Interfaces System administrator can add basic system information to framework Browse through the transactions Alter the status of the transaction and mark transaction as cancelled Add, alter and remove basic information of the content providers Dataflow Framework recognizes invalid messages and saves them to error log Rights Restrict the content providers’ rights to use the framework. Goals  Done more than necessary

  6. All the deliverables delivered in time Internal review process -> followed as defined Customer approvement -> followed as defined Delivered -> in time Deliverables Iteration plan SE process description Project plan Requirements documentation Quality Assurance documentation and reports Test logs and test case lists Risk documentation and risk lists SEPA-documentation Technical Specification Demo product and documentation (at this point javadocs) Presentation slides Deliverables

  7. Task efforts (1/4)

  8. Task efforts (2/4)

  9. Task efforts (3/4)

  10. Task efforts (4/4)

  11. Task efforts (4/4)

  12. Other work

  13. Task efforts (4/4)

  14. Team efforts in Implementation 1

  15. Effort burn down graph

  16. Team effort plan for final Iteration

  17. Team effort plan for final Iteration

  18. Effort used - worktypes

  19. Quality Assurance Decent – Poor - Bad

  20. Metrics (1/2) • Defects • All the blocker and critical level bugs were related to administrator UI. • The blocker lever defect prevented adding new content providers to the system. Without this feature the system is useless. • The critical level defects consists a set of administrative functions performed in the administrator UI (for example: adding pricing model, basic information etc..) • The reason for this is that the UI was still under construction when the first test run was executed • There would have been a bigger amount of defects if all test cases would have been run • Most of the defects would probably have been related to incorrect exception handling

  21. Metrics (1/2) • LOC NCLOC is used to represent a non-commented source line of code COM is used to represent a commented line of code (currently we have no software to measure this)

  22. Evaluation of the quality goals

  23. Changes in the project • Challenges In SMS • MO / MT • Different interfaces (Sonera vs. Others) • Quality objectives were changed • Customer changed quality objectives in the end of iteration I • More implemented functionality over full test coverage  Testing effort is used to test case based testing • Other planned testing will be done during this project if there are enough resources or by customer after the project using the planned QA practises foun from the QA plan

  24. Risks in the project • Unusable system/product • Internal DL’s are not met • Selected tecniques are inadequate • CR process is not working as documented • Important information is not spread between the group and the customer High risk area Impact 2 1 3 5 4

  25. Results of Implementation I • Product • Demo ( demo –script) • Functionalities • User Interface • Tech-Spec • Architecture • QA plan • (implemented Usecases)

  26. DEMO

  27. FUNCTIONALITIES

  28. System overview Content providers Price models Payment methods Reports Logs UI Mobirox – Payment Framework Administration Luottokunta Current MAC key: BBIP87654321/AB12C MAC key valid until: 30.11.2007 24:00 New MAC key: BBIP12345678/AB12C Nordea Current MAC key: BBIP87654321/AB12C MAC key valid until: 30.11.2007 24:00 New MAC key: BBIP12345678/AB12C Sampo Current MAC key: BBIP87654321/AB12C MAC key valid until: 30.11.2007 24:00 New MAC key: BBIP12345678/AB12C OP Current MAC key: BBIP87654321/AB12C MAC key valid until: 30.11.2007 24:00 New MAC key: BBIP12345678/AB12C … Modify Modify Modify Modify

  29. Architecture

  30. Used work practices • Mitä käytetty, mitä tulee mitä poistuu

  31. What we have learned • We need some working system to test it throughly • Some tasks require more time • When software bases are ready, implementing features takes only a little of time.

  32. What we’ll do in next phase • Freeze the product functionalities at the end of january -> one month to test and fix bugs -> importance of quality

More Related