Académique Documents
Professionnel Documents
Culture Documents
Software Requirement
Speci cation Document
Contents
1
Introduction
2
1.1
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.2
Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.3
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
Overall Description
2
2.1
Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2.2
Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
2.3
2.4
Operating Environment . . . . . . . . . . . . . . . . . . . . . . . .
4
2.5
Design and implementation constraints . . . . . . . . . . . . . . . .
4
2.6
Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . .
4
3
Functional Requirements
4
3.1
Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
3.2
Speci c Requirements . . . . . . . . . . . . . . . . . . . . . . . . .
5
3.2.1
User Class -Manager . . . . . . . . . . . . . . . . . . . . .
5
3.2.2
User Class - Donor . . . . . . . . . . . . . . . . . . . . . .
6
Introduction
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 ex-plain
system constraints, interface and interactions with other external applications.
Project Scope
NMS would help increase productivity of the NGO by reducing the time required
in the operations of the NGO. It will also increase the accuracy of the work done.
References
[1] IEEE Software Engineering Standards Committee, IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Speci cations, October 20, 1998.
Overview
Overall Description
Product Perspective
The origin of this problem is the need of automating and computerizing the opera-tions
of a NGO.All the data including the information of donors,students,volunteers etc is
stored in database. The user interface helps the management to extract infor-mation
from the database.The software takes care of the communications between
the database and the user interface.The software also automates various
operations of the NGO.The web portal allows new donors to register and view
the activities of the NGO.
Since this is a data-centric product it will need somewhere to store the data, a
database will thus be used.
Product Features
Get records of students who have sought the NGO's help Get estimate of funds
required for the coming year.
Choose limited number of students in case of insu cent funds. Display records of
donors who have pledged to help the NGO Also provide an option of contacting
any particular donor
Maintain the data of various donations to the NGO Keep a record of all expenditure in
the present year
Contain information related to the activitiex of the NGO Have an option for
users to register as donors
There is only one type of user who interacts with the software :
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.
The users who use the internet portal are Donors and other users who want
to learn about the NGO.
Operating Environment
The information of all users and statistics related to the NGO must be stored in
a database that is accessible by the Manager.
The data is stored in a single database so its prone to loss due to digital and
physical calamities
The software will be constrained by the capacity of the database . MS SQL Server will
be used as SQL engine and database.
Each NGO member who is a part of the NGO management is expected to have
an account of his own.
The software assumes that estimate for amount of money needed for
books,dress etc for each class is available to the software.
The software assumes that list of donors who have pledged support is
available to the software.
To choose limited number of students we use a metric which gives girls and
students with low parental income.
Functional Requirements
Use Case Diagram
Speci c Requirements
Register:
{ Input :
{ Output:
{ Process:
The management of the NGO has a secret code.An account can be created
only if the person has the secret code.The NGO management can provide the
codes to all the people in the Management who need to have an account.
{ Output:
The Manager gets the total amount of funds the NGO would require to
continue its operation in the coming year.
{ Process:
The NGO has an estimate of the amount of money needed for the books,
dress, fees for di erent classes. This estimate data stored in the database is
accessed to nd out total money that would be needed for each stu-dent and
the total cost of funding all students is determined. Money required for other
things is further added and the total funds required for continuing operations
is thus obtained
{ Output:
The Manager gets a list of donors who can contribute this year and the
amount they are ready to contribute
{ Process:
The Donor list is traversed and those donors who havent contributed in the
last year their pledged amount are added to the list.This list is nall returned.
Get list of limited students whom NGO would continue to support in case f
insu cient funds:
{ Input:
{ Process:
The list of all students is traversed.A custom score is given to each stu-dent.
Custom Score is Initially set equal to the students performance.If the student
is a girl 5% is added to the custom score.Also if the income of parents of a
student is below Rs 50,000 per annum 5% is again added to his custom
store. Then the list of students is sorted on the basis of this custom store and
the maximum number of students who can be added are added to the list.The
list is returned to be displayed to the Manager
{ Output: Database updated: All new items recieved by the NGO as donation
is added to the database.
{ Process:
The
Register:
{ Input :
{ Output:
{ Process:
{ Output:
{ Process:
The donor selects items from a list, the item he wants to donate.
{ Output:
{ Input:
{ Process:
The list of all students is traversed.A custom score is given to each student. Custom Score is Initially set equal to the students performance.If
the student is a girl 5% is added to the custom score.Also if the income
of parents of a student is below Rs 50,000 per annum 5% is again
added to his custom store. Then the list of students is sorted on the
basis of this custom store and the maximum number of students who
can be added are added to the list.The list is returned to be displayed to
the Manager
{ Process:
The
User Interfaces
Any one who opens the portal, can see a welcome page. There are options to
log in.
Software Interfaces