It Sets The Expectation For The Product You Are Building.: Investigation

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

1.

Intrduction
Political Campaign Management System is an online management system used for managing
campaigns, expenses and the events during elections. The aim of this project is to help politicians
and political organizations. Our goal is to develop a requirement specification document that
supports all the functional and non-functional requirements that will improve the managing
campaigns and the events during elections

Purpose

The purpose of the requirements specification document is to specify all requirements for the
current Political Campaign Management System. It sets the expectation for the product you are
building. It also help the designers of the software during the development of this system in
according to the requirements given in this specification.

Scope

The scope of this document is to specify or list the requirements for the current Political
Campaign Management System. It also includes the improvements that are suggested to us
during the investigation or test of this system.

This document covers:

 Functional requirements for the current registration system and improvements for
theSystem.
 Non-functional requirements.
 Constraints or assumptions of the specification.

2. Overview

Political Campaign Management System is a management system available for campaign


management. This management system provides set of multiple window operation to all the
authorize persons include admins, team members and the volunteers of a specific Political
Party.The system provides customized interfaces for the mentioned authorized users. Where their
queries regarding .Where the quires about campaign, expanses and events etc. can be adequately
and efficiently handled.
Product Functions

The Political Campaign Management System provides the following functions:

The admin can perform the following functions:

 Unique user id with password assigned to admins specified by Political party.


 Manage entire system.
 Admin can assign voting day setup.
 Admin can add volunteer details.
 Admin can assign volunteer rights
 Admin can check expense report.

3. Functional Requirements

FR01: Admin Login

Reg no Functional Requirements


FR01- Admin and only admin should be able to login with their unique ID and password
01
FR01- Only admin should be able to see the whole details of the entire campaign
02 management system.
FR01- Admin should be able to manage/edit/configure the entire campaign management
03 system
FR01- Admin should have a unique profile with picture, name, address, CNIC, political
04 party name with respective symbol.

This authority should be given to admin directly by the end user/software developer
only.

FR02: Team Management System

Reg no Functional Requirements


FR02- Team should consist of members selected only by admin and these members belong
01 to the same political party as the admin is.
FR02- Each team member should have a unique ID only.
02
FR02- Team member should be able to interact with each other easily
03
FR03: volunteer Management System

Reg no Functional Requirements


FR03- There should be a Portal for registration for each and every volunteer
01
FR03- Volunteers management system should be able to save cnic name email address and
02 contact no of all the volunteers included in the campaign
FR03- Volunteer Managemnet system should be able to deploy volunteers in their
03 respective areas with the help of datav provided with specific data and time

FR04: Voter Database System

Reg no Functional Requirements


FR04- There should be a voter database of their respective areas with their respective
01 adreesses
FR04- Voter database should include CNIC, address , contact no, of all the voters in a
02 specific constituency
FR04- Voter Database System should be only accessible to admin and team members only
03 of the campaign management system

FR05: Event Management System

Reg no Functional Requirements


FR05- Event management system should specify about the specific time and specific date
01 for a particular campaign , rally/gathering
FR05- Event management system should be able to retrieve data from voter database and
02 volunteer management system also.
FR05- Event management system can be only managed by admin
03

FR06: Bulk SMS & Email System

Reg no Functional Requirements


FR06- Bulk sms and email system should be able to retrieve contact no and email from
01 voter database and volunteer management system respectively
FR06- Bulk sms system should be connected by a connecting system which should be very
02 fats and reliable even in the most crowded system
FR07: Campaign analysis Database System

Reg no Functional Requirements


FR07- Campaign analysis system should be able to analyze results in charts and graphs
01 based on the event management module
FR07- Campaign management system, should be able to forecast new campaigns based on
02 previous analysis

FR08: Front-end website System

Reg no Front end website System


FR08- Front-end website should be available for the public.
01
FR08- Front-end website should be able to show all the campaign details in the respective
02 area.

FR08: Expense management System

Reg no Expense management System


FR08- In expense management System, only admin and team members should able to
01 access the system.
FR08- Expense management System the record of expense should be saved in a separate
02 system (hard drive)

FR08: Donation Database

Reg no Donation Database


FR08- Donation Database saves all the foreign and local donations.
01
FR08- Donation Database can only be access by the admins.
02

FR08: Database Backup System

Reg no Database Backup System


FR02- In Database Backup System, admin should be able to should be able to form a team
01 with special member and volunteer.
FR02- In Database Backup System backup of the entire system should be saved to
02 computer.
FR02- In Database Backup System, each database should be encrypted.
03
FR02- Database Backup System is accessible only by only admin.
04

FR08: Team Coordination

Reg no Team Coordination


FR08- In Team Coordination, admin should be able to should be able to form a team with
01 special member and volunteer.

Non-functional requirements:

NFR01: Performance

Reg no Requirement
FR01- Political campaign management system should open every next module in 2 sec. In
01 addition, if a module consist of large data than maximum 5 seconds.
FR01- System should respond to user each and every queriy in 2 second
02

NFR02: Security

Reg no Requirement
FR02- All databases should be encrypted and secure
01
FR02- Admin’s login and password credentials should be secure and password should be a
02 combination of lower, upper case letter along with special characters like(,./!#$%)

NFR03: User Interface

Reg no Requirement
FR03- Interaction between Campaign management system and user should be rich with
01 bright graphics

NFR04: Defects-Maintenance
Reg-no Requirement
FR04- Post Release defects of the system must not exceed 2 critical bug per month.
01
FR04- Post Release bug fixing should not take more than 3 hours.
02

You might also like