Analytical Study on Internet Banking System

The Internet era is a period in the information age in which communication and commerce via the Internet became a central focus for businesses, consumers, government, and the media. The Internet era also marks the convergence of the computer and communications industries and their associated services and products. Nowadays, the availability of the Internet make it widely used for everyday life. In order to led business to success, the business and specially the services should provide comfort use to its costumer. The bank system is one of the most important businesses who may use the website. The using for the web-based systems should contain special requirements to achieve the business goal. Since that the paper will present the functional and non-functional for the web-based banking system.

💡 Research Summary

The paper addresses the design of an Internet‑based banking system by systematically outlining both functional and non‑functional requirements that are essential for success in today’s digital economy. It begins with a contextual overview of the Internet era, emphasizing how the convergence of computing and communications has transformed business models, especially in the financial sector where trust, security, and accessibility are paramount. The authors argue that a web‑based banking platform must be built on a solid requirements foundation to meet business goals and regulatory expectations.

The functional requirements section enumerates core banking operations such as account inquiry, balance display, fund transfers, bill payments, loan applications, credit management, and customer authentication. For each operation the paper stresses the need for rigorous input validation, comprehensive error handling, transaction atomicity, and detailed audit logging. The authors also highlight the necessity of supporting multiple channels—desktop browsers, mobile apps, and emerging interfaces like chatbots—through well‑defined APIs (RESTful, GraphQL) and a service‑oriented architecture that separates presentation, business logic, and data layers. Real‑time processing and high concurrency are identified as critical drivers for adopting asynchronous messaging and scalable service orchestration.

In the non‑functional requirements segment the paper groups quality attributes into four major categories: security, performance, availability/reliability, and scalability/maintainability. Security requirements include end‑to‑end encryption (TLS), data‑at‑rest encryption, multi‑factor authentication, role‑based access control, intrusion detection/prevention systems, and regular vulnerability assessments. Performance goals are quantified as sub‑2‑second average response times and the ability to handle at least 10,000 transactions per second, which the authors propose to achieve through caching layers (Redis, CDN), load balancing, and efficient database sharding. Availability targets a 99.9 % service level agreement, necessitating redundant server clusters, automatic failover mechanisms, disaster‑recovery sites, and continuous health monitoring. Scalability is addressed through a micro‑services architecture deployed in containers (Docker, Kubernetes), enabling horizontal scaling and rapid provisioning of new services. Maintainability is reinforced by coding standards, automated unit/integration testing, and a CI/CD pipeline that supports frequent, low‑risk releases. The paper also stresses accessibility compliance with WCAG 2.1 Level AA, multilingual support, and assistive‑technology integration to serve users with disabilities.

To ensure traceability, the authors propose a Requirements Traceability Matrix (RTM) that maps each requirement to design artifacts, implementation modules, and test cases. They recommend iterative stakeholder reviews—including bank executives, regulators, customers, and development teams—to capture evolving business needs and regulatory changes. Although the paper does not present a concrete case study or empirical performance data, it offers a comprehensive framework of metrics and quality‑attribute models that can guide practitioners in building robust, user‑friendly, and secure online banking systems. The concluding remarks suggest that while the theoretical model is thorough, real‑world validation through pilot deployments and performance benchmarking is essential for confirming the efficacy of the proposed requirements set. Overall, the work provides a balanced, detailed blueprint that aligns functional capabilities with stringent non‑functional constraints, positioning Internet banking platforms to thrive in a competitive, security‑sensitive market.