MOBILE BASED ONLINE HELP DESK FOR DEBRE

BERHAN UNIVERSITY

A Senior Project Documentation Submitted to Debre Berhan University in

Partial Fulfillment of the Requirement for the Degree of Bachelor of Science in
Computer Science

By Group Seven

Name Id
1. Tigist Tamre………………………………… DBU07002017UR
2. Adane Alemayehu…………………………… DBU07001976UR
3. Sharew Alemu ………………………………. DBU07002014UR
4. Getaneh Belayneh…………………………… DBU07002025UR

Advisor: Faris Awol.

Department: - Computer Science

College of Computing, Department of Computer Science DBU

Debre Berhan University, Debre Berhan Ethiopia,

May 2018.
 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Approval
The project is our own and has not been presented for a degree in any other university with this
functionality and all the source of material used for the project has been duly acknowledged.

Name and Signature of the project group members

Name Signature

1. Tigist Tamre …………………………

2. Adane Alemayehu ………………………….
3. Sharew Alemu ………………………….
4. Getaneh Belayneh ………………………….

Name of Advisor Signature

…………………… …………………………

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

Examiners Name Signature

1. Examiner 1 …………………………
2. Examiner 2 …………………………
3. Examiner 3 …………………………
4. Examiner 4 …………………………

Department Of Computer Science Page I

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Acknowledgment
First of all, we would like to express our special thanks to almighty God for helping us through all
our steps from the starting up to finishing of our work in such beautiful manner. Then the team
would like to thanks to the project advisor, Ins. Faris Awol. For his valuable guidance and advice.
And the last we would like to thanks for us.

Department Of Computer Science Page II

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Contents

Approval ......................................................................................................................................................... I

Acknowledgment .......................................................................................................................................... II

List of Figure ............................................................................................................................................... VIII

List of table................................................................................................................................................... IX

List of Acronyms ............................................................................................................................................ X

CHAPTER ONE ............................................................................................................................................... 1

INTRODUCTION OF WHOLE PROJECT PROCESS ............................................................................................ 1

1.1 Introduction .................................................................................................................................. 1

1.2 Background information of the organization...................................................................................... 1

1.2.1 Vision of the organization ............................................................................................................ 1

1.2.2 Mission of the organization ......................................................................................................... 1

1.3 Background of the project .................................................................................................................. 2

1.4 Problem statement ............................................................................................................................. 2

1.5 Team composition............................................................................................................................... 2

1.6 Objective of the project (SMART) ....................................................................................................... 3

1.6.1 General objective ......................................................................................................................... 3

1.6.2 Specific objective ......................................................................................................................... 3

1.7 Scope and limitation of the project .................................................................................................... 4

1.7.1 Scope of the project ..................................................................................................................... 4

1.7.2 Limitation of the project ....................................................................................................... 4

1.8 Significance of the project .................................................................................................................. 5

Department Of Computer Science Page III

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

1.9 Target beneficiaries of the project...................................................................................................... 5

1.10 Methodology for the project ............................................................................................................ 5

1.10.1 Data collection method.............................................................................................................. 7

1.10.2 System Analysis and Design Methodology ................................................................................ 8

1.10.3 CASE Tools .................................................................................................................................. 9

1.10.4 Testing Procedure .................................................................................................................... 10

1.11 Risks & contingencies (What if Analysis?)....................................................................................... 10

CHAPTER TWO ............................................................................................................................................ 12

DESCRIPTION OF THE EXISTING SYSTEM .................................................................................................... 12

2.1 Introduction of existing system......................................................................................................... 12

2.2 Players of the existing system ........................................................................................................... 12

2.3 Major functions/activities in the existing system like inputs, processes and outputs ..................... 12

2.4 Business rules .................................................................................................................................... 13

2.5 Report generated in the existing system .......................................................................................... 13

2.7 Bottlenecks of the existing system (using for example PIECES frame work) .................................... 16

2.9 proposed solution for the new system ............................................................................................. 18

2.10 Requirements of the proposed system........................................................................................... 18

2.10.1 Functional requirements..................................................................................................... 18

2.10.2. Non-Functional requirements................................................................................................. 19

CHAPTER THREE .......................................................................................................................................... 20

SYSTEM ANALYSIS ....................................................................................................................................... 20

Department Of Computer Science Page IV

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

3.1 System models .................................................................................................................................. 20

3.1.1 Scenarios .................................................................................................................................... 20

3.1.2 Use case model .......................................................................................................................... 20

3.1.3 Use case description .................................................................................................................. 23

3.1.4 Object model.............................................................................................................................. 31

3.2 Dynamic model ................................................................................................................................. 35

3.2.1 Sequence diagram...................................................................................................................... 35

3.2.2 Activity diagram ......................................................................................................................... 42

3.2.3 State diagram (if any) ................................................................................................................. 51

3.2.4 User interface prototype (navigational paths and screen mock-ups) ....................................... 53

3.2.5 Supplementary specification ..................................................................................................... 54

CHAPTER FOUR ........................................................................................................................................... 55

SYSTEM DESIGN .......................................................................................................................................... 55

4.1 Introduction ...................................................................................................................................... 55

4.1.1 Purpose of the system ............................................................................................................... 55

4.1.2 Design goals ............................................................................................................................... 55

4.2 Current software architecture .......................................................................................................... 56

4.3 Proposed software architecture ....................................................................................................... 56

4.3.1 Overview .................................................................................................................................... 56

4.3.2 Subsystem decomposition ......................................................................................................... 57

4.3.3 Hardware/Software mapping ............................................................................................. 58

4.3.4 Persistent data management ..................................................................................................... 59

4.3.4.2 Database Design...................................................................................................................... 61

4.3.5 Access control and security........................................................................................................ 62

Department Of Computer Science Page V

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

4.3.6 Global software control ............................................................................................................. 62

4.3.7 Boundary conditions .................................................................................................................. 62

4.4 Subsystem services ........................................................................................................................... 63

4.5 Component Diagram ......................................................................................................................... 63

4.6 Deployment Diagram ........................................................................................................................ 65

CHAPTER FIVE ............................................................................................................................................. 66

OBJECT DESIGN ........................................................................................................................................... 66

5.1 Introduction ...................................................................................................................................... 66

5.2 Object design trade-offs.................................................................................................................... 66

5.3 Interface documentation guidelines ................................................................................................. 66

5.4 Packages ............................................................................................................................................ 66

5.5 Class interfaces.................................................................................................................................. 66

CHAPTER SIX................................................................................................................................................ 68

IMPLEMENTATION AND TESTING ............................................................................................................... 68

6.1 Introduction ...................................................................................................................................... 68

6.2 Final Testing of the system ............................................................................................................... 68

6.3 Hardware software acquisitions ....................................................................................................... 68

6.4 User manual preparation .................................................................................................................. 69

6.5 Training ............................................................................................................................................. 73

6.6 Installation Process ........................................................................................................................... 73

6.7 Start-up strategy ............................................................................................................................... 73

Department Of Computer Science Page VI

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

6.8 Coding ............................................................................................................................................... 74

CHAPTER SEVEN .......................................................................................................................................... 89

CONCLUSIONS AND RECOMMENDATION................................................................................................... 89

7.1 Conclusions ....................................................................................................................................... 89

7.2 Recommendations ............................................................................................................................ 89

References .................................................................................................................................................. 90

APPENDIX .................................................................................................................................................... 91

Department Of Computer Science Page VII

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

List of Figure
Figure 1:waterfall Model............................................................................................................................... 7
Figure 2:Report Generate Form .................................................................................................................. 14
Figure 3:Form of Main Board ...................................................................................................................... 15
Figure 4:Form of Direction Indicator .......................................................................................................... 16
Figure 5:Use Case Model ............................................................................................................................ 23
Figure 6:Class Diagram ................................................................................................................................ 34
Figure 7:Sequence Diagram for get Information ........................................................................................ 35
Figure 8:Sequence Diagram for Register information ................................................................................ 36
Figure 9:Sequence Diagram for Help .......................................................................................................... 37
Figure 10:Sequence Diagram for Update information ............................................................................... 38
Figure 11:Sequence Diagram for Login ....................................................................................................... 39
Figure 12:Sequence Diagram for Create Account....................................................................................... 40
Figure 13:Sequence Diagram for Change password ................................................................................... 41
Figure 14:Activity Diagram For Get information......................................................................................... 43
Figure 15:Activity Diagram For Register information ................................................................................. 44
Figure 16:Activity Diagram For Get help ..................................................................................................... 45
Figure 17:Activity Diagram For Feedback ................................................................................................... 46
Figure 18:Activity Diagram For Change Password ...................................................................................... 47
Figure 19:Activity Diagram For Login .......................................................................................................... 48
Figure 20:Activity Diagram For Update information .................................................................................. 49
Figure 21:Activity Diagram For Create Account .......................................................................................... 50
Figure 22:State Diagram Login .................................................................................................................... 51
Figure 23:State Diagram Create account .................................................................................................... 52
Figure 24:State Diagram Get information................................................................................................... 53
Figure 25:User interface or prototype ........................................................................................................ 54
Figure 26:Proposed software architecture ................................................................................................. 57
Figure 27:Subsystem Decomposition ......................................................................................................... 58
Figure 28:Hardware/software mapping ..................................................................................................... 59
Figure 29:Database Mapping ...................................................................................................................... 60
Figure 30:Database Design ......................................................................................................................... 61
Figure 31:Component Diagram ................................................................................................................... 64
Figure 32:Deployment Diagram .................................................................................................................. 65
Figure 33:User manual Interface ................................................................................................................ 70
Figure 34:User manual interface ................................................................................................................ 71
Figure 35:User manual Interface ................................................................................................................ 72

Department Of Computer Science Page VIII

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

List of table
Table 1: Team Composition .......................................................................................................................... 3
Table 2: Use Case Description for Login...................................................................................................... 23
Table 3: Use Case Description for View ...................................................................................................... 24
Table 4: Use case Description for Give feedback ........................................................................................ 25
Table 5: Use case Description of Get Help .................................................................................................. 26
Table 6:Use case Description of Register information................................................................................ 27
Table 7: Use case Description of Get information ...................................................................................... 27
Table 8: Use case Description of Update information ................................................................................ 28
Table 9: Use case Description of Create account ....................................................................................... 29
Table 10: Use case Description of Change password ................................................................................. 30
Table 11: Use case Description of Mange account ..................................................................................... 31
Table 12: Data Dictionary of Create account .............................................................................................. 32
Table 13: Data Dictionary of Register College ............................................................................................ 32
Table 14: Data Dictionary of Register class room ..................................................................................... 32
Table 15: Data Dictionary of login............................................................................................................... 33
Table 16: Data Dictionary of Register building ........................................................................................... 33
Table 17: Data Dictionary of Register office ............................................................................................... 33
Table 18: Access control and security ......................................................................................................... 62
Table 19: Appendix ..................................................................................................................................... 91

Department Of Computer Science Page IX

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

List of Acronyms
DBU-------------------------------------------------Debre Berhan University

UML-------------------------------------------------Unified Modeling Language

SQL--------------------------------------------------Structural Query Language

OS----------------------------------------------------Operating System

CD----------------------------------------------------Compact Disc

DVD-------------------------------------------------Digital Versatile Disc

BR---------------------------------------------------Business Rule

UC--------------------------------------------------Use Case

HTTPS---------------------------------------------Hyper Text Transfer Protocol Secure

JDC------------------------------------------------Java Database Connectivity

MBOHD------------------------------------------Mobile Based Online help desk

.apk-------------------------------------------------is a file extension type on the android application file.

FK-------------------------------------------------Foreign Key

PK------------------------------------------------ Primary Key

Department Of Computer Science Page X

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER ONE

INTRODUCTION OF WHOLE PROJECT PROCESS

1.1 Introduction
This chapter will introduce about background of the study, and overview of the system that
developed which is the project aims and objectives, summary modules description, project scope,
project limitation, project team, the outline of approach or methodology, development
environment, case tool used.

1.2 Background information of the organization

Debre Berhan University, which is 11 young University is established in the 600 years old
historical town Debre Berhan. A town situated in Amara Region, North Showa Zone, 130km away
from Addis Ababa in the north. This university make different infrastructure for users in the
compound of Debre Berhan University, so help desk which gives information for user how to get
their target information or place. This university start help desk by understanding the tiredness of
the users. Help desk is the most important to function in a campus that solves users get not clear
information. Users can be contact to the help desk workers due to the reason that users want to get
information of the organization. It supports relating to Debre Berhan university information as
well as information regarding to products and services of the organization to the end users. In
Debre Berhan University help desk worker gives the information to the user or employee by
moving place to place or by different adverts related to the user needs to get information.

1.2.1 Vision of the organization

 Aspires to be the best university in Ethiopia by 2020.

1.2.2 Mission of the organization

 Producing efficient graduates by offering research assisted quality education.

Department Of Computer Science Page 1

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Undertaking a problem solving research based on national need and benefiting the
community with the outcome.
 Offering government and community centered training, consultancy service, transferring
technology and undertaking innovation.

1.3 Background of the project

A help desk is a resource intended to provide the end user with information and support related to
a companies or institution's products and services. The purpose of a help desk is usually to solve
problems or provide guidance about product. People may have different work at different places.
They may forget to keep track of all the work which is associated at different places. So we
proposed a system where user will be reminded about their work at certain place where the work
is associated with. This application also works even when user does some other task in their mobile
phone. This system can be used to automate the workflow of service requests for the various
facilities in the organization /campus. This is an integrated system that covers different kinds of
facilities like labs, colleges, departments, dormitory’s, offices, buildings. We motivate to work this
project to reduce the problem like the user to get the target information.

1.4 Problem statement

At present the current system works manually. It provides the information in written or orally
within the organization/campus. The following are the most problems of the current system: -

 Time consuming during finding summarized information.

 It has long procedures to obtain the information.
 Wastage of resource like paper, human power.
 It does not provide all information regarding any query at a time.
 The user cannot get information at any time because it has time limitation, individual has
to apply within the working hours of an organization/campus.

1.5 Team composition

The project team is composed from four members as follows

Department Of Computer Science Page 2

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Table 1: Team Composition

Project Title Mobile Based online help desk for DBU

Prepared by No. Member name ID Number Responsibility
1 Tigist Tamre DBU07002017UR leader
2 Adane DBU07001976UR Vice- leader
Alemayehu
3 Sharew Alemu DBU07002014UR secretary
4 Getaneh DBU07002025UR member
Belayneh
Advisor Faris Awol

1.6 Objective of the project (SMART)

The general and specific objective of the project is described below.

1.6.1 General objective

The general objective of the project is to design and implement Mobile based online help desk for
DBU.

1.6.2 Specific objective

In order to achieve the general objective of this project we will have the following specific
objective. These include:

 To study the existing system so as to identify:

 The working principle
 Business rules that need to be enforced
 Players of the existing system and their role
 To propose a new and automated solution
 To study the proposed solution so as to identify the:
 Functional requirement
 Non-functional requirement

Department Of Computer Science Page 3

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Suitable technology
 Hardware requirement
 Software requirement
 To design the proposed system in such a way that it will:
 Eliminate data redundancy
 Be user friend
 To develop user friendly and interactive system.
 To implement and test.
 To forward recommendation.

1.7 Scope and limitation of the project

1.7.1 Scope of the project

The proposed system focused on developing mobile based online help desk for Debre Berhan
University. It provides necessary information for users about Debre Berhan University such as
Buildings, Dormitory’s, Colleges, Offices, Libraries and administrator can be register information
about buildings, dormitory, laboratory, college and office information. Our system runs on android
studio.

1.7.2 Limitation of the project

The main limitation of our project is: -

 The proposed system is implemented only for Debre Birhan University and cannot
authenticate the users.
 The system doesn’t show each student dorm and full personal information.
 The system doesn’t show give course information.
 Our application supports only show main office like president, academic vice president,
and college dean office.
 The system doesn’t show the number of student in Debre Birhan University.
 The system doesn’t show the amount of budget in Debre Birhan University.

Department Of Computer Science Page 4

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

1.8 Significance of the project

The significance of the proposed system is changing the manual system to Mobile based system
for Debre Birhan University. It has a good opportunity for user to observe the campus states and
get the services. The following are some Significance like: -

 Get information easily and clearly too desired destination place.

 Minimize wastage of time.
 Decrease economical cost like metal (tin), writer, and worker.
 Reducing human effort and improving quality of work flow.
 Provide self-help to the end users.

1.9 Target beneficiaries of the project

The target beneficiary of the proposed systems is Debre Birhan university customer, guest and any
other people who get information from DBU. The most target beneficiary of our project is:

End user: Who have knowledge on how to access information using mobile.

DBU: After finishing implementation DBU is one of the beneficiary due to reduce the number of
employee i.e. saving cost increase, Resource wastage decrease.

1.10 Methodology for the project

Methodology is a system of board principles or rules from which specific method for procedure
may be derived to interpret or solve different problems within the scope of a particular discipline.
In our system we choice a waterfall model how to work this project. Due to choice a waterfall
model, waterfall model is simple and liner and sequential phase of developing the project. In
waterfall model there are some process such as requirement, design, implementation, testing,
verification and maintenance. Show in detail: -

Requirement: - It involves understanding what need to be design and what its function, purpose
for the project is.

Design: -Uses specifying hardware and system requirements and also helps in defining the system
architecture.

Department Of Computer Science Page 5

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Implementation: - Used to development the works are performed and development the
component or units hand to test the project.

Testing: - The project team performs some tests on that unit of program to know if it is error free.
This testing level helps us to decide that individual units of the program are working as per
requirement and are error free.

Verification: - Is used how the system install.

Maintenance: - This occurs after installation, and involves making modification to the system.

Show in diagram below: -

Department Of Computer Science Page 6

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 1:waterfall Model

1.10.1 Data collection method

Observation: - We see that a person keeps their queue to get information, a person set down near
to help desk office until the office open, the employee who works on the help desk she/he moves
from place to place with users to show the required information, and also a person who asks the
students to get the location of help desk.
Interviewing: -. To ask help desk workers in what way user get information, due to this help desk
responses users can get information by direction indicator, mainboard, and by moving users with

Department Of Computer Science Page 7

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

help desk adept, to show by orally and to attach the notice. User can get building information and
main office. A help desk worker can be generated reports how information is located for users in
month to the public relation director office.
Literature review: - The teams also try to read and understand about the problems related to our
project in different written documents.

1.10.2 System Analysis and Design Methodology

The project team plan to use the object oriented design methodology for the development of the
system among the different methodologies. Because it is better way to construct, manage and
assemble objects that are implemented in our system. Object oriented design methodology has two
phases: -

Object Oriented System Analysis: During this phase the team will look at the problem domain
and with the aim of producing a conceptual model of the information that exists in the area which
will be analyzed. And this model the functions of the system (use case modelling), identifying the
business objects, organize the objects and also the relationship between them and finally model
the behavior of the objects.

Object Oriented System Design: During this phase the model interactions and behaviors that
support the use case scenario, and finally update object model to reflect the implementation
environment. And also transforms the conceptual model produced in object-oriented analysis to
take account of the constraints needed to our system, so that we will use this phase to improve the
use case model to reflect the implementation environment.

Reasons for the selection of Object Oriented System Analysis and Object Oriented System
Design are:

Increase reusability: - The object oriented provides opportunities for reuse through the concepts
of inheritance, polymorphism, and encapsulation.
Increased extensibility: -When you need to add new feature to the system you only need to make
changes in one part of the applicable class.
Flexibility: It is really flexible in terms of using implementations.

Department Of Computer Science Page 8

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Improved quality: - Quality of our system must be on time, on budget and meet our exceeded the
expectation of the users of our system, improved quality comes from increased participation of
users in the system development.

1.10.3 CASE Tools

 Android studio used to implementation part.
 Enterprise architecture used for Unified Modeling Language Diagram.
 XAMP is used to design database design.
 Koplayer is used for run the code
 Microsoft office 2010 used to preparation documentation.

1.10.3.1 System Development Environment

The project team decided to use the following hardware and software tools throughout the
progress.

The following tools are used to analyze the proposed system.

Hardware tools:

 Desktop computer/laptop.
 Displaying devices like printer.
 Hard disk, flash disk is used for the movement of data from one machine to another. We
use both of the devices when we move our data from one machine to another.
 Real device after finishing our implementation to use it.

Software tools:

 Microsoft word 2010: - Is very useful because it takes less time to write and format the
text, communicate effectively smart diagram and chart tools, quickly assemble document.
By looking its useful properties, we use Microsoft word to type our project work to get all
the above benefits of it.
 Microsoft PowerPoint is used for presentation.
 Gantt chart software to schedule time

Department Of Computer Science Page 9

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Enterprise architect application for UML diagram (use case diagram, sequence diagram,
class diagram, activity diagram, state chart diagram, component diagram, and deployment
diagram).
 Android OS: Android is a Linux base operating system designed primarily for touch screen
mobile devices such as smart phones and tablet computers.
 Antivirus is used to prevent, detect and remove computer virus.

1.10.4 Testing Procedure

Testing Procedures are the testing practices, processes and techniques used to ensure that the
software application is tested and validating before release or deployment.

There are different testing levels for a system. But we will use the following testing levels. These
are:

Unit Testing
While coding, the project team performs some tests on that unit of program to know if it is error
free. This testing level helps us to decide that individual units of the program are working as per
requirement and are error free.
Integration Testing
Even if the units of the system are working fine individually, there is a need to find out if the units
were integrated together would also work without errors. For example, we test argument passing
and data updating.
System Testing
The software is compiled as product and then it is tested as a whole.

1.11 Risks & contingencies (What if Analysis?)

During the development of the project there may be different problems that we may face. These
are:
Unfortunate failure of system: To handle this problem the teams have some method to resist not
completely but partially by using back up mechanisms using flash disks, CD/DVD and by storing
the data in more than two computers.

Department Of Computer Science Page 10

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Virus attack: It is difficult to control data from virus but try to scan the data, installing and
updating antivirus software.
Time management problem: We solve this problem by working cooperatively, divide our time
by schedule for each phase of the project and we try to use this schedule effectively.
One of our group members may be sick while in the process of project development: To solve this
problem the remaining group member together covers this member done.
Therefore, whatever situation happen or occurred that hinder during the progression of the project
the team try the best to do what expected and reform it.
System Failure: To solve this problem the organization workers must take backup file by
using external hard drive daily.
Power problem: We tried to use laptops to cover the gap happened to our project during
power failure.

Department Of Computer Science Page 11

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER TWO

DESCRIPTION OF THE EXISTING SYSTEM

2.1 Introduction of existing system

The existing system which means help desk is a manual system that everyone can see information
and go away through these information indicators to their desired destination. As we understand
from the existing system is backward and it use too much human labor to organize the system. The
existing system uses the board stapled on the specific area so to get the information one must go
to that specific area in addition to this the board contain only the specific information of the place
not road how to go to that specific office so the person who use this navigator is must additionally
ask other person who know the DBU well. It supports only local language so as a university many
foreigners will come up so they cannot navigate through the campus. Generally, this manual
system needs lot of resource consumption.

2.2 Players of the existing system

An existing system compromises different players to carry out its job. Among those different
players, the most common are: -
User: - Those users’ wants to get information by asking help desk workers, seeing by direction
indicators and also asking Debre Berhan university workers.
Writer: Those workers who are responsible for writing the drafted information to well-designed
word on the board.
Public relation directorate: - Who leads the help desk workers.
Help desk worker: - To guide information for any users.

2.3 Major functions/activities in the existing system like inputs,

processes and outputs
In the existing system the activities are works manually. Such as: -

Department Of Computer Science Page 12

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Users use direction indicators and mainboard as input to get information, which means
these direction indicators to play the role of information to guide users.
 The help desk workers use direction indicators as input to show information for users.
 The help desk workers show information for the users by moving one place to the other
place together.
 The help desk workers show information for the users by orally.

2.4 Business rules

The office does not have written or formal document regarding business rule, but as we have
discussed with the help desk worker the following business rule are:
BR1: - To prepare sample guiding material which indicates the direction of destination place.
BR2: -Help desk workers show the direction of place by orally.
BR3: - Help desk workers show the target place move together with user.
BR4: - Help desk workers put his/her signature daily to public relation director office.
BR5: -Help desk workers must be respect to users.
BR6: -Help desk workers must be known DBU sights.
BR7: -The users use ID cards to enter the university.

2.5 Report generated in the existing system

In the existing system reports are generated in the forms of manual. The help desk workers are
responsible to prepare reports how information is located for users in month to the public relation
director office. Show reports generate form as follow.

Department Of Computer Science Page 13

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 2:Report Generate Form

2.6 Forms and other documents of the existing systems

The forms and direction indicators of existing system is indicated as in the figure below.

Department Of Computer Science Page 14

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 3:Form of Main Board

Department Of Computer Science Page 15

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 4:Form of Direction Indicator

2.7 Bottlenecks of the existing system (using for example PIECES

frame work)
There are many different problems in the existing system, because of the manual service is not
reliable and not lead to the exact place that someone wants to go so due to this the following
problems.

Performance Problems:

Department Of Computer Science Page 16

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Through put: The time taken to find one place or Building is taking too much time in manual
navigation system.

Information Problems:

Output: It lacks full information on the main board. It displays only main office, it also lacks exact
indication of the wanted office or building and exact building may change its task because the
campus/organization is found in development.

Economics Problems:

Too much cost for metal (tin), writer, and worker

Material uses short time because the materials life time is to short due to resting by natural factor
like wind, rain, and temperature.

Efficiency Problems: The information indicator guide the general name partially specified and
when new building becomes available partially or completely the existing manual system a
problem that means they should reconstruct the board and add another information indicator.

Service problems: - If the building changed or replace their tasks, due to this reason so many
changes occurred, so the direction indicators are useless. From the list of information on the
mainboard someone finding exactly place not get destination place, so according to this someone
cannot get full information on the mainboard.

2.8 Practices to be preserved

Even if the existing system is manual and it has weakness, but there are some important activities
we should preserved to the proposed system. These practices are: -
 Solve problems by their order of request
 Provide service to the user

Department Of Computer Science Page 17

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

2.9 proposed solution for the new system

From the description of the existing problem, the project team identifies the above problems. So,
the team decides to solve the problems found in the existing system by appropriate systems. Hence,
we try to solve the problems by the following alternatives:

 Save time and resource: - It minimize the resource like Human labor, metal and so on, and
time takes for this manual navigation system by getting full information about building.
 Increase reliability: - The reliability of the system is increased by the information indicators
that we give the exact information of the building.
 Give information that is not recorded by the existing system, like collage dean.
 The system is supports at least one international language and one local language.
 The system cannot be affected by human or natural factor as easily.
 Automating the existing system using android studio.
 When new thing happening, then the information becomes update, which means when the
building, office, laboratory, library, any building found in the campus/organization can be
renewed.

2.10 Requirements of the proposed system

2.10.1 Functional requirements

Functional requirements are expressed as what system must do. Functionality of mobile based
online help desk is:
Login: -The administrator who are privileged for inserting the essential info in to database.
Update information: -The administrator can be update information when the thing is renewed
View information: -The user can be view the building information gates desired destination place.

Get information: -The user can see the information to the desired destination place.
Get help: -The user can see the instruction how to use this system.
Give feedback: -The user can be give feedback to the system, when cannot get full information.
View feedback: -The administrator can be view feedback.
Create account: - The administrators can create their own account.

Department Of Computer Science Page 18

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Change password: - The administrator changes his/her current password.

Update Account: - The Administrator can be update account.
Chat: users and admin can be communicating each other by using email and Facebook
Register information: - The administrator can be register building information and main office.

2.10.2. Non-Functional requirements

Non –functional reqiemnets are requirements that at are not directly concerned with the specific
servies delivered by the system to its users. They may relate to emergent system properties such
as reliablity and response time. Alternatively, they may define constraints on the system implement
such as the capablities of input and out put devies or other data reprsentations used in interfaces
with other systems. Those non-functional requirements are performace, securty or availability,
usability or contation characteristics of the system as whole.

Speed: - The system will perform very fast at the normal working condition of the network.

Availability: - The system helps us to give timely information for the user when they are around.

Reliability: The system that tells the full information of the building.

Security: The system doesn’t worry about any security that prevents it from monitoring the
business environment or from performing its main function, but the administrator can be secure to
register the building information.

Usability: - The system provides a help and brief description of how to use the system. That is
users can be use the system by reading help.

Department Of Computer Science Page 19

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER THREE

SYSTEM ANALYSIS

3.1 System models

Introduction

An important goal of requirement modelling is come to an understanding of the existing system

problem that the new system is to address. This chapter focuses on developing the requirement
and analysis models for the new system using the UML use case model, sequence diagram, activity
diagram and class diagram.

3.1.1 Scenarios
The user to get arrives to some destination place in the existing system. It may be getting
information from main board above figure2.1 that the user wants to go, and then the user may ask
someone who is a help desk worker or the user may follow the direction indicator described like
in the figure 2.2 Direction indicators. Users can get information by guided help desk workers.

3.1.2 Use case model

The Use Case model describes the proposed functionality of the new system. A use case represents
a discrete unit of interaction between user and system. A use case is a single unit of meaningful
work. An actor is a user of the system. This includes both human users and other computer systems.
An actor uses a use case to perform some piece of work which is of value to the business. For the
proposed system the actors are operate the application and administrator that register some
essential information from database. Generally, there are three component of use case model.
Those are

Actor: An actor represents a role of a user that interacts with the system that you are modeling.
The user can be a human, organization, machine, another external system modeling. It represents
as:

Department Of Computer Science Page 20

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Use case: A use case describes a function that a system performs to achieve the user’s goal. A use
case must yield an observable result that is of value to the user of the system.

Represents:

Use

Boundary: Describing the system by grouping the use cases in the rectangle boundary, the system
boundary in visual paradigm provides containment behavior.

Represents: Boundary

Actor Description

Administrator: Perform the activity of register the essential information into database on the local
server. That, this information may be building like Dormitory, laboratory, class room information
that the building contains many offices in it, so the administrator registers that information.

User: Those are the end user of the application that uses this application by installing on their
android mobile phone.

System Use Case Diagram for New System and Its Identification

To develop the use case diagram for proposed system the following use case identifications are
available:

View information: The user can be view the building information gates desired destination place.

Get information: The user can see the information to the desired destination place.

Department Of Computer Science Page 21

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Feedback: The user can be feedback to the system.

Get help: The user can see the instruction how to use this system.

Register information: The administrator can register information in the database.

Update information: The administrator can be update information which means when the
building, office, laboratory, library, any building found in the campus/organization can be
renewed.

Create account: The administrators have an account page.

Change password: The administrator can be change password.

Department Of Computer Science Page 22

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

uc Use Case Model

Use case diagram

View
Information
Chat

View
Feedback

Get
Register
Information «include»
information
Administrator
User

Login «include»

«include» Update
Giv e Feedback
Information

«include»

Create
account «extend» Mange account

Get Help Change «extend»

account «extend»

Update
Account

Figure 5:Use Case Model

3.1.3 Use case description

1. Use Case Login

Table 2: Use Case Description for Login

Use case No: UC-01

Department Of Computer Science Page 23

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Use case Name: Login

Participating Administrator
Actor (s):
Description: Administrator Login to system in order to have privileges for performing
different tasks.
Trigger: The admin must be logged to the system.
Priority: High
Basic course of Actor action System response
action: 1. Admin starts the system. 2. The system displays “Home Page”.
3. Admin Click login link. 4. The system Display the “Login
5. Admin enters username and Form”.
password and click on login 6. If username and password is valid, the
button. corresponding page for each user is
displayed (Alternatives A1: If it is
invalid).
7. The use case ends.
Alternative A1: If the user name and password is not valid (Basic course 5: if re-enter
course: the password)
A2: System displays error message
A3: End use case.

Preconditions: Admin must have account

Post condition: Admin successful login
2. Use Case View

Table 3: Use Case Description for View

Use case No: UC-02

Use case Name: View information
Participating Actor (s): User

Department Of Computer Science Page 24

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Description: The user can be view the building information to gets desired
destination place and users can view available data.
Trigger: The users can wants to get information.
Priority: high
Basic course of action: Actor action System response
1. The user clicks view 2. The system display
3. The user view any information.
information. 4. If viewing any information are
5. The user gets information. match (Alternatives A1. If the
6. The use case end. viewing any information does
not match )
Alternative course: A1. The user viewing any information does not match.
A2. The system displays invalid view (Basic course 3 again view)
A3. Use case end.
Preconditions: The actor needs to know the specific information.
Post condition: The actor obtains information.
3. Give Feedback

Table 4: Use case Description for Give feedback

Use case No: UC-03

Use case Name: Give feedback
Participating Actor (s): User
Description: The user can be feedback to the system.

Trigger: Users cannot get full information, and then give feedback to the
system.
Priority: medium
Basic course of action: Actor action System response
1. The user ask any information 2. The system display
information list.

Department Of Computer Science Page 25

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

3. The user see the information 5. The system accepts the

or data feedback.
3. Users cannot get full
information (Alternatives A1:
they get full information).
4. The user can give feedback
to the system.
6. Use case end.
Alternative course: A1: get full information.
A2. The system accepts feedback.
A3: End use case.
Preconditions: Users must be get or not get information.
Post condition: Users give feedback to the system.
4. Get Help

Table 5: Use case Description of Get Help

Use case No: UC-04

Use case Name: Get help

Participating actor(s): user

Description: This use case is used to see the instruction how to use the system
for end user of the system.
Trigger: When the user is not known how to use the system.
Priority: medium
Basic course of action: Actor action System response
1. The user clicks Get Help 2. The system display the
(Alternate Action A1). Get Help page.
3. The user view Get Help.
4. The use case end.
Alternative course: A1. If the user un know how to use (Basic course 1.).
A2.The use case end.

Department Of Computer Science Page 26

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Precondition: The user should know how to start the application.

Post condition: The user sees the instruction.
5. Register Information

Table 6:Use case Description of Register information

Use case No: UC-05

Use case Name: Register information
Participating actor(s): Administrator
Description: The administrator can register information on the database.
Trigger: When the admin login to the system.
Priority: High
Basic course of action: Actor action System response
1. The admin activate select 2. The system browses the page
Register info. for registration.
3. Fill the required information 4. The administrator inputs valid
5. Save. data. (Alternate course A1: If The
6. The use case end. administrator inputs invalid data).
Alternative course: A1: If The administrator inputs invalid data
The system displays incorrect message for the Admin.
A2: the use case end.
Precondition: The admin login to the system.
Post condition: The administrator get access to the registering the information on
database.

6. Get Information

Table 7: Use case Description of Get information

Use case No: UC-06

Use case Name: Get information
Participating actor(s): User

Department Of Computer Science Page 27

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Description: The user can see the information to the desired destination.
Trigger: When the admin login to the system.
Priority: High
Basic course of action: Actor action System response
1. The user starts the system. 2. The system
3. The user clicks the View button. opens the home
(Alternate Action A3). page of the system.
5. The use case end. 4. The system
display the
information.
Alternative course: A1. If the user cannot click correct view button.
A2.The use case end.
Precondition: The user can install the app.
Post condition: User gets information.
7. Update Information

Table 8: Use case Description of Update information

Use case No: UC-07

Use case Name: Update information
Participating actor(s): Administrator
Description: The administrator can be update information which means when the
building, office, laboratory, library, any building found in the
campus/organization can be renewed.
Trigger: When the admin update information.
Priority: Medium
Basic course of action: Actor action System response
1. The admin activate in the 3. The system displays store
home page information (Alternatives A1. The
2. The admin clicks update form. system cannot display any store
4. The admin view information. information).

Department Of Computer Science Page 28

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

5. The admin starts to update 5. The system store information in

information. to the database.
6. Use case end.
Alternative course: A1. The system cannot display any store information (Basic course 1.
The admin activates the home page)
A2. The admin activates update information.
A3. The system store updates information on database.
5. End use case.
Precondition: The admin can get a new thing.
Post condition: The admin can be update information.
8. Create Account

Table 9: Use case Description of Create account

Use case No: UC-08

Use case Name: Create account
Participating actor(s): Administrator
Description: The administrators have an account form.
Trigger: The admin create account
Priority: High
Basic course of Actor action System response
action: 1. The admin o Clicks 2. The system display “Create New
“Create New Account Account Form”.
Link”. 4. The system Validate data, and Save
3. The admin fill information (Alternative use A4: If data is invalid).
on the New Account Form, 5. The system Display “Account
and clicks save. Created Successfully” message.
6. The use case end.
Alternative course: A4: If data is invalid:
1. System displays error message, try again.
2. The admin fills required information on to “New Account Form”.

Department Of Computer Science Page 29

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Precondition: The admin first login.

Post condition: The admin create account.
9. Change Password

Table 10: Use case Description of Change password

Use case No: UC-09

Use case Name: Change password
Participating actor(s): Administrator
Description: The administrator can be change password.
Trigger: When the admin intended to new password.
Priority: Medium
Basic course of action: Actor action System response
1. Admin click sign up. 2. The system display “Sign
3. Enter old password, then new up form”.
password, and confirm new 4. The system validates the
password, click “Change password” new password information and
button. Save (Alternatives use A1: If
6. Admin see confirms message. new password information is
7. The use case end. invalid).
5. The system display
“Successful message”.
Alternative course: A1: If new password information is invalid:
1. The system displays error message, try again (Basic course 3 Enter
old password, then new password, and confirm new password, click
“change password “button.
2. End use case.
Precondition: The admin login to the application
Post condition: Password for the admin changed.
10. Manage Account

Department Of Computer Science Page 30

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Table 11: Use case Description of Mange account

Use case No : UC-015

Use case Name : Mange Account
Participating Administrator
Actor
Description The Administrator can be mange’s of Account, those are includes create
account, update account, create password, change password and login.
Trigger The Administrator mange’s the system
Priority High
Basic course of Actor action System response
Action 1.The administrator can create account to 2. The system display different
manage option or privileges.
3. The administrator selects one option 4. The system displays the form
from the system. from that select option.
5. The administrator fill full the required 6. The system save the data and
information/or data and clicks save it. display the message to the
7. The administrator sees the message. administrator (Alternatives A1.
8. End of use case. if the data is not valid to save).
Alternatives A1. If the data is not valid to save (Basic course 5. The administrator fills
course of Action full the required information/or data and clicks save it
A2. The system save information
A3. End use case
Precondition The administrator wants to mange’s account
Post condition The administrator to inserts the required data or information to the system

3.1.4 Object model

3.1.4.1 Data dictionary

Department Of Computer Science Page 31

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

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.

Table 12: Data Dictionary of Create account

Field Name Data type Description

ID Integer Holds id for the Admin

Username String Holds user name of the Admin.

password Varchar Holds password of the admin.

First Name Varchar Holds the name of Admin

Last Name Varchar Holds the father name of admin

Holds the phone number of the

Phone No Varchar
admin

Sex Varchar Holds the gender of the admin

Table 13: Data Dictionary of Register College

Field Name Data Type Description

College-id Int It holds college number
College-name varchar It holds college name
Phone Int It holds phone number of college
Email Varchar It holds email address of college
Fax Varchar It holds fax number of college
Table 14: Data Dictionary of Register class room

Field Name Data Type Description

Class room-Id Int It holds Class room number
Class room Name Varchar It holds Class room name

Department Of Computer Science Page 32

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Table 15: Data Dictionary of login

Field Name Data type Description

Username String Holds user name of the Admin.

password Varchar Holds password of the admin.

Table 16: Data Dictionary of Register building

Field Name Data Type Description

Building-Id Int It holds building number
Building Name Varchar It holds building name
Table 17: Data Dictionary of Register office

Field Name Data Type Description

Office-id int It holds office number
Office-name varchar It holds office name
Phone int It holds phone number of office
Email Varchar It holds email address of office
Fax Varchar It holds fax number of office

3.1.4.2 Analysis level class diagram (conceptual modeling)

Diagrams are used to represent the structure of the system in terms of objects, their notes and
nature of relationship between classes. The help desk provides the end user with supports related
to products and services of Debre Berhan University. Those users get information from the system.

Department Of Computer Science Page 33

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

class class Diagram

Dormitary Labratory room

Main Office
- Dormitary code: int - Building code: Varchar
- Building Name: varchar
- Dormitary name: varchar - Building name: int
- Building number: Varchar
+ create Labratory room(): void - Email: varchar
+ Create Dormitary(): Void
- occupation: varchar
1..* - Office Name: Varchar
1
- office Nmber: varchar
- OfficeCode: int
contain 0..* - Phone: int
Library
Contains - staff name: varchar
- library code: int Contains
1 + Create office(): Void
- library name: varchar
contain
+ create clinic(): Void 0..* Builiding *
1 has
1 - Builiding code: int
- Builiding name: Varchar
1 1
Role + Create Builiding(): Void
1
Contains College
- Name: varchar
- Role id: int - College code: int
+ create role(): void 0..* - College name: varchar
- Department: varchar
1 - Email: varchar
- phone: int
- program: varchar

+ Create staff(): void

1..*

Admin role

- Admin id: int

- Admin role id: int Admin account
Login
- role id: int
1..* 1 - Password: varchar
- Pasword: Varchar
+ create admin role(): void - User name: varchar
- User name: Varchar
1 1
+ Get password(): Void
+ get password(): void
+ Get user name(): Void
+ get user name(): void

1
has
1

Admin

- Address: varchar
- age: int
- First name: varchar
- Last name: varchar
- Sex: varchar

+ Create account(): Void

Figure 6:Class Diagram

Department Of Computer Science Page 34

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

3.2 Dynamic model

3.2.1 Sequence diagram

Sequence Diagrams are interaction diagrams that detail how operations are carried out. It is a
construct of a system. Sequence diagram shows object interactions arranged in time sequence. It
duplicates the objects and classes involved in the scenario and the sequence of messages exchange
between the objects needed to carry out the functionality of the scenario. Sequence diagrams are
typically associated with use case realizations in the logical view of the system under development.

sd Sequence diagram for Get information

User
Home page Get Information Controler Data base

Initial()

Click View Button()

Sequence Diagram for
Get Information
Display information()

Displayed()

Display the message()

Display the information()

Successfully Display ()

Get Information()

Figure 7:Sequence Diagram for get Information

Department Of Computer Science Page 35

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd Sequince Diagram Of Register information

Sequence Diagram of Admin

Register information Home Page Register form Control Database

Click Insert Button()

Select Fill information()

View Form()

Fill the form()

Check()

Validate()

Save into Database()

Saved()

Successfull Fill()

End End End End

End

Figure 8:Sequence Diagram for Register information

Department Of Computer Science Page 36

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd Sequince Diagram Of Get Help

Sequence Diagram of
Get help
User
Home Page Help Control

Click help()

View help()

Request()

Responce()

Display get help()

End End End

End

Figure 9:Sequence Diagram for Help

Department Of Computer Science Page 37

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd sequince Diagram of Update information

Sequence Diagram of
Update e information Admin
Home page Update form Control Database

Click Update()

Select Update Form()

Display Update form()

Fill the form()

Check()

Validate()

Save Update information()

Update()

Success full update()

End End End End End

Figure 10:Sequence Diagram for Update information

Department Of Computer Science Page 38

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd sequence diagram

Administrator
Home Page Login Checker Login form

Sequence Diagram for

Click on Login Link()
Login
Fetch Login page
form()

Return login form()

Display login page()

Fill username and password()

Click login button()

Accept input()

Check validation()
if invalid try again()

If valid the page display()

Return login confirmation()

Display success message()

Close()

End

Figure 11:Sequence Diagram for Login

Department Of Computer Science Page 39

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd sequence diagram

Administrator
Home page CreateAccount CreateAccount Database
form controler

Sequence Diagram for Initiate()

create Account

Click()

Open()

Display CreateAccount form()

Enter username and password()

Re-enter password confirm()

Click createAccount page()

Validate()

If not valid()

If valid()

Response confirmation message()

CreateAccount successfuly()

End

Figure 12:Sequence Diagram for Create Account

Department Of Computer Science Page 40

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

sd sequence diagram

Administrtor
Home page Login Form

Sequence Diagram for Click Login Link()

Change password

Desplay login form()

Login form Desplayed()

Click Change password button()

Password change()

Password successfully changed()

End

Figure 13:Sequence Diagram for Change password

Department Of Computer Science Page 41

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

3.2.2 Activity diagram

Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. It is constructed from a limited number of
shapes, connected with arrows. The most important shape types:

 Start-represents the beginning of a process or workflow in an activity diagrams.

 Activity- indicates the activities that make up a modeled process and it is the main
component of activity diagram
 Connector- arrowed lines that show the directional flow, or control flow, of the activity.
An incoming arrow starts a step of an activity, once the step is completed, the flow
continues with the outgoing arrow.
 Decision- represents the branching or merging of various flows with the symbol acting as
a frame or container.
 Note- allows the diagram creators or collaborators to communicate additional messages
that don’t fit within the diagram itself.
 End- represents the completion of a process or workflow etc.

Department Of Computer Science Page 42

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity diagram for get information

Click View Button

Initial

Activity diagram of Get Display information

information

Successfully Get
Information

Final

Figure 14:Activity Diagram For Get information

Department Of Computer Science Page 43

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity diagram of Register information

Ini ti al

Click Insert Button

Activity diagram of
Register Information

Select Builiding
Information

Fill The form

No
Val i date

Yes

Successful Fill

Fi nal

Figure 15:Activity Diagram For Register information

Department Of Computer Science Page 44

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of Get help

Ini ti al

Click Help

Activity Diagram of Get

help

View Help

Get Explanation of How

to use application

Fi nal

Figure 16:Activity Diagram For Get help

Department Of Computer Science Page 45

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of Feedback

Ini ti al

Click FeedBack

Activity Diagram of
Feedback

Display Feeddback page

Insert Feedback into text

Click Send

Fi nal

Figure 17:Activity Diagram For Feedback

Department Of Computer Science Page 46

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of change passw ord

Initial

Click Change Passw ord

Activity Diagram of
Change password

Enter new Passw ord

Confirm Passw ord

No
Yes
Valid
enter

Successfull Changed

Final

Figure 18:Activity Diagram For Change Password

Department Of Computer Science Page 47

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of Login

Initial

Select Login Menu

Activity Diagram of
Login

Display Login page

Enter User name and

passw ord

Click Login button

No
Validate User name
and password

Yes
Login to the system

Final

Figure 19:Activity Diagram For Login

Department Of Computer Science Page 48

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of UPdate information

Initial

Activity Diagram of
Update information Click update

Display update page

Enter update information

No
Validate enter Yes

Successfull update

Final

Figure 20:Activity Diagram For Update information

Department Of Computer Science Page 49

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Activ ity Diagram of Create account

Initial

Select Create account

menu

Activity Diagram of
Create account

Enter user name and

passw ord

Confirm Passw ord

Click Create Button

No
Validate
Password

Yes

Successfull Create

Final

Figure 21:Activity Diagram For Create Account

Department Of Computer Science Page 50

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

3.2.3 State diagram (if any)

State-chart diagram describes the flow of control from one state to another state. States are defined
as a condition in which an object exists and it changes when some event is triggered. So the most
important purpose of State-chart diagram is to model life time of an object from creation to
termination.

stm State Diagram of Login

Failed

State Diagram of Login

[Again]
[User name and password not match]

Waiting Login
[Admin Enter User name and Password] Waiting User name
[Admin start the system] Information
and Password Valid

Initial

[User name and password match]

Login

[Success]

Final

Figure 22:State Diagram Login

Department Of Computer Science Page 51

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

stm State Diagram of Create account

Idle

Initial

[Create Account]

State Diagram of Create

account Display Form

[Fill Form]

Incorrect fill Correct fill

Final

Figure 23:State Diagram Create account

Department Of Computer Science Page 52

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

stm State diagram for Get information

Idle

Initial

[Click]

v iew button

State diagram for Get

Information [View]

Disply Information

Successfuly v iew
information

end

Figure 24:State Diagram Get information

3.2.4 User interface prototype (navigational paths and screen mock-ups)

The user interface is the main component that is used as a communication medium between the
user and the system. We do have a user Interface as described below

Department Of Computer Science Page 53

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 25:User interface or prototype

3.2.5 Supplementary specification

In our system the main factor is, we cannot give the route name which is found in our local area.
This is because Ethiopia is unable to make changes on google map. And also the library which is
used to connect our application to the built in the phone’s GPS application is not freely available.

Department Of Computer Science Page 54

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER FOUR
SYSTEM DESIGN

4.1 Introduction
System design is the transformation of the analysis model into a system design model. System
design is the first part to get into the solution domain in a software development. This chapter
focuses on transforming the analysis model into the design model that takes into account the non-
functional requirements and constraints described in the problem of the statement and requirement
analysis section discussed earlier.

The purpose of designing is to show information how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the system
with high quality. Implementing of high quality system depend on the nature of design created by
the designer. If one wants to change to the system after it has been put into operation depends on
the quality of the system design. So if the system is design clearly, it will be easy to make changes
to it.

4.1.1 Purpose of the system

The product in this project is clearly know that is an. apk extension file which is extracted from an
android application developing software specifically called android studio integrated development
environment. The scope of the product covers the area with too much or excessive network
coverage.

4.1.2 Design goals

Design goals describe the qualities of the system that develops should optimize. The objectives of
design are to model the system with high quality. The design goals are derived from non-functional
requirements that means non-functional requirement is the description of the feature characteristics
and attribute of the system as well as any constraints that may limit the boundary proposed
solution. The goal of the system design is to manage complexity by dividing the system in to
manageable pieces.

Department Of Computer Science Page 55

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Some of design goal are listed below,

Modifiability: -The system should be modifiable for further modification and enhancement of the
application.

Flexibility: - The system able to change to suit new condition situation.

Efficiency: - The new application process efficiently in terms of space and time.

Performance: - May include the speed and memory requirements of the system.

Maintainability: - The application should be easily extensible to add new functionalities at a later
stage.

4.2 Current software architecture

The currents existing system of help desk is used in manual system and as this is no software
architecture.

4.3 Proposed software architecture

4.3.1 Overview
The proposed system will be implemented in three tier architecture this three tier architecture are
application layer/ presentation layer, business layer and data access layer. Application or
presentation layer is the form which provides the user interface it either end user or programmer.
The business layer is the class which uses to write the function which works as a mediator to
transfer data from presentation layer to data access layer. This layer also has a property layer which
is a class where variable is declared to the field of the data base which can be required for the
application and makes the properties into the variables. Access layer is to set/to get from data to
database queries back and forth. The database queries or store procedures will be written here to
access the data from the database.

Department Of Computer Science Page 56

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

act Deployment Model

«device» «device»
Android mobile «device»
WebBrowser
phone serv er

network
HTTPS

JDBC

«device»
Database

Figure 26:Proposed software architecture

4.3.2 Subsystem decomposition

Subsystem decomposition is the process of dividing the system into manageable subsystems from
the analysis model of the proposed system. The goal of the system decomposition is to reduce the
complexity of design model and to distribute the class of the system into large scale.

Department Of Computer Science Page 57

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

cmp Sub system Decomposition

Register Information
Manage Account

Update Information
Create Account

Update Account
Mobile Based online Help Desk

Change Password

Get Information

View Information
Assign role

Get Help

Figure 27:Subsystem Decomposition

4.3.3 Hardware/Software mapping

Department Of Computer Science Page 58

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

deployment Hard ware soft ware mapping

<<Application>> «device»
MBOHD.APK Android Mobile

Install

Application Serv er

Manage account Datebase serv er

Client Application HTTPS

Android Data base mysql
Android Studio
Register
information

View Information

Figure 28:Hardware/software mapping

4.3.4 Persistent data management

The administrator can be save their building information that should be persistently kept in the
database and it can be possible for updating information to same building information to save in
to the database.

4.3.4.1 Mapping

Department Of Computer Science Page 59

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

class Mapping Diagram

Library Table
Library
Staff Staff Table
- Library code: int
- Library code: int
- Name: Varchar(50) - Email: Varchar - Email: Varchar(50)
- Name: Varchar
- Fax: Varchar - Fax: Varchar(50)
- Name: Varchar - Name: Varchar(50)
Office Table - phone: int - Phone: int(15)
Office - staff code: int - Staff code: int
- Email: Varchar(50)
- Email: Varchar - Fax: Varchar(50)
- Fax: varchar - Name: Varchar(50)
- Name: varchar College Table
- Office code: int College
- Office code: int - Phone: int(15) - College code: int
- Phone: int - College code: int
- Email: Varchar(50)
- Email: intVarchar
- Fax: Varchar(50)
Lab-room Lab-room Table - Fax: Varchar
- Name: Varchar(50)
- Name: Varchar
- Lab- room code: int - Phone: phone(15)
- Lab-room code: int - Phone: int
- Name: Varchar - Name: Varchar(50)
Admin role Table
Admin role
- Admin Id: int
Builiding Builiding Table - Admin id: int - Admin role id: int
- Admin role Id: int - Role id: int
- Builiding code: int - Builiding code: int - Role id: int
- Name: Varchar - Name: Varchar(50)

Admin account Table

Dormitary Table Admin account
Dormitary
- Admijn id: int
- Dormitary code: int - Admin id: int
- Dormitary code: int - Password: varchar(50)
- Name: Varchar(50) - Password: Varchar
- Name: Varchar - User name: Varchar(50)
- User name: VArchar

Figure 29:Database Mapping

Department Of Computer Science Page 60

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

4.3.4.2 Database Design

Figure 30:Database Design

Department Of Computer Science Page 61

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

4.3.5 Access control and security

Here we will describe the privileges or authorities of actors over the functionalities. In this system
there are two actors such as User and Administrator. Each has their own privileges to gain access
of the system. But in this application the user is any public user who uses the application so to
make security for this is somehow unwanted. Below is the description of access control using
access control matrix.

Table 18: Access control and security

Access control Administrator User

Login  
Change password  
Create account  
Register information  
View information  
Get information  
Get help  
Feedback  

4.3.6 Global software control

Our new system is action performed give full information with text for user but our system mainly
uses for its functionality or to do well.

4.3.7 Boundary conditions

Boundary condition is the process of how to use the application of online help desk. Which
includes: -

 System start up: - Users starts to use this system first install the application then after
installation end the user can be view information.
 System exit: - When users can want to get information users can be exit the system.
 Error handling: - The system will handle the error happen during data insertion to get
information.

Department Of Computer Science Page 62

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

4.4 Subsystem services

Manage account: this subsystem is used to manage the account.

It contains: -

Update account: -this subsystem is used to update account.

Change password: -this subsystem is used to change new password.

Create account: -this subsystem is used to create new account

Information register: - this subsystem is used to record information. It includes

Insert information: -this subsystem is used to record building and their related information.

Update information: - this subsystem is used to update when new information is happening
(renewed).

Manage information: - this subsystem is used to how to get information. It includes

View information: This subsystem contains the view service for the user of this app to view the
information when the users reach the destination place.

Get Help: This Subsystem contains the instruction how to use the application and it contains: -

Get Help: This subsystem contains the Help service for the user of this application to see the
instruction how to use this application.

4.5 Component Diagram

This diagram depicts the components of the system and their interaction. Actors and their
corresponding activities are illustrated by the component diagram.

Department Of Computer Science Page 63

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

cmp Componet diagram

Register
information
Administrator

Secuirty

Manage account

View information
MBOHD
Database

User Give feedback

Get help

Figure 31:Component Diagram

Department Of Computer Science Page 64

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

4.6 Deployment Diagram

The deployment diagram specifies a set of constructs that can be used to define the execution
architecture of systems that represent the assignment of software artifacts to nodes. Nodes are
connected through communication paths to create network systems of arbitrary complexity. Nodes
are typically defined in a nested manner, and represent either hardware devices or software
execution environments.

deployment Deployment Diagram

«device» «executionEnvironme...
Application Serv er mysql
Android Dev ice

MBOHD.APK MBOHD
MBOHD
HTTPS Database
Application JDBC

HTTPS

«device»
Smart phone

WebBrowser

Figure 32:Deployment Diagram

Department Of Computer Science Page 65

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER FIVE

OBJECT DESIGN
5.1 Introduction
Mobile Based Help desk system has a lots of subsystem that makes it a full system hence by
working separately but working together in the way that by calling each other using their
instantiated object they make the whole system. In this chapter we will consider each behavior of
the subsystem as well as the whole system.

5.2 Object design trade-offs

In the object design phase some trade-off decisions may need to be made: It is all about a situation
that involves losing one quality or aspect of something in return for gaining another quality or
aspect.

5.3 Interface documentation guidelines

Interface documentation guidelines and coding conventions are the most important factors that
can improve communications between developers during object design.

5.4 Packages
Packages are used in Java in order to prevent naming conflicts, to control access, to make
viewing/locating and usage of classes, interfaces, enumerations and annotations easier, etc. A
Package can be defined as a grouping of related types (classes, interfaces, enumerations and
annotations) providing access protection and name space management.

We use our project package is package com.example. sharik.helpdesksystemfordebrebrihan

university.

5.5 Class interfaces

In our project use different class like:

Home class: -this class describes title of our project.

College class: -consist of department list

Department Of Computer Science Page 66

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Get Building class: -consists of building information such as office building, college, lab room,
dormitory.

Feedback Class: - Users can be send feedback and admin can be view feedback.

Contact class: - Users can be contact phone ,email them, write to them, or go to see them in
order to tell or ask them something.

About Class: - Descripts how work the project and descripts back ground of the organization

Help class: - The class name Help is used for providing the user a start-up guide or an advanced
information for the users of the application.

Department Of Computer Science Page 67

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER SIX

IMPLEMENTATION AND TESTING

6.1 Introduction
In this section we do the Coding of the all documents gathered starting from requirement analysis
to Design phase. So now the team is in a position of converting all documents gathered and
designed into the code so that the system will be implemented for the user to be used for the
purpose it developed.

6.2 Final Testing of the system

Our team used an ordered procedure to test the system developed as listed below:

Unit testing: - it is the first testing method we used to test each module that build the whole
system by applying some selection mechanism. Through this mechanism every modules gets
tested. If an error occurs correction will be taken without affecting another module. So that it
plays the crucial role for testing the module easily without difficulty.

Integrated testing: - it is the next step we implemented after we successfully ensure that each
single module is working correctly ever after all related module combined together and tested
together for the correct fitness with each other and with the systems functionality. If error occurs
in combining them, the module with problem will be identified and fixed without need of much
effort.

System testing: - it is the last step we implemented after we successfully integrated each related
single module for the purpose of building the overall functional testing of the system by
checking whether it meets the required target or not. Here is the last procedure that system
reached its requirement.

6.3 Hardware software acquisitions

For the project implementation the following Software and hardware are used.

Hardware

Department Of Computer Science Page 68

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Computer (desktop, Laptop)

 Android Phone

Software

 Android Studio
 Note pad++
 Xampp database
 Koplayer Emulator

6.4 User manual preparation

Since the system is android application everything we expect important for the user will be
explained using Help buttons in the help desk menu and in some basic activity of the application
and implemented while preparation of short training document when the system is deployed.

Department Of Computer Science Page 69

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 33:User manual Interface

Department Of Computer Science Page 70

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 34:User manual interface

Department Of Computer Science Page 71

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Figure 35:User manual Interface

Department Of Computer Science Page 72

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

6.5 Training
During the deployment of the system, our project team will give short time training for all the
system users in the way that by showing how the system works and in what way they can
manage their system effectively for ensuring the system deployed successfully.

6.6 Installation Process

To use the system, you must deploy some installation process since it is an android application.
Since the system is android based, you need to install it on Android based phone or device.

To install this application, we use the following steps:

Precondition:

. APK file be published

Option 1: Importing. APK file in your android device or memory card.

1. Find and get. APK file from your android device

2. Click on. APK file

3. The application will start its installation automatically.

4. Open it and use.

6.7 Start-up strategy

The organization user group might have a different training strategy but our group listed some of
start-up strategy.

End-user training:

End-user training will be provided using a separate modules and departments. It focuses on each
user of the system and provides a step-by-step walk through of the business process. Custom
text, tips and explanations can be included in the recorded process.

Trainer:

Department Of Computer Science Page 73

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

 Project managers will determine who will conduct the training

 The stakeholder will determine who will be trained for a specific module.

Evaluate training:

 After system testing solicit feedback to determine next steps.

 Respond to areas that need more attention
 Make required changes per user feedback.
 Announce what changes or edits were made

User acceptance testing:

 We will create user acceptance testing prior to delivery.

 Edit and modify system documentation when needed.

6.8 Coding
In this phase we illustrate the code that build the system as a sample:

Java class for login interface: -

package com.example. sharik. helpdesksystemfordebreberhanuniversity.Account;

import android. content.Intent;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android. view.View;
import android. util.Log;
import android. widget.Button;
import android. widget.EditText;
import android.widget.Toast;
import com.android.volley.AuthFailureError;
import com.android.vduzu zare new yahi nafekishign
olley.Request;
import com.android.volley.RequestQueue;
import com.android.volley.Response;
import com.android.volley.VolleyError;

Department Of Computer Science Page 74

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

import com.android.volley.toolbox.StringRequest;
import com.android.volley.toolbox.Volley;
import com.example. sharik.
helpdesksystemfordebreberhanuniversity.Main.Get_building;
import com.example.sharik.helpdesksystemfordebreberhanuniversity.R;
import com.example.sharik.helpdesksystemfordebreberhanuniversity.URL.URLClass;
import org.json.JSONException;
import org.json.JSONObject;
import java.util.HashMap;
import java.util.Map;
public class LoginForm extends AppCompatActivity {
EditText Username,Passw;
Button Login,CreateAccount;
String Passholder,EmailHolder;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_login_form);
Username=(EditText)findViewById(R.id.editusername);
Passw=(EditText)findViewById(R.id.editPassword);
CreateAccount=(Button)findViewById(R.id.btnCreateAccount);
Login = (Button) findViewById(R.id.btnLogin);
CreateAccount.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick (View v) {
Intent i=new Intent (LoginForm.this,CreateAccount.class);
startActivity(i);
}});
Login.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick (View v) {

Department Of Computer Science Page 75

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

final String UserN= Username.getText(). toString(). trim ();

final String Pass=Passw.getText().to String (). trim ();
if (Username.length() <0||Passw.length() ==0) {
Username.findFocus();
Passw.findFocus();
Username.setError("Please Eneter the Required Username ");
Passw.setError("Please Enter the Required password “);}
else if (Username.length() <4||Username.length() >20||Passw.length()
<4||Passw.length()>20) {
Toast.makeText(LoginForm.this,"UserName and password must be between
4 and 4.”, Toast.LENGTH_LONG). show ();
/* else if (UserN.matches("^[_a-zA-Z0-9] +")) {
Username.requestFocus();
Passw.setError("Please Enter valid name"); */
}
else {
RequestQueue queue = Volley.newRequestQueue(LoginForm.this);
final StringRequest request = new StringRequest(Request.Method.POST,
URLClass.LOGIN_URL, new Response.Listener<String> () {
@Override
public void onResponse (String response) {
try {
JSONObject jo=new JSONObject(response);
boolean success=jo.getBoolean("success");
if(success) {
Toast.makeText(LoginForm.this, "you are:" + " " + response,
Toast.LENGTH_SHORT). show ();
startActivity(new Intent(LoginForm.this, Get_building.class));
Log.i("My success", "" + response);
}
else {

Department Of Computer Science Page 76

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Toast.makeText(LoginForm.this, "ERROR ON:" + " " + response,

Toast.LENGTH_SHORT). show ();
Log.i("Not success", "" + response);
}
} catch (JSONException e) {
e.printStackTrace();
}}
}, new Response.ErrorListener() {
@Override
public void onErrorResponse (Volley Error error) {
Toast.makeText(LoginForm.this, "my error:" + error,
Toast.LENGTH_LONG). show ();
Log.i("My error", "" + error);
}
}){
@Override
protected Map<String, String> getParams() throws AuthFailureError {
Map<String, String> map = new HashMap<String, String> ();
map.put("username”, UserN);
map.put("password",Pass);
return map;
}
};
queue.add(request);
}}
});
}}

Java class for Register information interface: -

package com.example. sharik. helpdesksystemfordebreberhanuniversity.

Building.RegisterBuliding;

Department Of Computer Science Page 77

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

import android. content.Intent;

import android.support.v7.app.AppCompatActivity;

import android.os. Bundle;

import android. util.Log;

import android. view.View;

import android. widget.Button;

import android. widget.EditText;

import android.widget.Toast;

import com.android.volley.AuthFailureError;

import com.android.volley.Request;

import com.android.volley.RequestQueue;

import com.android.volley.Response;

import com.android.volley.VolleyError;

import com.android.volley.toolbox.StringRequest;

import com.android.volley.toolbox.Volley;

import com.example. sharik. helpdesksystemfordebreberhanuniversity.

Building.ViewClassroom.ViewClassroom;

import com.example.sharik.helpdesksystemfordebreberhanuniversity.R;

import com.example.sharik.helpdesksystemfordebreberhanuniversity.URL.URLClass;

import java.util.HashMap;

import java.util.Map;

public class Class_room extends AppCompatActivity {

EditText id,email,phone,officname,floors;

Button save,view;

// String Url="http://10.18.46.219/Colleges/RegisterClassRoom.php";

Department Of Computer Science Page 78

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

@Override

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.activity_class_room);

id=(EditText)findViewById(R.id.editclassbuildingcode);

floors=(EditText)findViewById(R.id.editclassbuildingname);

email=(EditText)findViewById(R.id.editclassdepartiment);

phone=(EditText)findViewById(R.id.editclassyear);

officname=(EditText)findViewById(R.id.editclasslocation);

save=(Button) findViewById(R.id.classroomsend);

view=(Button) findViewById(R.id.classroomview);

view.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick (View v) {

Intent i=new Intent(Class_room.this,ViewClassroom.class);

startActivity(i);

}});

save.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick (View v) {

final String cid= id.getText().toString();

final String floor=floors.getText().toString();

final String cemail= email.getText().toString();

final String cphone= phone.getText().toString();

final String sname= officname.getText().toString();

Department Of Computer Science Page 79

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

//check if it is correct

if(id.length()<0||email.length()==0||phone.length()==0){

id.setError("Please Eneter The Required Id ");

//bulidingnumber.setError("Please Enetr The Required Name");

email.setError("Please Enter The Required Email Account ");

phone.setError("Please enter the required phone number (0-9)");

else if (! cid.matches("^[_a-zA-Z0-9]+")) {

id.requestFocus();

id.setError("Please Enter valid Office Id");

else {

RequestQueue queue = Volley.newRequestQueue(Class_room.this);

StringRequest request = new StringRequest(Request.Method.POST,

URLClass.RegisterClassroom_url, new Response.Listener<String> () {

@Override

public void onResponse (String response) {

Toast.makeText(Class_room.this, "you are :" + " " + response + "successfully",

Toast.LENGTH_SHORT).show();

Log.i("My success", "" + response);

}, new Response.ErrorListener() {

@Override

public void onErrorResponse (VolleyError error) {

Toast.makeText(Class_room.this, "my error :" + error,

Toast.LENGTH_LONG).show();

Department Of Computer Science Page 80

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Log.i("My error", "" + error);

}) {

@Override

protected Map<String, String> getParams() throws AuthFailureError {

Map<String, String> map = new HashMap<String, String> ();

map. Put ("classBuildingNumber", cid);

map. Put ("classBuildingName”, floor);

map. Put ("classDepartementName", cemail);

map. Put ("classYear", cphone);

map.put ("classLocation", sname);

return map;

} };

queue. Add(request);

}});

Java class for chatting interface: -

package com.example.sharik.helpdesksystemfordebreberhanuniversity.CHAT;

import android.support.v7.app.AppCompatActivity;

import android.os. Bundle;

import java.io.DataInputStream;

import java.io.DataOutputStream;

import java.io.IOException;

import java.net.Socket;

Department Of Computer Science Page 81

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

import java.net.UnknownHostException;

import android. view.View;

import android.view.View.OnClickListener;

import android. widget.Button;

import android. widget.EditText;

import android.widget.LinearLayout;

import android.widget.TextView;

import android.widget.Toast;

import com.example.sharik.helpdesksystemfordebreberhanuniversity.R;

public class Chat extends AppCompatActivity {

static final int SocketServerPORT = 8080;

LinearLayout loginPanel, chatPanel;

EditText editTextUserName, editTextAddress;

Button buttonConnect;

TextView chatMsg, textPort;

EditText editTextSay;

Button buttonSend;

Button buttonDisconnect;

String msgLog = "";

ChatClientThread chatClientThread = null;

@Override

protected void on Create (Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.activity_chat);

loginPanel = (LinearLayout)findViewById(R.id.loginpanel);

Department Of Computer Science Page 82

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

chatPanel = (LinearLayout)findViewById(R.id.chatpanel);

editTextUserName = (EditText) findViewById(R.id.username);

editTextAddress = (EditText) findViewById(R.id.address);

textPort = (TextView) findViewById(R.id.port);

textPort.setText("port: " + SocketServerPORT);

buttonConnect = (Button) findViewById(R.id.connect);

buttonDisconnect = (Button) findViewById(R.id.disconnect);

chatMsg = (TextView) findViewById(R.id.chatmsg);

buttonConnect.setOnClickListener(buttonConnectOnClickListener);

buttonDisconnect.setOnClickListener(buttonDisconnectOnClickListener);

editTextSay = (EditText)findViewById(R.id.say);

buttonSend = (Button)findViewById(R.id.send);

buttonSend.setOnClickListener(buttonSendOnClickListener);

OnClickListener buttonDisconnectOnClickListener = new OnClickListener() {

@Override

public void onClick (View v) {

if(chatClientThread==null) {

return;

chatClientThread.disconnect();

} };

OnClickListener buttonSendOnClickListener = new OnClickListener() {

@Override

public void on Click (View v) {

Department Of Computer Science Page 83

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

if (editTextSay.getText(). toString (). equals ("")) {

return;

if(chatClientThread==null) {

return;

chatClientThread.sendMsg(editTextSay.getText(). toString () + "\n");

} };

OnClickListener buttonConnectOnClickListener = new OnClickListener() {

@Override

public void onClick (View v) {

String textUserName = editTextUserName.getText(). toString ();

if (textUserName.equals("")) {

Toast.makeText(Chat.this, "Enter User Name",

Toast.LENGTH_LONG). show ();

return;

String textAddress = editTextAddress.getText(). toString ();

if (textAddress.equals("")) {

Toast.makeText(Chat.this, "Enter Addresse",

Toast.LENGTH_LONG). show ();

return;

msgLog = "";

chatMsg.setText(msgLog);

Department Of Computer Science Page 84

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

loginPanel.setVisibility(View.GONE);

chatPanel.setVisibility(View.VISIBLE);

chatClientThread = new ChatClientThread (

textUserName, textAddress, SocketServerPORT);

chatClientThread.start();

} };

private class ChatClientThread extends Thread {

String name;

String dstAddress;

int dstPort;

String msgToSend = "";

boolean goOut = false;

ChatClientThread (String name, String address, int port) {

this.name = name;

dstAddress = address;

dstPort = port;

@Override

public void run () {

Socket socket = null;

DataOutputStream dataOutputStream = null;

DataInputStream dataInputStream = null;

try {

socket = new Socket (dstAddress, dstPort);

dataOutputStream = new DataOutputStream(

Department Of Computer Science Page 85

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

socket.getOutputStream());

dataInputStream = new DataInputStream(socket.getInputStream());

dataOutputStream.writeUTF(name);

dataOutputStream.flush();

while (! goOut) {

if (dataInputStream.available() > 0) {

msgLog += dataInputStream.readUTF();

Chat.this.runOnUiThread(new Runnable() {

@Override

public void run () {

chatMsg.setText(msgLog);

} });

if (! msgToSend.equals("")) {

dataOutputStream.writeUTF(msgToSend);

dataOutputStream.flush();

msgToSend = "";

}}

} catch (UnknownHostException e) {

e.printStackTrace();

final String eString = e.toString();

Chat.this.runOnUiThread(new Runnable() {

@Override

public void run () {

Toast.makeText(Chat.this, eString, Toast.LENGTH_LONG). show ();

Department Of Computer Science Page 86

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

}});

} catch (IOException e) {

e.printStackTrace();

final String eString = e.toString();

Chat.this.runOnUiThread(new Runnable() {

@Override

public void run () {

Toast.makeText(Chat.this, eString, Toast.LENGTH_LONG). show ();

}});

} finally {

if (socket! = null) {

try {

socket.close();

} catch (IOException e) {

// TODO Auto-generated catch block

e.printStackTrace();

if (dataOutputStream! = null) {

try {

dataOutputStream.close();

} catch (IOException e) {

// TODO Auto-generated catch block

e.printStackTrace();

}}

Department Of Computer Science Page 87

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

if (dataInputStream! = null) {

try {

dataInputStream.close();

} catch (IOException e) {

// TODO Auto-generated catch block

e.printStackTrace();

}}

Chat.this.runOnUiThread(new Runnable() {

@Override

public void run () {

loginPanel.setVisibility(View.VISIBLE);

chatPanel.setVisibility(View.GONE);

} });

}}

private void sendMsg (String msg) {

msgToSend = msg;

private void disconnects () {

goOut = true;

}}

Department Of Computer Science Page 88

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

CHAPTER SEVEN

CONCLUSIONS AND RECOMMENDATION

7.1 Conclusions
Implementing the analyzed and designed android based Help desk system that might be the best
solution to the current getting the place problem in most of user. Therefore, in the first and the
second chapter of this project document we were trying to assess the existing system and studying
each and every activity of the existing system by conducting different data gathering methodology.
Then after examination of the limitation of existing system we choose this android based system,
as it will be able to address problems encountered by users. And in order to accomplish the
objective of the proposed system implementation tool XAMP database and android java language,
asp.net web application and design model such as (use case modeling, sequence diagram is
specified and most of the designing tool were used in chapter two and three. Main Activity and
other Activity functionality are illustrated. The activity diagram shows different type of user
interacts with the system. Furthermore, the use cases showed what the user will do with the system.
And finally each class and attribute was explained in detail. Furthermore, the class diagram
demonstrates the relationship between classes in the system. From a proper analysis of positive
points and constraints on the existing system we conclude that the proposed system that we
designed to implement will be efficient and effective one to solve current problem, if we implement
it in carefully planned manner.

7.2 Recommendations
Based on the preceding information in our project, we believe that the following
recommendation will help the organization to improve their system more reliable and
available, as they want. The proposed system will be best reference for the next version of
this application to add or modify some remaining functionalities.
 In the current context Google Map does not recognize the DBU map as a road we
recommend that the compound map is made and upload to google map by authorized body
after this there may be clear and simple to use this application.

Department Of Computer Science Page 89

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

References
[1] Dennis, A. (2012). Systems Analysis and Design. John Wiley and Sons.

John W.Satzingar, R. B. (n.d.). System Analysis and Design in a changing world.

John W.Satzingar, R. B. (n.d.). System Analysis and Design in a changing world.

John W.Satzinger, R. B. (2008). System Analysis and Design in a changing world.

Sandep Kumar, M. A. (2008). Location based service using android.

Sandep Kumar, M. A. (2009). Location based service using android.

Department Of Computer Science Page 90

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

APPENDIX
Table 19: Appendix

Symbol Description
uc Us e Ca ...

Actor

uc Use Case Diagram

System boundary

Use case diagram

uc Use Case Diagram

Class Diagram

deployment Deploy...
Deployment Diagram

Message line

Include, related to include use case to

indicate inserted behavior
Decision

Activity

Boundary

Controller

Entity

Department Of Computer Science Page 91

 MOBILE BASED ONLINE HELP DESK FOR DEBREBIRHAN UNIVERSITY 2018

Department Of Computer Science Page 92