1 / 19

ePayments

ePayments. The A-Team. Nathanaël Müller, Michiel Hauwaert, Arnold Meyers, Teemu Airaksinen, Petja Hartikainen. Contents. Context of the workshop Team Overview Task description Visual model of the payment process Test statistics Failed transactions Problems faced and solutions

tuan
Download Presentation

ePayments

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. ePayments The A-Team Nathanaël Müller, Michiel Hauwaert, Arnold Meyers, Teemu Airaksinen, Petja Hartikainen

  2. Contents • Context of the workshop • Team Overview • Task description • Visual model of the payment process • Test statistics • Failed transactions • Problems faced and solutions • Recommendations • Reflection

  3. Context of the workshop • In this workshop our challenge was to design, develop and implement a flexible Payment Processor. • This workshop was a simulation for simulating electronic payment systems. • The aim is to experience the backend processing of payment orders.

  4. Dividing tasks Visual model, SQL code and data handling were done by Belgian students Data model, BPM, team documentation and presentation done by Finnish students Team overview Team members • Nathanaël Müller (BE) • Michiel Hauwaert (BE) • Arnold Meyers (BE) • Teemu Airaksinen (FI) • Petja Hartikainen (FI) Team Tasks • SQL coding (the hard work) • Visual model • Data model • Business process models • Team documentation • Presentation

  5. Task description • Teams were supposed to run two test runs • We managed one test run • Create a team documentation and use that to produce this presentation • The electronic payment system is SQL based and the development tool used was Oracle Application Express • Basis for the SQL were to be downloaded and the actual functionality to be added by students

  6. Visual model of the payment process • Visual model • 3 ways to view the business process • The optimal situation with working connections • = “Story of a payment” • The 5000 randomly generated transactions transferred via XML file • Receiving and processing received transaction info • Data model

  7. Test statistics • Internal TransactionsA-How many transaction records did your bank process internally? 284B-For what total amount? 947225 • External TransactionsA-How many transaction records did you send to the clearing house? 945B-For what amount? 2993113C-How many transaction records were sent to every member bank?  FIBA 322, NOBA 314, BEBA 309D-For what amount? FIBA 1061151, NOBA 920164, BEBA 1011798 • SucessA-For how many transactions did you get a successful reply? %70B-How many transactions were missing in the replies? %30C-What is the percentage of internal transactions that succeeded? %100D-What is the percentage of external transactions that succeeded?

  8. BalanceA-What was the start balance of every account before the testrun? 5000B-What is the end balance of every account after the testrun?C-Who is your lucky customer? AccountID 1035D-Who is the customer that is the most unfortunate? AccountID 1041E-Who has a new balance below zero? 10 • TimingA-How much time was needed on average to send an external transaction via the clearing house to the destination bank? (Check the time stamps of the sending and the destination bank) 0.68 + 0.51 + 0.53 + 0.12 + 0.11 = 1.95 • Current BalanceA-Check the current balance of every account. Which bank accounts go in the red? 10 • Prove that your team has been able to complete a full PingFIN operation.

  9. Failed transactions • Transactions generated by the generate_random_payments procedure (SB_BANK_ID that isn’t our bank)

  10. Problems faced and solutions • Business process model had to be remade multiple times • Reason: lack of knowledge + misunderstandings • Data model • Difficulties finding right tool to create it • With MS Access 2010 it was simple enough • SQL code • One of the pre-made pieces of script was broken • It tried to fetch data from an empty table and teacher had to fix it • Relationships between tables were hard to understand • Some of the data was duplicated • We had one script that had to be divided into two separate scripts

  11. Recommendations • Better instructions • Table of contents • Headings are confusing (no numbering, style, etc) • Needs work with structure • Working SQL code • Finnish students couldn’t help with SQL at all • We Finns can kinda read and kinda understand the code but yeah…

  12. Reflection • Overall experience was fun • Learned bunch of stuff • The weather was good • Teachers are skilled and helpful • Manual was really confusing and hard to understand • Fun people

  13. Thankyou for listening! AnyQs?

More Related