Professional Documents
Culture Documents
<Project>
Prepared by <author>
<organization>
<date created>
Table of Contents
Table of Contents ......................................................................................................................... iii Revision History ............................................................................... Error! Bookmark not defined. 1. Introduction ..............................................................................................................................4
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 Purpose............................................................................................................................................. 4 Document Conventions .................................................................................................................... 4 Intended Audience and Reading Suggestions .................................................................................. 4 Project Scope ................................................................................................................................... 4 References ........................................................................................................................................ 5 Product Perspective.......................................................................................................................... 5 Product Features .............................................................................................................................. 5 User Classes and Characteristics ..................................................................................................... 6 Operating Environment .................................................................................................................... 6 Design and Implementation Constraints .......................................................................................... 6 User Documentation ........................................................................................................................ 6 Assumptions and Dependencies ...................................................................................................... 7
3.1 System Feature 1 .............................................................................Error! Bookmark not defined. 3.2 System Feature 2 (and so on) ........................................................................................................... 7
6. Other Requirements ..............................................................................................................10 Appendix A: Glossary..................................................................................................................10 Appendix B: Analysis Models .....................................................................................................10 Appendix C: Issues List ...............................................................................................................10
B.E. Computer
Revision History
Date 15/09/2008 Version 1.0 Description Internet Banking System Author SASIYAGNITES
Introduction
Purpose
The Traditional way of maintaining details of a user in a bank was to enter the details and record them. Every time the user need to perform some transactions he has to go to bank and perform the necessary actions, which may not be so feasible all the time. It may be a hardhitting task for the users and the bankers too. The project gives real life understanding of Internet banking and activities performed by various roles in the supply chain. Here, we provide an automation for banking system through Internet. Internet banking system project captures activities performed by different roles inreal life banking which provides enhanced techniques for maintaining the required information up-to-date, which results in efficiency. The project gives real life understanding of Internet banking and activities performed by various roles in the supply chain.
Document Conventions
OBS: Online Banking System SRS: Software Requirement Specification
Project Scope
This Project investigates the entry threshold for providing a new transaction service channel via the real options approach, where the entry threshold is established by using an Internet banking system designed for the use of normal users(individuals), Industrialists, Entrepreneurs,Educational Institutions(Financial sections), Organizations and Academicians under transaction rate uncertainty.
-4-
B.E. Computer
Customer must have a valid User Id and password to login to the system If a wrong password is given thrice in succession, that account will be locked and the customer will not be able to use it. When an invalid password is entered a warning is given to the user that his account is going to get locked. After the valid user logs in he is shown the list of accounts he has with the bank. On selecting the desired account he is taken to a page which shows the present balance inthat particular account number
References
SRS (IEEE SRS Format and Format provided by TGMC) Project specification requirement (provided by TGMC) Problem Definition (provided by TGMC)
Overall Description
Product Perspective
The client will have client interface in which he can interact with the banking system. It is a web based interface which will be the web page of the banking application. Starting a page is displayed asking the type of customer he is whether ordinary or a corporate customer. Then the page is redirected to login page where the user can enter the login details. If the login particulars are valid then the user is taken to a home page where he has the entire transaction list that he can perform with the bank. All the above activities come under the client interface. The administrator will have an administrative interface which is a GUI so that he can view the entire system. He will also have a login page where he can enter the login particulars so that he can perform all his actions. This administrative interface provides different environment such that he can maintain database & provide backups for the information in the database. He can register the users by providing them with username, password & by creating account in the database. He can view the cheque book request & perform action to issue the cheque books to the clients.
Product Features
The Internet banking system consists of following modules : 1) Login Process 2) This module allows valid customers to access the functionalities provided bythe bank. 3) Balance Enquiry 4) This module maintains the balance details of a particular account. 5) Update Profile 6) This module allows the customer to update profile of their account. 7) Funds Transfer 8) This module allows the customers to transfer funds from one account to another within the same bank 9) Change of Password 10) This module allows customers to change their password.
-5-
B.E. Computer
Operating Environment
GENERAL Customer shall obtain, install, operate and maintain the Equipment in accordance with the specifications set forth below and the terms and conditions of the FNB Online User Agreement as it may be modified from time to time. The following are the current minimum access, hardware and software requirements to utilize FNB Online. Future FNB Online modifications may affect minimum hardware and software requirements. Customer agrees at all times to use hardware and software complying with the minimum requirements established from time to time by First National Bank.
INTERNET ACCESS
Connectivity to the Internet is a prerequisite to utilization of FNB Online. Customer is solely responsible for maintaining connectivity to the Internet.
HARDWARE
Internet access. A color monitor. Display settings 800 x 600 pixels or higher.
SOFTWARE
Operating System Win 2000, SP4 Win XP, SP2 (Recommended) MAC OS X Certified Browsers Internet Explorer 6.x Supported Browsers Netscape 6.1, AOL 8.0 and 9.0, Firefox 1.0
Internet Explorer 7.0, Netscape Netscape 6.1 and Firefox 1.0 7.2, AOL 8.0 and 9.0 AOL for OS X and Safari 1.2
-6-
B.E. Computer
User Documentation
<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.>
1)
This project is a stand-alone project so it will not affect the system where it will be embedded.
2)
This project is a web-based project while the staff was addict of using traditional methods of data storage and retrieval so they will be trained a bit to jump to it.
3)
This system will not depend on any other module. It will be a webbased so every one will independently contact it.
4) 5)
It is will not affect the environment at all. Banks will feel free to adopt it because it will not be so much expensive.
6)
As this project contains valuable and new features so it will probably remove the previous online banking systems embedded in some banks.
System Features
Features: Online banking solutions have many features and capabilities in common, but traditionally also have some that are application specific. The common features fall broadly into several categories: 1) Transactional (e.g., performing a financial transaction such as an account to account transfer, paying a bill, wire transfer... and applications... apply for a loan, new account, etc.) Electronic bill presentment and payment - EBPP Funds transfer between a customer's own checking and savings accounts, or to another customer's account Investment purchase or sale
-7-
B.E. Computer
2) Non-transactional (e.g., online statements, check links, cobrowsing, chat) Bank statements
3) Financial Institution Administration - features allowing the financial institution to manage the online experience of their end users 4) ASP/Hosting Administration - features allowing the hosting company to administer the solution across financial institutions Features commonly unique to business banking include: 1) Support of multiple users having varying levels of authority 2) Transaction approval process 3) Wire transfer Features commonly unique to Internet banking include: Personal financial management support, such as importing data into personal accounting software. Some online banking platforms support account aggregation to allow the customers to monitor all of their accounts in one place whether they are with their main bank or with other institutions...
Hardware Interfaces
Client Side ( IE Along with Printer ) Processor Ram Disc Space
64 MB 1 GB
Server Side
-8-
DB2 V8.1
1 GHz
Software Interfaces
User on Internet : Web Browser, Operating System (any)
Application Server : WAS Data Base Server Network Development Tools : DB2 : Internet : WSAD (J2EE,Java,Servlets,HTML), DB2, OS(Windows), Application Server.
Communications Interfaces
Client on Internet will be using HTTP/HTTPS protocol. Client on Intranet will be using TCP/IP protocol.
Safety Requirements
By incorporating a robust and proven DB2 UDB into the system, reliable performance and integrity of data is ensured. There must be a power backup for server system. Since the product is of 24x7 availability there should be power backup for server which provides the information .Every day the data should be backup even when the operation of an user is not
-9-
B.E. Computer
successful i.e., while performing the operation power failure occurs then data should be backup.
Security Requirements
Sensitive data is protected from unwanted access by users appropriate technology and implementing strict user-access criteria. Facility of unique user number and Password in such a way that unauthorized user cannot log in. Operational rights for each user/terminal can be defined. Thus, a user can have access to specific terminals and specific options only.
Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>
- 10 -
B.E. Computer
6. What are the Software Quality Attributes? Explain it in the context of your system?
- 11 -
B.E. Computer
7. What are the External Interface Requirements? Which requirements are need to be satisfied by your system?
8. Explain the term assumption and dependencies. State these terms in the context of your system?
9. What is SDLC?
- 12 -