MEKDELA AMBA UNIVERSITY

FACULITY OF TECHNOLOGY
DEPARTMENT COMPUTER SCIENCE

Project Title: Web Based Kebele Management System for 01

tuluawuliya kebele

Advisor: Mr.______________

Mekdela Amba University, Ethiopia

2015 E.C
 MEKDELA AMBA UNIVERSITY
FACULTY OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
SUMMAR STUDENTS
WEB BASED KEBELE MANAGEMENT SYSTEM FOR 01 TULUAWULIYA
KEBELE

SUBMITTED TO DEPARTMENT OF COMPUTER SCIENCE PARTIAL

FULFILLMENT OF THE REQUIREMENT FOR

THE DEGREE OF BACHELOR OF SCIENCE IN COMPUTER SCIENCE

BY

NAME ID NO

1. NEGA WUBTU MEKURIA MAUS/065/11

2. GETACHEW MISGANAW ASEFA MAUS/037/11
3. JEMAL BEZABIH YIMER MAUS/043/11
4. MOHAMMED SIRAJE ABDELA MAUS/064/11
5. SOLEMON GEZIE BIRU MAUS/070/11
6. JEMAL SEID YIMER MAUS/046/11

Email Address: engidaadugna2009@gmail.com

Mekdela Amba University, Ethiopia.

2015 E.C
Approval Sheet

This is to confirm that the project report entitled web based Kebele Management System for Ginba
city, 01 tuluawuliya kebele, in the institute of technology department of computer science in partial
fulfillment of the requirement for the award of the degree of Bachelor of Science in computer science
is an original work carried out by group members, under my guidance. The matter embodied in this
project is reliable and is genuine work done by the student and has not been submitted whether to this
University or to any other University /Institute for the fulfillment of the requirement of any study.

Team member’s Signature date

NEGA WUBTU ………………… …..……………….

GETACHEW MISGANAW ………………….. …………………

JEMAL BEZABIH …………………. ………………….

MOHAMMED SIRAJE …………………. …………………

SOLEMON GEZIE …………………. …………………

JEMAL SEID …………………. …………………

Institute: Technology Program: Degree

Project Title: Web Based Kebele Management System for 01 tuluawuliya kebele, ginba city

This is to certify that we have read this project and that in our opinion it is fully adequate, in scope and
quality, as a project for the degree of Bachelor of Computer Science.

Name of Advisors role Signature date

1. AntenehTiruneh (Msc) Adviser _________ ___________
Examining committee members Signature Date
Examiner 1 ____________________ ____________ ___________________

Examiner 2 ____________________ _____________ ___________________

Examiner 3 ____________________ _____________ ___________________

It is approved that this project has been written in compliance with the formatting rules laid down by
the department.
 ACKNOWLEDGEMENTS

First of all, we would like to thank GOD for giving us strength and health to do this project. Secondly
we would like to thank to our advisor Mis. Feven and Co-advisor, Mr. Girmaye for their motivation
and guidance. We would like to forward our special thanks to 01 tuluawuliya administrator, Mr.
Abebe. We also thank to our department head Mr. Kbede for giving us a clue and recommendation
letter to gather information from 01 tuluawuliya administrator. Finally, we want to thank to our
parents for their encouragement and support throughout our study.
Table of Contents
Acknowledgements.....................................................................................................................................3
LISTS OF FIGURES..................................................................................................................................III
LISTS O TABLES.....................................................................................................................................IV
ACRONYMS/ABBREVIATION...............................................................................................................V
1 CHAPTER ONE: INTRODUCTION..................................................................................................1
1.1 Back ground.................................................................................................................................1
1.2 Motivation...................................................................................................................................1
1.3 Statement of the Problem.............................................................................................................1
1.4 Objective of the Project...............................................................................................................2
1.4.1 General Objective................................................................................................................2
1.4.2 Specific Objective................................................................................................................2
1.5 Literature Review........................................................................................................................2
1.6 Scope and Limitation of the project.............................................................................................3
1.6.1 Scope of the project.............................................................................................................3
1.6.2 Limitation of the project......................................................................................................3
1.7 Methodology................................................................................................................................4
1.7.1 Data Collection Technique...................................................................................................4
1.7.2 System Analysis and Design Methodology..........................................................................4
1.8 System Development Model........................................................................................................5
1.9 System Development Tool...........................................................................................................6
1.9.1 Hardware Tool.....................................................................................................................6
1.9.2 Software Tool......................................................................................................................6
1.9.3 Documentation Tools...........................................................................................................7
1.10 Significance of the project...........................................................................................................7
1.11 Feasibility study...........................................................................................................................7
1.11.1 Operational feasibility..........................................................................................................7
1.11.2 Technical feasibility.............................................................................................................7
1.11.3 Economic feasibility............................................................................................................8
1.12 Work Breakdown structure and Schedule feasibility...................................................................9

Mekdela Amba University Computer Science Graduate Students (2015EC). Page I

2 CHAPTER TWO: SYSTEM ANALYSIS.........................................................................................10
2.1 Introduction to System Analysis................................................................................................10
2.1.1 Existing System.................................................................................................................10
2.1.2 Proposed System...............................................................................................................12
2.2 Functional Requirements...........................................................................................................12
2.3 Non-Functional Requirements...................................................................................................13
2.4 Use Case Design........................................................................................................................13
2.4.1 Actor Identification............................................................................................................15
2.4.2 Use case Identification.......................................................................................................15
2.5 Use Case Description.................................................................................................................16
2.6 Sequence Diagram.....................................................................................................................29
2.7 Activity Diagram.......................................................................................................................35
2.8 Class Diagram............................................................................................................................39
2.9 Data Structure Model.................................................................................................................41
2.9.1 Entity-Relationship (ER) Model........................................................................................41
3 CHAPTER THREE: SYSTEM DESIGN..........................................................................................43
3.1 Purpose and Goals of Design.....................................................................................................43
3.1.1 Introduction.......................................................................................................................43
3.1.2 Purpose of Design..............................................................................................................43
3.2 Current Software architecture....................................................................................................44
3.3 Proposed Software Architecture................................................................................................44
3.3.1 System Decomposition......................................................................................................45
3.3.2 SubSystem Decomposition................................................................................................45
3.3.3 Component diagram...........................................................................................................46
3.3.4 Deployment diagram..........................................................................................................48
3.3.5 Persistent Data management..............................................................................................48
3.3.6 Access Control and Security..............................................................................................49
3.3.7 Boundary Condition and Exception Handling....................................................................50
3.4 User Interface Design................................................................................................................51
.................................................................................................................................................................. 52
REFFERENCE:.........................................................................................................................................53
APPENDICES...........................................................................................................................................54

Mekdela Amba University Computer Science Graduate Students (2015EC). Page II

LISTS OF FIGURES
Figure 1-1 Iterative Development Model........................................................................................5
Figure 2-1 Existing system flow chart diagram.............................................................................11
Figure 2-2 Use case Diagram........................................................................................................14
Figure 2-3 Sequence diagram for create account..........................................................................29
Figure 2-4 Sequence diagram for Login........................................................................................30
Figure 2-5 Sequence diagram for Give Marriage Certificate........................................................31
Figure 2-6 Sequence diagram for Give ID....................................................................................32
Figure 2-7 Sequence diagram for Renew ID.................................................................................33
Figure 2-8 Sequence diagram for Change password.....................................................................34
Figure 2-9 Activity diagrams for login..........................................................................................35
Figure 2-10 Activity diagram for renew ID...................................................................................36
Figure 2-11 Activity diagram for create account...........................................................................37
Figure 2-12 Activity diagram for give birth certificate.................................................................38
Figure 2-13 Class diagram.............................................................................................................40
Figure 2-14 EntityRelationship Diagram.......................................................................................42
Figure 3-1 Proposed software architecture....................................................................................45
Figure 3-2 Component Diagram....................................................................................................47
Figure 3-3 Deployment Diagram...................................................................................................48
Figure 0-1 User Interface Proto Type............................................................................................52

Mekdela Amba University Computer Science Graduate Students (2015EC). Page III
LISTS O TABLES
Table 1-1 Hardware Tool.................................................................................................................6
Table 1-2 Software Tool..................................................................................................................6
Table 1-3 Documentation Tool........................................................................................................7
Table 1-4 Proposed System Cost Estimation...................................................................................8
Table 1-5 Existing System Cost Estimation....................................................................................9
Table 1-6 Time schedule.................................................................................................................9
Table 2-1 Use case Description for Login.....................................................................................16
Table 2-2 Use case Description for create account.......................................................................17
Table 2-3 Use case Description for De-activate account...............................................................18
Table 2-4 Use case Description for activate Account...................................................................19
Table 2-5 Use case Description for Change Password..................................................................20
Table 2-6 Use case Description for Give ID.................................................................................21
Table 2-7 Use case Description for Renew ID..............................................................................22
Table 2-8 Use case Description for Give Marriage Certificate.....................................................23
Table 2-9 Use case Description for Give Birth Certificate............................................................24
Table 2-10 Use case Description for Give Divorce Certificate.....................................................25
Table 2-11 Use case Description for Give Death Certificate........................................................26
Table 2-12 Use case Description for Post News...........................................................................27
Table 2-13 Use case Description for Generate Report..................................................................28
Table 3-1 Access control and Security..........................................................................................50

Mekdela Amba University Computer Science Graduate Students (2015EC). Page IV

ACRONYMS/ABBREVIATION
CSS Cascading Style Sheet
HTML Hyper Text Mark-up Language
JS Java Script
MS Micro Soft
PHP Hyper Text Preprosser
XAMP Cross platform Apache MYSQL PHP
PC Personal Computer
RAM Random Access Memory
GB Giga Byte
USB Universal Serial Bus
CD or DVD Compact Disk or Digital Video Disk
DML Data Manipulation Language
DDL Data Definition language

Mekdela Amba University Computer Science Graduate Students (2015EC). Page V

 Kebele Management System for 01 tuluawuliya Kebele

1 CHAPTER ONE: INTRODUCTION

1.1 Back ground
A kebele is the smallest administrative unit of a city in Ethiopia, similar to a ward, a
neighborhood or a localized and delimited group of peoples.

Kebele is generally defined spatially as a specific geographic area and functionally as a set of
social community. Then, kebeles are the spatial units in which face-to-face social interactions
occurs the personal settings and situations where residents seek to realize common values,
socialise youth, and maintain effective socials. Each kebele consists of at least five hundred
families, or the equivalent of 3,500 to 4,000 persons. Things to dividing the kebele can be
measured forthe amount of human resources, budget, location, ways of control in which it can be
devide.

Woldia town has 3 Kebeles since 2001 E.C. After 2002 E.C The number of kebeles becomes 6
and each kebele is administered by Woldia town. So, Debre Gelila, Yeju Genet, Tinfaz, Defergie
Kibikalo, Admas Bashager, Addis Ketema kebeles inside the town.[4]

1.2 Motivation

We are lived above 5 years in ginba city, 01 tuluawuliya kebele and for many situations we have
the chance to see how they perform their activities, the way they handle files and the way of
services delivering of customers.

In this process we understand so many problems like customer lots of time and resource, work
load for employees and difficulties for file handling and searching. So in these cases we are
motivated to develop web based kebele management system for 01 tuluawuliya kebele.

1.3 Statement of the Problem

Currently, there is no web based kebele management system for thios kebele, and in the city; due
to this there is wastage of time and cost to handle the problems such as registration of Id, renew
id, vital certificates like (mirraige, birth, death, divorced) and so on.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 1

 Kebele Management System for 01 tuluawuliya Kebele

It is difficult to search and modify resident’s information. Administrators keep information or

record of the residents in manual system that can causes everybody can access the resident’s
information, destroying resident’s information intentionally or accidentally and lack of accuracy
of information security.

1.4 Objective of the Project

1.4.1 General Objective
The general objective of this project is to develop web based automated Kebele management
system in for 01 tuluauliya kele, ginba city.

1.4.2 Specific Objective

In order to achieve the general objective of this project we will address the following specific
objectives.

 To Investigate and identify the problem of existing system.

 To understand the system requirments.
 To conduct system analysis.
 To design user friendly interface.
 To test and evaluate the system.

1.5 Literature Review

From what we were interviewed and gathered information from ginba city, 01 tuluawuliya
kebele as the chairman of the kebele told us still now there is no computerized system regarding
to the kebele not only 01 tuluawuliya kebele and kebeles in the city, but also in other kebeles
which are found in Amhara Region. So we have taken the guide line of the form what they are
used in the existing paper based system and we try to automate the existing system in to
computerized one.
Due to the above reason we have taken a decision to develop this system to solve the problems
which are found in the all in this kebele such as; register Id, register renewal Id, vital registration,
to minimize work load for the employees, to keep residences information permanently and
finally reduce the wastage of resource such as time, cost...

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 2

 Kebele Management System for 01 tuluawuliya Kebele

When a person goes to the kebele administration to retrieve or renew ID, he first goes to the
kebele manager's office and then the manager leads him to register for the record officer and
payment to finance. The manager will sign it and give it to him. [4]

1.6 Scope and Limitation of the project

1.6.1 Scope of the project

The scope of this project focuses mainly on functional aspects of Kebele management system

 Give ID card to Residences

 ID card renewal to Residences
 Death certificates to residences
 Birth certificates to Residences
 Marriage certificates to Residences
 Divorce certificates to Residences
 Social Court Service to residences
 Record new users
 Message
 Generate report
 Give and receive clearance
 View residence
 Give Supportive letter

1.6.2 Limitation of the project

Our analysis will not include some activities which are related with the Kebele: -

 Accept only two languages because we only know 2 languages(Amharic and

English)
 Not support signature because have no digital signature device(Very Expensive)
 Registration of House and population(registered by Federal Agency)

1.7 Methodology
1.7.1 Data Collection Technique

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 3

 Kebele Management System for 01 tuluawuliya Kebele

Data collection is the most important part of the project to find the main requirement of the
system and to understand how the system does. We have used different methods to collect data.
Among the methods, we used the following:

 Observation- we observed the current working system and how it manages

information or data and how they address information to the residences in the
Kebele.
 Interview: we interviewed the administratore of 01 tuluawuliya kebele staffs to
know how the existing system is working and provide information that means is
how files are stored in the kebele administration, the work flow, the problem, and
back ground of the kebele. Some basic questions regarding the following issues
will be asked during the interview:-
1. How does your current system work?
2. How many residences do you have?
3. Where do you keep residence information?
4. What are the majior steps to a customer get each service?
 Document analysis: We notice all written documents about the organizational
areas relevant to the system. Such as different forms used on the current system.

1.7.2 System Analysis and Design Methodology

We use the object oriented approach which examines requirements from the perspective of the
class and objects found in the problem domain. The reasons that we use the object oriented
approach are:

 We can inherit properties of the class that are defined in the super class.
 We can reuse methods for avoiding redundancy.
 The data and functions are encapsulated in the objects that help us for easily
debugging purpose.
 It enables us to comprehensively model a system before we develop it.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 4

 Kebele Management System for 01 tuluawuliya Kebele

1.8 System Development Model

Iterative model requires less time to design and to write document this means, we can start
implementation in early stage and back to requirement analysis at any stage if needed, because it
allows going backward and forward at any time. For example when we are doing something in
chapter two and error occurs in chapter one or any other chapter we can easily handle that error.
[2]

Figure 1-1 Iterative Development Model

1. Planning Phase: This is the first stage of the iterative model, where proper planning is done
by the team, which helps them in mapping out the specifications documents, establish software
or hardware requirements and generally prepare for the upcoming stages of the cycle.

2. Analysis and Design Phase: Once the planning is complete for the cycle, an analysis is
performed to point out the appropriate business logic, database models and to know any other
requirements of this particular stage. Moreover, the design stage also occurs in this phase of
iterative model, where the technical requirements are established that will be utilized in order to
meet the need of analysis stage.

3. Implementation Phase: This is the third and the most important phase of the iterative model.
Here, the actual implementation and coding process is executed. All planning, specification, and
design documents up to this point are coded and implemented into this initial iteration of the
project.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 5

 Kebele Management System for 01 tuluawuliya Kebele

4. Testing Phase: After the current build iteration is coded and implemented, testing is initiated
in the cycle to identify and locate any potential bugs or issues that may have been in the
software.

5. Evaluation Phase: The final phase of the Iterative life cycle is the evaluation phase, where the
entire team along with the client, examine the status of the project and validate whether it is as
per the suggested requirements.

1.9 System Development Tool

Tools that are used to develop this system are:

1.9.1 Hardware Tool

Table 1-1 Hardware Tool

No Item Type Amount Description

1 Laptop 1 with the following specification
1 TB disk space, 4 GB RAM
2 Flash Disk 2 For backup and file transfer.
3 Printer 1 To print the document.
4 Data Cable USB 1 To transfer files from mobile to PC.

1.9.2 Software Tool

Table 1-2 Software Tool

No Item Type Description

1 HTML For designing webpage and interface application.
2 JS Designing to add interactivity to HTML through validation.
3 CSS We have used it add style to HTML elements for decoration
and attractively
4 PHP We used it as a server script because of it run on different platform
like Linux, windows, and on other servers like Apache server.
5 XAMP server 2.5 We use it as server.
6 Adobe Photoshop For editing images and design some interfaces.
7 Notepad++ and VS Also for editing tool.
code
8 Google Chrome To run the system

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 6

 Kebele Management System for 01 tuluawuliya Kebele

1.9.3 Documentation Tools

Table 1-3 Documentation Tool

No Item Type Description

1 MS Visio For drawing UML diagram.
2 MS word 2010 Used for writing the document.
3 MS power Used for presentation purpose.
point2010/2007
4 Paper and pen Used to estimate and write the information about the project.

1.10 Significance of the project

 Reduce time wastage to assurance of ID card
 Reduce wastage of cost (paper and printing).
 Assures justice (Corruption and partiality)
 Customer to get information timely.
 It provides speed, efficiency, reliability and security.
 Faster decision making due to the report generation functionality.
 Supplies timely information for users and the users will be allowed to interact
with the system.

1.11 Feasibility study

This is a measure of how beneficial and practical development of the system which we want to
develop is studied. Measures time completion of the system, cost estimation and how much the
system is effective and it is also what benefits person, organization, populations and company get.
Feasibility study is a test of system proposal according to its workability, impact of the
organization, ability to meet needs and effective use of the resources. To consider this
feasibility we categorize as follows [2].

1.11.1 Operational feasibility

The system to be developed will provide accurate, active, secured service and decreases labor of
workers and also it is not limited to particular groups or body. And also it is platform independent
i.e. it run’s in all operating system. This makes our system feasible operationally.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 7

 Kebele Management System for 01 tuluawuliya Kebele

1.11.2 Technical feasibility

The technically feasibility of this system is to overcome the technical bug or error of the previous
system. Some of the technical feasibilities of this system are:-

 The availability of hardware and software tools

 The system will be developed using the object oriented development technique, so
the team members have enough knowledge of methodologies and tools to develop
this system.
Manpower: The proposed system will be friendly. Thus there is no requirement of highly
qualified staff in computers requiring. Anyone will understand easily only by giving little
training. Therefore the proposed system is financially feasible.

1.11.3 Economic feasibility

When we are looking towards the Economic feasibility of the system and also the system
constraints, we will develop the system using the existing resources. Reduce human labor
(money spend for payment reduced as the number of employs decrease). Generally in economic
feasibility the tangible and intangible benefits are considered. The following issues will use to
estimate the economic feasibility of the proposed system:

Hardware and Software Cost: The system needs no more complicated hardware and complex
software to install our system. Therefore the organization no needs to pay additional cost. This
will make the system economically feasible. Generally our proposed system cost estimation is
described in table 1.4 below

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 8

 Kebele Management System for 01 tuluawuliya Kebele

Table 1-4 Proposed System Cost Estimation

No Material Quantity in number Total Price

1 Human 19 116,000
2 Computer(laptop) 19 190,000
3 Printer 18 270,000
4 Flash 18 4,500
5 DSL Router 6 Cover by Tele 12,000
6 Switch 6 14,400
7 Network Cable 915meter 2,700
8 RJ45 300 900
9 Crimper 6 4,800
10 Network Cable Tester 6 3,000
11 Server Computer 1 280,000
Total 898,300

Table 1-5 Existing System Cost Estimation

No Material Quantity Total price

1 Human 90 345,600
2 Desktop computer 24 240,000
3 Printer 24 360,000
4 Flash 18 4500
5 Paper 432desta*200birr 86,400
6 File kent 600 30,000
7 Pen 2160 21,600
8 ID card published 21,000 315,000
9 Vital Certificate published 7800 390,000
10 Fuel,Carbon,Taxi,card 1 Year 108,000
Total 955500

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 9

 Kebele Management System for 01 tuluawuliya Kebele

1.12 Work Breakdown structure and Schedule feasibility

Time schedule is the most important consideration in the development of any project. The time
schedule required for the development of this project is very important since more development
time affect efforts; cost and cause delaying development of other system.Preparation of the
system will finish within given time interval.

Table 1-6 Time schedule

Time
Oct 25 -

Mar 12-

May16-
e2017-

Mar 10

Apr26-
May15
Apr 25
Nov10

June1
20D
Nov

Jan
Project Proposal

Requirement Analysis
System Design
Implementation &Coding

Testing

project Defense

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 10

 Kebele Management System for 01 tuluawuliya Kebele

2 CHAPTER TWO: SYSTEM ANALYSIS

2.1 Introduction to System Analysis

Software development life cycle encompasses the phases that a software developer goes through
when developing new software, it consists of five phases. Finding the domain problem is one of
the phases its aim is finding the analysis the domain problem of the current system, helps the
developer refine and structure the functional requirements. In the previous chapter we described
the background of the system, the problem of the current system, scope of the system, and the
feasibility of the system. In this chapter we will describe the detail overview of the current
system, problem of the current system, functional and nonfunctional requirement of the system,
business rules of the organization that helps to perform their activity efficiently and effectively
and analyzing the new system using different object-oriented UML modeling diagrams such as
Use case diagram, sequence diagram, class diagram, activity diagram and ER-diagram of the
system database [4].

2.1.1 Existing System

The current existing system is the Kebele Management System for 01 tuluawuliya kebele has
been done manually. This includes registration of Id and renew id, generate report, register vital
certificate are some important task and base for information to make plan for the society.

The Kebele has its own administrative rules to manage the society. Each person in the Kebele
must follow the principle of the Kebele. A person who wants to register and get other services in
the Kebele must fulfill the following criteria:

 A person must be resident and registered in the kebele.

 A person must be registered his or her family’s number.
 He or She must stay above 2 years in the Kebele, first he or she must be registered
in the system.
 If he or she comes from other Kebele, he or she must bring clearance from that
Kebele where he or she comes from.
 He or she should be above 18 years’ old to get id card

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 11

 Kebele Management System for 01 tuluawuliya Kebele

This is the result of lack of computerized system. When the project team was analyzing the
existing system, the team has tried to study the detailed nature and procedure of the tasks and
operations. The project team analyses the existing system problem as.

 Energy, time and resource wastage.

 The manager may load in work.
 The data in paper is less accurate.
 Difficulties in retrieving data.
 Difficulties in addressing services in time.

Figure 2-2 Existing system flow chart diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 12

 Kebele Management System for 01 tuluawuliya Kebele

2.1.2 Proposed System

The proposed system is an automated kebele management system for 01 tuluawuliya kebele in
ginba city that overcomes the existing system problems by conducting the works of the
organization. This system will develop to overcome mainly the time consumption and less
accuracy when filling forms in the existing system.The major thing in the proposed system is
authenticated users that means, Authorized one only access the system and prevented by user
name and password mechanism.

Hopefully the new system will solve these problems. The general overview of our proposed
system is to address the problem of the existing manual system and solves those entire problems
which are faced in the manual system. The new system able to save time and resources as well as
increases transparency of employees during implementation of kebele management system.

2.2 Functional Requirements

Functional requirements 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. Some of the functional requirements of this system are: -

System Administrator:

 Create accounts
 Activate the account
 Deactivate the account
 View account
 Manage Kebele

Kebele Manager:

 Give ID
 Renew ID
 Social Court service
 Post news
 Record new user
 Login into the system and logout

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 13

 Kebele Management System for 01 tuluawuliya Kebele

 Change password
 View Residence
Record officer:
 Birth certificates
 Divorce certificates
 Marriage certificates
 Death certificates.
 Report generate
 Login into the system and logout
 Change password

Customers: The customer get service form the kebele and participating in the Kebele issue.

2.3 Non-Functional Requirements

Fault tolerance:-We will make the system fault tolerance because of validation it cannot work
with error input.
Security:-Our system will be secured because it notify use strong password for every
authenticated user. As well as, sensitive datas like password are encrypted using different
algorithms in the database.
Accuracy:-The system will give accurate response to the correct input.
Scalability: - The system operates correctly when the number of user increases the system does
not depend on the number of employees we will import the information
Easy and User Friendly: - The system should be easy to learn, use, and understand it. The
system provides interfaces that are capable of being understood by every user so any interaction
with the system has no complexity to access all of its services.

2.4 Use Case Design

We use the use case to show the primary elements and processes that form the system. The
primary elements are termed as "actors" and the processes are called "use cases." The use case
diagram shows which actors interact with each use case.

An oval represents a use case such as create, view, give id, activate accounts, generate report etc.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 14

 Kebele Management System for 01 tuluawuliya Kebele

A stick figure represents an actor such as System administrator, kebele manager, record officer,
and customer.

Figure 2-3 Use case Diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 15

 Kebele Management System for 01 tuluawuliya Kebele

2.4.1 Actor Identification

In these system actors interacts with the system to perform meaningful work that helps us to
achieve a goal and has access to define overall role in the system and the scope of their action.
Actors of this system as follows

1. System Administrator: manages the user account and controls the activity of each user.
2. Kebele Manager: The kebele manager login to the system to Generate ID card, clearance,
generat report, Record new user, Social court service and post news.
3. Record officer: The record officer logs in, registration of the marriage, birth, divorced,
death certificates, and generat report.
4. Customer: view post

2.4.2 Use case Identification

We have used Use Case to identify, clarify, and organize system requirements. The use case is
made up of a set of possible sequences of interactions between systems and users in a particular
environment and related to a particular goal. It consists of a group of elements (for example,
classes and interfaces) that can be used together in a way that will have an effect larger than the
sum of the separate elements combined.

The Main Use Cases are:

 Login
 Manage Account (create, activate, deactivate, view, change password).
 Give ID card
 Renewed ID card
 Giving (mirraige, death, birth and divorce) certificates.
 Social court services(poor or not and marriage or not)
 Message
 Clearance(give and receive)
 Record new user
 Supportive letter
 Generate report

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 16

 Kebele Management System for 01 tuluawuliya Kebele

2.5 Use Case Description

Table 2-7 Use case Description for Login

Use case name Login

Use case id UC 1

Actor System Administrator, Kebele Manager, and Record officer.

Description The user enters authorized user name and password in order to access
the system.

Pre-condition The user should have user name and password.

Basic course of 1) The user clicks on login button.

action 2) The system will display a ‘login’ form that accepts user name and
password from the user
3) User enters user name and password.
4) Click the ’login’ button [A].
5) The system gets the user name from the database and matches it with
the password.
6) The use case ends
Alternative Course A1: If the entered user name and password is incorrect the system
of action A displays tray again message and go to step 3.

A2: End use case

Post condition The user login to the system.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 17

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-8 Use case Description for create account

Use case name Create Account

Use case id UC 2

Actor System Administrator

Description System Admin will Create Account for kebele manager, record officer.

Pre-condition The System Admin has login to the system

Basic course 1) Select ‘manage account’menu button.

of action 2) Click ‘create account’link
3) The system will display fields.
4) Enter user id, user name, password, re_password, role, email
5) Click ‘create’ button [A].
6) End use case.
Alternative A1: If the field is not correctly filled the system displays“please fill form”
course of and go to step 4.
action A
A2: End use case

Post condition The account will be created for the user.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 18

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-9 Use case Description for De-activate account

Use case name De-Activate Account

Use case number UC 3

Actor System Administrator

Description The system admin deactivates the users account when the user is out
of the organization.

Pre-condition The System Admin Login to the system and there should be account
with the user out of the organization.

Basic course of 1) Click ‘manage account’ link.

action 2) Select the user.
3) Turn Off the status.
4) Click ‘save change’ button.
5) End use case.
Post condition The system Administrator deactivates user account.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 19

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-10 Use case Description for activate Account

Use case name Active Account

Use case id UC 4

Actor System Administrator

Description The system admin Activates the users account during they back to their
work that has been deactivated.

Pre-condition The System Admin Login to the system and there should be deactivated
account.

Basic course of 1) Click ‘manage account’ link.

action 2) Select the deactivated user.
3) Turn ‘ON’ the status
4) Click ‘save change’ button.
5) End use case.

Post condition The system admin activates users account.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 20

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-11 Use case Description for Change Password

Use case name Change Password

Use case id UC 5

Actor System Administrator

Description System Admin Can change passwords for all actors if their password is
lost.

Pre-condition Have full privilege to do this task.

Basic course of 1) Login to the page.

action 2) Select Change Password link.
3) System displays registering forms.
4) Fills the required fields.
5) Change password.[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.
Post condition Can change password successfully.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 21

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-12 Use case Description for Give ID

Use case name Give ID

Use case id UC 6

Actor Kebele manager

Description Kebele manager can Give ID card for residences that lived more than 2
years and above and if their age is above 18.

Pre-condition The kebele manager has login the system and has an authorization for
giving ID card.

Basic course of 1) The kebele manager click on give ID card menu button
action 2) The system displays give ID card form
3) The kebele manager fills required field.
4) generate Id card.[A]
5) The system verifies that person is resident or not.
6) The system update list
7) The use case ends
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 3.
A2: Use case ends.
Post condition The kebele manager give ID for residences

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 22

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-13 Use case Description for Renew ID

Use case name Renew ID

Use case id UC 7

Actor Kebele manager

Description Kebele manager can Renew ID card for residences if their ID card is lost
or blurred.

Pre-condition The kebele manager has login the system and has an authorization for
renewing ID card.

Basic course of 1) The Kebele manager click on give ID card menu button
action 2) The system displays the form of renew ID card form
3) The kebele manager fills required field
4) System validate the required information is correct.[A]
5) The system update list.
6) The use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 3.
A2: Use case ends.
Post condition The ID card is renewed.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 23

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-14 Use case Description for Give Marriage Certificate

Use case name Give Marriage Certificate

Use case id UC 8

Actor Record officer

Description The Record officer can generate certificate for all residences become
married if they live in the kebele or if they have ID.

Pre-condition The Record officer has login the system and has an authorization for
generate Certificate.

Basic course of 1) Record officer login to the page.

action 2) Record officer select Mirriage Certificate link.
3) System displays Certificate forms.
4) Record officer fills the required fields.
5) System validate the required information is correct.[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.
Post condition The Record officer gives Certificate for residences.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 24

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-15 Use case Description for Give Birth Certificate

Use case name Give Birth Certificate

Use case id UC 9

Actor Record officer

Description The Record officer can generate certificate for all residences become
birth if they live in the kebele or if they have ID.

Pre-condition The Record officer has login the system and has an authorization for
generate Certificate.

Basic course of 1) Record officer login to the page.

action 2) Record officer select Birth Certificate link.
3) System displays Certificate forms.
4) Record officer fills the required fields.
5) System validate the required information is correct.[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.
Post condition The Record officer gives Certificate for residences.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 25

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-16 Use case Description for Give Divorce Certificate

Use case name Give Divorce Certificate

Use case id UC 10

Actor Record officer

Description The Record officer can generate certificate for all residences become
divorced if they live in the kebele or if they have ID.

Pre-condition The Record officer has login the system and has an authorization for
generate Certificate.

Basic course of 1) Record officer login to the page.

action 2) Record officer select Divorce Certificate link.
3) System displays Certificate forms.
4) Record officer fills the required fields.
5) System validate the required information is correct.[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.
Post condition The Record officer gives Certificate for residences.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 26

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-17 Use case Description for Give Death Certificate

Use case name Give Death Certificate

Use case id UC 11

Actor Record officer

Description The Record officer can generate certificate for all residences become
death if they live in the kebele or if they have ID.

Pre-condition The Record officer has login the system and has an authorization for
generate Certificate.

Basic course of 1) Record officer login to the page.

action 2) Record officer select Death Certificate link.
3) System displays Certificate forms.
4) Record officer fills the required fields.
5) System validate the required information is correct[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.
Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.

Post condition The Record officer gives Certificate for residences.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 27

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-18 Use case Description for Post News

Use case name Post news

Use case id UC 12

Actor Kebele manager.

Description Kebele manager can post news for residences with email.

Pre-condition Kebele manager has full privilege to do this task.

Basic course of 1) Login to the page.

action 2) Select Post News link.
3) System displays registering forms.
4) Fills the required fields.
5) System validate the required information is correct[A]
6) The system enters data into database and Display the success
message.
7) Use case ends.

Alternative Course A1: If the field is not correctly filled the system displays “please fill
of action A form” and go to step 4.
A2: Use case ends.
Post condition Post News Successfully

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 28

 Kebele Management System for 01 tuluawuliya Kebele

Table 2-19 Use case Description for Generate Report

Use case name Generate Report

Use case id UC 13

Actor The kebele manager and record officer.

Description Can full privilege to generate report.

Pre-condition The kebele manager and record officer have login the system and has an
authorization for generate Report.

Basic course of 1) Click ‘Generate report’ link.

action 2) The system generates the report.
3) Click ‘submit’ button.
4) End use case.
Post condition Report is submitted.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 29

 Kebele Management System for 01 tuluawuliya Kebele

2.6 Sequence Diagram

We use sequence diagram to design the interaction between different objects in the system.
Different objects in the sequence diagram interact with each other by passing "messages". A
sequence diagram is made up of objects and messages. Objects are represented exactly how they
have been represented in all UML diagrams as rectangles with the class name within the
rectangle. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or
objects that live simultaneously, and, as horizontal arrows, the messages exchanged between
them. [2]

Figure 2-4 Sequence diagram for create account

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 30

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-5 Sequence diagram for Login

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 31

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-6 Sequence diagram for Give Marriage Certificate

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 32

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-7 Sequence diagram for Give ID

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 33

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-8 Sequence diagram for Renew ID

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 34

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-9 Sequence diagram for Change password

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 35

 Kebele Management System for 01 tuluawuliya Kebele

2.7 Activity Diagram

We also use an Activity diagram to describe dynamic aspects of the system. Activity diagram is
basically a flow chart to represent the flow form one activity to another activity. The activity can
be described as an operation of the system. So the control flow is drawn from one operation to
another. This flow can be sequential, branched or concurrent. Activity diagrams also consists of
activities, actions, transitions, initial and final states, and guard conditions.

Figure 2-10 Activity diagrams for login

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 36

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-11 Activity

diagram for renew
ID

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 37

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-12 Activity diagram for create account

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 38

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-13 Activity diagram for give birth certificate

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 39

 Kebele Management System for 01 tuluawuliya Kebele

2.8 Class Diagram

We use it to refine the use case diagram and define a detailed design of the system. The class
diagram classifies the actors defined in the use case diagram into a set of interrelated classes. The
classes in a class diagram represent both the main objects, interactions in the application and the
classes to be programmed. In this system class diagram describes the structure of a system by
showing the system's classes, their attributes, methods, and the relationship among the classes.

Classes in this system are:

 System Adminnistrator
 Account
 Kebele manager
 Record Officer
 Marriage, birth, divorce and death
 Clearance
 Social court service
 Id
+ Represent public method
-Represent private method

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 40

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-14 Class diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 41

 Kebele Management System for 01 tuluawuliya Kebele

2.9 Data Structure Model

Entities in ER diagrams are represented in the form of rectangles or rounded rectangles. From
this system the entities are

 System Administrator
 Kebele manager
 Record officer
 ID
 Account
 Certificate
 Renew ID
 Customer
The diamond shape indicates relationship between from one entity to other entity. The
relationships for this system are

 System Administrator interacts with account by creates relationship.

 Record officer interact with account by has relationship.
 Kebele manager interact with ID by generate relationship.
 Record officer interacts with certificate by generate relationship.
The ellipse shape indicates attributes s of each entity. The attributes for this system are:

 System Administrator attributes are ID, sex, username, password phone number...etc.
 Account has attributes like user name, password etc.
 Record officer has attributes like ID, sex, name, etc.

2.9.1 Entity-Relationship (ER) Model

We have used the entity relationship diagram to show the entities and their attributes in
the system. The E-R data model is based on aperception of areal world that consists of
asset of basic objects called entities, and of relationships among these objects. There
are three basic notions that the ER Model: entitysets, relationships, and attributes.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 42

 Kebele Management System for 01 tuluawuliya Kebele

Figure 2-15 EntityRelationship Diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 43

 Kebele Management System for 01 tuluawuliya Kebele

3 CHAPTER THREE: SYSTEM DESIGN

3.1 Purpose and Goals of Design

3.1.1 Introduction
Web-based Kebele management system design document describes the proposed system in
detail. It also presents the proposed system architecture and decomposition into its manageable
subsystems. It presents the requirement information that is previously dealt in the requirement
analysis part of the RAD (requirement analysis document) in a more simplified and specific way
for the implementation of the new system so that it achieves the system specifications identified
during requirement analysis. This document provides list of design goals, hardware/software
mapping, access control and boundary conditions in addition to presenting the proposed
architecture, its components and the persistent data management. [2]

3.1.2 Purpose of Design

System design is a phase which provides a blueprint for implementation, testing and maintaining
the system. As we have stated in the requirements analysis and system modeling and data
description phases, the proposed system is aimed and going to be designed to attain
computerized system. System design is the transformation of the analysis model into a system
design model. System design is the first part to get into the solution domain in a software
development. The result of the system design is the model that includes the clear description of
software Architecture, Deployment diagram, and system persistent diagram.

Generally, the purpose of this design phases is to determine how to build the system and the
information needed to device the actual implementation of the project.
3.1.3 Design Goal

The design goals are derived from non-functional requirements that means non-functional
requirement is the description of the feature characteristics and attribute of the system as well as
any constraints that may limit the boundary of the proposed solution.

Design goals describe the qualities of the system that the developers should consider.
Portability: -The systems operate on desk top and laptop as well as other devices.
Access security: -The user log in password shall not been known by others.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 44

 Kebele Management System for 01 tuluawuliya Kebele

-The user login password shall be at list eight characters

-The user password shall contain special characters

Scalability: - The system operates correctly when the number of user increases.
Fault Tolerance: The system should be able to give response (error message) when the user
enters incorrect input. This recommends the user to enter correct input.
Easy: The system is easy to learn, use, understand or deal with. The system provides interfaces
that are capable of being understood by every user so any interaction with the system has no
complexity to access all of its services.

3.2 Current Software architecture

Currently, 01 tuluawuliya kebele don’t have any kind of automated works, because the current
system is manual, so there is no software architecture

3.3 Proposed Software Architecture

The architecture that we have used for the system is a 3 tier which is a web-based application in
which the presentation tier, a business or data tier, and a data tier are developed and maintained
as independent modules on separate platforms. Three layers in the three-tier architecture are as
follows

1. Client (Presentation) Tier The client tier is the applications of user interface containing
data entry forms and client side applications. The client tier interacts with the
web/application server to make requests and to retrieve data from the database. It then
displays to the user the data retrieved from the server.
2. Middle (Application) Tier The middle tier (web/application server) implements the
business logic, controller logic and presentation logic to control the interaction between
the applications clients and database. The controller logic processes client requests such
as request to view questions, answers, search questions or forum, deactivate or activate
data from database.
3. Database (Data) TierThe system has data access layer which requires SQL skill in the
form of DDL and DML contains methods to connect with database and to perform insert,
update, delete, get data from database based on users input data.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 45

 Kebele Management System for 01 tuluawuliya Kebele

Figure 3-16 Proposed software architecture

3.3.1 System Decomposition

Any system can be decomposed in to different sub system based on the functional services. A
subsystem is characterized by the services it provides to another sub system. Services are a set of
related operations that has a common purpose. In order to make the implementation easy and
manageable, the newly developed system decomposed in to the smaller subsystems. Subsystem
decompositions will help to reduce the complexity of the system. The sub systems that we take
the classes that our systems contain and the operation performed in the class.

3.3.2 SubSystem Decomposition

System decomposition refers to the process by which a complex problem or system is broken
down into parts that are easier to conceive, understand, program, and maintain. To reduce the
complexity of the solution domain, we decompose our system into simpler parts, called
subsystems, which are made of a number of solution domain classes. In the case of complex
subsystems, we recursively apply this principle and decompose a sub- system into simpler
subsystems. This system decomposition shows the existence of the following subsystems.

System Administrator Sub System:

 Create accounts
 Activate account
 Deactivate account
 Change Password

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 46

 Kebele Management System for 01 tuluawuliya Kebele

 Manage kebele
 View Account

Kebele Manager Sub System:

 Give ID
 Renew ID
 Generate Report
 Post news
 Clearance
 Social court Service
 Supportive letter
 Post news
Record officer Sub System:
 Give birthcertificates
 Give divorce certificates
 Give marriagecertificates
 Give death certificates.

Customers Sub System:

 View Post News

3.3.3 Component diagram

In this Diagram components of the system will be wired showing that there is relation among
components, management of the system, database and operations performed on databases some
security issue. This in some extent shows which component or objects will be accessed by whom
and what type of security infrastructures it is using. The diagram is draw as the following:

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 47

 Kebele Management System for 01 tuluawuliya Kebele

Figure 3-17 Component Diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 48

 Kebele Management System for 01 tuluawuliya Kebele

3.3.4 Deployment diagram

Deployment modeling is used to show the hardware of the system, the software that is installed
in the hardware and also the middleware that is used to connect the dissimilar machines to one
and other. It also shows how the software and the hardware components work together in order
perform thetask.

Figure 3-18 Deployment Diagram

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 49

 Kebele Management System for 01 tuluawuliya Kebele

3.3.5 Persistent Data management

Persistent data management is basically used to represent the design of the database, usually a
Relational Database. Database design is the process of producing a detailed data model of a
database. This logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a Data Definition Language, which
can then be used to create a database. Database design describes many different parts of the
design of an overall database system. Database designs also include ER (Entity-relationship
model) diagrams. An ER model ER model is an abstract way of describing a database. Design
process of a database includes:

1. Determine the purpose of the database.

2. Divide the information into tables.

3. Turn information items into columns.

4. Specify primary keys.

5. Set up the table relationships.

6. Modelling for object oriented database

3.3.6 Access Control and Security

The access control for the woidiatownkebele management system will be implemented through
the capabilities lists such as

 The capability associates a (class, operations) paired with an actor.

 A capability allows an actor access to the operation of the class.
 Specify how actors can control access and define how they are authenticated to the
system.
The following table shows the capability list of tuluawuliya kebele management system.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 50

 Kebele Management System for 01 tuluawuliya Kebele

Table 3-20 Access control and Security

Operation Actors
System Admin Kebele Manager Record Officer Customer
Login ()

Create
Account ()
Deactivate
account ()
Manage
kebele ()
Give Id ()
Renew Id ()
Generate
Report ()
Post News ()

Clearance ()

Marriage()

Birth()

View Post ()
Logout ()

3.3.7 Boundary Condition and Exception Handling

3.3.7.1 Exception Handling

Users may provide invalid information (like string for integer, etc), when the system reach such
kinds of exceptions, the system provide the correct information suggests the user to provide the
correct input. In this system there is a login form, if the user does not enter correct user name and
password, the system displays an error message and let them to try again.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 51

 Kebele Management System for 01 tuluawuliya Kebele

 The system displays messages if it is tried to access using wrong/invalid account by

checking against the account table.
 If the user tries to access to another privilege, the system should displays enter the
correct password.
 If the employee’s, account is deactivated by the system admin, he cannot login to the
system

3.3.7.2 Boundary Condition

Tuluawuliya kebele management system will have boundary conditions to start, shutdown, and
handle failures of the system.This system is going to formulate the recognition of the kebele by
providing services like give id, register house, register population, generate report etc to the
kebele. Therefore, the system is not expected to be started and shutdown at all times rather the
system should be available all the time to support different services to the residents of the kebele

3.4 User Interface Design

User interface prototype is to indicate the surface that can be used by user and the system. This
method involves a series of iterations and refinement until the prototype product is a fully
working system, and the user is satisfied. The process of prototyping identifies basic requirement
including the input and output information desired details, such us security, can typically be
ignored. The initial prototype is developed that includes only user interfaces. Here, the
implemented system is described. How the user interacts with the system and some of the results
of interaction with the system along with the screen shots are described. When a user starts the
application, a login screen is displayed as shown. The reasons of using prototype models are

 Since in this methodology a working model of the system is provided the users get a
better understanding of the system being developed.
 Error can be detected much earlier
 Qucker user feed back is available leading solution.missing functionality can beidentified
easily
 Confusing or difficult function can be identified requirements validation, quick
implementation of in complete, but functional, application.

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 52

 Kebele Management System for 01 tuluawuliya Kebele

Figure 0-19 User Interface Proto Type

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 53

 Kebele Management System for 01 tuluawuliya Kebele

REFFERENCE:
[1] D. James, "Google," UML Use Case Dessign, 3 may 2018. [Online]. Available:
https://www.smartdraw.com/use-case-diagram.html. [Accessed 22 Jan 2020].
[2] C. Robin, "google," Soft Ware Engineering, 3 September 2016. [Online]. Available:
https://www.smartdraw.com/sequence-diagram. [Accessed 2 Dec 2020]
[3] Wikipedia, the free encyclopedia(en.wikipedia.org)
[4] )1 tuluawuliya management system Documents 2015G.C, Ginba

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 54

 Kebele Management System for 01 tuluawuliya Kebele

APPENDICES
Annex 1 Existing system forms for Birth and MarriageResidence

Annex 2Existing system forms for ID card

Mekdela Amba University Computer Science Graduate Students (2015EC). Page 55