DEBRE MARKOS UNIVERSITY

DEBRE MARKOS INSTITUTE OF TECHNOLOGY

DEPARMENT OF COMPUTER SCIENCE

WEB BASED STUDENTES INFORMATION

MANAGEMENT SYSTEM FOR BURIE GENERAL
SECONDARY AND PREPARATORY SCHOOL
IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF

BACHELOR OF SCIENCE IN COMPUTER SCIENCE

1. MEWDED YIHUNIE…………TER065/08
2. YIMMER ALELEGN…………….TER079/08
3. CHEKOLIE SHIFERAW………...TER045/08
4. ALMAZ KASSAW…………….TER040/08

Advisor: Mr. KEREBIH G.

DEBRE MARKOS UNIVERSITY, ETHIOPIA

February, 2019
Acknowledgement

First of all we would like to thank GOD for helping us to reach this time and do this project.
After we would our honorable advisor instructor Mr. KEREBIH GETNET (MSC) give his great
contribution in stimulating suggestion encouragement and advice in all the time we were
working on the project. Next we would like to thank our best friend Mr. TADEGE TAREKEGN
(BSC) to give us any type of support. Finally, we would like to thank office for giving us the
necessary information about how the current systems are and how they work.

i
ABSTRACT
This project concerned about web based student information system which is found in
BURIE town. Today the overall activities of BURIE general secondary and preparatory
school are under taken manually. There unmannered storage space information, which
consume time, money and very tedious which make the situation very difficult. Based
on the above problem by developing this project we automate the existing manual
system. This project works on student registration, Information Provide, recording mark,
prepare transcript and card, club management and view mark. The system allow to the
users, to search Information in a fast mechanism.

ii
Contents
Acknowledgement ......................................................................................................................................... i
ABSTRACT...................................................................................................................................................... ii
List of table................................................................................................................................................ v
List of figure ................................................................................................................................................ vi
List of acronyms ......................................................................................................................................... vii
CHAPTER ONE ........................................................................................................................................... 1
1. Introduction ........................................................................................................................................... 1
1.2. Introduction ........................................................................................................................................ 1
1.2. Backgrounds of the organization ....................................................................................................... 1
1.3. Backgrounds of the project ................................................................................................................ 1
1.4. Statement of the Problems ................................................................................................................. 2
1.5. Objective ............................................................................................................................................ 2
1.5.1. General Objective ....................................................................................................................... 2
1.5.2. Specific Objective ....................................................................................................................... 2
1.6. Scope of the Project ........................................................................................................................... 3
1.7. Significance of the Project ................................................................................................................. 3
1.8. Methodology ...................................................................................................................................... 4
1.8.1. System requirements ................................................................................................................... 4
1.8.2. Data collection methodology ...................................................................................................... 5
1.8.3. Analysis and Design Methodology ............................................................................................. 6
Chapter Two.................................................................................................................................................. 7
1. System Analysis .................................................................................................................................... 7
1.1. Overview of The existing system.................................................................................................. 7
2.2. System Requirement specification ..................................................................................................... 8
2.2.1. Functional Requirement .............................................................................................................. 8
2.2.2. Non- Functional Requirements ................................................................................................... 8
2.2.3. Business Rule .............................................................................................................................. 9
2.2.4. Change case .............................................................................................................................. 10

iii
 2.3. System Requirement analysis .......................................................................................................... 10
2.3.1. Actor and Use case identification ............................................................................................. 10
2.3.1. Sequence diagram ..................................................................................................................... 22
2.3.2. Activity Diagram....................................................................................................................... 30
2.3.3. Analysis Class Diagram ............................................................................................................ 37
CHAPTER THREE .................................................................................................................................... 38
3. System Design ........................................................................................................................................ 38
3.1. Design class diagram ....................................................................................................................... 38
3.1.2. Design Class diagram descriptions ........................................................................................... 39
3.2. User interface design........................................................................................................................ 47
3.3 System architecture (Deployment diagram)...................................................................................... 50
CHAPTER FOUR ........................................................................................................................................... 51
4.1. IMPLEMENTAION ............................................................................................................................. 51
4.1.1. Overview of programming language used ................................................................................ 51
4.1.2. Algorithm used .......................................................................................................................... 51
4.1.3. Sample code .............................................................................................................................. 52
CHAPTER FIVE ............................................................................................................................................. 72
5.1. Testing .............................................................................................................................................. 72
5.1.1. System Testing .......................................................................................................................... 72
5.1.2.Unit testing ................................................................................................................................ 74
5.1.3. Integration Testing .................................................................................................................... 76
5.1.4. Validation Testing ..................................................................................................................... 76
CHAPTER SIX................................................................................................................................................ 77
6.1. CONCLUSION AND RECCOMENDATION ........................................................................................... 77
6. 1.1.Conclusion ................................................................................................................................. 77
6.1.2. Recommendation ...................................................................................................................... 77
6.2.3. Future Enhancement ................................................................................................................ 78
References .................................................................................................................................................. 78

iv
 List of table
Table 1: Development tools .......................................................................................................................... 4
Table 2: Development hard ware tools ......................................................................................................... 5
Table 3Development programming language ............................................................................................... 5
Table 4. Users of existing system ................................................................................................................. 8
Table 5Registration ..................................................................................................................................... 13
Table 6: Update Student.............................................................................................................................. 13
Table 7: View mark .................................................................................................................................... 14
Table 8: Prepare transcript .......................................................................................................................... 15
Table 9: save mark ..................................................................................................................................... 16
Table 10: Upload notice .............................................................................................................................. 18
Table 11: Create Account .......................................................................................................................... 18
Table 12: Delete Account ........................................................................................................................... 19
Table 13: Add club...................................................................................................................................... 20
Table 14: Send Feedback ............................................................................................................................ 21
Table 15: Class Description of student ....................................................................................................... 39
Table 16:Class Description of teacher ........................................................................................................ 40
Table 17: Class Description of Home room teacher ................................................................................... 41
Table 18: Class Description of director ...................................................................................................... 42
Table 19: Class Description of Record officer............................................................................................ 43
Table 20: Class Description of Vice director .............................................................................................. 44
Table 21: Class Description of parent ......................................................................................................... 45
Table 22. Programming language used....................................................................................................... 51
Table 23.authentication for user login ....................................................................................................... 75

v
List of figure
Figure 1: Use case ....................................................................................................................................... 12
Figure 2: Login sequence diagram ............................................................................................................. 22
Figure 3: Create account sequence diagram ............................................................................................... 23
Figure 4: prepare card sequence diagram ................................................................................................... 24
Figure 5Login activity diagram .................................................................................................................. 30
Figure 6: Add club activity diagram ........................................................................................................... 31
Figure 7: Student registration activity diagram........................................................................................... 32
Figure 8: Prepare transcript activity diagram .............................................................................................. 33
Figure 9: Save mark activity diagram ......................................................................................................... 34
Figure 10: View mark activity diagram ...................................................................................................... 35
Figure 11: Logout activity diagram ............................................................................................................ 36
Figure 12 Analysis Class Diagram............................................................................................................ 37
Figure 13. Design class diagram ................................................................................................................. 39
Figure 14. Home UI .................................................................................................................................... 47
Figure 15. Login form UI ............................................................................................................................ 48
Figure 16. Feedback form UI ...................................................................................................................... 48
Figure 17. Club member registration UI ..................................................................................................... 49
Figure 18.Deployment diagram .................................................................................................................. 50
Figure 19. screenshot for add mark first page ............................................................................................ 61
Figure 20. screenshot for add mark page second page .............................................................................. 71
Figure 21. Screen shoot for login with incorrect username and password .................................................. 73
Figure 22. Screen shoot for create account ................................................................................................. 74

vi
List of acronyms
Acronym Expanded form
HTML-------------------------------Hyper Text Markup Language
PHP---------------------------------- Hypertext pre-processor
HTTP--------------------------------Hyper Text Transfer Protocol
MYSQL-----------------------------My Structured Query Language
UC---------------------------------------Use Case
BR--------------------------------------- Business Rule

UI-----------------------------------------------User Interface
TID--------------------------------------Teacher identification
VDID-------------------------------------Vice Director Identification
SID--------------------------------------Student identification
HRTID--------------------------------Home Rome Teacher identification
PID-------------------------------------Parent identification
RID-----------------------------------Record officer identification
DID-----------------------------------Director Identification
OOAD-------------------------------- Object Oriented Analysis and Design

vii
CHAPTER ONE

1. Introduction
1.2. Introduction
As we know, today our world is under the control of technology because of this reason the world
is related each other. Our country is one part of the world but, we are too late according to this
technology as compare as others western countries. Even if our country is not developed, we try
to change the manual system of BURIE General Secondary and Preparatory School office into
web based student information system using today‟s technology. Web based application gives an
opportunity to access information from anywhere in the world at any time. So, this project can
increase the technology adoption for our country and can solve many problems such as bulky,
unreliable, and unsecure, creates data redundancy, loss of data and Consumes more resources to
do many activities such as Rank view, student registration, View exam results, prepare transcript
and manage club.
1.2. Backgrounds of the organization
BURIE General Secondary and Preparatory School was established in 1987 E.C. This school
includes grade levels from grade 9 up to grade 12. The school includes a large number of
students and teachers. The numbers of students included in the school were 2,329 males and
2,283 females with total number of 4,612 students. The numbers of teachers included in the
school were 112 males and 35 female teachers with total 147. Other supportive staffs included in
the school were 6 males and 6 females. Before doing this project the school has no different
websites to do activities easily.
1.3. Backgrounds of the project
In BURIE General Secondary and Preparatory School, most activities are done manually such as
Rank view, student registration, and View exam results. This way of activity is bulky, unreliable,
and unsecure; Data redundancy and loss of data; Need more manpower to process the manual in
the respective offices; Consumes more resources to complete the process which is of high cost
such as stationary material and time; Lack of information to the students.so, we try to reduce this

1
problem and enable the office system to have very fast service to their customer by designing
web based student information system for them.
1.4. Statement of the Problems
Currently Burie General Secondary and Preparatory School students system is manual based.
Due to this manual system, many problems occur. It includes:
 It is difficult to retrieve, edit and find particular information.
 Data recording system is not centralized
 It creates wastages of resources (Stationary material and time).
 Data redundancy and loss of data.
 Need more manpower to process the manual.
 Students are not available 24 hours of the day to get information.
 Customers wait more time to get services.
 Data are vulnerable to theft and natural disaster.
1.5. Objective
1.5.1. General Objective
The main objective of the project is to develop web based students information system for Burie General
Secondary and Preparatory School.

1.5.2. Specific Objective

To achieve a general objective mentioned above the project will have the following specific
objectives in hand.
 Gathering requirement about the existing system to know problems and to find solution for
the problems.

 To analysis and design the system.

 To design a search module to find all information easily.

 To develop the online registration system module

 To design system that performs tasks easily like:-add, delete, modify existing records and
to make it easy to retrieve, edit and find information easily.
 To design automated data base to decrease loss of data.
 To design a system that decreases wastage of resources.

 To design a user-friendly user interface and interactive system

2
  To develop a system that is available 24 hours every day everywhere.
 To design a system that provide fast access

 To design the proposed system using UML diagram.

 To design system that does not vulnerable data from theft and natural disaster.
 To test the system.

 Recommend for the future work.

1.6. Scope of the Project

This project mainly focused on web based Student information system in Burie General
Secondary and Preparatory School. It doesn‟t cover online exam and class scheduling, online
payment, and doesn‟t support for distance students. The system to be developing tries to provide
full information, which focuses on the following some areas.
 Manage account of the user with different privilege.
 Store all the students „data (status) on database.
 Display student‟s status (rank).
 Students able to view rank, assessment, transcript and report card.
 Parents can access student‟s status such as average, rank.
 To share information and idea between school and parent.

1.7. Significance of the Project

Some of the significance of the proposed system is:
 Minimize the processing time or increasing speed of activity
 Simple to all internet user and avoiding data loss
 Reduce cost and human effort
 Avoid document missing and material wastage.
 Identifying the problem under the existing system.

3
1.8. Methodology
1.8.1. System requirements

1.8.1. 1. Software requirements

Tools Reason
MS-window and Linux For documentation,
implementation and To run
our system. They are
familiar operating system.
MySQL To design database. It runs
on virtually all platforms
WAMP server Using for database
connectivity.
Intel(R) Core(TM) i3-2328M Currently available processor
CPU@2.20GHz 2.20GHz type
MS-word, MS-PowerPoint used for documentation and
presentation

EDRAW Max To draw UML diagram

Notepad++ To write PHP script

Table 1: Development tools

1.8.1.1.1. Software development process

 Iterative Development
The reason for choosing this development process is to allow more flexibility for
changes. I.e. By working iteratively, our project team goes through a cycle
where they evaluate each iteration and determine what changes are needed to
produce a satisfactory end product. It cycles through requirement gathering,
system analysis, system design, implementation and testing and can take
feedback for each phase.

4
1.8.1.2. Hard ware tools
Component Requirements Reason
Computer And Processor 500MHZ processor or To develop the system.
higher
Flash 16GB To back up data
paper 1 Desta A4 paper To store the documents in the
form of hard copy.
Printer To print (make soft copy to hard
copy) documentation.
Table 2: Development hard ware tools

1.8.1.3. Programming Language

Activities Programs Reason
Client side coding HTML, CSS  To develop user
interfaceeasy to use and
Client side scripting JavaScript
maintain, Platform
Server side scripting PHP
Independent.

Table 3Development programming language

1.8.2. Data collection methodology

To develop the proposed system, we will collect different types of data. To collect data that are
important to develop our system, we will use different kind of mechanisms.
Practical Observation: -To get additional information about the existing system, we observe it
physically.
Interview: -To get the basic information and background information about the existing system
and structure we ask different question fromthe Director of the School orally.
Document analysis: -To get more information about Student Information System, how it
processed manually, we refer documents and reading materials from the school.

5
1.8.3. Analysis and Design Methodology
We used object oriented analysis and design approach for modeling and Designing the modules
of the proposed system. The main reason behind using OOAD is:
 In order to check the reusability of the current Student Information System.
 It supports inheritance.
 Objects are easier to understand.
 In order to define new or modified objects that can be combined with the current Student
Information System in the Students.

6
Chapter Two

1. System Analysis
1.1. Overview of The existing system
Burie General Secondary and Preparatory School has a collection of manual files to store
student‟s record. Due to this, many problems happen like, Data storage problem (it needs much
physical space, unmanageable, highly exposed for catastrophic failure), Efficiency Problem
(wastage of many materials such as paper, pen, binders (to organize the manual files), and budget
of the school), loosing of teachers and students document, and it is highly prone to errors to
prepare transcripts of students and to update student data. There is a very inefficient and
uncomfortable way of storing and searching records which greatly slow down the flow of critical
information as well as makes looking up of information.

Users of existing system

Director Vice Record Home Teac Student Pare Administrator
Director Officer Room her nt
Teacher
Create account 
Activate, 
Deactivate and
update
Account

post Notice 
View All 
Information
Manage club 
Registration 

7
Update Student 
status
Prepare Transcript 
Calculate total, 
average, and rank
View Notice       
Register To Club   
View Mark  
View Transcript  

Table 4. Users of existing system

2.2. System Requirement specification

2.2.1. Functional Requirement
Functional requirement describes the way in which the system provides its service in
general. The proposed system can be providing the following task:
 User’s registration: This is used for record officer of the school to register users.
 Prepare transcript: This is used for record officer of the school to generate transcript.
 View transcript: used for students to view transcript from record office of the school.
 Save and update mark: which is used to display mark of students and other information
of the school that is updated every time.
 Manage club and register members: students can register to the club of the school.
 Manage account for user: the Administrator create, update, and deactivate account for
all actors of the system.
 Prepare and Post Notice: Director can prepare and post different notices.
 Generate student report: home Rome teacher fill the form of student card, total, average,
rank
 View Notice: Students can view notice
 View all information: Director can view all information.

2.2.2. Non- Functional Requirements

Some of the non-functional requirements of our system are:
System performance
8
 Our system has good performance in the case of the following:
 Our system support every user can access the system with authentication easily.
 User can access the system in 1 second.
 It supports multi-user
 It is available all the time
Usability
 More efficient to use:-it takes less time to accomplish a particular task.
 Easier to use:-operation can be used by observing the object since our system uses
graphic user interface.
Security Requirement
 The system support user name and password to authenticate.
 The system administration must grant and revoke privilege of the user.
Response time:-During the time of accessing the system, our system response for a user with in
short period of time (10 m/sec).
Reliability:-our system is available 24 hours a day, 7 days a week. Easily recover from error by
validating user input.
Scalability:-If the number of users increases in the institution it does not effect on the database
size.
Compatibility or Supportability:-This enables for all operating system and hardware machines
the system must support since our system is developed with PHP .i.e. platform independent.

2.2.3. Business Rule

BR1: Student must attach previous grade exam result before register.
BR2: Record officer must determine registration date.
BR3: Parents have access to their children‟s education records.
BR4: Students can view educational records.
BR5: information of students must be secreting for unauthorized user.
BR6: Student must registered by filling the necessary qualification.
BR7: class room teachers fill marks of student on the data base.

9
2.2.4. Change case
Change case describes a potential requirement that our system may need to
support in the future.
 Likely future changes (update) to either system, in terms of its capabilities and
properties are compatible with the new version.
 Our system can update easily with the new version.

2.3. System Requirement analysis

2.3.1. Actor and Use case identification
Identifying the activities that are mainly performed on the proposed system is the basic
thing in analyzing a new system. Use case gives
 Defining and organizing functional requirements in a system.
 It will help us in defining the role of users.
The following use cases have been identified from the system specification.
 Update Student
 View mark
 Prepare transcript
 Create account
 Add club
 Send feedback
 Student registration
Actor Identification

In our system the following actors are involved: -

 Administrator
 Student
 Director
 V/Director
 Teacher
 Parent
 Home Room Teacher
 Record officer

10
2.3.1.1. Use case diagram

11
Figure 1: Use case

2.3.1.2. Use case Description

Use case number UC01:
Name Teacher registration

Actor Record Officer

Description Record Officer registers Teacher.

Pre-condition Record Office has an account.

Flow of event Actor System

Exception condition
Step1, User writes to login Step2, The system checks the
page. username and password
Step4, Record Office clicks Step3, If it is valid the system
staff/teacher registration link. displays the main page that has
Step7, The user see the record office.
message, the user decided that Step5, The system displays
the staff/teacher is successfully registration form to fill staff
registered. information.
Step6, If it is valid the system
stores the data successfully.
And displays successful
message.
Step2. If user name and password is not valid system display
error message to re-enter information correctly.
Step5, If the information is not valid display error message to re-
enter the correct information.

Post The teacher is successfully registered and he/she is member of

condition the school.

12
Table 5Registration

Use case number UC02:

Use case name Update Student
Actor Record officer

Description The record officer to update student information.

Pre-condition Record officer should have valid user name and password

Actor System
Flow of event Step1: - Record officer login to Step2:- if it is valid system
the system by entering displays fill form.
username and password.
Step3:- Record officer fill
student ID and search. Step5:- if it is valid the system
Step4: - if it is valid, record updates the data successfully.
officer edit the student
information and click update
button.

Exception condition Step1: - if it is not valid system display error message to re-enter
username and password.
Step3: - if ID is not valid system display error message to re-enter
correct ID.
Step4: - if the information is not valid system display error
message to re-enter correct information.
Post condition Updating student information using student id.
Table 6: Update Student

13
Use case number US03:
Use case name View mark
Actor Student

Description Student view mark retrieving from database.

Pre-condition Student must have valid username and password.

Flow of event Actor System

Step1:- student login to the Step2:- system checks whether

system. he/she valid user or not.
Step5:- student enter id and Step 3:- if valid system displays
search mark. the main page.
Step4:- system display to enter id
and search mark.
Step 6:- system check the validity
of the id
Step7: -if the id is valid display
mark.

Exception condition Step2: - if it is not valid system display error message to re-enter
username and password.
Step 6:- if it is not valid system display error message to re-enter the
correct id.

Post-condition Student will able to see all his/her mark.

Table 7: View mark

14
Use case UC04:
number
Use case Prepare transcript
name
Actor Record officer
Description Record officer prepare student transcript that have no empty mark in their
assessment.
Pre- User name and password is needed to enter the system.
condition
Flow of Actor System
event
Step1:- record officer login to the Step2:- system checks authorized user
system or not.
Step4:-user clicks prepare transcript Step3: - system displays the main page.
link Step5:- system displays prepare
Step6:- fill information and view mark transcript page.
Step7:- the system checks the
information is valid or not.
Step8:- if it is valid record officer
prepare transcript.

Exception Step7:- if it is not valid system display error message to re-fill the information.
condition
Post Preparing and showing student transcript.
condition
Table 8: Prepare transcript

15
Use case number UC05:
Use case name Save mark
Actor Teacher
Description Teacher calculates student mark and adds to the data base.
Pre-condition Teacher must have user name and password.
Flow of event Actor System

Step1:-teacher login to the system Step2:- system checks the user is

authorized or not.
Step4:-teacher select mark button Step3:- system displays the main
from the page and select subject. page.
Step6:- teacher fill form and click Step5:- display the form to fill
save button. student mark and click to save
Step8:- teacher see successful register button.
message. Step7:- system stores the mark and
display a message.

Exception Step2- if it is unauthorized system display error message to re-enter

condition username and password.
Post condition Store student mark to the database.
Table 9: save mark

16
Use case number UC06:

Use case name Upload notice

Actor Director

Pre-condition The Director is logged in system. You must have user name
and password.

Description Director uploads notice with the system.

Flow of event Actor System

1. The director browses the 2.The system displays

website. the login form
6. The system verifies
3. The director enters user the requested data.
name and password. 7. The system
4. The director clicks login displays the upload
button. form.
9. The director clicks
5. The director sends data to the upload button
the system. 10. The system
uploaded data to
8. The director notice fills the
website.
form.

Exception condition: 9. If the director fills incorrectly the upload form.

Return to step 7.

Post-condition A new notice is uploaded.

17
 Table 10: Upload notice

Use case number UC07:

Use case name Create Account
Actor Administrator
Description Administrator creates account to teacher, student, and vice director.

Pre-condition Administrator should have user name and password.

Flow of event Actor System
Step1:- Administrator login to the Step2:- system checks the user
system. name and password.
Step4: - user click on the create Step3:- system opens the main page
account link. Step5: - systems open the page.
Step6: - users fill information and Step7: - system checks the value is
create account. valid or not.
Step9: - user see successful message Step8: - if it is valid account
of account created. created.

Exception condition Step7:- if it is not valid system display error message to re-fill the information.

Post-condition Administrator creates account.

Table 11: Create Account

18
Use case number UC08:
Use case name Deactivate Account
Actor Administrator
Description Administrator account of teacher, student, and vice director.

Pre-condition User name and password is needed.

Flow of event Actor System

Step1:-administrator login to the Step2:- system checks the user name

Exception condition
Post-condition
system. and password.
Step4: - user clicks on the Deactivate Step3:- system opens the main page
account link. Step6: - user click Deactivate button.
Step5: - then select status and specific Step7:-account Deactivate of
user. successful message will be displayed.
Step8: - users see the message.
Step2: - if it is not valid display error message to re-enter username and
password
Administrator Deactivate account.

Table 12: Delete Account

19
Use case number UC09:

Use case name Add club

Actor Vice director

Description Vice director add club to the database.

Pre-condition Vice director should have valid user name and password.

Actor System

Flow of event Step1:-vice director login to the Step2:- The system displays main
system by entering username and page of the system.
password.
Step4:- the system displays form of
Step3:- the user clicks on the add the club.
club link.
Step 6:- The system checks the
Step 5:- fill information to the club value is valid or not.
form.
Step 7:- the system displays add
Step 8:- the user clicks on add club club button.
button.
Step 9:- if it is valid the system
Step 10:- the user see the displayed displays a successful message to the
message. user.

Exception condition Step 6:- - if it is not valid system display error message to re-enter valid value.

Post-condition Add clubs to the database.

Table 13: Add club

20
Use case number UC10:

Use case name Send Feedback

Actor Parent

Description Parent wants to add message or feed back

Pre-condition Parent should have valid user name and password.

Flow of event Actor System

Step1:- The parents click on add Step2:- The system displays add
message link. message form.

Step3:- The parent writes message/ Step 5:- The system validates the id
feedback and id of destination. if it is correct format the message
Step4:- The parent clicks on send sends to database.
button.
Step 6:- The system displays
successfully send.

Exception condition Step 5:- if it is not correct format the system asks the parent to rewrite the
id.

Post-condition Parent Feed Back to the database.

Table 14: Send Feedback

21
2.3.1. Sequence diagram

Figure 2: Login sequence diagram

22
Figure 3: Create account sequence diagram

23
Figure 4: prepare card sequence diagram

24
Figure 5. Student registration sequence diagram

25
Figure 6: View mark sequence diagram

26
Figure 7: Save mark sequence diagram

27
Figure 8. Add club sequence diagram

28
Figure 9 View information sequence diagram

29
2.3.2. Activity Diagram

Login

Open home page

Click login link

Type username
and password

Click login button

Invalid username
And password

Login successfully

Figure 5Login activity diagram

30
 Add club

V.Director enter
username
&password

Display
error
message

Click add
club link

Add new
club

Figure 6: Add club activity diagram

31
 Student registration

Student
registration

Student click
registration button

Fill form

Click submit
button

Invalid

You are
successfully

Figure 7: Student registration activity diagram

32
 Prepare transcript

Record office click

prepare transcript

Search student information from

database

Check record

Invalid

Process transcript

Generate transcript

Display and print

Figure 8: Prepare transcript activity diagram

33
 Save mark

Teacher enter name and

password

Display error
message

Teacher click save mark

link

Fill mark and

save

Display error
message

Save mark

Figure 9: Save mark activity diagram

34
 View mark

Student enter name and

password

Display error
message

Click subject and enter ID and

click search button

Display error
message

View mark

Figure 10: View mark activity diagram

35
 Logout

Login

False

Page

Click logout

Display login page

Figure 11: Logout activity diagram

36
 2.3.3. Analysis Class Diagram

User

Fi name
Sec name
Last name
Sex
Age
Address
Class Diagram Phone

*
* * *
*
*
11 1 * 1 1

Student Teacher Director Homeroomteacher

DID
SID TID HRTID
Email
Email
Email
Register () Email
* View Mark ():
ViewTranscript (): * 1
View all Information ():
Upload Notice (): Send Feedback ():
* * * Update Mark (): GenerateFinalResult ():
Save Mark ():
Send Feedback ():
1

1
1
*
* * 1

* 1 1 *

Record Office Parent V/Director Administrator

*

RID * VDID
Email Aid
PID
Email

Create account ():

Activate and deactivate
Teacher Register (): Send Feedback ():
account ():
PrepareTranscript (): View Mark (): Add Club ():
View account ():
Manage (): RegistertoClub ():
UploadNotice ():
Figure 12 Analysis Class Diagram

* *
1

37
CHAPTER THREE

3. System Design
3.1. Design class diagram
This Model used to shows Classes with their attributes, methods, relationship, multiplicity and
Role.

User

-Fi name
-Sec name
-Last name
-Sex
-Age
Class Diagram -Address
-Phone

* * * * *
* 1
11 * 1 1

Student Teacher Director Homeroomteacher

-SID -TID -DID

-HRTID
-Email
-Email -Email
+Register (): String -Email
*
+View Mark (): Float
+View Transcript (): * +View all Information (): 1
Varchar String +Send Feedback (): String
+Upload Notice (): String +GenerateFinalResult ():
* * *
+Update Mark (): Float
+Save Mark (): Float Float
+Send Feedback (): String
1

1
1
*
* * 1
* 1 1 1

Record Office Parent V/Director Administrator

*

-RID * -VDID
-Aid
-Email
-PID
-Email

+Teacher Register ():

VARCHAR +Create account(): string
+Send Feedback (): String +Activate and deactivate
+register parent():varchar +Add Club (): String
+View Mark (): Float account (): string
+PrepareTranscript (): +RegisterClub (): String
VARCHAR +UploadNotice (): String +View account (): string
+register student (): String

* *
1

38
Figure 13. Design class diagram

3.1.2. Design Class diagram descriptions

Class name Attribute/operation Type Description of its purpose

Student SID Identification number for
INT
student.

Fi name First name of student.

VARCHAR
Sec name Second name of student.
VARCHAR
Last name Last name of student.
VARCHAR
Sex VARCHAR Sex of student.
Age Age of student.
INT
Address VARCHAR Address of student.

Phone INT Phone number of student.

VARCHAR
Email Email address for student

Register (): String Student register in record

officer or to club

View Mark (): Float Students can view mark.

ViewTranscript (): VARCHAR Students can view transcript

Table 15: Class Description of student

39
 Class name Attribute/operation Type Description of its purpose
Teacher TID Identification number for
INT
Teacher.

Fi name String First name of Teacher.

VARCHAR
Sec name Second name of Teacher.
VARCHAR
Last name Last name of Teacher.
VARCHAR
Sex VARCHAR Sex of Teacher.
Age Age of Teacher.
INT
Address VARCHAR Address of Teacher.

Phone INT Phone number of Teacher.

Email VARCHAR Email address for teacher.

Update Mark (): Float Teacher updates mark of

student.
Save Mark (): Float Teacher save mark of
student
Send Feedback String Teacher send feedback
():

Table 16:Class Description of teacher

40
 Class name Attribute/operation Type Description of its purpose
Home room HRTID Identification number for home
INT
teacher room teacher.

Fi name First name of home room

VARCHAR
teacher.
Sec name Second name of home room
VARCHAR
teacher.
Last name Last name of home room
VARCHAR
teacher.
Sex VARCHAR Sex of home room teacher.

Age Age of home room teacher.

INT
Address VARCHAR Address of home room teacher.

Phone INT Phone number of home room

teacher.
VARCHAR
Email Email address for home room
teacher
Send Feedback (): String home room teacher send
feedback

GenerateFinalResult Float home room teacher generates

():
final results of students
Table 17: Class Description of Home room teacher

41
 Class name Attribute/operation Type Description of its purpose
Director DID Identification number for
INT
Director.

Fi name First name of Director.

VARCHAR
Sec name Second name of Director
VARCHAR
Last name Last name of Director.
VARCHAR
Sex VARCHAR Sex of Director.

Age Age of Director.

INT
Address VARCHAR Address of Director.

Phone INT Phone number of Director.

VARCHAR
Email Email address for Director

View all String Director view all information

Information ():

Upload Notice () String Director uploads notice

Table 18: Class Description of director

42
 Class name Attribute/operation Type Description of its purpose
Record Officer RID Identification number for
INT
Record Officer.

Fi name First name of Record Officer.

VARCHAR
Sec name Second name of Record
VARCHAR
Officer
Last name Last name of Record Officer.
VARCHAR
Sex VARCHAR Sex of Record Officer.
Age Age of Record Officer.
INT
Address VARCHAR Address of Record Officer.

Phone INT Phone number of Record

Officer.
VARCHAR
Email Email address for Record
Officer
PrepareTranscript VARCHAR Record Officer prepare
():
transcript for students
Teacher Register VARCHAR Record Officer registers
():
teachers
Manage (): String Record Officer manages
account for user
Table 19: Class Description of Record officer

43
 Class name Attribute/operation Type Description of its purpose
Vice director VDID Identification number for Vice
INT
director.

Fi name First name of Vice director.

VARCHAR
Sec name Second name of Vice director
VARCHAR
Last name Last name of Vice director.
VARCHAR
Sex VARCHAR Sex of Vice director.

Age Age of Vice director

INT
Address VARCHAR Address of Vice director

Phone INT Phone number of Vice director.

VARCHAR
Email Email address for Vice director

Add Club (): String Vice director add club list

Register to Club String Vice director registers club

(): members
Upload Notice String Vice director upload notice
():

Table 20: Class Description of Vice director

44
 Class name Attribute/operation Type Description of its purpose
Parent PID Identification number for
INT
Parent.

Fi name First name of Parent

VARCHAR
Sec name Second name of Parent
VARCHAR
Last name Last name of Parent.
VARCHAR
Sex VARCHAR Sex of Parent.

Age Age of Parent

INT
Address VARCHAR Address of Parent

Phone INT Phone number of Parent.

Send Feedback String Parent sends feedback to

(): school.

View Mark (): Float Parent view marks of their

children.
Table 21: Class Description of parent

45
 Class name Attribute/operation Type Description of its purpose
Administrator Aid Identification number for
INT
admin.

first name First name of administrator

VARCHAR
middlname middle name of administrator
VARCHAR
lastname VARCHAR Last name of administrator

age INT Age of administrator

sex VARCHAR Sex of administrator

proffesion VARCHAR Proffesion of administrator

level VARCHAR Level of administrator

Phone number INT Phone number of administrator

Table 22: Class Description of Administrator

46
3.2. User interface design
Our system contains different user interface. That enables users to perform their activity
effectively and efficiently. The interface designed based on user‟s preference of colors, visibly
and suitability. Some of the interface such as Home page, Login form, Feedback, club registrat

Figure 14. Home UI

47
Figure 15. Login form UI

Figure 16. Feedback form UI

48
Figure 17. Club member registration UI

49
3.3 System architecture (Deployment diagram)
To model the hardware details for a client/server system.

Describe the hardware components used to deploy software components

Figure 18.Deployment diagram

50
CHAPTER FOUR
4.1. IMPLEMENTAION

4.1.1. Overview of programming language used

Table 22. Programming language used

Activities Programs Reason

Client side coding HTML, CSS  To develop user interface
Client side scripting JavaScript easy to use and maintain,
Server side scripting PHP Platform Independent.

4.1.2. Algorithm used

Pseoudocode for login

Steps/procedure

Method name=login

Begin

Variables:-username

-password

If (*inputs are valid*)

(*select the previous username and password from database and compare with entered*)

If username = entered username and

Password = entered password

(*go to login page*)

Otherwise

Display “incorrect password or user name please try again!”

End
51
4.1.3. Sample code
Add mark php code

<?php

include("../../../student/all/config.php");

session_start();

$t_id = $_SESSION['username'];

$sec_id = null;

$crs_id = null;

$semister = null;

if(isset($_POST['submit'])){

$sec_id = $_POST['section'];

$crs_id = $_POST['course'];

$semister = $_POST['semister'];

?>

<html>

<head>

<link rel="stylesheet" href="../../all/css/selam.css">

<style type="text/css">

table.style2 th{

padding: 10px;

color: white;
52
background: -webkit-linear-gradient(top,#005cb7 0%,#222222 100px);

table.style2 td{

padding: 5px;

</style>

<style>

input:invalid {

border: 2px dashed red;

input:valid {

border: 2px solid black;

</style>

<script type='text/javascript'>

function formValidator(){

//quize test assesment mid final

var quiz=document.getElementById('quiz').value;

var test=document.getElementById('test').value;

var assesment=document.getElementById('assesment').value;

var mid=document.getElementById('mid').value;

53
var final=document.getElementById('final').value;

if(quiz==""){

alert('please fill mark ');

return false;

if(test==""){

alert('please fill mark ');

return false;

if(assesment==""){

alert('please fill mark ');

return false;

if(mid==""){

alert('please fill mark ')

return false;

if(final==""){

alert('please fill mark ');

return false;

54
}

</script>

</head>

<body background="../../all/images/bt.jpg">

<table id="table5"><tr><td colspan="3">

<img src="../../all/images/burie1.jpg" width="100%" height="210px" id="im2"/></td></tr>

<tr>

<td colspan="3" height="10%" width="100%" id="Menus">

<ul>

<li><a href="../../all/teacher101.php">Home</a></li>

<li><a href="#">View</a>

<ul>

<li><a href="../../all/teacher/viewsection.php">section</a></li>

<li><a href="../../all/teacher/viewcourse.php">course</a></li>

<li><a href="../../all/teacher/viewnotice.php">notice</a></li>

</ul>

</li>

<li><a href="#">Manage</a>

<ul>

<li><a href="../../all/teacher/addmark101.php">Add Mark</a></li>

<li><a href="../../all/teacher/updatemark101.php">Update Mark</a></li>

55
 </ul>

</li>

<li><a href="../../all/teacher/changePass101.php">Change Password</a></li>

<li><a href="../../all/logout.php">Logout</a></li>

</ul>

</td>

</tr>

<tr>

<td bgcolor="#DCDCDC" id="calander1" width="4%" height='100%'>

</td>

<td id="table3" width="65%" rowspan="2">

<form onsubmit='return formValidator()' action="" method="POST">

<table border="1" class="style2">

<tr>

<th>Student ID</th>

<th>Student Name</th>

<th>Course Title</th>

<th>Semister</th>

<th>Quiz(10)</th>

<th>Test(10)</th>

56
 <th>Asses(15)</th>

<th>Mid(25)</th>

<th>Final(40)</th>

<tr>

<tr>

<?php

$db=mysqli_connect('localhost','root','','studentinfo');

$sql = "SELECT * FROM course c,newstudent s,stud_section ss

WHERE c.cid = '$crs_id' and ss.seid = '$sec_id' and s.admission = ss.admission ";

$query = mysqli_query($db,$sql) or die(mysqli_error($db));

while($row = mysqli_fetch_array($query)){

?>

<input type="hidden" value="<?php echo $row['admission']; ?>"

name="stud_id" size="8">

<input type="hidden" value="<?php echo $row['cid']; ?>" name="crs_id">

<input type="hidden" value="<?php echo $semister ?>" name="semister">

<input type="hidden" value="<?php echo $sec_id ?>"

name="section">

<td><?php echo $row['admission'] ?></td>

<td><?php echo $row['stu_fname'].' '.$row['stu_mname'] ?></td>

<td><?php echo $row['C_name'] ?></td>

57
 <td><?php echo $semister ?></td>

<td><input type="number" name="quiz" id="quiz" min="0"

max="10" pattern='\d'></td>

<td><input type="number" name="test" id="test" min="0"

max="10" ></td>

<td><input type="number" name="assesment" id="assesment"

min="0" max="15" pattern='\d'></td>

<td><input type="number" name="mid" id="mid" min="0"

max="25" pattern='\d'></td>

<td><input type="number" name="final" id="final" min="0"

max="40" pattern='\d'></td>

</tr>

<?php

?>

<?php

if(isset($_POST['save_mark'])){

58
 $db=mysqli_connect('localhost','root','','studentinfo');

$std_id = $_POST['stud_id'];

$crs_id = $_POST['crs_id'];

$semister = $_POST['semister'];

$section = $_POST['section'];

$quiz = $_POST['quiz'];

$test = $_POST['test'];

$assesment = $_POST['assesment'];

$mid = $_POST['mid'];

$final = $_POST['final'];

$total = $quiz+$assesment+$test+$mid+$final;

$sql = "INSERT INTO

mark_store(Stud_id,crs_id,Semister,Quize,test,Assesment,Mid,Final,section,total)

VALUES('$std_id','$crs_id','$semister','$quiz','$test','$assesment','$mid','$final','$section',
'$total')";

$query=mysqli_query($db,$sql);

if($query)

echo "<script>alert('New Mark has been inserted!')</script>";

echo "<script>window.open('addmark101.php?view_cats','_self')</script>";

59
 else

echo "<script>alert('Mark is already inserted!!')</script>";

echo
"<script>window.open('addmark101.php?view_cats','_self')</script>";

?>

</table>

<input type="submit" value="Save Mark" name="save_mark" id="save_mark" >

</form>

</div>

</td>

<td bgcolor="#DCDCDC" id="calander1" width="4%" height='100%'>

</td>

</tr

<tr>

<td height="10%" width="100%" colspan="3" bgcolor="gray" id="footer1" align="center" >

BURIE GENERAL SECONDARY AND PREPARATORY SCHOOL STUDENTS

INFORMATION SYSTEM &copy; 2011 E.C.

</font>

</td>

60
</tr>

</table>

</body>

</html>

Figure 19. screenshot for add mark first page

Next page

<?php

include("../../../student/all/config.php");

session_start();

$t_id = $_SESSION['username'];

$sec_id = null;

$crs_id = null;

$semister = null;

61
if(isset($_POST['submit'])){

$sec_id = $_POST['section'];

$crs_id = $_POST['course'];

$semister = $_POST['semister'];

?>

<html>

<head>

<link rel="stylesheet" href="../../all/css/selam.css">

<style type="text/css">

table.style2 th{

padding: 10px;

color: white;

background: -webkit-linear-gradient(top,#005cb7 0%,#222222 100px);

table.style2 td{

padding: 5px;

</style>

<style>

input:invalid {

62
border: 2px dashed red;

input:valid {

border: 2px solid black;

</style>

<script type='text/javascript'>

functionformValidator(){

//quize test assesment mid final

var quiz=document.getElementById('quiz').value;

var test=document.getElementById('test').value;

varassesment=document.getElementById('assesment').value;

var mid=document.getElementById('mid').value;

var final=document.getElementById('final').value;

if(quiz==""){

alert('please fill mark ');

return false;

if(test==""){

alert('please fill mark ');

63
 return false;

if(assesment==""){

alert('please fill mark ');

return false;

if(mid==""){

alert('please fill mark ');

return false;

if(final==""){

alert('please fill mark ');

return false;

</script>

</head>

<body background="../../all/images/bt.jpg">

<table id="table5"><tr><td colspan="3">

<imgsrc="../../all/images/burie1.jpg" width="100%" height="120px" id="im2"/></td></tr>

<tr>

64
<td colspan="3" height="10%" width="100%" id="Menus">

<ul>

<li><a href="../../all/teacher101.php">Home</a></li>

<li><a href="#">View</a>

<ul>

<li><a href="../../all/teacher/viewsection.php">section</a></li>

<li><a href="../../all/teacher/viewcourse.php">course</a></li>

<li><a href="../../all/teacher/viewnotice.php">notice</a></li>

</ul>

</li>

<li><a href="#">Manage</a>

<ul>

<li><a href="../../all/teacher/addmark101.php">Add Mark</a></li>

<li><a href="../../all/teacher/updatemark101.php">Update Mark</a></li>

</ul>

</li>

<li><a href="../../all/teacher/changePass101.php">Change Password</a></li>

<li><a href="../../all/logout.php">Logout</a></li>

</ul>

</td>

</tr>

65
<tr>

<td bgcolor="#DCDCDC" id="calander1" width="4%" height='100%'>

</td>

<td id="table3" width="65%" rowspan="2">

<form onsubmit='return formValidator()' action="" method="POST">

<legend style="font-size:25px;color:red;">These students are <?php

$db=mysqli_connect('localhost','root','','studentinfo');

$sql = "SELECT * FROM section s,gradeg,teacher_sectiontc Where s.gid=g.Gid

and tc.t_id = '$t_id' and tc.s_id = s.se_id ";

$query = mysqli_query($db,$sql);

while($row = mysqli_fetch_array($query)){

?>

<option value="<?php echo $row['se_id']; ?>" ><?php echo $row['year'].'

'.$row['G_name'].' '.$row['se_name']; ?></option>

<?php

?></legend>

<table border="1" class="style2">

<tr>

<th>Student ID</th>

<th>Student Name</th>

<th>Course Title</th>

66
 <th>Semister</th>

<th>Quiz(10)</th>

<th>Test(10)</th>

<th>Asses(15)</th>

<th>Mid(25)</th>

<th>Final(40)</th>

<tr>

<tr>

<?php

$db=mysqli_connect('localhost','root','','studentinfo');

$sql = "SELECT * FROM course c,newstudent s,stud_section ss

WHERE c.cid = '$crs_id' and ss.seid = '$sec_id' and s.admission = ss.admission ";

$query = mysqli_query($db,$sql) or die(mysqli_error($db));

while($row = mysqli_fetch_array($query)){

?>

<input type="hidden" value="<?php echo $row['admission']; ?>"

name="stud_id" size="8">

<input type="hidden" value="<?php echo $row['cid']; ?>" name="crs_id">

<input type="hidden" value="<?php echo $semister ?>" name="semister">

<input type="hidden" value="<?php echo $sec_id ?>"

name="section">

67
 <td><?php echo $row['admission'] ?></td>

<td><?php echo $row['stu_fname'].' '.$row['stu_mname'] ?></td>

<td><?php echo $row['C_name'] ?></td>

<td><?php echo $semister ?></td>

<td><input type="number" name="quiz" id="quiz" min="0"

max="10" pattern='\d'></td>

<td><input type="number" name="test" id="test" min="0"

max="10" ></td>

<td><input type="number" name="assesment" id="assesment"

min="0" max="15" pattern='\d'></td>

<td><input type="number" name="mid" id="mid" min="0"

max="25" pattern='\d'></td>

<td><input type="number" name="final" id="final" min="0"

max="40" pattern='\d'></td>

</tr>

<?php

?>

<?php

if(isset($_POST['save_mark'])){

$db=mysqli_connect('localhost','root','','studentinfo');

$std_id = $_POST['stud_id'];

$crs_id = $_POST['crs_id'];

68
 $semister = $_POST['semister'];

$section = $_POST['section'];

$quiz = $_POST['quiz'];

$test = $_POST['test'];

$assesment = $_POST['assesment'];

$mid = $_POST['mid'];

$final = $_POST['final'];

$total = $quiz+$assesment+$test+$mid+$final;

$sql = "INSERT INTO

mark_store(Stud_id,crs_id,Semister,Quize,test,Assesment,Mid,Final,section,total)
VALUES('$std_id','$crs_id','$semister','$quiz','$test','$assesment','$mid','$final','$section',
'$total')";

$query=mysqli_query($db,$sql);

if($query)

echo "<script>alert('New Mark has been inserted!')</script>";

echo "<script>window.open('addmark101.php?view_cats','_self')</script>";

else

echo "<script>alert('Mark is already inserted!!')</script>";

69
 echo
"<script>window.open('addmark101.php?view_cats','_self')</script>";

?>

</table>

<input type="submit" value="Save Mark" name="save_mark" id="save_mark" >

</form>

</div>

</td>

<td bgcolor="#DCDCDC" id="calander1" width="4%" height='100%'>

</td>

</tr

<tr>

<td height="10%" width="100%" colspan="3" bgcolor="gray" id="footer1" align="center" >

BURIE GENERAL SECONDARY AND PREPARATORY SCHOOL STUDENTS

INFORMATION SYSTEM &copy; 2011 E.C.

</font>

</td>

</tr>

</table>

</body>

70
</html>

Figure 20. screenshot for add mark page second page

71
CHAPTER FIVE
5.1. Testing
Testing the next phase from the implementation in which specified to check whether the function
is correct or not for the developer intended and user expected system can achieve. We can use
different type of testing strategies.

5.1.1. System Testing

System test insures that the entire integrated software system meets requirements. It tests a
configuration to insure known and predictable results.

5.1.1.1. Performance Testing

The system can perform with a short bandwidth response time and also they can perform or
accomplish specific task within the user intended and they can store user expected resources.

5.1.1.2. Security Testing

The system has a security protection by using authentication. User of the system will be
authorized by the system administrator and get their user name and password to enter into the
system. Unauthorized access will be detected when user wants to access the system. This is done
by authenticating user; user with user name and password can only enter into the system.

72
Figure 21. Screen shoot for login with incorrect username and password
5.1.1.3. Testing the Accuracy
The system gives only valid result, if no data is found or enter incorrect entity with the specified criteria,
the system should give appropriate response. Since, our application fulfills these characteristic it is
accurate.

73
Figure 22. Screen shoot for create account
5.1.2.Unit testing
First we will tests each unit at each system. Each modules of the system can be tested
check the working of each classes, methods and attributes of the system. For immediately
maintain at which the problem is occurred.

74
Test case 1:-for authentication of user login

Table 23.authentication for user login

Unit test=authentication of login user

Assumption =login to the appropriate page

Test data=username, password(empty,valid,invalid)

Steps to be executed Test data Expected result

Empty username, password Username=” ”,password=” “ Please enter

valid username
and password

Valid username, invalid password Username=1000Password=1 Please enter

2 valid password

Valid password invalid username Password=teacherUsername Please enter

=us valid username

Valid username and password Username=10000 Open new

password=teacher page

75
5.1.3. Integration Testing

The modules can be independent to each other cannot be contradict with the user accessed data.
Modules are typically integrated a top-down incremental fashion. In this testing mechanism each
form is tested by a general data. Like login form Check the correctness of the form to be
displayed after login is succeeded that means user expected or intended application.

5.1.4. Validation Testing

When we say valid it is to mean that the software functions as it is intended. The group team can
test by giving real data and get real information from the software. Like all forms can be validate
the functionality. The user can expected to provide the function required by the form

76
CHAPTER SIX
6.1. CONCLUSION AND RECCOMENDATION

6. 1.1.Conclusion
We have already developed a website or web-based application for student information system.
It provides much functionality for its users. For example, it enables students to view mark, view
status and it also enables the administrator to manage events and students record on the system.

As project come up to the end. We pass all software development life cycles. Start from system
specification up to system testing and at each stage system development we understand clearly
what to be done and what need to be done each tasks. For example, in analysis, we tried to model
the new and proposed system using UML diagrams: - use case diagrams, sequence diagrams,
class diagrams and Activity Diagram. And from this we understand how to model the system.

In general, the project (system) that the team developed will benefit the school by changing it‟s
from manual to online level.

The overall benefits of the system to the school are:

provide sufficient security
Minimize the time required to perform task.
Reducing human power and cost that are spent on the manual system.
As a system developing team the group member has acquired more knowledge and experience
about the different phases of the software development life-cycle. As software developers, the
team has worked together and assessed risks, and minimizes them.

6.1.2. Recommendation
We try to solve the existing system of student information management system as much as
possible, but some concept is not included in our project due to the shortage of time and
resource. Our group members try to puts those concepts that are not solved by the proposed
system as a recommendation as follow:

77
It doesn‟t cover online exam and class scheduling, taking attendance, online payment, and
doesn‟t support for distance students .So we recommend for the next project designer to consider
these things.

6.2.3. Future Enhancement

For the future as the services of the associations becomes increased, this system should be
improved by adding functions and using better technologies. So, future works that the project
team proposed are:

 Maintaining the system according to the services of the organization after

applying and testing the acceptance of the project by the organization.
 Connecting the system with other school organizations.
 Appling better security mechanisms.
 It is better to use android in order to be more applicable.

References
1. Wikipedia. .Sequence diagram. Last edited on 13 December 2017, at 22:46. From
https://en.wikipedia.org/wiki/Sequence_diagram
2. www.w3scchol.com: to Design user interface. from
https://www.w3schools.com/css/css3_user_interface.asp
3. www.ofnisystems.com to Functional-requirement. from
http://www.ofnisystems.com/services/validation/functional-requirements/
4. www.medium.com. Object-Oriented Analysis and Design from
https://medium.com/omarelgabrys-blog/object-oriented-analysis-and-design-introduction-part-1-
a93b0ca69d36
5. BOOCH.G (1998). Object-oriented analysis and design.Welseley.Addison: USA.
6. www.creately.com.Unified Modelling Language. From
http://creately.com/blog/diagrams/uml-diagram-types-examples/
7. System analysis and design Tutorial points pdf
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutori
al.pdf
8. System analysis and design from
https://www.scribd.com/doc/7325348/Systems-Analysis-and-Design-Full-Book-1

78