HORSEED INTERNATIONAL UNIVERSITY

DESIGN AND IMPLEMENTATION OF:

HORSEED INTERNATIONAL UNIVERSITY

DESIGN AND IMPLEMENTATION OF:

Online Digital Library

IN MOGADISHU –SOMALIA

____________________________________

A project

PRESENTED TO HORSEED INTERNATIONAL UNIVERSITY

The Faculty of Computer Science and INFORMATION TECHNOLOGY

Mogadishu, Somalia

_____________________________________

In Graduation Project Fulfillment of the Requirements for the Degree of

Bachelor of Science in Information Technology

____________________________________

I
 DECLARATION A

We declare this thesis is our original work and has not been presented for a degree or any
other academic award in any university or Institution of learning

Signature 1: _____________________________________ Date: ___/ ____

Signature 2: _____________________________________ Date: ___/ ____

Signature 3: _____________________________________ Date: ___/ ____

DECLARATION B

“I confirm that the work reported in this thesis/proposal was carried out by the candidate(s)
under my direct supervision”.

Name of Supervisor:

Abdirashid: ______

Signature: ____________________________________

Date: / /2023

II
 APPROVAL SHEET

This Project Committee of the Department of Information Technology, the Faculty of

Computer

Science and information Technology Horsed International University has approved this Final
Project, prepared and submitted by Mohamud, Mohamed, Liban, in partial fulfillment of
the requirements for the degree of Bachelor Science and Information Technology has been
examined and approved by the panel on oral examination with a grade of PASSED.

____________________ ____________________

Name and Sig. of Chairman Name and Sig. of Panelist

____________________ ____________________

Name and Sig of Supervisor Name and Sig. of Panelist

____________________ ____________________

Name and Sig. of Panelist Date of Comprehensive Examination: ____________________

Grade: ____________________

:____________________

Name and Sig. of Dean

III
 DEDICATION

This project is dedicated to: Our relatives for their love, unfailing support and understanding.
Our parents for their constant encouragement even thorough their own adversity. Our best
friends who continue to guide us towards our life goals.

IV
 ACKNOWLEDGMENT

We thank to Allah the Creator of this world, who gave us the opportunity to complete this
project successfully. You won't find a successful person made his way to the top, without a
support. Each one of us is debt to known or unknown people. Those who gave us hands when
darkness was everywhere around. Show us the way, surrounded us, and smiled to us… gave us
hope. We would like to thank our family and parents for supporting us emotionally and
financially.

We would like to thank the administration of Horsed International University, especially Dean
of Faculty of Computer Science and Technology, Eng./ Ibrahim Farah Hilowle Mire for his
guidance, training, supervision and encouragement during our study at the university especially
Information Technology (IT).

We would like to extend our warmest gratitude to our supervisor, Eng. Abdirashid Dahir
Ahmed (Cowke) for his immense amount of support, advice, and guidance throughout the
process. We couldn’t have done any of this without their support.

V
 ABSTRACT

In the name of Allah, the creator and peace is upon Mohamed the prophet of Allah.

As Students who are assigned to develop their final project with the title “Online visa
Management System”. We are here to develop system that is our final project and four
Students will involve in the process of development of this system. The project will facilitate
the inline faculty Management System of Universities by using simple procedures. We are
preparing this project to reduce the complexity of the current system from manual to
computerized one.

VI
 TABLE CONTENTS

DECLARATION A..................................................................................................I
DECLARATION B...................................................................................................II

APPROVAL SHEET .............................................................................................. III

DEDICATION........................................................................................................... IV

ACKNOWLEDGMENT ............................................................................................V

ABSTRACT .............................................................................................................. VI

TABLE CONTENTS...............................................................................................VII

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

INTRODUCTION ...................................................................................................... 1

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

1.1 Background of the system....................................................................................1

1.3 Purpose of the project...........................................................................................3

1.4 Project objectives...................................................................................................4

1.5 Project Scope..........................................................................................................4

1.6 Significance of the project.....................................................................................4

1.7 Report organization................................................................................................5

CHAPTER TWO ....................................................................................................... 6

LITERATURE REVIEW.......................................................................................... 6

2.0 Introduction ...........................................................................................................6

2.1 Theoretical and Conceptual Development ..............................................................8

2.1.1 Online....................................................................................................................8

2.1.2 Faculty...................................................................................................................8
2.1.3Management.............................................................................................................9

2.1.4 System..................................................................................................................10

VII
2.1.5PHP ...................................................................................................................10
2.1.6MYSQL..............................................................................................................11

Case study of the research .........................................................................................13

Compare Between exiting system.............................................................................14

2.3.1. Harvard ............................................................................................................14

2.3.2 OXFORD..........................................................................................................15

Chapter Summary ......................................................................................................16

CHAPTER III ........................................................................................................... 16

SOFTWARE PLANNING AND ANALYZING ..................................................... 17

3.0 Introduction .........................................................................................................17

3.1 Operational Framework.......................................................................................18

3.2 Work Break down structure (WBS) ....................................................................20

3.3 System Requirement............................................................................................21

3.3.1 Software Requirement Specification ...............................................................22

3.3.2 User Requirements Definition .........................................................................23

3.4 Problem Analysis Identification..........................................................................23

3.5 Requirements Gathering Techniques...................................................................24

3.5.1 Interview ..........................................................................................................25

3.5.2 Observation ......................................................................................................26

3.6 Process Modeling ................................................................................................27

3.6.1 Data flow Diagram (DFD)................................................................................27

3.6.2 Unified Modeling Language (UML) ................................................................29

3.7 Data Modeling......................................................................................................31

3.7.1 ERD Diagram.....................................................................................................31

3.9 System Feasibility ................................................................................................34

VIII
3.9.1 Technical Feasibility ....................................................................................35

Table 3. 4 Technical Feasibility ............................................................................35

Table 3. 5 Items......................................................................................................36

3.9.2 Operational Feasibility .................................................................................36

Table 3. 6 Operational Feasibility.........................................................................36

3.9.3 Economic Feasibility.....................................................................................36

Table 3. 7 Economic Feasibility ............................................................................37

3.9.4 Schedule Feasibility......................................................................................37

Table 3. 8 Schedule Feasibility .............................................................................37

3.10 Chapter Summary...........................................................................................38

CHAPTER FOUR..................................................................................................39

SOFTWARE DESIGN...........................................................................................39

4.0 INTRODUCTION............................................................................................39

4.1 ARCHITRCTURAL DESIGN.........................................................................39

4.2 USER INTERFACE DESIGN..........................................................................40

4.3 DATABASE STORAGE DESIGN..................................................................40

4.4.1 DATABASE NORMALIZATION.................................................................41

4.4.3 DATA DICTIONARY...................................................................................44

4.5 DESIGNING FORMS AND REPORTS............................................................47

4.6 CHAPTER SUMMARY......................................................................................50

CHAPTER FIVE....................................................................................................... 51

SYSTEM IMPLEMENTATION...............................................................................51

5.0 INTRODUCTION................................................................................................51

5.1 CODING PHASE.................................................................................................51

IX
5.2 TEST SYSTEM IMPLEMENTATION.....................................................................51

5.2.1 DEVELOPMENT TESTING..................................................................................51

5.2.2 RELEASE TESTING..............................................................................................52

5.2.3 USER TESTING.....................................................................................................53

5.3 DEVELOPING USER MANUALS..........................................................................54

CHAPTER SIX................................................................................................................58

CONCLUSION & ENHANCEMENT............................................................................58

6.0 INTRODUCTION.....................................................................................................58

6.1 WEAKNESSES AND PROBLEMS OF THE SYSTEM..........................................59

6.2 FUTURE WORK &RECOMMENDATIONS...........................................................59

6.3 CHAPTER SUMMARY ............................................................................................60

REFERENCES ................................................................................................................61

PENDICES ................................................................................................................... .62

X
 LIST OF TABLES

Table 2. 1 Compare Exiting System...................................................................... 16

Table 3. 1 Software Requirements......................................................................... 22

Table 3. 2 Hardware Requirements........................................................................ 23

Table 3. 3 ERD Proposed System.......................................................................... 33

Table 4.1 First Normal Form................................................................................. 42

Table 4.2 Second Normal form.............................................................................. 43

Table 4.3 Third Normal Form................................................................................ 44

Table 4.5: User Registration .................................................................................. 44

Table 4.6:Year Level Registration ......................................................................... 45

Table 4.7:Student Registration............................................................................... 45

Table 4.8: Teachers Registration ........................................................................... 45

Table 4.9: Faculty ................................................................................................. 46

Table 4.10: Subject................................................................................................ 46

Table 4.11: Schedule ............................................................................................. 46

Table 4.12: Class............................................................................................................... 46

LIST OF FIGURES

Figure 2.1 literature review ..................................................................................... 7

Figure 2. 1 Harvard ............................................................................................... 15

Figure 2. 2 Horseed............................................................................................... 16

Figure 3. 1 Operation Frame Work........................................................................ 19

Figure 3. 2 WBS Product....................................................................................... 20

Figure 3. 3 Work Break down Structure (WBS) Process........................................ 21

XI
Figure 3. 4 UCD.................................................................................................... 28

Figure 3. 5 UCD.................................................................................................... 30

Figure 3. 6 Use Case Diagram............................................................................... 30

Figure 3. 7 ERD .................................................................................................... 32

Figure 3.3 ERD proposed system .......................................................................... 34

Figure 4.1 architecture design................................................................................ 39

Figure 4.2 User Interface ....................................................................................... 40

Figure 4.3 ERD Transforming ............................................................................... 44

Figure 4.4 Create User Activity............................................................................. 48

Figure 4.5 Login Activity...................................................................................... 48

Figure 4.6 year level Activity ................................................................................ 49

Figure 4.7 Student ................................................................................................. 49

Figure 4.8 class ..................................................................................................... 50

Figure 5.1 shows the login validation .................................................................... 52

Figure 5.2 Main form ............................................................................................ 53

Figure 5.3 Login form........................................................................................... 55

Figure 5.4 User form............................................................................................. 55

Figure 5.5 year level.............................................................................................. 56

Figure 5.6 Student ................................................................................................. 56

Figure 5.7 Schecude .............................................................................................. 57

Figure 5.8 class ..................................................................................................... 57

XII
XIII
CHAPTER ONE

INTRODUCTION

1.0 Introduction

A faculty is a division within a university or college comprising one subject area or a group of
related subject areas, possibly also delimited by level (e.g. undergraduate). In American usage
such divisions are generally referred to as colleges (e.g., "college of arts and sciences") or
schools (e.g., "school of business"), but may also mix terminology (e.g., Harvard University
has a "faculty of arts and sciences" but a "law school").

A faculty position is one in which an individual is hired by a school to help educate students.
At the university or college level, you may be brought on to conduct research as well. Although
research and teaching are main facets of faculty life, your other responsibilities may include
updating course materials, holding office hours to assist students, developing class websites,
advising students, writing letters of recommendation, and more. Faculty members also include
other education professionals like guidance counselors and librarians.

The field of analysis, called intonation, is a much confused and slippery term in foreign
language education and teacher training. According to some experts, the learning problems of
fossilized pronunciation and intonation errors are undoable ( Fromkin et al, 2003) because the
elements of intonation, namely the stress, pitch, and juncture, collectively, exert impacts in
forms of negative transfers from L1, and make a league against L2 intonation learning
strategies of the non-native learners. Therefore, they cannot be erased. This claim is not true.
Even though the typological difficulties of L1 along with the cognitive learning styles,
strategies, age, degree of awareness, motivation, self-monitoring skills of non-native teacher’s
pact against the L2 teachers, there are some helpful.

1.1 Background of the system

The medieval University of Bologna, which served as a model for most of the later medieval
universities in Europe, had four faculties: students began at the Faculty of Arts, graduates from
which could then continue at the higher Faculties of Theology, Law, and Medicine. The
privilege to establish these four faculties was usually part of medieval universities’ charters,
but not every university could do so in practice.

1
The Faculty of Arts took its name from the seven liberal arts: the trivium (grammar, rhetoric,
dialectics) the quadrivium (arithmetic, music, geometry, and astronomy). In German,
Scandinavian, Slavic and related universities, it would more often be called the Faculty of
Philosophy. The degree of Magister Artium (Master of Arts) derives its name from the Faculty
of Arts, while the degree of Doctor Philosophize (Doctor of Philosophy) derives its name from
the Faculty of Philosophy, The German name of the same faculty. Whether called Faculty of
Arts or Faculty of Philosophy, it taught a range of subjects with general and fundamental
applicability.

The higher Faculty of Law and Faculty of Medicine was intended, much like today, for
specialized education required for professions. The Faculty of Theology was the most
prestigious, as well as least common in the first 500 years—and generally one that popes sought
most to control. Although also "professional" education for clergy, theology (until the
Enlightenment) was also seen as the ultimate subject at universities, named "The Queen of the
Sciences, and often set the example for the other faculties.

The number of faculties has usually multiplied in modern universities, both through
subdivisions of the traditional four faculties and through the absorption of academic disciplines
that developed within originally vocational schools, in areas such as engineering or agriculture.
Previous studies of community colleges have shown that instructors play a vital role in the
plans and actions of students who transfer to 4-year colleges and universities (Britt &Hirt,
1999; Cejda&Kaylor, 2001; Cuseo, 1998; Gaskin, 1999; Tatum, 2001). The purpose of the
current study was to obtain information from the faculty on the extent of their involvement in,
and knowledge of, the transfer process at a large, urban community college. The study was
conducted in 2 phases. The first phase involved sending a questionnaire to all instructors at the
college. The questionnaire obtained data on the background, knowledge, and support activities
of the faculty related to student transfers. The second phase involved focus groups composed
of selected faculty and staff. The questionnaire was used to create a path model that showed
the relationships between faculty background, involvement with the or a transfer, and
knowledge of the transfer. This information, combined with the focus group results, was used
to develop strategies for employing the faculty in efforts to improve the transfer culture and
increase the transfer rate.

2
1.2 problem statement

The providers working under the manual of paper. The Online Faculty Management System
uses papers; all records related to visits; payment is stored. There is a lot of duplicate data. The
process of entry took a lot of effort and by computing and storing of data manually the process
is prone to error and just by a single mistake repeating the process required.

Developing Online Faculty Management System would make the task of recording and
computing easier for the administrator will also benefit the work because of the improvement
in the accuracy of the calculation in provenience and productivity so many problems the Online
Faculty Management System faces now will be solved in this project.

1.3 Purpose of the project

The purpose of this Online Faculty Management Systems for society is that the persons are to
use a system to the storage of data Students and keep all records related to the actions and
Performance by teaching to use a book this system allows you to insert, modify and delete of
data, this system allows you to see previously saved records, there is no duplicate data, this
system can perform all of the information report or individual data report.

1.4 Project objectives

Here are the most three objectives to develop Online Faculty Management System:

Somalia doesn’t have online System for Online Faculty Management System.

1. To study the existing Online Faculty Management System.

2. To analyze Online Faculty Management System.

3. To design, implement and test Online Faculty Management System.

1.5 Project Scope

Online Faculty Management System Thus, the researcher thinking to analyze Online Faculty
Management Systemin Mogadishu – Somalia. This system is developed for the client to
manage their customers Monitoring System functions that will be delivered through this system
are shown below: Register, Login Online Faculty Management System, Employee, Reports,
and Logout The proposed system will be developed using PHP and MYSQL, it will be
implemented between 24th March to 25th June 2020.

3
1.6 Significance of the project

This system is significant for all the ONLINE FACULTY MANAGEMENT SYSTEM those
are now work traditionally, when this system is used, all the facilities done through by any time
from any place. This system a more has many functions that allows you to access and to easily
get more reports so you can manage every part or every branch on the cloud available.

4
CHAPTER TWO LITERATURE REVIEW

2.0 Introduction
A literature review is a critical and in-depth evaluation of previous research. It is a summary
and synopsis of a particular area of research, allowing anybody reading the paper to establish
why you are pursuing this particular research. A good literature review expands on the reasons
behind selecting a particular research question.
A literature review is a survey and discussion of the literature in a given area of study. It is a
concise overview of what has been studied, argued, and established about a topic, and it is
usually organized chronologically or thematically. A literature review is written in essay
format. It is not an annotated bibliography, because it groups related works together and
discusses trends and developments rather than focusing on one item at a time. It is not a
summary; rather, it evaluates previous and current research regarding to how relevant and/or
useful it is and how it relates to your research.
This chapter consists of a discussion of the Literature review related to the online Faculty
Management System Includes Theoretical and Conceptual Development, Case study of the
research, Compare Between exiting system, and Chapter Summary.

5
 Online

Facult

Introduction

Management
Theoretical and
Conceptual
Development
System
Case Study of the
Literature Review Research
JSP
Compare between
existing system
MYSQL

Chapter Summary

Figure 2.1 literature review

2.1 Theoretical and Conceptual Development

The following section, the research briefly illustrates the concept and ideas related to the
Online Faculty Management System used today around the world
Con
e2.1 Theoretical and Conceptual Development
The following section, the research briefly illustrates the concept and ideas related to the Online
Faculty Management System used today around the world

6
2.1.1 Online

Online learning involves courses offered by postsecondary institutions that are 100% virtual,
excluding massively open online courses (MOOCs). Online learning, or virtual classes offered
over the internet, is contrasted with traditional courses taken in a brick-and-mortar school
building. It is the newest development in distance education that began in the mid-1990s with
the spread of the internet and the World Wide Web. Learner experience is typically
asynchronous, but may also incorporate synchronous elements. The vast majority of
institutions utilize a Learning Management System for the administration of online courses. As
theories of distance education evolve, digital technologies to support learning and pedagogy
continue to transform as well.

2.1.2 Faculty

Academic personnel, also known a faculty member or member of the faculty (in North
American usage) or academics or academic staff (in British, Australian, and New Zealand
usage), are vague terms that describe teaching or research staff of a university, college, school,
or research institute. In British and Australian/NZ English "faculty" usually refers to a sub-
division of a university (usually a group of departments), not to the employees, as it can also
do in North America. Law Enforcement instructors at community colleges are important parts
of the certificated faculty. Universities, community colleges and even some secondary and
primary schools use the terms faculty and professor. Other institutions (e.g., teaching hospitals
or not-for-profit research institutes) may likewise

2.1.3Management

Management is essential for an organized life and necessary to run all types of management.
Good management is the backbone of successful organizations. Managing life means getting
things done to achieve life’s objectives and managing an organization means getting things
done with and through other people to achieve its objectives. 10
Whether management is an art or science’ will continue to be a subject of debate. However,
most management thinkers agree that some form of formal academic management background
helps in managing successfully. Practically, all CEO,s are university graduates. Hence, the
reason for including business degree programs in all academic institutions.

7
2.1.4 System

The “System” concept is a collection of elements or components that are organized for a
common purpose. The word sometimes describes the organization or plan itself (and is similar
in meaning to the method as in "I have my own little system") and sometimes describes the
parts in the system (as in "computer system"). A system is a set of things working together as
parts of a mechanism or an interconnecting network; a complex whole a system is a group of
related hardware units or programs or both, especially when dedicated to a single application a
system is a set of organs in the body with a common structure or function. The system is a set
of principles or procedures according to which something is done; an organized scheme or
method. A set of detailed methods, procedures, and routines created to carry out a specific
activity, perform a duty, or solve a problem.

2.1.5PHP

PHP stands for Hypertext Preprocessor (no, the acronym doesn't follow the name). It's an open-
source, server-side, scripting language used for the development of web applications. By
scripting language, we mean a script-based program, (lines of code) written for the automation
of tasks, what does open-source mean? Think of 11 a car manufacturer making the secret to its
design models and technology innovations available to anyone interested. These design and
technology details can be redistributed, modified, and adopted without the fear of any legal
repercussions. The world today might have developed an amazing super Web pages can be
designed using HTML. With HTML, code execution is done on the user's browser (client-side).
On the other hand, with PHP server-side scripting language, it's executed on the server before
it gets to the web browser of the user. PHP can be embedded in HTML, and it's well suited for
web development and the creation of dynamic web pages for web applications, e-commerce
applications, and database applications. It's considered a friendly language with abilities to
easily connect with MySQL, Oracle, and other databases.

2.1.6 MYSQL

MySQL is a database management system. A database is a structured collection of data. It

may be anything from a simple shopping list to a picture gallery or the vast amounts of
information in a corporate network. To add, access, and process data stored in a computer
database, you need a database management system such as MySQL Server. Since computers
are very good at handling large amounts of data, database management systems play a central
role in computing, as standalone utilities, or as parts of other applications.

8
MySQL databases are relational. A relational database stores data in separate tables rather
than putting all the data in one big storeroom. The database structures are organized into
physical files optimized for speed. The logical model, with objects such as databases, tables,
views, rows, and columns, offers a flexible programming environment. You set up rules
governing the relationships between different data 12 fields, such as one-to-one, one-to-many,
unique, required or optional, and “pointers” between different tables. The database enforces
these rules, so that with a well-designed database, your application never sees inconsistent,
duplicate, orphan, out-of-date, or missing data. The SQL part of “MySQL” stands for
“Structured Query Language”. SQL is the most common standardized language used to
access databases. Depending on your programming environment, you might enter SQL directly
(for example, to generate reports), embed SQL statements into code written in another
language, or use a language-specific API that hides the SQL syntax .SQL is defined by the
ANSI/ISO SQL Standard. The SQL standard has been evolving since 1986 and several versions
exist. In this manual, “SQL-92” refers to the standard released in 1992, “SQL:1999” refers to
the standard released in 1999, and “SQL:2003” refers to the current version of the standard.
We use the phrase “the SQL standard” to mean the current version of the SQL Standard at any
time.

MySQL software is Open Source. Open Source means that anyone can use and modify the
software. Anybody can download the MySQL software from the Internet and use it without
paying anything. If you wish, you may study the source code and change it to suit your needs.
The MySQL software uses the GPL (GNU General Public License),
http://www.fsf.org/licenses/, to define what you may and may not do with the software in
different situations. If you feel uncomfortable with the GPL or need to embed MySQL code
into a commercial application, you can buy a commercially licensed version from us. See the
MySQL Licensing Overview for more information
(http://www.mysql.com/company/legal/licensing/).

13 The MySQL Database Server is very fast, reliable, scalable, and easy to use. If that is
what you are looking for, you should give it a try. MySQL Server can run comfortably on a
desktop or laptop, alongside your other applications, web servers, and so on, requiring little or
no attention. If you dedicate an entire machine to MySQL, you can adjust the settings to take
advantage of all the memory, CPU power, and I/O capacity available. MySQL can also scale
up to clusters of machines, networked together. MySQL Server was originally developed to
handle large databases much faster than existing solutions and has been successfully used in

9
highly demanding production environments for several years. Although under constant
development, MySQL Server today offers a rich and useful set of functions. Its connectivity,
speed, and security make MySQL Server highly suited for accessing databases on the Internet.

Case study of the research

HORSEED International University (HIU) is one of the leading universities in Somalia. It was
founded in 2010 by some of the Somali Scholars. HIU is an institution of higher education and
It provides high-quality practical instruction at the under graduate and Postgraduate partnership
with Foreigner Universities.

HIU is a Non-Profit, Private University recognized by the Somali Minister of education,

Culture and Higher Education. We strive for continuous improvement and our students will
benefit from stimulating exciting environment. Our syllabus was carefully designed to produce
exceptional graduates with specialized knowledge and providing practical training to generate
critical-thinking graduates

HIU has a reputation for providing practical learning experiences with high-quality
curriculums.

We seek to offer affordable quality education with high experienced lecturers.

MISSION –

To achieve excellence in teaching and research, to maintain and spawn knowledge, HIU
provides high quality programs through innovative teaching methodologies That Engage
students in self-directed learning and management performance.

VISION –

To be a role model of excellence and affordable education in Africa

Compare Between exiting system

The Purpose of this Online Faculty Management System is that the client is to use a system to
store data customers and keep all records related to the actions and order payments by
transferring to use a book this system allows you to insert, modify and delete data.

10
2.3.1. Harvard

The following links provide resources for all Harvard University faculty. Additional faculty
resources may be found at Faculty Development and Diversity. See also Open Faculty
Positions

• Academic Calendars

• Admissions & Financial Aid

• Commencement

• DASH

• Directions and Parking

• Employment

• Harvard Faculty Club

• Harvard Link

• Harvard Mobile Apps

• Harvard University Health Services

• Harvard University Information Technology

• Harvard University Police Department

• Human Resources/HARVie

Figure 2. 1 Harvard

2.3.2 OXFORD

Our short online courses take place in a virtual learning environment. Most courses are 10
weeks in duration and they all run asynchronously – they have no live-time meetings - so you
do not have to be online at any specific time to take the course. You can access the course
whenever it is convenient for you, from anywhere in the world

11
Class sizes are kept small to maximise interaction between you and your classmates and tutor
in the online forums. Students are able to take part in in-depth discussions and receive
personalised tutor guidance and feedback.

Figure 2. 1 Horseed

Table 2. 1 Compare HARVARD OXFORD Proposed System

Exiting System
Features
Register Yes No Yes
Faculty Yes Yes Yes
Reports No No Yes
Distance Learning Yes No Yes
Employee Yes Yes Yes
Validation No Yes Yes

12
 CHAPTER III

SOFTWARE PLANNING AND ANALYZING

3.0 Introduction

Software: in its most general sense, is a set of instructions or programs instructing a computer
to do specific tasks, Software is a generic term used to describe computer programs. Scripts,
applications, programs and a set of instructions are the terms often used to describe software.

The word software was first used by John Tukey in 1958. The theory of software was first
proposed by Alan Turing in 1935.

Software is often divided into three categories:

1. System software serves as a base for application software. System software includes
device drivers, operating systems (OSs), compilers, disk formatters, text editors and utilities
helping the computer to operate more efficiently

2. Programming software is a set of tools to aid the developers to write grograms. The
various tools available are compilers, linkers, debuggers, interpreters and text editors.

3. Application software is intended to perform certain tasks. Examples of application

software include office suites, gaming applications, database systems and educational software.
(definition/4356/software, n.d.)

Planning: A basic management functions involving the formulation of one or more detailed
plans to achieve the optimum balance of needs or demands with the available resources.
(definition/planning.html, n.d.)

Software Analyses is Software analysis patterns or analysis patterns in software engineering

are conceptual models, which capture an abstraction of a situation that can often be encountered
in modeling. (Software_analysis_pattern, n.d.)

This chapter will include the following sections: Introduction, Operational Framework, Work
Break down structure (WBS), System Requirement, Problem Analysis Identification,
Requirements Gathering Techniques, Process Modeling, Data Modeling, Suitable solution
Strategies of the proposed system, System Feasibility and Chapter Summary.

13
3.1 Operational Framework the Operational Framework starts planning, proposal, chapter one
introduction, chapter two literature review, chapter three software planning & analyzing
chapter four software design, chapter five system implementation and finally chapter six
conclusions & enhancement.

3.2 Work Break down structure (WBS)

Work break down structure (WBS) is a vehicle for breaking an engineering project down into
subproject, tasks, subtasks, work packages, and so on. It is an important planning tool which
links objectives with resources and activities in a logical framework. It becomes an important

14
status monitor during the actual implementation as the completions of subtasks are measured
against the project plan. (Tausworthe, 1984) WBS is categorized into:

A) WBS product

B) WBS process

Figure 3. 3 Work Break down Structure (WBS) Process

15
3.3 System Requirement

System requirement is a characteristic or feature that must be included in any information

system to satisfy users. Since the Administrator and the users are the main target collection of
our software, I will only concern about some important functions for the admin and the user.
The system needs Applications like web browsers safari, Mozilla Firefox, Google Chrome, and
internet connection. They include the following interfaces:

a) User Interfaces: The keyboard, mouse, menus of a computer system. The user interface
allows the user to communicate with the operating system.

b) Software Interfaces: The languages and codes that the applications use to communicate
with each other and with the hardware.

c) Hardware Interfaces: The wires, plugs and sockets that hardware devices use to
communicate with each other, computer systems, or any other medium of communication. A
physical interface is an interconnection between two items of hardware or machinery.

3.3.1 Software Requirement Specification

One of the critical success factors in the development of high-quality software product or
website isthe deep understanding of the user’sreal requirement as opposed to their perceived
requirements. This will make the product very easy to develop, maintain, and to use software
properly by the end-users. User requirement is the process by which user desires, needs, and
expectations are gathered to establish what the users will use the software for, and recorded in
a way that will be meaningful both to the users and developments.

3.3.1.1 Software Requirements

Table 3. 1 Software Requirements

3.3.1.2 Hardware Requirement

16
Table 3. 2 Hardware Requirements

3.3.2 User Requirements Definition

A document that defines what a proposed system must be capable of doing to solve the
problems of a defined set of potential users of such a system. The user requirements
specification should be completely independent of any solution-oriented bias and must use
terminology from the problem domain of the users. It must be understandable by the intended
users who must “buy in” to it. Therefore, it is most unlikely to be created using a conventional
requirements-analysis method, since these introduce solution bias, representations, and
concepts that are rarely understood by (and are irrelevant to) the users (userrequirements,
2017).

A customer cannot demand features not in the user requirement document (URD),
while the software developer cannot FACULTY MANAGEMENT SYSTEM the product is
complete and ready if it does not meet even one item of the user requirement document (URD).

3.4 Problem Analysis Identification

The current method in which the after observing the FACULTY MANAGEMENT SYSTEM
process in detail, I have noticed the system had the following problems such as facilitates more
functions that helps everyone in our customers’ Somalia does not have an Application Tracking
FACULTY MANAGEMENT SYSTEM.

I made a web FACULTY MANAGEMENT SYSTEM that uses by everyone And also we
create some features to help users with this App.

17
Admin Problem

 No direct role for the management.

 Lack of efficient and useful reports.

Procedural Problem

 Manual tracking of due Projects.

 No multiple accesses at the same time.

Technical Problem

 Lack of centralized storage and backup.

 Time-consuming.

 Lack of security of data

3.5 Requirements Gathering Techniques

Requirements gathering techniques are a process of collecting data from different sources. Data
or (datum is singular) is valuable pieces of information collected during the research. Data can
be divided into two categories: primary data and secondary data. In this research, the primary
data comes from observation to the respondents. First, the observation will be carefully
evaluated and to ensure its validity and reliability by pilot test. There are various methodologies
for gathering data like the following:

➢ Interviews

➢ Observations

3.5.1 Interview
An interview is a formal face-to-face meeting, especially, one arranged for the assessment of
the qualifications of an applicant, as for employment or admission. A conversation, as one
conducted by a reporter, in which facts or statements are elicited from another, the interview is
the primary technique for information gathering during the systems analysis phases of a
development project. It is a skill which that must be mastered by every analyst.

18
The interviewing skills of the analyst determine what information is gathered, and the quality
and depth of that information. Interviewing, observation, and research are the primary tools of
the analyst. The interview is a specific form of meeting or conference, and is usually limited to
two persons, the interviewer and the interviewee. In special situations there may be more than
one interviewer or more than one interviewee in attendance (Part model, 2017).

3.5.1.1 Advantages of interview

The main advantage of interviews is that the researcher (interviewer) can adapt the questions
as necessary, clarify doubt and ensure that the responses are properly understood, by repeating
or rephrasing the questions. The researcher/interviewer can also pick up nonverbal cues from
the respondent. Any discomfort, stress and problems that the respondent experiences can be
detected through frowns, nervous flapping and another body language, unconsciously exhibited
by any person.

This would be impossible to detect in a telephone interview. So face-to-face helps the

interviewee to get the desired results and help them the expression of the person to whom they
are interviewing. By reading the facial expression of the respondent the interviewer can easily
understand what the respondent wants to tell them about anything (answers-yahoo, 2017)

3.5.1.2 Disadvantages of interview

The main disadvantages of face-to-face interviews are the geographically limitations they may
impose on the surveys and the vast resources needed if such surveys need to be done nationally
or internationally. The costs of training interviewers to minimize interviewer's biases for
example differences in questioning methods, interpretation of response are also high. Another
drawback is that respondents might feel uneasy about the anonymity of their responses when
they interact face-to face interviews.

3.5.2 Observation

An observation is a data collection method used to gather detailed information about a situation
or event. Observation data is used to describe the setting, activities, participants, and the
meaning of the observations from the observer's perspective. Observation in this project will
be based on facts which that are both accurate and detailed, but left any irrelevant or slight
information that makes the description difficult to understand. This data allows the reader to
fully understand the situation.

19
3.5.2.1 Advantages of observation

a) Allows you to directly see what people do practically rather than relying on
what people say they did.

b) Observer’s document program activity takes time and cost gathering providing
documentation, rather than relying on recollections of the events.

3.5.2.2Disadvantages of observations

a) Observer bias may occur. (Observer may only notice what interests him or her).

b) With participant observation, a skilled facilitator is needed to help participants present a

critical evaluation.

3.6 Process Modeling

A process model is a formal way of representing how a computer system operates. It illustrates
the processes or activities that are performed and how data move among them. A process model
can be used to document the current system (i.e. as-is system) or the new system being
developed (i.e. to-be system). Whether computerized.

Process modeling is the process and analysis of data and objects that are used in business or
other contexts and identification of the relationship among these data objects. Data modeling
is a first step in doing object-oriented Programming and involves professional data modelers
working closely with business stakeholders, as well as potential users of information systems.

3.6.1 Data flow Diagram (DFD

Data Flow Diagrams show information transfers and process steps of a system. A general
concept is an approach depicting how occurs input in a system, further processes and what runs
out. The aim of DFD is in accomplishing of understanding between developers and users. Data
flow diagrams are maintained with other methods of structured systems analysis.

A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs
and outputs. As its name indicates its focus is on the flow of information, where data comes
from, where it goes and how it gets stored.

✓ Graphical representation of the "flow" of data through an information system;

✓ Modeling process aspects;

20
 ✓ An overview of the system;

✓ For the visualization of data processing (structured design);

✓ What kinds of information will be input to and output from the system;

✓ Where the data will come from and go to;

✓ Where the data will be stored. (concept draw, 2017)

Data Flow Diagrams notations:

The Data Flow Diagrams solution from the Software Development area of Concept Draw
Solution Park provides three vector stencil libraries for drawing DFD using the Concept Draw
PRO diagramming and vector drawing software.

The design elements library Data flow diagram (DFD) contains 15 data flow diagram symbols
for drawing both context-level data flow diagram and Level 1 DFD.

The design elements library DFD, Ganesa’s notation contains 12 data flow diagram symbols
of Ganesa’s DFD notation. The design elements library DFD, Yourdon and Coed notation
contains 22 data flow diagram symbols of Yourdon/DeMarco DFD notation (concept draw,
2017)

3.6.2 Unified Modeling Language (UML)

UML stands for Unified Modeling Language; UML is a way of visualizing a software
program using a collection of diagrams. The notation has evolved from the work of Grady
Booch, James Rumbaugh, Ivar Jacobson, and the Rational Software Corporation to be used for
object-oriented design, but it has since been extended to cover a wider variety of software

21
engineering projects. Today, UML is accepted by the Object Management Group (OMG) as
the standard for modeling software development (smart draw, 2017)

The key to making a UML diagram is connecting shapes that represent an object or
class with other shapes to illustrate relationships and the flow of information and data. To learn
more about creating UML diagrams:

Types of UML Diagrams

The current UML standards call for 13 different types of diagrams: class, activity,
object, use case, sequence, package, state, component, communication, composite structure,
interaction overview, timing, and deployment.

These diagrams are organized into two distinct groups: structural diagrams and
behavioral or interaction diagrams.

3.6.2.1 Use Case Diagram (UCD)

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

A use case diagram shows you some of the use cases in your system, some of the actors in
your system, and the relationships between them. A use case is a high – level piece of
functionality that the system will provide. An actor is anyone or anything that interacts with
the system being built.

Use case diagram is done in an early phase of a software development project. The use case
diagram describes the use case (functions of the system), Actors (users) and the relationship
between the actors and the use case is connective.

22
3.7 Data Modelling

Data modeling is the analysis of data objects and their relationships to other data objects. Data
modeling is often the first step in database design and object-oriented programming as the
designers first create a conceptual model of how data items relate to each other. Data modeling
involves a progression from conceptual model to logical model to the physical schema (Web,
2017). Data modeling is the process and analysis of data and objects that are used in business
or other contexts and the identification of the relationship among these data objects. Data
modeling is a first step in doing object-oriented Programming and involves professional data

23
modelers working closely with business stakeholders, as well as potential users of information
systems.

3.7.1 ERD Diagram

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

interrelationships between entities in a database. ERD show entities in a database and
relationships between tables within that database. It is essential to have one of these if you want
to create a good database design. The patterns help focus on how the database works with all
of the interactions and data flows, although another useful tool is a Data Flow Diagram (DFD)
which more directly describes this. ERD is a detailed, logical representation of the entities,
associations and data elements for an organization or business. ERD is a graphical modeling
tool to standardize ER modeling; the modeling can be carried out with the help of pictorial
representation of entities, attributes and relationships (lucidchart, 2107).
The basic building blocks of ERD are Entity, Attributes, Relationship and lines entity is an
object that exists and is distinguishable from another object or other objects words Entity types
or Entity set is a collection of similar entities; an entity may belong to more than one entity
type. A relationship is an association of entities where the association includes one entity from
other particular types is a meaningful, association before entity types. Attributes are properties
of entity types in other words; entities are described in a data base by a set of attributes (Peter
Pin-Shan Chen, 1976).

3.7.1.1 ERD Symbols

The ERD is used to represent database schema, here are some symbols used to represent ERD
Symbols:

A rectangle represents an Entity.

An Ellipse represents an attribute.

A diamond represents a relationship

Lines represent linking of attributes to entity sets & of entity sets to relationship sets.

24
3.7.1.2 TYPES OF RELATIONSHIP

The Relationship is an association among one or more entities. This relationship can be broadly
classified into one-to-one relation, one-to-many relation, and many-to many relations.

• One to many Relationships Type: Abbreviated 1:M, the relationship that associate one
entity to more than one entity is called one to many relationships: - Example is country having
states for one country there can be more than one states hence is an example of one-to-many
relationships.

• One to one Relationship Type: Abbreviated 1:1, one to one relationship is a special case
of one-to-many relationships. True one to one relationship is rare. relationship between the
president and Country is an example is one to one relationship.

• Many to Many Relationships Type: Abbreviated M: M, the relationship between

EMPLOYEE entity and PROJECT entity is an example of many to many relationships. Many
employees will be working in many projects hence the relationship between employee and
project is many to many relationships.

• Many to One Relationship Type: Abbreviated M: 1, the relationship between

EMPLOYEE and DEPARTMENT is an example of many to one relationship, there may be
EMPLOYEE working in one DEPARTMENT. Hence the relationship between EMPLOYEE
and DEPARTMENT is many to one relationship (Aplim, 2010).

25
3.7.1.3 ERD of the Proposed System

3.8 Suitable Solution Strategies of the Proposed System

As we are reaching the development phase, this section would contemplate other ways the
project’s objectives can be achieved. As you may know, the system will be developed in PHP.
Programming language and it is the most used or popular.

26
3.9 System Feasibility

A feasibility study for an information system project is an in-depth look at the project to
determine whether or not an organization should proceed with its implementation. Feasibility
studies provide project managers with an overview of the primary issues related to the project,
as well as insights about the outcomes of the project, before the company invests too much time
and money (reference, 2017). A feasibility study could be used to test a new working system,
which could be used because the Feasibility study is an analysis of possible alternative solutions
to a problem and a recommendation on the best alternative. It can decide whether a process be
carried out by a new system more efficiently than the existing one.

The Feasibility or the feasibility study is divided into four types:

1. Technical Feasibility.

2. Operational Feasibility.

3. Economic Feasibility.

4. Schedule Feasibility.

3.9.1 Technical Feasibility

Technical Feasibility is defining as the feasibility that is concerned with specifying equipment
and software that will successfully satisfy the requirement. It compasses the technical needs of
the system Configuration of the system is given importance than the actual make of hardware
while examining technical feasibility (quora, 2017).

This can be counted in terms of volumes of data, trends, frequency of updating, etc. to estimate
whether the new system will perform sufficiently or not. Technological feasibility is carried
out to determine whether the company has the capability, in terms of software, hardware,
personal and expertise, to handle the completion of the project.

27
3.9.2 Operational Feasibility
Operational feasibility is the ability to utilize, support and perform the necessary tasks of a
system or program. It includes everyone who creates, operates or uses the system. To be
operationally feasible, the system must fulfill a need required by the business. The following
table will show the training cost of the user of the system.

28
3.9.3 Economic Feasibility
Economic analysis is the most frequently used evaluating the effectiveness of the proposed
system, more commonly known as benefit analysis. The benefit analysis is to determine
benefits and saving which are expected from a candidate system and compare them with cost.
If the benefits are more than the cost, the decision is made to design and implement the system.
The cost and benefits may be direct or indirect and tangible or intangible

3.9.4 Schedule Feasibility

Typically, this means estimating how long the system will take to develop, and if it can be
completed in a given period using some methods like payback period. Schedule feasibility is a
measure of how reasonable the project timetable is.

This involves questions such as how much time is available to build the new system, when it
can be built, whether it interferes with normal business operation, the number of resources
required, dependencies, can the system be developed in time etc. The project duration schedule
is explained in the following.

29
3.10 Chapter Summary

This chapter presented the following sections: Introduction, Operational Framework, Work
Break down structure (WBS), System Requirement, Problem Analysis Identification,
Requirements Gathering Techniques, Process Modeling, Data Modeling, Suitable solution
Strategies of the proposed system, System Feasibility and Chapter Summary

30
 CHAPTER FOUR

SOFTWARE DESIGN

4.0 INTRODUCTION

This chapter will discuss about the software design of the Online Faculty Management
System. Designing is the most significant phase of software development; it requires a careful
planning and philosophy on the part of the app designer. The design phase involves
converting the App Requirement Specification (SRS) identified during the initiation and
planning phases in to a logical Design and then into Physical Design that the technical
programmer can follow to develop the project during the development phase. Design will
play a bigger role in every project, therefore; developing a good design is needed and related
to have enough information.

4.1 ARCHITRCTURAL DESIGN

The Online Faculty Management System will have the following features:

Registration

Online Faculty
Student Management System Users

Reports

Figure 4.1 architecture design

31
4.2 USER INTERFACE DESIGN

Interface design is the process of defining how the app will interact with the external entities
“web”. It describes the layout of the pages and the flow of events, and is also concerned with
where and how data are represented on the pages. However, in a User Interface Design, the
needs, experience, and capabilities of the mobile app users must be taken into account. In
addition, the designers should be aware of users‟ physical and mental limitations “E.g.,
limited short-term memory” and should recognize that people make mistakes. The user of this
digital app doesn’t need any software to install, but only requires a browser interface to
access it. To access the app, users will be required to have login through the web app’s login
page, which can be accessed via homepage.

Figure 4.2 User Interface

4.3 DATABASE STORAGE DESIGN

Design for database for using MySQL with relational database management app Provides
minimum search times when locating specific records. That will provide Stores data in the
most efficient manner possible to keep the database from growing too large, makes 41 data

32
updates as easy as possible and creating more flexible enough to allow inclusion of new
functions required of the app.

4.4 DATABASE DESIGN

Database design process integrates relevant data in such a manner that is can be processed
through a mechanism for recording the facts. A database of an organization is an information
repository that rep.

Resents facts about the organization, the database design is a complex process. The
complexity arises mainly because of the identification of relationships among individual
components and their representation for maintaining correct functionality are highly
involved. The complexity increases if there are many-to-many relationships among individual
components. This section discusses about the database created for this project. The database
is created using MySQL.

The following diagram shows the database tables. The most relationship among the table is
one to many relationships. The student, admin tables are the center bridge among the other
tables. To deploy this app, it will be used three tier architectures.

4.4.1 DATABASE NORMALIZATION

Normalization is the process of organizing data in a database. This includes creating tables
and establishing relationships between those tables according to rules designed both to
protect the data and to make the database more flexible by eliminating two factors:
redundancy and inconsistent dependency. Redundant data wastes disk space and creates
maintenance problems. Most popular Normalization stages include.

Un normalized

(ID, Username, Password, Student, Name, Teacher, Faculty, Subject, Year level)

33
4.4.1.1 FIRST NORMAL FORM (1ST NF)

First Normal Form (1NF): A relation is in first normal form (1NF) if the following two
constraints both apply: There are no repeating groups in the relation (thus, there is a single
fact at the intersection of each row and column of the table) and A primary key has been
defined, which uniquely identifies each row in the relation.

Table 4.1 First Normal Form

Teacher Teacher Phone subject Student_ Class

_id name name

3 Ali 465433 PHP Farah cl17D

5 Ahmed 784777 C Hussein Cs17

language

4.4.1.2 SECOND NORMAL FORM (2ND NF)

Second Normal Form (2NF): A relation is in second normal form (2NF) if it is in first normal
form and contains no partial functional dependencies. A partial functional dependency exists
when a non-key attribute is functionally dependent on part (but not all) of the primary key.
To convert a relation with partial dependencies to second normal form, the following steps
are required: Create a new relation for each primary key attribute (or combination of
attributes) that is a determinant in a partial dependency. That attribute is the primary key in
the new relation. Move the non-key attributes that are dependent on this primary key attribute
(or attributes) from the old relation to the new relation.

4.4.1.3 THIRD NORMAL FORM (3RD NF)

Third Normal Form (3NF): A relation is in third normal form (3NF) if it is in second normal
form and no transitive dependencies exist. A transitive dependency in a relation is a
functional dependency between the primary key and one or more non-key attributes that are
dependent on the primary key via another non-key attribute. You can easily remove transitive
dependencies from a relation by means of a three-step procedure: 1) For each non-key
attribute (or set of attributes) that is a determinant in a relation, create a new relation. That
attribute (or set of attributes) becomes the primary key of the new relation. 2) Move all of the

34
attributes that are functionally dependent on the primary key of the new relation from the old
to the new relation. 3) Leave the attribute that serves as a primary key in the new relation in
and stays as foreign key in the old table.

Table 4.3 Third Normal Form

4.4.1.4 NORMALIZED TABLES OF THE PROPOSED APP

Class id F no Sub no Class name Scheu no Teacher no Student no

3 1 1 Cs17D 1 1 1

Normalization of Database can decrease redundancy, increase efficiency and reduce

anomalies by implementing three of seven different levels of normalization called Normal
Forms. The first three NF’s are usually sufficient for most small to medium size applications.

4.4.2 TRANSFORMING E-R DIAGRAMS INTO RELATIONS

Figure 4.3 ERD Transforming

4.4.3 DATA DICTIONARY

Data dictionary, or data repository, is central store house of information about App’s data. I
will use it to collect, document, and organize specific facts about app include the data flows,
data stores, external entities, and processes. The data dictionary also defines and describes all
data elements and meaningful combinations of data elements.

35
Table 4.5: User Registration

Table 4.6: Year Level Registration

Column Type
Y_no (Primary) int(11)

Y_name varchar (50)

Table 4.7: Student Registration

Table 4.8: Teachers Registration

36
37
4.5 DESIGNING FORMS AND REPORTS

The most effective method of online data entry is a form filling, in which a blank form that
duplicates or resembles the source document is completed on the screen. The user enters the
data and then moves to the next field. The form can have many control features such as menu
bars, toolbars, dialog boxes, text boxes, command buttons, list boxes, scrollbars, drop-down,
group boxes, check boxes, and more others. The design of data entry screens shall consist of
the following forms.

1. User Registration form

2. Login form
3. dashboard form
4. year level Registration form
5. Student form
6. class form

38
Figure 4.4 Create User Activity

39
 Figure 4.6 year level Activity

Figure 4.8 class

40
4.6 CHAPTER SUMMARY

This chapter discussed app design of the Mobile App for Health care provider App including
Architectural Design, user interface design, Data storage design, database design,
Normalization, Transforming E-R diagram into relations, data dictionaries, design forms and
finally chapter summary.

41
 CHAPTER FIVE

SYSTEM IMPLEMENTATION

5.0 INTRODUCTION

This chapter discusses the functions’ implementations of the online faculty Management
system with the coding phase then testing and finally documentation. The system has two
users; who are the admin, and student, the admin has the highest ability of the systems and
controls the rest of the students. To implement web for HORSEED Admission, Researchers
php programming language as front end, PHP and MySQL server as back end.

5.1 CODING PHASE

This Phase is devoted to providing access to most of the computer programs that I used to
prepare the data and apply the programming is techniques, instructions on how to construct
this application project using the software available on the attached compact disk (CD).

5.2 TEST SYSTEM IMPLEMENTATION

The testing phase involves some modification to the previous design phase and system
testing has been done to minimize the programming errors. Testing the system is a very
important stage to ensure that all system requirements have been developed without errors.
System testing can be done through some stages. These include.

1. Developing test
2. Release test
3. User test

5.2.1 DEVELOPMENT TESTING

Development testing is a software development process that involves the synchronized

application of a broad spectrum of defect prevention and detection strategies to reduce
software development risks, time, and costs. Development testing is always done by the
developer who is responsible programming stage. This testing shows as if the wrong
username and password are entered can’t to be allowed to access the system.

42
Figure 5.1 shows the login validation

Figure 5.1 shows what happens when you enter the wrong credentials. The system will return
a message in a toast telling you either your username or password is incorrect.

5.2.2 RELEASE TESTING

The ability to evaluate and ensure the quality of in-process and/or final product based on
process data, which typically include a valid combination of measured material attributes and
process controls. A release is the distribution of the final version of an application. A
software release may be either public or private and generally constitutes the initial
generation of a new or upgraded application. This testing type is done by software
development Solution Company, though the system is coming finalize the product.

43
figure 5.2 Main form

5.2.3 USER TESTING

User testing is a stage in the testing process in which users provide input and advice on
system testing. This may involve formally testing a system that has been admin from by user,
or could be an informal process where users experiment with a new software product to a see
if they like it and that it does what they need. User testing is essential, even when
comprehensive system and release testing have been carried out. The reason for this is that
influences from the user’s working environment have a major effect on the reliability,
performance, usability, and robustness of a system.

5.3 DEVELOPING USER MANUALS

In computer software product development, documentation is the information that describes

the product to its users. It consists of the product technical manuals and online information
(including online versions of the technical manuals and help facility descriptions). The term
is also sometimes used to mean the source information about the product contained in design
documents, detailed code comments, white papers, and blackboard session notes. The term is
derived from the idea that engineers and programmers. Also is a general term for a
multiplicity of documents in a chosen mix of media and with a certain collection. The

44
Purpose of documentation is the use to support a tool or a process. Classical documentation is
a set of documents printed on paper.

Figure 5.4 User form

45
 Figure 5.7 Schedule

Figure 5.8 class

46
5.4 CHAPTER SUMMARY

This chapter discusses the implementation and testing of the system. Developing the system
requires a server, host to access the portal. The purpose of the Testing is to check the errors
and analyze the problem to develop a successful System that meets the users’ requirements.
In this I have discussed important points on the system Development starting from
introduction of the chapter then the Coding step of the system, Types of testing, User
Documentation, and the last Implementation although I have covered the majority of the
project now, I am going to Conclude and Summarize this research and for recommendations
of the project.

47
 CHAPTER SIX

CONCLUSION & ENHANCEMENT

6.0 INTRODUCTION

This chapter covers the achieved objectives of the project and demonstrates how the works of
this project are implemented. Also, it debates the experiences that have been gained during
the development of this project and it also includes the future recommendation which will
facilitate how to improve the functionality and features of this Mobile Health care provider
app in the future. 6.1 OBJECTIVE ACHIEVEMENT The key objective for developing this
project is to develop a mobile Health care provider app in Somalia and then, the project will
be applied to the other universities. Furthermore, here are the details of the project objectives
that have been accomplished.

1. This Research Studied the current mobile health care provider systems in \ Somalia:
this study focused on the

2. The researcher designed the mobile health care provider system using mod tools such
as unified modeling language (UML) diagrams including use cases class diagrams.

3. The research coded the proposed system and tested it; during the implementation phase
of the project using android with PHP or front end and MYSQL for the back end, and
eventually achieve this objective properly.

Generally, all the objectives above mentioned have been attained and the constraint of the
users has been met through the project.

6.2 WEAKNESSES AND PROBLEMS OF THE SYSTEM

A lot of experiences have been gained during this project such that the literature review
provided knowledge of the existing system of mobile application systems for universities,
and also it helps in identifying the weaknesses and the strengths of the developing system by
comparing the features of the system that is going to be developed with three existing
systems which are related to it.

The methodology study, it identifies the software engineering methodology for any software
engineering system. Moreover, one of the most experiences gained during this project was
the methods used to get the requirements from the user and doing the practice in analyzing
the collected requirement to achieve the objectives of the system.

48
6.3 FUTURE WORK & RECOMMENDATIONS

The future enhancements of the system are as follows:

1. To improve the security and privacy of the mobile application system for the University of
Somalia health care provider.

2. To add a help desk for the sake of solving the problems that many be faced by the new user
of the system.

3. To extend the scope of the project and include extra modules and functions.

6.4 CHAPTER SUMMARY

This chapter discussed the Introduction, Objectives Achieved, Weaknesses and problems of
the system, Future Work and Chapter Summary.

49
 REFERENCES

1. Siddhant Gokule (2016). web Application for Online Faculty Management System
Process. International Journal of Emerging Engineering Research and Technology.
2. Tong, Stephen (2015). Application of Technology Online Faculty Management
http://web.worldbank.org/archive/website00236B/WEB/REG_01.HTM.
3. Jadhav Snehal Balasaheb (2014). Web Based College Online Faculty Management
System. International Journal of Engineering Development and Research.
4. Simon Bates (1991). A History of web Application Development.
http://manifesto.co.uk/ history-mobile-application-development/.
5. Dirk Reagle (2015). 10 Years of web Industry History in 10 Minutes.
http://www.sitepoint.com/ the-advancements-in-web-design-and-how-it-has-
developedinto-a-strong-industry/.
6. By Peterson's Staff (2015). Types of Colleges and Universities in the U.S. Types of
Colleges and Universities in the U.S.11 23 2015.html.
7. Rohit Jadhav (2015). A web Application to Enhance the Online faculty Management
Process and Communication between Members of an Institute. International Journal
on Recent and Innovation Trends in Computing and Communication.
8. Sanchita Chhajed (2014) web Application for Online Faculty Management System
Process. International Journal of Emerging Engineering Research and Technology.

50
 PENDICES

Appendix A – Budget

Items Unit Cost Units Total

Printing Costs

Drafts 0.5 SoSh Approx. 77 $1.5

Final 0.5 SoSh 74 $1.5

Grand Total $3

51
Appendix B – Time Frame of the Development of the proposed system

52