Final Year Project Report for Solomon Gai Ayuen

MOUNT KENYA UNIVERSITY

DEPARTMENT OF BUSINESS INFORMATION TECHNOLOGY

RWANDA TOURISM UNIVERSITY COLLEGE (RTUC) Campus, Kigali, Rwanda

A PROJECT REPORT

ON

Submitted By:

SOLOMON GAI AYUEN Reg N0: BIT/0169/11/F

Under the supervision of

Mr. MANIRAHO Jean FRANOIS

Submitted in partial fulfillment of the requirements for the award of

BACHELORS DEGREE OF BUSINESS INFORMATION TECHNOLOGY

PASSPORT AND VISA APPLICATION MANAGEMENT INFORMATION

SYSTEM

Academic 2012

i

MOUNT KENYA UNIVERSITY

DEPARTMENT OF BUSINESS INFORMATION TECHNOLOGY

RWANDA TOURISM UNIVERSITY COLLEGE (RTUC) Campus, Kigali, Rwanda

C E R T I F I C A T E

This is to certify that Mr. Solomon Gai Ayuen Ayom, bearing in Roll REG.:

BIT/0169/11/F has developed system Title Passport & Visa Application

Management Information System Case study South Sudan Immigration

Department as in partial fulfillment of the requirement for the award of

Bachelors Degree of Business Information Technology at Mount Kenya

University in collaboration with Rwanda Tourism University College (RTUC),

during the Academic Year 2012.

Signature.. Signature

SUPERVISOR Head Department of BBIT

Mr. MANIRAHO Jean FRANOIS Mr. KULE Julie WARREN

Date: Date:...

Submitted to the Project Examination held at Rwanda Tourism University College

on September 30, 2012

ii

DECLARATION

I, Solomon Gai Ayuen Ayom declare that the content of this project is my original work intended

to serve as part of the fulfillment of the requirements for the award of a Bachelor degree of

Business Information Technology at Mount Kenya University.

I, hereby affirm that to the best of my knowledge, this work is original and has never been

presented for any academic award in any university or institution as a whole or in part.

The content of this project may be made available for academic purpose within RTUC library

and may be photocopied or rent to other similar libraries for researchers.

Signed by:

SOLOMON GAI AYUEN AYOM Reg N0: BIT/0169/11/F

Date 16/08/2012

iii

DEDICATION

To my parents Ayuen Ayom Lual and Mama Awuok Mabei Jok , Achic Adit Deng and Adit

Amol Kuot, for bringing me up, my mostly treasured cousins Brothers Eng. Elijah Mabior Bol

Ayom and Francis Chagai Bol for their kindly generous support in my Education and all my

cousins Brothers and Sisters for their love and care.

iv

ACKNOWLEDGEMENT

Therefore; I send my greatly and kindly Joy goes to the almighty God for the gift of precious

life. I also extend my sincere appreciation and thank to my project Supervisor Maniraho for his

guidance, Mr. Njoroge Atanas for his support me in implementation. A vote of thanks goes to

my cousin brother and sister for their continued support during my studies. I own appreciation

to my various friends for giving me company, help and encouragement throughout my

studies.

The special gratitude goes out to the Government of Rwanda through the Ministry of Education

for funding my Studies at KIST and Rwanda Tourism University College (RTUC) in

collaboration with Mount Kenya University. My vigorous gratefulness goes first to former

Minister of Telecommunication and Postal Services Government of South Sudan and currently

the Minister of Road and Bridge (GOSS) Maj. Gen. Hon.Minister Gier Chuang Aluong, and

Director General RTD. Brig. Gen. Elijah Biar Kuol at Minister of Telecommunication and

Postal Services.

Lastly my special thanks and joy gone to the Inspector general of Police Government of South

Sudan Lt Gen. Acuil Tito Madut for his encouragement and support for his country mate

students aboard as he gave us encouragement to work hard for the new born nation in

development. I entirely vigorously and appreciate his special and kindly support towards South

Sudanese will to develop a good image of new generation to come.

Department Kule Warren, Atanase Njoroge, Kumar Kundan, Ddumba Arafat and Uwimana

Benjamin, I also extend my greatly thanks to all staff of RTUC other Faculties for their

Cooperation during my Courses.

v

ABSTRACT

This project focuses at developing Passport and Visa Applications Management Information

System User Agent (PVAMISUA) with web Interfaces to allow users on any system to register

apply electronically and get feedback to their mails. The web application system is client

implemented here by developing a web application called passport and Visa application system

an acronym of the Author and researchers names Solomon Gai Ayuen Ayom.

The system also enables users to apply online for visa applications. An Administrator manages

the System Users accounts using the available system. Our Project gives the depth solution to

one of its important requirements as Passport and Visa application.

The client of this project is any organization who is having many abroad clients especially

nationals and non-nationals clients. This type of organizations is frequently sending their

employees for their overseas clients. This project is application that helps processors to save

record for passport, visa and store all the details regarding the passport holder. This project will

handle all type of visas, and very much concentrate in visa processing. It will generate all

possible reports, which are need by Consulate.

It is a Client Server Project, Administrator can be able to create many no of users and the users

are called Customers. Administrator will describe the utilities accessed by a Customer.

vi

Table of Contents

C E R T I F I C A T E ...................................................................................................................... i

DECLARATION ............................................................................................................................ ii

DEDICATION ............................................................................................................................... iii

ACKNOWLEDGEMENT ............................................................................................................. iv

ABSTRACT .................................................................................................................................... v

TABLE OF CONTENTS ......................................................................................................................... vi

LIST OF FIGURES .................................................................................................................................. xi

LIST OF TABLES ................................................................................................................................... xii

ABBREVITIONS ........................................................................................................................ xiii

CHAPTER ONE: INTRODUCATION AND BACKGROUND OF THE STUDY................ 1

1.0 Introduction ............................................................................................................................... 1

1.1 Background ............................................................................................................................... 1

1. 2 Problem statement .................................................................................................................... 2

1.3 Objective ................................................................................................................................... 2

1.3.1 General objectives .................................................................................................................. 2

1.3.2 Specific objectives ................................................................................................................. 2

1.4 The function of the new system ................................................................................................ 3

1.5 Scope of the project study ......................................................................................................... 3

1.5.1 Scope of Project ..................................................................................................................... 3

1.5.2 Achievement principles ......................................................................................................... 3

1.6 Interests of the project ............................................................................................................... 4

1.6.1 Academic interests ................................................................................................................. 4

1.6.2 Public interests ....................................................................................................................... 4

vii

1.6.3 Personal interests ................................................................................................................... 4

1.7 Organization of the project report ............................................................................................. 4

CHAPTER TWO: LITERATURE REVIEWS.......................................................................... 6

2.1 Introduction ............................................................................................................................... 6

2.1 passport and visa application management information system ............................................... 6

2.1.1 Passport applications .............................................................................................................. 6

2.1.2 Visa applications .................................................................................................................... 6

2.1.3 Passport and Visa applications Management Information System ........................................ 6

2.1.4 management system ............................................................................................................... 6

2.1.5 System .................................................................................................................................... 6

2.2 Microsoft.NET Framework....................................................................................................... 7

2.3 Internet Explorer ....................................................................................................................... 7

2.4 Features of the Common Language Runtime ........................................................................... 7

2.5 NET Framework Class Libraries .............................................................................................. 8

2.6 Client Application Development .............................................................................................. 8

2.7 Server Application Development .............................................................................................. 8

2.8 ASP.NET .................................................................................................................................. 8

2.9 Active Server Pages.NET ......................................................................................................... 9

2.9.1 Enhanced Performance. ......................................................................................................... 9

2.9.2 World-Class Tool Support. .................................................................................................... 9

2.9.3 Power and Flexibility. ............................................................................................................ 9

2.9.4 Simplicity. .............................................................................................................................. 9

2.9.5 Manageability. ..................................................................................................................... 10

2.9.6 Scalability and Availability.................................................................................................. 10

2.9.7 Customizability and Extensibility. ....................................................................................... 10

viii

2.10 Security: ................................................................................................................................ 10

2.11 CSS ....................................................................................................................................... 10

2.12 SQL ....................................................................................................................................... 11

CHAPTER THREE: SYSTEM ANALYSIS ............................................................................ 12

3.1 Introduction ............................................................................................................................. 12

3.2 Information Gathering ............................................................................................................ 14

3.2.1 Interview .............................................................................................................................. 14

3.2.2 Observation .......................................................................................................................... 14

3.2.3 Documentation ..................................................................................................................... 14

3.3. Description of existing System .............................................................................................. 15

3.4 Description of Proposal system .............................................................................................. 15

3.5 Methods................................................................................................................................... 16

3.6 Software development model ................................................................................................. 16

3.6.1 Modified waterfall model .................................................................................................... 17

3.6.2 Activities in waterfall model. ............................................................................................... 17

3.7 Proposed system is illustrated using the following data flow diagrams ................................. 19

3.7.1 Level 0 data flow diagram (context diagram) ...................................................................... 19

3.8 UML ........................................................................................................................................ 19

3.8.1 Use Case Diagram of Main Functionality of South Sudan PVAMIS .................................. 19

3.9 Physical data flow diagram level 1 of the current system ...................................................... 20

3.7.2 Activity Diagram for admin login........................................................................................ 22

3.7.3 Sequence diagram ................................................................................................................ 23

3.8 Limitations of current system ................................................................................................. 23

CHAPTER FOUR: SYSTEM DESIGN .......................................................................................... 24

4.1 Introduction ............................................................................................................................. 24

ix

4.2 Entity Relationship Diagram................................................................................................... 24

4.3 Database normalization ........................................................................................................... 25

4.3.1 first normal form .................................................................................................................. 26

4.3.2 Second normalization form .................................................................................................. 26

4.3.3 Third normal form................................................................................................................ 27

4.4 Data Base Scheme................................................................................................................... 28

4.5 Data Dictionary ....................................................................................................................... 29

4.6 Architecture design of the Proposed System .......................................................................... 31

CHAPTER FIVE: IMPLEMENTATION AND TESTING ................................................... 32

5.1 Implementation ....................................................................................................................... 32

5.2 User interfaces Application forms .......................................................................................... 32

5.2.1 Home page for login ............................................................................................................ 33

5.3 Test Process ............................................................................................................................ 33

5.3.1 Unit Testing: ........................................................................................................................ 35

5.3.2 Integration Testing: .............................................................................................................. 35

5.3.3 System testing: ..................................................................................................................... 35

5.3.4 Validation Testing:............................................................................................................... 36

5.3.5 Output Testing: .................................................................................................................... 36

5.3.6 User Acceptance Testing: .......................................................................................................... 36

5.4 Test Data ............................................................................................................................................... 36

5.5 Testing................................................................................................................................................... 37

5.6 Summary ............................................................................................................................................... 37

CHAPTER 6: CONCLUSION AND FUTURE IMPROVEMENT ................................................. 39

6.1 Conclusion .............................................................................................................................. 39

RECOMMENDATION ................................................................................................................ 40

x

6.2 Future Improvement................................................................................................................ 41

REFERENCES ............................................................................................................................. 42

Electronic sources ......................................................................................................................... 42

xi

LIST OF FIGURES

Figure 1: A modified waterfall model .......................................................................................... 17

Figure 2: context diagram(logical) ............................................................................................... 19

Figure 3: Use Case Diagram ........................................................................................................ 20

Figure 4: Physical diagram level 1 DFD of current system .......................................................... 21

Figure 5: Activity diagram for administrator ................................................................................ 22

Figure 6: Sequence Diagram ......................................................................................................... 23

Figure 7: ERD diagram for the propose system............................................................................ 25

Figure 8: Data Base Scheme ......................................................................................................... 28

Figure 9: Architecture design of the Proposed System ................................................................. 31

Figure 10: Applications form ........................................................................................................ 32

Figure 11: user login form ............................................................................................................ 33

Figure 12: system testing after entering information .................................................................... 35

xii

LIST OF TABLES

Table 1:data dictionary30

xiii

ABBREVITIONS

BBIT: Bachelor of Business Information Technology

DDL: Data Definition Language

ERD: Entity Relationship Diagram

HDD: Hard Drive Disk

IBM: International Business Machines

ICT: Information Communication and Technology

IT: Information Technology

ID: Identification

RTUC: Rwanda Tourism College University

MKU: Mount Kenya University

SQL: Structured Query Language

PVAMIS: Passport and Visa Applications Management Information System

ASP: Server side scripting

RAM: Random Access Memory

UML: Unified Modelling Language

CSS: Cascading Style Sheets

HCI: human computer interaction

1

CHAPTER ONE: INTRODUCATION AND BACKGROUND OF THE STUDY

1.0 Introduction

This chapter focuses in application management information system especially in immigration. It

will highlight the background of the study and as will starting the problem, effects and objectives

of this study.

1.1 Background

In most of the system in South Sudanese, Ten State Immigration department are using manual

system whereby the information are not really safe update as they may lost from an accident if

occur, this is the challenging that Passport and visa processing information system will address

inured to help people citizens and non-national to apply for the government records like passport,

visa process. Its primary objective of this web site is to give awareness about the government or

legal documents and its registration details as well as to help for quick access. This also acts as to

assist the public to reduce the effort by the candidate and save time and avoid unwanted rushes at

the government offices and assure a smooth working schedule at government offices.

This project Passport and visa applications still requires more development of IT solutions and

its applications to improve the issuance of copies of government certificates and legal

documents. Passport and visa applications are trying to get more affiliation to government offices

and Immigration department. These will help the public. With the raising investment being

experienced in South Sudan, it is right to envisage that corporate passport and visa applications

management information system that will required environment and the public register for

passport as applying for visa applications to save their time. Currently only very few computers

are been use by saving people information when applying for passport and visa giving presently.

This is the challenging in situation where users have to share the same computer or where users

would like to have access to passport and visa away from work. It is upon this background that

this project is seeking to address such challenges and provide alternative support to corporate

passport and visa applications with mobility proficiency.

2

Lastly this software specification is to establish the major requirements & Specification

necessary to develop the Software Systems for the Developers. The overall objective of the

Project is to establish a web-application system.

1. 2 Problem statement

To develop a passport and visa applications management system that will integrate processes in a

centralized database so as to make the entire process more efficient, accurate and secure.

It is difficult to store and process huge volumes of data and their information manually.

More time and space are consumed

Less security was provided for the valuable information of a clients

1.3 Objective

1.3.1 General objectives

The main objective of this project is to design, develop, implement and test a new system called

passport and visa application management information system which is be used by the South

Sudan Immigration Department.

1.3.2 Specific objectives

To develop a passport and visa applications management information system that will

amalgamate all the applications and bring efficiency in the work place.


facilitate easier and faster data processing to provide information for faster managerial

decision making.


offer compact data storage, easier retrieval and promote data integrity and security.

3

1.4 The function of the new system

The proposed system is designed to provide a solution for the drawbacks of present system. It

aims to:

Replace Manual applications system with an automated one.

Reduce the chances of malpractices associated in a manual system.

Reduce the workload involved in applications

Update information system and provide easy access to corresponding information.

Full automated data storing through online

Online Checking Visa Status.

1.5 Scope of the project study

1.5.1 Scope of Project

These scope contents of this project have various activities to address at the public need on

documents applications; this gives encouragement to customer inherent their document on time

when needed.

Therefore, many of people who are non-native to any country in the nation are in needing visa

renewal applications to be done to them in order to live the Country as national do for passport

when needing to go to other nation. In nowadays the world of technology is changing and

advancing with many difficulty and challenges as the professional technical inherent to solve

challenges in the system in future. This web application will helps all the users to view the

registration documents in users friendly.

1.5.2 Achievement principles

Formerly accomplishment deeper, it is imperative to set principles for achievement which will

present a reference point when estimate and testing are been done. Hence, this project will have

flourished when it has fulfilled the following criteria:

4

The system accesses able and implements the necessary functionality associated with each. A

web User Interface has been developed for the application which displays users registrations

online contents on the clients screen in a coherent well-structured technique.

1.6 Interests of the project

1.6.1 Academic interests

In Rwanda, it looks that they are growing up in ICT (Information Communication Technology )

development where almost all business plans, government services are looking for .So this work

reminds and encourages students in BBIT departments to develop such more system applications

in different fields which is like a reference to their qualifications especially BBIT department-

RTUC students.

1.6.2 Public interests

Any success of this project causes many others government institutions to think about their

operations and services improvement by including most new technologies of using management

information system. This means that the available mechanisms of their functionalities are not

efficacy and more are hardly to apply. For that reason , it can be a public profit where they can

based on to improve their capacity of working and considering that those applications are

commercial package which are not very expensive where are efficient, faster , rapid, flexible and

even reliable systems so that they profit to apply it for their private operations .

1.6.3 Personal interests

The way this project is conducted and success ,it provides a good look to me and to my country

even to all the world where it defines me as the one who can offer such solutions of their system

improvement and its implementation so that it makes for me such profits.

1.7 Organization of the project report

The project report is organized in five chapters as follows

Chapter one: General introduction and background describe the most key features of the project

report and overview.

Chapter two: mainly in this chapter it describes the literature review which allows explaining

what tasks to be done in this project and of course defining the situation of the project. Then

5

describe and analyse the existing system where it is possible to establish their weak and strong

points.

Chapter three: this chapter is concerned to the system analysis in highlights the various

Research methodologies, mechanisms, software and hardware that are used when designing the

new system.

Chapter four: This chapter is concerned to the system design, explanation of the new system

design basing to the old system to the new one. It describes the key success of the new system

design.

Chapter five: This chapter covers the development, implementation, testing, and result of the

system, so there are establishment system interfaces.

Chapter Six: Finally the Recommendation and conclusion are made. In this part of the project

summary of the key points is provided.

6

CHAPTER TWO: LITERATURE REVIEWS

2.1 Introduction

This chapter covers the theoretical and fundamentals concepts used in this research and the goal

is to provide with an overview on the concepts that leads to the development of a web

application for passport and visa application management information system.

2.1 passport and visa application management information system

2.1.1 Passport applications

The passport is documents that use to be given to native if needed for traveling to the foreign

country which is process if he/she needs to travel to the other country.

2.1.2 Visa applications

The visa applications that allows you to travel to a port of entry, airport or land border crossing,

and request permission of the Immigration Department of Homeland Security, Customs and

Border Protection inspector to enter the country.

2.1.3 Passport and Visa applications Management Information System

Its the automatic system that will help quiet access and differ to the old system which requires a

lot of time for the small record in manually systems, it is a Client Server Project, Administrator

can be able to create many no of users and the users are called as Customers. Administrators will

describe the utilities accessed to the clients.

2.1.4 management system

A management system is the framework of processes and procedures used to ensure that an

organization can fulfill all tasks required to achieve its objectives.

For instance, an environmental management system enables organizations to improve their

environmental performance through a process of continuous improvement.

2.1.5 System

A set of detailed methods, procedures, and routines established or formulated to carry out a

specific activity, perform a duty, or solve a problem. All systems have (a) inputs, outputs, and

feedback mechanisms, (b) maintain an internal steady-state (called homeostasis) despite a

7

changing external environment, (c) display properties that are peculiar to the whole (called

emergent properties) but are not possessed by any of the individual elements, and (d) have

boundaries that are usually defined by the system observer. Systems underlie every phenomenon,

and are everywhere one looks for them.

2.2 Microsoft.NET Framework

The .NET Framework is a new computing platform that simplifies application development in

the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the

following objectives:

To provide a consistent object-oriented programming environment whether object code is

stored and executed locally, executed locally but Internet-distributed, or executed

remotely.

To provide a code-execution environment that minimizes software deployment and

versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance problems of

scripted or interpreted environments.

To make the developer experience consistent across widely varying types of applications,

such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the .NET

Framework can integrate with any other code.

2.3 Internet Explorer

The internet explorer is an example of an unmanaged application that hosts the runtime (in the

form of a MIME type extension). Using Internet Explorer to host the runtime enables you to

embed managed components or Windows Forms controls in HTML documents. Hosting the

runtime in this way makes managed mobile code (similar to Microsoft ActiveX controls)

possible, but with significant improvements that only managed code can offer, such as semi-

trusted execution and secure isolated file storage.

2.4 Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution, code safety

verification, compilation, and other system services. These features are intrinsic to the managed

code that runs on the common language runtime.

8

2.5 NET Framework Class Libraries

The .NET Framework class library is a collection of reusable types that tightly integrate with the

common language runtime. The class library is object oriented, providing types from which your

own managed code can derive functionality. This not only makes the .NET Framework types

easy to use, but also reduces the time associated with learning new features of the .NET

Framework.

2.6 Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the desktop,

enabling a user to perform a task. Client applications include applications such as word

processors and spreadsheets, as well as custom business applications such as data-entry tools,

reporting tools, and so on. Client applications usually employ windows, menus, buttons, and

other GUI elements, and they likely access local resources such as the file system and peripherals

such as printers.

2.7 Server Application Development

Server-side applications in the managed world are implemented through runtime hosts.

Unmanaged applications host the common language runtime, which allows your custom

managed code to control the behavior of the server. This model provides you with all the features

of the common language runtime and class library while gaining the performance and scalability

of the host server. The following illustration shows a basic network schema with managed code

running in different server environments. Servers such as IIS and SQL Server can perform

standard operations while your application logic executes through the managed code.

2.8 ASP.NET

ASP.NET is the hosting environment that enables developers to use the .NET Framework to

target Web-based applications. However, ASP.NET is more than just a runtime host; it is a

complete architecture for developing Web sites and Internet-distributed objects using managed

code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing

mechanism for applications, and both have a collection of supporting classes in the .NET

Framework.

Finally, like Web Forms pages in the managed environment, XML Web service will run with the

speed of native machine language using the scalable communication of IIS.

9

2.9 Active Server Pages.NET

ASP.NET is a programming framework built on the common language runtime that can be used

on a server to build powerful Web applications. ASP.NET offers several important advantages

over previous Web development models:

2.9.1 Enhanced Performance.

ASP.NET is compiled common language runtime code running on the server. Unlike its

interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time

compilation, native optimization, and caching services right out of the box. This amounts to

dramatically better performance before you ever write a line of code.

2.9.2 World-Class Tool Support.

The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio

integrated development environment. WYSIWYG editing, drag-and-drop server controls, and

automatic deployment are just a few of the features this powerful tool provides.

2.9.3 Power and Flexibility.

Because ASP.NET is based on the common language runtime, the power and flexibility of that

entire platform is available to Web application developers. The .NET Framework class library,

Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASP.NET is

also language-independent, so you can choose the language that best applies to your application

or partition your application across many languages. Further, common language runtime

interoperability guarantees that your existing investment in COM-based development is

preserved when migrating to ASP.NET.

2.9.4 Simplicity.

ASP.NET makes it easy to perform common tasks, from simple form submission and client

authentication to deployment and site configuration. For example, the ASP.NET page

framework allows you to build user interfaces that cleanly separate application logic from

presentation code and to handle events in a simple, Visual Basic - like forms processing model.

10

Additionally, the common language runtime simplifies development, with managed code

services such as automatic reference counting and garbage collection.

2.9.5 Manageability.

ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying

settings to your server environment and Web applications. Because configuration information is

stored as plain text, new settings may be applied without the aid of local administration tools.

This "zero local administration" philosophy extends to deploying ASP.NET Framework

applications as well. An ASP.NET Framework application is deployed to a server simply by

copying the necessary files to the server. No server restart is required, even to deploy or replace

running compiled code.

2.9.6 Scalability and Availability.

ASP.NET has been designed with scalability in mind, with features specifically tailored to

improve performance in clustered and multiprocessor environments. Further, processes are

closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks,

deadlocks), a new process can be created in its place, which helps keep your application

constantly available to handle requests.

2.9.7 Customizability and Extensibility.

ASP.NET delivers a well-factored architecture that allows developers to "plug-in" their code at

the appropriate level. In fact, it is possible to extend or replace any subcomponent of the

ASP.NET runtime with your own custom-written component. Implementing custom

authentication or state services has never been easier.

2.10 Security:

With built in Windows authentication and per-application configuration, you can be assured that

your applications are secure.

2.11 CSS

Cascading Style Sheets (CSS) is a simple mechanism for adding style like fonts, colors, and

spacing to Web documents. It is a style sheet language used to describe the presentation

11

semantics of a document written in a markup language. CSS is mainly used to style web pages

written in HTML and XHTML, but can also be applied to any kind of XML document, including

plain XML, SVG and XUL.

CSS is designed primarily to enable the separation of document content (written in HTML or a

similar markup language) from document presentation, including elements such as the layout,

colors, and fonts. This separation can improve content accessibility, provide more flexibility and

control in the specification of presentation characteristics, enable multiple pages to share

formatting, and reduce complexity and repetition in the structural content. CSS can also allow

the same markup page to be presented in different styles for different rendering methods.

2.12 SQL

Structured Query Language (SQL) is the standard language for accessing relational databases.

12

CHAPTER THREE: SYSTEM ANALYSIS

3.1 Introduction

This chapter focus on analyzing the current systems was created to solve problems. One can

think of the systems approach as an organized way of dealing with a problem. In this dynamic

world, the subject System Analysis mainly deals with the software development activities can

refer to the science that studies the methods of solving problem. Most sciences have their own

specific methodology. Research methodology is intended to highlight the methods and

techniques that have been used in order to collect data and tools for working on the project. The

information gathering techniques used to get userful information about Passport and Visa

application management information system included interview, observation and documentation.

System Analysis

Systems analysis is the study of sets of interacting entities, including computer systems analysis.

This field is closely related to requirements analysis or operations research. It is also "an explicit

formal inquiry carried out to help someone (referred to as the decision maker) identify a better

course of action and make a better decision than he might otherwise have made.

Need For Systems Analysis

Business systems are usually complex. Making changes to a system without reference to its

effects on other subsystems or current working practices could result in a worsening rather than

improvement. Systems analysis will identify

Outputs and application processing needed.

Data required providing this application processing and output.

Role of people in the application process.

Security aspects to ensure the efficient continuation of the business.

Costs of providing the system.

The Role of the Systems Analyst

13

Liaison with senior management and the computer manager (Data Processing Manager )

Investigate aspects of the business and produce a Feasibility Report that will be presented

to the board or suitable body.

Attend meetings to decide the way forward and provide technical expertise to the board

in making this decision. Recommend a particular solution.

Make detailed investigations of the affected sections of the e business and consult with

the users who are using the current system.

Design all aspects of a new system. Report on developments to the board and identify any

likely changes needed/problems discovered as a result of investigations. Produce a

systems specification.

Begin the implementation by convening a meeting of the new system designers. Provide

the programmers with individual program specifications. The programmers may actually

be database specialists. Set up planning schedules.

Order Hardware and any structural/electrical wiring changes needed to buildings.

Liase with programmers on progress. Chase up problems. Begin preliminary user

training.

Supervise testing of new programs. User training with programs.

Supervise completion of documentation.

Acceptance tests. Changeover. Hand-over

Monitoring of existing systems. Regular reviews to see if changes are needed.

Supervise maintenance and inclusion of new requirements.

14

3.2 Information Gathering

During the gathering of data we had again knowledge and understand on how the current system

will operate with the researcher employed the following techniques to the information about the

new system

3.2.1 Interview

Interview was the method used to get data collection by asking permission in how I can meet

with the Director of Immigration Department and staff, as we met after long struggle of getting

time to meet, it was my pleasure to ask them how their old system work and suggest this

proposal system. Oral interviews, phone calls and social media facebook and skype were used

while asking for information pertaining passport and visa processing. Various categories of

people were contacted during the interview which included; staffs of the Directorate of

immigration and emigration, passports and nationals, immigrants and applicants of passports and

visas.

3.2.2 Observation

Observation is a method of data collection used when researchers want to know what happened

in the field.This method may be direct in the field or direct in the controlled environments.

Observation involves recording the behavioral patterns of people, objects and events in a

systematic manner. They chose of this technique because its special in a way that it enables the

researcher to get some facts that could not be revealed by any other technique. Those techniques

are specially the rate or speed of execution in each department, the quality of service to

customers, and staff as well and the attitude of respecting immigration rules about the new

system under the development.

3.2.3 Documentation

Documentation is the method based on reading books, documents and browsing from internet

searching for necessary information related to the topic.In this project, different books and

websites related to the project were consulted. The Internet and the Library were import

resources during the information gathering from documents. This idea came to my thought that

15

after I have gone with so many books in reading them mentioned as above to have a new ideas in

order to be put in documentation.

3.3. Description of existing System

The existing is the manual system that consumes time of process and entering information.

The problems, which are perceived by the customers / users in existing systems are;

Less Efficiency and accuracy due to lot of manual entries

More Time Delay for payments.

Increased expenditure for storage

Lag of information while enquire about particular employee

Increased in Labor

3.4 Description of Proposal system

This proposed system is designed to provide a solution for the drawbacks of existing system.

That will replace Manual applications system with an automated one which can reduce the

chances of malpractices associated in a manual system in order reduce the workload involved in

processing applications while the system will be up-to-date information system and provide easy

access to corresponding information.

The proposed system is designed to provide a solution for the drawbacks of present system. It

aims to:

Replace Manual Processing system with an automated one.

Reduce the chances of malpractices associated in a manual system.

Reduce the workload involved in processing

Update information system and provide easy access to corresponding information.

Full automated data storing through online

Online Checking Visa Status of clients.

16

3.5 Methods

In this project the methods used are based on software engineering process and standards of

system analysis and design. It provides for all majors workflows in the project including

requirements gathering,analysis design,implementation,coding and testing.

3.6 Software development model

Software development models also known as software Life cycle or software process describe

phases of the software cycle and the order in which those phases are executed. Each phase

produces deliverables required by the next phase in the life cycle. Requirements are translated

into design. Code is produced during implementation that is driven by the design. Testing

verifies the deliverable of the implementation phase against requirements.

The general phases of the software life cycle are the following:

Requirements: System requirements are gathered in this phase. This phase responds to

the general questions which are: who is going to use the system? How will they use the

system? What data should be input into the system? What data should be output by the

system? This produces a nice big list of functionality that the system should provide,

which describes functions the system should perform, business logic that processes data,

what data is stored and used by the system, and how the user interface should work. The

overall result is the system as a whole, how it performs, not how it is actually going to

do it.

Design: The software system design is produced from the results of the requirements

phase. This is where the details on how the system will work are produced. Architecture,

including hardware with software, communication, software design (UML is produced

here) are all part of the deliverables of a design phase.

Implementation: Code is produced from the deliverables of the design phase during

implementation, and this is the longest phase of the software development life cycle. For

a developer, this is the main focus of the life cycle because this is where the code is

produced. Implementation may overlap with both the design and testing phases. Many

tools exists (CASE tools) to actually automate the production of code using information

gathered then producing during the design phase.

17

Testing: During testing, the implementation is tested against the requirements to make

sure that the product is actually solving the needs addressed, gathered during the

requirements phase. Unit tests with system/acceptance tests are done during this phase.

In order to meet the results of this research project, the modified waterfall model is used.

3.6.1 Modified waterfall model

The modified waterfall model is a sequential development process as the pure waterfall model, in

which development is seen as flowing steadily downwards through the general phases of

requirements, design, implementation and testing as well as allowing backtracks to earlier stages

of development when an error occur.

Requirements

Design

Implementation

Testing

Figure 1: A modified waterfall model

3.6.2 Activities in waterfall model.

This model has the following activities. Software Requirements Analysis, Systems Analysis and

Design, Code Generation / implementation, Testing / verification and Maintenance

Advantages of modified waterfall model

Simple and easy to use.

More flexible than the pure waterfall model.

It is documentation driven, that is, documentation is produced at every stage.

The amount of resources required to implement this model is very minimal.

18

After every major stage of software coding, testing is done to check the correct

running of the code.

Limitations of the waterfall model

The model implies that one should attempt to complete a given stage before

moving on to the next stage.

Does not account for the fact that requirements constantly change. It also means

that users cannot use anything until the entire system is complete.

The model makes no allowances for prototyping.

One cannot go back, if the design phase has gone wrong, things can get very

complicated in the implementation phase.

Small changes or errors that arise in the completed software may cause a lot of

problem.

19

3.7 Proposed system is illustrated using the following data flow diagrams

Introduction to data flow diagram

A data flow diagram includes the data, processes, stores, and external entities of a system, and all

of the data necessary for the system to function (both how it flows and where it is stored).

3.7.1 Level 0 data flow diagram (context diagram)

Figure 2: context diagram (logical)

3.8 UML

UML (Unified Modeling Language) is used to specify, visualize, modify, construct and

document the artifacts (software development) of an object oriented software intensive system

under development. UML offers a standard way to visualize a system architectural blueprint,

including elements such as: actors, activities, business process, business process, database

schemas, and Logical components and programming languages statements etc...

3.8.1 Use Case Diagram of Main Functionality of South Sudan PVAMIS

South Sudan Passport and Visa Application Management System has been designed with two

Main actors: Administrator, client. Clients can read or apply online for her/his visa in PVAMIS

applications that he/she has fil in his/her informations for the Administrator to record and

process her/his passport visa . In general administrator controls all functionalities of the system.

20

Admin

Users

Figure 3: Use Case Diagram

3.9 Physical data flow diagram level 1 of the current system

The physical DFD show the physical aspects of the system as well as the information flow so the

DFD below describes the interaction of staff involved with the system and how the information

is following the clients making application enquiry of the approval, all the processes are show

here such enquiry of application form, checking applicants qualify clients for visa apps, payment

for processes, and their data store to keep records after one process.

Registrations

Log in

Online app

Upload bank slip

Logout

21

Figure 4: Physical diagram level 1 DFD of current system

22

3.7.2 Activity Diagram for admin login

An activity diagram is defined as a flow chart that shows the flow of activities that are involved

in a single process.

Yes

No

Figure 5: Activity diagram for administrator

login

start

Enter username n

pwd

Login

validate

End

Viladate login

Done

23

3.7.3 Sequence diagram

The Sequence Diagram models the collaboration of objects based on a time sequence. It shows

how the objects interact with others in a particular scenario of a use case.

1.Administrator

2.Login to system

3.Invalid access

4. Clients applying for Visa applications

7. Store clients data

5.Logoff system 6.Encyption Clients app

Figure 6: Sequence Diagram

3.8 Limitations of current system

As with every project, this project has also got some of the restriction, which should be followed

when it used. These restrictions are listed below:

User must have a valid email-id.

User can login only one time.

Only registered user can approve applicants requests.

Hence finally we can conclude that if handled with care this project will lead to an efficient

approach in answer checking.

Admin Access Clients records Encryption algo Database

24

CHAPTER FOUR: SYSTEM DESIGN

4.1 Introduction

This chapter clearly illustrates the diagrams used in design, and techniques used to develop

passport and visa application management information system and its implementation.

4.2 Entity Relationship Diagram

Entity-relationship (ER) diagram is a specialized graphic that illustrates the relationships

between entities in a database. ER diagrams often use symbols to represent three different types

of information. Rectangle is commonly used to represent entities. Diamonds are normally used to

represent relationships and are used to represent attributes.

Types of Database Relationships

There are three different types of database relationships, each named according to the number of

table rows that may be involved in the relationship. Each of these three relationship types exists

between two tables.

One-to-one relationships occur when each entry in the first table has one, and only one,

counterpart in the second table. One-to-one relationships are rarely used because it is often more

efficient to simply put all of the information in a single table.

One-to-many relationships are the most common type of database relationship. They occur when

each record in the first table corresponds to one or more records in the second table but each

record in the second table corresponds to only one record in the first table. For example, the

relationship between a Applications table and a documentstype table in an passport and visa

database would likely be a one-to-many relationship.

Many-to-many relationships occur when each record in the first table corresponds to one or more

records in the second table and each record in the second table corresponds to one or more

25

records in the first table. For example, the relationship between a document category and a

applications table would likely be many-to-many have more than one instructor.

Figure 7: ERD diagram for the propose system

4.3 Database normalization

Define the above topic

Table 1: Table structure matches the report format

Table 1: table structure matches the report format

26

4.3.1 first normal form

The normalization process involves getting our data to conform to progressive normal form, and

higher level of normalization cant be achieve unless the previous levels have been satisfied.

Tables 1NF

Applications(Applicationsid,Documenttypeid,Documentcategoryid,Firstname,Lastname,DOB,Fa

thername,Mothername,Telephone,Email,Address,applicationdate)

Passportissuing(Passportissuingid,Applicationid,issuedate)

Applicationpayments_Applicationsid_Paymentid(Applicationpaymentid,Applicationsid,Payment

id) this is the relationship btn three tables applications, payment and applications.

4.3.2 Second normalization form

Where the first normal form deals with atomicity of data, the second normal formal form(or

2NF) deals with relationships between composite key column and non-key columns. As stated

earlier, the normal forms are progressive, so to achieve second normal form, your tables must

already be in first normal form.

The second normal form (or 2NF) any non-key columns must depend on the entire primary key.

In the case of a composite primary key, this means that a non-key column cant depend only part

of the composite key.

Tables in 2NF

Applications(Applicationsid,Documenttypeid,Documentcategoryid,Firstname,Lastname,DOB,Fa

thername,Mothername,Telephone,Email,Address,applicationdate)

Applicationpayments (Applicationpaymentid,Applicationsid,Paymentid) this is the relationship

btn three tables applications, payment and applications.

Documentcategory(Documentcategoryid,Documenttypeid,documentname)

Approvalstatus(approvalstatusid,applicationsid,approval,statusdate,comments,approvalstatus)

Processingstatus(processingstatusid,applicationid,statusdescription,date)

Documenttype(documenttypeid(primary,Passportvisarequirementsid,documentname)

Payment(Paymentid,paymentdescription,paymentamount)


27

4.3.3 Third normal form

The third normal form (3NF) requires that all columns depend directly on the primary key tables

violate the third normal form when one column depends on another column, which in turn

depends on the primary key(a transitive dependency)

One way to identify transitive dependencies is to look at your table and see if any columns would

require updating if other column in the table was updated. If such a column exists, it probably

violate 3 NF

Tables in 3NF below:

Documentcategory(Documentcategoryid,Documenttypeid,documentname)

Approvalstatus(approvalstatusid,applicationsid,approval,statusdate,comments,approvalstatus)

Processingstatus(processingstatusid,applicationid,statusdescription,date)

Documenttype(documenttypeid,Passportvisarequirementsid,documentname)

Payment(Paymentid,paymentdescription,paymentamount)


28

4.4 Data Base Scheme

The term database system implies that the data is managed to some level of quality (measured in

terms of accuracy, availability, usability, and resilience) and this in turn often implies the use of

a general purpose database management system (DBMS). A general purpose DBMS is typically

a complex software system that meets many usage requirements and the databases that it

maintains are often large and complex. The utilization of databases is now so widespread that

virtually every technology and product relies on databases and DBMSs for its development and

commercialization, or even may have such software embedded in it. Also, organizations and

companies, from small to large, depend heavily on databases for their operations.

Figure 8: Data Base Scheme

29

4.5 Data Dictionary

A data dictionary is a collection of descriptions of the data objects or items in a data model for

the benefit of programmers and others who need to refer to them. A first step in analyzing a

system of objects with which users interact is to identify each object and its relationship to other

objects.

In this database management systems, a file that defines the basic organization of a database. A

data dictionary contains a list of all files in the database, the number of records in each file, and

the names and types of each field. Most database management systems keep the data dictionary

hidden from users to prevent them from accidentally destroying its contents. Data dictionaries do

contain any actual data for the database, only pvamis information for managing it. Without a data

dictionary, however, a database management system cannot access data from the database

Tables attributes Constrain datatype Description

Applications

Applicationsid primary key varchar(10) AplicationsID

Documenttypeid Forgein key varchar(10) documenttypeid

Documentcategoryid Forgein key varchar(10) documentcategoryid

Firstname Not null varchar(10) Applicant fname

Lastname Not null varchar(10) Name

DOB Not null Smalldate(20) Date of birth

Fathername Not null varchar(10) Father name

Mothername Not null varchar(10) Mother name

Telephone Not null varchar(10) telephone

Email Not null varchar(10) e-mail

Address Not null varchar(10) address

applicationdate Not null Smalldate(20) Application date

Applicationpaymenti Primary key varchar(10) applicationpaymenti

30

Applicationpayments d d

Applicationsid Forgein key varchar(10) applicationid

Paymentid Forgein key varchar(10) paymentid

Documentcategory

Documentcategory

id

Primary key varchar(10) documentcategoryid

Documenttypeid Forgein key varchar(10) documenttypeid

documentname Not null varchar(10) Document name

Approvalstatus

approvalstatusid Primary key varchar(10) Approval status id

applicationsid Forgein key varchar(10) applicationsid

approvalstatusdate Not null varchar(10) date

Comments Not null varchar(10) comments

approvalstatus Not null varchar(10) Reject or approval

processingstatusid Primary key varchar(10) Processing statusid

Processingstatus

processingstatusid Primary key varchar(10) processingstatusid

statusdescription Not null varchar(10) Status description

applicationid Forgein key Varchar(10) applicationid

Date Not null Smalldate(20) date

Documenttype

documenttypeid Primary key varchar(10) documentypeid

Passportvisarequire

mentsid

Forgein key varchar(10) Visa Requirement id

documentname Not null varchar(10) name

Payment

Paymentid Primary key varchar(10) Payment id

paymentdescription Not null varchar(10) Payment description

paymentamount Not null varchar(10) paymentamount

Passportissuing Passportissuingid Primary key varchar(10) Date of issue

Applicationid Forgein key varchar(10) applicationid

Issuedate Not null smalldate(20) Issue date

Table 1: data dictionary

31

4.6 Architecture design of the Proposed System

The architecture design is software application architecture is the process of defining a structured

solution that meets all of the technical and operational requirements, while optimizing common

quality attributes such as performance, security, and manageability. It involves a series of

decisions based on a wide range of factors, and each of these decisions can have considerable

impact on the quality, performance, maintainability, and overall success of the application.

Figure 9: Architecture design of the Proposed System

Home page

of

Passport and Visa

Application MIS

Applications

Documentcategory

Payments

Documents Types

Approval issuing

Approval status

Applicationspayment

Processing Status

Administrator

Staff

Database

32

CHAPTER FIVE: IMPLEMENTATION AND TESTING

5.1 Implementation

Implementation is the carrying out, execution, or practice of a plan, a method, or any design for

doing something. For the Online criminal records checking system it provides the

encompassetion of all processes involved in getting new application properly in its environment

including running ,testing ,and making necessary changes to the PVAMIS.

5.2 User interfaces Application forms

The user interface applications form is the space where interaction between humans (users) and

the system occurs. The user is not concerned to the backend (codes) of the system.

The goal of user interface applications to the PVAMIS is to make their access easy in term of

time factor, efficient and enjoyable wherever you are in as its desired for your results and get

feedback to respective mail for coming for more information.

Figure 10: Applications form

33

5.2.1 Home page for login

This is the general home page which provides the way to login and it is authenticated (secured)

by using the user name and password. The user may login as administrator, police station

commander or judicial officer. This interface is available to all users of the system, so that each

user must have own user name and password which means that each user is provided personal

operations on the system. The figure below shows the main page of the system where all users

must pass though:

Figure 11: user login form

5.3 Test Process

The testing is the process of detecting errors. Testing performs a very critical role for quality

assurance and for ensuring the reliability of software. The results of testing are used later on

during maintenance also Psychology of Testing. The aim of testing is often to demonstrate that a

program works by showing that it has no errors. The basic purpose of testing phase is to detect

the errors that may be present in the program. Hence one should not start testing with the intent

of showing that a program works, but the intent should be to show that a program doesnt work.

Testing is the process of executing a program with the intent of finding errors.

34

Testing Objectives:

The main objective of testing is to uncover a host of errors, systematically and with minimum

effort and time. Stating formally, we can say,

Testing is a process of executing a program with the intent of finding an error.

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it exists.

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable standards.

Levels of Testing

In order to uncover the errors present in different phases we have the concept of levels of testing.

The basic levels of testing are

Client Needs Acceptance Testing

Requirements System Testing

Design Integration Testing

Code Unit Testing

A series of testing is done for the proposed system before the system is ready for the user

acceptance testing.

The steps involved in Testing are:

35

5.3.1 Unit Testing:

Unit testing focuses verification efforts on the smallest unit of the software design, the module.

This is also known as Module Testing. The modules are tested separately. This testing carried

out during programming stage itself. In this testing each module is found to be working

satisfactorily as regards to the expected output from the module.

5.3.2 Integration Testing:

Data can be grossed across an interface; one module can have adverse efforts on another.

Integration testing is systematic testing for construction the program structure while at the same

time conducting tests to uncover errors associated with in the interface. The objective is to take

unit tested modules and build a program structure. All the modules are combined and tested as a

whole. Here correction is difficult because the isolation of cause is complicate by the vast

expense of the entire program. Thus in the integration testing stop, all the errors uncovered are

corrected for the text testing steps.

5.3.3 System testing:

System testing is the stage of implementation that is aimed at ensuring that the system works

accurately and efficiently for live operation commences. Testing is vital to the success of the

system. System testing makes a logical assumption that if all the parts of the system are correct,

then goal will be successfully achieved.

Figure 12: system testing after entering information

36

5.3.4 Validation Testing:

At the conclusion of integration testing software is completely assembled as a package,

interfacing errors have been uncovered and corrected and a final series of software tests begins,

validation test begins. Validation test can be defined in many ways. But the simple definition is

that validation succeeds when the software function in a manner that can reasonably expected by

the customer. After validation test has been conducted one of two possible conditions exists.

One is the function or performance characteristics confirm to specifications and are accepted and

the other is deviation from specification is uncovered and a deficiency list is created. Proposed

system under consideration has been tested by using validation testing and found to be working

satisfactorily.

5.3.5 Output Testing:

After performing validation testing, the next step is output testing of the proposed system since

no system could be useful if it does not produce the required output in the specified format.

Asking the users about the format required by them tests the outputs generated by the system

under consideration. Here the output format is considered in two ways, one is on the screen and

other is the printed format. The output format on the screen is found to be correct as the format

was designed in the system designed phase according to the user needs. For the hard copy also

the output comes as the specified requirements by the users. Hence output testing does not result

any corrections in the system.

5.3.6 User Acceptance Testing:

User acceptance of a system is the key factor of the success of any system. The system under

study is tested for the user acceptance by constantly keeping in touch with the prospective

system users at the time of developing and making changes wherever required.

5.4 Test Data

Taking various kinds of test data does the above testing. Preparation of test data plays a vital role

in the system testing after preparing the test data the system under study is tested using the test

data. While testing the system by using the test data errors are again uncovered and corrected by

using above testing steps and corrections are also noted from the future use.

37

5.5 Testing

The testing done here was System Testingchecking whether the user requirements were

satisfied. The code for the new system has been written completely using JSP as the coding

language, HTML as the interface for front-end designing and Java Script for validating the

client-side applications. The new system has been tested well with the help of the users and all

the applications have been verified from every nook and corner of the user.

Although some applications were found to be erroneous these applications have been corrected

before being implemented. The flow of the forms has been found to be very much in accordance

with the actual flow of data.

5.6 Summary

Under the circumstances, this was the most effective testing available. The user interface tests

consisted of observing each evaluator. These highlighted a few problems, but as specified at the

start of this document, this project was inclined more towards the technology, not HCI.

Finally, one complete sample test-run through the passport and visa processing application was

implementation of users interfaces and observation of documented which included screen shots

of some of the screens.

These were developing a highly functional content-based website that shows you how to use

ASP.NET 3.5, ASP.NET CSS, the ADO.NET Entity Framework, and various external APIs to

their full capacity. This chapter gave you a broad idea about what were going to discuss, design,

and implement throughout the rest of the book.

In each chapter, youll learn something new about ASP.NET and web programming, and at the

end of the book you will have created a real-world site with most of the features required by

modern content-centric sites and e-commerce stores. Furthermore, the site you develop in this

book may provide a good deal more functionality than any site youve designed in the past, and

the relatively small development effort will enable you to do more than you thought possible in a

small amount of time. One of Microsofts key goals with the .NET platform is to help you fall

38

into the pit of success. ASP.NET is designed to make developers jobs easier: to reduce the

amount of effort required to implement common functionality, thereby giving them more time to

focus on business needs, and enabling them to offer more advanced functionality to empower

users and site administrators, while keeping the site maintainable and scalable. This book will

help you judge whether Microsoft has met this goal.

39

CHAPTER 6: CONCLUSION AND FUTURE IMPROVEMENT

6.1 Conclusion

The Passport and Visa Applications Management Information System is a web-based application

for online the visa transactions in which provide customized solutions to meet

company/customer needs. This application software has been computed successfully and was

also tested successfully by taking test cases. It is user friendly, and has required options, which

can be utilized by the user to perform the desired operations.

The software is developed using ASP.NET as front end and SQL as back end in Windows

environment. The goals that are achieved by the software are:

Instant access.

Improved productivity.

Optimum utilization of resources.

Efficient management of records.

Simplification of the operations.

Less processing time and getting required information.

User friendly.

Portable and flexible for further enhancement.

40

RECOMMENDATION

Further improvement and implementation of this system, I recommend the South Sudan

Immigration Department to take and use this application so that it can get more researchers in

software development in order to increase the performance including handling the missing

functionalities which are not covered in this product.

I recommended RTUC to provide the way all students of BBIT department may be encouraged

to develop more ideas in software development in order to develop industrial, company software

level from simple application.

I recommend the Department of BBIT and RTUC to facilitate and encourage students to use

online open source or web application as it is more helpful to develop different software

dependingontherequiredissues.

41

6.2 Future Improvement

This section describes issues and recommendation point out by the evaluate of the project. It is

therefore imperative to mention that in the subsequent versions of system the following

recommendations will have to be incorporated.

It should be possible to send and read emails with attachments. Most email users will

always prefer to send additional documents to a mail message as an attachment.

It should be possible for user to send messages with embedded html formatting and

images in later versions of system.

PVAMIS will have to give logical feedback to users in form of warnings, customized

error messages and acknowledgement.

Ability to create more customized users.

Support for address book.

42

REFERENCES

[1] Microsoft (2005) MSDN

[2] ASP.NET 3.5 Website Programming by Chris Love

[3] Evangeleous Petereous C#.NET Black Book

[4] Binh Nguyen (2003), Linux Dictionary, Version 0.11

[5] Grady Booch, Ranbaugh,Jacobson (2007) unified modeling language

[6] Roger.S. Pressman (2009) Software engineering

[7] Jain (2005) SQL FOR PROFESSIONALS

[8] Steven Holzner (2005) complete html

[9] Alex Weeks (2004), The Linux System Administrator's Guide version [0.9]

[10].The American idealist philosopher Josiah Royce 1935, [1958]), Fundamentals of

Methodology Part I Definitions and First Principles by C. S. Herrman

[11].Vikram Vaswani [2010] MySQL Database Usage & Administration

[12]. Avison D. E. and Fitzgerald G. (1995), Information Systems Development: Methodologies,

Techniques and Tools 2nd Edition, McGraw-Hill.

[13] Rob Birdwell (2003) Beginning ASP.NET 1.0 with Visual Basic .NET

Electronic sources

[14] Joji Babu [2001- 2006], management processing information system by Sagitta Software

Technologies Project www.sagittasoft.com [April 2012]

[15] Macmillan Computer Publishing (2012), Java 1.2 unleashed; [march 18, 2012]

http://www.webbasedprogramming.com/Java-1.2-Unleashed/ch34.htm