Banking Management System: Core Transaction 2 (Communication Management, Savings Tracking, Social Performance Monitoring, Consolidation)

Abstract

This study focuses in Core Transaction 2 of a banking management system. The problem that the core transaction have is about the savings tracking, the client does not have the system to track the savings of the depositors. Another problem are the monitoring of purpose of the bank client, and the consolidation of the bank account. Scrum is an agile project management methodology or framework used primarily for software development projects with the goal of delivering new software capability every 2-4 weeks. It is one of the approaches that influenced the Agile Manifesto, which articulates a set of values and principles to guide decisions on how to develop higher-quality software faster. The development team uses the Agile Scrum Methodology in constructing the system. In agile scrum the team created a sprint backlog that is needed to be perform during the sprint. Each sprint should be passed to the scrum master to be presented to the product owner for verification. The following are the recommended features of Banking Management Core Part 2. A Kiosk Machine in Savings Tracking module for checking the client transaction. View the performance of the client to know the status of their loan account in Social Performance Monitoring module. Easily to communicate using Communication Management module and enable to merge two accounts to become one in Consolidation. Banking Management System aims to develop appropriate system that is easy to use and create transaction much better. Through months of researching, the development team will able to solve identified problems such as lack of data security. The team addresses the identified problems by developing an EIS that has a user restriction to avoid unwanted user accessing the system. Developing a user friendly interface that can be easily navigate and use by the user.