Software requirements Specification for < Web and Android Based Census Management

System for Ethiopia Statistical Agency>

ASSOSA UNIVERSITY
COLLAGE OF COMPUTING AND INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
<Web and Android Based Census Management System for Ethiopia Statistical Agency>

A Software Project Documentation Submitted to the

Department of Computer Science of Assosa University in Partial Fulfillment of
Requirements for the Degree of Bachelor of Science in Computer Science
Prepared by:
1 ABDURAHEM EMRHAN
2 GEBREMEDIN DESALEW
3 HABTAMU DEBEBE
4 MESERET WALE
5 SELAM TIBEBU

Main Advisor: - Mr. Yordanos A (MSc)

Submitted Date: /2015

Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Software Requirements
Specification
for
< Web and Android Based Census Management System for Ethiopia Statistical Agency>

Version 1.0 Approved

Prepared by < ABDURAHEM EMRHAN, GEBREMEDIN DESALEW, HABTAMU

DEBEBE, MESERET WALE, SELAM TIBEBU>

<ASSOSA, ETHIOPA>
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

ACKNOWLEDGEMENT
This project is not done only by our effort. It has got an input from different individuals. First of
all we would like to thank our GOD who gives great potential for us to do our project with
healthy life and well-coordinated team from beginning up to today. Next to this we want to
express our sincerely gratitude to thanks our advisor Mr. Yordanos A for his advising and
guiding us through the right path how the project is prepared and reflect the idea about the
project for us and gives necessary comments until the completion of the Software requirements
Specification and next we would like to thank our department teachers and class students those
have given ideas how to do different diagrams in our project. And we sincerely thank Assosa
statistical agency officers for giving manual document of Census management and more
information about Population census and housing how work is performed in the organization and
telling how the existing system works for better understanding to the system.

Table of Contents

ii | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

ACKNOWLEDGEMENT...........................................................................................................................ii
1 Introduction..............................................................................................................................................1
1.1 Document Purpose............................................................................................................................1
1.2 Product Scope....................................................................................................................................2
1.3 Intended Audience and Document Overview....................................................................................3
1.4 Definitions, Acronyms and Abbreviations..........................................................................................3
1.5 References.........................................................................................................................................4
2. Overall Description.................................................................................................................................4
2.1 Products perspective.........................................................................................................................4
2.2 Product Functions..............................................................................................................................5
2.3. User Classes and Characteristics.......................................................................................................6
2.4 Operating Environment.....................................................................................................................7
2.5. Design and Implementation Constraints..........................................................................................7
2.6 User Documentation..........................................................................................................................7
2.7 Assumptions and Dependencies........................................................................................................8
3. Specific Requirements.............................................................................................................................8
3.1 External Interface Requirements.......................................................................................................8
3.1.1 User interfaces............................................................................................................................9
3.1.2 Hardware Interfaces....................................................................................................................9
3.1.3 Software Interface.....................................................................................................................10
3.1.4 Communication interfaces........................................................................................................10
3.2 Functional Requirements.................................................................................................................10
3.3 System Use Case Modeling..............................................................................................................12
3.4. System Use Case Documentation...................................................................................................15
4. Non-functional requirements.................................................................................................................24
4.1 Performance Requirements.............................................................................................................24
4.2 Safety and Security Requirements...................................................................................................24
4.3. Software Quality Attributes............................................................................................................25
4.3.1 Reliability.................................................................................................................................25
4.3.2 Robustness................................................................................................................................25

iii | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

4.3.3 Availability...............................................................................................................................25
4.3.4 Maintainability..........................................................................................................................25
4.3.5 Portability.................................................................................................................................26

List of table
TABLE 3. 1 ACTOR AND USE CASE
TABLE 1 : USE CASE DESCRIPTION FOR LOGIN
TABLE 2 : USE CASE DESCRIPTION FOR APPROVE
TABLE 3: USE CASE DESCRIPTION FOR GENERATE REPORT
TABLE 4 : USE CASE DESCRIPTION FOR CREATE ACCOUNT
TABLE 5: USE CASE DESCRIPTION FOR UPDATE ACCOUNT
TABLE 6 : USE CASE DESCRIPTION FOR VIEW REPORT
TABLE 7: USE CASE DESCRIPTION FOR REGISTER
TABLE 8: USE CASE DESCRIPTION FOR SEARCH PERSON
TABLE 9 : USE CASE DESCRIPTION MESSAGE

iv | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

1 Introduction
System requirement specification is an essential activity that must be undertaken in any project
to have a clear idea of the proposed system. The requirement of the proposed system will be
explained on the form of functional and non-functional requirements are modeled by the
essential use case. Analysis is the process of breaking something into its parts so that the whole
may be understood. System analysis is concerned with becoming aware of the problem,
identifying the relevant and most decisional variables, analyzing and synthesizing the various
factors and determining an optimal or at least a satisfactory solution. During this a problem is
identified, alternate system solutions are studied and recommendations are made about
committing the resources used to design the system. This document will discuss details of the
requirement analysis and overall description and Work flow of the existing system. The
requirement of the proposed system will be explained in functional and nonfunctional
requirements. In doing so, use case model will be used. [1]

The goal and principle of the system requirement specification is to prepare the scope of the
document, the designer’s view of the client’s needs and requirements before the actual system is
designed. It serves like the evidence tool that implies both client and designer have accepted to
introduce the new system. The system is first evaluated to verify how it operates, view the
problems of the current system, its specifications and additional technological options. Measures
the weakness and strength that the system is bound to get.

This system specification including the existing system of the Ethiopia Statistical Agency Census
Management system and proposed system of functional and nonfunctional requirements used to
design the system. It also includes: System Requirement Specifications (SRS), Use case
diagrams, Use case description (for each use case identified), and Sequence diagram, Activity
Diagram and User Interface Prototyping.

1.1 Document Purpose

It describes each of the functional and non-functional requirement of the system. Since our
system is going to be developed from scratch the software requirements specification allows for

1|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

a complete understanding of what is to be expected from the newly introduced system which is
to be constructed. The clear understanding of the system and its’ functionality will allow for the
correct software to be developed for the end user and will be used for the development of the
future stages of the project.

The purpose of this software requirements specification document is to provide a detailed

description of the functionalities of the Web and Android Based Census Management system.
The document will also cover hardware, software, and various other technical dependencies.

1.2 Product Scope

The introducing software, Web and Android Based Census Management System which is going
to be implemented for Assosa city will automate the major operations of the offices which
supports web and Android based application. The system will be able to handle many services to
take care of all population in a quick manner. As a solution to the large amount of file handling
happening, this software will be used to overcome those drawbacks registration, documentation,
writing, search and retrieval of the specific information of the population is done manually.
These types of system make the worker to document erroneous and redundancy information,
lack of automated statistical manipulations or analysis, decreases flexibility and it also
consume the time of employee for completing specific task [2].

The new system will allow the institution to manage its Population information effectively. This
system will provide a more reliable alternative to the existing system by ensuring efficient
information retrieval, secure and convenient mode of storing data and database management. The
system will be integrated in parallel with the existing system. As its services are to enhance the
existing one, it will not replace the existing one. This system requirement document is the initial
release and will only cover the requirements through preliminary analysis of the proposed
system’s features. These requirements have been developed through intensive consultations with
users and include a summary of all the necessary assumptions and relations. The system provides
ultimate protection against unauthorized access trying to access the system which contains the
organizations data by setting up logins. It will have a large database that would provide enough
space to store the people’s records gathered from the field.

2|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

1.3 Intended Audience and Document Overview

The document is intended for the clients below: Developers: The developers will be able to
access the various features provided by the application thus increasing the security. Users: Users
include the field clerks and the Supervisors of the system. System Administrators: They will
ensure that the system is working well and will be responsible of managing the user’s database.
Enumerator is the one who has privilege to collect and fill the census by collecting the
information of the people on the paper manually

The intended readers of this document are the developers of Web and Android Based Census
Management System that means group 5 student members, testers, project examiner document
writers, society and office managers and team members. Any suggested changes on the
requirements listed on this document should be included in the last version of it so it can be a
reference to developing and validating teams.

 Enumerator:
The Enumerator is the one who has privilege to collect and fill the census by collecting the
information of the people on the paper manually. Each enumerator was given the map of an
enumeration area along with other census document and he/she was responsible to record all
persons and households in that enumeration area without omission and duplication. Each
enumerator contains a national enumerator number given by central statics agency to identify
each and every enumerator.
 Supervisor:
Supervisor is a person who has a privilege to supervise and validate the collected census data.
He/she will assign to a supervision area and will responsible for ensuring the quality of the
information collected in the area of his/her jurisdiction

1.4 Definitions, Acronyms and Abbreviations

CSS…………………………………….Cascade style sheet
HTML………………………………Hypertext markup language

HTTPS……………………………...Hypertext transfer protocol secure

JS……………………….…………….JavaScript

3|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

SRS………………….. ……………….Software requirement specification

MYSQL…………………………………My Structural query language

SQL…………………………..………… Structural Query Language

Id…………………………………….. Identification number

PC…………………………………….personal Computer

PHP…………………………………Hypertext preprocessor

PW……………………….……………. password

UML…………………………………..Unified Modeling Language

WABCMS…………………………web and Android Based Census Management system

1.5 References
[1] " PROJECT MANAGEMENT / SOFTWARE REQUIREMENT SPECIFICATION," IEEE, 2018.
[Online]

[2] www.wdc/index.php/about-us/history-of-census, Accessed Date:-5 DEC, 2010 E.C, 9:14 PM

[3] Communications Interfaces Definition | Law Insider

[4] "Di-ipsc-81433a, data item description software requirements specification (srs)".

Everyspec.com. 1999-12-15. Retrieved 2013-04-04.

2. Overall Description
This section provides a more detailed overview of the system under development, including a
description of the product’s function and all Overall -encompassing constraints.

2.1 Products perspective

Web and Android Based Census Management system is a self-contained systems and is a
replacement for the ordinary Web and Android Based Census Management system which depend
on paper work for, writing, search and retrieval of the specific information of the population is
done manually. We are going to develop this system from scratch and there is no one who
developed this system for Ethiopia before.

4|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

The product is distributed but requires web server software to operate. It has two external
interfaces consisting of a configuration interface and a client interface. Both require the use of a
web-browser running on the client computer. The product is designed to run on existing
hardware and software.

WABCMS

Figure 1 Product perspective

2.2 Product Functions
Functionality describe the interactions between the system and its environment independent of its
implementation. The environment includes the user and any other external system with which the
system interacts. The user of web and Android based System are able to the system will do
online Registering new person, house, migration, death, birth rate and marriage.

 The manager generates different statistical reports (like birth rate, mortality
rate, migration).
 Enables supervisor to approve, update and search population information the
census recorded by the enumerator.
 Enables administrator to create, delete, update, view, activate and deactivate
accounts.

5|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

 Enables the enumerator to record the information person and housing unit.

Data Processing. Data processing will be on the basis of first come first served. i.e. the first bit
of data to be entered in the system will be the first one to be processed.

Data Output. Processed data will be displayed on the screen first to view if there are any errors
that are to be removed before it may be sent to the printer incase a hard copy is required.

Monitoring. The system will be able to monitor some destructive activities like when deleting of
any record. It will also inform the users of information such as record updated and so on.

2.3. User Classes and Characteristics

The Web and Android Based Census Management system is meant to offer a shared expenses
solution that is faster, easier, and more convenient than manual system. Consequently, the
application will have little or no learning curve, and the user interface will be as intuitive as
possible.

The users of the system have different skills and some will require a lot of training to be able to
use the system comfortably. In this case, use of menus in the application system will be a very
good option so as to avoid a lot of training. In addition to menus, there will be the need to come
up with a user guide that will be able to show the instructions on what is performed in the
system. The general characteristics of the users are:

 All the users are computer literate

 Users at the operational level have skills for comprehensive data capturing, data entry
and manipulation of the databases.
 Users at the management level use the system to study summarized data and for strategic
decision-making.
1 Administrator:
Admin is a person who has privilege to create, delete, view and update an account.
2 Enumerator:
The Enumerator is the one who has privilege to collect and fill the census by collecting the
information of the people on the paper manually.

6|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

3 Supervisor:
Supervisor is a person who has a privilege to approve and validate the data recorded by the
enumerator.
4 Manager:
Manager is a person who has privilege to generate report, view report and communicate with
message.

2.4 Operating Environment

The Web and Android Based Census Management system is platform independent it operate on
windows operating system will run on browsers such as Google Chrome, Internet explorer,
Android studio, Mozilla Firefox, Baidu Spark, Maxton and other java and JavaScript support
browsers Our system is developing using Android studio, Bootstrap content management system,
which has HTML, CSS and JS inside it. This helps us to develop the system easily and allow our
system to be displayed on any screen appropriately.

2.5. Design and Implementation Constraints

The primary design constraint is the web and Android platform. Since the application is
designated for web, limited screen size and resolution will be a major design consideration.
Creating a user interface, which is both effective and easily navigable, will pose a difficult
challenge. Other constraints such as limited memory and processing power are also worth
considering

 The system use PHP for web-based development.

 The system use MYSQL Database Engine.
 The system use Android Studio for android application.
 The front-end programming will be done with PHP.
 Use bootstraps for development and smart form.
 The system employ UML modeling language for specifying requirements, designing
subsystems and implementing the system.

7|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

2.6 User Documentation

The system will provide an on-line help feature, providing the users with easy to read “how-to”
instruction use WABCMS administration will be given an in –depth manual of the entire system,
so that they may support the system after development is complete.

2.7 Assumptions and Dependencies

The system assumptions that relate to the requirements here are;

 The first assumption about the product depend on the internet connection.
 That the sample interviewed and respondents of the questionnaires adequately represent
the entire population and that the computer systems shall fully support the application.
 That the systems are meant only for users running the windows operating systems and the
users shall keep to the domain scope and not traverse it.
 The system is not supposed to exceed the stated budget since this may lead to omission of
some necessary requirements that are stated in this project.
 The system will be fully integrated with the University website.

The product will always be used on PC that have enough performance mostly in desktop with in
the local area network. If the PC or desktop does not have enough hardware resources and
available broadband Wi-Fi or data connection the system does not perform any task. In this case
our assumption is there will be enough internet connection for us to develop the software and in
order to use the software product to perform their activity properly. If the lack of connection
occurs, for the developer it is difficult to develop the target software in given time and difficult to
use properly the system for end user.

The system is depended upon by many users therefore it should be able to deal with number of
users logging onto the system at any one time. Another assumption, we assumed that the user has
basic computer use skill and other general knowledge of how to use the system.

3. Specific Requirements
It describes all the details that the software developer need to know for designing and
developing the system. This is typically the largest and most important part of the document.

8|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

3.1 External Interface Requirements

External interface requirements specify hardware, software, or database elements with which a
system or component must interface...." This section provides information to ensure that the
system will communicate properly with external components [From Web 2.0 Wiki, Wiegers
Wiki Template [4].

3.1.1 User interfaces

The user interface for Web and Android based Census Management Systems is very easily
understandable and flexible, a since no need finding professional experts to work on the system.

The system will have a friendly graphical user interface. Which is easy to use and understand the
interface will be interactive. And as the system is web and Android based the user interface will
be on web page there are many pages:

 Login Page: this page is the first page of the system. It is used to login the user to the
system by requesting the user to insert Username and password. It contains a text filed
for username, password filed for the password, a dropdown for login as with a login
button
 Home Page: this page will be different throughout the user type. This page is loaded as
soon as the user login successfully. It contains notification area, and menus for traveling
to other pages.

All pages of the system have consistent themes and clear in structure. The occurrence of errors
should be minimized through the use of checkboxes, radio buttons and scroll down in order to
reduce the amount of text input from user. HTML Tables to display information to give a clear
structure that easy to understand by user. Error message should be located beside the error input
which clearly highlight and tell user how to solve it. If system error, it should provide the contact
methods. The page should display the project process in different color to clearly reflect the
various states that users done.

9|Page
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

3.1.2 Hardware Interfaces

The system works on any computer to generate online functional operation with no device type
selection of computer. The computer provides abstractions for all network communication
interfaces as well as hardware parts of the device.

Hardware contains the components that are used by the user to interact with the system either in
inputting or retrieving information.

• The mouse will be used to navigate various windows/sections required by user

• The keyboard will be used for data entry to the screen
• The monitor will be used to show information inputted or retrieved by the user.
• The database will serve as the information repository.
• The central processing unit will enable control of writing to and retrieving information from
the database.

3.1.3 Software Interface

The application will be communicated with the database through MySQL. There will be many
forms to allow user interactivity with the system. It will provide links which will guide the user
to various pages.

The poll server runs on http server that is enabled to handle server pages. It uses a relational
database to keep track of the polls, which it connects through standard database connectivity
interfaces. In order to run our system we will use the following software.

 Operating system: We have chosen Windows operating system for its best support and
user friendliness.
 Database: We have chosen SQL database application to save the actors records.

 PHP: We have chosen PHP to implement the project.

 Android studio: We have chosen Android to implement this project .

10 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

3.1.4 Communication interfaces

We use JavaScript which plays a great role for security and HTTPS protocols as a
communication interface to facilitate communications between the client and server [3].It
requires having a stable internet connection. Mostly a broadband connection with the client’s
computer will provide the efficient service.

3.2 Functional Requirements

Each user have a login name and password and this information is required before the user is
allowed to access any information from the database thus integrity is enhanced. Request will be
stored in a database, which will be run by MySQL. The system shall receive requests from the
users then process the data thus giving information to the users. The system will also ensure that
the data and information is safe from unauthorized users by use of username and password.

The functional requirement for the system describes the functionally or services that the system
is expected to provide. They are fundamental building block requirements. It is a statement of
exactly what the system must do. The new system has the following functional requirements:

The main functional requirements of this system are:

 The user should have user account and password to login to the system. - In
this software all actors who have privilege to login to the system.
 Activate and deactivate of user account: The system permits users to login
according to their privilege.
 Search: the system would enable to help the user to find the information from
the data base.
 Remove: system would enable to delete the information detail when it is
required.
 The system enables the enumerator to record the information person and
housing unit.
 The system shall be generates different statistical reports (like birth rate,
mortality rate, migration).
 The system would calculate the total number of people or density of population
in the Ethiopia statistical agency.

11 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

 The system should allow messaging to the users.

 The system shall be allow for system administrator to create account, update
account and delete account.
 The system shall be enables the supervisor to approve the census recorded by
the enumerator.
 The system should allow for system administrator to activate and deactivate
accounts.
 The system should collect and store the detailed information population
provided by enumerator.
 The system should allow the user to view their full reports.
 The system should update the detailed information population provided by
enumerator.

3.3 System Use Case Modeling

A system use case model is composed of use case diagram associations. Use case diagram: Use
Case represents interaction between a user (human or machine) and the system [3].

An actor describes any entity that interacts with the system. Our project system contains the
following actors:

 Administrator
 Supervisor
 Manager
 Enumerator

Actor Specification: In the use cases an actor interacts with the system.

Table 3. 1 Actor and use case

User Use Case Description

Administrator  Login
 Create account
 Delete account
 Update account

12 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

 View account
 logout
Supervisor  Login
 Approve
 View report
 Search
 Communicate with message
 logout
Manager  Login
 Generate report
 View report
 Communicate with message
 logout
Enumerator  login
 Register (new person, migration, death,
birth, household and marriage)
 View report
 Communicate with message
 logout

13 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Figure 3.1: Use case Diagram for Web

14 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Figure 3.2: Use case Diagram for Android

3.4. System Use Case Documentation
Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions.
The system should or can perform in collaboration with one or more external users of the
system (actors). Each use case should provide some observable and valuable result to the actors
or other stakeholders of the system.

Table 1 : Use Case Description for login

Use case name Login

Use case ID UC-1
Author Abdurahim
Actors Administrator, Enumerator, Supervisor ,Manager

Precondition User must have user name, password to access the system

15 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Post condition The actor is logged into the system and can access it
Priority Medium

Description It helps to access the system by authenticating and authorizing un and pw

Basic course of User System

action
Step 1.User initiate login system Step 2.System display login form

Step3.The user input user name, Step 4. The system checks the validity of the
password and submit. entry and then verifies whether the user is
authenticated and authorized.

Step 5. If the user is authenticated &

authorized the system displays the requested
page

Step 6. Use case end.

Alternative course If the username and password is incorrect

of action 1A. The user can try again to access the system or return to step 3.
Exception Error

Table 2 : Use Case Description for Approve

Use case name Approve

Use case ID UC-2
Author Meseret

Actors Supervisor

Precondition Supervisor must have to logged in to the system.

Post condition The Supervisor is now approved the record data

Priority High

16 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Description The Supervisor approve the recorded census data

Basic course of User System

action
Step1.Click recorded data Step 2. display the recorded data

Step3. view recorded data Step 5.The system move the data from
temporary database to permanent
Step 4.The actor click on approve button
census data base

Step 6.The system display done

message

Step 7.use case end.

Alternative course 1A.if the recorded data is not valid return to basic course of action 3
of action
Exception Error

Table 3: Use Case Description for generate report

Use case name Generate report

Use case ID UC-3

Author Gebremedin
Actors Manager
Precondition Manager must be authenticated and authorized.
Post condition Manager generates report successfully.

Priority Medium
Description Manager generates person data & house holding filled by enumerator.

Basic course of User System

17 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

action Step1. Manager click on Step 2.The system display generate

generate person report or person report or generate house
generate house report report
Step3. Manager view recorded
Step 4.The system display recorded
data
data
Step 5. Manager generates Person
report and house report. Step 6. The system display report
generate successfully.
Step 7. use case end
Alternative course 1A. If there is no data the system display error message go to step3.
of action

Exception Error

Table 4 : Use Case Description for Create account

Use case name Create account

Use case ID UC-4

Author Selam
Actors Administrator
Precondition Administrator must be authenticated and authorized.
Post condition User can use the account to interact to the system.
Description The administrator can create new user account for the purpose of
accessing the system

Basic course of action System

User step

Step:

1. Administrator login to the system by entering username and password

2. Administrator click on create account button.

3. Administrator fills create account form.

18 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Step2. The system show

Step1. Open homepage
options like
Step3. Administrator click on
create account button.  Create, update and
 delete account
Step5. Administrator fills create Step4. The system display
account form. creates account form.
Step6. Click create account
Step 7. The system display your
button.
account is successfully created.

Step8. use case end

Alternative course of 1A. If the administrator’s entry is invalid data the system displays
action error message and return to step 5.

Exception Error

Table 5: Use Case Description for update account

Use case name Update account

Use case ID UC-5
Author Habtamu

Actors Administrator
Precondition Administrator must be authenticated and authorized.
Post condition An administrator can view the account.

Description An administrator can update exiting account.

Basic course of User Step: System
action
1. Administrator login to the system
by entering username and password
2. Administrator clicks on update
account link.

19 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Step1. Open homepage Step2. The system show options

Step3. Administrator click on update like
account button.  Create, update and
Step5. Administrator fills update account  delete account
form.
Step4. The system display updates
Step6.Clicking update button.
account form.

Step 7. The system display account

updated successfully.

Step8. Use case end.

Alternative course 1A. If the administrator’s entry invalid data the system displays error message
of action and return to step 5.

Exception Error

Table 6 : Use Case Description for View report

Use case name View report

Use case ID UC-6

Author Meseret

Actors Supervisor & Manager

Precondition User must have to logged in to the system

Post condition The user leaves view report page.

Priority high

Description The user view person report and house report on the data base.

Basic course of action User step System

20 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

.
Step1. Users go to census homepage.
Step 2. The system display
homepage
Step3. The user click view person
button menu or view house report. Step 4.Thesystem displays

Step 5.Enumerator, Supervisor views the person or house report.

the person or house report. Step 6.use case end

Alternative course of 1A.If there is not sent to database(no report)return to

action

Exception Error

Table 7: Use Case Description for Register

Use case name Register

Use case ID UC-7

Author Abdurahim

Actors Enumerator

Precondition User must have to logged in to the system

Post condition The enumerator see registration success

Priority Medium
Description The enumerator register new person, migration, birth rate, death, marriage

And house holding.

Basic course of User System
action

Step:

21 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Step 1.click the registration page Step2: The system displays the
Step3:Fill the registration form registration form.
Step4. Click on registration button. Step 5:The system check whether the
entered value is correct or not correct
Step 6: The System display
registration is success.
Step 7: use case end.

Alternative course If the entered value is not correct1A. The Enumerator can register again or
of action return to step 3&4.
Exception Error

Table 8: Use Case Description for Search person

Use case name Search

Use case ID UC-8
Author Gebrmedin
Actors Enumerator, Supervisor, Manager
Precondition Enumerator ,Supervisor, Manager must get search person page

Post condition Enumerator, Supervisor, Manager can get person detail information.

Priority Medium
Description User can search person data

Basic course of User System

action

22 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Step2.the system display homepage

Step 1. Open homepage
Step3. User click on the search button Step 4.The system displays the text box
to enter data.
Step5. User enters Person ID in the
form. Step 7. The system displays searched

Step6. User searches person by clicking data.

search button. Step8.use case end

Alternative course 1A.If user enter invalid person ID the system displays error message and go
of action to step 5.

Exception Error

Table 9 : Use Case Description message

Use case name Messaging

Use case ID UC-9
Author selam
Actors Enumerator, Supervisor, Manager
Precondition Enumerator, Supervisor, Manager logged to the system.

Post condition Enumerator, Supervisor, Manager must communicate with each other by messaging
Priority Medium

Description Enumerator, Supervisor, Manager must communicate by message to share information

to each other.
Basic course of User System
action

23 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

Step: 1. Open homepage Step 2.The system display

homepage
Step3.Enumerator, Supervisor, Manager select
messaging page. Step5. Display message form.

Step4.Click on message button. Step7. The system checks the

validity of the entry and then verifies
Step 6.The user inputs user name, position and
whether the user is authenticated and
send.
authorized.

Step 8. Use case end

Alternative course 1A. If the user’s entry (user name and Password) is not validated and verified the
of action system displays error message and return to step 6.
Exception Error

4. Non-functional requirements
Non-functional requirements (NFR) describe the non-behavioral attributes of a system, including
completeness, correctness, efficiency, interoperability, usability, reliability, maintainability,
portability, test-ability, and understandability [4].

4.1 Performance Requirements

System accomplishes tasks with in good response time and produce output within a good
throughput time. Checking the fact that the system must perform as what every user expects. So
in every action-response of the system, there are no immediate delays. Unless there are,
hardware and Internet connection constraints, the system can handle multiple users request at the
same time and responsive to user’s requests.

4.2 Safety and Security Requirements

Our system uses different security mechanism to protect user personal information. Among those
Password, user name and encryption technique. The system users are allowed to perform

24 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

activities or make a modification to the data if and only if they are authorized which will be
checked by their username, password, and account type. In other word unauthorized user cannot
access the system.

The non-functional requirement of the system deals with how well the system provides service to
the user.

 Security: Provide authentic and authorized features to the current system

where private and confidential data can only be viewed by authorized user.
 Speed: it will let the employers to access the needed information quickly
 Maintainability: to ensure that the system continues to work properly by
checking it regularly and making repairs and adjustments if required.
 Organization of menu: menus are organized in hierarchical manners.
 Scalability: it is the ability of a system to continue to function well as it
(its context) is changed in size or volume in order to meet a user need.

4.3. Software Quality Attributes

4.3.1 Reliability
The system is always reliable. The new system will operate for long period of time without
failure. If a connection failure occurs while submitting a request for consultation, the system
must save the data and retry sending when connection is re-established.

4.3.2 Robustness
The new system will show errors message when errors occur. This means the system should be
designed in such a way that users cannot proceed having entered invalid input or data in all cases
of interacting with the system.

4.3.3 Availability
Our system should be available 24 hours per a week unless there is no internet connection or it is
under some failure.

4.3.4 Maintainability
The system is designed with Object oriented approach and different modules. Our system can
maintain easily when the problem or failure occur. The system does not need higher expert to

25 | P a g e
Software requirements Specification for < Web and Android Based Census Management
System for Ethiopia Statistical Agency>

troubleshoot failure of it. Generally, any developer can easily maintain and modify without
affecting other parts.

4.3.5 Portability
The system can be executed in different platforms without any restriction. Patient can access the
system through any desktop. The system administrator can access the system through web
browsers with all platforms.

26 | P a g e