designing the initial proposal report

SOLUTION AT Australian Expert Writers

The project is based on designing the initial proposal report for developing an online banking system. The system is planned based on simple model–view–controller architecture. The system designed will access all the data from centralized database. PHP scripts along with SQL queries will be used as a middleware and the user interfaces will use HTML5 and CSS to style the website if necessary. The report enlights on various key deliverables like tangible and intangible deliverables. Moreover, the report consists of various functional and non-functional requirements along with extra three functional requirements required for the system. Similarly, the project will use RAD (Rapid Application Development) as the developmental approach.
Executive Summary 2
Introduction 4
Aim 4
Key Deliverables 4
Functional and Non-Functional Requirements 4
Development Approach 5
Conclusion 6
References 7
Emergence of internet has brought the drastic change in every sector including the banking sector. Online banking has helped individual to focus their time on more productive works rather than queuing up in banks. Moreover, this has helped banking sectors to provide quality services to their customers at lower cost and at any time.
Aim
This project focuses on developing an online banking that can be accessed by everyone in the organization and outsider with proper login. It is planned with simple Model View Controller (MVC) architecture. Storage of the database will be centralized and the user interface will be designed using HTML5 and CSS while the middleware will be developed using PHP scripts and SQL queries. The report will also focus on functional and non-functional requirements as well.
Key deliverables are the main functionality that we develop in our online banking system. Our online banking system has many deliverables but some of the important ones have been discussed below. The key deliverables of our online banking system can be categorized of two types. Tangible deliverables and intangible deliverables. It focuses on both goods and services which will be delivered to the customer as an outcome of the project.
In case of our online banking system, network infrastructure and physical server (mobile banking server, application server, ATM server, etc) as well as improved customer service, ease-of-use and adaptability will be the intangible deliverables. In the other hand, the products that we will be selling in our system will be the tangible deliverables. For example, we will be providing facility to our customers that will allow them to e-shopping. In same system we will be doing banking services and e-commerce as well. A digital wallet is also a deliverable of our project which will allow our customers for transition of their balance from e-banking to e-commerce. They will be allowed to store money in their digital wallet from our banking system (other banks as well) which will allow them for shopping within the same system.
Also, our banking system will have a facility which can be used to pay bills of daily use (such as, rent, phone bill, gas bill, etc). E-payment is also a key deliverable of our system. Atm accessibility, e-pay, digital wallet, e-commerce, mobile banking, etc are the deliverables of our online banking system.
Furthermore, generation of bank statement, work breakdown structure, project scope statement and the governance plan for the banking system are the crucial deliverables of our project.
The project focuses on developing Online banking for the users/customers. While developing, functional, non-functional and many other requirements are to be considered.
Functional Requirements:
Functional requirement normally describes the behaviour of the system under specific conditions. Following are the functional requirements of the system as mentioned in the assessment brief along with three extra functional requirements.
Valid User ID and password is provided to the user to login to the system.
System shows the present balance of the user’s account.
Customer can withdraw and deposit money i.e. transaction from his/her account.
Customer can transfer funds to other accounts using the system.
Customer can have a faster balance enquiry.
System keeps track of each and every transaction to prepare a balance statement.
Authentication of Username and password to login into the system.
System keeps the record of old transaction along with updated balance when user logout the system.
Administrator has the authority to view, add, edit or remove any customer from the system.
Three extra functional requirements of the system are explained below in brief:
Investment Account: System will provide platform to view customer’s finance like viewing portfolio or investment by linking their saving accounts, term deposits, property or share investments to the system.
Cheque services: Customer can enquire about cheque status whether its paid, unpaid or bounced. In addition to that, system allows customer to request a cheque book online.
Utility Services: It allows customer to pay their bills (electricity, water and gas). Moreover, it allows customer to schedule their payment date.
Non-functional Requirements: It involves all the requirements that are not related to the specific functions delivered by the system (Baltzan et. al. 2014). Following are the non-functional requirements of the system:
Performance requirements: It includes the activities like allowing customer access the system 24 hours a day with backups and minimum downtime. It also focuses on reducing the overall costs per transactions.
Safety requirements: The system and all the data will have backup and recovery in place periodically. However, the frequency depends on various factors.
Security requirements: It includes the activities like protection of user ID and password (like use of special characters, upper case, numbers for a password), auto timeout when user is not using the system for 4-5 minutes and the system automatically denies the access if 5 continuous attempts are made.
A website with great usability, frictionless UI is a vital to create a positive impact on the user. Regardless of any devices, our system will be accessible anywhere in any device that supports internet and will be easy to use. System will be using graphical icons and notations so that customers can interact with our online banking effectively.  A model–view–controller is being used in this project allowing flexible structures in which the interface is independent from and indirectly linked to application functions, so the GUI can be customized easily( Mostak 2019). Proper GUI will help us in running the system effectively considering the functional and non-functional needs of the system.
Rapid Application Development (RAD) approach will be used for developing the system. It is very structured that focuses on quickly building a working model of the software, getting feedback from users and using feedback to update the working model (Baltzan et. al. 2014). It is an agile project management strategy popular in software development. It has four phases: –
Requirements Planning
In this phase we will have proper plan for our project. It includes all the functional and non-functional needs of the system. The proper project plan helps us to get our desired banking system. First of all, we will be researching the current problem then we will be dealing with the requirements for the project then finally finalizing the requirements (Lucid software 2018).
User design
In this phase continuous interactive process helps us to understand, modify and working model of system. As we will be applying proper Graphical User Interface (GUI), it will help the costumers to interact with our online banking effectively (Lucid software 2018).
Construction
This phase includes the rapid construction of the project. We have to prepare for this construction. It includes program and application development where coding is done to make sure everything is working smoothly. Final process includes system testing (Lucid software 2018).
Cutover
It is the implementation phase where our online banking comes into use. The final changes to be made are done in this phase and make our system into action.
Our group comprises of three members each responsible for doing various task. This assessment task is more like project proposal rather than developing the system. Gaurav Phuyal (k170766) is assigned with proper introduction, the aim and conclusion of the project. Moreover, he is to be dealt with executive summary, where overall view of project is mentioned. Key deliverables, functional and non-functional requirements are assigned to Roshan Adhikari(K170784). So, in this part, functional needs of the system are described briefly. The system we are going to build needs functional requirements to run the system effectively. Those functional needs are to be interacting with database in the backend using SQL queries along with the PHP scripts as the middleware and HTML5 and CSS for the front end. On the other hand, we have got non-functional requirements. Although they are the requirements that are not related to the specific functions delivered by the system but it plays vital role in developing perfect system. So, we have got performance requirements, safety requirements and security requirements. Finally, Sajit Magar(k170957) is dealing with the development approach of the project. For this Rapid Application Development (RAD)is used so that it will be easy for every user to use our banking system.
To sum up, we have initiated a preeminent project proposal favourable for an online banking costumer. We will be having a simple Model-View-Controller (MVC) framework with a centralised storage of the database. We will be using HTML and CSS to design a user interface. On the contrary, PHP scripts along with SQL queries are to be used for development of middleware. Investment, account, cheque services and utility services are extra functional requirements. Along with these we have some non functional requirements as well. Hence, Considering the architecture we have used, extra requirements added in our project will make our project standout.
Baltzan, P., Lynch, K. and Blakey P. (2014), Business Driven Information Systems, 4th Edition, McGraw Hill Irwin Boston MA
Lucid Software 2019,’Lucidchart’, Lucid viewed on 2nd April 2020 , https://www.lucidchart.com/blog/rapid-application-development-methodology
Mostak, t 2019,’Omni.sci’,omnsci.com, viewed on 1st April 2020, https://www.omnisci.com/technical-glossary/graphical-user-interface

Order from Australian Expert Writers
Best Australian Academic Writers

QUALITY: 100% ORIGINAL PAPERNO PLAGIARISM – CUSTOM PAPER