1st Group Final Project Document Comment

METTU UNIVERSITY
COLLEGE OF EDUCATION AND BEHAVIORAL SCIENCE
PROJECT TITLE:-WEB BASED PARENT STUDENT FOLLOW UP
MANAGEMENT SYSTEM FOR METTU SECONDARY SCHOOL
USING AFAN OROMO
SUBMITTED TO:-DEPARTMENT OF EDUCATIONAL
TECHNOLOGY AND INFORMATION MANAGEMENT
IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE
DEGREE OF BSc IN EDUCATIONAL TECHNOLOGY AND
INFORMATION MANAGEMENT.
INDUSTRIAL PROJECT
Advisor name
Mr.Fanta Teferi (MSc)
Mettu, Oromia Ethiopia

August, 2021
Compiled by 1st Group Page 2

WEB BASED PARENT STUDENT FOLLOW UP MANAGEMENT
SYSTEM FOR METTU SECONDARY SCHOOL USING AFAN OROMO
INDUSTRIAL PROJECT
SUBMITTED BY:
1. Segni Teklu…………………..RU/2184/10
2. Gada Aga…………………….RU/2048/10
3. Gathkouth Tang……………..RU/3150/10
4. Bontu Lelisa………………….RU/1785/10
5. Yadesa Motuma……………..RU/1761/10
6. Feyisa Gubena…………….…RU/2187/10
7. Fayera Biratu………………..RU/1963/10
Submission Date:
Compiled by 1st Group Page i

Declaration
This is to declare that this project which is produced under the supervision of Mr.Fanta and
Co- advisor Mr.Oljirra title “Web-based parent student follow-up management system
using Afan Oromo for Mettu secondary school” is the sole contribution of the authors and
no part here of has been produced illegally which can be considered as plagiarism. We will
be responsible and liable for any consequences if violation of this declaration is proven.
Date: ________________
Project members:
Name: Segni Teklu___signature_______________________
Name: Gada Aga__signature_______________________
Name: Yadesa Motuma_signature_______________________
Name: Feyisa Gubena__signature_______________________
Name: Fayera Biratu_signature______________________
Name: Gatcouth Tang__signature_______________________
Name: Bontu Lelisa__signature______________________
The project has been submitted for examination with my approval as university advisor.
Advisor name:
____________________signature______________date_____________________
Co-Advisorname
______________________signature_______________date_____________
Compiled by 1st Group Page ii

Approval Sheet
Approval for the examining board:
_____________________________ _________________
Project coordinator signature
______________________________ _________________
Examiner 1 signature
_______________________________ _________________
Examiner 2 signature
Compiled by 1st Group Page iii

Acknowledgment
First of all, the project team would like to thank Almighty God for reasons to giving
us a full healthy and gave us the power to understand and to better analyzed the
system. Nothing is done without his free well. Next we take this opportunity to
express our sincere thanks to our Advisor and department head Mr.Fanta and our
instructor Dr.Mokonnen and Mr.Oljirra for the guidance and support us by giving
ideas.
Abstract
Compiled by 1st Group Page iv

Students' academic performance is affected by several factors which include students'
learning skills, parental background, peer influence, teachers' quality, learning
infrastructure among others. The main focus of this project is to use web based parent
student follow up management system to make students attention high on education. This
system is developed by Afan Oromo Language and our document part includes the
introduction, which contains background, existing system study, proposed system, objective
of the project, beneficiary of the project, scope, methodology, significant of the project,
analysis deliverables of new system, system design, testing and conclusion. The method of
data gathering tools we used are interview and observation, and design methodology we
used to design this system are object-oriented analysis and design. There are still some
problems in creating such systems as there aren’t enough resources and time. The proposed
system helps the parents to communicate with the school by being at home. Based on this
system parent gets great benefits about the status of their students at school. The System is
developed by using PHP as server side coding and HTML as client side coding as well as
MYSQL as server side database for storing data. This project therefore shares the lessons to
rise up the quality of education and recommends Mettu Secondary School to use the designed
system.
Compiled by 1st Group Page v

Table of Contents Page
Declaration............................................................................................................................................ii
Approval Sheet.....................................................................................................................................iii
Acknowledgment..................................................................................................................................iv
Abstract.................................................................................................................................................v
Abbreviations and Acronyms..............................................................................................................viii
Chapter 1...............................................................................................................................................1
Introduction...........................................................................................................................................1
1.1 Background (the organization and the project)............................................................................1
1.2Statement of the problem..............................................................................................................2
1.3Objectives.....................................................................................................................................2
1.3.1 General Objectives................................................................................................................2
1.3.2 Specific Objectives...............................................................................................................2
1.4 Scope of the project.....................................................................................................................2
1.5 Significance of the Project...........................................................................................................3
1.6 Feasibility Study..........................................................................................................................4
1.6.1 Economic feasibility.............................................................................................................4
1.6.2 Technical feasibility..............................................................................................................4
1.6.3 Operational feasibility...........................................................................................................5
1.7 Methodology................................................................................................................................5
1.7.1 Data Collection Methodology (if needed).............................................................................5
1.7.2 Software Process Model.......................................................................................................5
1.7.3 Tools and Techniques...........................................................................................................6
1.8 Roles and Responsibilities...........................................................................................................8
1.9 Dependencies and Constraints.....................................................................................................9
1.10 Risks and Contingencies............................................................................................................9
1.10.1 Risk Assessment and management...................................................................................10
1.11 Time Table...............................................................................................................................11
Chapter 2: Study of Existing System...................................................................................................12
2.1 Introduction...............................................................................................................................12
2.2 Organization Structure...............................................................................................................12
2.3 Services provided......................................................................................................................13
2.4 Users..........................................................................................................................................14
2.5 Existing infrastructure...............................................................................................................14
Compiled by 1st Group Page vi

Chapter 3: Analysis Deliverables of New System...............................................................................15
3.1 Introduction...............................................................................................................................15
3.2 Specific Requirements...............................................................................................................16
3.2.1 External Interface Requirements.........................................................................................16
3.3 Functional Requirements...........................................................................................................18
3.4 Use Cases..................................................................................................................................18
3.4.1 Actors.................................................................................................................................18
3.4.2 Use Case Diagram..............................................................................................................19
4.2.1 Use Case Description..........................................................................................................22
3.5 Classes / Objects........................................................................................................................41
3.5.1 Class Diagram.....................................................................................................................41
3.6 Non-Functional Requirements...................................................................................................42
3.6.1 Performance........................................................................................................................42
3.6.2 Reliability...........................................................................................................................42
3.6.3 Availability.........................................................................................................................42
3.6.4 Security...............................................................................................................................42
3.6.5 Maintainability....................................................................................................................42
3.6.6 Portability...........................................................................................................................42
3.7 Design Constraint......................................................................................................................42
3.8 Logical Database Requirements.................................................................................................43
3.8.1 Normalized database...........................................................................................................44
3.10 Analysis Models......................................................................................................................46
3.10.1 Sequence/Collaboration Diagrams....................................................................................46
3.10.2 State-Transition Diagrams (STD).....................................................................................51
Chapter 4: System Design...................................................................................................................56
4.1 Design Overview.......................................................................................................................56
4.2 System Architectural Design(include Component and Deployment Diagram)..........................56
4.2.1 Chosen System Architecture...............................................................................................56
4.2.2 Discussion of Alternative Designs......................................................................................58
4.2.3 System Interface Description..............................................................................................58
4.3 Detailed Description of Components.........................................................................................58
4.3.1 Component.........................................................................................................................60
4.4 User Interface Design................................................................................................................61
4.4.1 Description of the User Interface........................................................................................61
4.4.2 Screen Images.....................................................................................................................62
4.4.3 Objects and Actions............................................................................................................63
Compiled by 1st Group Page vii

Chapter 5: Testing...............................................................................................................................66
5.1 System Overview.......................................................................................................................66
5.2 Test Approach...........................................................................................................................66
5.3 Test Plan....................................................................................................................................66
5.3.1 Testing................................................................................................................................66
5.3.2 White Box Testing..............................................................................................................67
5.3.3 Black Box Testing..............................................................................................................67
5.3.4 Functional Tests..................................................................................................................67
5.4Features to be Tested..............................................................................................................68
5.3.2 Features not to be Tested....................................................................................................68
5.3.3 Testing Tools and Environment..........................................................................................68
Chapter 6: Conclusion.........................................................................................................................69
6.1 Summary of Final product.........................................................................................................69
6.2 Recommendation.......................................................................................................................69
6.3 Future Work...............................................................................................................................70
References...........................................................................................................................................71
Appendix.............................................................................................................................................72
Compiled by 1st Group Page viii

Abbreviations and Acronyms
CD------------------------Compact Disk
CSS-----------------------Cascading Style Sheet
DVD----------------------Digital Versatile Disk
HTML--------------------Hypertext Mark-up Language
MYSQL------------------My Structured Query Language
OOA-----------------------Object Oriented Analysis
OOAD---------------------Object Oriented Analysis and Design
OOD-----------------------Object Oriented Design
OOSAD--------------------Object Oriented Software Analysis and Design
OOSE-----------------------Object Oriented Software Engineering
PC----------------------------Personal Computer
PHP--------------------------Hypertext-Pre-processor
SRS--------------------------Software Requirements Specification
UML-------------------------Unified Modelling Language
Compiled by 1st Group Page ix

List of Figures Page
Figure 1: Software Process Model.............................................................................................6

Figure 2 Roles and responsibility..............................................................................................8
Figure 3.Mettu Higher Secondary School................................................................................12
Figure 4: Activity diagram to show the flow of events............................................................13
Figure 5: System use case modelling diagram.........................................................................19
Figure 6: System use case modelling diagram in Afan Oromo...............................................20
Figure 7: Class diagram...........................................................................................................40
Figure 8: The sequence diagram of login in the system...........................................................45
Figure 9: Sequence diagram Create account............................................................................46
Figure 10: Sequence diagram for Insert Result.......................................................................47
Figure 11: Sequence diagram for Generate report...................................................................48
Figure 12: Sequence diagram for View Assessment ...............................................................49
Figure 13Activity diagram for login........................................................................................50
Figure 14 Activity diagram Create account.............................................................................51
Figure 15 Activity diagram Record officer to update report....................................................52
Figure 16 Activity diagram for insert result.............................................................................53
Figure 17 Activity diagram the record officer to Prepare transcript........................................54
Figure 18.Tier architecture in deployment...............................................................................56
Figure 19.Deployment Diagram...............................................................................................57
Figure 22.User Interface...........................................................................................................62
Figure 23.System Enrollment page..........................................................................................63
Figure 24.System Login Interface............................................................................................64
Compiled by 1st Group Page x

List of Tables Page
Table 1. Front and back end design tools...................................................................................7
Table 2:Hardware and software requirement.............................................................................8
Table 3: Risks and Contingencies............................................................................................10
Table 4: Time schedule by using Gantt Chart..........................................................................11
Table 5: User interfaces...........................................................................................................17
Table 6: Use case diagram symbol...........................................................................................22
Table 7 Use case description for create account......................................................................23
Table 8 Use case description for create account......................................................................24
Table 9 Use case description for update account.....................................................................25
Table 10 Use case description for insert result........................................................................26
Table 11 Use case description for insert attendance................................................................27
Table 12 Use case description for prepare report card.............................................................28
Table 13 Use case description for view attendance.................................................................29
Table 14 Use case description for view assessment.................................................................30
Table 15 Use case description for view student result.............................................................31
Table 16 Use case description for prepare transcript...............................................................32
Table 17 Use case description for generate report...................................................................33
Table 18 Use case description for registration.........................................................................34
Table 19 Use case description for approve application...........................................................35
Table 20 Use case description for Registration Report............................................................36
Table 21 Use case description for view update report.............................................................37
Table 22 Use case description for view comment...................................................................38
Table 23 Use case description for give comment....................................................................39
Table 24 Use case description for logout.................................................................................40
Table 25: Logical Database Requirements..............................................................................42
Table 26: Detail description of components............................................................................58
Compiled by 1st Group Page xi

Chapter 1
Introduction
1.1 Background (the organization and the project)

Mettu Secondary School is one of the governmental organizations that provide teaching and
learning process at secondary school. It was established and began services in 1963 E.C
aimed to serve the communities of Mettu town and its surroundings through providing high-
quality education. The school is located in Mettu town, the capital of Ilu Ababor zone,
Oromia regional state. Based on the interests of the communities of the town and the
increased number of students from year to year, school is growth and transformed to both
high school and preparatory program. Currently, there are about 1,327 students and 48
teachers in the school.[CITATION MrG21 \l 2057 ]
Mettu Secondary school consists of academic staff (teachers) and administration staff or
supportive offices such as guards, record officer etc. The tasks performs in the school are like
registering students, registering new academic staff and administrative staff, student grades,
clubs formation and organization, one to five student formation,students exam schedule
announcement and producing different reports. And also at the beginning of each academic
year which starts in September, the students get registered and register new academic staff
and administrative staff. Mettu Secondary school is communicating with the students’ parent
through traditional/manual and time consuming. The communication is not enough to the
parent to follow up their children’s. [CITATION MrG21 \l 2057 ]

1.2Statement of the problem
Now days, there is no enough communication between Parents of the student and Mettu
Higher Secondary School due to the reason of parents cannot get their children’s continuous
assessment result as soon as possible because of time, the students adopt bad behaviour,
parents cannot able to control their children easily, parent and school communications is
tedious and time consume and they don’t know their Childs status in school, students can’t
success their goal or aim, lying of students to tell truth for their parent if they failed or get
fewer score, student is also lies the teacher when they abase in the class, the students are not
attending the class properly. Generally, it doesn’t provide opportunity for the parents to work
on their children in a close collaboration with the teachers and in general with the school.
1.3Objectives
The general and specific objectives of the project are described below:
1.3.1 General Objectives

The general objective of this project is to design and implement web-based parent student
follow up management system for Mettu secondary school using Afaan Oromo.
1.3.2 Specific Objectives

In order to achieve the general objective the following specific objectives are needed:-
 To gather required information for proposed system by using interview, observation, and
document analysis.
 To Analyse the gathered information using SRS document
 To Specify functional and non-functional requirements of the proposed System
 To Design the proposed system using UML diagram.
 To Design a database for the proposed system
 To Design implementation for the proposed system
 To Test the proposed system
1.4 Scope of the project

The scope of the project can be described as the overall features of what the new system is
capable of doing. This system has different features which make things easier for the office.
Generally, our proposed system will support the following features:
 The system creates an account for users.
 The system changes an account.

 The system views attendance of student.
 The system views report of the home room teacher.
 The system inserts the result of student.
 The system prepares report card.
 The system registers student.
 The system approves requests by parent.
 The system provides record reports.
 The system inserts attendance.
 The system prepares transcript.
 The system updates report.
 The system generates report.
1.5 Significance of the Project

After implementing the project our proposed system provides many advantages for parents,
homeroom teachers, school as well as administrator.
The main significance of the project includes: -
 The students follow their class in a good manner.
 Parents control their children easily.
 Parent and school communications is efficient and effective.
 The system works by Afan Oromo language.
 Parents know their Childs status in school.
 The students can success their goal or aim.
 Lying of child's is avoided.
 It supports the student to attend in the class every day.
 Making students more successful and disciplined from school.
 The students are attending in class properly.
 The system is more secured than existing one so files cannot be lost easily.
 It increases performance of the system.
 It makes disabled persons to follow his/her student by being at home..
 Save time, money, and other related things.
 Decrease the difficulties of parents.
 Makes the system user friendly.
 Motivate the people to use online system.
 Provide knowledge and internet service for the people.

1.6 Feasibility Study
The feasibility study is the preliminary study that determines whether a proposed system
project is financially, technically, politically and operationally viable. The alternative
analysis usually include as part of the feasibility study, identifies viable alternatives for
the system design and development.[CITATION Roy17 \l 2057 ]
1.6.1 Economic feasibility

The purpose of the economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This assessment typically
involves a cost/ benefits analysis. [CITATION Roy17 \l 2057 ]
Economic Feasibility is categorized in to two:-
Tangible feasibility
Since the proposed system is web-based, it reduces the costs that are assigned to avoid any
wastage of time and paper to handle the student’s information.
Intangible benefit
These are the benefits that the users can get after the proper completion of the proposed
system.
 The system is user friendly and it gives satisfaction for the parents and administrators
 Makes teachers, registrar and parents interested to work and join to this system.
 Work flow will be efficient and effective.
1.6.2 Technical feasibility

We believe that building this system will involve through technical knowledge and
technology availability. In technical feasibility our new system can implement with current
technology and also the user has enough experience using that technology.[CITATION Roy17 \l
2057 ]
Technical feasibility addresses these two main things:
 Is the technology practical?
Which means the system can understand easily for the users how to use it.
 The ability to do on that technology? This means, is the system can fit with the technology
that is applicable to the current time.

1.6.3 Operational feasibility
The new system will support the major activities of managing how the parent can follow
their children and will take advantage to solve the problem out lined in the statement of
the problem section .The users (teacher, parent, student, registrar and admin) can operate
the system with little training. So our system is operationally feasible. [CITATION Roy17 \l
2057 ]
1.7 Methodology
1.7.1 Data Collection Methodology (if needed)
For conducting our proposed system we used the following data collection methodology.
 Observation:-we used this method to get the right information about the organization and
also understand how the existing system works.[CITATION Sye18 \l 2057 ]
 Interview:-This methodology encapsulates two types of methods. These methods are
closed and open interview. So we selected an open interview for interviewing the manager
and employees for recognizing the existing working procedure of the organization. So we
were able be to gather more information about the organization and requirements.
1.7.2 Software Process Model

To solve actual problems in the Mettu Secondary School we must integrate with a
development strategy. This strategy is often referred to a process model or a software
development methodology. The project follows waterfall model. The waterfall model is
a sequential, plan driven-process where you must plan and schedule all your activities
before starting the project. Each activity in the waterfall model is represented as a separate
phase arranged in linear order.
It has the following phases:
 Requirements
 Design
 Implementation
 Testing
 Deployment
 Maintenance

Figure 1: Software Process Model
Each of these phases produces one or more documents that need to be approved before the
next phase begins. However, in practice, these phases are very likely to overlap and may feed
information to one another.The software process isn’t linear, so the documents produced
may need to be modified to reflect changes.
The waterfall model is easy to understand and follow. It doesn’t require a lot of customer
involvement after the specification is done. Since it’s inflexible, it can’t adapt to changes.
There is no way to see or try the software until the last phase.The waterfall model has a rigid
structure, so it should be used in cases where the requirements are understood completely and
unlikely to radically change.
1.7.3 Tools and Techniques

For the new system to be efficient there is a requirement for specific hardware and software.
 Hard ware
Personal computer (PC): almost all tasks of our project are performed on computer.
Flash disk: required for data movement to store & transfer data from one PC to another PC.
Disks (CD, DVD): necessary for the movement of relevant data and for backup and recovery
mechanism.[ CITATION Ker76 \l 2057 ]

Network cable: It helps us to extract relevant information about our project from internet.
 Software
Software isapplication program that helps us to
For design interface
For create database
For write and run our code program efficiently and effectively.
Back end design tool
MYSQL software of the data base system and PHP language is used in developing and
managing the back end of the system.
Front end design
The user interface had been developed using HTML, java script CSS since it is easily
designing the front end and connected into database easily.
Activity Tools/programs
Client side coding HTML

Clint side script Java script
Database server PHP
Design tools E-draw max
Documentation MS word
Table 1. Front and back end design tools

XAMPP server: to provide MySQL for creating and manipulating databases and PHP
(Hypertext Pre-processor) to design user interface from the front end of software. It also
provides the latest releases of phpMyAdmin, HTML, CSS and JAVA SCRIPT embedded
inside it. It is very nice and good for beginner and its start, pause and stop button work very
nicely by functionality. You can add other services to XAMPP also. Because of this we use
XAMPP for our project Development.[ CITATION W3S21 \l 2057 ]
Microsoft office 2010 and Notepad++: to write on any necessary documents about the
project.
E-draw max: to draw diagrams such as use cases diagrams, class diagrams, sequence
diagrams, collaboration diagrams, activity diagrams and state charts.
Adobe Photoshop and Picasso: to edit images and texts:
Windows 10 Operating system

Hardware and software tools required for successful completion of the projects
are listed below with their respective significance.
Hardware and software requirements
Tools
Hardware Software
 Processor: Intel(R) core(TM).i5-  Microsoft 2013 :to write the entire documents
2120cpu@2.70GHZ  Power point 2013 :for presentation for both
 Flash Disk : at minimum 8GB phase1 and phase 2.
 RAM : to the maximum of 1.90GB  Wamp server 2.5 :To run the site on the tool
Hard Disk: to the maximum of bar.
464.6GB  Notepad++ : To edit the entire implementation
 CD-R : to the maximum of 700MB code.
 Sql database server: To store data.
 Visual paradigm for UML 10.2 : to draw UML
diagrams
Table 2:Hardware and software requirement
1.8 Roles and Responsibilities
Figure 2 Roles
and
responsibility

1.9 Dependencies and Constraints
System constraints are elements, factors or sub system that works as a narrow part of a road,
when congestion occurs. It put a limit on an entity, project or system from achieving its
qualities that may be developed with reference to its goals.
Dependencies:
 User must have the basic knowledge of English.
 The user must have the ability to use the internet.
 The user must have connected to the intranet or internet to use the system.
 The accuracy of the information of user is the responsibility of all users.
Constraints
Project schedule/time limit
There is a few month to work and to implement a production system of web-based
information system from project commencement in time for graduation of truly and the
time is very consistent to use wisely because there is a class schedule all day and preparing
and reading for the class as the same time working other assignments and project works.
So that time limit may affect the work of this project.
1.10 Risks and Contingencies

Some Risks and Contingencies that may happen during the development of the system are
includes absence of electric power, if backup files were destroyed by someone else,
There may be risks during the development of the system, some actions may occur when we
are doing our project (Those actions may be damaged our system that is why we say risk).
There may be losing data from our machine (computer) when there is power failure operating
system scratched, and if there is absence of team member during working because of
different problems.
Every programmer may face many problems when he/she want to develop any project. While
we are doing this project we encounter or come across different problems.
 Loss of data by different problem.
 Shortage of time while doing the project.
 The problem of contacting the office manager at the time we needed.
 Virus attack the software.
 Lack of enough reference.

This constraint may be hindrance to come up with the software we need to develop. To
overcome these we try to schedule our time and budget and scanning with anti-viruses and
recovering the system.
No. Risk Actions/solution
1 Computer viruses, computer Backup the file, scanning with anti-
failures viruses and recovering the system.
Lack of as much as necessary To read information from different

2 references sites, using internet when there is
access.
3 Lack of financial support from the Use own money appropriately and
Organization. effectively.
Table 3: Risks and Contingencies
1.10.1 Risk Assessment and management

Technical Risks: These risks may result from excessive constraints, lack of experience,
poorly defined parameters, or dependencies on organizations outside the direct control of the
project team. In order to mitigate or control this risk the team will perform periodic checks on
the work that have been done, and by using continuous advice provided from the project
advisers.
Requirement changes: since this risk leads to system poor communication resulting in
misunderstandings and quality problems, the team altered participatory type of data modeling
to overcome such risks.
In addition there are other risks like power frailer, virus attack, when one group members fail
to continue with us.

1.11 Time Table
Table 4: Time schedule by using Gantt Chart

Chapter 2: Study of Existing System
2.1 Introduction
The existing student follow up in Mettu secondary school currently uses the manual way of
following to communicate with the parents and the school that is when one parent needs to
communicate with school committee. The parents will called by letter.
The school send letter to parents when necessary to communicate with them.
 The school prepare meeting at the end of the academic year.

 The teacher mark student’s attendance with paper.
 The home room teacher give report card to the student at the end of the
academic year.
 The recorded officer prepare report card manually.
2.2 Organization Structure

Mettu Higher
Secondary School
Administrator Teacher Record Officer Guards
Manage school Generate Keeping the

Teaches student Transcript property
Maintain school
Assess student
Generate
Hire guards Keeping robbery
clearance
from property
Generate student’s
result
Meeting with
staffs
Ask the waste

period
Forms relationship with

Figure 3.Mettu Higher Secondary School
education bureau

2.3 Services provided
(You can use activity diagram to show the flow of events)
During Parents follow up their students the service provided are the place where the school
administrator presented.Also the material on which the result of student is prepared on is a
paper.The machine used to print the student report is used.The power used to make print is an
electric power and the like services provided for the students.
Start
Admin Prepare Time

Table
Record
Home Room
Attendance
Teacher
Record Score
Prepare
Record
Transcript
Officer
Register Student
Parent
Report
Registration
Send Student to
the school
End
Figure 4: Activity diagram to show the flow of events

2.4 Users
The end user of the software can be divided into two categories
Administrator: Access to master forms for the purpose of data entry and Generation of
reports.
Operator: Access to his corresponding records.
2.5 Existing infrastructure

 Paper
 Transportation
 Copy machine
 Stapler
 Electricity.

Chapter 3: Analysis Deliverables of New System
3.1 Introduction
Requirement analysis is the initial step of constructing the whole software system. It is a
description of the project requirements that we have been gathered and analyzed. Without
requirements, the goal is not clear and understandable. In this chapter, requirements of the
software system are defined through human natural language and use case. The document is
provided in order to ensure that the software we produce will be consistent with the need of
the system’s user or customer.
During this phase, the analysis and system modeling must become full aware of functional
requirements, nonfunctional requirement of the proposed system, boundaries of the system
using use case description, Use-case diagram, showing the behavior of the system and the
communication among objects using sequence diagram and describing the structure of the
system using class diagram.The aim of this document is to gather and analyze and give an
Interactive system by defining the current system problem statement in detail. [ CITATION w3s1
\l 2057 ]
The proposed system is a Web Based system that is developed by using PHP language. The
static page is designed by using HTML for the layout of the web page, Java Script for
validation and CSS for more attractive Web site while the server side programming will be
done by using MYSQL as a database. The Administrator of the system, Home room teacher,
Registrar, parent and Record officer are login to the system by using their user name,
password and user level to login to the system, the proposed system is a web based system
which performs different tasks performed in the existing system in the secured and advanced
manner by using new technology. Our system performed different tasks such as the Record
officer can, generate transcript, update report a students’ detail and prepare final report. The
Admin account (i.e., create, update, activate, user account), the Admin can view change
password, view feedback and the home room teacher can add attendance of the student, view
report. The parent can view report, See attendance, see student result and add notification. To
access the service where registered parents have access to student’s profile and get
information on the student in concern uploaded by the teacher. The new proposed system
which is called web based parent-student follow up system for Mettu Secondary School
which solves the problems of the existing system.

3.2 Specific Requirements
This section provides software requirements to level of detail sufficient to enable designers to
design the system andtesters to test the system.
3.2.1 External Interface Requirements

3.2.1.1 User Interfaces
User Interfaces Role
Organization Registr Various fields available on this screen will be:
ation Screen F Home/ Fuula Jalqabaa
F Registration/Galmee
Raawwadhu
F About Us/Waa’ee
Keenya
F Contact Us/
Nu Quunnami
F Login/Seeni
Login Screen Fields available on this screen are:

F User Name/Maqaa
Fayyadamaa
F Password/Lakkoofsa
Iccitii
Registration Various Fields are:
F Full Name/Maqaa
Guutuu
F Mother’s Name/ Maqaa
Haadhaa
F Father’s Name/ Maqaa
Abbaa
F Gender/Saala
F Age/Umurii
F Nationality/Lamummaa
F Grade/Daree
F Supporting
Document/Xalayaa
Deggersaa
F Phone.No/Lakkoofsa
Bilbilaa
Table 5: User interfaces

3.2.1.2 Hardware Interfaces
Different hardware’s used to develop this project are listed below.
 Computer: computer is a machine capable of doing many things. We use it to type
on it and install all software and programming language. All tasks are done on
computer.
 Network cable: used to get the internet access by connecting internet line from
internet hub to computer for further read and search information from internet.
 Flash Disk and CD: used for the movement of data from one machine to another.
 Digital Camera: used to capture images regarding store, like different documentation
form and arrangement of materials to remember it.
 Hard disk with minimum of 512GB and RAM with minimum of 4GB for
information Storage purpose.
3.2.1.3 Software Interfaces

Software Tools used are:
 Microsoft office word: It offers great scope for endless revision of a document; this
includes words, word order, style and layout. It is what we use to type our project
work.
 Power point: Used to present our project in short and brief way.
 Edrawmax: is software which we used to design unified modeling diagram.
 Web browsers: Mozilla Firefox, IE, Google Chrome, Opera.
 MYSQL: for database
 XAMPP with MY-SQL.
 Operating System: Windows 8.
3.2.1.4 Communications Interfaces

The system should be accessed over LAN or WAN. For Clients to access application server
the network should be running TCP/IP protocol.
3.3 Functional Requirements

FR1: The system shall have a user account management feature.
FR2: The home room teacher shall be able to write the attendance of the student.
FR3: The parent shall be able to open and see the results of their children.
FR4: The parent shall be able to send a comment (message) to their child
teachers.

FR5: The parent shall be able to see the attendance status of their children on
their web page.
FR6: The subject teacher shall be able to add the results of the student.
FR7: The subject teacher shall be able to write comments (message) about
his/her students only to the student’s parent regarding how the student is doing in
the subject.
FR8: The subject teacher and homeroom teacher shall be able to send comments
(message) to parents.
FR9: The parent shall be give feedback for the message.
3.4 Use Cases

Use Case Diagrams describe what a system does from the viewpoint of an external observer.
The emphasis is on what a system does rather than how. A use case describes a function
provided by the system that yields a visible result for an actor. An actor describes any entity
that interacts with the system (e.g., a user, another system, the system’s physical
environment). Use Case Diagrams are closely connected to scenarios. A scenario is an
example of what happens when someone interacts with the system.
3.4.1 Actors
 Administrator.
 Home Room teacher.
 Record Officer.
 Parent.
3.4.2 Use Case Diagram

Figure 5: System use case modelling diagram

Figure 6: System use case modelling diagram in Afan Oromo
A use-case model is a model of how different types of users interact with the system to solve
a problem. As such, it describes the goals of the users, the interactions between the users and
the system, and the required behavior of the system in satisfying these goals.
 It represents interaction between a user (human or machine) and the system.
 It describes the proposed functionality of the new system. It is a single unit of
meaning full work. Each Use Case has a description which describes the functionality
that will be built in the proposed system.
 It has two types of use cases:
 Essential use case
 System use case
A use case diagram contains four components.

 Boundary:-which defines the system of interest in relation to the world around it.
 Actors: -usually individuals involved with the system defined according to their roles.
 Use cases: - the specific roles are played by the actors within and around the system.
 The relationships:-between the actors and the use cases
Construct Description Symbol
Use case ✓ A sequence of action including the

function that system can perform to interact
with actor of the system
Actor ✓ A coherent set of roles that users of the

use case play when interacting with these
use case(system)
Actor Name
System ✓ Represents boundary between physical

boundary
system and the actor who interact with Boundary name
Association ✓ The participation of actors in use case that

is instance of actor and instance of use case Association Name
communicate with each other.
Extended ✓ The relationship from an extension use
case to base use case specify how the
behavior for extension use case can be
<<extend>>Use or include
inserted into behavioral defined for the base
use case.
✓ An extend relationship between two use

case indicates alternative behavior
Use or Include ✓ A relationship from use case to an
inclusion use case specifying how the
behaviors use case for the inclusion uses
<<include>>
case inserted to the behavior for the base use

case.
✓ An include relationship between use cases

indicates where one use case always
includes the behavior of another.
Generalization ✓ Taxonomic relationship between more
general use case and more specific use case
Table 6: Use case diagram symbol
4.2.1 Use Case Description

Use case name Login/Seensa
Use case number 01

Actor Users
Description To login by his/her username & password
and access the system
Pre- condition The administrator, home room teacher,
parent and record officer have to registered
or have an account before login to the
system.
Basic course of action Step1, The users want to login.
Step2, The system displays login page for

users.
Step3, The user enters its username and

password to the system.
Step4, The system check the validity of

user name & password
Step5, The systems display the appropriate

page.
Step6, The use case end.

Alternative course of action If the users enters incorrect user name and
password. The system display error
message.
Post- condition The user will login to the system.

Table 7 Use case description for create account
Use case name Create Account/Akkaawontii Uumuu
Use case number 02

Actor Users
Description Used to create account for users
Pre- condition The user should be member of the school

Basic course of action Step1, The administrator selects create
account link.
Step2, The system displays create account

page.
Step3, The administrator fills the required

information and submits it.
Step4, The system validates the

information.
Step5, The system registers the users into

the database and display a Message
successfully register thank you.
6) The use case ends users.
Alternative course of action If the information admin fill is invalid
Go to step 3 to fill again

Post- condition The account is successfully created
Table 8 Use case description for create account

Use case name Update Account/Akkaawontii
Fooyyessuu
Use case number 03

Actor Users
Description Used to update account for users
Pre- condition The user should be member of the school
Basic course of action Step1, The administrator selects update
account link.
Step2, The system displays create account

page.
Step3, The administrator fills the required

information and submits it.
Step4, The system validates the

information.
Step5, The system registers the users into

the database and display a Message
successfully register thank you.
6) The use case ends users.
Alternative course of action If the information admin fill is invalid

information 1. The system display
duplicate entry of user name.
Go to step 3 to fill again

Post- condition The account is successfully updated
Table 9 Use case description for update account
Use case name Insert result/Firii Barataa Galchuu
Use case number 04

Actor Home Room Teacher/Ab-daree
Description Teacher can able to insert student result in
to the system
Pre- condition You should have a legal user name and
password
Basic course of action Step1, Teacher wants to Insert the student
mark to the database.
Step2, The system displays home page.
Step3, The system asks teachers to enter

their own user name and password to insert
student marks.
Step4, The system verifies the entered

username and password. If it is correct or
not.
Step5, The system display insert mark

form to teacher if correct then teachers
can be insert student mark.
Step6,The use case end.

Alternative course of action If a teacher made a mistake during entering
their own user name and password. The
system display please enters a correct user
name and password.
Post- condition Student result will successfully insert in to

the system
Table 10 Use case description for insert result
Use case name Insert Attendance/Hordoffii Galchuu
Use case number 05

Actor Home Room Teacher/Ab-daree
Description Teacher can able to insert student
Attendance in to the system
Pre- condition You should have a legal user name and
password
Basic course of action Step1, teacher wants to Insert the
Attendance to the database.tep2, The
system displays home page.
Step3, The system asks teachers to enter

their own user name and password to insert
Attendance.


not.
Step5, The system display insert

attendance form to teacher if correct
then teachers can be insert Attendance.

Alternative course of action If a teacher made a mistake during entering
their own user name and password.
The system display please enters a correct

user name and password.
Post- condition Student Attendance will successfully insert

in to the system
Table 11 Use case description for insert attendance
Use case name Prepare Report card/ Gabaasa Barataa

Galchuu
Use case number 06

Actor Home room Teacher/Ab-daree
Description First Home room Teacher must be
register /must have legal account
Pre- condition Home room Teacher can able to prepare
report card using this system
Basic course of action Step1, The system asks Home room
Teacher enter their own user name and
password to prepare Report card.
Step2, The system displays Home room

Teacher Page.
Step3, Home room Teacher click prepare

Report card link.

Step4, The system display Report card
form to Home room Teacher if it is Correct
or not.
Step5, Home room Teacher fill the required

information and submit it in to the
database.
Step6, Use case end.

Alternative course of action The system display error message if
required fields are not filled properly. And
display transcript form again
Post- condition Home room teacher will success to prepare

Report Card using this system.
Table 12 Use case description for prepare report card
Use case name View Attendance/Hordoffii Barataa

Ilaaluu
Use case number 07

Actor Parents/Maatii Barataa
Description The Parent can be able to view Attendance
using this system.
Pre- condition First Parent must be register /must have
legal account
Basic course of action Step1, Parents want to view Attendance.
Step3, The system asks users to enter

their own user name and password to
view.


not.
Step5,The system displays view

Attendance page
Step6, Parent first enter student ID And

name to view Attendance.
Step7, View Attendance display

Alternative course of action If the parent made a mistake during
entering student ID and user name, display
view Attendance again
Post- condition Parents will success to view Attendance

using this system.
Table 13 Use case description for view attendance
Use case name View Assessment/ Madaallii Ilaaluu
Use case number 08

Description The Parent can be able to view Assessment
using this system.
legal account
Basic course of action Step1, Parents want to view Assessment.

view.

not.
Step5,The system displays view

Assessment page
Step6, Parent first enter student ID And

name to view Assessment.
Step7, View Assessment display

entering student ID and user name, display
view Assessment again
Post- condition Parents will success to view Assessment

using this system.
Table 14 Use case description for view assessment
Use case name View Student result/ Firii Barataa

Ilaaluu
Use case number 09

Description The Parent can be able to view Student
result using this system.
legal account
Basic course of action Step1, Parent wants to view student result.

view.

not.
Step5,The system displays view student

result page
Step6, Parent first enter student ID to view

student result.
Step7, View Student result display

entering student ID display view Student
result from again
Post- condition Parents will success to view Student result

using this system.
Table 15 Use case description for view student result
Use case name Prepare transcript/Cuunfaa qabxii

barataa qopheessuu
Use case number 11

Actor Record officer /Mana Galmee
Description Record officer can able to prepare
transcript using this system
Pre- condition Record officer should have their own legal
account.
Basic course of action Step1, The system asks Record officer
enter their own user name and password to
prepare student transcripts.
Step2, The system displays Record officer

Page.

Step3, Record officer click prepare
transcript link.
Step4, The system display transcript form

to Record officer if it is correct or not.
Step5, Record officer fill the required

information and submit it in to the
database.
Step6, Use case end..
Alternative course of action If the recordofficer made a mistake during

entering student ID return back to step 3
Post- condition Record officer will success to prepare

transcript using this system
Table 16 Use case description for prepare transcript
Use case name Generate report/Gabaasa Dhiyeessuu
Use case number 12

Actor Record officer/Mana Galmee
Description Used for the Record officer to form
report on each actions done on student
information on the database
Pre- condition Must login to the system
Basic course of action Step1, On the home page record officer
will login to its account
Step2, System will validate the username

and password
Step3, The record officer will click on

the report button to report to the
administrator for all changes made on the

database
Step4, System will create a report
Step5, Record officer will send the report

to the administrator
Step6, System will display the report on the

administrator page

required fields are not filled properly
Post- condition Generate report on Record officer actions
on the database.
Table 17 Use case description for generate report
Use case name Register Student /Barataa Galmeessuu
Use case number 13

Description Used for the Record officer to register
new students on the database

and password

database
Step4, System will register students
Step5, Record officer will send the

registration to the database
Step6, System will display the registration

on the database.

required fields are not filled properly
Post- condition Registration of the students by Record
officer actions on the database.
Table 18 Use case description for registration
Use case name Approve Application/ Unka

Mirkaneessuu
Use case number 14

Description Used for the Record officer to approve
enrolled registration on the database

and password

database
Step4, System will approve enrolled

application
Step5, Record officer will approve

application and store on the database
Step6, System will display the approved

application on the database.

Alternative course of action The system have also deny application if
the record officer don’t want to approve it.
Post- condition Approved application of the students stored
on the database.
Table 19 Use case description for approve application
Use case name Registration Report/ Gabaasa Galmee
Use case number 15

Description Used for the Record officer toreport the
registration on the database

and password

database
Step4, System will report the registration
Step5, Registration report stored on the

database.
Step6, System will display the reported

application on the record officer page.

Alternative course of action The systems have no any report if the
record officer doesn’t register the students

in the system.
Post- condition Approved application of the students stored
on the database.
Table 20 Use case description for Registration Report
Use case name Update report/Gabaasa Fooyyessuu
Use case number 16

Description Used for the Record officer to form
update report on each actions done on
student information on the database
Basic course of action Step1,On the home page record officer


and password

the update report button tore port to the
database
Step4, System will create a report
Step5, Record officer will send the report

to the administrator
Step6, System will display the report on the

administrator page

required fields are not filled properly.
Post- condition Record officer update report actions on the

database using this system.
Table 21 Use case description for view update report
Use case name View Comment/Yaada Ilaaluu
Use case number 17

Actor Parents(Maatii Barataa), Home room
Teacher (Ab-daree)
Description The Parents, Home room Teacher, Can be
able to view Comment using this system.
Pre- condition First Parents, Home room Teacher must be
Basic course of action Step1, Parents, Home room Teacher Want

to view Comment.

view.

not.
Step5, the system displays view Comment

Page.
Step6, Parents, Home room Teacher First

enter student ID And name to view
Comment.
Step7, view Comment display
Step8, The use case end..

Alternative course of action the Parents, Home room Teacher made a
mistake during entering student ID and user
name. display view Comment Again
Post- condition Parents, Home room Teacher Will success
to view Comment using this system.
Table 22 Use case description for view comment
Use case name Give Comment/Yaada Kennuu
Use case number 17

Actor Parents(Maatii Barataa), Home room
Teacher (Ab-daree)
Description The Parents, Home room Teacher can be
able to view Comment using this system.
Pre- condition First Parents, Home room Teacher must be
Basic course of action Step1, Parents, Home Room Teacher want

to give comment.

view.

not.
Step5, The system displays Give Comment

Page.
Step6, Parents, Home room Teacher First

enter student ID And name to Give
Comment.

Step7, Give Comment display

Alternative course of action If the Parents, Home room Teacher made a
mistake during entering student ID and user
name, display Give Comment Again.
Post- condition Parents, Home room Teacher Will success

to Give Comment using this system.
Table 23 Use case description for give comment
Use case name Logout/Ba’uu
Use case number 18

Actor All user
Description Used for all user to logout from their
account in the website.
Pre- condition Must login to the system.
Basic course of action Step1, On their page users will press

logout button
Step2, System will logout from the current

account.
Alternative course of action The system don’t permit for users unless
they click on the logout button.
Post- condition User will logout from the database
Table 24 Use case description for logout

3.5 Classes / Objects
3.5.1 Class Diagram
UML class diagrams show the classes of the system, their interrelationships (including
inheritance, aggregation, and association) and the operations and attributes of the classes.
Class diagrams are used for a wide variety of purposes, including both conceptual/domain
modeling and detailed design modeling. A class model is comprised of one or more class
diagrams and the supporting specifications that describe model elements including classes,
relationships between classes, and interfaces. UML class diagram show the classes of the
system, their inter-relationships, and the operations and attributes of the classes.
Class diagram is a type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, operations (or methods), and the relationships
among objects. An object model is a logical interface, software or system that is modeled
through the use of object-oriented techniques. It enables the creation of an architectural
software or system model prior to development or programming.
Figure 7: Class diagram

3.6 Non-Functional Requirements
The nonfunctional requirements of the proposed system are collected from the users’
expectations and technical skills they are expected to have. These are categorized and
presented as follows.
3.6.1 Performance
NFR-1: -Acceptable response times for system functionality.
3.6.2 Reliability
NFR-2: The system that is to be developed is real and not ideal.
NFR-3: The system does not allow unauthorized users to login.
NFR-4: This system is developed based on the collected requirements.
NFR-5: This system will work properly in specified environment and in a
given time.
3.6.3 Availability
NFR-5: The developed system is easy to change when a new technology is
introduced and additional applications found. The system will only support
the Afan Oromo Language.
3.6.4 Security
NFR 6: Unauthorized access to the system shall be denied.
3.6.5 Maintainability
NFR-7: System is being developed in php. Php is an object oriented
programming language and shall be easy to maintain
3.6.6 Portability
NFR-8:-The System shall run in any Microsoft Windows environment that
contains php Runtime and the MySQL database management system.
3.7 Design Constraint

Project limitations typically fall into several categories. By recognizing these categories, you
can focus the investigations and thereby increase the chances that you’ll discover all
limitations affecting the project.
The project drivers and supporters may have present expectations or requirements in one or
more of the following categories:

 Time frames: When you must produce certain results. For example, the project must
be done by August 30. You don’t know whether it’s possible to finish by August 30.
 Resources: The type, amount, and availability of resources to perform your project
work. Resources can include people, funds, equipment, materials, facilities,
information, and so on.
 Activity performance: The strategies for performing different tasks.
3.8 Logical Database Requirements

In order to store information persistently group of actors map objects into tables and the
attributes into fields to the specific table based on the objects found on the system.
Therefore, the identified the major tables that would be implemented on the selected
DBMS.
Sno Entity Attribute of an Data type Primary key

entity
1 Administrator  Fname varchar(40) admin_id
 Lname varchar(40)
2 Home Room  Fname varchar(56) teacher_ id
Teacher  Lname varchar(56)
3 Parent  stud_name varchar(40) stud_id

 stud_id varchar(30)
 Parent_nam
e
4  Fname varchar(30) Recordofficer-id

Record officer  Lname varchar(30)
Table 25: Logical Database Requirements

3.8.1 Normalized database
1st normal form
Assessment table
Grade Teacher Grade Subject MaxMarkT1 Test1 Test2
Attendance table
Attendance Student Status Recorded Sex G section Student

Name By ID
Mark form table
Amharic English Maths Physics Biology Chemistry Geography History Civics
Comment form table
Date Username Student ID Comment
Student table
Full name Gender Student Parent Status Paid Failed Student ID

Type Name months Subjects
2nd normalization
Assessment table
Attendance table

Name By ID
Mark form table

Amharic English Maths Physics Biology Chemistry Geography History Civics
Comment form table
Student table
Full name Gender Student Parent Status Paid Failed Student ID

Type Name months Subjects
3rd normalization
Assessment table
Attendance table

Name By ID
Mark form table

Amharic English Maths Physic Biology Chemistry Geograph History Civic
s y s
Comment form table

Student table

Full Gender Student Parent Status Paid Failed Student
name Type Name months Subjects ID
3.10 Analysis Models

3.10.1 Sequence/Collaboration Diagrams
Sequence diagrams show a succession of interactions between classes or object instances
over time. The Sequence diagrams of some classes are given below:
Figure 8: The sequence diagram of login in the system

Figure 9: Sequence diagram Create account

Figure 10: Sequence diagram for Insert Result

Figure 11: Sequence diagram for Generate report

Figure 12: Sequence diagram for View Assessment report

3.10.2 State-Transition Diagrams (STD)
Login
Enter user name & password
Ckeck user name & password
If input is invalid If input is valid
Logged succesfully

Figure 13Activity diagram for login

Login
No
Yes
Display create account form
Fill account forms and submit
Fill again Valid

No
Yes
Account created successfully

for user
Figure 14 Activity diagram Create account

Login
No
Yes
Display Record officer page
Click Upadate link
Select update report and

submit
The Update report is

successfully
Figure 15 Activity diagram Record officer to update report

Login
NO
yes
Display The Home room Teacher Page
Click Insert result
Display Insert result form
Fill the form
Check Validity
NO
yes
result inserted
Figure 16 Activity diagram for insert result

login
NO
yes
Display The Record Officer Page
Prepare Transcript
Display the form
Fill the form
Check Validity
NO
yes
Transcript inserted
Figure 17 Activity diagram the record officer to Prepare transcript

Chapter 4: System Design
4.1 Design Overview
Parent-Student follow up web based system design document describes the proposed system
in detail. It also presents the proposed system architecture and decomposition in to its
subsystems which are manageable. It presents the requirement information that is previously
dealt in the requirement analysis part of the Waterfall Model in a more simplified and
specific way for the implementation of the new system so that it achieves the system
specifications identified during requirement analysis. This document provides list of design
goals, hardware/software mapping, access control and boundary conditions in addition to
presenting the proposed architecture, its components and the persistent data management.
4.2 System Architectural Design (include Component and Deployment

Diagram)
4.2.1 Chosen System Architecture

Architecture is the fundamental organization of a system, embodied in its components, their
relationship to each other and the environment, and the principles governing its design and
evolution.
Three-tier architecture is a client-server architecture in which the functional process
logic, data access computer data storage and user interface are developed and
maintained as independent modules on separate platforms. Three-tier architecture is a
software design pattern and well-established software architecture. Its three tiers are the
presentation tier, application tier and data tier.[ CITATION w3s \l 2057 ]
Three tier architectures consist of three components distributed in three layers:
1. Client (requester of services),
2. Server (provider of services) and
3. Database.
The three components made the three-tier architecture.
1. User System Interface (such as session, text input, dialog, and display output services).
2. Application server
3. Database Management server (such as data and file services).
Why we choose three-tier architecture?

Because of the system is distributed application with client which are distributed around
different area hence each need to contact the central server to get some service which in
turn contacts the Database server for persistent data storage and retrievable. Based on this
scenario it is straight forward to select 3-tier architecture.
Figure 18.Tier architecture in deployment

4.2.1.1 Deployment Diagram
UML deployment diagram show physical view of system, taking software into real world by
showing how software gets assigned to hardware and how communicates. The deployment
diagram shows how the software components, processes, and objects are deployed into the
physical architecture of the system.
Figure 19.Deployment Diagram
4.2.2 Discussion of Alternative Designs
4.2.3 System Interface Description

The system will remain operational and its functionality will be complementary but
independent from the parent student management system. At any time, user may use either
the user service system only.
The online user creation and the follow up system will be operational even if the
student service system is offline also the system interfaces are not needed during the
development of this project that the system is connected with organization data base.

4.3 Detailed Description of Components
Component name Component number Description Of Components
#1 Login page which enables

Login page user of system log into
system by entering their user
name and password.
#2 User interface part where
main page of the PSFMS
Home page
would be viewed and link for
related interface.
#3 The system Admin Page is
the page that enables the
Administrator page system Administrator to
manage user account for
users of the system.
Parent page #4 It is the page contains all

activities of the parent
enables to follow their
students.
Record Officer page and #5 It is the page contains all
activities that would be done
by Record Officer.
Home Room Teacher #6 It is the page contains all

activities that would be done
by Home Room Teacher.
Enables to enchained quality
of education and get report.
Table 26: Detail description of components

4.3.1 Component
Figure 20.Component Diagram

4.4 User Interface Design
Application will be accessed through a Browser Interface. The software would be fully
compatible with Microsoft Internet Explorer, Mozilla Firefox and Google Chrome. No user
would be able to access secured part of the application (such as exam page, result, account
settings etc.) without logging on to the system. The system should be accessed over LAN.
The OEMS is also user friendly that it is simple to be used by any users. The user interface
of this application is shown below.
4.4.1 Description of the User Interface

 Administrator: The administrator is a person who has the responsible for the
managing user account and manages the system.
 Home Room Teacher:is a person who has the responsible for to enhanced quality of
education and get report from the system.
 Record Officer: has the right to view some information on the system and manage
the student’s transcript.
 Parent:they cannot add, update and edit or modify any results/score of their student.
But, they see their student result and give the comment.

4.4.2 Screen Images
Figure 21.Screen Image

4.4.3 Objects and Actions
The Administrator Login page consists of:
Id text box – the administrator writes his/her id (string, max_length 30 characters)
Password text box – the administrator writes his/her password (string, max_length 20
characters)
 Radio button – the Administrator chooses his/her level of access.
 Log in button – after being pressed the system performs user authentication. If the
administrator inputs correct data, he/she gets the access to the system. Otherwise, the
system displays Invalid/Missing data massage and clears the text boxes.
The Main Page is the user page that provides him/her with the access to other pages he/she
intends to visit. It contains of:
 Logo of the company
The User Login Page is divided into the part for a current user and a new user. It consists of
the:
 text boxes for users id and password,
 Log in button, for the current user authentication.
Figure 22.User Interface

Figure 23.System Enrollment page

Figure 24.System Login Interface

Chapter 5: Testing
5.1 System Overview
This test document defines all the procedures and activities required to prepare for
testing of the functionalities of the system. Functional testing consists of a series of
functional tests of workflows and transactions created and executed to identify and measure
the quality of software. The testing will simulate user interaction with the system so that
functionality of the system can be evaluated with different User Roles. The objectives
of the test plan are to define the activities to perform testing, define the test
deliverables documents and to identify the various risks and contingencies involved in
testing.
5.2 Test Approach

Testing is an empirical investigation conducted to provide stake holders with information
about the quality of the product or service under test, with respect to the context in which it is
intended to operate. Some new projects are testing also provides an objectives, independent
view of the new system to allow the user to appreciate and understand the testing including.
 Allow the user to appreciate.
 Understand the risks at implementation of the new system
 Defects and failures
5.3 Test Plan

In case of Web based parent student follow up management system the following testing
mechanisms are used:
5.3.1 Testing
It is typically done by system developer during system development and the team tested
different service of the system and checked the effectiveness of the system and weather they
are computable to Web based parent student follow up management system. These testing
include:
Web based parent student follow up
Web based create account.
Web based student registration.

Web based generate report.
5.3.2 White Box Testing

White Box Testing is a testing in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is used to test areas
that cannot be reached from a black box level.
Using this testing method we test the system for the following purposes:-
 Validate the users
 Change accounts
5.3.3 Black Box Testing

Black Box Testing is testing the software without any knowledge of inner workings, structure
or language of the module being tested. Black box tests, as most other kinds of tests, must be
written from a definitive source document, such as specification or requirements document,
such as specification or requirements document. It is a testing in which the software under
test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds
to outputs without considering how the software works.
Using this testing method we test the system for the following:-
 User login
 View result
 View attendance
 View Assessment
5.3.4 Functional Tests

Functional tests provide a systematic demonstration that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals. Functional testing is centered on the following items:
 Valid Input: identified classes of valid input must be accepted.
 Invalid Input: identified classes of invalid input must be rejected.
 Functions: identified functions must be exercised.
Test objectives:
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

5.4Features to be Tested
The following list describes the features to be tested:
USER
 Registration
 Login
 View Result
ADMIN:
 Login
 Create Account
 Update Account
5.3.2 Features not to be Tested

 Data base server recovery and maintenance will not be tested.
 Internal errors i.e. communication and other outside system components related to
the system
5.3.3 Testing Tools and Environment

The following resources requirements are needed for testing the hardware and software
components of the system.
5.3.3.1 Hardware Requirement and Software Requirement

 Processor speed: 2.0GHz
 RAM size: 1gb
 Hard disk size: 80GB
 Network card and fast Ethernet port for networking and connectivity.
 4.0 GB RAM for server side
 3.6 GHz processor for server side
 Windows Os (XP and above)
 Windows Server 2003/2008

Chapter 6: Conclusion
6.1 Summary of Final product
The system that we have developed has two phases; the first phase deals with the analysis
phase of the life cycle with the school, and the next phase addresses the design phase. As the
end of the first phase, we need to review what we have planned at the beginning. We began
our work by identifying the significance of the new system for the school and the overall
techniques to be used in the development process. This concerned defining the system
development methodology, identifying process and resource, and setting the deliverable and
scheduled for the project. And also helps the team to understand the major functional areas
and processes of the proposed system. We identified the weakness and strength of the
existing system by developing the proposed system.
After that, we discovered system requirements. Through this phase, we identify functional
and non-functional requirements of the new system. Then we have undertaken a major phase
in system development process: object oriented Analysis. Here, we tried to model the new
system we proposed using UML diagrams: Use case, sequence, and class diagrams. Also, we
designed the new system user interface prototype.
As a result, we proposed the new system to solve the problem of existing system such as time
management and to address student’s information in time for their parents.
6.2 Recommendation
Using this new system will make the school more profitable than before or to achieve their
goals that are to give attention for giving education, so the team greatly recommends giving
more attention to this new developed system.
We would like to suggest that the system is open for interested groups or individuals who
wish to add new functionalities because the scope of the proposed project is very interesting.
Finally, we would like to recommend to Mettu Secondary School to use this system. Because
the proposed system is useful for the school, parents, as well as students.

6.3 Future Work
 Capable of sending text messages to mobiles while the information of student being
posted to the system.
 Integrity
 Make the system friendly in such a way that anyone can use the system using Small
devices which have narrow screen resolution such as smart phones.
 Alarming system while the problems are occurred in the school.

References
[1] M. G. Denu, Interviewee, Background of Mettu Secondary School. [Interview]. 15 6 2021.
[2] D. d. B. B. Momin Mukherjee, "ResearchGate," International journal of advanced Engineering

and Management, 19 7 2017. [Online]. Available:
https://www.researchgate.net/publication/317713058_Feasibility_Studies_and_Important_Asp
ect_of_Project_Management/link. [Accessed 1 july 2021].
[3] S. M. S. Kabir, "ResearchGate," 25 June 2018. [Online]. Available:

https://www.researchgate.net/publication/325846997_METHODS_OF_DATA_COLLECTION/link/
5b3127b3a6fdcc8506cc9d48/download. [Accessed 19 7 2021].
[4] B. W. Kernighan and Plauger, 1976. [Online].
[5] W3Schools, 1999-2021. [Online].
[6] w3schools. [Online]. Available: http://www.w3schools.com/css/css_background.asp.
[7] w3schools. [Online]. Available:  http://www.w3schools.com/html/html_intro.asp.

Appendix
 Source Code(important sections )
Code for home or index page
<?php
session_start(); // you must always start session
if (!isset($_SESSION['username']))
{
$x=5;
include('include/header.php'); ?>
<div class="wrapper row3">

<div class="rounded">
<main class="container clear">
<div class="group btmspace-30">


<div class="one_quarter first">

<ul class="nospace">
<li class="btmspace-15"><em class="heading">Barattoota Achitti Barnoota
Xumuranii Dhaabbilee Barnoota Olaanoo Deeman </em> <img class="borderedbox"
src="images/fc.jpg" alt=""></li>
<li class="btmspace-15"><em class="heading">Barattoota Amma Achitti
Barachaa Jiran</em> <img class="borderedbox" src="images/g.jpg"" alt=""></li>
</ul>

</div>



<div class="one_half">

<i class="text-success"></i> <h3>Maqaa fi Lakkoofsa iccitii keessanii galchaa!
</h3>
<div class="login-box-body col-md-8">
<form action="Login.php" method="post">
<div class="has feedback">
<div class="input-group">
<tr>
<td width="20" height="37" ><div align="left" margin-
left="2px"><strong><font color="#FF0000">*</font>Fayyadamtoota :
</strong></div></td>
<td align="left">
<select id='usertype' name="usertype" required style="width:175px;"
"height:20px;" margin-left="2px" >
<option></option>
<option>Hogganaa</option>
<option>Mana Galmee</option>
<option>Bariisaa Daree</option>
<option>Maatii</option>
</select>
</td>
</tr>

<i class="fa fa-user"></i>
<input type="text" name="username" placeholder="Maqaa
fayyadamaa" required/>
</div>
</div>
<br>
<div class="has feedback">
<div class="input-group">
<i class="fa fa-lock"></i>
<input type="password" name="password" placeholder="Lakkoofsa
Iccitii" required pattern="^[0-9 a-z A-Z]*$" title="inter valid password"//>
</div>
</div>
<br>
<div class="form-group">
<div class="col-md-4">
<button type="submit" value="Login" name="submit" class="btn btn-
success btn-block"><i class="fa fa-log-in"></i> Seeni</button>
<br>
<button input type="Reset" class="btn btn-success
btn-block">Haqi</button>
</div>
</div>
</div>
</form>
<?php

require 'include/conn.php';
if(isset($_POST['submit'])){
$username = $_POST['username'];
$password = $_POST['password'];
if($username&&$password){
//Create query
$login = $conn->query("SELECT * FROM account1 WHERE
Username='$username' AND Password='$password'");
while($row=$login->fetch_assoc()){
$db_type=$row['type'];
$IsActive=$row['IsActive'];
if($db_type=="teacher"&& $IsActive=="true"){
$_SESSION['username']=$username;
header("Location: Teacherp.php");
exit();
}
if($db_type=="record officer"&& $IsActive=="true"){
header("Location: RecordOfficerp.php");
exit();
}
if($db_type=="parent" && $IsActive=="true"){
header("Location:Parentp.php");
exit();

}
if($db_type=="adminstrator"&& $IsActive=="true"){
header("location:Adminp.php");
exit();
}
}
die ('<script type="text/javascript">alert("Maqaafi lakkoofi iciitii isin

galchitan dogoggora yookiin akkaawontiin keessan hojiirra hin oolle!");
</script>');
}
else
die("Maaloo maqaa fi lakkoofsa iccitii keessan galchaa!");
}
?>
</div>
<div class="clear"></div>
</main>
</div>
</div>
<?php include('include/footer.php'); ?>
<?php
}
?>

<?php ob_start();
error_reporting(0);
?>
<html>
<head>
<title>Admin page</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-
scale=1.0, user-scalable=no">
<link href="layout/styles/layout.css" rel="stylesheet" type="text/css" media="all">
<link href="layout/styles/bootstrap.css" rel="stylesheet" type="text/css" media="all">
<link href="layout/styles/AdminLTE/dist/css/skin-blue.css" rel="stylesheet"
type="text/css" media="all">
</head>
<body id="top">
<body id="top">
<div id="topbar" class="clear">
<nav>
<li><a href="profile.php">Anaadhufu <?php echo $_SESSION['username'] ?

></a></li>
<li><a href="include/Logout.php">Bahi</a></li>
</nav>
</div>
</div>

<header id="header" class="clear">

<div id="logo" class="fl_left">
<br>
<h1><a href="index.php">Mettu Higher Secondary School</a></h1>
<p>Web-Based Parent-student follow Up System using Afan Oromo</p>
</div>
</header>
</div>
<div class="rounded">
<nav id="mainav" class="clear">
<ul class="clear">
<li <?php if($x==1){echo "class='active'";}?>><a href="Adminp.php"
style="text-decoration:none;">Fuula Jalqabaa</a></li>
<li <?php if($x==2){echo "class='active'";}?>><a href="account.php"
style="text-decoration:none;">Akkaawontii Uumuu</a></li>
<li <?php if($x==3) {echo "class='active'";}?>><a
href="RemoveAccount.php" style="text-decoration:none;">Akkaawontii
Fooyyessuu</a></li>

<ul>

</ul> </li> </ul> </li>
</ul> </nav>
</div>
</div>

1st Group Final Project Document Comment

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1st Group Final Project Document Comment

Uploaded by

Copyright:

Available Formats

METTU UNIVERSITY

COLLEGE OF EDUCATION AND BEHAVIORAL SCIENCE

PROJECT TITLE:-WEB BASED PARENT STUDENT FOLLOW UP

MANAGEMENT SYSTEM FOR METTU SECONDARY SCHOOL

USING AFAN OROMO

SUBMITTED TO:-DEPARTMENT OF EDUCATIONAL

TECHNOLOGY AND INFORMATION MANAGEMENT

IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE

DEGREE OF BSc IN EDUCATIONAL TECHNOLOGY AND

Mettu, Oromia Ethiopia

Compiled by 1st Group Page 2

Compiled by 1st Group Page i

Name: Segni Teklu___signature_______________________

Name: Gada Aga__signature_______________________

Name: Yadesa Motuma_signature_______________________

Name: Feyisa Gubena__signature_______________________

Name: Fayera Biratu_signature______________________

Name: Gatcouth Tang__signature_______________________

Name: Bontu Lelisa__signature______________________

Compiled by 1st Group Page ii

Approval for the examining board:

Project coordinator signature

Compiled by 1st Group Page iii

Compiled by 1st Group Page iv

Compiled by 1st Group Page v

Compiled by 1st Group Page vi

Compiled by 1st Group Page vii

Compiled by 1st Group Page viii

Compiled by 1st Group Page ix

Figure 1: Software Process Model.............................................................................................6

Compiled by 1st Group Page x

Compiled by 1st Group Page xi

1.1 Background (the organization and the project)

Compiled by 1st Group Page 1

1.3.1 General Objectives

1.3.2 Specific Objectives

1.4 Scope of the project

Compiled by 1st Group Page 2

1.5 Significance of the Project

Compiled by 1st Group Page 3

1.6.1 Economic feasibility

1.6.2 Technical feasibility

Compiled by 1st Group Page 4

1.7.2 Software Process Model

It has the following phases:

Compiled by 1st Group Page 5

1.7.3 Tools and Techniques

Compiled by 1st Group Page 6

Client side coding HTML

Table 1. Front and back end design tools

Adobe Photoshop and Picasso: to edit images and texts:

Windows 10 Operating system

Compiled by 1st Group Page 7

1.8 Roles and Responsibilities

Compiled by 1st Group Page 8

1.10 Risks and Contingencies

Compiled by 1st Group Page 9

Lack of as much as necessary To read information from different

Table 3: Risks and Contingencies

1.10.1 Risk Assessment and management

Compiled by 1st Group Page 10

Table 4: Time schedule by using Gantt Chart

Name: Segni Teklu_signature_____________________

Name: Gada Agasignature_____________________

Name: Feyisa Gubenasignature_____________________

Name: Gatcouth Tangsignature_____________________

Name: Bontu Lelisasignature____________________