SOFTWARE REQUIREMENTS SPECIFICATION- MOBILE BANK

The output of requirement analysis phase is SRS, which is clear and concise specification of detailed functional description, indication of performance requirements and design constraints, appropriate validation criteria and  other data pertinent to requirements.

1. Scope:

                       To provide information available on a web service to all the mobile users.

      2. Overview:

            The project is designed & coded in such a way that in any other modifications that are needed in future can easily implemented with out effecting the functionality of the system.

Overall Description

1        Product Perspective: 

                  The objective of the online mobile Banking service is to provide a great

Communication between the mobile users

Product Functions:

                  The creation of a web-service which act as a mediator in between mobile users and database.

3 User Characteristics:

This is assisted by mobile application that allows mobile users to communicate with web-service to get the information available on a web-service and also allow user to communicate with banks via mobile services

2.4.PROJECT PLANNING:

It was decided to use good Software engineering principals in the development of the system aiming to expand their operations in the near future. So the following Project Plan was drawn up:

1. The Analysts will interact with the current manual system users to get the Requirements. As a part of this the Requirements Specification Document will be created.

2. The requirements Specifications document will contain the Analysis & Design of the system.

3. The Analysis, Design, Implementation & testing of the System will be followed to produce an incremental cycle, which will deliver milestones like the Requirements Specification Document etc., at the end of each of the iterations, Phases or cycles.

4. The Architecture & Technologies will be decided as a part of the Analysis of the requirements.

5. Once the Design is ready the Implementation & Testing strategy of the system will commence. Each will be independent of the other. The implementation of the system itself will be broken down into sub-systems following the Software Engineering principles for the development of robust software.

6. Once the implementation is ready, the System testing will take place. If the system is judged to be stable then Acceptance testing by the Users will take place & once the Users are satisfied the System will be rolled out to the Users & they will be trained on how to use it for an initial period.