Develop an SRS for ‘Online Banking System’. Make necessary assumptions. Follow IEEE SRS format.

Understand the Problem

The question is asking to create a Software Requirements Specification (SRS) document for an Online Banking System, adhering to the IEEE format and making any necessary assumptions. This involves defining the requirements and functionalities of the system.

Answer

Follow IEEE SRS format. Include introduction, overall description, and specific requirements. Make assumptions.

To develop an SRS for an 'Online Banking System' using the IEEE format:

Introduction
- Purpose
- Scope
- Definitions
- References
- Overview
Overall Description
- Product Perspective
- Product Functions
- User Characteristics
- Constraints
- Assumptions and Dependencies
Specific Requirements
- Functional Requirements (e.g., Login, View Balance, Transfer Funds)
- Non-functional Requirements (e.g., Security, Usability)
- Interface Requirements (e.g., User Interfaces, Communication Interfaces)

More Information

An SRS (Software Requirement Specification) specifies what the software will do and how it will perform. The IEEE format helps ensure a structured and comprehensive document.

Tips

Common mistakes include missing key sections from the IEEE template, not making clear assumptions, and failing to specify all necessary constraints.

Sources

Software Requirement Specification (SRS) of Online Banking System - studocu.com
IEEE Software Requirements Specification Template - dspmuranchi.ac.in
How to Write an SRS Document - perforce.com

AI-generated content may contain errors. Please verify critical information

Thank you for voting!