SOFTWARE REQUIREMENT

SPECIFICATION
NGO MANAGEMENT SYSTEM
/*PROJECT_NAME*/

17/06/2019

/*….
….
TEAM_MEMBERS
…*/

Page 1 of 17
 TABLE OF CONTENTS
Table of contents
Revision History ……………………………………………………………………………. 2

1. Introduction
1.1 Purpose ………………………………………………………………………… 3
1.2 Document Conventions ………………………………………………………... 3
1.3 Intended audience and Reading Suggestions ………………………………….. 3
1.4 Project Scope …………………………………………………………………... 3
1.5 References ……………………………………………………………………... 4

2. Overall Description
2.1 Product Perspective …………………………………………………………… 4
2.2 Product Features ………………………………………………………………. 4
2.3 User Classes and Characteristics ……………………………………………… 4
2.4 Operating Environment ……………………………………………………….. 4
2.5 Design and implementation constraints ………………………………………. 5
2.6 User Documentations …………………………………………………………. 5
2.7 Assumptions and Dependencies ………………………………………………. 5

3. System Features
3.1 System feature 1 ………………………………………………………………. 5
3.2 System feature 2(and so on) …………………………………………………. 5-6

4. External Interface Requirements

4.1 User Interface ………………………………………………………………… 6
4.2 Hardware Interface …………………………………………………………... 6-7
4.3 Software Interface …………………………………………………………….. 7
4.4 Communications Interface ……………………………………………………. 7

5. Other Nonfunctional Requirements

5.1 Performance Requirements ……………………………………………………. 7
5.2 Safety Requirements …………………………………………………………… 8
5.3 Security Requirements …………………………………………………………. 8
5.4 Software Quality Attributes ……………………………………………………. 8

6. Other Requirements …………………………………………………….... 8

Appendix A: Glossary ……………………………………………………………………. 9
Appendix B: Analysis Models ………………………………………………………… 10-16
Appendix c: Issue list …………………………………………………………………….. 17

Page 2 of 17
REVISION HISTORY
Name Date Reason For Changes Version

1. INTRODUCTION
Page 3 of 17
1.1 Purpose
The purpose of this document is to give a detailed and complete description of the
requirements for the NGO Management Software (NMS) software. It will illustrate the
purpose and complete declaration for the development of system. It will explain system
constraints, interface and interactions with other external applications.
It includes the functions and features of the software. Moreover, it gives an overview of the
design implementation of the software. It describes the projects target audience and its user
interface.

1.2 Document Conventions

There are lots of abstraction to represent in a more convenient way the objects and their
behavior on the system. Every requirement statement is assumed to have its own priority as to
define in most appropriate way the system, where it is needed, and serve only for better
understanding of the deployment. Major headings are in bold 16pt font, and concurrent
headings in 14pt font, and the content under these headings in 12pt font.

1.3 Intended Audience and Reading Suggestions

The expected audience consists of the Donors and the Manager (Admin) at the NGO and the
volunteers.
NMS : NGO Management Software
Donor : The person who has pledged to help NGO financially.
Manager (Admin) : The person who supervises the workings within the NGO and contacts
volunteers who are willing to support the NGO.
Volunteer : Volunteer/Helpers are the persons who are willing to help the NGO in there
events and campaigns.

1.4 Project Scope

The NMS is designed to provide NGO a system to help poor students. Donor
can register and can enter the amount they intend to donate. It allows Donor to provide
donations to the NGO, who in turn provide teaching and other facilities to the students
in return.
Admin can supervise staff, faculty, volunteers and events organized by NGO. The
Software is user-friendly and easy to use.

1.5 References

Page 4 of 17
1.5.1 www.wikipedia.com
1.5.2 www.krazyTech.com
1.5.3 www.Github.com

2. OVERALL DESCRIPTION
Page 5 of 17
The NMS provides the NGO with a system for its management. The manger at the
NGO keeps record of students and faculty at its facility and updates their various info.
Further it helps manage funds collected and granted by the NGO.
The pledged donors can donate by registering and donating the amount of money or by
providing other helps at the events and camp set up by NGO.
2.1 Product Perspective
This software is a new, self-contained product which provides the NGO a system for
its management. The NMS is developed as an extension of the work previously done
manually and/or on paper. All the data including the information of donors, students,
volunteers, etc. is stored in databases.
This software makes the work of both Donors/volunteers and manager easy.

2.2 Product Features

 The main aim of this software is to provide the NGO a system for its management.
Records can be maintained as a soft copy.
 Lesser manual work will be required as this is convenient, efficient and less error
prone.
 All of the calculations and bookkeeping are done automatically.
 The interface is obvious enough to use without any experience.
 Promotions and event activities motivates donor to volunteer and provide help to
NGO.

2.3 User Classes and Characteristics

2.3.1 Donor
 A Donor is a verified user of website who is intended to provide help to NGO by
pledging money and change their frequency of donations.
 A Donor can also search events organized by NGO and take part in them.
 They can interact with NGO via this product.

2.3.2 Volunteer
 These are the person who are willing to work with NGO and provide their help.
 They can search the events and works of the NGO and register themselves through the
website.

2.3.3 Manager
The person responsible for running the NGO. There might be more than one managers
managing the NGO. Each manager would be having his own account. They can all easily
create an account and then login and access all the functionalities available to the Manager
like supervising granted financial account and exclusively add/remove(update)
volunteers.
2.4 Operating Environment
Page 6 of 17
  Hardware: Any Personal Workstations with internet connection will do.
 Operating System: Windows XP and above.
 Standard: The software will be developed in Java. The database Management task is
done with the help of JDBC
 Libraries: JRE (Java Runtime Environment) needs to present on the workstation.

2.5 Design and Implementation Constraints

The user interface shall be implemented using any tool or software package like Java
JSP, Net-Beans etc. on following languages that are the primary tools which are to be
used by the developers are HTML, CSS and JavaScript.
 The web portal requires an internet connection so Donor registration and donations
cannot be done offline.
 The software will be constrained with the capacity of the database.
 Java should be the language preferred in case of updating the software.

2.6 User Documentation

 UD-1: The system will provide an online user manual in HTML that describes the
functionality and options available to the user.
 UD-2: The system will provide a hard copy of the user manual, which is identical to
the manual outlined in UD-1.

2.7 Assumptions and Dependencies

 Each NGO member who is a part of the NGO management is expected to have an
account of his own.
 The software assumes that list of donors who have pledged support is available to the
software.
 The software assumes that estimate for amount of money needed for books, clothes,
etc. for students is available to the software as in database records.
 We assume that website will open on system which support Html and css.

3. System Features
Using the actor list we begin the analysis of the donor-server features that’s take place
in section and then for each tool that is being reported so far in section B we analysis
its requirements basis in the data base editor program.

3.1 SIGN UP:

The Donor can create account for the fist time by signing up and providing personal
details and the registration will be confirmed.

3.2 LOG IN:

Page 7 of 17
The donor will be able to sign in to the system and can use the features by accessing the
website.
3.3 FORGOT PASSWORD:
The users who don’t remember their password can get a chance to get a new password by the
help of security question or OTP.
3.4 SEARCHING:
The users can search about the events organized by the NGO, they can also search the blogs
maintained.
3.5 DONATE:
The Donor can pledge donation after logging in to his/her account, and can view previous
donation history.
3.6 Volunteer:
The Donor can volunteer to the NGO by registering himself.
3.7 Enquiry:
The Donor/volunteer can enquire about his/her query by submitting the enquiry form online
and the managers will act upon it precisely.
3.8 Contact Us:
Used to provide information so that communication between user and admin could be
maintained.
3.9 About Us:
Using this the NGO will provide inside view of how the NGO works.
3.10 Reviews:
Using this module the user can give its opinion and feedback to NGO.

4. External Interface Requirements

This section provides a detailed description of all inputs into and outputs from the system. It
gives a description of the software interfaces and provides basic prototypes of the user
interface.

4.1 User Interface

UI-1: Signup and login page.
UI-2: The website should provide details of the events precisely.
UI-3: Every event can be clicked by a mouse in order to view details of events
UI-4: All modifications to the database will be done through a keyboard.
UI-5: Application will be accessed through a browser interface.

Page 8 of 17
UI-6: After every donation the system makes the donation report as portable document
format(pdf). And sent to Donors email address.
UI-7 The website will provide a registration page to register the Donor as a volunteer.

4.2 Hardware Interface

The System must run over the internet, all the hardware shall require to connect internet will
be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet Cross-
Cable and WIFI. The System require Database also for the store of any transaction of the
system like Derby etc. System also require DNS for the naming on the internet. At the last
user need web browser for interacting with the system.

4.3 Software Interface

 The system is on server so it requires any scripting language like JavaScript etc.
 The system require Database also for storing any transaction of the system like Derby
etc.
 System also require server on the internet like Glass fish server.
 System also require DNS for the naming on the internet.
 At the last, user needs web browser for interacting with the system.

4.4 Communications Interface

The NGO Management System shall use the HTTPS protocol for communication over the
Internet and for the Intranet communication will be through TCP/IP protocol suite. The user
must have SSL certificate licensing registered web browser.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
 You will be sign in with in 26 sec.
 If anybody make new account then he will receive confirmation email within 6
minutes.
 Search results shown within 15 sec.
 Web support 100 Donors logged at the same time.
 The confirmation email for successful donation will be sent within 30 sec.
 The response to enquiry will be done as soon as possible.

5.2 Safety Requirements

 We will try the best to make product safe.

 System would be protected by a password.
 There is no risk of mismanagement of data.
 The system makes the overall project management much easier and flexible.

Page 9 of 17
5.3 Security Requirements
 The application assumes that the user or customer is allowed to access his/her account
by login ID and password necessary to verify the identity.

 Modifications for the database shall be synchronized by the administrator.

 The system shall not leave any cookies on the customer’s computer containing the
user’s password or confidential information.

5.4 Software Quality Attributes

The software quality attributes are the first priority of our project. Some of them are:
5.4.1 Reliability-
The system provides storage of all databases on redundant computers with automatic
switchover. The reliability of overall program depends on the reliability of the separate
components.

5.4.2 Maintainability-
The software design is being done with modularity in mind so that the maintainability can be
done efficiently. In case of failure, a reinitialization of the program will be done.

5.4.3 Reusability –
The coding part can be use anywhere, anytime and produces simple and independent core
modules that can be reused.

5.4.4 Availability-
The system shall be available all the time with enormous speed and better utilization of the
time.

6. Other Requirements
6.1 Hardware: Personal computer
6.2 Operating System: Windows or Linux
6.3 Internet Connection: Any suitable connection.
6.4 Code Standard: Coding is done in Netbeans.
6.5 Performance: The software should function correctly always.

Page 10 of 17
Appendix A: Glossary

SRS Software Requirement Specification

Manager
It refers to the people who will supervise the
NGO management and its facilities.
Pledging Donor It is the name given to the donor who
provide financial donations to the NGO.

Appendix B: Analysis Models

Page 11 of 17
ERD

0 level DFD

Page 12 of 17
Page 13 of 17
1 Level DFD

Page 14 of 17
2 Level DFD
2nd Level DFD for login of Donor/volunteer:

Page 15 of 17
2nd Level DFD for login of Admin

Page 16 of 17
2nd level DFD for forgot password:

2nd level DFD for Search Event:

Page 17 of 17