0% found this document useful (0 votes)
38 views12 pages

SRS PW1 Final-1

Uploaded by

Rohit Jambhulkar
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
0% found this document useful (0 votes)
38 views12 pages

SRS PW1 Final-1

Uploaded by

Rohit Jambhulkar
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/ 12

SOFTWARE REQUIREMENTS

SPECIFICATION for Online Blockchain


Based Payment System
Version 1.0

Prepared by:
1. Rohit Jambhulkar (22220336)
2. Gaurav Maddi (22220309)
3.Sandip Ugile (22110679)

Submitted to : Prof Manohar.K.Kodmelwar


December 8 2023
Table of Contents

Introduction
1.1 Purpose of the Document
1.2 Scope of the System
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview of the System
General Description
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 User Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communication Interfaces
3.2 Functional Requirements
3.2.1 User Registration and Authentication
3.2.2 Wallet Creation and Management
3.2.3 Transaction Processing
3.2.4 Transaction History
3.2.5 Security Measures
3.2.6 Notification System
3.2.7 Compliance and Regulations
3.3 Performance Requirements
3.4 Design Constraints
3.5 Software System Attributes
3.5.1 Reliability
3.5.2 Availability
3.5.3 Security
3.5.4 Maintainability
3.5.5 Scalability
External Requirements
4.1 Regulatory Requirements
4.2 Security Requirements
4.3 Privacy Requirements
Testing and Validation
5.1 System Testing
5.2 User Acceptance Testing
5.3 Performance Testing
5.4 Security Testing
Diagrams
6.4.1 Entity-Relationship (ER) Diagram
6.4.2 System Architecture Diagram
6.4.3 Communication Flow Diagram
1. Introduction

1.1 Purpose of the Document: This comprehensive Software Requirements Specification (SRS)
document serves as a pivotal guide, capturing the intricacies and specifications of the
blockchain-based payment application. It outlines the requirements, functionalities, and
constraints essential for the successful development and implementation of the system.
1.2 Scope of the System: The scope of the blockchain-based payment application extends
beyond traditional payment solutions, aiming to revolutionize financial transactions by
leveraging the transparency and security offered by blockchain technology. It encompasses user
registration, wallet management, transaction processing, and meticulous compliance with
regional regulatory frameworks.
1.3 Definitions, Acronyms, and Abbreviations: To ensure clarity and understanding, a
comprehensive glossary is included (refer to Appendix 6.1) providing definitions for technical
terms, acronyms, and abbreviations utilized throughout this document.
1.4 References: This document draws upon relevant references, including industry standards,
blockchain protocols, and legal requirements. A comprehensive list of these references is
included for further exploration and context (refer to Appendix 6.2).
1.5 Overview of the System: At its core, the blockchain-based payment application is designed
to provide users with a seamless, secure, and transparent payment experience. Through
intuitive web and mobile interfaces, users can engage in transactions, manage wallets, and
benefit from the inherent advantages of blockchain technology.

2. General Description

2.1 Product Perspective: The application interfaces with users through web and mobile
platforms, offering an intuitive experience. Additionally, it integrates seamlessly with blockchain
networks, utilizing Application Programming Interfaces (APIs) for transaction validation. This
integration enhances the reliability and security of transactions.
2.2 Product Functions: The application encompasses a spectrum of functionalities to meet the
diverse needs of users, including:
 Robust user registration and authentication processes
 Flexible wallet creation and management capabilities
 Transparent and secure transaction processing on blockchain networks
 Real-time transaction history for user visibility
 Stringent security measures, including end-to-end encryption and secure key
management
 A proactive notification system to keep users informed
 Adherence to compliance standards and regulations to ensure a legal and secure
environment

2.3 User Characteristics: The user base consists of individuals and businesses seeking a cutting-
edge payment solution. While no specialized technical expertise is required, users are expected
to have a basic understanding of blockchain technology to fully leverage the application's
capabilities.
2.4 Constraints: The application operates within certain constraints, including the necessity for
a reliable internet connection and strict compliance with regional regulatory requirements.
These constraints are vital considerations to ensure the seamless functionality and legal
adherence of the system.
2.5 Assumptions and Dependencies: To operate optimally, the system assumes that users will
willingly comply with Know Your Customer (KYC) procedures. Additionally, the application is
dependent on external blockchain networks for transaction validation, emphasizing the
importance of a symbiotic relationship with these networks.

3. Specific Requirements

3.1 External Interface Requirements:

3.1.1 User Interfaces: The application commits to providing users with an intuitive, visually
appealing, and user-friendly interface, accessible across various devices and screen sizes.
3.1.2 Hardware Interfaces: Accessibility is prioritized, ensuring the application is usable across
devices with an internet connection, from smartphones to desktop computers.
3.1.3 Software Interfaces: Seamless integration with blockchain networks is facilitated through
well-defined APIs, enabling secure and efficient transaction validation.
3.1.4 Communication Interfaces: Data transmission is secured through robust communication
interfaces, utilizing encryption protocols to safeguard user information during transmission
between the application and blockchain networks.

3.2 Functional Requirements:


3.2.1 User Registration and Authentication: User onboarding is a secure process, requiring
valid identification for registration. Authentication is fortified through multi-factor
authentication methods, ensuring the integrity of user accounts.
3.2.2 Wallet Creation and Management: Users enjoy the flexibility of creating and managing
multiple wallets within the application. These wallets extend support to major cryptocurrencies,
enhancing the application's versatility.
3.2.3 Transaction Processing: Transactions are processed transparently on the blockchain,
ensuring a tamper-proof and verifiable record of each transaction. Real-time confirmation
notifications offer users immediate feedback on the status of their transactions.
3.2.4 Transaction History: Users have access to detailed transaction history, providing a
comprehensive overview of their financial activities. Information includes transaction status,
amount, and timestamp, fostering transparency and accountability.
3.2.5 Security Measures: The application employs robust security measures, including end-to-
end encryption for user data and secure key management for wallets. These measures are
crucial in safeguarding user information from unauthorized access.
3.2.6 Notification System: To enhance user experience, the application incorporates a
proactive notification system. Users receive timely notifications for successful transactions and
other account activities, keeping them informed and engaged.
3.2.7 Compliance and Regulations: Stringent adherence to Know Your Customer (KYC)
procedures is mandated to ensure compliance with regulatory requirements. Additionally, the
application aligns with the General Data Protection Regulation (GDPR) and other pertinent
regulations, prioritizing the privacy and security of user data.

3.5 Software System Attributes

3.5.1 Reliability: Reliability is a cornerstone of the application, with an uptime commitment of


99.9%. This reliability ensures users can depend on the application for their financial
transactions consistently.
3.5.2 Availability: A robust backup and recovery mechanism is implemented to guarantee the
availability of the system. In the event of failures or disruptions, the application can swiftly
recover, minimizing downtime.
3.5.3 Security: The security of user data is paramount. The application incorporates end-to-end
encryption, secure key management, and undergoes regular security audits to identify and
rectify vulnerabilities, ensuring a resilient security posture.
3.5.4 Maintainability: To facilitate ongoing updates and maintenance, the application is
designed with a modular architecture. This modularity allows for easy integration of updates
and enhancements without compromising the stability of the system.
3.5.5 Scalability: The system architecture is inherently scalable, capable of accommodating an
increased number of users and transactions. This scalability ensures the application can evolve
alongside user demand without compromising performance.

4. External Requirements

4.1 Regulatory Requirements: The application operates within the framework of financial
regulations and data protection laws specific to the regions it serves. Strict adherence to these
regulatory requirements is a non-negotiable aspect of the system.
4.2 Security Requirements: The application employs a multi-faceted approach to security,
incorporating secure sockets layer (SSL) for data transmission. Regular security audits and
penetration testing further fortify the system against potential threats.
4.3 Privacy Requirements: Privacy is prioritized through compliance with the General Data
Protection Regulation (GDPR) and other privacy regulations. User data is handled with the
utmost sensitivity and confidentiality to maintain user trust.

5. Testing and Validation

5.1 System Testing: Comprehensive system testing is undertaken to validate the functionality,
integration, and performance of the application. This testing phase ensures that all components
work cohesively to deliver a reliable and seamless user experience.
5.2 User Acceptance Testing: User feedback is actively solicited during the user acceptance
testing phase. This iterative process allows for the validation of usability, functionality, and
overall user satisfaction, ensuring the application meets user expectations.
5.3 Performance Testing: Performance testing is conducted under various load conditions to
assess the application's ability to handle varying levels of user activity. This testing phase aims
to identify and address any performance bottlenecks, ensuring optimal system performance.
5.4 Security Testing: Regular security audits and penetration testing are integral components of
the application's development lifecycle. These tests are conducted to identify and rectify
potential vulnerabilities, safeguarding the application against security threats.

6. Diagrams

Fig 6.1 ER Diagram

Fig 1. System Design Architecture


Fig 2. Data flow Diagram

Fig 3.1 Login Screen


Fig 3.2 Allowing meta mask to establish connection

Fig 3.3 Login Screen of EthxChain Payment System

Fig 3.4 Payment Initiation Screen


Fig 3.5 Transaction Validation & Confirmation

6. Appendix

6.1 Glossary: The glossary (refer to Appendix 6.1) provides a detailed compilation of technical
terms, acronyms, and abbreviations used throughout this document. It serves as a quick
reference for readers seeking clarification on terminology.
6.2 User Documentation: User manuals and documentation (refer to Appendix 6.2) are
provided to guide users through the functionalities and features of the application. This
documentation aims to enhance user understanding and facilitate a smooth onboarding
process.
6.3 Technical Documentation: For developers and technical stakeholders, detailed technical
documentation (refer to Appendix 6.3) is available. This documentation delves into the
intricacies of the application's architecture, APIs, and other technical aspects, providing a
comprehensive resource for development and maintenance.
This Software Requirements Specification document stands as a testament to the commitment
to delivering a cutting-edge blockchain-based payment application. By encapsulating a myriad
of features, functionalities, and stringent security measures, the application aims to redefine
the landscape of financial transactions, offering users a secure, transparent, and efficient
payment solution.

You might also like