THE MWALIMU NYERERE MEMORIAL ACADEMY

KARUME CAMPUS ZANZIBAR

DEPARTMENT OF LEADERSHIP AND MANAGEMENT SCIENCE

ORDINARY DIPLOMA IN INFORMATION AND COMMUNICATION

TECHNOLOGY (ICT)

Candidate Reg. No.: MNMA/ODZ.ICT/0011/20

Candidate Name: MAKAME, NASRA HUSSEIN

Project Title: ASSIGNMENT MANAGEMENT SYSTEM

2021/2022
 THE MWALIMU NYERERE MEMORIAL ACADEMY

KARUME CAMPUS ZANZIBAR

DEPARTMENT OF LEADERSHIP AND MANAGEMENT SCIENCE

ORDINARY DIPLOMA IN INFORMATION AND COMMUNICATION

TECHNOLOGY (ICT)

Project Code: ITT 06205

Project Name: PROJECT

Candidate Reg. No. : MNMA/ODZ.ICT/0011/20

Candidate Name: MAKAME, NASRA HUSSEIN

Academic Year: 2021/2022

SUBMISSION DATE

………………………
 PROJECT TITLE
Title of the Project:

ASSIGNMENT MANAGEMENT SYSTEM

Project Type:

SOFTWARE PROJECT

Project Category:

WEB DEVELOPMENT
 DECLARATION

I…………………………………………………..declare that the project worked entitled

ASSIGNMENT MANAGEMENT SYSTEM submitted to THE MWALIMU NYERERE

MEMORIAL ACADEMY is a record of an original work done by me under the guidance of

MS. NGOLLO KISHEGENA and this report is submitted in the partial fulfilment of the

required diploma in Information Communication Technology and that it has not been

prepared to any other University or higher learning Institution for a similar or other Diploma

program.

Student Signature: ………………

Date: ………………..

Supervisor Name: MS. NGOLLO KISHEGENA

Supervisor Signature: …………………….

Date: ……………………

i
 ACKNOWLEDGEMENT

First of all, I would like to thank Allah for giving me courage, ability and enabling me to

complete this Project report timely and successfully.

Secondly, I would also like to thank my parents for their support as regard to my studies and

thirdly, I would like to take this opportunity to thank my academic supervisor MS. NGOLLO

KISHEGENA as well as Mr HAFIDH SHAIB AHMADA, Mr Charles Sadalah, Mr

Muhammad and Mr Masoud for supporting me and for their directions and guidance in

accomplishing this project proposal report.

Finally, I would like to thank all the teachers and fellow students in department of

Information and Communication Technology (ICT) for their support and advices.

ii
 ABSTRACT

A good system is needed to manage the submission of student assignments at the University.

The manual system needs to be replaced with the computerized system to give more

convenience to the student and the lecturer. When students hand over their assignment the

operator will keep the records of the submission details. Emails will be sent to the students to

verify their submission. The same goes for the marked and collected assignment. In addition,

the lecturer will be informed to check the submission records of the students. By doing this,

the assignment is always kept in safe condition after the submission. The proposed system

also helps lecturer to keep track of their student submission. The lecturer can check the time

of submission and enable the student to collect their assignment after being marked. This

system will improve the management of student assignment at the Institute.

iii
 TABLE OF CONTENTS

DECLARATION.........................................................................................................................................i
ACKNOWLEDGEMENT............................................................................................................................ii
ABSTRACT.............................................................................................................................................iii
TABLE OF CONTENTS............................................................................................................................iv
LIST OF FIGURES....................................................................................................................................vi
LIST OF TABLES.....................................................................................................................................vii
CHAPTER ONE........................................................................................................................................1
1.1 Introduction...........................................................................................................................1
1.2 Background of the Project.....................................................................................................1
1.3 Problem of the existing system..............................................................................................1
1.4 Proposed System.........................................................................................................................2
1.5 Literature Riview..........................................................................................................................2
CHAPTER TWO.......................................................................................................................................3
2.1 Main objective.............................................................................................................................3
2.2 Specific Objectives.......................................................................................................................3
2.3 Significance of the project...........................................................................................................3
2.4 Limitations of the project............................................................................................................5
2.5 Scope of the project.....................................................................................................................5
CHAPTER THREE....................................................................................................................................6
3.0 Methodology used in system design and implementation..........................................................6
3.1 Project Approach.........................................................................................................................6
CHAPTER FOUR....................................................................................................................................10
4.1 Feasibility Study.........................................................................................................................10
4.2 Data Collection..........................................................................................................................11
4.3 System Analysis.........................................................................................................................13
4.4 Time Frame of the Project.........................................................................................................13
4.4 Project Budget...........................................................................................................................13
CHAPTER FIVE......................................................................................................................................15
4.5 System Design............................................................................................................................15
REFERENCES........................................................................................................................................17

iv
 LIST OF ABBREVIATIONS

AMS Assignment Management System

CSS Cascading Style Sheet
DFD Data Flow Diagram
GB Gigabyte
HOD Head of Department.
HTML Hypertext Markup Language
ICT Information and Communication Technology
MNMA Mwalimu Nyerere Memorial Academy
SDLC System Development Life Cycle.
SQL Structure Query Language
PHP Hypertext Preprocessor
RAM Random Access Memory
UML Unified Modelling Language

v
 LIST OF FIGURES

Figure 1 : Prototyping Model................................................................................................................7

Figure 2 : Questionnaire......................................................................................................................11
Figure 3 : DFD Level 0 diagram..........................................................................................................15
Figure 4 : Entity Relationship Diagram...............................................................................................17
Figure 5: Physical Database Design....................................................................................................18
Figure 6: Registration form.................................................................................................................26
Figure 7: Login form...........................................................................................................................27
Figure 8: Admin dashboard.................................................................................................................27
Figure 9: Admin view the lecture and head of unit information..........................................................28

vi
 LIST OF TABLES.
Table 1: Time frame of project............................................................................................................12
Table 2: Project Budget.......................................................................................................................13
Table 3: Database diagram..................................................................................................................29
Table 4: Assignment Table..................................................................................................................29
Table 5: Course Table..........................................................................................................................29
Table 6: Lecture Table.........................................................................................................................30
Table 7: Program Table.......................................................................................................................30
Table 8: Pro_Course Table..................................................................................................................30
Table 9: Student Table.........................................................................................................................31
Table 10: Unit Table............................................................................................................................31
Table 11: User_log Table....................................................................................................................31

vii
viii
 CHAPTER ONE

1.1 Introduction.

Assignment management is one of the fundamental activities in education. In traditional

assignment management schemes, assignments are recorded on paper, floppy disks, and

emails. They have to be delivered or organized manually. This is inconvenient and

inefficient, and may cause many problems due to material limits and human errors, such

as disordered printouts (without page numbers), damaged floppy disks, etc. Furthermore,

instructors and students usually are unaware of the ongoing academic information, which

can be used to help them find out problems and improve their teaching and learning

qualities. Therefore, it becomes important to implement an assignment management

which can provide both instructors and students with quality educational services.

1.2 Background of the Project.

The present assignment management system uses manual operations in receiving and

submitting the assignment from the lecturers and students respectively. It has been found

that the existing system is cumbersome and time consuming. The student spend a lot of

time and a lot of paperwork. The lecturers fail to keep proper record of the submitted

assignments. The proposed system will be the position to get rid of all these challenges.

1.3 Problem of the existing system.

The Assignment Management System (AMS) presently used, has been found to have the

following problem namely:-

i. Time consuming.

The student have to spend a lot of time to complete their assignment before

submitting them to the lecturers.

ii. A lot of paper works.

1
 The student used a lot of paper for their assignment which is also very costly.

iii. Risk of losing the documents.

There is also a risk of losing the submitted document by lecturers or staff. It is also

inconvenient to handle the Documents properly and sometimes cause poor recording.

1.4 Proposed System.

The proposed assignment management system provides a platform to eradicate the drawbacks

(problems/challenges) of the existing system. In this system, the students will submit their

assignment using computerised system. By doing so the above mentioned drawbacks will be

eradicated (solved) accordingly.

2
 CHAPTER TWO

2.1 Main objective.

To develop an Assignment Management System which is efficient, reliable and user friendly

for both lecturers and students in their day to day activity and to replace the existing system.

2.2 Specific Objectives.

i. The system will have user interface that allow admin to register user.

ii. The system will have user interface that will enable the students to receive the

assignment timely.

iii. The system will have user interface that allow the students to submit their assignment

on time and safely and get to view that it has been received by the lecturers.

iv. The system will have user interface that will enable the lecturers to know whether his

or her students submit their assignment on time and then marking them.

v. The system will have user interface that the student will receive the assignment after

marking.

vi. The system will have user interface that allow a forum to make the interaction

between the lecturers and students.

2.3 Significance of the project.

i. It reduces the use of file and paper. Many processes will be performed online via an

internet.

ii. It is user friendly system as regard to cost, time, efficiency and security.

iii. Information is secured. The information will be secured because the online system

won`t allow unauthorized user to use or access information.

3
 iv. It allows both lecturers and students to easily access the information and use them

accordingly.

2.4 Limitations of the project.

i. Lecturers won’t be notified when assignment is submitted.

ii. The lecturers have the access to receive and mark the assignment even after due time.

iii. The Head of the Unit will be able to view all needed information about the Students

and the Lecturers.

2.5 Scope of the project.

The scope of the project is at the MWALIMU NYERERE MEMORIAL ACADEMY

(MNMA). The Students will submit the assignment using computerized (online) system to

the operator. The operator will pass all of the assignment to the lecturers to be marked. After

marking, the assignment will be passed back to the operator at the system administrator. The

students can collect their Assignments from the operator at the Administrator office (admin).

4
 CHAPTER THREE

3.0 Methodology used in system design and implementation.

The Methodology used in system design was Object-oriented design, is an approach to

systems development that proposes the use of system objects to build new systems and

rebuild old ones. An important goal of object-oriented development is to change the nature of

traditional software development from designing and writing models from scratch to building

systems through the assembly of reusable software objects.

3.1 Project Approach.

In this chapter, the approach taken to accomplish the project is Prototyping Model. The use of

System Development Life Cycle (SDLC) theory is fully considered due to its importance as

regarded to any project.

The model will help collect the requirements from the users (lecturers, students) and prepare

a prototype (sample). The prototype will be reviewed and improved by the users as per their

requirements. After finishing the process, and become satisfied, the next step of starting the

project follows. The updates and changes of the prototype will be also communicated to the

users until to the end of the system itself.

Finally, the system will be accepted by both parties and be ready for use.

5
 Figure 1 : Prototyping Model

3.2 Advantage of Prototyping Model.

i. It enables user to understand very basics product requirements especially in terms of

user interface.

ii. It is easy to detect errors in this design method.

iii. It is easy to find missing functionality.

iv. New requirements can easily be accommodated in the design.

v. It can easily be reused by the developer for more complicated projects in the future.

vi. Quicker user feedback is available leading to better solutions.

6
 CHAPTER FOUR

4.1 Feasibility Study.

Feasibility study can be considered as preliminary investigation that helps the

management take a decision about whether study of system should be feasible for

development or not.

Any proposed system should be studied first in order to define project problem that

leads to the development of new system, also feasibility study will help define the

alternative solution of problem and the recommended solution that will be used in

implementation of new proposed system.

i. Economic feasibility.

The aim of economic feasibility is to investigate whether the system development is

economic viable or not comparing with the existing system. The project has shown

that is economic feasible by the fact that by using this software the students and

lecturers can use it effectively and efficiently and can save a lot of time and money.

This is because the paper work will be avoided which involves cost and need time for

printing the assignment.

So it will concluded that the new system is economic viable.

ii. Technical feasibility.

It assists to understand whether the developed system will use some of technology in

existing system or not. It also gives the real pictures on which Technology to be used.

Technically, the developed system will support the existing one. The project system

will use the software technology for the development including Java script, PHP,

HTML, MySQLi, CSS and bootstrap.

7
 iii. Operational feasibility.

It determines if the operational resources (like human and others) are available to use

the system when it has been installed. The project is obviously can be operational due

to the fact that all the students and lecturers are computer literate in their day to day

activities.

iv. Legal feasibility.

All legal aspects needed, will be considered in order to enable the development

system be functionable.

4.2 Data Collection.

Data collection is the process of gathering and measuring information on targeted variables in

an established system, which then enables one to answer relevant questions and evaluate

outcomes. It is a research component in all study fields, including physical and social

sciences, humanities, and business. Data collection is an important aspect in any project. In

this project, two method of data collection will be used namely:-

i. Interview

It is the process of gathering information by asking questions direct to the selected

people. There will be also direct discussion in terms of interviews between the

targeted users of development system and Interviewer (data collector) aimed at

collecting data. For my side I get the information by forming the interview between

student and lectures.

8
 ii. Questionnaire.

It is the way of collecting information or data by using questions will be prepared

and distributed to different people in order to get their views and suggestions as

regard to the existing system. The targeted people are lecturers and students. The

bellow figure show the example of the closed and open questions

Figure 2 : Questionnaire

4.3 System Analysis

System Analysis used to determine data and requirement for the system which is going to be

developed. System Analysis usually using various method for collecting data or information

about system. Data can be collected through interviews, questionnaires, group discussion that

will help gather requirement and specification of the project from difference people and

representing entity relationship diagram, in this project system used diagram of entity

relationship to present how entities interact with database within system.

9
4.4 Time Frame of the Project

Table 1: Time frame of project

4.4 Project Budget

In accomplishing this project, some cost are incurred. The table bellow shows the breakdown

of the total project budget including transport, bandwidth, printing questioner forms and the

report.

S/N SERVICES COST

1 Transport 5000/=

2 Printing questions paper and the 2000/=

report

3 Bandwidth 25000/=

TOTAL 32,000/=

Table 2: Project Budget

10
 CHAPTER FIVE
5.1 System Design
System design is the process of defining elements of a system like modules, architecture,

components and their interfaces and data for a system based on the specified requirements. In

this system the part of Unified Modelling Language (UML) known as DFD Level 0 will be

used.

5.1.1 DFD Level 0 is (also known as context diagram) designed to be an abstraction view,

showing the system as a single process with its relationship to external entities. It represents

the entire system as a single bubble with input and output data that indicate by incoming/

outgoing arrows.

5.1.2 System users and their descriptions:-

Admin.

Is a super user of the system, he can perform all task in the system like register all users,

view, edit, update, delete user’s information and change role of the users.

Student.

The main features for student users are register, checking information of classes

( r e c e i v e assignments), submitting assignments online and receive back the assignment. A

student can check assignment information and upload assignment files for the courses he/she

is taking. After selecting a course, the student enters the assignment information page. On

this page, all the current assignment information for the selected course is displayed, which

includes assignment name, total points, post-date, due time, assignment files (if exist) and

answer files (if exist). The student can press the Submission Information button to see his/her

own current submission status for the selected assignment, and then upload assignment files.

11
The student can press the Submission Information button to see his/her own current

submission status for the selected assignment, and then upload assignment files. Uploading

page will repeatedly display until the student indicates that all files have been uploaded.

Functions for deleting or replacing uploaded files are provided to let students conveniently

manage submissions. Each time a change is made, the AMS system automatically changes

student’s submission status and shows the student the new submission time, status.

Lecturer.

The main functions of the lecturer as regard to project is to register, assign assignment, then

receive back and mark then report back.

Head of Unit. (HOU).

HOU will be able to view, monitor and supervise all incoming information to their respective

unit accordingly.

12
 Figure 3 : DFD Level 0 diagram
5.2 Database design.

Database is a collection of information organized in such a way that can be access quickly.

The database is usually controlled by a database management system DBMS, along with the

applications that are associated with them, data within the most common types of databases

in operation today is typically modelled in rows and columns in a series of tables to make

processing and data querying efficient. The data can then be easily accessed, managed,

modified, updated, controlled, and organized. Most databases use structured query language

13
(SQL) for writing and processing data. In database design I used E-R (Entity-Relationship)

Diagram that used to represent the relationship between entities in a table. Database design

divided in two categories which are logically design and physical design.

5.2.1 Logical design.

The logical design of a system refers to an abstract representation of the data flows, inputs

and outputs of the system. Logical design involves arranging data into a series

of logical relationships called entities and attributes. An entity represents a chunk of

information. One output of the logical design is a set of entities and attributes corresponding

to fact tables and dimension tables.

It describes the inputs (sources), outputs (destinations), databases (data stores), procedures

(data flows) all in a format that meets the user requirements. Below is a figure that show an

entity relationship diagram of the system.

14
Figure 4 : Entity Relationship Diagram

15
5.2.2 Physical Design.
The physical design relates to the actual input and output processes of the system. This is laid

down in terms of how data is input into a system, how it is verified/authenticated, how it is

processed and how it is displayed as shown in my physical database design. This system has

one database named AMS which has nine table such as assignment, course, program,

pro_course, student, lecture, hou and user_log.

Figure 5: Physical Database Design

16
5.3 Implementation

Implementation is a process of ensuring that the information system is operational. The goal

of the implementation is to translate the design of the system into code in a given

programming language which include the process of coding and testing.

5.3.1 Coding
Coding is a set of word and symbols that enable human to communicate with a computer or is

a set of rules that provides a way of telling a computer what operations to perform.

5.3.1.1 PHP scripting language PHP5 scripting language

<?php

require_once '../../includes/connection.php';

if (isset($_POST['change']))

if (empty($_POST['current']) || empty($_POST['new']) || empty($_POST['confirm']))

header("location:change_userpss.php?EMPTYSPACE=0");

else

$id=$_SESSION['person'];

$crrnt =$_POST['current'];

$new=$_POST['new'];

$confirm=$_POST['confirm'];

$access="select password from user_log where username = '$id'";

$qrt=mysqli_query($con,$access);

$search=mysqli_fetch_assoc($qrt);

if ($search['password'] == $crrnt)

if ($new == $confirm) {

17
 $upd="update user_log set password='$confirm' where username ='$id'";

$qrty=mysqli_query($con,$upd);

if ($qrty)

echo "<script> alert('Succesfully password change'); </script> .

<script>window.location='index.php'</script>";

else

{ header("location:change_userpss.php?WRONG=1");

else

header("location:change_userpss.php?
CONFIRM=0");

else

header("location:change_userpss.php?OLD=1");

else

header("location:change_userpss.php");

?>

18
5.3.1.2 HTML (Hyper Text Markup Language)
<!doctype html>

<html lang="en">

<head>

<title> AMS | Admin </title>

<meta charset="utf-8">

<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

<meta name="viewport" content="width=device-width, initial-scale=1.0, ">

<link rel="stylesheet" href="../../assets/vendor/bootstrap/css/bootstrap.min.css">

<link rel="stylesheet" href="../../assets/vendor/font-awesome/css/font-awesome.min.css">

<link rel="stylesheet" href="../../assets/vendor/linearicons/style.css">

<link rel="stylesheet" href="../../assets/vendor/chartist/css/chartist-custom.css">

<link rel="stylesheet" href="../../assets/css/main.css">

<link rel="stylesheet" href="../../assets/css/demo.css">

<link rel="stylesheet" href="../../assets/css/style.css">

</head>

<body>

<div id="wrapper">

<div class="main">

<div class="main-content">

<div class="container-fluid">

<div class="panel panel-headline ">

<div class="panel-body">

<div class="row">

<div class="col-md-3">

19
 <div class="metric">

<span class="title">head of unit</span>

</div>

</div>

<div class="col-md-3">

<div class="metric">

<span

class="icon"><a href="selected_student.php" class=""><i class="fa

fa-odnoklassniki"></i></a></span>

class="title">Students</span>

</p>

</div>

</div>

<div class="col-md-3">

<div class="metric">

<i class="fa fa-users"></i></a></span>

<p>

<span class="number"> </span>

<span class="title">Lecturers</span>

</p>

</div>

</div>

</div>

</div>

20
 </div>

</div>

</div>

</div>

<div class="clearfix"></div>

<footer>

<div class="container-fluid">

<p class="copyright">Copy right &copy;

</p>

</div>

</footer>

</div>

</body>

</html>

5.3.1.3 CSS (Cascading Style Sheets)

.nav-style-1{

font-family: times new roman;

.lb-style-st-1 {

font-size: 20px;

font-family: Times new roman;

.demo-button button {

21
 margin-bottom: 5px; }

.demo-icons li {

margin-bottom: 50px;

text-align: center; }

.demo-icons .cssclass {

display: block;

margin-top: 5px;

margin-left: 5px; }

5.3.1.4 Java Script

Java Script is a dynamic computer programming language. It is most commonly used as part

of web browsers, whose implementations allow client-side scripts to interact with the user,

control the browser, communicate asynchronously, and alter the document content that is

displayed.

Java script is used to create popup windows displaying different alerts in the system like

“User registered successfully”,” username or password is invalid”.

Java Script

<script src="../../assets/vendor/jquery/jquery.min.js"></script>

<script src="../../assets/vendor/bootstrap/js/bootstrap.min.js"></script>

<script src="../../assets/vendor/jquery-slimscroll/jquery.slimscroll.min.js"></script>

<script src="../../assets/vendor/jquery.easy-pie-chart/jquery.easypiechart.min.js"></script>

<script src="../../assets/dataTables/jquery.min.js"></script>

<script src="../../assets/dataTables/jquery.dataTables.min.js"></script>

22
<script src="../../assets/dataTables/dataTables.bootstrap.min.js"></script>

<script src="../../assets/dataTables/dataTables.responsive.js"></script>

<script src="../../assets/dataTables/bootstrap.min.js"></script>

<script>

$(document).ready(function() {

$('#dataTables-example').DataTable({

responsive: true

});

});

</script>

5.3.2 Interface

System interface is referring to the part of system where end user interacts with a system, this

is among the most essential parts of the system because it’s what the users see and interact

with it.

5.3.2.1 Registration Form

The first part is registration form where all users including students and lecturers should have

providing essential details in order to register in the system such as first name, second name,

last name, registration number, unit name, gender and phone number, the following are the

sample of Lectures Registration form:-

23
 Figure 6: Registration form

5.3.2.2 Login Form

This is the interface that allow authorized user to enter within a system by using user name

and password as figure shown bellow

24
 Figure 7: Login form

5.3.2.3 Main Dashboard for admin

This is a user-interface where admin login, manage all user in the system and user’s

information.

Figure 8: Admin dashboard

25
5.3.2.4 Admin view the lecture and head of unit information

Figure 9: Admin view the lecture and head of unit information

5.3.3 Testing
Evaluation of the software against requirements gathered from users and system

specifications. Testing conducted at the phase level in software development life cycle or at

module level in program code. Software testing comprises of Validation and Verification.

5.3.3.1 Validation and Verification.

Figure 10: Update system testing

26
5.3.4 Database table

Table 3: Database diagram

Table 4: Assignment Table

Table 5: Course Table

27
 Table 6: Lecture Table

Table 7: Program Table

Table 8: Pro_Course Table

28
 Table 9: Student Table

Table 10: Unit Table

Table 11: User_log Table

5.4 System Requirement Specifications

System specification describes the operational and performance requirements of a system,

such as a computer hardware and software specifications. It helps to define the operational

and performance guidelines for a system. It may outline how the system is expected to

perform and what that may include.

29
5.4.1 Hardware specifications

 Processor due core

 RAM at least 2GB

 Hard disk drive at least 160GB

5.4.2 Software specifications

 Window 7 for running information system

 Xampp sever for hosting MSQL sever and Apache sever

 Sublime text 3 for coding

 Visual Studio for coding

30
 CHAPTER SIX
6.1 Recommendation

6.1.1 Recommendations to Mwalimu Nyerere Memorial Academy

Develop and design project is not simple work so as academy should increase teaching

practice in different programming language that can help student to develop advance

information system.

6.1.2 Recommendations to student.

For students who design and develop information system should find their system

requirement and start early to develop their information system as faster as possible because

when they finish early it will help and get much time for testing and correction errors on their

information system and finish their project book earlier too.

31
REFERENCES

Arcisphere technologies (2012) December2016. The Software Development Life Cycle.

B. Henderson-Sellers; C. Gonzalez-Perez (2006). Uses and Abuses of the Stereotype

Mechanism in UML and Model Driven Engineering Languages and Systems.

Buchanan, Da. A., and Huczynski, A. A. (2013). Organizational Behavior Harlow Pearson

Education Limited.

Jean Wilson Murray (2008). The Complete Guide to Writing Effective and Award Winning

Business Proposals: Step-by-step Instructions. Atlantic Publishing Company

John Hunt (2000). The Unified Process for Practitioners: Object-oriented Design, UML and

PHP.

Iman Poernomo (2006) The Meta-Object Facility Typed and Proceedings of symposium on

applied computing

Manuel, Luis. (2007). Describing Use Case Relationships with Sequence Diagrams.

Mr. R. J. laird (2008) .Interactive Web based Placement Management Principles and

Practice.

December, (2013). An Interactive Online Training Placement System, International Journal of

Advanced Research in Computer.

32