Software Requirements

Specification
for

Joint Application for

Community Development
(JACD)

Version 1.0 approved

Prepared by Noreen V. Dacay

Trishia Ella A. Josol
Jojie A. Avergonzado
Kent M. Cabrera

<Organization>

<Date>
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ 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 .................................................................................................................................. 2
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 3
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 4
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies ...................................................................................................... 4
3. External Interface Requirements ...........................................................................................5
3.1 User Interfaces ................................................................................................................................. 5
3.2 Hardware Interfaces ......................................................................................................................... 6
3.3 Software Interfaces .........................................................................Error! Bookmark not defined.
3.4 Communications Interfaces ............................................................................................................. 6
4. System Features .......................................................................................................................7
4.1 System Feature 1 .............................................................................................................................. 8
4.2 System Feature 2 (and so on) ........................................................................................................... 8
5. Other Nonfunctional Requirements .......................................................................................8
5.1 Performance Requirements .............................................................................................................. 8
5.2 Safety Requirements ........................................................................................................................ 9
5.3 Security Requirements ..................................................................................................................... 9
5.4 Software Quality Attributes ............................................................................................................. 9
5.5 Business Rules ................................................................................................................................. 9
6. Other Requirements ................................................................................................................9
Appendix A: Glossary....................................................................................................................9
Appendix B: Analysis Models .......................................................................................................9
Appendix C: To Be Determined List ..........................................................................................10

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Joint Application for Community Development Page 1

1. Introduction

1.1 Purpose
The purpose of this Software Requirements Specification is to describe and provide accurate
description about the system “Joint Application for Community Development” (JACD). It is clearly
detailed in this document the features and specification about the mentioned system. The
document will also cover hardware, software, and various other technical dependencies. This
system was created based on the existing problems in Barangay Bato (a government
organization). And this was approved by our client.

1.2 Document Conventions

This manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.

 Bold – Identifies the title that helps the readers to understand the topic.

The following are the list of the conventions and synonyms used in the document & project.

Term Definition
Administrator A log in Id representing the user with user administration privileges to
system.
Client Intend user of the system.
SQL (Structured Used to perform CRUD Operations on Database
Query language)
XAmpp A server used to store data in organized form
PHP Coding language
DFD Show the data flow between entities.

1.3 Intended Audience and Reading Suggestions

 Developers who can review project’s capabilities and more easily understand where their
efforts should be targeted to improve or add more features to it (design and code the
system that sets the guidelines for future project).
 Project testers can use this document as a basis for their testing strategy as some bugs are
easier to find using a requirements document. This way testing becomes more methodically
organized. This documents also can help the testers to define what the project about.
 End users of this system who wish to read about what this project can do and what this
project all about.
Software Requirements Specification for Joint Application for Community Development Page 2

1.4 Product Scope

The system will able to monitor the barangay documents request. It enables easy searching and
retrieving of household data. Provides specific information about the Barangay. It will also prepares
and prints Barangay Certificates. The system has a distribution of the programs to the deserving
recipients to the barangay and can monitor of the programs specifically in health, education, and
agriculture.

Its main objective is to monitor the programs every month and can generate a report of the
progress. To create a virtual database for easy retrieving. It has embedded SMS notification in
notifying and sharing announcement to the members of the barangay. To create online or web-
based for registration forms, application or interview. The system also can easily add and update
the data. A system that will let the recipients upload a picture or files to the progress of the
programs given so that the barangay can monitor it. To achieved its main objective we used Quick
Response Code or QR Code in monitoring the programs.

1.5 References
https://www.qr-code-generator.com/qr-code-marketing/why-should-i-use-qr-codes/

2. Overall Description

2.1 Product Perspective

This system is a new and self-contained product. It is a client-server network and in the client side
have five users and in the server-side is the admin.

This table shows the users and their description.

USERS DESCRIPTION
Barangay Captain This person is the highest elected official in the barangay that has the
power to enforce laws and ordinances.
Committee Head The person who takes responsibility for managing a specific topic in a
barangay.
Purok Leader The person who executes or disseminate information, plans, and
policies duly approved by the Barangay Captain.
Secretary The person who is an essential participant in the development of the
requirements, like keeping records in the Barangay.
Resident The resident provides the desired transactions in the Barangay Hall.

Below is the figure which you can see the program relationship in which one program (the client)
request a service or resource from another program (the server).
Software Requirements Specification for Joint Application for Community Development Page 3

2.2 Product Functions

The project is an advanced and automated process of managing a barangay to let go of the
manual process. The system displays the profiles, populations, information of the barangay,
constituents, and programs given by the government to the residents. It can automatically sort out
the names of the recipient for a specific program. This can also monitor the programs given to the
residents by uploading pictures of the actual happenings or progress of the program and it can
generate a report. In monitoring the programs, we used the Quick Response Code or QR Code.
The following are the functions of QR Code:
 This QR code monitoring process is applicable only in agricultural programs.
 Once the plants or seedlings were distributed to the recipients, the monitoring of its
progress using QR code is monthly (or based of what plant given to them, but for our
example we use Cacao plant)
 Every seedling of the cacao, there is a QR code attached to it. When it's time to monitor its
progress, the purok leader or the committee or any responsible person to monitor the
program will scan the QR code attached to every plant. Once he scans the QR code, it will
go to the site where he can evaluate the progress of the plant.
 He will input the data required in monitoring the plant such as the height of the plants, the
number of leaves and the state of the plant.
 The monitoring of the plants will continue until the plant will bear fruits.
 In case of the plant will die, the monitoring of the plant will stop.
 After monitoring, the system will generate a report about the progress of the programs
given.

2.3 User Classes and Characteristics

The current users were Brgy Captain, Secretary, Kagawad, Purok Leader and also the residents.
The user who work in the barangay is the one who can access mostly all the features but it
Software Requirements Specification for Joint Application for Community Development Page 4

depends on their positions. The residents can only access some features, most of them was
restricted.
 Barangay Captain- This user can access all the features like the admin.
 Barangay Secretary- This has the same access of the Barangay Captain.
 Barangay Kagawad- This user can only access on the program area, messaging, and the
list of the resident in the barangay.
 Purok Leader- This user can access the residents under his Purok and can monitor the
programs given to the resident.
 Resident- The only feature they can access is their profile and sending report for the
monitoring process.

2.4 Operating Environment

The system will operate with the following software components and applications: The software
being developed will run under Xampp server embedded operating system or any windows
version. The system shall provide the option to take a picture using camera on mobile and use a
printer.

2.5 Design and Implementation Constraints

The program is created using PHP programming language and uses the Xampp as local server
and it also use to communicate the system into database.

Synchronization: uses USB 2.0, connects to Windows 7 up to windows 10.

Memory: device will have 2GB internal hard drive. Software and database cannot exceed this
amount.
Language requirements: system is not multilingual.
Languages: English.

2.6 User Documentation

We are still under the process of making our Capstone Project.

<List the user documentation components (such as user manuals, on-line help, and tutorials) that
will be delivered along with the software. Identify any known user documentation delivery formats
or standards.>

2.7 Assumptions and Dependencies

It is assumed that the hardware designed will work correctly with the operating system and the
developed system. For creating the system Xampp as a local server was used. This local server
works on your desktop or laptop computer. This Xampp server software gives suitable environment
for testing the system. The language editor used is PHP, and to connect with the database is
MySQL. The system also uses SMS notification. The Ozeki SMS is used to give the information to
the residents of the barangay.
Software Requirements Specification for Joint Application for Community Development Page 5

3. External Interface Requirements

3.1 User Interfaces

Our system was about community development. When you first open it you will see the page and
when you click sign in button a modal will pop up and you will see the log in, see Figure 1. On the
other hand if the user has not register, he/she should be able to do that on the sign up page.

In figure 3 was add program shown. You can add program and distribute it to the resident in the
barangay. Also you can see the list that capable to that specific program. Our system was capable
of creating folders where the users can use the folders they made and put their documents, see
Figure 4.
Software Requirements Specification for Joint Application for Community Development Page 6

In figure 5 you can see your profile. You can edit the details in your profile like your personal
background.

3.2 Hardware Interfaces

Server side
The web application will be hosted on a local server which is listening on the web standard port,
port 80.

Client side
a) Monitor screen – the software shall display information to the user in the monitor screen
b) Mouse – the software shall interact with the movement of the mouse and the mouse
buttons. The mouse shall activate areas for data input, command buttons and select
options.
c) Keyboard – the software shall interact with the keystrokes of the keyboard. The user will
input data using keyboard into the active area of the database.
d) System unit – use as a local storage of the files.
e) Printer – support for printing

3.3 Software Interfaces

a) Windows Operating System
b) Any Latest Browser
c) XAMPP
Software Requirements Specification for Joint Application for Community Development Page 7

3.4 Communications Interfaces

Figure 6 Figure 7
Chat -a way to communicate the SMS - to inform the residents of the
barangay kagawad and the barangay bato.
barangay captain.

4. System Features
<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section
by use case, mode of operation, user class, object class, functional hierarchy, or
combinations of these, whatever makes the most logical sense for your product.>

The users of the system should be provided the surety that their account is secure. This is possible
by providing:

 PROFILES
 Advanced profile (customizable profile steps/fields)
 User authentications of members using their unique member ID.
 Personal Pages for users

 SEARCH AND MATCH

 Quick search
 Matchmaking (auto search based on user-specified criteria)

 COMMUNICATION
 Barangay Captain can post announcement
 Barangay Captain can message barangay kagawad
 Can deliver a message to residents
Software Requirements Specification for Joint Application for Community Development Page 8

 SITE ADMINISTRATION

 Profile statistics: number of members, total members, registered today

 Ability to define membership access level
 Database backup

4.1 System Feature 1

Monitoring and Distribution
<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or
Low priority. You could also include specific priority component ratings, such as
benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a
high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior
defined for this feature. These will correspond to the dialog elements associated with
use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the
services provided by the feature, or to execute the use case. Include how the product
should respond to anticipated error conditions or invalid inputs. Requirements should
be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a
placeholder to indicate when necessary information is not yet available.>

<Each requirement should be uniquely identified with a sequence number or a meaningful

tag of some kind.>

REQ-1:
REQ-2:

4.2 System Feature 2 (and so on)

5. Other Nonfunctional Requirements

5.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements as
specific as possible. You may need to state performance requirements for individual functional
requirements or features.>
Software Requirements Specification for Joint Application for Community Development Page 9

5.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well as
actions that must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>

5.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect the
product. Define any security or privacy certifications that must be satisfied.>

5.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility,
interoperability, maintainability, portability, reliability, reusability, robustness, testability, and
usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify
the relative preferences for various attributes, such as ease of use over ease of learning.>

5.5 Business Rules

<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Software Requirements Specification for Joint Application for Community Development Page 10

Appendix C: To Be Determined List

<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>