RESEARCH GUIDE

FACULTY OF

ENGINEERING & COMPUTER SCIENCE

DEPARTMENT

INFORMATION TECHNOLOGY

1
 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”

Name & Sign researcher 1: ___ Date: __/____/______

Name & Sign researcher 2: __ Date: __/____/______

Name & Sign researcher 3: Date: __/____/______

Name & Sign researcher 4: Date: __/____/______

Name & Sign researcher 5: Date: __/____/______

2
 DECLARATION B

We hereby declare that, this thesis has been done by us under the supervision of Eng.
____________________________Lecturer of Faculty Engineering and computer Science.

Name and signature of Supervisor: _______

Date ________/_______/__________

3
 APPROVAL SHEET

This Thesis titled online _________________________at KOWNAYN UNIVERSITY

submitted by

1) _______________________ 2) _______________________ 3) _________________

4) ______________________________ 5) ___________________________

to the Department of Engineering And Computer Science, KOWNAYN UNIVERSITY, has

been accepted as satisfactory for the partial fulfillment of the requirements for the degree
of Bachelor of Science in Engineering and Computer Science and approved as to its style
and contents. The presentation has been held on June 2024.

Name and Sig. of Chairman of the Panel

Name and Sign of Panelist Name and Sign of Panelist

Name and Sign of Dean of faculty

Name and Sign of Director of Academics

4
 ACKNOWLEDGEMENT

First, we would like to thank Allah for giving us the opportunity to work on this project.
Second, our sincere thankfulness goes to our thesis supervisor Eng. _____________
Helpful feedback and valuable suggestions during the development of this thesis.
We would like to express our heartiest gratitude to Eng. Ibrahim Yusuf Mohamed
Bulbul, Head of Department of Information technology, for giving us an opportunity
to carry out the research work, without him we should not reached our goal and also
to other faculty member and the staff of C Engineering & Computer Science at
KOWNAYN UNIVERSITY.
Thanks to KOWNAYN UNIVERSITY for the study opportunity and for the technical
assistance during the last phase of finishing this thesis.
We are greatly indebted to our beloved Parents, our fathers and our mothers may
Allah protect them; they are always very understanding and supportive on our
choices. They love us more than themselves and have sacrificed so much to support
us.
Finally wish to thank our families, friends, roommates for their help and constant
support, thank again for your understanding and encouragement in our many, many
moments of crisis. Your friendship makes our life a wonderful experience thanks all.

5
 DEDICATION

We dedicate our dissertation work to our families and many friends. A special feeling
of gratitude to our loving parents, to our mothers and fathers a strong and gently
soul who taught us to trust in Allah, believe in hard work and that so much could be
done with little..

6
 ABSTRACT

Freshwater resources are of major environmental, economic and social importance.

Their distribution varies widely among and within countries. If a significant share of a
country’s water comes from transboundary rivers, tensions between countries can
arise. In arid regions, freshwater resources may at times be limited to the extent that
demand for water can be met only by going beyond sustainable use. Freshwater
abstractions, particularly for public water supply, irrigation, industrial processes and
cooling of electric power plants, exert a major pressure on water resources, with
significant implications for their quantity and quality. Main concerns relate to
overexploitation and inefficient use of water and to their environmental and socio-
economic consequences.

7
TABLE OF CONTENTS

PUT IT CLEARLY HERE

8
 General Guidelines of the Font:
Headings for Chapter Names: Tahoma 14, CAPITAL. LETTERS, Bold. Headings for Big Titles:

Tahoma 14, Small Letters, Bold.

Sub titles: Tahoma, 12, Bold. Passages: Tahoma, 12 Small

Letters Spacing: 1.5 Spaces

No header & no footer

The Proposal should be at least 30 pages, while the complete thesis should be at least 60 pages.

9
10
 CHAPTER ONE

INTRODUCTION

1.0 INTRODUCTION

Few initiating and prefacing phrase of one or two paragraphs should be included here
CHAPTER ONE INTRODUCTION

Few initiating and prefacing phrase of one or two paragraphs should be included
here to justify the heart of what is about to be embarked to meet the expected goals
of this chapter

1.1 BACKGROUND OF THE PROJECT

The background of the project introduces the salience, status and the theoretical
framework necessary to carry out the study. It also clearly broadly describes the
prevailing conditions of the study problem at the local, national and global levels. This is
intended to clarify what the study is all about. It should entice the interest of the readers.

The background of the research balances four important perspectives. These

are:

a. Historical (global, regional and national level)

b. Theoretical/applications

c. Conceptual and;

d. Contextual perspectives or the problem coherence

e. The length of the background varies for the proposal and reporting of the
project.

11
1.2 STATEMENT OF THE PROBLEM

In this section of the project proposal/report, the problem addressed by the study is

clearly delineated. The problem addressed by the study can have one or more of several
Forms. It could be that some existing theories or models seem not to be working as
Previously held. It also may be that some phenomena had been understudied in previous
studies and thus requires a closer look. Or there may be a serious situation that requires a
more specific profound study. Furthermore, the students should show that; the problem is
so serious that study is worth undertaking by including opinions of professionals or
academics or politicians.

a. The problem is connected to business, technological, political and social issues by

b. Originality and Contribution

Finally, the student must be able to summarize the study problem statement in a single
sentence.

12
1.3 PURPOSE OF THE PROJECT

In this part of the project book, the developer is required to clarify the need for the
system. Why is it necessary after all? The broader goals that need to be attained at
the conclusion of the system must be shown clear-cut.

1.4 PROJECT OBJECTIVES

The objectives are the narrow goals that derive from the overall purpose of the system.

They include the specific goals to be reached. Furthermore, the project objectives.

13
1.5 RESEARCH QUESTIONS

Questions that highlight or serve as base point scenario to precede the study
is here by entered with their relevant answers.

They must be attainable at the basic level. The aim is like where you intend
to go to, while objectives represent the specific steps taken to reach that
place.

1.6 THE SCOPE OF THE SYSTEM

The scope identifies the boundaries within which the system is being
developed. Such limits as contents, geography and the period within which
the system is to be developed.

1.7 SIGNIFICANCE OF THE PROJECT

Significance or importance of the project claims that the system is necessary

for the improvement over the existing conditions. The developed system must
help improve the knowledge, practice and policy conditions of the prevailing
context.

1.8 PROJECT ORGANIZATION

The system in which the project phases are arranged according to their
timelines will be concisely mentioned herein. Some sub-phases may have a
very complex collective hierarchy that need earlier attention before consuming
up the whole project resources.

14
15
 CHAPTER TWO

LITERATURE REVIEW

2.0 INTRODUCTION

Few initiating and prefacing phrases of one or two paragraphs should be

included here to justify the heart of what is about to embarked to meet
the expected goals of the review of related literature.

2.1 CONCEPTS, OPINIONS, OR IDEAS FROM AUTHORS/ EXPERTS

This section introduces what prior literature has said about the subject
matter to be

Studied now. The wording should be in a way such that the expression
belongs to the student but the concept is preserved as originated by its
author.

The order of the literature citation is best arranged in the following order:
international, regional and then local perspectives. The student must make
sure to discuss those points relevant to the current study only. These must
be aligned with current study research questions, objectives or hypotheses.
Finally, this chapter is closed with the literature gap.

This means what previous literature could not have achieved or has
remained inconsistent throughout.

2.2 PREVIOUS WORK/ EXISTING SYSTEMS

This section deals with the previous work performed so far or existing
systems of the project. To provide insight into the project development

16
2.3 GAP ANALYSIS AND DIRECTION

Tabulated comparative will be entered here. Closer look of the resultant

data from the reviewed literature based on known and unknown
weakness will be discussed. The tabulation should point out the
Developer/Author Name, Project name, Assumptions, the Solution and
its limitations)

2.4 CHAPTER SUMMARY

Summarize the major points discussed, the result reached and the roads
ahead

17
 CHAPTER THREE

REQUIREMENT ANALYSIS

3.0 INTRODUCTIO
N

Few initiating and prefacing phrases of one or two paragraphs should be

entered here to justify the heart of what is about to embarked on as well
as the pledged points of the prior chapter down to this chapter to meet the
expected goals of the Requirement Analysis

3.1 USER REQUIREMENT ANALYSIS

User Requirement Analysis is the first of five phases in the systems

development life cycle (SDLC).

Consider here use of use of analysis tool as the DFD or UML functional
decomposition diagrams (FDD) to describe the current systems analysis
phase activities and the end product of the systems analysis phase

3.2 PRELIMINARY INVESTIGATION

A preliminary investigation is an inquiry conducted to launch fact gathering

from the case’s stated problem which may be further one of the following

Main Reasons for Systems Projects Preliminary Investigation

A. Project Level

a. Improved service

b. Support for new products and services

18
c. Better performance

d. More information

e. Stronger controls

f. Reduced operating costs

g. Thesis Level

h. Academic study

i. Experiment

j. Problem analysis and solving

k. Or anything that reflects the understanding of an existing

body of theory or knowledge related to current problem

19
3.2.1 Organizational Profile

Reading, Listening, Watching and or Browsing all archive media of the

concerned system performance from the incept date directly to the
moment of launch

3.2.2 Current system

Here an in - depth analysis of how the current system is operating is

entered following the fact finding tasks performed below
3.2.3 The limitations of the current system
The known limitation from the users or customer’s direct account is
enlisted here to cross check with the later - to - come result from the in -
depth analysis.
Category of the expected limitation ma y touch on: -
a. Administration problems

b. Technical problems

c. Other limitations

3.3 DATA GATHERING

Data gathering is a step-by-step problem solving technique used to analyze

information

system domain without any regard that the system being analyzed be
either a manual -based information system or computer-based information
system.

20
There are various Data Gathering methodologies to be utilized. At
least one of the following Data Gathering methods is minimally required.

a. Interviews

b. Observations / Surveys

c. Questioners and other documents.

3.3.1 DATA FLOW DIAGRAM (DFD) / ( UML)

These two analysis methods are mutually excluded for implementation and
one has to observe the uniformity of analysis methods in this chapter.

3.3. 2 DFD

Use Data-flow diagram (DFD) graphical representation to show the "flow"

of data through an information system. DFDs can also be used for the
visualization of data processing (structured Analysis). Indicate the style of
DFD as to Yourdon or Gane and Serson style that will be typically adopted

3.3. 3 UML

In the event that UML is opted, object-oriented analysis will be used to

describe the information system including the object modeling terms and
concepts, like objects, attributes, methods, messages, classes, and
instances, use cases, use case diagram, class diagram, state and showing
relationships among objects and the concept of inheritancethrough
object relationship diagram.

21
3.4 PROBLEM STATEMENT

After having extensively investigated the current system, analyst should

have arrived to a point that the documented analysis shows drawback in
comparison the Management business case. This is the time when a
statement declaring the discovered problems is to be composed.

3.5 FEASIBILITY STUDY

Feasibility study is process used for identifying if this problem is feasible to

solve or not.

3.5.1 Technical feasibility

In Technical feasibility, we explain all technological resources to be

capitalized including hardware and software needed to solve these
problem in a three option tabulated format

22
 3.5.2 Operational feasibility

The operators are those who work on system for performing daily
activities from old version (manual) to automated system.
3.5.3 Schedule feasibility

The accurate time that the development of this project is to lapse in the
names of months if not weeks is mentioned according to the timetable of the
Faculty semesters
3.5.4 Feasibility report

The report is made to be short, concise and clear aimed for the purpose to
empowering the management to decide the merit of total cost of
ownership such that recommending option one be approved since it offers
the most promising large-scaled solution.

3.8 CHAPTER SUMMARY

Summarize the major points analyzed and then specified, the result
reached and the roads ahead

23
 CHAPTER FOUR

SYSTEM DESIGN

4.0INTRODUCTION

Designing is the most significant phase of software development. it

requires a careful planning and philosophy on the part of the system
designer. Designin g software means to plan how the varieties of parts of
the software are going to achieve the preferred goal.
It should be done with greatest care because if the phase contains any
error then, that will affect the performance of the system, as a result it m
ay take more processing time, more response time, extra coding
workload etc
4.1 DESIGN GOALS

Design intends to articulate efficient design strategy that:

Make system user- friendly. This being necessary so that system could be
used efficiently.
Make the system reliable, understandable and cost -
effective.
4.2 DATABASE DESIGN:

Design is the process of producing a detailed data model of a database.

This logical data model contains all the needed logical and physical
design choices and

24
 Physical storage parameters needed to generate a design in a Data
Definition Language, which can then be used to create a database. A
fully attributed data model contains detailed attributes for each entity.

4.3 ENTITY RELATIONSHIP DIAGRAM (ERD)

ER diagram is a diagram that helps to design databases in an effective

and efficient way.

4.3.1 De-normalization of entity relational diagram

Demoralization is the process of taking a normalized database and

modifying table structures to allow controlled redundancy for increased
database performance. Attempting to improve performance is the only
reason to ever denormalize a database. A denormalized database is not
the same as a database that has not been normalized. Denormalizing a
database is the process of taking the level of normalization within the
4.3.2 Normalization

Normalization is a process in which a given set of relations is replaced by

successive collections of relations that have a simpler and more regular
Structure.
4.4 DATA DICTIONARY

A data dictionary is a part of the metadata that is used to understand

the data and the databases that contain it. The data dictionary identifies
data elements and their attributes including names, def initions and units
of measure and other information. Often they are organized as a table.

25
4.5 TABLE DESIGN

Table design is where the designer of the system deeply explains Table
reference and the modeling between the referential; integrity of the
sequential flows.

4.6 FORM DESIGN

Form design is where the developer of the system deeply explains system
tasks and how forms of the system are working together by observing the
sequential flows.

4.7 CHAPTER SUMMARY

Summarize the major points designed and then specified, the result
reached and the roads ahead .

26
 CHAPTER FIVE
SYSTEM DEVELOPMENT

5.0 INTRODUCTION

Software Coding, testing and debugging are a risky elements of the

eventual review of specification design and coding. Testing of software
leads to the uncovering of errors in the software’s useful and performance
requirements. Testing also provides a good indication of software
consistency and software excellence as a whole.
5.1 CODING PHASE

This phase is devoted to providing access to most of the computer

programs that have been used to prepare the data and apply the
programming techniques.
Instructions and how to construct and /install this application project and
using the software included is m ade available on an attached compact
disk (CD ) that comes with th is
graduation book.
5.2 TYPE OF TESTING
a. Unit testing

The testing of individual program o r module is called unit testing. The

objectiv
e is to identify and eliminate execution er rors that could cause the
program to terminate abnormally, and errors that could have been missed
during the checking.

27
b. Integration testing

Testing two or more programs that depend on each other is called

integration testing, or link testing.
c. System testing

After completing integration testing, system testing will performed, which

involves the entire information. A system test includes all typical
processing situations and is intended to assure users, developers.
During system testing, user enter data including samples of actual, or live,
data, perform queries, and produce report to simulate actual operating
condition.
5.3 USER DOCUMENTATION

User documentation consists of instructions and information to users who

will interact with the system and includes user manuals help screen.
User documentation includes the following: -A system overview that clearly
describes all major system features, capabilities, and limitations.

5.4 IMPLEMETATION

Implementation is where we implement how the system works as the

chronological flow pages with validation and verification scenarios.

5.5 CHAPTER SUMMARY

Summarize the major points covered like coding, Testing and

Implementations, the result reached and the roads ahea

28
 CHAPTER SIX

RECOMMENDATION & CONCLUSION

6.0 INTRODUCTION

Every project conducted under the sun either meets the time, budget or
scope goals, here concluding on future works recommendation is a good
step towards finishing the activity.
6.1 CONCLUSION

Illustrate by concluding bellow strength and weakness.

a. Achievements

Every project has some strengths and weaknesses; so, present here some
of th e strengths and good features of the System will provide to the users
at the time of operations.
b. Limitations

Every project has its own weaknesses so, present here some of the
weakness and limitation features of the System will provide to the users
a t the time of operations.

c. Future Enhancement

Mention the technology of the system to implement and necessary future

development that this system must face eventually

29
6.2 CONCLUDING REMARKS

Enter here the final concluding and recommending remarks as a roundup

for the entire result obtained

6.3 REFERENCES

6.4 APPENDIXES

30