Output:-

Output:-
Output:-
Program:-
set ns [new Simulator]
set nf [open [Link] w]
$ns
namtrace-all
$nf proc finish
{} { global ns
nf
$ns
flush-trace
close $nf
exec nam
[Link] & exit 0
}
set n0 [$ns
node] set n1
[$ns node]
set n2 [$ns
node] set n3
[$ns node]

$ns duplex-link $n0 $n2 10mb 10ms DropTail

$ns duplex-link $n1 $n2 10mb 10ms DropTail
$ns duplex-link $n2 $n3 10mb 10ms DropTail

$ns duplex-link-op $n0 $n2 orient right-down

$ns duplex-link-op $n1 $n2 orient right-up

$ns duplex-link-op $n2 $n3 orient right

$ns at 1.0 "finish"

$ns run
Output:-
Output:-
Output:-
UDP Sever import [Link].*;

import [Link];

class UDPServer

public static void main(String args[])throws Exception

DatagramSocket serverSocket = new DatagramSocket(9876);

byte[] receiveData=new byte[1024];

byte[] sendData=new byte[1024];

while(true)

[Link]("Server is Up");

DatagramPacket receivePacket=new DatagramPacket(receiveData,[Link]);

[Link](receivePacket);

String sentence=new String([Link]());

[Link]("RECEIVED:"+sentence);

InetAddress IPAddress=[Link]();

int port=[Link]();

String capitalizedSentence=[Link]();

sendData=[Link]();

DatagramPacket sendPacket=new DatagramPacket(sendData,[Link],IPAddress,port);

[Link](sendPacket);

//UDP Client import [Link].*;

import [Link].*;

import [Link];

class UDPClient

public static void main(String[] args)throws Exception

{

BufferedReader inFromUser=new BufferedReader(new InputStreamReader([Link]));

DatagramSocket clientSocket=new DatagramSocket();

InetAddress IPAddress=[Link]("localhost");

byte[] sendData=new byte[1024];

byte[] receiveData=new byte[1024];

[Link]("Enter the sting to be converted in to Upper case");

String sentence=[Link]();

sendData=[Link]();

DatagramPacket sendPacket=new DatagramPacket(sendData,[Link],IPAddress,9876);

[Link](sendPacket);

DatagramPacket receivePacket=new DatagramPacket(receiveData,[Link]);

[Link](receivePacket);

String modifiedSentence=new String([Link]());

[Link]("FROM SERVER:"+modifiedSentence); [Link]();

}
 ONLINE BANKING SYSTEM
SOFTWARE REQUIREMENT SPECIFICATIONS (IEEE)

The system will function as a standalone

I.​INTRODUCTION product accessible via browsers and mobile
apps. It will be supported by a secure
centralized database and cloud hosting.
I.I​Purpose
The purpose of the Online Banking System
System Architecture:
is to provide customers with secure, reliable, •​ Frontend: ReactJS / Angular (Web),
and efficient digital banking services. The
Flutter / React Native (Mobile)
system enables customers to check account
balances, transfer funds, pay bills, request •​ Backend: [Link] / Django / Java Spring
services (chequebook, loans, cards), and Boot
manage their accounts anytime, anywhere. •​ Database: MySQL / PostgreSQL (with
Bank administrators can manage users, encryption)
monitor transactions, and ensure •​ Hosting: AWS / Azure (with banking
compliance with regulations. compliance)

[Link]​Scope [Link]​Product Functions

•​ Account Management (view balance, •​ Authentication Module – Secure login,
transaction history, account details) OTP, biometric authentication
•​ Funds Transfer (within bank, inter-bank, •​ Account Management Module – View
UPI, international) balances, transactions, download
•​ Bill Payments (utilities, insurance, loans, statements
recharge, taxes) •​ Funds Transfer Module – Intra-bank,
•​ User Services (loan applications, card inter-bank, UPI, international transfers
requests, cheque services) •​ Payment Module – Bill payments,
•​ Security (OTP, encryption, fraud recharge, tax payments
detection, two-factor authentication)
•​ Service Request Module – Loans, credit
•​ Admin Dashboard (customer cards, cheque books
management, transaction monitoring, •​ Admin Module – Manage users, approve
reporting) services, generate compliance reports
[Link]​Definitions, Acronyms, and
Abbreviations [Link] Constraints
•​ KYC: Know Your Customer •​ Must comply with RBI/International
•​ OTP: One-Time Password banking regulations
•​ IMPS/NEFT/RTGS: Fund transfer •​ Mobile app should run on Android 10+
methods and iOS 13+
•​ UI: User Interface •​ High availability (99.99% uptime)
•​ DBMS: Database Management System •​ Strong encryption for all transactions
(AES-256, SSL/TLS)
[Link]​References
•​ IEEE Std 830-1998 – Software
Requirement Specifications III.​ SPECIFIC
•​ RBI Digital Banking Guidelines REQUIREMENTS
•​ Documentation from existing online
•​ FR1.1: The system shall allow users to
banking systems
log in with credentials + OTP/biometric.

II.​OVERALL DESCRIPTION •​ FR1.2: The system shall enforce

password complexity and periodic reset

II.I​Product Perspective
 [Link]​Use Case: Admin Monitors
Account Management Transactions
•​ FR2.1: Customers can view balance and
mini-statement. Admin logs in → accesses dashboard →
•​ FR2.2: Customers can download detailed filters suspicious transactions → system
statements in PDF/CSV. highlights flagged entries.
Funds Transfer
V.​ APPENDICES
•​ FR3.1: Customers can transfer funds
between accounts in the same bank.
Glossary:
•​ FR3.2: Customers can transfer to other
banks via NEFT/RTGS/IMPS. •​ KYC, OTP, IMPS, RTGS, NEFT, UPI,
•​ FR3.3: International transfer via SWIFT SWIFT, DBMS
integration.
Future Enhancements:
Payments
•​ AI-powered fraud detection
•​ FR4.1: Customers can pay utility bills •​ Chatbot for customer service
and mobile recharges. •​ Voice-enabled banking
•​ FR4.2: Customers can schedule •​ Cryptocurrency wallet integration
recurring payments.

Services
•​ FR5.1: Customers can request cheque
books, debit/credit cards.
•​ FR5.2: Customers can apply for personal
loans.

Admin Functions
•​ FR6.1: Admin can monitor transactions
and flag suspicious activity.
•​ FR6.2: Admin can generate compliance
and audit reports.

IV.​SYSTEM FEATURES (USE

CASES)

IV.I​Use Case: Fund Transfer

Customer logs in → selects transfer option

→ enters details → authenticates via OTP

→ system processes transaction →

confirmation message displayed.

[Link]​Use Case: Bill Payment

Customer logs in → selects bill payment →

enters amount/details → authenticates

payment →
system confirms transaction.
 ONLINE BANKING SYSTEM
SOFTWARE REQUIREMENT SPECIFICATIONS (SRS)

I. INTRODUCTION

I.I Purpose
The purpose of the Online Banking System is to provide customers with secure, reliable, and
efficient digital banking services. The system enables customers to check account balances,
transfer funds, pay bills, request services (chequebook, loans, cards), and manage their accounts
anytime, anywhere. Bank administrators can manage users, monitor transactions, and ensure
compliance with regulations.

[Link] Scope
• Account Management (view balance, transaction history, account details)
• Funds Transfer (within bank, inter-bank, UPI, international)
• Bill Payments (utilities, insurance, loans, recharge, taxes)
• User Services (loan applications, card requests, cheque services)
• Security (OTP, encryption, fraud detection, two-factor authentication)
• Admin Dashboard (customer management, transaction monitoring, reporting)

[Link] Definitions, Acronyms, and Abbreviations

• KYC: Know Your Customer
• OTP: One-Time Password
• IMPS/NEFT/RTGS: Fund transfer methods
• UI: User Interface
• DBMS: Database Management System

[Link] References
• IEEE Std 830-1998 – Software Requirement Specifications
• RBI Digital Banking Guidelines
• Documentation from existing online banking systems

II. OVERALL DESCRIPTION

II.I Product Perspective

The system will function as a standalone product accessible via browsers and mobile apps. It will
be supported by a secure centralized database and cloud hosting.

System Architecture:
• Frontend: ReactJS / Angular (Web), Flutter / React Native (Mobile)
• Backend: [Link] / Django / Java Spring Boot
• Database: MySQL / PostgreSQL (with encryption)
• Hosting: AWS / Azure (with banking compliance)

[Link] Product Functions

• Authentication Module – Secure login, OTP, biometric authentication
• Account Management Module – View balances, transactions, download statements
• Funds Transfer Module – Intra-bank, inter-bank, UPI, international transfers
• Payment Module – Bill payments, recharge, tax payments
• Service Request Module – Loans, credit cards, cheque books
• Admin Module – Manage users, approve services, generate compliance reports

[Link] Constraints
• Must comply with RBI/International banking regulations
• Mobile app should run on Android 10+ and iOS 13+
• High availability (99.99% uptime)
• Strong encryption for all transactions (AES-256, SSL/TLS)

III. SPECIFIC REQUIREMENTS

III.I Functional Requirements

Authentication
• FR1.1: The system shall allow users to log in with credentials + OTP/biometric.
• FR1.2: The system shall enforce password complexity and periodic resets.

Account Management
• FR2.1: Customers can view balance and mini-statement.
• FR2.2: Customers can download detailed statements in PDF/CSV.

Funds Transfer
• FR3.1: Customers can transfer funds between accounts in the same bank.
• FR3.2: Customers can transfer to other banks via NEFT/RTGS/IMPS.
• FR3.3: International transfer via SWIFT integration.

Payments
• FR4.1: Customers can pay utility bills and mobile recharges.
• FR4.2: Customers can schedule recurring payments.

Services
• FR5.1: Customers can request cheque books, debit/credit cards.
• FR5.2: Customers can apply for personal loans.

Admin Functions
• FR6.1: Admin can monitor transactions and flag suspicious activity.
• FR6.2: Admin can generate compliance and audit reports.

IV. SYSTEM FEATURES (USE CASES)

IV.I Use Case: Fund Transfer

Customer logs in → selects transfer option → enters details → authenticates via OTP → system
processes transaction → confirmation message displayed.

[Link] Use Case: Bill Payment

Customer logs in → selects bill payment → enters amount/details → authenticates payment →
system confirms transaction.
[Link] Use Case: Admin Monitors Transactions
Admin logs in → accesses dashboard → filters suspicious transactions → system highlights flagged
entries.

V. APPENDICES

Glossary:
• KYC, OTP, IMPS, RTGS, NEFT, UPI, SWIFT, DBMS

Future Enhancements:
• AI-powered fraud detection
• Chatbot for customer service
• Voice-enabled banking
• Cryptocurrency wallet integration
Program (SQL):

SQL code for OLAP operations

Sample Outputs:
ROLLUP – aggregated totals

SLICE – Year=2024 by Region

DRILLDOWN – Region='North' by Year, Quarter
Program (Python):

Python code — Naive Bayes (Gaussian)

Execution Output:

Terminal output — accuracy

Histogram Output (Required):

Histogram of predicted P(class=1)

Program (Python)

Python code — discretization and visualization

Outputs & Graphs:

Histogram of raw values

Equal-width bin counts
Screenshots (Representational):

WEKA — Preprocess tab

Program (Python):

import numpy as np

import [Link] as plt

from [Link] import make_blobs

# Generate synthetic dataset

X, y = make_blobs(n_samples=300, centers=3, random_state=42)

# Initialize parameters

k=3

[Link](42)

centroids = X[[Link]([Link][0], k, replace=False)]

for _ in range(100):

# Assign clusters

distances = [Link](X[:, [Link]] - centroids, axis=2)

cluster_labels = [Link](distances, axis=1)

# Update centroids

new_centroids = [Link]([X[cluster_labels == i].mean(axis=0) for i in range(k)])

if [Link](centroids == new_centroids):

break

centroids = new_centroids

# Output cluster sizes

for i in range(k):
 print(f"Cluster {i+1}: {[Link](cluster_labels==i)} points")

# Plot clusters

[Link](X[:,0], X[:,1], c=cluster_labels, cmap='viridis', s=30)

[Link](centroids[:,0], centroids[:,1], c='red', marker='X', s=200)

[Link]("K-Means Clustering (k=3)")

[Link]()

K-Means code (screenshot)

Execution Output:

Cluster 1: 100 points

Cluster 2: 100 points

Cluster 3: 100 points

Terminal output showing convergence and cluster sizes

Graphical Output:
Program (Python):

import [Link] as plt

from [Link] import dendrogram, linkage

from [Link] import make_blobs

# Dataset

X, _ = make_blobs(n_samples=50, centers=3, random_state=42)

# Perform hierarchical clustering

Z = linkage(X, method='ward')

# Plot dendrogram

[Link](figsize=(8, 5))

dendrogram(Z)

[Link]("Hierarchical Clustering Dendrogram")

[Link]("Data Points")

[Link]("Distance")

[Link]()
Execution Output:

Graphical Output:
Program (Python):

from mlxtend.frequent_patterns import apriori, association_rules

import pandas as pd

# Transaction dataset

dataset = [

['milk', 'bread', 'eggs'],

['milk', 'bread'],

['milk', 'eggs'],

['bread', 'eggs'],

['milk', 'bread', 'eggs', 'butter']

# Convert to one-hot dataframe

items = sorted(set(item for transaction in dataset for item in transaction))

encoded = [{item: (item in transaction) for item in items} for transaction in dataset]

df = [Link](encoded)

# Apply Apriori

frequent_itemsets = apriori(df, min_support=0.4, use_colnames=True)

rules = association_rules(frequent_itemsets, metric="confidence", min_threshold=0.6)

print("Frequent Itemsets:\n", frequent_itemsets)

print("\nAssociation Rules:\n", rules[['antecedents', 'consequents', 'support', 'confidence',

'lift']])
Execution Output:

Rules (Graphical/Table):
Program (Python):

import numpy as np

# Graph adjacency matrix (5 nodes)

G = [Link]([

[0,1,1,0,0],

[0,0,1,1,0],

[0,0,0,1,1],

[1,0,0,0,1],

[0,0,0,0,0]

])

# PageRank

def pagerank(G, d=0.85, max_iter=100, tol=1e-6):

n = [Link][0]

out_degree = [Link](G, axis=1)

M = [Link](G.T, out_degree, where=out_degree!=0)

pr = [Link](n)/n

for _ in range(max_iter):

new_pr = (1-d)/n + d*[Link](pr)

if [Link](new_pr-pr, 1) < tol:

break

pr = new_pr

return pr

# HITS

def hits(G, max_iter=100, tol=1e-6):

n = [Link][0]

h = [Link](n)

a = [Link](n)
 for _ in range(max_iter):

a_new = [Link](h)

h_new = [Link](a_new)

a_new /= [Link](a_new, 2)

h_new /= [Link](h_new, 2)

if [Link](a, a_new, atol=tol) and [Link](h, h_new, atol=tol):

break

a, h = a_new, h_new

return a, h

pr = pagerank(G)

a, h = hits(G)

print("PageRank Scores:", pr)

print("Authority Scores:", a)

print("Hub Scores:", h)

Execution Output:

in theory

PageRank Scores: [0.185 0.215 0.215 0.215 0.170]

Authority Scores: [0.47 0.43 0.59 0.48 0.34]

Hub Scores: [0.45 0.55 0.48 0.51 0.00]

Practical output:

Terminal output showing files saved

Graphical Outputs:

PageRank scores (bar chart)

HITS Hub scores (bar chart)