CHAPTER THREE
RESEARCH METHODOLOGY
This chapter discusses the methodology used in designing and implementing the Multifactor
Authentication System for Mobile Banking Solutions. It outlines the system analysis, design, and
architecture, providing a detailed description of the existing system, its limitations, and the
justification for the proposed solution.
3.0 SYSTEM ANALYSIS AND DESIGN
3.1 System Analysis
3.1.1 Analysis of the Existing System
The existing authentication system used in mobile banking relies primarily on single-factor
authentication methods such as passwords or PINs. This approach, while common, is susceptible
to various security threats, including phishing attacks, brute force attacks, and credential leaks.
3.1.2 Limitations of the Existing System
The major drawbacks of the current system include:
• Vulnerability to phishing and brute-force attacks.
• Lack of biometric or multi-layered authentication.
• Difficulty in recovering lost or stolen credentials securely.
3.1.3 Justification for the New System
To enhance security in mobile banking authentication, the proposed system integrates multifactor
authentication (MFA), which combines traditional credentials with an additional security layer,
such as QR code authentication. This ensures:
• Improved security against credential-based attacks.
• Easier and more secure user authentication.
• Enhanced user experience with minimal complexity.
3.1.4 Description of the New System
The proposed system integrates QR code-based authentication, where a user logs in by scanning
a dynamically generated QR code. This enhances security by ensuring that authentication occurs
only through a verified mobile device.
3.2 DESIGN OF THE PROPOSED SYSTEM
3.2.1 Data Model (ERD and Normalization)
The system’s database is structured to ensure data integrity and efficiency. The Entity-
Relationship Diagram (ERD) is translated into relational schemas, and the database tables are
normalized to at least the third normal form (3NF) to remove redundancy.
Fig 3.2 Database Table
3.2.2 Functional Requirement (Use Case Diagram)
The system’s core functionalities are represented in the Use Case Diagram, which illustrates how
users interact with the system.
Login
Register
Authenticate
Authenticate
Login
Fig 3.3: Use Case Diagram
3.2.3 System/Network Architecture (Deployment Diagram)
The proposed system follows a client-server architecture, where the authentication process is
managed by a central authentication server. The Deployment Diagram provides an overview of
the interaction between different system components.
Fig3.4: Deployment Diagram
3.2.4 Software Structure (Class Diagram)
The Class Diagram showcases the object-oriented structure of the system, depicting classes such
as User, Authentication, QRCodeGenerator, and Database Handler.
Fig3.5: Class Diagram
3.2.5 Workflow of Use Cases (Activity Diagram)
The Activity Diagram illustrates the step-by-step authentication process, from user login to QR
code verification and system access.
Login to Authentication System
Start
QR Code Verification
Check Check
Permission Permission
Logout from the End
system
Fig 3.6: Activity Diagram Here
Conclusion
This chapter presented the methodology used in analyzing and designing the Multifactor
Authentication System. It outlined the existing system’s limitations, justified the need for the
new system, and detailed its design, including ERD, use case diagrams, system architecture, and
workflow models. The next chapter will focus on system implementation and testing.