Assignment 1 SRS Template

ASSIGNMENT NUMBER : 1

TITLE OF ASSIGNMENT : Software Requirement Specification

NAME :

DATE :

REMARK :

Software Requirements Specification

for

<Project>

Prepared by <author>

<organization>

<date created>

Software Requirements Specification for <Project>Page iii

Table of ContentsTable of Contents...........................................................................................................................vRevision History.............................................................................................................................v1. Introduction..............................................................................................................................6

1.1 Purpose..............................................................................................................................................61.2 Document Conventions.....................................................................................................................61.3 Intended Audience and Reading Suggestions...................................................................................61.4 Project Scope....................................................................................................................................61.5 References.........................................................................................................................................6

2. Overall Description..................................................................................................................72.1 Product Perspective...........................................................................................................................72.2 Product Features................................................................................................................................72.3 User Classes and Characteristics......................................................................................................72.4 Operating Environment.....................................................................................................................72.5 Design and Implementation Constraints...........................................................................................72.6 User Documentation.........................................................................................................................82.7 Assumptions and Dependencies.......................................................................................................8

3. System Features.......................................................................................................................83.1 System Feature 1...............................................................................................................................83.2 System Feature 2 (and so on)............................................................................................................9

4. External Interface Requirements...........................................................................................94.1 User Interfaces..................................................................................................................................94.2 Hardware Interfaces..........................................................................................................................94.3 Software Interfaces...........................................................................................................................94.4 Communications Interfaces..............................................................................................................9

5. Other Nonfunctional Requirements.....................................................................................105.1 Performance Requirements.............................................................................................................105.2 Safety Requirements.......................................................................................................................105.3 Security Requirements....................................................................................................................105.4 Software Quality Attributes............................................................................................................10

6. Other Requirements..............................................................................................................10Appendix A: Glossary..................................................................................................................10Appendix B: Analysis Models.....................................................................................................11Appendix C: Issues List...............................................................................................................11

OOMD Lab Manual B.E. Computer

Revision History

Date Version Description Author

15/09/2008 1.0 Internet Banking System 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 hard-hitting 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

Intended Audience and Reading Suggestions

<Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.>

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.•Customer must have a valid User Id and password to login to the system

Sinhgad Institute Of Technology and Science, Narhe - 4 -


•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 Process2) This module allows valid customers to access the functionalities provided bythe bank.3) Balance Enquiry4) This module maintains the balance details of a particular account.5) Update Profile6) 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 bank9) Change of Password10) This module allows customers to change their password.11) Mini Statements12) This module allows customers to view their transaction details.



User Classes and Characteristics

Customers: The normal users will have an account of fixed or savings and should have a minimum balance of 500 Rs. He can transfer funds to another account of the same bank & may view his monthly or annual statements. Industrialists, Entrepreneur, Organizations academicians: These users will have all the three accounts & should have a minimum balance of 20,000 Rs. He can view the statements of his organization or industry.

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 Certified Browsers Supported Browsers

Win 2000, SP4 Internet Explorer 6.x Netscape 6.1, AOL 8.0 and 9.0,

Firefox 1.0

Win XP, SP2

(Recommended)

Internet Explorer 7.0, Netscape

7.2, AOL 8.0 and 9.0

Netscape 6.1 and Firefox 1.0

MAC OS X AOL for OS X and Safari 1.2

Design and Implementation Constraints•Login and password is used for identification of customer’s account and there is no facility for non users to login.•This system works only on a single server.•GUI is only in English



•Limited to HTTP/HTTPS protocols

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.>

Assumptions and Dependencies Following are the assumptions and dependencies which are related to this

online banking project.

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 web-

based so every one will independently contact it.

4) It is will not affect the environment at all.

5) 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

Loan applications and transactions, such as repayments

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...

External Interface Requirements

User Interfaces<Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.>

Hardware Interfaces

Client Side ( IE Along with Printer )

Processor Ram Disc Space

Internet Explorer

6.0

Pentium

II at

500

MHz

64 MB

1 GB

Server Side

Web sphere

application server

V5.0

Pentium III at

1 GHz 512 MB 2 GB



DB2 V8.1

Pentium III at

1 GHz

512 MB

1GB

(Excluding data size)

Software Interfaces

User on Internet : Web Browser, Operating System (any)

Application Server : WAS

Data Base Server : DB2

Network : Internet

Development Tools : 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.

A Web Browser such as IE 6.0 or equivalent.

Other Nonfunctional Requirements

Performance Requirements

System can withstand even though many no. of customers request the desired service. Access is given to only valid users of bank who requires the services such as balance enquiry, update profile, funds transfer, mini statements, and request for stop payments and for cheque book.

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 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 user’s 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.

Software Quality Attributes 1) Conformance to specific standards:

2) Performance constraints: This system must be fit according to the performance wise. It should use less memory and will be easily accessible by the user. Memory management should be done wisely so that none of the memory part goes wasted.3) Hardware limitations: It should be designed in such a way that cheap hardware must be installed to access and use it effectively. It should be platform independent. There should be no hardware limitations. In should be designed to work with the low specification hardware so that it could easily work with the high specification hardware. 4) Maintainable: Each of the modules should be designed in such a way that a new module can easily be integrated with it. 5) Reliable:

6) Testable:

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.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

FAQs:-

1. Explain the need of SRS?



2. Explain SRS of your system?

3. What do you mean by Scope of the system?

4. What are the functional requirements?

5. What are the non-functional requirements?

6. What are the Software Quality Attributes? Explain it in the context of your system?

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?

10. Explain the difference between functional and nonfunctional requirements?


Documents

Assignment 1 SRS Template