03-01-2013, 04:51 PM
Software Requirement Specification Software Requirement Specification Software Requir
Software Requirement Specification.pdf (Size: 925.9 KB / Downloads: 60)
Introduction:
1.1 Purpose:
My Bill Buddy is intended for an easy, secure, instant and cashless transfer of small money amount to friends through mobile phones. This document is meant to delineate the features of My Bill Buddy, so as to serve as a guide to the developers on one hand and a software validation document for the prospective client on the other.
1.2 Scope:
We describe what features are in the scope of the software and what are not in the scope of the software to be developed.
In Scope:
a. Registration through IIIT-D mail account and phone number
b. User authentication.
c. Transfer of money through phone applet.
d. Sending encrypted SMS to server when a person has to pay to the other, with the receiver’s number and amount.
e. Sending notifications from server to phone via SMS whenever there is a transaction.
f. Sending monthly account balance notification via SMS.
Out of Scope:
a. Trustworthy bank body to take care of physical money transactions.
b. To make sure the person who has to pay will surely pay the money through the application.
1.3 Definitions, Acronyms and Abbreviations
Acronyms and Abbreviations:
A) SRS: Software Requirements Specification
B) SMS: Short Messaging Service
Definitions
A) User – It refers to the person who will register and use the phone application.
B) Server – It refers to the system which has complete database of all the transactions and users and also has a SMS gateway attached to send and receive SMS.
A) Bank – It refers to the secure body which takes care of physical transactions of money and updating ofs database whenever there is such transfer.
Overview:
The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed. Section 3 gives specific requirements which
SRS – MY BILL BUDDY Page 4
the software is expected to deliver. Functional requirements are given by various use cases. Some performance requirements and design constraints are also given. Section 4 gives some possible future extensions of the system.
Requirements
Essential Requirements:
A) A Trustworthy Bank: A trustworthy body to act as a bank is a primary requirement for our project. For now we are implementing this project inside IIIT-D so the body needs to be recognized by the institute and the students should be able to trust it to a level that they can deposit their money here.
B) A Dedicate GSM Device: A GSM receiver is needed at server to continuously listen for the incoming messages about transactions and account related enquiries.
C) SMS system on Device: A SMS sending and receiving system is must at the user device. The applet will use this mode of communication for transaction requests and account enquiries.
D) Java on Phone: The phone device should also be Java Enabled.
E) Dedicated Server: A dedicated server at bank to record, process and manage the money and transactions.
2.2 Desirable Requirements:
A) Notification via E-Mail: Notification of transactions can be sent via E-mail as well as SMS.
B) Lending money: The user can lend money to his friend in emergency.
C) Cloud Environment: Our server can be put on cloud and used as a Web App.