Bahir Dar University

Bahir Dar Institute of Technology

Faculty of Computing

Industrial project on

Student Information Management System for Blue Nile College

Submitted to the faculty of computing in partial fulfillment of the requirements for the degree of
Bachelor of Science in Computer Science.

Group Member’s

Name IDNO

1. Getnet Tigabie 0700979

2. Gizachew Esubalew 0700981
3. Ermias Eneyew 0700893
4. Eshetie Weretaw 0602023

Advisor: Mr. Muluadam T.

2010
Bahir Dar, Ethiopia,
Declaration

The Project is our own and has not been presented for a degree in any other university and all the
sources of material used for the project have been duly acknowledged.

------------------------------------- ---------------------------------------------
Name Signature

------------------------------------- -----------------------------------------------
Name Signature

------------------------------------- ---------------------------------------------
Name Signature

------------------------------------- ---------------------------------------------
Name Signature

Faculty: Computing

Program: computer science

Project Title: student information management system for Blue Nile College

This is to certify that I have read this project and that in my opinion it is fully adequate, in scope
and quality, as a project for the degree of Bachelor of Science.

------------------------------------- ---------------------------------------------
Name of Advisor Signature

Examining committee members Signature Date

1. Examiner 1
2. Examiner 2

It is approved that this project has been written in compliance with the formatting rules laid
down by the faculty.

i
Acknowledgment

The success and final outcome of this project required a lot of guidance and assistance from
different people and we are extremely privileged to have got this all along the completion of our
project. All that we have done is due to such supervision and assistance and we would not forget
to thank them.

Firstly We wish to express our sincere gratitude to the Faculty Of Computing, for providing as
an opportunity to perform our project work on “SIMS for Blue Nile College” .We respect and
thank to our project Advisor, Mr. Muiuadam T. for his diligence in advising and guiding us to
through the right path, from the inception until the completion of this document. we would like
to thank to Blue Nile College Dean and Other members of the college for enabling us to visit
their office to observe their daily operations and they are open to give different information that
are very relevant to this project work.

ii
List of Acronyms and Abbreviations

ADID: Administrator Identifier

BCSIMS: Blue Nile College student Information Management System
BR: Business Rule
Dep Head: Department Head
FREQ: Functional Requirement
HTML: Hyper Text Markup Language
HTTP: Hyper Text Transfer Protocol
MySQL: My Standard Query Language
Pro-Co: Program Co coordinator
RID: Registrar Identifier
SIMS: Student Information Management System
SID: Student Identifier
TID: Teacher Identifier
UC: Use Case
Wamp: Window Apache MySQL Php

iii
List of Figures
Figure1. 1 Iterative approach development method.................................................................................6Y
Figure2. 1Existing system work flow diagram..............................................................................................8
Figure2. 2 Proposed system work flow diagram..........................................................................................9
Figure2. 3 System use case Diagram..........................................................................................................15
Figure2. 4 User interface prototype..........................................................................................................30
Figure2. 5 Activity Diagram for login.........................................................................................................31
Figure2. 6 Activity Diagram for Register User............................................................................................32
Figure2. 7Activity Diagram for Create Account.........................................................................................33
Figure2. 8 Activity Diagram for Disable Account........................................................................................34
Figure2. 9 Activity Diagram for Submit Result...........................................................................................35
Figure2. 10 Activity Diagram for Approving Curriculum............................................................................36
Figure2. 11 Activity Diagram for View Status............................................................................................37
Figure2. 12 Activity Diagram for View result.............................................................................................38
Figure2. 13 Activity Diagram for Assign Teacher.......................................................................................39
Figure2. 14 Activity Diagram for Disable Course........................................................................................40
Figure2. 15 Activity Diagram for Register Course......................................................................................41
Figure2. 16 Activity Diagram for Upload Announcement.........................................................................42
Figure2. 17 Activity Diagram for Logout....................................................................................................43
Figure2. 18 Sequence Diagram for Login...................................................................................................44
Figure2. 19 Sequence Diagram for Submit Result.....................................................................................45
Figure2. 20 Sequence Diagram for Assign Teacher....................................................................................46
Figure2. 21 Sequence Diagram for Upload News......................................................................................47
Figure2. 22 Sequence Diagram for View Status.........................................................................................48
Figure2. 23 Sequence Diagram for Register user.......................................................................................49
Figure2. 24 Sequence Diagram for Register Course...................................................................................50
Figure2. 25 Sequence Diagram for Create Account...................................................................................51
Figure2. 26 Sequence Diagram for View Result.........................................................................................52
Figure2. 27 Sequence Diagram for Update Result.....................................................................................53
Figure2. 28 Sequence Diagram for View Grade.........................................................................................54
Figure2. 29 Sequence Diagram for Approve Curriculum...........................................................................55
Figure2. 30 Sequence Diagram for Approve Result...................................................................................56
Figure2. 31 Sequence Diagram for Reset Password....................................................................................5
Figure3. 1 System Component Diagram....................................................................................................59
Figure3. 2 System Deployment Diagram...................................................................................................60
Figure3. 3 System Class Model..................................................................................................................61
Figure3. 4 System Persistence diagram....................................................................................................62
Figure3. 5 User Interface for Home Page...................................................................................................63
Figure3. 6 User Interface for Login............................................................................................................64
Figure3. 7 User Interface Add Curriculum.................................................................................................65

iv
List of Tables

Table2. 1 Use case Description for Submit Result.....................................................................................16

Table2. 2 Use case Description for View Status.........................................................................................17
Table2. 3 Use case Description for Register User......................................................................................18
Table2. 4 Use case Description for Register for course.............................................................................19
Table2. 5 Use case Description for View Result.........................................................................................20
Table2. 6 Use case Description Assign Teacher.........................................................................................21
Table2. 7 Use case Description for Add Curriculum...................................................................................22
Table2. 8 Use case Description for Generate Grade Report......................................................................23
Table2. 9 Use case Description for Register course...................................................................................24
Table2. 10 Use case Description for Upload Announce.............................................................................25
Table2. 11 Use case Description for Update Result...................................................................................26
Table2. 12 Use case Description for View grade........................................................................................27
Table2. 13 Use case Description for Disable Account................................................................................28
Table2. 14 Use case Description for Approve result..................................................................................29
Table2. 15 Use case Description for Login.................................................................................................30
Table2. 16 Use case Description for Update Announcement....................................................................31
Table2. 17 Use case Description for Logout...............................................................................................32
Table2. 18 Use case Description for View Account....................................................................................33
Table2. 19 Use case Description for Disable Course..................................................................................34
Table2. 20 Use case Description for Approve Curriculum.........................................................................35
Table2. 21 Use case Description for View Course......................................................................................36
Table2. 22 Use case Description for View Curriculum...............................................................................37
Table2. 23 Use case Description for Create Account.................................................................................38
Table2. 24 Use case Description for Update Account................................................................................39
Table2. 25 Use case Description for Reset Password................................................................................40

v
Contents
Declaration..................................................................................................................................................i
Acknowledgment.......................................................................................................................................ii
List of Acronyms and Abbreviations.......................................................................................................iii
List of Figures...........................................................................................................................................iv
List of Tables..............................................................................................................................................v
Abstract.....................................................................................................................................................viii
CHAPTER ONE........................................................................................................................................1
1.1 Introduction.....................................................................................................................................1
1.1.1 Vision of the College..................................................................................................................1
1.1.2 Mission of the college.................................................................................................................1
1.2 Objective...........................................................................................................................................2
1.2.1 General Objective.......................................................................................................................2
1.2.2 Specific Objective.......................................................................................................................2
1.3 Statement of the problem................................................................................................................2
1.4 Beneficiary of the project................................................................................................................3
1.5 Limitation of the project.................................................................................................................3
1.6 Scope of the project.........................................................................................................................4
1.7 Methodology.....................................................................................................................................4
1.7.1 Requirement gathering methods.................................................................................................4
1.7.2 Analysis and Design methodology..............................................................................................5
1.7.3 Implementation Methodology.....................................................................................................6
CHAPTER TWO: SYSTEM FEATURES..............................................................................................7
2.1 Introduction/Overview....................................................................................................................7
2.2 Existing System Description...........................................................................................................7
2.3 Overview of the Proposed System..................................................................................................8
2.4 Requirement Analysis.....................................................................................................................9
2.4.1 Functional Requirements............................................................................................................9
2.4.2 Non-Functional Requirements..................................................................................................13
2.4.3 System Use case.......................................................................................................................14
2.4.4 Business Rule Documentation..................................................................................................40
2.4.5 User Interface Prototype...........................................................................................................41

vi
2.4.6 Activity Diagram......................................................................................................................42
2.4.7 Sequence Diagram....................................................................................................................55
2.5 System Requirement......................................................................................................................69
2.5.1 Hardware requirement..............................................................................................................69
2.5.2 Software requirement................................................................................................................70
CHAPTER THREE: SYSTEM DESIGN..............................................................................................71
3.1 Architectural Design......................................................................................................................71
3.1.1 Component Modeling...............................................................................................................71
3.1.2 Deployment Modeling..............................................................................................................72
3.2 Detail Design..................................................................................................................................72
3.2.1 Design Class Model..................................................................................................................72
3.2.2 Persistence Model.....................................................................................................................74
3.3 User Interface Design....................................................................................................................75
3.4 Logic model Design.........................................................................................................................77
4 References..............................................................................................................................................80
5 Appendix................................................................................................................................................81

vii
Abstract

viii
CHAPTER ONE

1.1 Introduction

Student information management system means the general information system for maintaining
and providing student information. It exists in all the schools, colleges, universities and any other
educational institutions. However, those information management systems vary from one to
another. Some of them are paper based; heavily manual work is involved in managing and
maintaining information such as student personal records files. However recently most
universities utilize computer in some way. A grading system plays a key role in management
system for any college.it is highly desirable to the educational kit. Particularly can provide less
effort and more effective and timely outcome. Grading system are designed to provide incentive
for achievement and assist in identifying problem areas of a student. Blue Nile College is a
private college in Bahir Dar city. It was established eight years ago and it utilizing the manual
system in almost all phases of their college. It uses the manual way of computing grades and
adding information or records of students. The process entails a lot of effort and by computing
and storing of data manually the process is prone to error especially for the teacher.By using the
manual way of computing and storing data, being prone to error is possible and just by a single
mistake repeating the process may be required. The benefit of this project is to reduce the work
load of teachers by eliminating the need for manual computation and recording of each grade.
The common problems encountered in manual recording and computations are error and file-
handling, and redundancy. As the work load gradually with growing amount of grades and
student list. It becomes tedious on part of the teacher to proficiently manage them in time for
documentation and file submission. As such, this project aims to produce a workable
computerized grading system that will address these issues.

1.1.1 Vision of the College

To be one of the best universities in Ethiopia in teaching, research and community participation
in the year 2025 E.c.

1
1.1.2 Mission of the college

To contribute towards the overall development of the country by producing inquisitive,

competent and creative citizens of critical and rational mind through task oriented and student
centered teaching at a fair service charge.

1.2 Objective

1.2.1 General Objective

The general objective of the project is to develop Web-Based Student Management System for
Ambo university woliso campus

1.2.2 Specific Objective

In order to attain the general objective, the following list of specific objectives is set:

 Perform a requirement analysis to find out the system functional and non-functional
requirement.
 Design a user interface that can help to retrieve student management.
 Design the database for storing student information using MySQL.
 Design web interface that allow students to view result online.
 Design web interface that allow to control student result
 Implement web application using PHP, CSS,java and apache web serve.

9. Methodology of the Project

10.1. Requirement Gathering Methods
To develop the proposed system, we will collect different types of data. The data that will be
collected can be primary or secondary data. To collect data that are important to develop our
system, we will use different kind of mechanisms.
Data source

We will get data from the Director of the school that will help us to develop our project. The data
may include:
 Written documents from head office and other respected offices.
 Different forms for different users from existing system
Fact Finding Techniques

2
Practical Observation: - To get additional information about the existing system, we will
observe it physically.
Interview: - To get the basic information and background information about the existing system
and structure we will asks different question for different person’s servants in the Vice Director
and teachers of the School orally.
Document analysis: -To get more information about Student Information System, how it
processed manually, we refer documents and other reading materials from the school.
10.2. 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.
 In order to define new or modified objects that can be combined with the current Student
Information System in the Students.

1.3 Statement of the problem

The current function of AUWC is not automated computerized system. So the current system is
subjected to the following problems.

 Timing problem: to view grades, to record files, to submit result and other activities are done
by manual process. So the current system is subjected to timing problem.
 Lack of availability: students cannot view their grade result, department curriculum list,
taken courses at any time and any place as they want. In addition to this it is difficulty to
search or find specific information.
 Wastages of materials: in the current manual process, the course break down is prepared and
putted in document form. Different departments that are offered in the college have their own
curriculum. In addition to this, student’s course grade is prepared in paper. This also needs
plenty of paper resources. So the current system is easily subjected to wastage of material.
 Management problem: the current system is not efficient to manage different activities
related to grading registering process.

3
1.6 Scope of the project

The scope of this project is Designing web Based Student Management System for AUWC that
helps to Regular Degree students to view their grade result.

Generally the scope of the project are:

Enables to view student grade.

The System can calculate students’ grade from their result.
Generate & view grade report.
Register course and allow to prepare course curriculum.
Allow teachers to submit student result.
Allow to Assigning course teacher
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
 Minimize the processing time or increasing speed of activity
 Simple to all internet user and avoiding data loss
 Avoid document missing and material wastage.
 To perform tasks like :-add, delete, modify existing records , register
 The system will be quick and user friendly.
 Identifying the problem under the existing system.

1.7 Methodology
1.7.1 Requirement gathering methods
Direct Observation: Observation involves an analyst watching their client performing their
daily tasks and asking questions about what they are doing and why. It is a great way to
understand what the user might go through in their job and can provide some immediate
requirements for how a process can be improved. We have observed the current system and
identified the problems regarding to the students in managing the students information .so it help

4
us an easy way to understand the system and to develop the project. By observing their system
structure we design a project to solve their problems.

Document analysis: The technique involves written documentation of procedures and tasks that
often exist, particularly in business contexts. It describes how things should be done rather than
how they are. We have analyzed different documents in the college how the grading process is
taken.

Interview technique: Interviews are of primary ways for information gathering where the
system analyst will have face-to-face interaction with relevant stakeholders or subject matter
experts. Is also probably the most widely used fact finding technique and we had performed
strong interview with the college dean, and other college members.

Questioner: It is an informal technique in which a document is used to collect   information and

opinion from respondents. And we have prepared some structured questions and present to the
college member’s.

1.7.2 Analysis and Design methodology

We decided that to use object oriented methodology because of the following reason.

 Easier to maintain
 Unaffected to change
 Its flexibility because object oriented programs are really flexible in terms of using
implementation
 Ease of understanding object oriented models due to a consistent underlining representation
throughout the development process
 Ease of modification and extensibility of object oriented models
 Ease of reuse of object component from previously designed system

And this system uses an Iterative model Approach, Because of selecting this approach from other
approaches its projects the development process in cyclic manner repeating every step after
every cycle of software development cycle. Therefore this model is used to discover errors
easily. In this development model the software is first developed on every small scale and all the
steps are followed which are taken consideration then every next and added to the software. And

5
this model is easier to manage and perform the development process. It has also the ability to
back up the system. This means the developers got comment from users, friends and from ours
until the team have finished the project

Figure1. 1 Iterative approach

development method

1.7.3 Implementation
Methodology

Blue Nile College is an

educational organization we
are design an interactive web
application that students can
easily view their grades from
this site. This web application
uses the following software implementation tools.

 Wamp server: is fully featured apache/MySQL/php development environment running on

windows.
 PHP scripting language: is server side programming.
 MySQL database system
 HTML,CSS and Java-script client side programming language

6
CHAPTER TWO: SYSTEM FEATURES

2.1 Introduction/Overview

This chapter covers introduction of existing system, players of existing system and major
functions/activities of the proposed system. This chapter also covers the practice to be preserved
from existing system, proposed solution of the existing system that address problem of existing
system and requirements of the proposed system.

2.2 Existing System Description

The existing system that has been practiced in Blue Nile College is manual system and grading
process is monitored with paper work. Students also see their grade result on papers. Teachers
also submit their student result using excel paper sheet. And also the course curriculum list is
hold using paper document. The major actors of the existing system are registrar, program
coordinator (pro-co), department head (dep head), teacher, administrator of the college and
students.

The major role of registrar is register user, apply course register to students for specific semester
and specific year, generate students grade report and also have an authority to re-correct students
result when there is a complain is comes from student after the grade is submitted to registrar.

The major role of program coordinator (pro-co) is preparing course curriculum into document
that are approved by educational bureau, assign teacher for each class to each courses and can
also perform insert new course into the curriculum when new courses is included to the
curriculum and Disable the courses that are excluded in the curriculum.

The major role of department head is approving course curriculum that are done by program
coordinator, approving student result that are submitted by teachers.

The major role of teacher is to teach student, take their assessments and submit their result.

The major role of the administrator is managing different activities that are held within the
college. And the final actor is student, they have a role like register course from registrar, take
course, take assessments, view course, view curriculum and see their cumulative grade result.

7
Figure2. 1Existing system work flow diagram

2.3 Overview of the Proposed System

The current system used in the Blue Nile College is highly tedious and is not easily available to
the users. So by carefully analyzing and observing these problems of existing system we came up
with a solution that the current manual system should automated with computerized system. The
automated computerized system reduces the problem on time, work load and complexity on
viewing student’s grade. This computerized system will have a database for storing different data
(I.e. students mark and grade information, curriculum list, courses list and etc.) that facilitate fast
information retrieving, modifying, inserting and deleting. It also includes an attractive user
interface that facilitates accessing the database. Registrar can register different users and
generate grade report.

The system enables the program coordinator to register course information, Disable course, add
and edit course curriculum easily and this curriculum is approved by Department Head. Then
Students also can register for course. Next to registering this course the program coordinator
assigns course teacher, this assignation is approved by Department Head. Finally teachers teach
their students and take assessment according to the rule and regulation of the college. This
system can compute students’ grade from their total score in each subject, so the only thing
expected from teachers is to submit students result to the system and this submitted result is

8
approved by Department Head. After this process is taken out students can view their result
(semester grade), their status (cumulative grade), curriculum (list of courses that included in
college life) and course (list of taken courses) included in the curriculum easily.

Figure2. 2 Proposed system work flow diagram

2.4 Requirement Analysis

2.4.1 Functional Requirements

Functional requirement is statements of services the system should provide, how the system
should react to particular inputs and how the system should behave in particular situation.

The system functional requirement is specified based on the following criterias:

Level of functional requirements:- this is FREQ_n where n is 1, 2, 3, 4. . . .

Requirement: general statement of the system requirement

Description:-brief description about the requiremnt.

Category:- type of actors that use this requirement functionality.

Priority:- value of the requirement, it may be high, medium or low.

9
Based on these mesuasurements the system gives the following functional requirements:

FREQ_1:

Requirement: the system shall to allow to register different users.

Description:when the registrar wants to register new users (i.e teachers, student,program
coordinater, departement head),the system gives permission to do this. The system registrar
performs this functionality as aregistrar privileges.

Category: Registrar.

Priority: high.

FREQ_2

Requirement: the system allows to assign teacher for course.

Description:when the program coordinator wants to assign teachers for different course the
system allows to do this action. Program coordinator performs this functionality as program
coordinator privilege.

Category: program coordinator.

Priority: high.

FREQ_3:

Requirement: the system shall allows to view their result and status.

Description: when the student wants to view their ststus and result, the system retrieves their
result and status from the database and display it to the user. Student performs this functionality
as student privilege.

Category: student.

Priority: high.

FREQ_4:

Requirement: the system shall allows to submit students result.

10
Description: when teachers wants to submit stuents semester result, the system allow to enter
stuudents result and submited it to the system. Teachers perform this functionality as teacher
privilege.

Category: teacher.

Priority:high.

FREQ_5

Requirement: system shall allows to generate students grade report.

Description: when the registrar wants to generate students grade report, the system allows to
generate it. Registrar performs this functionality as registrar privilege.

Category: registrar

Priority: high

FREQ_6:

Requirement:the system shall allows the program coordinator to prepare course breakdown.

Description:when the program coordinator wants to to prepare course breakdown for different
semister, year and for different departement, and when he/she also wants to edit curriclum, the
system allows to do this functionality. Program coordinator performs this functionality as
program coordinator privilege.

Category: program coordinator.

Priority:high.

FREQ_7:

Requirement:the system shall allow a student to register for a course.

Description:when the registrar wants to register students semester course. The system allows to
register this semester course registration. Registrar performs this functionality as registrar
privilege.

11
Category: Registrar.

Priority:high.

FREQ_8:

Requirement: the system shall allow to manage (create, deactivate, activate) user account.

Description: when the system adminstrator wants to create different new user account, to
activate system user account or when adminstartor wants to disable system active user account
the system gives aperission to do this action. The system adminstrator performs this functionality
as adminstrator privilege.

Category:System adminstrator

Priority: high.

FREQ_9:

Requirement:the system shall allow the user to change user Password

Description:when users wants to change their old password with new password, the system
requests the user to enter old password. Then the system changes the old password by new
password. All users can perform this functionality as users privilege.

Category: all user.

Priority: medium.

FREQ_10:

Requirement: the system allow the to reset password.

Description:when users account is forgot by different cases, the system gives privilege to enter
pre-request information and then ths system replaces that forgoten password with the new
password. system Admin can perform this functionality as admin privilege.

Category: Admin.

Priority: high.

FREQ_11:

12
Requirement: the system allows to view course curriculum.

Description: when the users wants to view course curriclum, the system retrieves the requested
curriculum list from the database and displays it to users. Department head, program coordinator
and student do this functionality as department head, program coordinator and student privilege.

Category: Department head, program coordinator and student.

Priority: medium.

FREQ_12:

Requirement: the system allows to approve students result and curriclum.

Description: when department head wants to approve students result submited by teachers,
course break down prpared by the program coordinator. The syetem allows to do this action for
the privileged user. Department head performs this functionality as department head privilege.

Category: department head.

Priority:high.

FREQ_13:

Requirement: the system shall allow users to log into the system.

Description: when authorized users wants to log into the system. The system allows the user to
enter their username and password. Immediately the user clicks login button. Then the system
authonticate these username and password, if the account is valid the system redirects to users
privileged home page. If unauthorized user tryies to log into the system the system prevents
login. All user performs this functionality as users privilege.

Category: All user.

Priority:high.

FREQ_14:

Requirement: the system shall allow to post peroidically announcement and setting submit
result date.

13
Description: when the program coordinator wants to post peroidically announcement and to set
submit result date, the system allows to accept news data and store it to the database. Program
coordinator performs this functionality as program coordinator privilege.

Category: program coordinator.

Priority: high.

FREQ_15:

Requirement: the system shall allow to register course information.

Description:when the program coordinator wants to register new course information to the
database the system gives the program coordinator to do this functionality as aprogram
coordinator privilege.

Category:program coordinator.

Priority: high.

2.4.2 Non-Functional Requirements

Non-functional requirements is constraints on the services or functions offered by the system

such as timing constraints, constraint on the development process, standards etc.

 Security and Access permissions: Users of the system must be identified, authenticated and
authorized before having access to the system’s services. Users will have their own password
and username through which they could gain access to. When the users of the system interact
with the system errors may appear. To control these inaccuracies the system will generate
different messages. When users of the system input wrong username or password, the system
responses failure message which tells them that either username or password is not correct.
 Availability: all data in the system will be available all the time if the internet is available
and the system contains redendent server to protect the down time of the system . So students
can view their grades in every time (24 hours available per day).
 Response time: average reponse time of this system shall be less than 25 seconds.
 Capacity: The system accommodate allows concurent user to use.
 Efficiency: The system uses less time to retrive. Insert and modifying data.

14
 Easy to learn: The system can be learned with in 30 minutes who can read and write
english. So students can easily see their grades online.
 User friendly interface: the user interface have attractive color selection,user can easily
input and retrieve their profile and their data.
 Maintainablity:the system is easy to modify and to add functionality without affecting the
general frame work of the system.
 Operating system: the system can be deployed in Windows OS or Linux OS.

2.4.3 System Use case

A usecase diagram is arepresentaion of a users interaction with the system that shows the
relationship between the user and diffenent usecases in which the user is involved. A use case
diagram can identify the different types of users of a system and the different usecase and will
often be accompained by other types of diagrams as well.

Actors: An actor models an external entity which communicates with the system. An actor has a
unique name and an optional description.

Use case: use case represents akinds of tasks provided by the system of an event flow. It consists
unique name participating actor, entery condition, flow of event, exit condition and alternative
actions.

The system has six actores namely Student, program coordinator, Department Head, Registrar
teacher and system administrator and it also has 26 main use cases.

15
Figure2. 3 System use case Diagram

16
2.4.3.1 Use case Documentation

Below are the lists of the use cases that are identified for Blue Nile College student information
management system

Table2. 1 Use case Description for Submit Result

Use case ID UC1

Use Case Name Submit result
Actor Teacher
Description Submit result used to submit the result of the student into the
system.
Pre-condition Teacher must log into the system
Post-condition Submitted student result
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1: the user clicks new grade form link
Step3: user fills the form
Step4: user clicks the submit button
System Response
Step2: the system display the grade form
Step5: the system validate the form
Step6: display successfully message
Step7: use case end.
Alternative course of action A3. Users enters invalid data
A3.1 go to step two.

Table2. 2 Use case Description for View Status

Use case ID UC2

Use Case Name View status
Actor Student
Description View status used for students to see their taken course list with

17
their corresponding grade during all year and semester.
Cumulative grade point.
Pre-condition student must log into the system
Post-condition Viewed status
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. student must request to view status
Step3. View status
System response
Step2. System Retrieve and display status
Step4. Use case end.
Alternative course of action A2. if error occurring retrieving status
A2. 1 The System display does not display status message.

Table2. 3 Use case Description for Register User

Use case ID UC3

Use Case Name Register user
Actor Registrar
Description Used to register different users
Pre-condition Registrar Must log into the system
Post-condition Registered users
Extend -----------------------------------------
Include UC15
Basic course of action User action

18
Step1. Registrar must want to register users
Step2. Registrar request to register users
Step4. Select the specified link among different links
Step6. Enter user information and submit the form
System response
Step3. System display different register link for different user
Step5. System displays registration form for the selected user
Step7. Display successfully register message
Step8.usecase end.
Alternative course of action A6. If invalid data are putted
A6.1 the system validate the putted data
A6.2 Display invalid data message
A6.2 go to step six

Table2. 4 Use case Description for Register for course

Use case ID UC4

Use Case Name register for course
Actor Registrar
Description Register course is used to register courses in specific semester and
specific year courses.
Pre-condition registrar must log into the system
Post-condition Registered student for course
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. registrar must request to register for course
step3. fill the form
step4. submit the form

19
System response
Step2. System display register for course form
Step5. validate the form
step6. display successfully registered course message
step7. Use case end.
Alternative course of action A3.Putted invalid data
A3.1. Validate the form and display invalid data message
A3.2. go to step two.

Table2. 5 Use case Description for View Result

Use case ID UC5

Use Case Name View result
Actor Student
Description View result used for students to see their taken course list with
their corresponding grade in specific semester and year.
Cumulative grade point.
Pre-condition student must log into the system
Post-condition Viewed result
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. student must request to view result
Step3. Enter semester and year
Step4. Submit the form
Step6. Click view grade.
System response

20
Step2. Display view result form
Step5. System display result
Step7. Use case end.
Alternative course of action A3. If student enters semester and year that is out of the
registration /While error occurring retrieving result
A3.1. The System display error message/ does not display result
message.
A3.2. to step two.

Table2. 6 Use case Description Assign Teacher

Use case ID UC6

Use Case Name Assign teacher
Actor Pro-co
Description Assign teacher enables the pro-co to assign teacher for specific
courses in specific semester and year.
Pre-condition Pro-co must log into the system
Post-condition Assigned teacher
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Pro-co must request to assign teacher
step3. select teacher from displayed List
step4. click assign button
step6. Enter Required information (select department, course...)
step7. click assign Button
System response
Step2. System display list of teachers
step5. Display assign form
step8. display successfully assign teacher message

21
step9. Use case end.
Alternative course of action A7. If error occurring during assigning of teacher
A7.1. The System display does not assign teacher message
A7.2. go to step two.

Table2. 7 Use case Description for Add Curriculum

Use case ID UC7

Use Case Name Add course curriculum
Actor Pro-co
Description Add course curriculum used to prepare course breakdown.
Pre-condition Pro-co must log into the system
Post-condition added curriculum
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Pro-co must request to add curriculum
Step3. fill the form
Step4. submit the form
System response
Step2. System display add curriculum form
step5. validate the form
step6. display successfully added message
step7. Use case end.
Alternative course of action A3. If pro-co putted invalid data
A3.1.display error message.
A3.2. go to step two.

22
Table2. 8 Use case Description for Generate Grade Report

Use case ID UC8

Use Case Name Generate grade report
Actor Registrar
Description Print grade report enables registrar to print students result.
Pre-condition Registrar must log into the system
Post-condition Printed grade report
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. registrar must request to generate grade report
Step3. Enter Required information
Step4. Click Generate
System response
Step2. System display printing form
Step5. Generate grade.
Step6. use case end
Alternative course of action A4. if error occurring generating grade
A4.1 The System display does not generate grade message.
A4.2 go to step two

23
Table2. 9 Use case Description for Register course

Use case ID UC9

Use Case Name register course
Actor Pro-co
Description Register course used to the pro-co to Register course
Pre-condition Pro-co must register into the system
Post-condition Registered course information
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1.Pro-co must request to register course
step3. fill course information
step4. submit the form
System response
Step2. System display register course form
step5. validate the form
step6. display successfully register message
step7. Use case end.
Alternative course of action A3. Putted invalid data
A3.1. Validate the data and display error message
A3.2. go step two.

Table2. 10 Use case Description for Upload Announce

24
Use case ID UC10
Use Case Name Upload announcement
Actor Pro-co
Description Post announcement used for pro-co to add different periodically
announcement into the system that are necessary to different
users.
Pre-condition Pro-co must log into the system
Post-condition uploaded announcement
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Pro-co must request to add announcement
step3. fill announcement information
step4. submit the form
System response
Step2. System display add announcement form
step5. system validates the data
step6. display successfully posted announcement message
step7. Use case end.
Alternative course of action A3. If putted invalid data
A3.1. Validate the data and display invalid message
A3.2. go to step two

Table2. 11 Use case Description for Update Result

Use case ID UC11

Use Case Name Update result
Actor Registrar
Description Update result helps to the registrar when there is a problem of

25
student result then the result is updated by the registrar.
Pre-condition Registrar must log into the system
Post-condition Updated result
Extend -----------------------------------------
Include UC15
Basic course of action User action
step1. registrar must request to update result
step3. fill the form
step4. submit the form
System response
step2. system displays update result form
step5. validate the form
step6. display successfully updated message
step7. Use case end.
Alternative course of action A3. Putted invalid data
A3.1. Validate the form and display invalid data message
A3.2. go to step two.

Table2. 12 Use case Description for View grade

Use case ID UC12

Use Case Name View grade
Actor Registrar
Description View grade used for registrar to see their students grade
Pre-condition Registrar must log into the system
Post-condition View grade
Extend -----------------------------------------

26
Include UC15
Basic course of action User action
Step1. Registrar must request to view student grade
Step3. enter students id number, year and semester
Step4. Click view
System response
Step2 System display search form
Step5. system display grade
step6. Use case end.
Alternative course of action A3. If registrar putted id of student not included in his/her
student
A3.1.display error message
A3.2. go step two

Table2. 13 Use case Description for Disable Account

Use case ID UC13

Use Case Name Disable Account
Actor Admin
Description Disable account helps to system administrator to disable account
from users.
Pre-condition Admin must log into the system
Post-condition disabled account
Extend Search
Include UC15
Basic course of action User action
Step1. Admin want to disable account
Step2. admin must request to disable account

27
Step4. Search user account
Step6. click inactive Button
Step8. click yes
System response
Step3. System display List of active system users with active
password associated with disable button.
Step5. Display selected user account
Step7. Display are you Shure to Deactivate
Step9. Display successfully disabled message
Step10. Use case end.
Alternative course of action A8. If system admin does not confirm the disabling choice
A8.1 go to step two.

Table2. 14 Use case Description for Approve result

Use case ID UC14

Use Case Name Approve result
Actor Dep Head
Description Approve result used to approve the result submitted from teacher.
Pre-condition Department head must log into the system
Post-condition Approved result
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Department head must request to approve result.
Step3. View student result
Step4. click approve button
System response
Step2. System display students result
Step5. display successfully approved message

28
Step6. Use case end.
Alternative course of action A4 if error occurring During approving result
A4.1. The System display does not approve result message.
A4.2. step two.

Table2. 15 Use case Description for Login

Use case ID UC15

Use Case Name Login
Actor All user
Description Login used to authenticate and validate system users so that only
validated users can have access to the system.
Pre-condition All Users must have valid account
Post-condition Users will log into the system
Extend Logout
Include -----------------------------------
Basic course of action User action
Step1. User must request to login
Step3.Enter username and password
Step4.Submit form
System response
Step2. System display login page
Step5. System authenticates the username and password.
Step6. Re-directed page (user log into system).
Step7. Use case end.

29
Alternative course of action A3. inputted username/password is not valid
A3.1 The system verifies username/password is not valid
A3.2 go to step two

Table2. 16 Use case Description for Update Announcement

Use case ID UC16

Use Case Name Update announcement
Actor Pro-co
Description Update announcement enables the pro-co to updated announce that
are posted before.
Pre-condition Pro-co must log into the system
Post-condition updated announcement
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Pro-co must request update announce
Step3. fill form
Step4. submit form
System response
Step2. System display update announcement form
Step5. validate form
step6. display successfully message
step7. Use case end.
Alternative course of action A2. Pro-co putted invalid data
A2.1. Verifies the data.

30
A2.2. go to step two

Table2. 17 Use case Description for Logout

Use case ID UC17

Use Case Name Logout
Actor All user
Description Logout used to secure out of the system
Pre-condition Users must log into the system
Post-condition Perfectly logout
Extend ------------------------------------
Include -----------------------------------
Basic course of action User action
Step1. User must request to logout
System response
Step2. Re-directed page (user logout to system).
step3. Use case end.
Alternative course of action --------

31
Table2. 18 Use case Description for View Account

Use case ID UC18

Use Case Name View Account
Actor Admin
Description View account allow the system administrator to view active user
account.
Pre-condition Admin must log into the system
Post-condition viewed account
Extend Search
Include ----------------------------
Basic course of action User action
Step1. An administrator wants to view an account
Step2. admin must request to view account
Step4. Search user account and click view
Step6. view selected account
System response
Step3. System display search account form
Step5. display selected user account
Step7. Use case end.
Alternative course of action A4. If error occur during retrieving user accounts
A4.1. go to step three.

32
Table2. 19 Use case Description for Disable Course

Use case ID UC19

Use Case Name Disable course
Actor Pro-co
Description Disable course enables the pro-co to Disable course from the
curriculum when the course is becomes out of curriculum
Pre-condition Pro-co must log into the system
Post-condition Disable course
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. Pro-co must request to Disable course
Step3. select course from displayed list of courses
step4. submit the form
step6. click yes
System response
Step2. System display list of courses
Step5.are you sure to Disable this course
step7. display successfully Disable message
step8. Use case end.
Alternative course of action A6. If pro-co clicks cancel button
A6.1. go to step two

Table2. 20 Use case Description for Approve Curriculum

33
Use case ID UC20
Use Case Name Approve curriculum
Actor Dep Head
Description Approve curriculum used to approve the curriculum submitted
from pro-co.
Pre-condition Department head must log into the system
Post-condition Approved curriculum
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1.Department head must request to approve curriculum
Step3. Select curriculum and View submitted curriculum
Step4. click approve
System response
Step2. System display curriculum list
Step5. display successfully approved message
step6. Use case end.
Alternative course of action A4. if error occurring During approving curriculum
A4.1 The System display does not approve curriculum message.
A4.2. go to step two.

Table2. 21 Use case Description for View Course

Use case ID UC21

Use Case Name View course
Actor Student
Description View course used to see taken course list included in the

34
curriculum.
Pre-condition student must log into the system
Post-condition View list of course
Include UC15
Basic course of action User action
Step1. student must request to view course
Step3. View taken course list.
System response
Step2. System display taken course list
step4. Use case end.
Alternative course of action A1. if error occurring retrieving course
A1.1 The System display does not display course message.
A1.2. go to step one.

Table2. 22 Use case Description for View Curriculum

Use case ID UC22

Use Case Name View curriculum
Actor Dep Head, student and pro-co
Description View course used to see course list included in the curriculum.
Pre-condition Department head ,program coordinator and student must log
into the system
Post-condition View courses listed in the curriculum
Extend -----------------------------------------

35
Include UC15
Basic course of action Step1.student / department head /program coordinator must
request to view course curriculum
Step3. View course list in the curriculum.
System response
step2. System display course list in the curriculum
Step4. Use case end.

Alternative course of action A1. if error occurring during retrieving course

A1.1 The System display does not display course message
A1.2. go to step1.

Table2. 23 Use case Description for Create Account

Use case ID UC23

Use Case Name create Account
Actor Admin
Description Create account helps to the system administrator to create account
for different users.
Pre-condition Admin must log into the system
Post-condition Created account
Extend View user
Include UC15
Basic course of action User action
Step1. Admin wants to create account
Step2. admin must request to create account

36
Step4. Select specified link
Step6. Click create account button
Step8. Enter account information and click create button
System response
Step3. System Displays different create account link for different
users
Step5. Display list of active users who need an account which each
have create account button
Step7.System display create account form
Step9. Validate and display successfully created message
Step10. Use case end.
Alternative course of action A8. If putted invalid data
A8.1. display error message
A8.2 go to step four.

Table2. 24 Use case Description for Update Account

Use case ID UC24

Use Case Name update account
Actor All users
Description Update account used to update old account with new account
Pre-condition Users must log into the system
Post-condition Updated account
Extend -----------------------------------------
Include UC15
Basic course of action User action
Step1. users must request to update account
Step3. fill the form
step4. submit the form
System response

37
Step2. the system displays update account form
step5. validate the form
step6. display successfully updated account message
step7. Use case end.
Alternative course of action Putted invalid data
A1. Validate the form and display invalid data message
A2. Go to step two.

Table2. 25 Use case Description for Reset Password

Use case ID UC25

Use Case Name reset password
Actor Admin
Description reset password helps to users in order to reset password when
someone forgets his/her own passwords
Pre-condition Users must have username
Post-condition reset password
Extend -----------------------------------------
Include ----------------------------------------
Basic course of action User action
Step1. admin must request to reset password
step3. fill the form
step4. submit the form
System response
Step2. the system displays reset password form
step5. validate the form(find required data from the database)
step6. display successfully reset password message
step7. Use case end.

38
Alternative course of action A3. Putted wrong data (data that is not found on the database)
A3.1. display invalid data message
A3.2. go to step two

2.4.4 Business Rule Documentation

The business rule works as follows:

BR1: Firstly program coordinator must prepare course curriculum then it is approved by
department head.

BR2: Then the student registers for semester course

BR3: program coordinator assigns teacher for these semester register course

BR4. Then course teachers test their students, take assessments and collect exam result in manual process
finally those collected result is submitted to the system.

BR5. After this department head can view students result and approve these result.

BR6. Finally when the result is approved by department head then student can view their own result
remotely/online.

2.4.5 User Interface Prototype

Prototype is asimulation of real thing.Itis also amodel of system or subsystem under syatem. The
prototyes of the system can shown in paper based or computer based. They can model the entire
system with real data or just afew screan with sample data. Prototyping is the process of
developing prototype. Is a one method of requirement analysis technique. The following
prototype shows BCSIMS system:

39
Figure2. 4 User interface prototype

2.4.6 Activity Diagram

An activity diagram visually presents a series of actions or flow of control in a system similar to
a flowchart or a data flow diagram. Activity diagrams are often used in business process
modeling. They can also describe the steps in a use case diagram. Activities modeled can be
sequential and concurrent. In both cases an activity diagram will have a beginning and an end.

An activity diagrams have activity nodes and activity edges.

 Activity node: which are placeholders for one or more steps within an activity.
 Activity edge: which are connections between activity nodes.

Activity nodes has different control nodes (which coordinates flow among other activity nodes).

40
 An initial node: is where the flow of control starts when an activity is invoked.
 A final node: is control node at which one or more flows within the given activity stop.

The following are sample activity diagram for Blue Nile College Student Information
Management System

Figure2. 5 Activity Diagram for login

41
Figure2. 6 Activity Diagram for Register User

42
Figure2. 7Activity Diagram for Create Account

43
Figure2. 8 Activity Diagram for Disable Account

44
Figure2. 9 Activity Diagram for Submit Result

45
Figure2. 10 Activity Diagram for Approving Curriculum

46
Figure2. 11 Activity Diagram for View Status

47
Figure2. 12 Activity Diagram for View result

48
Figure2. 13 Activity Diagram for Assign Teacher

49
Figure2. 14 Activity Diagram for Disable Course

50
Figure2. 15 Activity Diagram for Register Course

51
Figure2. 16 Activity Diagram for Upload Announcement

52
Figure2. 17 Activity Diagram for Logout

2.4.7 Sequence Diagram

A sequence diagram illustrate object interactions arranged in a time sequence.

Sequence diagram show you step by step what has to happen to accomplish
something in the use case.

A sequence diagram focus on the time-ordering of messages between objects (i.e.

displays the time sequence of the objects participating in the interaction).

The following are sample sequence diagram for Blue Nile College Student Information
Management System.

53
Figure2. 18 Sequence Diagram for Login

54
Figure2. 19 Sequence Diagram for Submit Result

55
Figure2. 20 Sequence Diagram for Assign Teacher

56
Figure2. 21 Sequence Diagram for Upload News

57
Figure2. 22 Sequence Diagram for View Status

58
Figure2. 23 Sequence Diagram for Register user

59
Figure2. 24 Sequence Diagram for Register Course

60
Figure2. 25 Sequence Diagram for Create Account

61
Figure2. 26 Sequence Diagram for View Result

62
Figure2. 27 Sequence Diagram for Update Result

63
Figure2. 28 Sequence Diagram for View Grade

64
Figure2. 29 Sequence Diagram for Approve Curriculum

65
Figure2. 30 Sequence Diagram for Approve Result

66
Figure2. 31 Sequence Diagram for Reset Password

2.5 System Requirement

To develop this web based system, it needs different tools. These development tools are
hardware and software tools both collaboratively work to achieve specific goals. The followings
are some hardware and software requirements:

2.5.1 Hardware requirement

Hardware requirements are requirements that are used after the deployment of the system. These
are:

Server:

67
Processer: this is the basic hard ware component to develop the system so in the client side it
needs 3.30MHZ and in the server side also 6MHZ is needs.

RAM: also another type of hard ware component to develop the system and it is a storage device
and it need 1.75GB and 4GB in client and server side respectively.

Internal Hard Disc Space: this is another type of hard ware component to develop the system
so in the client side it need 500GB and in the server side also 1TB is needs.

Network ruck: network ruck used for housing of network device (e.g. switch).

Personal computer: Clients use personal computer to access the system.

Printer: after generating grade report user use a printer to print that grade.

Router:

2.5.2 Software requirement

Notepad++: used as text editor (to write source code).

Java Script and HTML: client side programming.

Server side language (PHP):- which is a server side scripting language used in order to collect
information from the user interface storing in a data base and retrieving data from the database
and displaying the data retrieved on the user interface.
Web Browsers:-it uses Baidu Browser , internet explorer to access the system.
Database (MYSQL):- is quick, powerful, free and can handle large database.

68
CHAPTER THREE: SYSTEM DESIGN

3.1 Architectural Design

In this project the team uses a three-tier architecture which has three layers. These three layers
are the Application or Presentation layer, the business layer and the data access layer.
Application or presentation layer is the form which provides the user interface to either
programmer or end user. The business layer is the class which the team uses to write the function
which works as a mediator to transfer data from application layer or presentation layer to data
layer. This layer also has a property layer which is a class where variables are declared
corresponding to the fields of the database which can be required for the application and make
the properties so that the team can get or set the data using these properties into the variables.
The third tire is the data access layer which is also a class to get or set data to the database
queries back and forth. This layer only interacts with the database. The database queries or stored
procedures written here to access the data from the database or to perform any operation to the
database.

3.1.1 Component Modeling

Component is a physical and replaceable part of the system that confirms to and provides the
realization of a set of interfaces. Component model shows the structural relationship between the
component of the system. It also provide physical view of the system and it focus on a set of
compnents and the structural relationship among them. Its purpose is to show the dependencies
that the software has on other software component.

69
Figure3. 1 System Component Diagram

3.1.2 Deployment Modeling

Deployment modeling shows the configuration of run time processing nodes and the components
that live on them. It also shows how the finished system will be deployed on one or more
machines and used to visualize the topology of the physical components of a system where the
software components are deployed. Deployment modeling used for describing the hardware
components where software components are deployed.

70
Figure3. 2 System Deployment Diagram

3.2 Detail Design

3.2.1 Design Class Model

Class diagrams are used to describe the structure of the system in terms of classes.
Analysis Class model shows the classes of the system, with attributes, methods,
relationship, multiplicity and Role of classes.

71
Figure3. 3 System Class Model

72
3.2.2 Persistence Model

Persistence models are used to design the schema of your database. You typically need to draw a
Persistence model whenever you are using a relational database to store your objects in. The
strength of Persistence models is that data entities are conceptually the same as the tables of a
relational database and that attributes are the same as table columns.

Figure3. 4 System Persistence diagram

73
3.3 User Interface Design

Figure3. 5 User Interface for Home Page

74
Figure3. 6 User Interface for Login

75
Figure3. 7 User Interface Add Curriculum

3.4 Logic model Design

Logic model is an algorithm or pseudo code for a process. The following are
sample pseudo codes.

Login to the system

Login ()

Display login page

User enters username and password

If “login” button is clicked

76
Open database

Open account table

If “username” is matched and password is “matched”

Display Users Home Page

Else

Display Error Message

Close table

Close database

Else

If “clear” Button is clicked

Clear form data and refresh form

End function

Viewing Status

View status ()

User log into the system

If “view status” is clicked

77
Open database

Open result table

If “result” is exist

Display Cumulative grade point

Else

Display Error message

Close table

Close database

End function

Submit result

Submit result ()

Users log into the system

Users click “submit result” link

Display submit result page

Enter result

If “submit” button clicked

If form data is valid

78
Open database

Insert data into result table

If inserted

Display successfully submitted message

Else

Display does not submitted result

Close database

Else if invalid data

Display error message

Else if “cancel” button clicked {

Clear form data and refresh form

End function}

79
4 References
1. https://www.slideshare.net/computerized grading system.
2. http://WWW.Youtube.com/Transparent Login Form with HTML & CSS - Login
form Design with Source Code - Html Login Page Design
3. Object oriented software engineering using UML, Patterns by Bernd Bruegge &
Allen H.Dutot, Third Edition
4. Unified modeling language by Giant Dino.

80
5 Appendix
Sample Questions that we have forwarded to the College Dean and Answers given by the Dean
is shown by the following table
No Questions Answer
1 Does the College Currently Uses Automated NO still we use manual
SIMS?
2 Does the Grade interval and letter grade is fixed or Fixed Similar to University Student
Variable?
3 How the assessment is taken in each department? Test1(15%),
test2(15%),
Project work or Assignment(15%),
Quize(5%),
Final Exam(50%),
Total=100%.

4 How much result is expected from students to pass 1.75 and above for first year student and
to next level? 2.00 and above for second year and above
students.

81
82