UNIVERSITY OF GONDAR

FACULTY OF INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
WEB BASED STUDENT INFORMATION MANAGEMENT SYSTEM FOR
EDGETFELEG GENERAL SECONDARY SCHOOL

BY:
1. Chalachew Ejigu-----------8587/08

2. Lakech Tadesse------------8610/08

3. Getienat Demeke-----------8598/08

4. Silenat Getahun -----------6921/07

5. Eyerus Dagnew------------6834/07

DECEMBER 2019

GONDAR, ETHIOPIA
 CHAPTER ONE

1 INTRODUCTION

1. 1 Background of the Project

Student information management system(SIMS) is a software system that enable educational
institutions to supervise student-related activities such as keeping records of tests or
examinations conducted, attendance, appraisal on performance including details of marks scored,
particulars of everyday school activities; in short, It is provide a complete student records
system. It is design with diverse application potentials ranging from simple management of
students’ records at school to management of all student-related functions.

Edgetfeleg general secondary school is one of the secondary schools in Gondar city
administration.

In fact the students information in Edgetfeleg general secondary school is now manage in
manually (paper work). This manual system makes many problems like: - time consume, need
many number of workers, unsatisfaction of customer, requires wide space to put paper files, etc.

To solve those problems, another mechanism is important. So, we propose that mechanism, we
call it, web based student information management system (SIMS) in Edegetfeleg general
secondary school. This SIMS can solve the problem mention above by registering all information
of each student from starting grade 9th up to leaving the school.

1.2 Overview of the project

This SIMS plays a great role to solve the manually (paper work). This project is mainly focus
students data and class scheduling. This project clarifies the school director activities, the
teachers’ activities, the students’ activities and the data recorder office activities. Most activities
require approval from the director because of ensure the security.
1.3 Statement of the problem

In Edgetfeleg general secondary school there is no computerized (automated system) which

provides a service of student information. Thus in the school all activities that relate to student
information is going to do manually. With the current systems the level of service is dependent
on individuals and this puts a requirement on management to run training continuously for staff
to keep them motivated and to ensure that they are following the correct procedures.  It can be all
easy to accidentally switch details and end up with inconsistency in data entry or in hand written
orders. Reporting and checking that data is robust can be timely and expensive.

So the SIMS takes more effort and physical space to keep documents in a physical file achieve
place, to find an information about the students are difficult and has a secure problem. When
mistakes are made or changes or corrections are needed, often a manual transaction must be
completely redone rather than just updated.  With manual information tracking systems, the
information often has to be written down and copied or entered more than once. 

Due to this fact the current manual system has the following problems:-

 Lack of information security

 Time consuming during accessing information (not efficiency)
 Lack of integrating data
 The file or the students information is getting lost
 Delay in bringing document for those who need it and updating the required information

Therefore; to solve such kind of problems Edegetfeleg secondary school needs an automated
SIMS.

Edgetfeleg general secondary school has many problems like:-equipment handling mechanism,
finance handling mechanism, large class size(number of students in a class), etc. One of the
problems is student information handling mechanism. This mechanism is manual work (paper
work). Each student’s information is record in paper and cover by one hard paper and stores it
in one room. Most problems this mechanism is:- Time consuming, Tedious paper work, There is
possibility for loss of record, It is difficult to update.

1.3 Objective of the Project

1.3.1 General objective

The general objective of this project is to develop a web based student information management
system for Edgetfeleg general secondary school.

1.3.2 Specific objective

In order to achieve the general objective of this project, the following specific objectives are
addressed.

 Understanding the business process of the current manual work

 Conducting the requirement analysis and specification followed by requirement gathering
 Identifying the functional and non-function requirements of the system
 Designing the complete component of the system
 Developing the implementable version of the system
 Conducting a full deployment of the system
 Testing the developed system with collecting feedback from users

1.4 Scope and Limitation of the Project

1.4.1 Scope of the Project

This project covers the whole data about the Student Information of the Edgetfeleg general
secondary school. This Project includes student record, class schedule, subject’s information.

???1.4.2. Limitation of the Project

The project does not include the following:
 The system does not run on connectionless environment because it is web base.
 The system has not information of administrative staffs in the school.
 The system has not considered plasma program.
  The system does not give online exam.

1.5 Significance of the project

This new system has the following significance:-

 It replaces the manual work to web based system.

 It is more efficient and easy to use.
 Eliminate paper based recording.
 Reduce waiting time
 It eliminate data redundancy
 It eliminate data loss
 It is easy to update students information
 It is easy to search students specific information

1.6 Methodology of the Project

In order to achieve the general and the specific objectives of the project we used the following
methodology.

1.6.1 System Development Method

System Analysis: - is the process of breakdown an entire system into module, analyzing each
module separately, and determining the relationship between them. In system development
process we used system modeling. System modeling is the process of creating a model of system
by analyzing and organizing the system element [5].

System Design: - to design the system we used object oriented method because in object
oriented method, the information are treated and stored permanently as objects.

Development Approach: - the development approach model for this project selects iterative.
The process of development is cyclic manner by repeating every step after every cycle of system
development life cycle (SDLC) process. Iterative approach used to encourage innovation,
increase flexible design, and provide quick implementation of incomplete functionalities [5].

1.6.2 System Development Tools

In this section we mentioned the software and the hardware tools which used to develop a
proposed system.
1.6.2.1 Software Tools
This project is developed using proven tools. These tools are technological products like
computer software programs, interfaces which used to develop software. In this project we used
some technological software and hardware products, to list them specifically:-
Hypertext Pre-processor (PHP): is a server-side scripting language designed primarily for web
development. We used PHP for server side scripting because it runs on different platforms
(windows, Linux, UNIX, etc.) and it is compatible with almost all servers used today apache and
runs efficiently on the server.

Hyper Text Markup Language (HTML): is the standard markup language for creating web
pages and web based systems.

Cascading Style Sheets (CSS): is the language that describes the style an HTML documents or
the presentation of web pages, including colors, layout, and fonts.

JavaScript: is the programming language of HTML and the web that supported by all web
browsers and used on almost every site on the web for more powerful and complex functionality.

MySQL: is an open source relational database management system. It runs as a server and
allows multiple users to manage and create numerous databases. It is central component in the
WAMP stack of open source web application software that is used to create websites. WAMP
stands for Window, Apache, MySQL, and PHP.

1.6.2.2 Hardware tools.

To develop and deploy the proposed or the automated web based system we used the following
hardware tools.
 Personal computer:-for accessibility any time to accomplish the project
 Processor: Intel(R)core(TM)i5-6200U CPU@2.30GHz 2.40GHz
 Flash disk :-for backup purpose
 Paper and pen:-to design the idea roughly before put into computer

1.6.1 System development methodology

To accomplish this project, we follow iterative system development method because it used to
update and correct the system if the error is exist and OOSAD (object oriented system analysis
and design) because of the following reasons:-

 It utilizes full of information about object based and object-oriented programming

language.
 It enables the designer to model the design accurately.
 These techniques can improve the quality of the model.
 These techniques reduce the complexity of the designer.
 These techniques can build the model faster.
 These techniques can provide opportunities for reuse through the concept of
inheritance, polymorphism and encapsulation.
 These techniques improve the quality of the system must be on time.

1.6.2 Data collection techniques

Data collection techniques are used to collect data from different data source (documents, users
and organizations etc.)

The following are the data collection techniques which used for requirement gathering:-

 Primary data source:-

 Direct observation:-as part of the learning process and as a student we have gone
through the observation students’ paper file.
 Interview:-we used interview as one of the major data collection method. During
interview our team got different necessary information from the school director and
office of data record.
 Document analysis:-we analyzed different documents of the project from the school
principal and the concerned body.
 Director office document
 Record office document
 Secondary data source:-
 Internet:-internet aids us to see the available sample on the internet and to download
different types of tutorials which help us in doing the project.
1.7 Tools
The programming tools that the proposal:-

Software requirement:-
 Edraw Max and visual paradigm: - To design sequence diagram,
class diagram, activity diagram and use case diagram.
 Sublime text editor :-used to write HTML code for front end
 Microsoft office word: - It is very useful because it takes less time to
write and format the text, communicative effectively smart diagram
and chart tools, quickly assemble document. By looking its useful
properties we use Microsoft office word to type our project work to get
all the above benefits of it.
 Microsoft Power point: - use to present the document in abstract
forms. We use it to present our presentation in short and brief way.
 JavaScript:-used to handle events because it is client side scripting
language
 CSS:-used to decorate the interface
 PHP:-used to write the back end code(server side scripting language)
to access the database
 WAMP:-it is a software package contains: Apache, MySQL, and PHP
for windows
 MySQL :-used to create database
 Windows operating system: - it is simple to use.

Hardware tools:-

 Personal computer:-for accessibility any time to accomplish the project

 Processor: Intel(R)core(TM)i5-6200U CPU@2.30GHz 2.40GHz
 Flash disk :-for backup purpose
 Paper and pen:-to design the idea roughly before put into computer
1.8 Feasibility of Project
Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.

The document provide the feasibility of the project that is being designed and lists various areas
that were considered very carefully during the feasibility study of this project such as
operational, scheduling, technical and economical feasibilities. The following are its features:

1.8.1 Technical feasibility

The system is technically feasible for the following reasons:-
 The team is commit in developing the system.
 The needed resources like software’s to develop the system are available.
 The needed working place is available.

1.8.2 Economic feasibility

. It has two benefits.

 Tangible benefits:-
 Reduction of paper and pen.
 Reduction of space needed to record data and manipulate.
 Intangible benefit:-
 Give better and effective service.
 Error reduction.
 Increase efficiency

1.8.3 Operational feasibility

The system can be accessed by the users that interact to the system by their computer with
internet connection.

The system can be easily operate by

  Directors
 Record office
 Teachers and it is highly expected to meet the objectives that we specify specifically.

1.8.4 Scheduled feasibility

Scheduled feasibility is the process of assessing the degree to which the potential time frame and
we will try to avoid the problems as much as we can and finish our project as scheduled.

1.9 Project schedule

Table 1.1Workbreakdown Schedule

No Phase
10th 16th 2nd 3rd 21th 22th
Nov- Nov- Jan- Mar- April- May-
15thNov 1thJan 2ndmar 20thApril 21thMay 10th June
1 Proposal preparation

2 Requirement analysis

3 Design

4 Implementation

5 Testing

6 Project closure
 CHAPTER TWO

ANALYSIS

2.1 INTRODUCTION
Analysis is the way of studying a system with an eye on solving its problem using computers. It
is the most essential part of the development of a project of a system analysis. System analysis
consists of system element, process and technology. It is the detailed study of the various
operations performed by a system and their relationships within and outside of the system. A key
question is: What must be done to solve the problem? One aspect of analysis is defining the
boundaries of the system.

After carful observing and analyzing the problem of manual system the team decides to design
and develop the web base student information management system as a solution. Requirement
analysis is the process of determining user expectations for a new system. These requirements
must be quantifiable, relevant and detailed. In software engineering such requirements are often
called functional specification. Requirement analysis is critical to the success of a systems or
software project.

In this section we are going to discusses about the existing system of student information
management, the system that we are going to develop, functional requirements for our system,
non-functional requirements about our system and also some UML diagrams like:- use case
diagram, sequence diagram, activity diagram and class diagram.

2.1 Existing work

2.1.1 Existing work description

The current system of Edgetfeleg general secondary School is generally a manual based system.
Student’s information is executed manually.
Currently, all activity of Edgetfeleg general secondary School Student Information management
is going to done manually by the staff. The student’s document is stored using file cabinets and
suspension filing system for a long period of time. And the home room teacher prepares report
card by filling the form manually and also at preparation of transcript the form filling manually.
So, the project team proposed a new system for students, teachers and homeroom teachers of
Edgetfeleg general secondary School in an environment that have an internet connection .

2.1.2 Major Problems of Existing work

The current system has many problems in the working procedure for the school and users. Like
Student information while keeping results in manual, it can be damaged or lost due to many facts
and during result submission day students may not be there due to some reason. And risk of
management data due to massive data collection and Accuracy not guaranteed, the students must
go and read to get the available information. This takes time and energy for students. And also
the students may not get service of the school twenty-four hours a day and seven days a week.
When generating report, it takes time and it may not be easy to manage and analysis the monthly
work due to massive collection of data and the generated report may not be accurate because of
manually doing.

Moreover, during registration time students are tired, take time and did not get their satisfaction;
Because of many processes in the system to approve their registration.

time table is found to be important to address those problems.

2.1.3 Alternative solution

As we try to describe above the current work faces some problems and the problems primarily
resulted from the manual system of running the activities and we try to put an alternative solution
to the problems which are described in the above problems of existing work section.

 The alternative solution to solve the problems described in the existing work is to
change the work by a new system that simplifies the problems listed the above.
 Use the developed system on web based environment to see properly.
2.2 New System

2.2.1 Overview of the proposed system

The proposed system is very easy to operate and easily handle all the data and the work done by
the existing system. The new system has some functionality which improves the work of the
manual system. Our proposed SIMS will also support: handling inquiries from prospective
students, handling the student details, the student can access their result where ever and
whenever they want, and maintaining the student marks details. It becomes essential to make a
properly managed SIMS so that users can easy access student’s records and get the desired
information easily. In addition to this our proposed system has several advantages including:
User friendly interface, Fast access to database, less error, more storage capacity, search facility,
look and feel environment, quick transaction, Easy to handle and feasible, cost reduction, fast
and convenient and accurate. After maintaining this system, the above problems of the existing
system will be completely solved and means of distributing information is within a short period
of time. The proposed system will also have some other features like: -

 Login system must be present and secured by password.

 Accuracy in the handling of data.
 Fast rate of operation and excellent response time.
 The system is flexible i.e. it can be accessed at any time.
 Accessibility from anywhere.

2.2.2 Functional Requirements

The functional requirement is describing the behavior of the system that relates to the system's
functionality. Functional requirements describe the interaction between the system and its
environment independent of its implementation. Functional requirement is what a system should
be able to do, the functions it should perform. Functional requirements describe what the system
should do.
According to their functionality, the tasks that the SIMS will do are listed as follows:
Prepare and view report card

 The system that allows the student view report card

 The system that allows the home room teacher prepare report card.
Prepare and view transcript

 The system that allows the record officer generate transcript and the administrator
approve the transcript.
 The system that allows the student view transcript.

Attendance

 The system that allows the home room teacher take attendance.
 The system that allows the student view attendance.

Change user name or password

 The system will allow student, teacher, home room teacher, administrator and record
officer to change user name and password

Create an account

The system itself will automatically create a user account to all students, teachers and home
room teachers that means if the student is registration at that time the system create the account
and also the teacher allocate that school the system automatically create an account.

Posting

 The system allows the teacher, home room teacher and also administrator to post.

Validation for user

 The system should have validation for the user name and password.

Checking result

 The system allows the student to check result.

Give feedback

 The system allows all users to give feedback on the system.

 The system allows the administrator to accept and check feedback.
View each subject’s information

 The system allows authorized users to see the information about each subject.

Generating report

 The system allows authorized administrator generate the report.

Deactivate account

 The system allows administrator to terminate accounts of home room teachers when they
are changed.
 The system allows administrator to terminate accounts for teachers who are out of the
school because of different reason.
 The system allows administrator to terminate accounts for students who are out of the
school because of different reasons.

Update account

 The system allows administrator to update user account when it is necessary.

 Users can also update the basic information like user name, password and security code.

2.2.3 Nonfunctional Requirement

Non-Functional requirements describe user visible aspects of the system that are not designated
to the functional behavior of the system. The requirement includes from user interface to
resource issues. As the name suggests, non-functional requirements are requirements that are not
directly concerned with the specific functions delivered by the system. It’s essentially specifies
how the system should behave and works that it is a constraint upon the systems behavior. Non –
functional requirements place restrictions on the product being developed, the development
process, and specify external constraints that the product must meet.

2.2.3.1 User Interface and Human factors

The expert that is required from user is only knowledge of computer usage and interface access.
The interface of the proposed system is very flexible for users. The system uses English language
so that the user is required to know English language to use the system.
2.2.3.2 Performance Characteristics
The proposed system should have fast response time. The system can also support many
concurrent users simultaneously with in best response time. The system must support parallel
transactions involving different clients from different location.

 Response Time: The output should be generated in fast response time.

 Capacity: System should serve many users simultaneously.
 Resource Utilization: The system should utilize minimum amount of CPU and
memory of the device.

2.2.3.3 Error Handling and Extreme Conditions

If the user enters incorrect input like inserting empty string, inserting a duplicated username in to
the database or login with unregistered username and password the system should display an
appropriate message for each error.

The system should handle exceptions listed below

 Login error (unauthorized login): the system shall handle an attempt to login with
incorrect username and password and display appropriate message.
 Submitting Empty String.
 Inserting alphabetic value in integer text field.

2.2.3.4 Quality Issues

 Reliability: The system should work with required accuracy.
 Usability: The System should be user friendly and should require least effort to operate.
 Availability: the system should be available for all working hours (24 hours).
 Portability: should work on any operating systems.
 Flexibility: It is effort required to modify operational program. The whole System should
be made using independent modules so that any changes done in 1 module should not
affect the other one and new modules can be added easily to increase functionality.
 2.2.3.5 System Modifications
As the world is capable of change from time to time; there will be future change to the system as
a result of new technology invention. Therefore, the system can be upgrade to the new
technology by maintainer or the system developers.

2.2.3.6 Security Issues

The system allows only authorized users to access by entering the correct login username and
corresponding password. On the other hand, the system must give a maximum trial of 3 chances
for user to enter their authentication information for logging in to system after 3 chances the
system must block the user from login to the system for 5 minutes. User information like
password should be stored in the database in encrypted form.

2.2.3.7 Resource Issues

 Server: - CPU: 32 bit or 64 bit.
 Client: - CPU: 32 or 64 bit and RAM: 512MB.

2.5 System Model

2.5.1 Scenario

Scenario 1:

Scenario Name: Login

Participating actors: administrator, teacher, home room teacher, student, parent and record
officer.

Flow of event:

 User initiates the system.

 User enters user name and password.
 The system validates user name and password.
 If user name and password is valid, access shall be granted.
 If user name and password is invalid access is denied and then the system display error
message.
 Alternative case:

If the Username and password are invalid, the system displays an error message
and allows the User to try again.

Scenario 2:

Scenario name: approve student registration

Participating actor: Administrator, record officer.

Entry condition: Administrator and record officer logs in to the system by using his account.

Flow of event

 Admin login and record officer to the system.

 Admin click approve Account link and then record officer check all information.
 If student information is valid, record into the database.
 If student information is invalid delete the account request.

Scenario 3:

Scenario name: Delete account

Participating actor: Administrator.

Entry condition: Administrator logs in to the system by using his account.

Flow of event

 Admin login to the system.

 Admin fills the required information (role number, phone number).
 Admin click Delete Account link and the system load the data filling form.
 The system warns the user to delete.

Scenario 4:

Scenario name: generate report

 Participating actor: Administrator

Entry condition: Administrator logs in to the system by using his account.

Flow of event

 Admin login to the system.

 Admin click view report link and the system load the report.
 required information will be displayed for the administrator.

Scenario 5:

Scenario name: Prepare transcript

Participating actor: record officer and administrator.

Entry condition: the record officer and administrator must be login.

Flow of event

 The record officer clicks on prepare transcript button.

 The system automatically creates the form of transcript.
 The system sends transcript request to the administrator.
 The administrator selects approve or delete.
 Then the system sends to the student.

Scenario 6:

Scenario name: Manage result

Participating actor: Teachers

Entry condition: Teachers log in to the system by using his account.

Flow of event

 Teachers login to the system.

 Teachers click manage result link and the system load the Continuous assessment
cumulative mark List form.
  Teachers fill the modified information.
 User clicks the save button system save the information to the student’s data in the
database and notify that the required data is modified.

Scenario 7:

Scenario name: post result

Participating actor: Teachers

Entry condition: Teachers log in to the system by using his account.

Flow of event

 Teachers login to the system.

 Teachers click post link and upload the required file and the system load the data
filling form.
 Teachers fill the required information (data type that he/she want to post, phone
number, role number).
 User clicks the save button then the system sends the required information to the
database and display for the users.

Scenario 8:

Scenario name: Give system feedback

Participating actor: students

Entry condition: Users log in to the system by using their user account.

Flow of event

 Users login to the system and read the information that was posted.
 Users click comment or replay link and the system load the text area to send the
feedbacks of users.
 Users fill the required information (comment).
  User clicks the send button then the system sends the required notification
information to the database.

Scenario 9:

Scenario name: View data

Participating actor: students

Entry condition: Users and log in to the system by using his account.

Flow of event

 Users login to the system.

 Users click view link and then after other links like: conduct, view course, view
schedule, result, attendance and subject information. Then the system loads the data
entry form.
 Users fill the required information (phone number, role number).
 User clicks the send button then the system sends the required information to the
database and the required information will be displayed for the users.

Scenario 10

Scenario name: upload material

Participating actor: teacher

Entry condition: teacher log in to the system by using his account.

Flow of event

 Teacher login to the system.

 Teacher click on Material menu.
 Systems display the form to upload material.
 Teacher selects the material according to the perspective course, level and year.
 Teacher click on upload button then the System displays a message that material is
successfully uploaded.
 2.6 Use Case Model

2.6.1 Use Case Diagram

Use cases are used during requirements elicitation and analysis to represent the functionality of
the system. It focuses on the behavior of the system from an external point of view. It 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). The identification of actors and use cases results in the definition of the boundary
of the system that is, in differentiating the tasks accomplished by the system and the tasks
accomplished by its environment. The actors are outside the boundary of the system, whereas the
use cases are inside the boundary of the system.

figure 2. 1 Use Case Diagram

 2.6.2. Description of Use-Case Model

This part describes what the system must provide to the actor when the use case is executed.

Use case No : UC 1

Description: Login to SIMS

Actors: Teacher, system Admin, Student, director, class room teacher ,parent and record
officer.

Precondition: The user must have a username and password or an account.

Basic course of action:

1) Users open the system.

2) Click on login button on web page.
3) The system prompts the user to enter password and username.
4) The users insert their valid username and password.
5) The system verifies the entered username and password.
6) The System display welcomes the user if user name and password are valid .

Post condition: Login to the system

Alternative:

 If a user entered invalid user name and password; the system displays the appropriate
error message to the user and the system prompts enter again password and
username.

Table 2. 1 Use case description for login

Use case No : UC 2

Description: fill registration form to SIMS

Actors: Student

Precondition: the user must have grade 8 card admission number.

Basic course of action:

 1) Users open the system.
2) Click on sign up button on the web page.
3) The system displays admission number insertion form
4) The system displays signup form and prompts all detail information
5) The users insert valid detail information.
6) The system verifies the entered all information
7) The System display successfully send registration.

Post condition: the student have an account.

Alternative:

 If a user entered invalid admission number and detail information; the system displays the
appropriate error message to the user.

Table 2. 2 Use case description for registration form

Use case No : UC 3

Description: attendance

Actors: class room teacher

Precondition: the teacher must have an account.

Basic course of action:

1) Class room teacher opens the system and login into the system.
2) Click on attendance button on the web page.
3) The system displays the form for record attendance
4) If the student is present record “P” otherwise record “A”
5) The user clicks submit attendance.
6) The System display successfully record attendance.

Post condition: record attendance of the student

Alternative:
  If the teacher record invalid detail information; the system displays the appropriate
error message to the user.

Table 2. 3 Use case description for attendance

Use case No : UC 4

Description: give feedback

Actors: student and parent

Precondition: the user must have visit the page.

Basic course of action:

1) Users open the system.

2) Click on give feedback button on the web page.
3) The system displays give feedback form.
4) Fill feedback form and click submit.
5) Verify filled information. If all filled information are correct save feedback and display
send successfully to the user.

Post condition: give comment for something.

Alternative: In the system found an unfilled feedback box.

1. The system asks user to fill the form again.

2. Use case continues at step 3 in the basic action

Table 2. 4 Use case description for feedback form

Use case No : UC 5

Description: submit student result

Actors: Class room teacher and teacher

 Precondition: teacher and Class room teacher must be record student result.

Basic course of action:

1) Teacher and class room teacher open the system and login the system.
2) Teacher and class room teacher click on submit result button.
3) The system displays the submit result form.
4) Teacher and class room teacher fills the information and submits the result.
5) The system added to the student’s result in to database
6) The system displays send successfully message.

Post condition: add the student result on the database successfully

Alternative: if the subject teacher and class room teacher fills invalid information

1. The system displays error message and return to step3.

Table 2. 5 Use case description for submit result form

Use case No : UC6

Description: post notice

Actors: Teacher, director and class room teacher

Precondition: the user must have account

Basic course of action:

1) Teacher, director and class room teacher open and login the system.
2) Teacher, director and class room teacher click on post notice button.
3) The system displays the post notice form.
4) Teacher, director and class room teacher fills the information and submits the post.
5) The director must approve for teacher and class room teacher notice post
6) The system checks all information and then post notice added in to database
7) The system displays message.

Post condition: add the post notice on the database successfully

 Alternative: if the teacher, director and class room teacher fills invalid information

2. The system displays error message and return to step2.

Table 2. 6 Use case description for post notice

Use case No: UC 7

Description: logout

Actors: Student, director, class room teacher, teacher , parent , systemadmin and record officer.

Precondition: All must be login in to the system.

Basic course of action:

1) User click logout button.

2) System destroys session ID.

Table 2. 7 Use Case Description for Logout

Use case No: UC 8

Description: schedule class

Actors: director

Precondition: the director must have an account

Basic course of action:

1) director clicks on schedule class button.

2) System display the form to schedule class.
3) director fill the form.
4) Director click submit button.
5) The system display message.
Post condition: The schedule is submitted to Database.

Table 2. 8 Use Case Description for schedule class

Use case No: UC 9

Description: View class schedule

Actors: teacher, Student, director and class room teacher

Precondition: Login to the system

Basic course of action:

1) User Click on view class Schedule Button.

2) The system displays the schedule form.
3) User selects grade and level.
4) The system displays the schedule.
5) The user view and navigate
Post condition: teacher, Student, director and class room teacher get class schedule information

Table 2. 9 Use Case Description for View class schedule

Use case No: UC 10

Description: generate transcript.

Actors: record officer, director and class room teacher.

Precondition: the record officer, director and class room teacher must login the system.

Basic course of action:

1) record officer, director and class room teacher clicks on generate transcript Button.
 2) The system display form to generate transcript.
3) record officer, director and class room teacher selects grade and section.
4) record officer, director and class room teacher clicks submit generate transcript.
5) The system displays the form to director to approve generate transcript.
6) The director approves the transcript.

Post condition: record officer, director and class room teacher successfully generate transcript.

Table 2. 10 Use Case Description for generate transcript

Use case No: UC 11

Description: manage user account

Actors: system admin

Precondition: system admin must login the system

Basic course of action:

1) system admin must login into the system.

2) system admin clicks mange user account Button.
3) The system display form to select add, remove, update link to manage the user account.
4) The system admin fills all information about the manage user account.
5) system admin r click submit manage user account.
6) The system displays manage user account successfully if the system admin fills correctly all
information.
Post condition: manage the user account successfully

Alternative: if the system admin fills invalid information

3. The system displays error message and return to step3.

Table 2.11 Use Case Description for manage user account

Use case No: UC 12

Description: view result

Actors: student, parent, teacher, class room teacher and director

Precondition: the user must have an account

Basic course of action:

1) student, parent, teacher, class room teacher and director must be login into the system.
2) student, parent, teacher, class room teacher and director click on view result button.
3) The system display result.

Post condition: view result from database successfully

Table 2. 12 Use Case Description for view result

2.5.3 Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system.

Activities are states that represent the execution of a set of operations. The completion of these
operations triggers a transition to another activity. Activity diagrams are similar to flowchart
diagrams in that they can be used to represent control flow (i.e., the order in which operations
occur) and data flow (i.e., the objects that are exchanged among operations).
figure 2. 2 login activity Diagram
figure 2. 3 registration activity Diagram

References

[5] Zhiming Liu, Object-Oriented Software Development, International Institute for Software
Technology, UNU/IIST Report No. 259, July 2002