You are on page 1of 10

DAR ES SALAAM INSTITUTE OFTECHNOLOGY

SOFTWARE ENGINEERING

STUDENT'S NAME: SAAD A KIMANGALE

ADMISSION NO: 190230222340

CLASS: BENG 20 COE

DEPARTMENT: COMPUTER DEPARTMENT

PROGRAMME: BACHELOR DEGREE OF COMPUTER


ENGINEERING

ACADEMIC YEAR: 2020/2021

1
SOFTWARE REQUIREMENT
SPECIFICATION DOCUMENT (SRS)
For
PLOT MANAGEMENT SYSTEM

WRITTEN BY: SAAD A KIMANGALE


ON: 19rd NOVEMBER 2021

2
3
Contents
1.INTRODUCTION .................................................................................................................................... 5
1.1 Purpose and intended audience ....................................................................................................... 5
1.2 Project scope ..................................................................................................................................... 5
1.3 Acronyms and Definition .................................................................................................................. 5
2. OVERALL DESCRIPTION ....................................................................................................................... 6
2.1 User needs ........................................................................................................................................ 6
2.2 operating environment and implementation constraints ................................................................ 6
2.3 Assumptions ...................................................................................................................................... 6
3. SYSTEM FEATURES .............................................................................................................................. 7
3.1 Functional requirements and non-functional requirements ............................................................ 7
3.1.1 Registering a new user ................................................................................................................... 7
3.1.2 Non-functional requirements ........................................................................................................ 7
3.2 Functional requirements................................................................................................................... 7
3.2.1 Login ............................................................................................................................................... 7
3.2.2 Logout ............................................................................................................................................ 8
3.2.4 Register a new user ........................................................................................................................ 8
3.2.5 Removing old user ......................................................................................................................... 8
3.2.6 View plot details ............................................................................................................................ 9

4
1.INTRODUCTION
The management of the plots that have been sold and bought has become very
tough to LOCAL GOVERNMENT OFFICIALS, since there are some of the
people who are buying from the wrong property owners having all credentials
of making sales and then all blames return to government officials. The
software will provide assistance to these officials together with buyers to notice
who is real owner of the plots by showing all of his/her credentials of owning
specified plot.

1.1 Purpose and intended audience


The purpose of the document is to provide agreement on what a portion of
system or system is to do.
• Simplify communication to the project supervisors
• It will later simplify software testing that will be done by software testers.
• Supporting software design

1.2 Project scope


The system project will facilitate to eradicate scamming of plots, by allowing
the owners of the plots to register to the system. This will help people with
plots needs to see the real owners of the plots and will avoid the plots to have
more than one owners. The software will not involve the process of selling and
buying plots online since its not E-COMMERCE software.

1.3 Acronyms and Definition


terms definition
Old user The user that will sell his/her plot

New user The user that will buy the plot from
registered owner
DBMS Database Management System
Plot A compound

5
2. OVERALL DESCRIPTION
2.1 User needs
The system will be used by local government officials who will be having
the access of registering plots owners to the software. These officials are the
ones operating on local government as the leaders of the society that has
selected them to be their leader, so they will be registered to the software as
admins. These leaders needs this software to facilitate their task of controlling
and managing the plots ownership.
Also other users are plots clients which are primary uses, these are intended
users , they can view from software all about the plots they want to buy.

2.2 operating environment and implementation constraints


The system will be used by citizens and local government officials and will
be used outdoors.
There are software that have been used to complete this project
• Django as a web framework
• Python
• HTML, CSS and JavaScript
• Microsoft windows 10
• Computer
• Postgres as DBMS
• XAMPP

2.3 Assumptions
The assumptions is done that software will come to be used as e-commerce
system that anyone can make sales and purchases on software
Also software will be used by all citizens around the country since it is now
used by local government citizens.

6
3. SYSTEM FEATURES
3.1 Functional requirements and non-functional requirements

3.1.1 Registering a new user


• Unregister an old user
• Login to the system
• Logout from the system
• View plots details

3.1.2 Non-functional requirements


o Security
o perfomance

3.2 Functional requirements

3.2.1 Login
Inputs
Should have registered account
Process
Should enter the username and password
Output
Should be logged in
actors
actors activities

Admin (local government officials) Login to the system to control other


activities like registering plot owners

7
3.2.2 Logout
Inputs
Should be logged in as registered account
Process
3.2.3 Log out from the account
Output
Logged out
Actors
actors activities

Admin (local government officials) Log out from the system

3.2.4 Register a new user


Inputs
a user should buy plot(s) from registered user
Process
Removing the old owner and give ownership to new owner.
Output
Registered to system
Actors
actors activities
Admin (local government officials) Adding new use to the system
Give the ownership of the plot to new
user

3.2.5 Removing old user


Inputs
A user Should have registered account

8
Process
A user Should sell his/her plots and then the ownership should be given to new
buyer
Output
Removed from system as the owner of the sold plot, but if he/she owns more
than one plot can remain on the system.

actors
actors activities
Admin (local government officials) Delete the user from the system
Remove plot ownership from the user
sold plot

3.2.6 View plot details


Inputs
Knowing location of the plots
Process
Enter location of the plots
Output
Able to view plot details
Actors
actors activities
Client(citizens) Can view a plot she/he wants to buy
and plot’s information including the
owner

9
.

10

You might also like