DEBRE TABOR UNIVERSITY

DEPARTMENT OF INFORMATION TECHNOLOGY

TITLE OF:- INTERNSHIP MANAGEMNET SYSTEM

Host ORGANIZATION:- SOUTH SCIENCE AND INFORMATION

TECHNOLOGY BUREAU

NAME ID

Teshager Wosale 0784

1
Acknowledgement

I would like to thank almighty God for giving us strength and health to complete this project.
I also grateful to the company supervisor he has helped by giving direction and supportive ideas
for us.
Finally, I like to thanks our directors who gives detail information of the existing system
and background of the organization

declaration
I am third-year Information technology student at DEBRE TABOR University. I also received
practical training at the HAWASSA Science and Information technology bureau. I would like to
declare my working tasks within the company and all the tasks that I had done from this
internship projects. This projects focuses on the work I have seen and done during my time in
the organization. The practical training will be conducted from July 10 to August 30,2014E.C
with the help of the company’s supervisor Mr’s Asamamaw
I made this projects based on instructions from our university department office. and I have
included all necessary points.

Student Name signature

Teshager Wosale _______________

Approved by
Monitor name signature
Mr Habtamu _______________

TABLE CONTENTS

2
 Chapter one..................................................................................................................................5
Introduction..................................................................................................................................5
1.1 BACKGROUND OF ORGANIZATION..............................................................................5
1.2 Problem of the statement:-.....................................................................................................6
1.3 General objectives of the internship.......................................................................................6
1.4 The specific Objectives of internship:-..................................................................................7
1.5 Significance of the projects....................................................................................................7
1.6 Scope of the project................................................................................................................8
1.7 Work Breakdown structure and schedule..............................................................................8
1.8 Methodology..........................................................................................................................9
1.8.1 SYSTEM DEVELOPMENT MODEL:-.............................................................................9
1.8.2 Data Gathering Techniques:-..............................................................................................9
1.8.3 COST ANALYSIS............................................................................................................10
1.9 Software requirement and programing language.................................................................10
Hardware requirements............................................................................................................10
Chapter two Existing system......................................................................................................11
2.0 The advantage/strength of existing system are:-..................................................................11
2.1 Main disadvantages/weakness of existing system are:-.......................................................11
2.2 Proposed system...................................................................................................................11
2.3 Basic rule identification of the organization........................................................................12
Chapter three..............................................................................................................................12
System requirement....................................................................................................................12
3.1 Functional requirements.......................................................................................................12
3.2 Nonfunctional requirement..................................................................................................13
CHAPTER FOUR......................................................................................................................14
SYSTEM MODEL.....................................................................................................................14
4.1USECASE.................................................................................................................................14
4.1.11 Actors:-...............................................................................................................................15
4.1.12Use case identification.........................................................................................................15
Use case description of create account......................................................................................16
Table4.1 description of create account...................................................................................17
Use case description of login.....................................................................................................17

3
 Use case description of Update account....................................................................................17
Use case description of delete account......................................................................................18
Use case description of logout...................................................................................................19
Use case description of edit student result.................................................................................20
4.2 Sequence diagram................................................................................................................21
4.2.11 Sequence diagram of create account...................................................................................22
4.2.12 Sequence diagram of Login................................................................................................23
4.2.13 Sequence diagram of Delete account..................................................................................23
4.2.14 Sequence diagram of logout...............................................................................................25
4.2.15 Sequence diagram of view report.......................................................................................26
4.2.16 Sequence diagram of edit information................................................................................27
4.2.17 Sequence diagram of send report........................................................................................28
4.3 ACTIVITY DIAGRAM.......................................................................................................29
Activity diagram of create account................................................................................................29
Activity diagram of Login.............................................................................................................30
Activity diagram of logout.............................................................................................................31
Activity diagram of delete account................................................................................................31
Activity diagram of send report.....................................................................................................33
Activity diagram of edit information.............................................................................................34
4.4 CLASS DIAGRAM.............................................................................................................34
4.5 Deployment diagram............................................................................................................36
chapter five ……………………………………………………………………………………36
5.0 Database designing model and interface..............................................................................36
5.1.1 conceptual model..............................................................................................................36
5.1.2 Logical model………………………………………………………………………….37
5.1.3 physical model……………………………………………………………………………..38
5.2 Entity relationship (ER) model………………………………………………………..….39
5.3 Normalization……………………………………………………………………………..40
UN NORMALIZE TABLE…………………………………………………………………….40
First normal form (1st NF)..........................................................................................................41
Second normal form (2ND NF)....................................................................................................42
Third normal form (3rd NF)........................................................................................................43

4
 Chapter six.................................................................................................................................46
Conclusion.................................................................................................................................46
recommendation………………………………………………………………………………46

Chapter one

Introduction

Internships are the way to explore or expand the related knowledge and skills required in a real
world situation and experience to enter into a particular career field. It is basically for
undergraduate student, or a trainee, this not only for gaining experience, but also expose them to
fine if they totally interest in the field.

An internship is a period of training carried out by a student within a company or organization.

Basically, the objective of internship program is to expose students to the real world of work and
in the process, provide feedback to institutions on the relevance or otherwise of the curriculum.
Internship is a structured educational approach which integrates class room learning with
productive, structured work experience(s) that are directly related to the goals and objectives of
the technology education programs in Ethiopia.
In order to integrate on-the-job practical field experience with academic studies, internship
programs offer students a chance to extend the classroom into a workplace setting.
Moreover, internship programs is also an to the employer to consider students as prospective
employee and evaluate their skills such as communication, quantitative analysis, information
technology, problem-solving and ability to work with other people

1.1 BACKGROUND OF ORGANIZATION

The Southern Nations, Nationalities and People's Region (SNNPR) government has recognized
the need to examine the organization, power and function of the executive bodies in order to
make the country's transformation effective, sustainable and institutional, and to fulfill its
regional mission in line with our current level of development.

5
 The Regional Council on 08/02/2012 approved the merger of two institutions, the Science and
Technology Development Institute and the Communication Information Technology Agency,
called the Science and Information Technology Bureau. It is known that the revised SNNPR
Government Proclamation No. 180/2012 was approved by the conference.

The Science and Information Technology Bureau's five-year development plan will be
implemented by the objectives and public directorates of the Science and Information
Technology Bureau at all levels during the strategic planning period 2013-2017.

The plan document includes a strategic focus area, strategic goals, metrics, targets and strategic
measures, a data collection system, a monitoring and evaluation system.
By developing, implementing and broadening science and information technologies that are
significant for social and economic development to the society, developing nationally
competitive and sophisticated system.
In 2030, to witness successful science and information technologies with fast learning,
development and utilization of scientific information technologies in the region.

1.2 Problem of the statement:-

The manual creation of various reports not only makes the process time consuming,
but also is wastage of human resource e ff ort that would have been used to perform
other tasks.
When applying to the internship, students need to complete the registratio n process.
This process needs to be done manually, which means students need to fill and
complete it by write it in a documen t.

After receiving an accordance letter from the company, students need to inform the
faculty internship coordinator for approving.
While a student undergoing the training, they need to document what they are
doing every day in a report. Other than that, student performance also had to be
marked by the company supervisor every week. The mark will be given in the final
work to nurture and evaluate their prospect/potential employee at a minimum cost and risk.

1.3 General objectives of the internship

we aim to develop a web based application of an internship management system that works by
allowing the university to deploy a web portal, to collect users data, review that data, make a
decision, and then continue to interact with users and reviewers. The goal of the system is to
enable online interaction with applicants and their supervisors and automate the entire process;
thereby eliminating a huge amount of paperwork and manual task.

6
1.4 The specific Objectives of internship:-

To assure a certain awareness and openness of the students to the professional world, particularly
to the societal, ethical and human aspects.
To help students develop analytical, research, as well as organizational and
presentation skills applied to the corporate world.
 To become acquainted with organizations and organizational structures.
 To be able to acquire some basic professional reflexes and relational skills and understand their
future role within the organization.
 To apply a combination of knowledge, capacities and attitudes learnt along the technology
curriculum to a real professional situation
 Ability to design and implement engineering and technology tools and techniques
 Ability to undertake research and to progress to higher levels of studies
Moreover, to fulfil employer’s requirements, universities with engineering and technology
undergraduate programs have been using internships as a means of providing their students with
practical skills/experiences and preparing them for their future careers.
On the other hand, hosting organizations will also get the opportunity

1.5 Significance of the projects

. Internships are a great way for students to test their skills in real-life situations, explore career
options and gain an insight into a company or organization.
. Internships also allow interns to make contacts with managers and recruiters, which
Can later be used to negotiate full-time employment.
Taking an internship can also significantly increase your chances of getting a full-
time graduate job.
To evaluate the benefit gained by the host organization involved in the internship
program.
To address the feedback of involving employee and identify key influence factors
on the intern performance.
. Internships not only help you in developing professionalism but also enhance self-growth. You
certainly develop various characteristics like integrity, commitment, and self-motivation.

7
. Pursuing an internship, you will get to work on a wide range of tasks that will boost your
managerial skills, and working in a team, you can polish your interpersonal and communication
skills while learning about the importance of teamwork.
An internship gives you the significant practical experience required and how you can apply the
knowledge you have attained in your degree program to real-life situations. alongside academic
qualifications.

1.6 Scope of the project

The system boundary including functions like:

.Manages student's and supervisor's activity
.The system provides sharing of information among the actors digitally in real-time
.Allocate Resources such as the number of students with supervisors

Limitations of the project

As any digital systems it depends on internet and electric power supply
.The system doesn't provide information about the working behavior of the organization

1.7 Work Breakdown structure and schedule

TASKS START DATE END DATE DURATION

proposal 10/11/2014 25/11/2014 Two week

System requirement 26/11/2014 05/12/2014 One week

specification
System designing 06/12/2014 13/12/2014 One week

implementation 28/12/2014 Two week

14/12/2014
Testing 29/12/2014 4/13/2014
One week
Table 1.1 work breakdown structure and schedule

Object oriented approaches

The object-oriented approach is a development strategy based on the concept that
systems should be built from a collection of reusable parts called objects

8
In developing this system we follow an object oriented approach.
Using Object Oriented approach enables us to develop system in iterative way. That means we
can restart our system development in some cases like require

1.8 Methodology

To perform this project our system requirement will follow methods, models and development of
software life cycle techniques.

1.8.1 SYSTEM DEVELOPMENT MODEL:-

Iterative model

Advantages
<>It is more cost effective to change the scope or requirements in Iterative model.
<>Parallel development can be planned.
<>Testing and debugging during smaller iteration is easy.
<>Risks are identified and resolved during iteration; and each iteration is an easily managed.
<>In iterative model less time is spent on documenting and more time is given for designing.

<>It is efficiently versatile to the forever changeable requirements of the project as well as the
users.
<> in the iterative model, the process of iterative begins with a simplistic execution of a little
collection of the software requisite, which iteratively improves the developing variants until the
whole system is executed and prepared to be redistributed.

Disadvantages
<> each phase of an iteration is rigid with no overlaps.
<> Also, system architecture or design issues may arise because not all requirements are
gathered in the beginning of the entire life cycle.

1.8.2 Data Gathering Techniques:-

Questionnaires
We have interviewed the organization supervisor and director
What are the roles of zerif and the directors concerning about the internship
What are their function
How to accept student request for the internship

9
What are the basic rule of the organization
How look like the existing system with internship etc..

1.8.3 COST ANALYSIS

Item name Quantity Unit birr

pen 2 30

Paper 5 10

transport 30 days 800

Copy paper 8 24

total 864

Table1.2 cost analysis

1.9 Software requirement and programing language

MS- word

Sublime Text
Google Chrome browser
ZAMPP
EDRAW Max
HTML
CSS
PHP
Java Script
MYSQL

Hardware requirements
Flash
/Computer
Hard disk
Keyboard

10
Chapter two Existing system

2.0 The advantage/strength of existing system are:-

<>Manual data entry provides the advantages of ensuring the quality of data entered in to a
system has high level of integrity.
<>Manual data entry is capable of being more accurate than automated data entry because of the
level of care in handling specific tasks.

<> manual system helps for every internship student who want to request the organization for
internship he/she understand about working system of the organization and structure in
psychological as well as in practical.

2.1 Main disadvantages/weakness of existing system are:-

<> Student internship request could be lost because its manual form.
<> The system have not security to protect user’s information.
<> The system could take long time to respond responses
<> The manual creation of each student’s internship offer letter using Microsoft Word is
a real waste of time and human resource effort.

<> Wastage of resource like time, human power.

<> It does difficult to erase and edit the forms.
<> It is not reliable and efficient service for users.
<> It is difficult to request and accept responses concerning about human effort
<> The information transaction is very late to the users

2.2 Proposed system

<> The new system will run on any platform efficiently.

<> With the new system, user will be able to apply and check the status of their application.

<>Changes made to data cannot easily be seen by other staffs in the same unit and as far as
security is concerned, there is the tendency that people without the right grant or permission
cannot easily gain or access to the stored data.

<>The new system will offer the possibility to generate this letter automatically. There is a lack
of data independence and efficient access to the current system.

11
<> The new system will employ a unified database, making it easy for changes to be seen by
everyone. Also, security will be enforced by granting each user a username and password.
<> The new system will offer the possibility to track human errors. Also, many aspects will be
automated human error is reduced. The fact that the existing system is not web-based, it is
impossible to manage on

2.3 Basic rule identification of the organization

every internship student should be attend their practice.

all employees should be being on time to the organization.
every internship student first should ask the organization to be allowed.
every employees and internship student should not use drug in the organization.

Chapter three

System requirement

3.1 Functional requirements

A functional requirement relates directly to a process the system has to perform as a part of
supporting a user task and/or information it needs to provide as the user is performing a task. a
requirement is a statement of what the system must do.
Functional requirement of our system are the following :-
The system should allow admin to add departments and stream
The system should allow director to manage company supervisor and student
<>The system should allow director to add loads
<>The system should allow director to add supervisor
<>The system should allow admin to create account
<>The system should allow admin to edit account
<>The system should allow admin to delete account
<>The system should allow student to send weekly report

12
<>The system should allow student to send monthly report
<>The system should allow student to send final project
<>The system should allow ZERIF to manage director & department
<>The system should allow ZERIF / manager approve requests
<>The system should allow company supervisor to view student report
<>The system should allow DEPT head to send student lists with their supervisor
<>The system should allow admin to manage the all users.

3.2 Nonfunctional requirement

• The quality attributes, design, and implementation constraints, and external interfaces which a
product must have. includes important behavioral properties that the system must have.

Non-functional requirements are requirement, which has no essential for the system, but it can
support and give more quality for the system.
Users interface requirement
-User interface should be menu driven and attractive.

-In the proposed system e going to develop an easy to use user

interface.

-The system should support error-handling mechanism that display

alert message and the system guide the user what will be the next action.

Security requirement:-
-The system support user name and password to authenticate.

-The system should give different privilege to protect interfering.

-The system administration must grant and revoke privilege of the user
. Performance requirement:-
The information is refreshed at regular intervals depending upon whether some updates have
occurred or not.
The system shall respond to the member within few seconds from the time of the request
submittal. The system shall be allowed to take more time when doing large processing jobs.

13
. Accessibility requirement:-
system can be accessed from anywhere
when a user want to use the system in anywhere its allowed

Accuracy requirement:- The system should accurately provide real time information taking
into consideration various concurrency issues.
Binary compatibility:-
The system is accessible for many computers.

Flexibility:- the system intends to increase or the functionality after its deployment.
Efficiency:- the system utilizes resources and takes less time to perform activities and mean
time to repair.
.
Maintainability and Portability:- Changes (addition of information, password changes, and
database changes) must be verified. The system should provide automatically notification to
users

CHAPTER FOUR

SYSTEM MODEL

4.1USECASE
Definition
Use cases are a way to capture system functionality and requirements in UML. Use case
diagrams consist of the named pieces of functionality (use cases), the persons or things invoking
the functionality (actors), and possibly the elements responsible for implementing the use cases
(subjects).

4.1.11 Actors:-
  <>Students.
 <>Company Supervisors.
<> Department head

14
<>ZERIF
<>Director
<>System administrators

4.1.12Use case identification

Send stud result

Manage request

Manage supervisor

Manage directors

Approve request

View result

Send weekly report

Send monthly report

Send final report

Edit student result

Delete student result

Send student list

Create account

Log in

Log out

Edit account

15
Use case description of create account

Use case Create account

Actor administrator
Description This use case helps administrator to create
account
Precondition Web based internship application must exist
Post condition Account will be created
Basic course of action Actor action:-
1: this use case starts when admin clicks on create
account on web page.
3: admin choose account type.
5: admin fills information and clicks create.
8: admin inserts the confirmation code. 10: use
case end

System response:-
2: the system displays choose account type option
page.
4: the system displays form of chosen account.
6: system validates user.
7: the system sends confirmation code.
9: the system stores account on account table

Alternative course of action 6.1: the system displays “the account cannot be
created” if the administrator account was created
before.
6.2: the system displays “the account cannot be
created” if user is not member.
6.3: the system displays “fill all profile spaces “if
admin left some spaces empty.
6.4: the system displays the message “insert valid
password” if admin inserts password less or
greater than six characters length
Table4.1 description of create account

16
Use case description of login

Use case login

Actor user
Description This use case allows the user to log in to the
system
Precondition The login form is displayed on the screen
Post condition The user logged in to the system and select
tasks
Basic course of action
Actors action:-

1: this use case is initiated when clicks login

button on web page.
3: user inserts name and password.
4: user clicks ok.
7: use case end

System response:-
2: system displays log in page.
5: system validates log in against account
table in the database.
6: system displays personal home page to the
user.
Alternative course of action 5.1: If the User name and password is not
valid, send a notification to the user to reenter
user name and password.
Table 4.2 description of login

Use case description of Update account

Use case Update account

Actor Admin
Description This use case allows administrator to update
account
Precondition The administrator must login
Post condition account is updated
Basic course of action
Actor action:-

17
 1: administrator clicks update button on home
page.
3: administrator inserts username and
password then click ok.
6: administrator update account and clicks
ok. 8:use case end

System response:-

2:system displays update page

4: system verifies information.
5: system searches username and password
and returns update page.
7: system store updated account on account
table

Alternative course of action 4.1:system displays “insert correct book name

and code” if administrator did not write
correct when the password have take a limited
number of characters
Table 4.3 description of update account

Use case description of delete account

Use case Delete account

Actor admin
Description This use case allows administrator to delete
Precondition The system verifies administrator
Post condition The account will be removed
Basic course of action Actor action :-
1: administrator clicks remove account button
on home page.
3: the administrator inserts information and
clicks ok.
6: the administrator clicks remove button on
account page.
8:use case
System Response:-
2: system displays search engine.
4: system verifies information.
5: system searches account from account table
and return account on account page.

18
 7: system removes account from account table
and displays “removed”.
Alternative course of action 4.1: system displays “insert correct
information” if administrator inserts incorrect
information
Table 4.4 description of delete account

Use case description of logout

Use case Logout

Actor user
Description Help users to leave the page
Precondition User must be logged in
Post condition User logout of the system
Basic course of action Actor action
1: this use case starts when user clicks log out
button on current page.
3:use case end

System response
2: system returns back to log in screen
Table 4.5 description of logout

Use case description of edit student result

19
Use case Edit student result
Actor Supervisor
Description The use case is used to edit student result
Precondition The supervisor must login
Post condition Some student result is edited
Basic course of action
Actor action
1: supervisor clicks edit stud result button on
main page.
3: supervisor selects student result he want to
edit.

5: supervisor edits student result and click ok.

7: use case ends

System response

2: system displays edit page.

4: system searches existing student result
from result table and return to supervisor.
6: system stores edited student result on result
table

20
4.2 Sequence diagram

It shows the participating objects by their lifelines and the interactions among those objects
arranged in time sequence by the messages they exchange with one another.
To describe the message flow in the system.
Objects communicate by sending and receiving messages.

21
4.2.11 Sequence diagram of create account

22
4.2.12 Sequence diagram of Login

4.2.13 Sequence diagram of Delete account

23
24
4.2.14 Sequence diagram of logout

25
4.2.15 Sequence diagram of view report

26
4.2.16 Sequence diagram of edit information

27
4.2.17 Sequence diagram of send report

28
4.3 ACTIVITY DIAGRAM

show how various events are coordinated.

Represents the flow of control or data step by step occurring in computation.

Activity diagram of create account

29
Activity diagram of Login

30
 Activity diagram of logout

Activity diagram of delete account

31
32
Activity diagram of send report

33
Activity diagram of edit information

4.4 CLASS DIAGRAM

34
35
4.5 Deployment diagram

36
Chapter five

5.0 Database designing model and interface

5.1.1conceptual model

37
5.1.2 Logical model

38
5.1.3 Physical model

39
5.2 Entity relationship (ER) model

ER model have played a central role in systems specification, analysis and development. It is
clear that the physical objects from the precious section: the student, department, supervisor etc.,
correspond to entities in the Entity Relationship model, and the operations to be done on those
entities. however, a good design will minimize redundancy and attempt to store all the
information in as small a space as possible. after some consideration, we have decided

40
5.3 Normalization

UN NORMALIZED TABLE
A table that contains one or more repeating groups.
A repeating groups a group of fields that holds multiple values for a single occurrence of a field.

STUDENT TABLE
id name age sex address department password Phone no
0223 teshager 21 M DTU IT 2014 0986745930
0910264132
1207 Haile 24 M AAU CS 3012
0916606699
0786 mihret 28 F AMU SE 5697 0941504893
0954440365

1766 meron 22 F HWU ME 7699 0916902220

0902673048
0907778400
0786 mihret 28 M AMU SE 0941504893
0954440365
0677 Mekides 26 F MU IS 0966642433

1207 Haile 24 M AAU CS 0916606699

1766 meron 22 F HWU ME 0916902220

0902673048
0907778400

First normal form (1st NF)

No repeating value in a group

No repeating groups

id Name phone

41
 0223 Teshager 0986745930
0223 Teshager 0910264132
0786 Mhiret 0941504893
0786 Mhiret 0954440365
1207 haile 0916606699
1766 Meron 0916902220
1766 Meron 0902673048
1766 Meron 0907778400
0677 mekides 0966642433

Second normal form (2ND NF)

Any none key field should entirely depend on its primary key
Should be in 1st NF
No partial dependency

id name department
0223 teshager IT
1207 Haile CS
0786 mihret SE

1766 meron ME

0786 mihret SE

0677 Mekides IS

1207 Haile CS

1766 meron ME

Third normal form (3rd NF)

Any none key depends on another non key fields

Should be in 1st NF and 2nd NF

42
No transitive dependency

By;\ name department

DTU teshager IT
AAU Haile CS
AMU mihret SE
HWU meron ME

AMU mihret SE

MU Mekides IS

AAU haile cs
HWU meron ME

Account table

id Full name username Password Account email

type
1 Henok Heni Ha1234 admin [email protected]
abera
2 Teshager teshe T3@9967 director [email protected]
wosale
3 Andualem andu Ad@#123 supervisor [email protected]
abebe
4 drakeman Papa department [email protected]
Drake
maki
5 papiyas 12ter student [email protected]
Papi smoke
6 Athlete Atwaree123 Zeriff [email protected]
Abebe 4
bikla

First normal form (1st NF)

No repeating value in a group

No repeating groups

id Full name username Password Account email

type
1 Henok Heni Ha1234 admin [email protected]
abera
43
 2 Teshager teshe T3@9967 director [email protected]
wosale
3 Andualem andu Ad@#123 supervisor [email protected]
abebe
1 Henok Heni Ha1234 admin [email protected]
abera
4 drakeman Papa department [email protected]
Drake
maki
5 papiyas 12ter student [email protected]
Papi smoke
3 Andualem andu Ad@#123 supervisor [email protected]
abebe
6 Athlete Atwaree123 Zeriff [email protected]
Abebe 4
bikla

Second normal form (2nd NF)

<> Any none key field should entirely depend on its primary key
<> Should be in 1st NF
<> No partial dependency
id Full name Username Account
type
1 Henok Heni Admin
abera
2 Teshager Teshe Director
wosale
3 Andualem Andu supervisor
abebe
1 Henok Heni Admin
abera
4 Drakeman department
Drake
maki
5 Papiyas Student
Papi smoke
3 Andualem Andu supervisor
abebe
6 Athlete Zeriff
Abebe
bikla
44
Third normal form (3rd NF)

<>Any none key depends on another non key fields

<> Should be in 1st NF and 2nd NF
<> No transitive dependency
Account Full name email
type
admin Henok [email protected]
abera
director Teshager [email protected]
wosale
supervisor Andualem [email protected]
abebe
admin Henok [email protected]
abera
departmen [email protected]
t Drake
maki
student [email protected]
Papi
smoke
supervisor Andualem [email protected]
abebe
Zeriff [email protected]
Abebe
bikla

Chapter six

Conclusion

45
An effort has been made to study as partial fulfillment of internship problem. In doing the study
the we have tried to follow HTML, PHP, Java script and MySQL methodology. Since the
success and failure of any system depends on gathering the right information through different
fact-finding techniques and user involvements, we have made the best effort to gather
requirements.
After a detail review and study of the existing system have been designed to reflect the new
system that is suppose to solve problems. In order to solve different problems existed, we have to
propose a solution that at least reduce the existed problems and model the proposed system using
different tools and methodologies.
This system is a web based application to serve students as well as the working group of the
system in different direction. Specially:-
1) Students now made possible to access the system in easy ways which overcomes extra
expenditure of student’s time and resource
2) this system has very advantage in order to minimize workload.
I believe that different tools have helped us a lot in capturing real user requirements and model
the right system for the users for their day to day transactions. Thus it should have the
precedence in know-how experience collecting, processing and utilizing information.

Recommendation

While doing this system the I have faced different challenges. So now I recommend to the
company supervisor that for the students, it has to provide them with better service than the
present in better hard ware, guaranteed software’s, giving orientations how to proceed, offering
guest to provide them with more experienced work, support morally, manually, forming good
relation with students, giving students description of each phases and so on. So that it will get
what it expects from its students and satisfy with them.

46