Scribd
Upload
18 views7 pages

EXPERIMENT - 1 Samiksha

The Software Requirements Specification (SRS) document outlines the E-Banking System's purpose, scope, and intended functionalities, providing a secure platform for online banking transactions. It details system interfaces, product functions, user characteristics, constraints, and specific requirements for development. The document serves as a comprehensive guide for stakeholders and developers throughout the software development lifecycle.

Uploaded by

gimowec215
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
18 views7 pages

EXPERIMENT - 1 Samiksha

The Software Requirements Specification (SRS) document outlines the E-Banking System's purpose, scope, and intended functionalities, providing a secure platform for online banking transactions. It details system interfaces, product functions, user characteristics, constraints, and specific requirements for development. The document serves as a comprehensive guide for stakeholders and developers throughout the software development lifecycle.

Uploaded by

gimowec215
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

EXPERIMENT - 1

Create a SRS document for e-banking system

1. Introduction

1.1 Purpose

The purpose of this Software Requirements Specification (SRS) document is to


provide a detailed description of the E-Banking System. It outlines the system's
intended features, functionalities, and constraints, serving as a guide for developers,
stakeholders, and project managers throughout the software development lifecycle.

1.2 Scope

The E-Banking System will provide users with a secure platform to perform banking
transactions online, including account management, fund transfers, bill payments,
and transaction history. The system will cater to individual customers and small
businesses, ensuring a user-friendly experience while maintaining high security
standards.

1.3 Definitions

● E-Banking: Electronic banking services that allow customers to conduct


financial transactions via the internet.
● **User **: An individual or entity that accesses the E-Banking System.
● Administrator: A user with elevated privileges to manage the system and its
users.

1.4 References

● IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements


Specifications.
● OWASP Top Ten Security Risks.
● ISO/IEC 27001:2013 Information Security Management.

1.5 Overview

This document is structured to provide a comprehensive overview of the E-Banking


System, including its functionalities, user characteristics, constraints, and system
attributes. It will also detail the specific requirements for the system, including
external interfaces, performance requirements, and compliance standards.

2. Overall Description

2.1 Product Perspective

The E-Banking System will be a web-based application accessible via desktop and
mobile devices. It will integrate with existing banking infrastructure and third-party
services for payment processing and security.

2.2 Interfaces

● User Interface: Web and mobile interfaces for customer interaction.


● Admin Interface: A separate interface for administrators to manage users and
transactions.
● API Interface: RESTful APIs for integration with third-party services.

2.3 Hardware Interfaces

● The system will operate on standard web servers and will be accessible via
any device with internet connectivity (PCs, tablets, smartphones).

2.4 Software Interfaces

● The system will be developed using a combination of HTML, CSS, JavaScript,


and a backend framework (e.g., Node.js, Django).
● Database management systems (e.g., MySQL, PostgreSQL) will be used for
data storage.
2.5 Common Interfaces

● The system will support common web standards (HTML5, CSS3, JavaScript)
and will be compatible with major web browsers (Chrome, Firefox, Safari).

2.6 Memory Constraints

● The application should efficiently manage memory usage to ensure smooth


performance on devices with limited resources.

2.7 Operations

● The system will operate 24/7, with scheduled maintenance windows


communicated to users in advance.

2.8 Site Adoption

● The system will be hosted on a cloud platform to ensure scalability and


reliability.

3. Product Functions

● User registration and authentication


● Account balance inquiry
● Fund transfers between accounts
● Bill payment processing
● Transaction history viewing
● User profile management
● Admin functionalities for user and transaction management

4. User Characteristics

● End Users: Individuals with basic computer skills who require online banking
services.
● Administrators: Users with advanced technical skills responsible for system
management.
5. Constraints

● Compliance with financial regulations (e.g., PCI DSS, GDPR).


● Limited budget and timeline for development.
● High availability and performance requirements.

6. Assumptions & Dependencies

● Users will have access to the internet and compatible devices.


● Third-party services (e.g., payment gateways) will be reliable and secure.

7. Specific Requirements

7.1 External Interfaces

● User Interface: Responsive design for various devices.


● API: RESTful endpoints for integration with external services.

7.2 Functional Requirements

● User registration and login functionality.


● Ability to view account balances and transaction history.
● Secure fund transfer capabilities.
● Bill payment options with confirmation notifications.

7.3 Performance Requirements

● The system should handle up to 10,000 concurrent users.


● Response time for transactions should not exceed 2 seconds.

7.4 Logical Database Requirements

● A relational database to store user data, transaction history, and account


information.

7.5 Design Constraints


● The system must be developed using secure coding practices to prevent
vulnerabilities.

7.6 Standard Compliance

● Compliance with PCI DSS for payment processing.


● Adherence to GDPR for data protection.

7.7 Software System Attributes

● Reliability: 99.9% uptime.


● Availability: 24/7 access with scheduled maintenance.
● Security: Multi-factor authentication and encryption

8 Organising the specific requirements

8.1. System Modes

● User Mode: For customers and small businesses to perform banking


transactions.
● Admin Mode: For administrators to manage users and system settings.

8.2. User Classes

● End Users: Individual customers and small business owners.


● Administrators: Bank staff managing the system.

8.3. Objects

● User Account: Customer banking account details.


● Transaction: Financial transaction details.
● Bill Payment: Scheduled payments to service providers.
● Admin User: Administrator with elevated privileges.
8.4. Features

● User Registration: Create a new account.


● User Authentication: Secure login.
● Account Management: View and manage account details.
● Fund Transfer: Transfer funds between accounts.
● Bill Payment: Manage bill payments.
● Transaction History: View past transactions.
● Admin Dashboard: Manage users and monitor transactions.

8.5. Stimulus and Response


Stimulus Response

User submits registration Account created, confirmation email sent.

User logs in Access granted to dashboard.

User initiates fund transfer Transfer processed, balances updated.

User requests transaction history History retrieved and displayed.

Admin logs in Admin dashboard displayed.

8.6. Functional Hierarchy

1. User Management
● Registration, Authentication, Account Management
2. Transaction Management
● Fund Transfer, Bill Payment, Transaction History
3. Admin Management
● User Management, Transaction Monitoring, System Settings

8.7. Additional Comments

● Ensure data integrity and security.


● Prioritize user experience and accessibility.
● Schedule regular security audits.

8.8. Change Management Process

● Change Request Submission: Stakeholders submit requests.


● Impact Analysis: Assess impact on scope, timeline, and budget.
● Approval Process: Reviewed by a change control board.
● Implementation: Approved changes implemented in the next cycle.
● Documentation: All changes documented in the project management system.

8.9. Document Approval

This SRS will be approved by:

● Project Manager: [Name]


● Lead Developer: [Name]
● Quality Assurance Lead: [Name]
● Business Analyst: [Name]
● Compliance Officer: [Name]

8.10. Supporting Information

● User Personas: Descriptions of typical users.


● Use Cases: Scenarios of user interactions.
● Wireframes: Visual representations of the user interface.
● Security Protocols: Documentation of security measures.
● Regulatory Compliance: Relevant regulations and standards.

This concise structure of specific requirements ensures clarity and understanding


among all stakeholders involved in the E-Banking System project.

You might also like