DEPARTMENT OF COMPUTING TECHNOLOGY

Aksum University

College of Engineering and Technology

Department of Computing Technology
Program of Information Technology
Final Project
On
Passport Management System

BY:

Efrem G/Tsadkan………………………AKUR/1819/05
Dagmawi Tadesse………………………AKUR/0849/05
Brhane G/Yesus ………………………...AKUR/1812/O5

Adviser Name : MR Abay Teshager (MSC)

February 9/2016
 DEPARTMENT OF COMPUTING TECHNOLOGY

EXIMANER NAME SIGNATUR

1…………………………………………….. ………………

2……………………………………………… ………………

3……………………………………………. ………………

4……………………………………………… ………………

5……………………………………………….. ………………

6………………………………………………… ………………

ADVISER NAME : MR Abay Teshager (MSC) SIGNATURE…………………….

 DEPARTMENT OF COMPUTING TECHNOLOGY

ACKNOWLEDGMENT
First of all we want to thank the almighty ‘GOD’ keep our safe, staying power and energy
starting from to get in to the friendship up to the day we have finished this project successfully.
Secondly we would want to . A special thanks to our final year project advisor instructor MR
Abay Teshager for his guidance, understanding, patience and most importantly, his friendship
during the project work.

And thirdly we want to express our gratitude to our department of computing and technology for
supporting us with all we need and encourage us to develop our final year project.
 DEPARTMENT OF COMPUTING TECHNOLOGY

ACRONYMS AND ABBREVIATION

 ICAO: International civil aviation organization

 PIN: personal Identification number
 XLS: Microsoft Excel
 ASP :Active Server Page
 UML: Unified Modeling Language
 Html: Hypertext Manipulating Language
 CSS: Cascading Style Sheets
 HDD: Hard Drive Disk
 RAM: Random Access Memory
 SDK: Software Development Kit
 SQL: Structured Query Language
 AMD: Advanced Micro Devices
 MDA: Model Driven Architecture
 ER: Entity Relationship
 DEPARTMENT OF COMPUTING TECHNOLOGY

OPERATIONAL DEFINITIONS

Administrator……….generates report and Manages all the system

Customer……………gets service from the passport management system

System………………That done all process and it is centralize between the customer and
administrator

Bank System………..The System that accept payment and transfer payment

Web-based online…..passport management system is Internet based and can reserve at any
place.

Front-end…………...This is a interface that collaborate users and system

Back end…………….This is interacting with database and it is hidden to users
User………………….officer – Client –employee
 DEPARTMENT OF COMPUTING TECHNOLOGY

LIST OF TABLE page

Table 1 actors and their responsibility...........................................................................................21

Table 2 use case description for login...........................................................................................27
Table 3 use case description for logout.........................................................................................28
Table 4 use case description create account..................................................................................29
Table 5 use case description manage account..............................................................................30
Table 6 use case description view account...................................................................................30
Table 7 use case description manage customer............................................................................31
Table 8 use case description post feedback..................................................................................32
Table 9 use case description view feedback.................................................................................32
Table 10 use case description view complain...............................................................................33
Table 11 use case description create account...............................................................................34
Table 12 use case description manage appointmet.......................................................................34
Table 13 use case description generate report..............................................................................35
Table 14 use case description manage branch..............................................................................35
Table 15 use case description send notification...........................................................................36
Table 16 use case description payment........................................................................................37
Table 17 use case description view payment................................................................................37
Table 18 use case description view notification...........................................................................38
Table 19 use case description view appointment.........................................................................39
Table 20 use case description capture biometric image...............................................................39
Table 21 use case description generate production order..............................................................40
Table 22 use case description manage news.................................................................................40
 DEPARTMENT OF COMPUTING TECHNOLOGY

LIST OF FIGURES page

Figure 1 use case diagram..............................................................................................................23

Figure 2 use case diagram for administrator..................................................................................24
Figure 3 use case diagram for customer........................................................................................25
Figure 4 use case diagram for officer............................................................................................26
Figure 5 Sequence diagram for user login.....................................................................................41
Figure 6 Sequence diagram for create account for users except customer....................................42
Figure 7 Sequence diagram when customer create account for his personal use..........................42
Figure 8 Sequence diagram when manage account for administrator edit account.......................43
Figure 9 Sequence diagram when manage account for administrator delete account...................43
Figure 10 Sequence diagram for view account by administrator..................................................44
Figure 11 Sequence diagram when manage customer for administrator view customer detail....45
Figure 12 Sequence diagram for view customer...........................................................................45
Figure 13 Sequence diagram when manage account for administrator view denied customer.....46
Figure 14 Sequence diagram when manage profile for customer update profile..........................46
Figure 15 Sequence diagram when manage profile for customer add profile...............................47
Figure 16 Sequence diagram for view feedback by administrator................................................47
Figure 17 Sequence diagram for post feedback by customer........................................................48
Figure 18 Sequence diagram for complain handling by administrator..........................................48
Figure 19 Sequence diagram for view complain by officer..........................................................49
Figure 20 Sequence diagram when update appointment by administrator....................................49
Figure 21 Sequence diagram when arrange appointment by administrator..................................50
Figure 22 Sequence diagram for generate report by Administrator..............................................51
Figure 23 Sequence diagram when manage branch for administrator create account...................52
Figure 24 Sequence diagram when manage branch for administrator update account.................53
Figure 25 Sequence diagram when manage branch for administrator delete account...................54
Figure 26 Sequence diagram for Send notification by Administrator...........................................55
Figure 27 Sequence diagram for view notification by customer...................................................55
Figure 28 Sequence diagram for payment by customer................................................................56
Figure 29 Sequence diagram for view payment by users..............................................................57
Figure 30 Sequence diagram for view appointment by customer.................................................57
Figure 31 Sequence diagram for capture biometric image by officer...........................................58
Figure 32 Sequence diagram for generate production order.........................................................59
Figure 33 Sequence diagram for post news by Administrator......................................................59
Figure 34 Class Diagram of passport management system...........................................................60
Figure 35 system decomposition for web based for passport management system......................63
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 36 system architecture diagram..........................................................................................64

Figure 37 deployment diagram for passport management system................................................65
Figure 38 Persistent data management for passport management system.....................................67
Figure 39 user interface design for login home page....................................................................69
Figure 40 user interface design for customer home page..............................................................70
Figure 41 user interface design for customer signup form............................................................70
Figure 42 user interface design for administrator home page.......................................................71
Figure 43 user interface design for create new user......................................................................71
Figure 44 user interface design for officer home page..................................................................72
 DEPARTMENT OF COMPUTING TECHNOLOGY

TABLE OF CONTENTS
ACKNOWLEDGMENT...................................................................................................................................iii
ACRONYMS AND ABBREVIATION................................................................................................................iv
OPERATIONAL DEFINITIONS........................................................................................................................v
LIST OF TABLE.............................................................................................................................................vi
LIST OF FIGURES.........................................................................................................................................vii
TABLE OF CONTENTS..................................................................................................................................ix
CHAPTER ONE..............................................................................................................................................1
1.1 INTRODUCTION...............................................................................................................................1
1.2 BACKGROUND OF THE ORGANIZATION...........................................................................................2
1.3 STATMENT OF THE PROBLEM..........................................................................................................4
1.4 JUSTIFICATIONOF THE PROJECT.......................................................................................................5
1.5 OBJECTIVES......................................................................................................................................5
1.5.1 GENERAL OBJECTIVE.......................................................................................................................5
1.5.2 SPECIFIC OBJECTIVES......................................................................................................................6
1.6 PURPOSE OF THE PROJECT..............................................................................................................6
1.7 SCOPE OF THE PROJECT...................................................................................................................7
1.8 METHODOLOGYOF THE PROJECT....................................................................................................8
1.8.1 DATA COLLECTION METHODS........................................................................................................8
1.8.2 SYSTEM ANALYSIS AND DESIGN METHODOLOGY..........................................................................8
1.8.3 IMPLEMENTATION METHODOLOGY...............................................................................................9
1.8.4 SYSTEM TESTING.............................................................................................................................9
1.8.5 DOCUMENTATION METHODOLOGY...............................................................................................9
CHAPTER TWO...........................................................................................................................................10
REQUIREMENT ANALYSIS DESCRIPTION....................................................................................................10
2.1 INTRODUCTION.............................................................................................................................10
2.2 OVERVIEW OF THE EXISTING SYSTEM............................................................................................10
2.2.1 ACTIVITIES OF THE EXISTING SYSTEM...........................................................................................10
2.2.2 PROBLEM OF EXISTING SYSTEM...................................................................................................11
2.2.3 SWOT OF THE EXISTING SYSTEM..................................................................................................12
 DEPARTMENT OF COMPUTING TECHNOLOGY

2.2.3.1 STRENGTH OF THE CURRENT SYSTEM....................................................................12

2.2.3.2 WEAKNESS OF THE CURRENT SYSTEM...................................................................12
2.2.3.3 OPPORTUNITIES OF EXISTING SYSTEM...................................................................13
2.2.3.4 THREATS OF EXISTING SYSTEM................................................................................13
2.2.4 BUSINESS RULE.............................................................................................................................13
2.3 OVERVIEW OF THE PROPOSED SYSTEM.........................................................................................14
2.3.1 FUNCTIONAL REQUIREMENTS......................................................................................................15
2.3.2 NON FUNCTIONAL REQUIREMENTS..............................................................................................16
2.3.3 SYSTEM REQUIREMENT................................................................................................................17
2.3.3.1 HARDWARE REQUIREMENT...........................................................................................17
2.3.3.2 SOFTWARE REQUIREMENT........................................................................................................18
2.3.4 CONSTRAINTS...............................................................................................................................18
2.3.5 ASSUMPTIONS..............................................................................................................................19
CHAPTER THREE........................................................................................................................................20
SYSTEM MODELING...................................................................................................................................20
3.1 INTRODUCTION.............................................................................................................................20
3.2 USE CASE MODEL...........................................................................................................................20
3.2.1 ACTOR SPECIFICATION...........................................................................................................20
3.2.2 USE CASE DIAGRAM...............................................................................................................21
3.2.3 USE CASE DESCRIPTION.........................................................................................................27
3.3 SEQUENCE DIAGRAM.....................................................................................................................41
3.4 CLASS DIAGRAM............................................................................................................................60
CHAPTER FOUR..........................................................................................................................................61
SYSTEM DESIGN.........................................................................................................................................61
4.1 INTRODUCTION.............................................................................................................................61
4.2 DESIGN GOALS...............................................................................................................................61
4.3 SYSTEM DECOMPOSITION.............................................................................................................62
4.4 SYSTEM ARCHITECTURE.................................................................................................................64
4.5 DEPLOYMENT DIAGRAM FOR PASSPORT MANAGEMENT SYSTEM................................................64
4.6 PERSISTENT DATA MANAGEMENT.................................................................................................65
4.7 ACCESS CONTROL AND SECURITY..................................................................................................67
4.8 USER INTERFACE DESIGN...............................................................................................................69
 DEPARTMENT OF COMPUTING TECHNOLOGY

5 REFERENCE........................................................................................................................................73
 DEPARTMENT OF COMPUTING TECHNOLOGY

CHAPTER ONE

1.1INTRODUCTION
According to www.tethyssolutions.com below is little consideration to keep in mind when
evaluating automation software. The first one is does automation software offer task recorder
capabilities? If it provides task recorder capabilities it would be easier for the user to record a
script and edit it instead of writing an automation script from scratch. Secondly, is it easy to
learn? Automation software by definition has some automation commands and how to create an
automated task manual. Is it easy to learn, does it offer wizard based task creation or do you have
to learn a new programming language? Thirdly, how easy is it to edit a macro or automation
script? Does it provide easy edit features?
Accordingtowww.dictionary.reference.com, automation is defined as
the technique, method, or system of operating or controlling a processby highly automatic means
by electronic devices, reducing human intervention to a minimum. Automating repetitive
procedures can provide real value to software development projects.
Passport is an official document that enables people to travel legally across national borders. The
role of a passport is to identify citizens a state for the benefit of foreign countries and to
guarantee their right of return.
The ideal structure of online passport registration provides security to the passports to be
registered wherein we can fill all the details in an efficient and easy manner. A passport is a
document, issued by a national Government. This certifies, for the purpose of international
travel, the identity and nationality of its holder. The Elements of identity are name, date-of-birth;
sex and place of birth most often, most often nationality and citizenship are congruent. A
passport does not of itself entitle the passport holder entry into another country, nor to consular
protection while abroad or any other privileges it does. However normally entitle the passport
holder to return to his country that issued the passport. Rights to consular protection arise from
international agreements, and the right to return arises from the laws of issuing country. An
individual can register for a passport irrespective of his/her age. The registration of passport is a
major step for issuing of a passport. It is system or process in which an individual has to provide
exact details of his /her personal information and residential information. Proper registration of a
passport is very vital as all the detail filled by the individual are depicted on the passport that is
 DEPARTMENT OF COMPUTING TECHNOLOGY

issued.
National passports for citizens and visa systems for non-residents manage the orderly movement
of people between states on temporary or permanent basics.
The movement to standardize passports that began decades ago as efficiency measure has now
evolved into a crucial security tool as well. Greater security measures are being introduced by
many states in response the threat of global terrorism. Ethiopian passport managers are assessing
the need to upgrade the quality and security of their passport in response to global security
threats.
Increased security is one of the highest priorities for governments and transportation carriers.
The foundation for international travel security is proof of identity and citizenship. The passport
is also important for the protection and support of a state’s citizen’s abroad.
This chapter describes about the project background, problem statements, objectives, scopes,
project significance, the methodology and finally the conclusion for this chapter. The project
background describes about the historical information about the Immigration and National
Affairs Ethiopia with particular emphasis on the passport management system. Meanwhile, the
problem statements describes about the problems faced by the office in the current system
whereas the objectives are the aims to solve the problems. The project scope covers the system
functionalities. The project significance states the importance of this project and the parties that
will gain benefits from it. Finally, the methodology is about the methods approaches and tools
used in doing this project and lastly are the conclusion that concludes this chapter.
1.2 BACKGROUND OF THE ORGANIZATION
The basis for orderly international travel is credible proof of identity and citizenship. The
passport is the universal official document used to identify persons and their
citizenship. It also provides sufficient for international travel. Therefore, passports are
linked directly to citizenship laws. However, a passport alone may not be assurance to the
country of transit or destination that the bearer can return to the country of issue.
In 1920, the League of Nations convened a conference to adopt standard passport and visa
formats for all signatory States, with uniform provisions governing their layout, content,
validity, and issuing fees. A second conference, in 1926, set additional specifications for
and improvements to the standard international passport format.
 DEPARTMENT OF COMPUTING TECHNOLOGY

ICAO involvement in passports started with the initial draft of Annex 9 (Facilitation) to the
Chicago Convention, as recommended by the First Session of the ICAO Facilitation (FAL)
Division in 1946 the draft contained a simplified model passport card for non-immigrants, as well
as various provisions governing the issuing of visas and other identity documents.
The rapid growth of international air passenger traffic prompted the ICAO Facilitation
Division in 1968 to consider proposals for the introduction of a machine-readable passport or
passport card that might eventually replace the conventional passport and accelerate clearance
through passport controls.
ICAO established the Panel on Passport Cards in November 1968,comprising members
from ten contracting States. The International Criminal Police Organization (INTERPOL) and
the International Air Transport Association were invited to participate as observers. The Panel
developed recommendations for the production and use of machine-readable passports.
ICAO Doc 9303 - A Passport with Machine Readable Capability was published in 1980 and
became the basis for the initial issue of machine-readable passports by Australia, Canada, and the
United States who pioneered the change in the production and issuance of such passports.
In 1981 and 1982, the European Community adopted resolutions calling for its contracting States
to issue uniform passports by 1 January 1985 and stipulating that the personal information items
of the issue uniform passports by 1 January 1985 and stipulating that the personal information
items of the standard European passport should follow the specifications found in ICAO Doc
9303. In 1986, ICAO established a new group, the Technical Advisory Group on Machine
Readable Travel Documents for which the terms of reference were broadened to include the
development of specifications for machine-readable visas and other official travel documents.
The fifth edition of the Passport Specification, Doc 9303, Part 1 was published in 2002. Building
on the earlier decision to expand the scope of the Technical Advisory Group on Machine
Readable Travel Documents, the Visa Specification, Doc 9303, Part 2 Had been published in
1994, and the specifications for Official Travel Documents (cards), Doc 9303, Part 3 were
published in 1996 and updated in 2002.
 DEPARTMENT OF COMPUTING TECHNOLOGY

1.3 STATMENT OF THE PROBLEM

The first problem in the current passport managment system is its difficulty in searching
customer’s documents. According to the Observation the data recorders register 500 new
customers per week and for these new customers it needs three sheets per each new customer.
And 1500 sheets are needed to register the basic information of the customer’s. These data was
recordedonly in one week. Besides for these activities, in one month they recorded above 60, 000
sheets. So, when the coustomer record is needed to update, edit, view, delete in the organization,
the data store keeper makes difficult to search and cannot get the profile of customers when
request.

The second problem in the current system is its economic problem. This problem has tow faces.
(Stationary materials and storage) The current passport managment system needs on data
recorder for recording the coustomers documents, In addition the current system also uses 1500
papers to register new customer in one week. So this current system is economically infeasible.
The third problem in the existing system is data redundancy and inconsistency. When the
coustomers document is lost while searching, then the coustomers is required to fill all the
information again. In this case the registration of coustomers information is redundant. And the
data inconsistency occurs when the coustomers registration is redundant and the registration of
coustomers information is not consistence.
The other main problem of the current passport managment system is in the payment handling.
In the current system the payment is made by physically going to the organization and the
service of the organization is not efficient, and this payment system is not comfortable to the
customers and the employees in the organization. Besides in case the physical payment, the
customer may not able to save his time and energy.
The last problem is in generating a report. The current system the report generation is made by
first searching the detail document of the coustomers, and their payment documents. It is error
prone in generating reports like numbers of registered coustomers, count the number of the
coustomers who paid.
 DEPARTMENT OF COMPUTING TECHNOLOGY

1.4 JUSTIFICATION OF THE PROJECT

As long as our knowledge is concerned, this project is the first attempt to develop Passport
Management System in Ethiopia.

The reasons why the passport managment system is still manual could include the following
reasons. The first reason could be the complexities or difficulties to use these software’s, either
they require very long time to master their way of workings because they didn’t contain all
necessary functionalities, help contents or training end users or not made with specific customer
requirements (made for general types). Because of these reasons the office managerial bodies
and end users get trouble using these software products.

The second reason is the expensiveness of business software’s available in the market. Moreover
passport managment system uses manual filling forms and after that Microsoft Excel to maintain
record in the office this method is better from doing it on papers, but this method has its own
limitation. And the way of workings are vulnerable to threats, not efficient and not effective.

Hence, there is a need of reformation of the system with more advantages and flexibility. Making
this system to web-based, eliminates most of the limitations of the existing software by
enhancing and upgrading the existing system and making very easy to work on it, by providing
accuracy along with a pleasant interface, by increasing its efficiency, effectiveness and
throughput with minimum time, effort and cost and maximum security and data availability
whenever and wherever needed.

1.5 OBJECTIVES

1.5.1 GENERAL OBJECTIVE

The general objective of this project is to develop a Passport Managment System for the
organizationof Immigration and National Affairs in Ethiopian.
 DEPARTMENT OF COMPUTING TECHNOLOGY

1.5.2 SPECIFIC OBJECTIVES

To achieve the general objective, this project sets out the following specific objectives.
 To Design a system considering the current capabilities and needs of the customers.
 To select an appropriate software development methodologies for the development of the
software.
 To develop a program (code) of the selected software development methodology using
Active Server Page (ASP) programming language.
 To test the performance of the system with real time data prepared by the office and by
the development team.
 To draw conclusion and forward recommendations for further projects.
1.6 PURPOSE OF THE PROJECT
The first significance of the system is to make easier the customers activities in many aspects.
For instance, the passport managment system starts to serve new customers easily without any
kind of confusion, wastage of time and interruption. Here, the administratorr, branch manager,
and officer simply guide customers what to do. Beside of this, customers also get efficient
service without any confusion, because they already know all about their scheduling payment,
registration information, etc.

The second beneficiary of the system is the organization. Firstly, the environment is changed to
a computerized environment, which improves the quality of internal operations as well as
services given to customers.Secondly, the problem associated with manual processing is
minimized and the quality of work and services became improved.

The other beneficiaries of the system are the workers in the office. Once the new system is
implemented, the workers are benefited from the system in such a way that the quality and
performance of their work is improved, the time they spent for manual operation is significantly
reduced and their management and control of their job is improved.
 DEPARTMENT OF COMPUTING TECHNOLOGY

1.7 SCOPE OF THE PROJECT

The passport managment system will be flexible, user friendly and features a very high level
automation. This gives the system flexibility and capability to deliver excellent customer service
and operate very efficiently with a minimum number of staff. The main modules to be handled
by this system will be:

 Customer Registration and Give Appointment: This module takes care of new
customer registration to create an account. During this registration, the Personal
Identification Numbers (PIN) is given by the adminstrator to the customers. The system
will take this PIN as appointmentschedle number. This module createscustomer’sbasic
personal information and an appointment date.And alsso this moduleProvide Passport
issue regulations and expectation of rules and regulations to get appointment date.
 Customer Handling:After customer registration all activities that need manage customer
profile, captureimage,capture finger print, capture digital signature, Handle customer
complain,send notification,renewal passport and manage customer will be handled by
this module. “Manage customerprofile” sub module will process the update, delete, and
handling of personal information. “Capture image”sub module will take care ofcapture
face image and add to the customer profile. “Capture fingerprint”sub module will take
care ofcapture fingerprintand add to the customer profile. “Capture digital signature “sub
module will take care of digital signatureand add to the customer profile. “Handle
customer complains” sub module will take care of handling of feedback for complains
and mistakes in spelling and numbering errors in the passport. “Send notification”sub
module will take care of notification of arrival of passport using the email of the
customer.“Renewal passport”sub module will take care offor renew passport based on the
appointments.“Manage customer”sub module will take care of managing customer
details, view confirmed customer and view denied customer.
 User Management: This module defines access restrictions and user management by
using roles. There are four level hierarchies of users based on roles. Such as customer,
administrator, office manager, branch manager. Features include: Administrator Creates
User, View User, Customer Change Password and Username and User Data Entry Status.
 Branch Management: This module defines access branch and update, delete and create
 DEPARTMENT OF COMPUTING TECHNOLOGY

the branch by their location.

 Report Generation: reports should be generated to be delivered to the concerned bodies
based on the office reporting frequency. Generate and vies reports on the total number of
customers who take the passport and who didn’t take the passport. Reports can be exported to
XLS (Excel) and PDF file. This module prepares monthly, quarterly, and annual reports.
 Payment Processing: This module takes care of customer payment to Receipt Delivery
and payment handling. “Receipt Delivery”this sub module delivers receipt to the
customers after their successful payment. “Payment Handling” this sub modules control
credit, debit and check balanceaccount of the customer.
 News and feedback management: This module takes care of managing news and
manages feedback. “Manage news” this sub module will take care of news edit, update
and delete the news. “Manage feedback” this sub module will take care of view feedback
and delete feedback.

1.8 METHODOLOGYOF THE PROJECT

1.8.1 DATA COLLECTION METHODS

To get a precise data from the organization we used the following data collection methods.
Observation: We select observation to know the real world environment of the organization
manual working. And to work the desired application of the passport managment system. In the
observation part we observe how service is delivered to the Tigray community. Totally, we have
an observation time for 2 hours in to two phases of time.
Document Analysis: we select the document analysis to know how the current system works .in
addition to this we used this analysis to know the manually operated forms. For example the
customers registration forms, payment handling forms, etc.
1.8.2 SYSTEM ANALYSIS AND DESIGN METHODOLOGY

To analyze the collected data, the project follows an Object Oriented Analysis and Design
Approach. This is because of its improved usability of objects and classes, easier maintenance
and easy to understand. The methodology used for analysis and design is Unified Modeling
Language (UML) 5.02. Specifically, use case diagrams, sequence diagrams and class diagrams
are used to analysis the current system while deployment diagram, decomposition diagram are
 DEPARTMENT OF COMPUTING TECHNOLOGY

used in the design phase.

1.8.3 IMPLEMENTATION METHODOLOGY
The objective of this phase is to do the actual coding of web based application development. The
generation of client side web service will be developed by Mozilla Firefox, Google chrome,
Html, and Css, Internet explorer. The server side will be developed by using Microsoft Asp.net
2010.

1.8.4 SYSTEM TESTING

After implementation of the system the developers are conducted the following testing
methodologies.
 Unit testing: every developer and analyst would test each module (like the Registration
module). For example we will test the functionality of registration of customers after
accomplishing the registration form or page.
 Integrated Testing: the integration of two or more modules should be tested by taking
sample test data for its functionality. For example we will test the functionality of the
registration and payment handling first, and then we will test the delivery receipt or other
functionality together after accomplishing these functionalities.
 Alpha Testing: Alpha testing is done at the developer’s site. It is done at the end of the
development process. Here also at the end of this project we will check for may be UN done
things or missed requirements or other uncorrected things and correct if an errors are occurred
or happened.
 Beta testing: Beta testing is done at the customer’s site. It is done just before the launch of the
product. When we finish our job our looking may be different from our end users view we will
open the project for some of selected end users from each corner because there may be
different types of end users use this website.

1.8.5 DOCUMENTATION METHODOLOGY

In the developing the project it uses the following documentation methodologies ;like Microsoft
word 2010 to write the documentation, starUML 5.02 to draw the UML diagrams , adobe
photoshopcs4 to edit the photos.
CHAPTER TWO
 DEPARTMENT OF COMPUTING TECHNOLOGY

REQUIREMENT ANALYSIS DESCRIPTION

2.1 INTRODUCTION
In this chapter we will deal with the overview, activity, problems, and (Strength, weakness,
Opportunity and Threat) SWOT analysis and business rule of the existing system. Then the
proposed system will be discussed by the functional requirements, nonfunctional requirements,
constraints, and assumption.

2.2 OVERVIEW OF THE EXISTING SYSTEM

In the current system they are using partially automated and manual system. So the customers come
to the passport office for registering. In this system every individual had to stand in a queue
which involved individuals in huge numbers. When the queue reached to the customer he enters
to the office and register registration form by the government agent. In this system the customer
fill of keeping the office records is done manually, i.e. paper files that are closely related are
grouped together and placed in file folder according to alphabetical order or some category on
shelves. When one file is needed, it is checked over these collections of file folders. And the
agent send the customer to the next agent, the customer goes to the office to pay money for get
the passport in this office the system is worked in manually. And also this agent send the
customer to the next agent, this agent is accept the customer payment card and capture face
image, capture fingerprint and digital signature of the customer and give the appointment date to
take the passport of the customer. In this office the system is worked in automated. Hence the
existing system is more time consuming and involves more manpower. So it is not possible to
get quick information on office status such as in emergency issues.

2.2.1 ACTIVITIES OF THE EXISTING SYSTEM

First the organization gives them a form and the customer fills the given form then finally they
submit to the organization. Later the organization called them and they register for passport and
the organization gives the passport for the customer.

To register currently the existing system is operated with manual and partialy automeated
handling system. The customer go to the organization to register using renew kebele id. This
Activity is registered in hard copy in file store form.
 DEPARTMENT OF COMPUTING TECHNOLOGY

To issuing of passport the current system worked,when the government agent give the
appointment date to take the passport,and the customer came to the office at appointment date
then the customer take the passport.
To renewal the passport in the curent system the customer come to the office and report after 3
year up to 5 year other wise the passport was out of service(expiread).In this time the customer
pay panality for expire passport and take the passport.
2.2.2 PROBLEM OF EXISTING SYSTEM
The problem of the organization listed in chapter one are the current problems of the existing
system. For example

Appointment for the customer

Payment system
Notification system
Registration problems because it is manual and additionally the following problems are
existed in the current passport system
The partially automated passport management system is prone to various problems.the curent
system not give an appointment date for the customer to register, but the custemer came to the
office and wating the quea of line to register, in one day from the quea same peoples are registers
and also same people can not register.the other problem is payment system.the customer pay the
mony when they came to the office other wise they do not pay any whear. These problems can
be seen from the following perspectives like performance, economic, control, efficiency and
services given by the existing system to the users. Next we will discuss the problems in detail.

I. Performance: The current system’s performance is weak. This is due to the following
reasons: first the acceptable throughput rate is relatively high i.e. the time required from
initiation to completion of a particular task is relatively high. Second, the numbers of
customers that access from the service are very small.
II. Economic problems: This problem has three faces. (Human power, stationary materials,
storage) The current passport managment system needs on data recorder for recording the
customer documents, 1500 papers to register new customers. So this current system is
economically infeasible.
III. Security problems: Since all the records associated with the manual system are recorded
and stored manually the security that the system provides for the privacy of this records is
 DEPARTMENT OF COMPUTING TECHNOLOGY

not good. The system shouldn’t provide sufficient protection for access and manipulation of
the records associated with the system. And the information that is stored in the organization
can lose. So this current system is security problems.
IV. Data Redundancy and inconsistence problem: The passport management system works a
manual record of every activity of the system activities so it is easily prone to data
duplication or redundancy in the customer’s administration. For example, when the
customer’s document is lost while searching, then the customer’s is required to fill all the
information again, and if the customer’s information is gained after re again registration of
the customer’s information, then In this case the registration of customer’s information is
redundant. And the data inconsistency occurs when the customer’s registration is redundant
and the registration of customer’s information is not consistence.
V. Services problems: The passport management system don’t give the fast services to
customers this is because the customer’s go to the organization to get different services and
wait in the organization until they administration is open. Hence they don’t get a full service
from the organization. So this current system is service problems.

2.2.3 SWOT OF THE EXISTING SYSTEM

The current manually passport management system has its own weaknesses, Strength,
Opportunities and Threat.

2.2.3.1 STRENGTH OF THE CURRENT SYSTEM

The main strength of the current system is partily automated.

2.2.3.2 WEAKNESS OF THE CURRENT SYSTEM

Because the system is partially automated if the connection is not present we will face to
problems and we cannot fully process the objective online. the curent system is economically
infeasible because of the different stationeries and employee. Additionally the following points
are listed in its weakness side.
 No notification system
 No appointment system
 No payment system
 No online registration system
 DEPARTMENT OF COMPUTING TECHNOLOGY

2.2.3.3 OPPORTUNITIES OF EXISTING SYSTEM

The main opportunity of passport management system is to provide job opportunity for many
employees. Despite its cost to pay for employees, the current system creates job opportunity for
many employees. In addition to this, the existing system gives an opportunity for customers to
have a good communication skill.

2.2.3.4 THREATS OF EXISTING SYSTEM

Threats for the current manually passport managment system are human or natural disasters like
fire, rain, payment handling form (data paper ) is lost, it is hard to find such information .

2.2.4 BUSINESS RULE

A business rule is effectively an operating principle or policy that the software must satisfy. It often
concerns to access control issues, and operating polices and principles of the new developing system.
Therefore, our new developing system has the following business rules.

BR1: The new customer should go to the organization to register.

BR2: All users must register on the registration form.

BR3: when the user came to the office they must came at the appontment date or the schdule.

BR4: All users must pay for geting confirmation massage.

BR5:The users must come with the entire fill that used to registration (i.e Barthday certificat, renew
kebelea ID......etc)

BR6:one person can register only once,otherwies the system rejected the person.

BR7:for takingthe apointment date the customer must pay online.

BR8:the taking date of the appointment expired the customer customer was not

The user see the schedule online and goes to the passport office to the nerest brunch.

BR9: for renewail purpose the customer must report after 3-5 month,otherwise the customer pay
penality to renew the passport.

2.3 OVERVIEW OF THE PROPOSED SYSTEM

Since we have understand the problems of the existing passport management system and we
 DEPARTMENT OF COMPUTING TECHNOLOGY

have collected the needed information, we‘re going to apply the following modules for the
improvement of the existed problems

Payment system: the customer is going to use this payment system to pay the payment to the
organization.

Notification: any announcement and any information will be posted to the customer online

Appointment: the appointment for the customer when they will renew their ID and when they
will get their passport will be posted or announced here.

Registration: the registration of the new customer is going to be online as it has its own impact
because if it is manual it has its own impact on time and expense cost and additionally it is
illustrated as follows

The development of this new system contains the following activities, which try to automate the
entire process keeping in the view of database integration approach.

 Customers are provided in the application with various controls provided by system rich
Customer interface.
 This system makes the overall project management much easier and flexible.
 Authentication is provided for this application only registered customers can access.
 Report generation features is provided using to generate different kind of reports.
 In this system the individual fills all the information or details required for passport
reservation through online.
 The individual has to fill all the details and can’t leave any field as blank.
Finally if these weakness of the organizations are eradicated the organization will be
profitable or gets advantages

2.3.1 FUNCTIONAL REQUIREMENTS

The functional requirement of the proposed system is described as follows.
 DEPARTMENT OF COMPUTING TECHNOLOGY

 Customer Registration:This module takes care of new customer registration to

create an account. During this registration, the Personal Identification Numbers
(PIN) is given by the adminstrator to the customers. The system will take this PIN
as appointmentschedle number.
 Give Appointment: This module creates customer’s basic personal information
and an appointment date.And alsso this moduleProvide Passport issue regulations
and expectation of rules and regulations to get appointment date.
 Manage customer’s module: this module manages customer details, view confirmed
customer and view denied customer.
 Manage customer profile: This module will manage the update, delete, and handling of
personal information.
 Manage branch: This module defines access branch and update, delete and create the
branch by their location.
 Renewal passport: this module takes care of if the passport needs renewals the system
renew the passport based on the appointments.
 Handling customers complain: this module will take care of handling of feedback for
complains and mistakes in spelling and numbering errors in the passport.
 Capture biometric image: this module it checks weather the owner of the passport is the
person registered first or not and recognizes the face of the customer.
 Manage user: This module defines access restrictions and user management by using
roles.
 Send notification: this module notifies for the customer that after the administrator
finishes the process of passport s/he will announce using email for the customer.

 Handel payment: this deals with the credit, debit and check the balance of the account
customer.
 Generating report: this is the way the administrator generates report about the passport
activity daily or monthly.

 Manage news: this is the mechanism of generating news, update and delete news
from the system.
 Manage feedback: this is the mechanism of generating feedback and delete
 DEPARTMENT OF COMPUTING TECHNOLOGY

feedback online from the system.

2.3.2 NON FUNCTIONAL REQUIREMENTS
The non-functional requirement for the proposed system is described in the following way.
 User friendly/system interface/: The system interface that will be developed must be
interactive and easily understandable by its users.
 Response time: When users access the system the system respond at short period of
time.
 Reliable: The data or information which is retrieved from the system are accurate the
requested information.
 Availability: the system is available at anywhere and any place with the existence of
internet connection 24/7 hour per week.
 Compatibility or Supportability (flat form independent): The system should support
for all operating systems and hardware machines.
 Security: unauthorized person can’t access the system unless the user must register or
have account in the database.
 System modification: Whenever modification is needed the system developers can
modify the system with easily way.

2.3.3 SYSTEM REQUIREMENT

2.3.3.1 HARDWARE REQUIREMENT

The hardware requirements for installing, running and using this system need the following
 DEPARTMENT OF COMPUTING TECHNOLOGY

resources:

Server Computer: for installing the new system.

 Minimum Hardware requirement:
 Intel Pentium 4 or AMD @ 1 GHz CPU , 2 GB of RAM for x86 or 32 bit systems and
10GB+ free HDD space.
 Intel Pentium 4 or AMD @ 1.4 GHz CPU , 4 GB of RAM for x64 or 64 bit systems and
12GB+ free HDD space.
 For best performance Hardware requirement: (Specified and above)
 Intel core i3 @ 3.0 GHz CPU , 6 or 8 GB of RAM and 250GB+ HDD
Client Computer
 Minimum Hardware requirement: it is dependent on operating system used.
 For Windows XP Service Pack 3, Intel Pentium 4, 1 GHz CPU, 512 MB of RAM and
10GB+ free HDD space.
 For Windows 7, Intel Pentium 4 or AMD @ 1 GHz CPU, 1 GB of RAM for x86 (32 bit
systems) and 2 GB RAM for x64 (64 bit) systems and 15GB+ free HDD space.
 For best performance Hardware requirement: (Specified and above)
 Intel Pentium 4 @ 3.0 GHz CPU , 2 GB of RAM and 80GB+ HDD
 Switch: already available.
 CAT 5 UTP Networking Cable: already available.
 The fingerprint machine:to take fingerprint from the customer.

2.3.3.2 SOFTWARE REQUIREMENT

The software requirements for installing this system requires
 Operating System:
 DEPARTMENT OF COMPUTING TECHNOLOGY

 For Server Computer: Microsoft® Windows Server 2008 or higher versions

 For client Computer: Any operating system.(Recommended Windows® family )
 Ado.net (Windows, SQL server and Asp
 Browser: for client computer
 Mozilla Firefox version 16 or higher, Chrome any, Opera version 9 or higher, IE version 7 or
higher.
 Application Software: for both server and client computer
 Microsoft Office Word 2010 or higher: for writing, formatting and adding digital signatures
to letters.
 Adobe Acrobat Pro XI (optional): Adding digital signature plus cloud storage for documents.
(Signup or Adobe account is needed.)

2.3.4 CONSTRAINTS
According to http://www.dummies.com, constraints (Project limitations) may influence how
projects manage the project and may even determine whether or not the project decide to proceed
with specific project. While developing this system, the project team may encounter different
types of constraints like:

This proposed passport management system can’t handle:-

 If the power is lost during the user register to the system,

 In the proposed system the employees of the organization do not improve their decision
making ability. This is because of the online environment.
 The proposed system prone to the skill constraint in operating or using the proposed
system. For example using the web based application needs high computer skill for the
customer.

2.3.5 ASSUMPTIONS
 The Applicants and Administrator must have basic knowledge of computers and English
 DEPARTMENT OF COMPUTING TECHNOLOGY

Language.
 In order to use this automated passport registration system, every user must have basic
skill to use computer and some knowledge on how to use or serf internet and networks to
do some task.
 To access the automated passport registration systemthey must have full network access
and fast.
 The user has to be careful while submitting the information. Much care is required
 The Applicants require a computer and fingerprint machine to submit their information .

CHAPTER THREE

SYSTEM MODELING
 DEPARTMENT OF COMPUTING TECHNOLOGY

3.1INTRODUCTION
System modeling is the interdisciplinary study of the use of models to conceptualize and
construct system in business and information technology development. This chapter deals about
modeling techniques we used to analyze the system. For modeling the system the object oriented
analysis methodology used, which includes System use case model, Sequence diagram, Class
diagrams.

3.2USE CASE MODEL

According to www.google.com.et/In software and systems engineering, a use cases a list of
steps, typically defining interactions between a role (known in Unified Modeling Language
(UML) as an "actor") and a system, to achieve a goal. The actor can be a human, an external
system, or time. This use case model uses STAR UML (5.0.2) which underlines the use of UML
and supports UML/MDA platformnotations.
3.2.1 ACTOR SPECIFICATION
According to www.sparxsystems.com,ause case diagram shows the interaction between the
system and entities external to the system. These external entities are referred to as actors. Actors
represent roles which may include human users, external hardware or other systems. An actor is
usually drawn as a named stick figure, or alternatively as a class rectangle with the «actor»
keyword

Actor Responsibility

Administrator A person who register users, mange users like edit, update,
delete, mange customer account like edit, update, delete,
post news, mange branch like create, edit ,delete
branches ,complain handling (lost, discard) generate report,
manages the customer like view customer detail, view
confirmed customer, view denied customer create account,
manage appointment send notification view payment
Customer A person who applies for passport, view appointment, view
news, replay message register, payment, deposit, check
 DEPARTMENT OF COMPUTING TECHNOLOGY

balance, give feedback and renewal passport to the system.

Officer A person who manages the passport process. i.e. checking
appointment, checking payment, view complain, capture
biometric images (photograph, images and finger print) and
generate production order.
Table 1 actors and their responsibility

3.2.2 USE CASE DIAGRAM

The use cases of the Passport management system include the following functionality or use
cases:

 Register customer detail

 Give appointment date
 Manage customer
 Manage customer profile
 Manage branch
 Renewal passport
 Handle customer complain
 Capture biometric image
 Manage user
 Send notification
 Handle payment
 Generate report
 Manage news
 Manage feedback

The proposed Passport management system allows the customers to interact with the system.
Currently, the custemer should be physically present at the office to get any kind of information.
This will add unnecessary charge to the office and reduce its efficiency.
Use case Diagram of passport managment system
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 1 use case diagram

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 2 use case diagram for administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 3 use case diagram for customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 4 use case diagram for officer

 DEPARTMENT OF COMPUTING TECHNOLOGY

3.2.3 USE CASE DESCRIPTION

Use case description includes use case name, descriptions of the use case, preconditions, post
conditions, flow of event and whatever which is important in modeling the user goal.

Use case name Login

Participating actor customer,officer and administrator

Description Only the registered users will login, it may be the customer,officer and
administrator

Precondition The user need to be already register

Flow of events Basic Course of Action:

1.The system displays a login form

2. The user enters his/her credentials such as name, password to the

system

3. The system validates the data entered (Alt course A: Invalid data)
4. The user clicks on login button

5. The system takes the user to his/her home page.

Alternate Course Action: Invalid data entered.

A.3. The system determines the data is invalid

A.4. The user resumes step 2 showing error message

Post condition The user is login

Table 2 use case description for login

Use case name Logout

 DEPARTMENT OF COMPUTING TECHNOLOGY

Participating actor Customer,officer and Administrator

Description The customer,officer and administrator will logout

Precondition A customer,officer and administrator is logged into the system

Flow of events Basic Course of Action:

1.The system displays a logout link

2. The user clicks on logout link

3. The system closes customer,officer and administrator sessions

4. The system takes the customer,officer and administrator to login page

Post condition The customer,officer and administrator is logged out of the system

Table 3 use case description for logout

 DEPARTMENT OF COMPUTING TECHNOLOGY

Use case name Create account

Participating actor Administrator

Description The administrator creates an account

Precondition The administrator must be logged in

Flow of events Basic Course of Action:

1. The Administrator Selects on create account button.

2. The system displays the account form.

3. The Administrator fill the profile data to the system

4. The system validates the data entered (Alt Course A: Invalid data
entered)

5. The system ends when it displays a successful creation of account.

Alternate Course Action: Invalid data entered

A.4. The system determines the data is invalid

A.5. The administrator resumes step 3 showing error messages.

Post conditions: The administrator account is created

Table 4 use case description create account

Use case name Manage account

Participating actor Administrator

Description The administrator edits or delete an account

Precondition The administrator must be logged in

Flow of events Basic Course of Action:

 DEPARTMENT OF COMPUTING TECHNOLOGY

1. The Administrator Selects manage user account button.

2. The system displays Edit or delete button.

3. The Administrator click the Edit button then fills the username,
password and click the update button. Click delete button then click
delete button.

4. The system checks the username, password, and ID (Alt Course A:

Invalid data entered).

5. The system ends when it displays a successful updated or delete of the

account.

Alternate Course Action: Invalid data entered

A.4. The system determines the data is invalid

A.5. The administrator resumes step 3 showing error messages.

post condition The administrator account is updated or delete.

Table 5 use case description manage account

Use case name View account

Participating actor Administrator

Description The administrator views the account

Entry condition The administrator must be logged in

Flow of events Basic Course of Action:

1. The Administrator Selects on manage user account button.

2. The system displays all the accounts already registered.

Exit condition The administrator is viewed his account.

Table 6 use case description view account

 DEPARTMENT OF COMPUTING TECHNOLOGY

Use case name Manage customer

Participating actor Administrator

Description Administrator confirmed customers or denied customer.

Precondition The administrator must logged in

Flow of events Basic Course of Action:

1. The administrator selects Manage customer button.

2. The system displays the customers detail form.

3. The administrator views customer details and then he/she checks all
the required information.

4. The administrator confirmed the customer when the customer’s

information is satisfied. Or denied the customer when the customer’s
information is unsatisfied/ incomplete.

post condition The customer is confirmed or denied.

Table 7 use case description manage customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Use case name Post feedback

Participating actor Customer

Description The customer posts feedback

Precondition The customer must be logged in.

Flow of events Basic Course of Action:

1. The customer Selects the post feedback button.

2. The system displays post feedback form.

3. The customer sets the feedback and clicks submit.

post condition The feedback is send successfully.

Table 8 use case description post feedback

Use case name View feedback

Participating actor Administrator

Description The administrator views his feedback

Precondition The administrator must be logged in.

Flow of events Basic Course of Action:

1. The administrator clicks on the view feedback button.

2. The system displays the view feedback form.

3. The administrator views his feedback and the he can delete it.

post condition The administrator will view his feedback.

Table 9 use case description view feedback

Use case name View complain

 DEPARTMENT OF COMPUTING TECHNOLOGY

Participating actor Administrator

Description The administrator views complain
Precondition The administrator must be logged in.
Flow of events Basic Course of Action:
1. The administrator clicks on the complain button.
2. The system displays the complain form.
3. The administrator views the complain.
post condition The administrator will view the complain.

Use case name Manage profile

Participating actor Customer
Description The customer views his profile and edits the incomplete profiles to make
complete.
Precondition The customer must be logged in
Flow of events Basic Course of Action:
1. The customer Selects on view and edit button.
2. The system displays the view and edits form.
3. The Customer then views the existing profile and completes the
remaining.
4.The system checks the entered values (Alt Course A: Invalid data
entered)
5. The system ends when it successfully added the customer’s profile.
Alternate Course A: Invalid data entered
A.4. The system determines the data is invalid
A.5. The customer resumes step 3 showing error messages.
post condition Customer’s profile is successfully completed
Table 10 use case description view complain

Use case name Create account

Participating actor Customer
 DEPARTMENT OF COMPUTING TECHNOLOGY

Description New customers can be creating their account.

Precondition The customer must be new customer.
Flow of events Basic course of action
1.the customer wants to create new account
2.the system displays the signup form
3.The customer fills the needed Information and other profile and click on
the signup button.
4.the system validates the inputs and saves to the database
5.the use case ends
Alternative course of A:4 if the customer enter invalid input, the system return to step 3
action
Post condition The customer successfully created his/her account
Table 11 use case description create account

Use case name Manage appointment

Participating actor Administrator

Description Administrator manages appointment

Precondition The Administrator must login

Flow of events Basic flow of events

1. Administrator click on manage appointment.
2. The system display manage appointment page.
3. Administrator look at the appointment schedules and
he can manage them.

post condition The appointment is managed.

Table 12 use case description manage appointment

Use case name Generate report

Participating actor Administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Description Administrator can generate report

Precondition Administrator must login

Flow of events Basic flow of events

1. Administrator click on generate report
2. The system display generate report form
3. Administrator fill report type and click on generate
button
4. The system validate the generated report from
database
5. Report generated successful message
Alternative floe of events
4.1 the system display error message
post condition Report generated
Table 13 use case description generate report

Use case name Manage branch

Participating actor Administrator

Description Administrator can manage branches

Precondition Administrator must login

Flow of events Basic flow of events

1. Administrator click on manage branches
2. The system display manage branches form
3. Administrator fill the form with appropriate data and he
can add, update or delete the branch
4. the system display success message
post condition Administrator managed the branch
Table 14 use case description manage branch

Use case name Send notification

Participating actor Administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Description Administrator can send notification

Precondition Administrator must login

Flow of events Basic flow of events

1. Administrator click on send notification
2. The system display notification form
3. Administrator fill the form and click send
4. Notification sent
5. Successful message display
Alternative flow of event
3.1 error message displayed
post condition Notification sent
Table 15 use case description send notification

Use case name Payment

Participating actor Customer

Description The customer sets the payment

Precondition The customer must be logged in.

Flow of events Basic Course of Action:

1. The customer Selects the payment button.

2. The system displays create payment form.

3. The customer set the payment for the Passport and Networking.

4. The system checks the balance (Alt Course A: Invalid balance)

5. The system ends when it successfully transfers money.

Alternate Course A: Invalid balance

A.4. The system determines the less balance

A.5. The customer resumes step 3 showing error messages.

 DEPARTMENT OF COMPUTING TECHNOLOGY

post condition The payment is sated.

Table 16 use case description payment

Use case name View payment

Participating actor officer and administrator

Description The customer, officer and administrator views payment

Precondition The customer, officer and administrator must be logged.

Flow of events Basic Course of Action:

1. Theofficer and administrator clicks on the view payment button.

2. The system displays the view payment form.

3. Theofficer and administrator views the total payments

post condition The officer and administrator is viewed the total payments to pay.

Table 17 use case description view payment

Use case name View Notification

Participating actor Customer and officer

Description This use case allows the customers and officers to view notifications

Precondition The customer and officer must be logged.

Flow of events Basic Course of Action:

1. The customer and officer clicks on the view notification link.

2. The system loads notifications from the database.

3. The customer and officer views the notification

Alternative flow of event

 DEPARTMENT OF COMPUTING TECHNOLOGY

2.1 if unable to load notification:

System displays error message.

post condition The customer and officer viewed notification.

Table 18 use case description view notification

Use case name View appointment

Participating actor officer

Description This use case allows the officers to view appointment

Precondition The officer must be logged.

Flow of events Basic Course of Action:

1. The officer clicks on the view appointment link.

2. The system loads appointment from the database.

3. The officer views the appointments

Alternative flow of event

2.1 if unable to load notification:

System displays error message.

post condition The officer viewed appointment.

Table 19 use case description view appointment

Use case name Capture biometric image

Participating actor officer
Description This use case allows the officers to upload or insert the biometric image
which is passport photo, finger print and digital signature in to the
 DEPARTMENT OF COMPUTING TECHNOLOGY

system.
Precondition The officer must be logged.
Flow of events Basic Course of Action:
1. The officer clicks on the capture biometric image link.
2. The system prompts customer selection.
3. The officer selects customer and submit.
4. The system displays form
5. Officer selects and submits images.
6. System validates the format and saves.
Alternative flow of event
2.1 if invalid format:
System displays error message. And allow retrial.
post condition The officer uploaded the biometric image successfully.

Table 20 use case description capture biometric image

Use case name Generate production order

Participating actor officer
Description This use case allows the officers to generate the production order for the
customer passport.
Precondition The officer must be logged.
Flow of events Basic Course of Action:
1. The officer clicks on the production order link.
2. The system displays production order form.
3. The officer fills and submit.
4. The system validate the data entered
4.1. Assume valid:
5, System saves to production order database.
Alternative flow of event
4.2. if invalid data entered:
System displays error message. And allow retrial.
 DEPARTMENT OF COMPUTING TECHNOLOGY

post condition The officer generates production order successfully.

Table 21 use case description generate production order

Use case name Manage news

Participating actor Administrator

Description The Administrator delete, update news

Precondition The Administrator must be logged in

Flow of events Basic Course of Action:

1. The Administrator Selects on manage news button.

2. The system displays the manage news form.

3. The Administrator then deletes the old news and updates the new one.

5. The system ends when it successfully deletes or updates the news.

post condition Administrator is successfully completed

Table 22 use case description manage news

3.3 SEQUENCE DIAGRAM

Sequence diagram is an "interaction diagram" that models a single scenario executing in the
system. The figure below shows a login use case sequence of an event in the proposed passport
managment system.
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 5 Sequence diagram for user login

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 6 Sequence diagram for create account for users except customer

Figure 7 Sequence diagram when customer create account for his personal use
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 8 Sequence diagram when manage account for administrator edit account

Figure 9 Sequence diagram when manage account for administrator delete account
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 10 Sequence diagram for view account by administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 11 Sequence diagram when manage customer for administrator view customer
detail

Figure 12 Sequence diagram for view customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 13 Sequence diagram when manage account for administrator view denied
customer

Figure 14 Sequence diagram when manage profile for customer update profile
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 15 Sequence diagram when manage profile for customer add profile

Figure 16 Sequence diagram for view feedback by administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 17 Sequence diagram for post feedback by customer

Figure 18 Sequence diagram for complain handling by administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 19 Sequence diagram for view complain by officer

Figure 20 Sequence diagram when update appointment by administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 21 Sequence diagram when arrange appointment by administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 22 Sequence diagram for generate report by Administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 23 Sequence diagram when manage branch for administrator create account
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 24 Sequence diagram when manage branch for administrator update account
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 25 Sequence diagram when manage branch for administrator delete account
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 26 Sequence diagram for Send notification by Administrator

Figure 27 Sequence diagram for view notification by customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 28 Sequence diagram for payment by customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 29 Sequence diagram for view payment by users

Figure 30 Sequence diagram for view appointment by customer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 31 Sequence diagram for capture biometric image by officer

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 32 Sequence diagram for generate production order

Figure 33 Sequence diagram for post news by Administrator

 DEPARTMENT OF COMPUTING TECHNOLOGY

3.4 CLASS DIAGRAM

UML class diagram is a mechanism of depicting the different class and their activities together
with the relationship that exist among the classes. A class diagram shows the declarative model
components such as classes, types, and so on with their contents and relationships. They contain
behavioral elements, but their dynamics are shown using other diagrams.

This class diagram includes the following classes. For example the customers class,
administrator class, the office manager, branch manager, payment, virtual bank, complain,
schedule etc. and their relationship among the classes. For example many merchants can pay.

Figure 34 Class Diagram of passport management system

 DEPARTMENT OF COMPUTING TECHNOLOGY

CHAPTER FOUR

SYSTEM DESIGN

4.1 INTRODUCTION
In this chapter we will deal with Design Goal, System Decomposition, System Architecture,
Deployment Diagram, Persistence Data Management, Access Control and Security and User
Interface Design depend on the passsport managment system.

4.2 DESIGN GOALS

Design goals define the important system design qualities. Design goals also define the values
against which options are evaluated.

 Response time: The system should immediate response to users. For example the system
responds to the user in few seconds in a single click. While registration, payment
handling form, and request confirmation page when the passengers and the driver click
on the respective buttons then the system should give a response quickly.
 Reliable: The system provides to the user correct information, In addition to this the
system notifies users to correct the input data when they enter wrong inputs..
 Availability: The system should always be available for access at 24 hours, 7 days a
week. Also in the occurrence of any major system malfunctioning, the system should be
available in 1 to 2 working days, so that business process is not severely affected.
 Security: unauthorized person can’t access the system unless the user must register or
have account in the database.
 Efficiency: the level of which web application uses scarce computational resources. For
example it uses less CPU, memory, disk space.
 Control: Nobody can’t access the database without the authorize person unless the
authorized person provides his/her username and ID number to access the data base.
 Performance Requirements: the system provides high throughput, transaction rate, uses
a less amount of resources. In addition to this the proposed system reduces the
consumption of paper based and other manual process. So the performance of the
proposed system is well.
 DEPARTMENT OF COMPUTING TECHNOLOGY

4.3 SYSTEM DECOMPOSITION

System decomposition is undertaken to reduce the complexity of the system and gaining insight
into the identity of the constituent components. The system is decomposed in to sub-systems
which are a collection of classes, associations, operations, events and constraints that are closely
interrelated with each other. And the web based passport managment system contains the
following subsystems:

 Register sub system: this deals with registering of customers.

 Payment handling sub system: this sub system deals with payment handling from the
customer to virtual bank.
 Notification sub system: this sub system sends a notification message for the customer.
 Manage account sub system: this subsystem deals with managing a account like update,
delete, create, etc.
 Upload documents sub system: this deal with uploading necessary documents from the
system
 Generate report subsystem: this subsystem generates reports based on transaction
performed.
 Check balance and deposit subsystem: these deals with checking the balance of the
customer in the bank and deposit of the customer in to the bank.
 Appointment sub system: after registering the customers they are scheduled when they
can take their passport
 Generate order sub system: this is the way happened after the customer are registered
and to order for print the passport.
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 35 system decomposition for web based for passport management system
 DEPARTMENT OF COMPUTING TECHNOLOGY

4.4 SYSTEM ARCHITECTURE

Software architecture intuitively denotes the high level structures of a software system. Software
architecture also denotes the set of practices used to select, define or design software
architecture. The architecture used in this project is the client–server. The server type/role for the
project is a web server. A web server serves web pages and waits for incoming requests. Clients
therefore initiate communication sessions with server and request a server's content or service
function.

Figure 36 system architecture diagram

4.5 DEPLOYMENT DIAGRAM FOR PASSPORT

MANAGEMENT SYSTEM
A deployment diagram is used to depict the relationship among the hardware and run time nodes.
A web server, for example, is a component that provides services to Web browsers. A
component is a physical unit of implementation with well-defined interfaces that is intended to
be used as a replaceable part of a system. Deployment diagrams are used to visualize the
topology of the physical components of a system where the software components are deployed.
The following deployment diagram three components like client browser, database server,
 DEPARTMENT OF COMPUTING TECHNOLOGY

application server.

Figure 37 deployment diagram for passport management system

4.6 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 is an
abstract way of describing a database.
 DEPARTMENT OF COMPUTING TECHNOLOGY

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. Refine the design.
7. Apply the normalization rules.
 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 38 Persistent data management for passport management system

4.7 ACCESS CONTROL AND SECURITY

Access control provide security by giving flexible control over who is allowed to enter or leave
this system and when.

Access control is way of limiting access to a system or to physical or virtual resources. In

computing, access control is a process by which users are granted access and certain privileges to
 DEPARTMENT OF COMPUTING TECHNOLOGY

systems, resources or information. In access control systems, users must present credentials
before they can be granted access. In physical systems, these credentials may come in many
forms, but credentials that can't be transferred provide the most security.

Function
Administrator Customer Office manager

Register customer √

Manage user √

Give complaints √

Manage profile √

Deposit Money √

View complaints √ √

Generate report √

View Payment √ √
Give feedback √
Check balance √
Capture biometric image √
Taking appointment √
Give appointment √
Send notification √
Manage customer √
Renewal passport √
Generate product order √
 DEPARTMENT OF COMPUTING TECHNOLOGY

4.8 USER INTERFACE DESIGN

The following Figures show the interface of the home page of the site that enables the user to
click on one of the links to access the information that he needs.

Figure 39 user interface design for login home page

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 40 user interface design for customer home page

Figure 41 user interface design for customer signup form

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 42 user interface design for administrator home page

Figure 43 user interface design for create new user

 DEPARTMENT OF COMPUTING TECHNOLOGY

Figure 44 user interface design for officer home page

 DEPARTMENT OF COMPUTING TECHNOLOGY

5 REFERENCE

1. http://www.tethyssolutions.com
2. http://www.dictionary.reference.com
3. http://www.dummies.com
4. http://www.google.com.et/?
gws_rd=cr&ei=Nju9VNubHK6ygPe7oCoBg#q=what+is+use+case+model In software
and systems engineering, last Retrieved on Dec 21, 2015.
5. http://www.sparxsystems.com/resources/uml2_tutorial/uml2_usecasediagram.html
6. bmi_ds_passport_FA_v2.pdf
7. KJD_Issue24_p19-23_MJ_071001.pdf
8. passeportuzbekistan_2.pdf
9. entity-relationship-modeling-of-automatedpassport-management-system.pdf
10. V3S01_CM.pdf