1.

Introduction

1.1 Background
SOS children village established after world second war by professor doctor Herman Gmeiner.
He lived (1919-1986). He was an Australian and he is also an orphan. First he established this
village to help children who lose their parent by the war. After a year he established school for
these children. The unique thing of SOS children village is it is not only help children it also
teach children who are orphan and poor parent children, without payment. This institute do the
other thing is collect wives they lose their husband by war or by different reason and give
mothers trailing and they help the children like mother.

SOS children village has one hundred thirty two branches around in the world. In Ethiopia
established this village and the school in 1966 E.c. at that time in our country there was a big
drought. This institute starts the fires work by help people who hurt by drought. Generally now
days in Ethiopia SOS have seven branches. Mekele, Harar, Addis Abeba, Hawassa, Bahrdar
Gode and lastly open in Jimma.

SOS Children decided to build an SOS Children's Village in Hawassa, after a severe drought
took many lives in the mid 1980s. The SOS Primary and Secondary School at Hawassa has
around 1,000 students, approximately 150 of whom are from the SOS village. The school is
established with:

Vision-every child belongs to a family and grows with love, respect and security.

Mission-we build families for children need, we help them shape their own futures and we share
in the development of their communities.

1.2 Statement of problem

SOS has not had adequate space and room to store all files and records of student. And also
accuracy, reliability, redundancy and efficiency problem that face because of file based system.
The most noticeable problems are:

 Students cannot get information about their school from their home they should
contact the school physically for registration, see their result.
1
  Searching student file is difficult
One has to look through all file to get a single student file.
 Student files can be lost or canceled by some one because files are found on the
shelf and on tables of the office they have a chance to be lost or canceled or
modified.
 Student progress is not well recorded and not consistent Its difficult to know the
progress of the student for both parents and the school as the records are not well
organized and not consistently recorded
 Parent cannot follow up their student status from their home. They should go to
school if wanted.
 Teachers submit students mark to class room teacher in file based system,
This may be unreliable and takes time.

1.3 Scope and limitation

Scope of the project

SOS school has various tasks to be accomplished rather than academic. Most of these tasks
are practiced using manual processing system. But manual processing has its own
problems, so the school requires an automated system to perform their task efficiently. Due
to some constraints like time and budget the system that I have limited the scope of my
project to the following tasks:

- Provide Some Basic Information About The School Like Mission, Vision,

- Contact Information

- Search The Student File From The Database

- Support Online Registration, Display Student Results.

- Announce The Academic Calendar And Different Notice.

- Generate Student Status Report.

- Give Comment, Read Comment About Student Status.

Limitation of the project

The tasks mentioned above to be done are limited to secondary and preparatory
school students. Primary and elementary school student information doesn’t include.
the system does nothing to do with other employee of the school and other tasks the
school accomplish.

2
2. Requirements
2.1 Functional requirements
The functional requirement for the system describes the functionally or services that the system
is expected to provide. Functional requirement for a software system may be expressed in a
number of different student information management systems. These are as follow

 The new system will have login password & username to enter the system
for both the administrator and other users in different way.
 The new system will search the student file from the database.
 The new system will add data from different user of the system to the DB
 The new system will support student registration, display student results.
 The new system will announce the academic calendar and different notice.
 The new system will generate student status report.

2.2 Non-functional requirements

Many non functional requirements relate to the system as a whole rather than individual system
features.

Efficient
 Searching a student history should not take more time
 The system displays every window.
 The system should be user friendly.
 The system should operate as efficiently as possible.

Control (security)
 Each user will have its own user ID and password.
 Central server will be placed in the administrator office secured with key, user name
and password.

Service
 Users of this system are parent, registrar staff, teachers and the administrator.

3
Maintenance
 The system should be easy to maintain and update.

2.3 Hardware and Software requirement

Basic requirement in this project used hardware and soft ware requirements. Both of
them are stated below:

2.3.1 Hardware requirement

 Personal computer
 NIC and necessary expansion slots.
 Printer

2.3.2 Software requirement

 Window XP
 Macromedia dream weaver
 Web browsers: Internet explorer and Mozilla Firefox
 Wamp server
 Notepad++
Front end
 Php
 Html
Back end
Mysql data base

3. Objective
3.1 General objective
The main objective of this project is to keep away from difficulties faced in Manual
students’ information management system by automating the system.

3.2 Specific objective

o To have centralized control over records of the students to administrator,
teachers and students family.
o To support online registration.
o To eliminate data redundancy problem.
o To avoid fraud or missing of any student data by unauthorized people.
o To enable students see their report card online.

4
4. Methodology

4.1 Data collection

 Interviewing: by asking the school administrator and director.
 Observation: by visiting the the school staffs while they are working.
 Existing document: from existing document of the school.

4.2 Systems design and development

This subject matter makes use of structured system analysis and design approach as its
methodology.

Based on this structure system analysis and design is centered on a technique referred as which is
identifying the attributes within a systems environment and the relationships between those
entities. Using ER diagram the customer can easily understand the flow of data and process.

1. Analysis tools 
 Essential Use case diagram

 Essential Use case description

 User interface prototyping diagram

 System use case

 Sequence diagram

2. Design tools
o ER diagram

o User interface flow diagram

o Modeling architecture

3. Implementation tools
PHP, HTML, CSS, MYADMIN.WAMP SERVER.

5
 4. Testing procedure and strategies
 Unit testing: During the implementation of the system, each module of the system
was tested separately to uncover errors within its boundaries.

 Module testing: It checks the functionality of each program with relation to

other programs within the same module. It then tests the overall functionality of
each module.

 Integration testing: For constructing the program, structure while conducting

tests to uncover errors associated with interfacing.

 Acceptance testing: The system has been tested with the realistic data given by

the client and produce fruitful results.

5. Schedule of the project

Month and Dec 2011 Jan 2012 Feb 2012 Mar 2012 Apr 2012 May 2012 June 2012
week

weeks weeks Weeks weeks weeks weeks weeks

Task name 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Proposal
document

Requiremen
t document

Design
document

Implementa
tion

Testing

6
Table 1. Project plan

Milestone Deliverable Time

Requirement analysis phase SRS document

Design phase Design document

Implementation phase presentation

Table2. Project mile stone.

6. Project budget
The costs of the material requirements to do this project are the followings:-

No of Name of items Number of item Cost in birr

materials

1 Papers 200 50.00 birr

2 Pen 5 15.00 birr

3 Taxi Many time 50.00 birr

4 printing 70 pages 100.00 birr

5 Flash memory 2GB 250.00 birr

6 Computer 1 pc ------

Total price 500.00 birr

Table3. Project cost.

7. Reference

Internet

Related previous work.

7
PROPOSAL FOR INDUSTRIAL PROJECT

Advisor: Loza

Submitted on DEC, 21-2011

8
 Table of contents
Page
1. Introduction …………………………………………...........1

1.1. Background …………………………………………………..1

1.2. Statement of problem………………………………………....1

1.3. Scope and limitation of the project…………………………...2

2. Requirements…………………………………………………….2

2.1. Functional requirements………………………………………2

2.2. Non- functional requirements…………………………............3

3. Objective …………………………………………………………4

3.1. General objective ……………………………………………..4

3.2. Specific objective……………………………………………...4

4. Methodology…………………………………………………….. 4

4.1. Data collection………………………………………………...4

4.2. Systems Design and development…………………………….4

5. Schedule of the project…………………………………………..6

6. Cost estimation…………………………………………………...7

7. Reference………………………………………………………….7