Back To My Village SRS

Software Requirements
Specification
for
BACK TO MY VILLAGE
Prepared by MUNA PARIDA
1602081031
Information Technology
Veer Surendra Sai University of Technololgy
Copyright © 2018 by muna parida,. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for Back To My Village Page 1
Table of Contents
Table of Contents...........................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
2. Overall Description..................................................................................................................1
2.1 Product Perspective........................................................................................................................1
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................3
2.5 Design and Implementation Constraints.........................................................................................3
2.6 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................4
3.3 Software Interfaces.........................................................................................................................4
3.4 Communications Interfaces............................................................................................................4
4. System Features.......................................................................................................................4
4.1 Registration.....................................................................................................................................4
4.2 Login..............................................................................................................................................5
4.3 Customized Language....................................................................................................................5
4.4 Viewing Govt. Schemes.................................................................................................................6
4.5 Bill Payments..................................................................................................................................6
4.6 Educational Videos.........................................................................................................................7
4.7 Buy Product....................................................................................................................................7
4.8 Sell Product....................................................................................................................................8
4.9 Update Profile.................................................................................................................................8
4.10 Complain Box.................................................................................................................................9
4.11 Query Platform...............................................................................................................................9
4.12 Scholarship...................................................................................................................................10
4.13 Job Application.............................................................................................................................10
4.14 Bus Timings..................................................................................................................................11
4.15 Book Tickets.................................................................................................................................12
4.16 Search Hospitals...........................................................................................................................12
4.17 Contributions................................................................................................................................13
4.18 Communication Platform..............................................................................................................13
5. Nonfunctional Requirements..................................................................................................14
5.1 Performance Requirements...........................................................................................................14
5.2 Security Requirements..................................................................................................................14
5.3 Availability...................................................................................................................................15
5.4 Reliability.....................................................................................................................................15
5.5 Portability.....................................................................................................................................15
5.6 Usability.......................................................................................................................................16
5.7 Maintainability..............................................................................................................................16
5.8 Integrity........................................................................................................................................16
5.9 Manageability...............................................................................................................................16
5.10 Capability & Scalibilty.................................................................................................................16
1. Introduction
1.1 Purpose
The product concerned here is an online village development & welfare system to let the villagers be
more advanced and to use the various facilities provided by the development group members. The
SRS describes the whole product.
1.2 Document Conventions
The typographical conventions used are:

The headings, subheadings and explanations are in bold with ‘Times New Roman’ font and
with font sizes 18,14 and 12 respectively.
1.3 Intended Audience and Reading Suggestions
The document is basically intended for developers, project managers, testers, administrators and
documentation writers. The SRS summarizes functions, software, hardware requirements,
functional and nonfunctional requirements of the product. This document also establishes on need
for such a system and follow up the pros and cons with the system.
1.4 Product Scope
The project is aimed at developing an Online Village Development system which will enable
villagers to use the advanced technology to improve the facilities being provided. Back To My
Village is being designed to help, organize and manage villager’s activities and to reduce time in
many activities like paying various bills, searching hospitals etc. To improve education standards
,system provides lecture videos and improved farming techniques videos for students and farmers
respectively.
The system should have a login. The software should include various govt. schemes and their rules
& regulations. The system should be accessible to the group members, Admin and villagers. For
using the software, the member has to first sign up/register. He/she can choose the language
preferable to them.
2. Overall Description
2.1 Product Perspective
As the current facilities that are being provided is not properly and also is not sufficient and
efficient, it is a good time to propose a new computer based system. The system can fulfill many
requirements of the villagers easily. The main objective of developing this project is to reduce the
effort required by the villagers to get facilities and that too not proper and to get benefit from the
latest technology. This is a new, selfcontained product which has been developed from the scratch.
The online development system includes the features such as it provides a reliable system to the
users, complaint registration , feedback, lecture videos, transportation details and bus bookings
,business platform and more. The SRS covers the entire project and had no sub systems and requires
no interfacing.
2.2 Product Functions
The major functions of Back To My Village are:
 To provide business platform to farmers
 To provide lecture videos to students
 To provide improved farming techniques to farmers via videos
 To provide a complaint platform
 To provide communication platform to development group members
 To provide bus timings and bus bookings to travelers
 To provide available jobs and scholarships list for students
 To provide query platform to all villagers
 To provide list of various govt. schemes
 To provide searching of nearby hospitals
 To provide facility to pay various bills online
2.3 User Classes and Characteristics
The various users or actors who will be involved in the system are:
 Administrator: Administrator will have the complete control over the system. They will
have the technical access to the system. The role of the administrator involves a great deal of
multitasking like track, compile, and analyze website data usage. He is responsible for
providing services to the villagers.
 Farmers: Farmers can use the system to view farming videos and they can also buy farming
equipments and sell their farming product using this system.
 Students: Students can use this system to view lecture videos, buy study materials and as
well as to apply various scholarships and jobs.
 Travelers: Travelers can easily search for bus timings and then can also book tickets using
the system
 Donors: Donors can see their contributions and credit points on the system.
 Seller: Seller can upload the details and price of his product to sell it using the system.
 Development Group Members: Group members can communicate using the system
among themselves for the improvisation in the village’s development.
 Patients: Patients can search for nearby hospitals easily.
2.4 Operating Environment
The software is designed to operate in the end users environment basically, considering all the
functions that it should efficiently perform to meet the requirements of better effective management.
For this, the software requirements should include a compatible operating system, available disk to
install all required software, database software to maintain all the records, fast and stable network
connection. The software will be a web resource and product. Since it is a website, so it needs a
working internet connection, any web browser supporting the HTML5 format and XHTML and
JavaScript, current version of Adobe flash player and the software should be protected from any
malicious item so that the antivirus installed will not block the site on any system. The internal CPU
specifications should be at the par with the current standard specs so that there would never be a
case of system lagging or system crashing while in use. Updated version of the software need to be
installed and manual regular updates need to be done by the admin.
2.5 Design and Implementation Constraints
The developers need to keep in mind that the End users database linked to the BTMV need to be
accessible all the times and should never lead to any loss of information. The software developed
should be such that it should take minimum amount of load time .The capital investment over the
whole setup of the cloud based database along with the required number of system is limited and thus
should be met with the proposed budget. It would be better to implement it using bootstrap so as to
accommodate in mobile devices.
2.6 Assumptions and Dependencies
The software works best on the assumption that the latest versions of web browsers will be used to
access the website and the servers are to be kept up and running at all times so that link to site is
never broken and it should be accessible for 24*7. Further the site depends on reliability and safety
factors which will be further described in nonfunctional requirements. It is needed to think about a
future way of making the system more efficient and easily accessible.
3. External Interface Requirements
3.1 User Interfaces
There is a one login section for registered members. For new users there is a signup/registration
option. Then in the homepage there are different options and some pictures of ongoing
developments. There is a section where we can get ask questions. On the top there is notification
icon. Also at the bottom there are links to Blogs, and social media. Footer is divided into two parts
the bottom left is for Contact us section and on right there is help section and important links.
3.2 Hardware Interfaces
Minimum requirement for client is Internet Explorer-6 with Intel Pentium or AMD processor and 128
megabyte RAM also disk space of 100 megabyte, where as minimum requirement for server is Intel
Pentium or AMD processor with 1GB RAM and 500 megabyte disk space. The supported device
will be personal computers, android phones, tablets etc.
3.3 Software Interfaces
The website will be capable of running on Internet Explorer-6, Google Chrome or in any higher
versions of these. It is also meant for android users through the targeted devices like tablets and
smart phones. It uses web browser supporting HTML5, XHTML, JavaScript and Adobe flash player.
3.4 Communications Interfaces
Client on internet will be using HTTP/HTTPS/FTP protocols. This system relies on single server and
all the databases are stored in that particular server.
4. System Features
The system features would simply be stated in the form of Functional Requirements. This basically
includes the user and the requirements for their authentication followed by the level of abstraction
that they are provided with while displaying the different segments of BTMV.
4.1 Registration
4.1.1 Description and Priority
Any villager who wishes to avail facilities provided by development group has to
register with BTMV. The priority for this functionality is high.
4.1.2 Stimulus/Response Sequences
The user needs to enter his/her full name, DOB, mobile no., email and a new
password. If the provided information is correct, then the user will be successfully
registered with BTMV, otherwise the user has to re-enter the details in correct format.
4.1.3 Functional Requirements
INPUT: Full Name, DOB, Mobile No., E-Mail and new password.
OUTPUT: Confirmation message with User ID and password.
4.2 Login
Every user has to login to access their respective accounts. The priority of this
functionality is high.
The user needs to enter his/her User ID and password. If the provided information is
correct, then the user will be successfully login with BTMV, otherwise the user have to
re-enter the valid details.
REQ1: Login
INPUT: User ID, Password, Captcha Code.
OUTPUT: Home Page will open if correct credentials are given else a retry
message.
REQ2: Reset Password
INPUT: Select Reset Password.
OUTPUT: Verification page and OTP message.
REQ3: Verification
INPUT: Enter OTP.
OUTPUT: If OTP is correct then reset password page else a retry message.

REQ4: Change Password
INPUT: Enter New Password.
OUTPUT: Success message.
4.3 Customized Language
To use BTMV. The priority of this functionality is medium.
The user needs to select their preferred language. After selecting the language the user
can view the system in their preferred language.
REQ1: Language Customization
INPUT: Select Language
OUTPUT: Web Application text will be converted into the selected language.
4.4 Viewing Govt. Schemes & Rules
Every user who wants to know about various government schemes & their rules and
regulations can view it on BTMV. The priority of this functionality is low.
The user needs to select ‘Govt. Schemes’ tab and then a page will appear with all govt.
schemes and their respective rules.
REQ1: Govt. Schemes List
INPUT: Click on ‘Govt. Schemes’.
OUTPUT: All current govt. schemes.
4.5 Payment Of Bills
Every user has who wants to pay different bills online can pay using BTMV. The
priority of this functionality is medium.
The user needs to select the service for which he/she wants to pay the bill and also the
amount and the payment option through which he/she wants to pay the bill. If the
entered details are valid then a payment success message will be shown with the online
receipt, otherwise a payment error message will be shown to the user.
REQ1: Select Bill
INPUT: Select corresponding bill i.e., phone bill, electricity bill, water bill.
OUTPUT: Directed to payment page.
REQ2: Payment Option
INPUT: Select corresponding payment option.
OUTPUT: Directed to Confirmation page.
REQ3: Confirm Payment
INPUT: Click on PAY BILL.
OUTPUT: Online Money Receipt and Success message.
4.6 Training & Educational Videos
To know efficient farming techniques, farmers can view farming videos and students
can view lecture videos. The priority of this functionality is medium.
The user needs to click on the ‘Videos’ tab and then have to choose a video to watch.
After which the user can watch the corresponding video.
REQ1: Video Stream
INPUT: Select the desired video.
OUTPUT: Video Streaming.
4.7 Buy Product
Users can buy product at cheaper rates through BTMV. The priority of this
functionality is medium.
The user needs to choose a product to buy and also a payment method to purchase it.
If the provided information is correct then a product receipt will be generated
otherwise the corresponding error message must be shown.
REQ1: Select Product
INPUT: Choose a product.
OUTPUT: Re-directed to billing page.
REQ2: Billing
INPUT: Name, Address, Mobile No.
OUTPUT: Re-directed to payment page.
INPUT; Click on buy.
OUTPUT: Successful buy message with tracking ID.
4.8 Sell Product
Farmers or any seller who wants to sell their product can sell it using BTMV. The
priority of this functionality is medium.
The user needs to click on Add Product and then enter the product details and price.
After successful upload of product, a success message will be generated otherwise the
corresponding error message will be shown.
REQ1: Add Product
INPUT: Click on ADD PRODUCT.
OUTPUT: Re-directed to pricing page.
REQ2: Upload
INPUT: Product details and price.
OUTPUT: Re-directed to confirmation page.
REQ3: Confirmation
INPUT: Click on ‘CONFIRM’.
OUTPUT: Success Message
4.9 Update Profile
Users can update their profile any time they want by selecting update profile. The
priority of this functionality is low.
The user needs to select ‘Update Profile’ tab and then can update the desired
information he/she wants. After successful completion, updated profile will be visible
to the user otherwise the corresponding error message must be shown.
REQ1: Update
INPUT: Update the corresponding details.
OUTPUT: Success profile update message.
4.10 Complain Box
Users can register complain about activities which are not done properly through
complain box. The priority of this functionality is high.
The user needs to click on the ‘Complain’ tab and then enter the complaint. After
successful completion, a complaint no. will be generated otherwise if something went
wrong, a corresponding error message will be shown..
REQ1: Register Complain
INPUT: Description of complain.
OUTPUT: Receiving confirmation message and complain number.
REQ2: Complain Tracking
INPUT: Enter Complain number.
OUTPUT: Status of complain
4.11 Query Platform
Users can ask their queries on query platform of BTMV. The priority of this
The user needs to enter his/her query on the site by clicking the ‘Query’ tab and after
successful completion a pop message will be generated stating the successful
submission of the query otherwise if something went wrong, a corresponding error

message will be shown.
REQ1: Query
INPUT: Enter query.
OUTPUT: Thank you message and response of query through message or

call.
4.12 Scholarship
Students can apply for different scholarships by checking their respective eligibility
criteria. The priority of this functionality is medium.
The user needs to click on the ‘View Scholarship’ section and then can view the
available scholarships and choose to apply. After successful submission, a success
message will be generated otherwise if something went wrong, a corresponding error
REQ1: Scholarship List
INPUT: Select view scholarships.
OUTPUT: Available scholarship list.
REQ2 : Select scholarship
INPUT: Choose the scholarship.
OUTPUT: Directed to applying page.
REQ3: Apply Scholarship
INPUT: Required details for corresponding scholarship.
4.13 Job Application.
Those who wants to apply for jobs can directly apply through BTMV. The priority of
this functionality is medium.
The user needs to click on the ‘View Jobs’ section and then can view the available jobs
and choose to apply. After successful submission, a success message will be generated
otherwise if something went wrong, a corresponding error message will be shown.
REQ1: Jobs List
INPUT: Select list of jobs.
OUTPUT: List of available jobs.
REQ2: Select job
INPUT: Choose job you want to apply.
OUTPUT: Direct to application page.
REQ3: Apply job.
INPUT: Enter required details for job.

.
OUTPUT: Successful submission message.
4.14 Bus Timings
Travelers can use BTMV to check bus timings to plan their journey ahead. The priority
of this functionality is low.
The user needs to click on the ‘Bus Timings’ tab and then the user can choose the bus
to view the bus. The user can see the route and timing for the corresponding bus. If
anything went wrong, a corresponding error message must be shown.
REQ1: Select Transportation
INPUT: Select bus.
OUTPUT: Directed to corresponding transportation list.
REQ2: Check timing.
INPUT: Bus number.
OUTPUT: Bus timing.
4.15 Book Tickets
Users can book tickets online through BTMV. The priority of this functionality is
medium.
The user needs to click on the ‘Book Ticket’ tab and then have to enter the bus no.,
date, source & destination. After which available seats will be shown to the user. To
book the ticket they need to enter name, address and age of the passenger. After
successful booking, a confirmation message with ticket details will be sent to the sent
to the passenger. If anything goes wrong, a corresponding error message must be
shown.
REQ1: Enter bus number
INPUT: Bus number in which want to book seat.
OUTPUT: Direct to availability page.
REQ2: Journey Details
INPUT: If seats available enter journey date and number of seats.
OUTPUT: Directed to payment page.
4.16 Search Hospitals
Patients can easily search nearby hospitals using BTMV. The priority of this
The user needs to click on the ‘Search Hospitals’ tab and then the list of all nearby
hospitals will be shown to the user. If something goes wrong, a corresponding error
REQ1: Search
INPUT: Select ‘VIEW HOSPITALS’.
OUTPUT: Page containing all nearby hospitals and their details.
4.17 Contributions
An user can contribute and can view his/her all contributions till date on BTMV. The
priority of this functionality is high.
The user needs to click on the ‘Contributions’ tab and then can contribute an amount
by entering the contribution amount and the payment mode. After successful
transaction a confirmation message must be sent to the registered mobile no. of the
user. If something goes wrong, a corresponding error message will be shown.
REQ1: View Contribution
INPUT: Select ‘Contributions’ tab.
OUTPUT: Re-directed to the ‘Contributions’ page.
REQ2: Contribution Details
INPUT: Contribution Amount.
OUTPUT: Re-directed to the ‘Payment’ page.
REQ4: Confirmation
4.18 Communication Platform
Development group members can communicate among each other using the
communication platform provided by BTMV. The priority of this functionality is high.
The user needs to click on the ‘CHAT’ tab and choose the member(s) to chat with and
also the means of communication. After which the user can easily communicate with
the desired person. If something goes wrong, a corresponding error message will be
shown.
REQ1: Select Member(s)
INPUT: Click on member(s) to communicate.
OUTPUT: Re-directed to choose methods of communication
REQ2: Communication Method
INPUT: Click on messaging, voice chat or video chat.
OUTPUT: Communication with corresponding method.
5. Nonfunctional Requirements
5.1 Performance Requirements
 System should open within 5 seconds.

 Any key functions i.e., payments of bills, buying products , watching lecture videos etc,
must be processed within 20 seconds.
 The application should be able to support 500 concurrent users without an performance
degradation.
 The system may be slowed down on heavy loads to ensure service for everybody. It may b
happen that certain functionality may be unavailable during heavy server load.
 System must have a 100% uptime, unless during schedule maintenance period, which will
be relayed to the users of the site well in advance .
5.2 Security Requirements
 Account login is made secured by invoking captcha code.
 Any password in the database should not be stored in the plain text.....a hashed value must
be stored.
 Blocking of account if wrong password is typed 3 times. To recover the account user needs
to enter the required OTP which is send to the registered mobile number.

 During the payment or recovering password, OTP must be send within 30 seconds.
 If any transaction is not completed within 15 minutes user must be automatically logged out.
 The system must automatically be logged out of all accounts after a period of inactivity.
 The system should not leave any cookies on customers computer containing the user’s
password.
 The system’s backend server shall only be accessible to authenticated administrators.
 Sensitive data will be encrypted before being sent over an insecure connection like internet.
5.3 Availability
 The system should remain accessible 24x7 by every user.
 The user can access it using below mentioned or of above version of web browsers: Firefox
5.0.1, Internet Explorer 8.0, Opera 10.1, Opera Mini 9.2.1, U C browser 10.0.1 etc., only
restricted by the downtime of the server on which system runs.
 In case of server downtime or any technical failure, a replacement page must be shown.
5.4 Reliability
 Main pillar for reliability is the back up of data base which maintained and updated in every 7
days to reflect the most recent changes.
 In case of failure that leads system outrage, the recovery should not take more than 2 hours.
5.5 Portability
 The system should be portable enough to be moved to various operating environments i.e.,
Windows, MaC, Linux, Android etc.
 The system should be portable enough to be moved over to a new server with a minimal
downtime if required.
5.6 Usability
 The user interface of the system should be very user friendly.
 It should take more than 120 seconds for a new user to register to a new account.
5.7 Maintainability
 The system should be developed in such a way that changes can be made easily (using
modular division or decomposition ), whether for a bug fixes or to add new functionalities.
5.8 Integrity
 The system should be able to protect and preserve transactions.
5.9 Manageability
 The system should be developed in such a way that it can be easily reused, deployed and
tested.
5.10 Capability and Scalability
 Throughput: System needs to handle minimum of 200 transactions a day.
 The system must have at least 10 GB storage per user.

Back To My Village SRS

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Back To My Village SRS

Hochgeladen von

Copyright:

Verfügbare Formate

Software Requirements

Prepared by MUNA PARIDA

Veer Surendra Sai University of Technololgy

The typographical conventions used are:

OUTPUT: Confirmation message with User ID and password.

INPUT: User ID, Password, Captcha Code.

INPUT: Select Language

INPUT: Click on ‘Govt. Schemes’.

OUTPUT: All current govt. schemes.

OUTPUT: Directed to payment page.

REQ2: Payment Option

INPUT: Select corresponding payment option.

OUTPUT: Directed to Confirmation page.

REQ3: Confirm Payment

INPUT: Click on PAY BILL.

OUTPUT: Online Money Receipt and Success message.

INPUT: Select the desired video.

OUTPUT: Video Streaming.

INPUT: Choose a product.

OUTPUT: Re-directed to billing page.

INPUT: Name, Address, Mobile No.

OUTPUT: Re-directed to payment page.

REQ3: Payment Option

REQ4: Confirm Payment

INPUT; Click on buy.

OUTPUT: Successful buy message with tracking ID.

INPUT: Click on ADD PRODUCT.

OUTPUT: Re-directed to pricing page.

INPUT: Product details and price.

OUTPUT: Re-directed to confirmation page.

INPUT: Click on ‘CONFIRM’.

OUTPUT: Success Message

INPUT: Update the corresponding details.

OUTPUT: Success profile update message.

INPUT: Description of complain.

OUTPUT: Receiving confirmation message and complain number.

REQ2: Complain Tracking

INPUT: Enter Complain number.

OUTPUT: Status of complain

submission of the query otherwise if something went wrong, a corresponding error

INPUT: Enter query.

OUTPUT: Thank you message and response of query through message or

INPUT: Select view scholarships.

OUTPUT: Available scholarship list.

REQ2 : Select scholarship

INPUT: Select list of jobs.

OUTPUT: List of available jobs.

REQ2: Select job

INPUT: Choose job you want to apply.

OUTPUT: Direct to application page.

REQ3: Apply job.

INPUT: Enter required details for job.

INPUT: Select bus.

OUTPUT: Directed to corresponding transportation list.

REQ2: Check timing.

INPUT: Bus number.

OUTPUT: Bus timing.

INPUT: Bus number in which want to book seat.

OUTPUT: Direct to availability page.

REQ2: Journey Details

INPUT: If seats available enter journey date and number of seats.

OUTPUT: Directed to payment page.

INPUT: Select ‘VIEW HOSPITALS’.