Enjoy Upto 30% off on all Your Assignments ORDER NOW
+61480015851 whatsapp white icon +61480015851 info@myassignmentservices.com

31253: Database Programming - Financial Settlement System - Report Writing Assessment Answer

Download Solution Order New Solution

Highlights

Internal Code: D_BJ_DFBE_CJA Code: 31253

Database Programming Report Writing Assessment Answer

Assignment Task - 31253 INSTRUCTIONS
  1. This assignment is worth 50% of your final grade and requires a commitment of about 35 hours from each student.
  1. Your task is to produce a working solution to the problem given in this specification. The solution will be written in the PL*Sql language and will run in your schema in the LOZ database. Please be aware that you must produce code that compiles and runs.
  2. You will be producing a report which will be a Terminal Usage report. I would like you to provide me with a design document for that report. You should include an ER diagram showing where the source of the report data is.
  1. You are expected to submit a professional presentation for your design document, prepared using a suitable Word Processor. A handwritten submission is not acceptable and will not be marked. Your submission should include your ORACLE userid DO NOT INCLUDE YOUR PASSWORD
  1. A hard copy of your code should not be included in the submission, only the design document for the report. The code will be marked in the database.
  1. I will be looking at and running your code in the Database. Once the assignment is handed in you must NOT recompile or modify any component of your system. I will be checking the object modification dates and if any object has been modified after the due date the assignment will not be marked.
  1. There may be errors and ambiguities in the assignment specification. If so, corrections/clarifications will be posted to the subject web sites. You are expected to check and incorporate these changes into your submission. The specification will be frozen one week before the assignment is due.
  1. I will be utilizing UTSOnline extensively to answer questions on the specification and to provide details of the existing data. I will assume that you will be checking the site regularly to make yourself aware of the latest developments.
  1. Please take note of the due date, and work to that date, as extensions will be granted only under extenuating circumstances. Late submissions are to be negotiated with the lecturer. Students should be aware that a penalty of up to 50% may be applied for late submissions. Assignments submitted later than two weeks will not be accepted
  2. Students are advised to make themselves familiar with the Academic Misconduct statement detailed in the Subject Outline and conduct themselves according to the expectations of the University
  3. I expect to return the marked Assignments 14 days after the submission date.
The Smartcard Financial Settlement System - 31253 Introduction - 31253 For the Assignment for Database Programming and Administration you are required to write a Financial Settlement System (FSS) for a Smartcard Transaction Centre. The Deliverables for the Assignment are structured in a way to enable you to achieve a mark that is related to the amount of work that you will contribute and the level of knowledge that you have attained. The detailed marking structure can be found at the rear of the document. Overview - 31253  For some time now there has been a trial deployment of a Smartcard System in various locations throughout the country. A number of different types of Smartcard terminals have been deployed at selected sites. The types of terminals include Parking Meters, Payphones, various Vending machines and ticketing machines at selected railway stations. A number of Smartcard enabled terminals have also been placed in selected retail outlets like Newsagents and University canteens enabling the holders of the Smart cards to pay for their purchases using these cards. The term electronic cash is often used when talking about Smartcard transactions; however, the electronic cash needs to be converted to real cash so that the merchants, accepting the cards as payment, can be reimbursed. During the trial phase, the merchants were reimbursed manually, once a week. The settlement amount calculations have been done by the staff in our IT department and the merchants were sent a cheque for the amount of the settlement. During the initial trial phase, the merchants were not charged a fee on the Smartcard transactions. The Smartcard System is moving into the next phase of deployment. The number of merchants will be increased and there is a requirement to automate the Settlement process. The payment to the Merchants will be done via direct credit into their nominated bank accounts and is to be done daily. Each month the merchants will be charged a fee for the use of the Smartcard. The fee to be charged will be a percentage of the total transactions for the month. The actual amount is yet to be negotiated and it will be uniform for every transaction. The fee collection will be done via direct debit from the merchant bank account. The merchant will also be sent a statement showing the money banked and the fees charged for the month. The details of the application follow. Daily Settlement Deskbank File - 31253 The FSS system will be required to run daily and at the conclusion of the run, will produce a banking file that will be known as a Deskbank file. The Deskbank file will be sent to the designated banking organization electronically, most likely using a secure FTP channel. The Deskbank file, when running in the banking system will contain information necessary to credit the merchant's bank account with the amount collected by the Smartcard transactions. The total of the deposits into the merchants accounts is to be offset by a debit from our working bank account. The total of the deposits and the debits is to reconcile to zero. This file is intended to be read by the bank's systems. A sample Deskbank file and the file specification can be found in the Appendix ****See the Note on Minimum Settlement under System Constraints Daily Settlement Report - 31253 In addition to the Deskbank file, your system is to produce a daily reconciliation report. The report will be used by the business unit and will show the banking details generated by the Daily Settlement. The report will be created automatically when the desk bank file is produced, however your system should be flexible enough to allow the manual creation for a given settlement date. This file is intended to be read by humans. A sample report is attached in the Appendix. Terminal Usage Report - 31253 We need to keep track of the busiest terminals and the amount of traffic they generate. A report is required for the business units. Each time the report is run it should produce Terminal Usage data for the current month, up to and including the current date. The report specifications is provided. RUN Table The FSS system will run each day and should settle all those transactions that have not yet been settled. You are asked to create and maintain a RUN table which should keep track of the run dates and the status of each run. You must use the run table to ensure that only one instance of the program is to run at any time. If the program is already running it cannot run again. If the program is restarted while another session is running then a log message is to be written into the logging table and the second program instance should terminate gracefully. In order to minimize the banking costs we want to run only one settlement process per day. Use the run table to ensure that only one settlement is run per day. If the settlement was already run on any day then the program should log a message to the log table and terminate gracefully. If the program fails during the run it should log the failure reason to the logging table, update the run table with a status of FAIL. Also the fail reason should be written to the Run table so that production support know what needs to be repaired. The run end column should be populated. In such a situation, where the settlement failed, your program can be rerun on the same day. The assumption is that production support will have fixed the problem with the data so they may wish to run the settlement again. You MUST BE VERY CAREFULL however, that your program does not duplicate the merchants settlements. This could send us bankrupt. The production support personnel will use the run table to assist them in monitoring and maintaining the system in the event of failures. One record should be created in this table for each run of the program. Also, you are asked to maintain a log of your program runs which will enable the production support team to monitor the progress of your run. The log table will contain a timestamp and a periodic entry to mark the progress of your system. Note: The logging is to be done by using the COMMON.log procedure which will be made available to you. I will show you which table the COMMON.log procedure utilizes for logging, You are of course free and encouraged to develop your own logging process.
This 31253: Database Programming Assessment has been solved by our IT experts at My Uni Paper. Our Assignment Writing Experts are efficient to provide a fresh solution to this question. We are serving more than 10000+ Students in Australia, UK & US by helping them to score HD in their academics. Our Experts are well trained to follow all marking rubrics & referencing style.

Get It Done! Today

Country
Applicable Time Zone is AEST [Sydney, NSW] (GMT+11)
+

Every Assignment. Every Solution. Instantly. Deadline Ahead? Grab Your Sample Now.

Find My Solution

© Copyright 2026 My Uni Papers – Student Hustle Made Hassle Free. All rights reserved.