Abstract

This project entitled with “Student information system web portal” is designed to keep
records of students and make retrieval of information easier. This project examines Student
information system web portal where Student information stored in the database and
Capable of easy retrieval of information. The system is very interactive and useful for the
Registrar workers, students, and teachers and for college deans and department heads. The
main idea of the system lays in the need for a system which the Registrar workers, students,
teachers,college deans and department heads and System administrators communicate each
other for improving Student information systems activities. The project has been designed in
JAVA technology i.e. JSP (java server pages and servlet) and Oracle database with apache
tomcat server for the development of the project. All the data needed for the application is
stored in the form of tables in the Oracle database. The report contains the details of all the
tasks carried out during the entire website development life cycle of the Student information
System web portal. Withdrawal and readmission of students and Add and drop of course can
be developed in the future to enhance the performance and increase the functions of the
system.

Acknowledgment

I
We have taken efforts in this project. However, it would not have been possible without the
kind support .First of all we would like to thank for God that helps through our life. Next we
would like to express our special thanks of gratitude to our advisor Metages Molla, Who
asses us starting from the beginning up to the completion of this system.

Contents
CHAPTER ONE....................................................................................................................................1

1 Introduction........................................................................................................................................1

1.1 background of the project...........................................................................................................1

1.2. Problem Statement (Problem of existing system).....................................................................2

1.3 Objective of the project..............................................................................................................2

1.3.1 General objective:................................................................................................................2

1.3.2Specific objective:.................................................................................................................3

II
 1.4 Significance of the project.........................................................................................................3

1.5 Scope of the project....................................................................................................................4

1.6 Limitations..................................................................................................................................4

1.7 Methodology..............................................................................................................................5

1.7.1 System development methodology.....................................................................................5

1.7.2 Programming and database tools........................................................................................5

1.7.3 Hardware and software Requirements................................................................................8

1.7.4. Data collection methodology..............................................................................................8

1.8 Feasibility Analysis......................................................................................................................8

1.8.1 Economic Feasibility.............................................................................................................8

1.8.2 Technical Feasibility...........................................................................................................10

1.8.3 Operational Feasibility.......................................................................................................10

CHAPTER TWO................................................................................................................................12

2. System Analysis..............................................................................................................................12

2.1 Overview of the existing system...............................................................................................12

2.1.1 Users of the Existing System..............................................................................................13

2.2 Overview of the new system....................................................................................................14

2.3 Requirements specification......................................................................................................14

2.3.1 Functional requirements....................................................................................................15

2.3.2 Non functional requirements..............................................................................................15

2.4 Requirement Analysis................................................................................................................18

2.4.1 Use-Case Diagrams.............................................................................................................18

2.4.1.1 Essential Use Case Modeling...........................................................................................20

2.4.2. Sequence Diagram.................................................................................................................33

2.4.3. Class diagram........................................................................................................................43

2.4.3. Activity Diagram....................................................................................................................43

CHAPTER THREE............................................................................................................................51

III
3.System design..................................................................................................................................51

3.1 Introduction..............................................................................................................................51

3.1.1 Design goals and objectives...............................................................................................51

3.2. Design the class diagram.........................................................................................................52

3.2.1. Description of design class diagram..................................................................................53

3.3. Collaboration diagram.............................................................................................................58

3.3.1. Physical data model..........................................................................................................62

3.4. Component diagram................................................................................................................66

3.5 Deployment diagram................................................................................................................68

3.6 User interface...........................................................................................................................70

3.6.1. Home page user interface.................................................................................................70

3.6.1.1 Student grade report user interface...............................................................................71

3.6.1.2 Student grade edition user interface..............................................................................72

CHAPTER –FOUR............................................................................................................................73

4. System Implementation.................................................................................................................73

4.1 Overview of Programming technology.................................................................................73

4.2 Sample Implementation code...............................................................................................73

CHAPTER FIVE................................................................................................................................83

5 Discussion and Results....................................................................................................................83

5.1.Recommendation..........................................................................................................................84

5.2 Future enhancements................................................................................................................84

References...........................................................................................................................................85

1 Web Reference.................................................................................................................................85

2 Bibliography......................................................................................................................................85

Acronyms and abbreviations used in the project................................................................................86

IV
 List of figures names……………………………………………………………...…page number
Figure 1 course management essential use case diagram .................................................................. 20
Figure 2 Grade Management Essential use case diagram ................................................................. 21
Figure 3Assignment Management Essential use case Diagram ......................................................... 21
Figure 4 User Management essential use case diagram..................................................................... 22
Figure 5 Student information Registration Essential use case diagram .............................................. 22
Figure 6 Dormitory Management essential use case diagram ............................................................ 23
Figure 7 System Use Case Diagram ................................................................................................. 32
Figure 8 View course result sequence diagram ................................................................................. 34
Figure 9 View grade report sequence diagram.................................................................................. 34
Figure 10 view course information................................................................................................... 35
Figure 11 Register student information sequence diagram ................................................................ 36
Figure 12 Student register on course sequence diagram .................................................................... 37
Figure 13 Submit grade sequence diagram ....................................................................................... 37
Figure 14 student post Assignment sequence diagram ...................................................................... 38
Figure 15 Instructor post Assignment sequence Diagram ................................................................. 39
Figure 16 View submitted grade sequence diagram .......................................................................... 39
Figure 17 View report sequence diagram ......................................................................................... 40
Figure 18 View log event sequence diagram ................................................................................... 40
Figure 19 create account sequence diagram ..................................................................................... 41
Figure 20 Manage account sequence diagram .................................................................................. 41
Figure 21 update student information diagram ................................................................................. 42
Figure 22 View dormitory sequence diagram ................................................................................... 42
Figure 23 Class diagram .................................................................................................................. 43
Figure 24 View Grade Report Activity Diagram .............................................................................. 44
Figure 25 Submit Grade report Activity Diagram ............................................................................. 45
Figure 26 Post Assignment Activity diagram ................................................................................... 46
Figure 27 Enter course result Activity Diagram ............................................................................... 47
Figure 28 View course result Activity Diagram ............................................................................... 48
Figure 29 User management Activity Diagram ................................................................................ 49

V
Figure 30 department management activity diagram ........................................................................ 50
Figure 31 Design class diagram ....................................................................................................... 52
Figure 32 Login Collaboration Diagram .......................................................................................... 58
Figure 33 Grade Report Submission Collaboration Diagram ............................................................ 59
Figure 34 View Grade Report Collaboration diagram....................................................................... 59
Figure 35 Grade submission Approval collaboration Diagram .......................................................... 60
Figure 36 register student collaboration diagram .............................................................................. 61
Figure 37 create account collaboration diagram ............................................................................... 62
Figure 39 Component diagram......................................................................................................... 67
Figure 40 Deployment diagram ....................................................................................................... 69

List of Tables names……………………………………………………...………page number

Table 1 Actors Identification ........................................................................................................... 18

Table 2 Use Case Identification ....................................................................................................... 19
Table 3 :Essential use case description ............................................................................................. 23
Table 4 Student table ....................................................................................................................... 62
Table 5 course table ......................................................................................................................... 63
Table 6 Department table ................................................................................................................. 63
Table 7 Student Course table ........................................................................................................... 63
Table 8 Instructor Table................................................................................................................... 64
Table 9 Instructor Course Table ....................................................................................................... 64
Table 10 Instructor Student Table ................................................................................................... 65
Table 11 grade Report table ............................................................................................................. 65
Table 12 college Table ................................................................................................................... 65

VI
 CHAPTER ONE
1 Introduction
1.1 background of the project
Debre Markos University is one of the thirteen newly established Universities in Ethiopia and
foundation stone was laid on January 2005 G.C. After the completion of the first phase of the
construction, the University began its service in February 2007G.C.Debre Markos University aspires
to a national recognition of excellence and performance in teaching, research and service. Among the
services and management areas student information is one of them. Student Information System
portal is a web-based application system designed to introduce a conducive and structured
information exchange environment for integrating students, parents, Departments and the
administration of registrar offices. Even if student information system the main concern of the
organization, Until January 2007 E.c Debre Markos university students cannot get the
services to view grade reports online. After January 2007 E.c Technology college students get
the chance to view grade reports online. But this system limited to technology
students.Keeping Student information is one of the great tasks that should be under taken by
the registrar officer, departments and colleges of the organization.
The solution of this project show student’s grade report online, register students detail
information, to generate reports. The system generates a grade report based on the grades and
credit hours of the course received.
The system enables students to view grade reports online with in a fraction of seconds
without any wastage of time, resources, time limitation and restriction of place. And also
instructors submit students grade Report using this system from anywhere that has network
connections within a specified period of times.
In this system students show the currently available posts related to their academic
achievements, such as view posted assignments, view notices, view Assignment results, View
the mid, final and Total Results get from 100% for each course and also submit assignments
to instructors, send messages (feedback) concerned on the relevance affairs.
Generally student information system web portal is a system that posts and stores student
related data in a well-organized manner.

1
 1.2. Problem Statement (Problem of existing system)
The existing system work manually. In the present system whenever someone asks about
student information it is difficult to find student information easily because student details
stored in a manually paper based system or using excel applications. Instructors submit
student’s grade report manually using paper based .So the present system is not good enough
for students and any members of the organization.
 Information retrieval of students detail is difficult and time consuming.
 Quick analysis of delivery is not possible.
 Information requires much human effort.
 There is no interface that helps user (student and teacher) to access the system. This
means students can’t access their information and it is obstacle for the right to access
own personal information.
 All records like student, department and faculty information are stored in the Ms
Access and excel but there is no network that enables employees to do their works in
their computer. This may lead to repetitive work and may decrease the efficiency of
the work and it may make the system dormant when information became huge.
 The other big problem is security. As we have indicated in the above the information
is stored in Ms Access and Ms Excel, every employee can edit others personal
information. But, the student information that is stored in the registrar need highly
secure system and also needs care to prevent it from an authorized access.
 Students grade report is calculated manually by using excel documents or any
calculator devices except technology students, this is bulky tasks.

 In the current system there is no mechanism for students to view grade reports online
except technology students. This is the main problem of the current system.
 In the current system there are no mechanisms for instructors to submit student’s
grade report using online systems this is the other problem of the current system.
1.3 Objective of the project

The new system has the following

specific and general objectives:

1.3.1 General objective:

The general objective of this project is to develop web based application for Debre Markos
University students and offices of registrar.

2
 1.3.2Specific objective:
Specific objects are objectives that help to achieve the general objectives of the system. The
specific objectives of this project are:
 To develop a database system that storing, manipulating, searching and retrieving
data.
 To develop easy and descriptive user interfaces to manipulate student’s records. 
To provide timely, accurately and reliable access and information to students.
 To develop a centralized database to keep students information adequately.
 To develop a mechanism for an automatic report generation.
 To develop good security mechanism
 To develop a system that enables students to view grade reports
 To develop a system that enables instructors to submit students grade and assignment 
To develop a system that enables automatic student grade report generation

1.4 Significance of the project

Significance of the project indicates or identifies who are the beneficiaries of the system and
what serves for the beneficiaries of the system.
This project gives incredible benefits to employees, students, and teachers and generally for
the university community. The following are the main beneficiaries of the project.
For students
Students sit at home or anywhere easily view their grade report, Submit assignments, view
assignments, view course information and their dormitory placement through internet without
waiting for long times.

For employees
The student shares some of the tasks through the internet then it is a huge relief for the
employees. The employees request information from other computers with a mouse click
instead of using letters.

For Instructors
Instructors can submit student’s grade report using the system.

Generally this system provides the following significances to the system users.
 To View grade reports online.
 To use time effectively.
 To increase students satisfaction.
 To view course information online.

3
  Reduces the number of days taken to give a service.
 Reduce resource wastage.
 Lower human resource need to accomplish a task.
 Faster decision making due to the report generation functionality.
 Creates Job satisfaction to the employees.
 Supplies timely information for users.
 To submit students grade report.
 To view students dormitory
 To assign students dormitory placement  To post and submit assignments

1.5 Scope of the project

Scope: Defines the coverage areas of the project and the activities and operations done by the
system.It is due to constraint of time, resource and manpower the project team are limited to
develop web based application for Debre Markos university student information system.
The project team developed:
 Student registration system.
 Grade report generating system.
 Documenting and storing student records system.
 Collect student’s grade report from instructors  Develop Security Mechanism.
 Print grade reports.
 Search facilities.
 Generate reports.
 Assignment posting and submitting system.
Our system does not include
 Withdrawal and Readmission of students.

1.6 Limitations
During this project life cycle faced a number of problems like over loading work, resources
shortage like internet, lack of computer access in lab class, power fluctuation, lack of
reference books and sample .learning the programming language is the other main problem
the team faced. Because the programming language we use is hard to learn and the team were
new for this programming language.
1.7 Methodology
A methodology is a set of methods, processes, and practices that are repeatedly carried out to
deliver a project [1].

4
Prototyping used for getting clear requirements and re-use the software components to
accelerate the development timelines.
This part deals about the method of data collection, source of data, and how the data
organized and analyzed.

1.7.1 System development methodology

System development methodology refers to the frame work that is used to structure plan and
control the flow of developing an information system there are different system development
methodologies that are suitable for different projects based on the values technical
organizational project and team consideration. For this project the team used object oriented
software development methodology [2][1].
The reason why we selected object oriented system development is because it has the
following advantages.
 In an object-oriented environment,
 Object-oriented systems development is a way to develop software by building
self-contained modules or objects that can be easily replaced, modified, and
reused.
 Software is a collection of discrete objects that encapsulate their data as well as
the functionality to model real-world "objects."
 Each object has attributes (data) and methods (functions).
 Objects are grouped into classes; in object-oriented terms, we discover and
describe the classes involved in the problem domain.
 Encourages re-use not only modules but also entire design.

1.7.2 Programming and database tools

The systems that are developed include the following database and programming tools. 
Programming language
 JAVA: JAVA is server side scripting, which means that only the output is sent to the
client’s browser the execution is performed from a server side. Used as front end.
The reason to select this programming Language is:
 Java is secure
Java considers security as part of its design. The Java language, compiler,
interpreter, and runtime environment were each developed with security in
mind.

5
  Java is multithreaded
Multithreaded is the capability for a program to perform several tasks
simultaneously within a program. In Java, multithreaded programming has
been smoothly integrated into it, while in other languages, operating
system-specific procedures have to be called in order to enable
multithreading.
 Java is platform-independent
One of the most significant advantages of Java is its ability to move easily
from one system to another. The ability to run the same code on many
different systems is crucial to www, and Java succeeds at this by being
platform-independent at the source and almost binary levels.
 Java is distributed
Java is designed to make distributed computing easy with the networking
capability that is inherently integrated into it. Writing network programs in
Java is like sending and receiving data to and from a file.
 Java is object-oriented this allows you to create modular maintainable
applications and reusable code.
 Java is robust robust means reliability. Java puts a lot of emphasis on early
checking for possible errors, as Java compilers are able to detect many problems
that would first show up during execution time in other languages.
 HTML is to tell the browser how things are supposed to be displayed. Used as a
front end.
 Java script. JavaScript is client side scripting, meaning it executes on the viewer’s
browser. Used as a front end
 CSS: cascading style sheet performs the designs of the interface and performs the
design of document layouts. Used as a front end
 SQL: Structured querying language which is used to query data from the database.
 Java Server Page (JSP): is a technology for controlling the content or appearance
of
Web pages through the use of servlets, small programs that are specified in the
Web page and run on the Web server to modify the Web page before it is sent
to the user who requested it.
 Servlet :- Servlets generate dynamic content or create dynamic web pages that is
easy to write and faster to run within a web servers[9]

6
 Database
 Oracle 11gused as back end to store data filled from the front end.
 The reason to select Oracle 11g as a back end is:
 It is an open source database.
 Supports large number of embedded applications which makes oracle very
flexible.
 Use of Triggers, Stored procedures and views which allows the developer
to give a higher productivity.
 And most of the time oracle is compatible with .net programming
language.
 Provides the least expensive, most scalable, secure and highly available
rapid application development environment!
 Improved performance for queries accessing large amounts of data 
High-performance transactional access to large object data.
 An Oracle database can run on all major platforms, including Windows
and networking protocols
 Consistent information, flexibility, easy management of data security and
privacy and a reduced application development time.
 Documentation tools:
 MS word 2010.
 MS power point 2010 for presentation.
 E draw max software for analysis of the system
 Operating system
 Window 7and 8.

1.7.3 Hardware and software Requirements

1.7.3.1 Software requirements

 Editor Software
 Edraw Max
 MS office 2010
 Oracle Database 11g Express Edition
 Net Beans IDE 6.9.1

7
 1.7.3.2 Hardware requirements
To implement the project efficiently the team used the following hardware’s.
 CD 700MB
 Printer
 Flash8GB
 Personal computer
 Server computer

1.7.4. Data collection methodology

The project team used different methods to collect data. Data collection is the most important
part in this project to find the main requirement of the system and to understand how the
system does. Among the methods that are used:
 Observation: to analyze the organization work processes
 Document analysis: to get information about background of the organization.
 Interviews: used interview to gather direct information from students and registrar offices
regarding of students information.

1.8 Feasibility Analysis

The main objective of the feasibility study is to test the Technical, Operational and
Economical feasibility of the new system [2].

1.8.1 Economic Feasibility

Economically this system not require much more cost and material to implement the system.
The system gives better services for users. Economic feasibility analysis often referred to as
cost benefit analysis.
Here the team stated the costs related to the project and the benefits that are going to be
gained after the completion of the project by performing a cost-benefit analysis.

Let’s start from the costs by classifying them into tangible and intangible.

Costs Tangible Costs

These costs are those that can be estimated in money terms [4]. The table below lists the
tangible costs with their description.
One Time Costs
The estimation is based on current price of computers, hardware devices and software to be used

8
 Quantity Unit Total
Price(Birr) Price(Birr)
Computers: These are the computers that are involved throughout the project. Such as the
development computers and test servers, are used only during the SDLC while the deployment
computers are also used after the completion of the SDLC (System Development life cycle).

Development Desktop 1 6000 6,000

Computers computer

Laptop 1 12,000 12,000

Test Server 1 8000 8,000
Deployment Computers 20 6000 120,000
Hardware: The hardware devices required for operation are specified here
Printers 4 5000 20,000
Scanners 4 4000 16,000
Software: These are the software tools used for developing and implementing the proposed
system

Microsoft office2010 1 Free free

Apache Tomcat 6.026 1 Free free
Oracle database 11g express
edition

Microsoft Windows Server 2008 1 Free free

Total Onetime Cost 181860
When we compare the benefits of the project from its expense it has higher benefits for users.
Intangible Costs
These costs cannot be estimated in money terms
• Time wasted
Benefits
Benefits are further divided into tangible and intangible benefits [4].
Tangible Benefits
These benefits can be estimated in terms of money which means the benefit is real or actual
rather than imaginary or visionary [4]. For instance, improving response time, producing
error free out put such as producing report are all tangible benefit. These benefits can be
• Cost reduction and/or avoidance
• Error reduction

9
 • Increased flexibility
• Increase the speed of activities
• Improvement of management planning and control.
• Reduction in material consumption
Intangible Benefits
These benefits cannot be estimated in money terms
• More timely information
• Faster decision making
• Boosting employee morale
• Increase accuracy
• increase information processing efficiency
Since the benefits are larger than the costs, the team concluded that the project is
economically feasible.

1.8.2 Technical Feasibility

The development process of student information System web portal has been advantages to
the organization because it uses only current resources of the organization. The technical
feasibility is also attributed to the fact that the system not make use of any additional
components which can lead to increased load on the system. The system has been technically
feasible because, the system is powerful to be applied by low skilled users as much as
possible.

1.8.3 Operational Feasibility

This system has been operationally feasible and the system has been user friendly. The
registrar worker and users of system uses the system to perform its regular task without any
ambiguity. The user of the system can understand the new system with little training and
instruction.
Operationally, the system has capable of producing quick and qualitative services of students
and employees so that to have immediate and satisfied services .The system developed are
operationally more functional.

10
 CHAPTER TWO
2. System Analysis
2.1 Overview of the existing system
Debre Markos university student information system is currently using a manual system to
view grade reports, to submit student grade report, to assign students dormitory allocation, to
submit and view assignments but only technology college students view their grade report in
January 2007. They use MS Excel and calculator for calculating and storing student
information.
The existing systems have Lack of a well-organized database system and data are not easily
accessible due to its integration and placed in different location.
The problems of the existing manual based system are described using the PIECES from
work. Where
 P is performance
 I is information
 E is economy
 C is control,

11
  E is efficiency and  S is service.
 Performance: - It is time consuming and less performance since every task is done manually and
it has taking much time and to complete the task requires a long period of time. Regarding on
lack of speed the system generate output with slow speed.
 Information: - Redundancy data.
- Not accurately captured.
 Economy  Costs
The current system takes more costs (resources) to perform its tasks like
calculator, pen, and very huge amount of paper.
 Profit
The current system does not design at producing profit when it compares with
the cost it expense.
 Control and security:-
The current system does not much secured or controlled refers to the data or
information is not getting only for authorized people and also the data privacy
rules and regulation are being not respected.
 Efficiency: It operates over specified long period of time interval. Generally, the above current
system mentioned is inefficient.
 Service:-
It takes more time to give as well as get the services both the workers and users. The
student document is stored simply in the shelf so if its file damaged there is no way to
recover the file.

2.1.1 Users of the Existing System

Users represent external entities that interact with the system. Here are the users involved in
the existing system:
Student
The student does not interact with the computerized system rather he/she requests a service
from the record officers of the registrar or from the department head. The student gets his/her
requested service from the record officers or from department head. But in this year
technology college students get the service to view their SGPA using the system.
Record Officer
This record officer only interacts with some services at one computer. Particularly Student
Registration, Student course information registration and students course grade information.

12
Here the record officer asks student every information and fill manually first on a paper then
finally put all the collected information to the computer.
Instructor
Instructor only interacts with some services at one computer. Particularly Student course
result registration, Student Course Grade calculation. Here the instructor collect every student
information and fill manually first on a paper then finally put all the collected information to
the computer.
Department head
Department head only interacts with some services at one computer. Particularly Student
Registration, Student course information registration and students course grade information.
Here the department head asks the Student every information and fill manually first on a
paper then finally put all the collected information to the computer.
Registrar manager
The Manager gets reports from the record officers and each departments and faculties
manually. The reports help the manager to see how services are given to the Students and
predict future outcomes.

2.2 Overview of the new system

The system that are developed solves the problems appear in the current system. The new
system enables all Debre Markos university students to view grade reports (including
semester GPA, previous GPA, cumulative GPA), to view their dormitory, to view course
information, to submit assignments, and helps instructors to submit student grade reports,
post assignments to students, allows coordination among workers, allows authorized users to
access any file without wasting any time, and the system can store a large amount of data.
The new system increases the security, availability and performance of the system. In this
system instructors can easily submit student’s grade report by sitting at his/her computer
using the system, rather than going to department then college then Registrar. All this
processes are handled electronically in the system. The new system handles a log event of all
user activities to increase security of the system.

2.3 Requirements specification

In this section the project teams have kept the basic understanding of the requirements and
dependencies of the current system prior to any actual design or development work. A
requirement specification is used to prepare requirement specification before starting the

13
actual design. This enables the designer to have a clear idea about the structure and content of
the information system.
A well-designed, well-written SRS accomplishes four major goals:
• It provides feedback to the customer. A SRS is the customer's assurance that we have
understood the issues or problems to be solved and the software behavior necessary to
address those problems.
• It decomposes the problem into component parts. The simple act of writing down
software requirements in a well-designed format organizes information, places
borders around the problem, solidifies ideas, and helps break down the problem into
its component parts in an orderly fashion.
• It serves as an input to the design specification. The SRS serves as the parent
document to subsequent documents, such as the software design specification and
statement of work. Therefore, the SRS must contain sufficient detail in the functional
system requirements so that a design solution can be devised.

This project is concerned in the functional requirements and non-functional requirements.

2.3.1 Functional requirements

A functional requirement describes what a software system should do. Functional
requirements are the intended behaviors of the system. This behavior may be expressed as
services, tasks or functions that the system is required to perform. The functional
requirement is the study of what a system should be able to do, the functions it should
perform and describes the interactions between the system and its environment.
The system used to manage and process data according to the rule & regulations of the
organization. It also provides report generation facilities.
The new system provide services like modifying data (i.e. adding, updating and deleting
data) searching data of student, storing the data of student, generate grade reports of student
and others. The system implemented efficiently and effectively use of resources.
The database of the system provides the following functionality [7] [9].
 Data entry: This is the functionality that data is entered to the systems. The
system serves different interface that can manage data entry mechanisms in the
organization. Like student registration form student grade result registration form
 Data processing :The system on input data provided the following data
processing:
 Student registration
 Verify the requested information
14
  Validate student information
 The system generates student grade report.
 The system has provision for the administrator, record officer and department
head to post notice.
 The system should allow students to submit their information.
 System provides the option for the student to send feedbacks to Department and
record officer.
 The System provides the option students to view grade reports online.
 Instructors able to submit students grade report, Post assignments online.
 Students able to view and post assignments.

2.3.2 Non functional requirements

Non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors. Non-functional requirements are
often called qualities of a system. Other terms for non-functional requirements are
"constraints", "quality attributes", "quality goals" and "quality of service requirements". It is
additional qualities expected from the new student information system portal. Non- functional
requirement are not directly related with the functional requirement behavior of the system at
all but constraints on implementing the functional requirements defined in the use case model
[7] [8]
This project include the following system related nonfunctional requirements:-
 Security: - Student information system portal provides security for student
information database.
 Performance: - The new student information system portal has faster
response time and use a minimal space usage.
 Usability: - The student information system portal is easy and understandable
to use.
 Availability: - The student information system portal available for further use
while needed.
 Reliability: - The student information system portal operates as expected over
specified time interval.
 Fault tolerance: - student information system portal should be tolerable of fault
in case of hardware and software failure.

15
 2.3.2.1. Business Rule Identification
Business rules are statements about the enterprise’s way of doing business. They reflect
business polices. This part specifies and gives somewhat understanding of activities which
are being done in the existing system in terms of business rule.
 Name:-determine authentication to insert data
ID:-BR-1
Descriptions:-this business rule states that a person can insert data in to the data base
of the system if and only if that person is eligible to insert data and this is confirmed
with password.
 Name:-determine validity of data
ID:-BR-2
Description:-this business rule validates the input data according to validation rule set
to the Oracle 11gdatabase.
 Name:- determine eligibility to modify data
ID:-BR-3
Description:-this business rule states that to modify data a person should be a valid
user and this can be validated by username and password.
 Name:-determine eligibility to delete data

ID:-BR-4
Description:-this business rule states that to delete data from the database of the
system a person should be user of the system and this can be determined by use of
user name and password
 Name :- determine eligibility to access the database
ID:-BR-5
Description: - this business rule states that a user can access the database if he/she
has a username and password to access the data
 Name :- determine eligibility to generate report
ID:-BR-6
Description:-this business rule states that a person should have a valid username and
password
 Name :-determine validity of user name and password
Id:-BR-7

16
 Description:-this business rule states that both the password and username assigned
to user must not be occupied by another user before
 Name:- determine eligibility to create new user
ID:-BR-8
Description: - this business rule states that create the new user must be a
system administrator and this can be checked by his/her username and
password
 Name :- determine eligibility to modify his/her username and password
ID:-BR-9
Description:-this business rule sates that the person who modify username
and password should be a user and this can be checked by his/her username
and password

2.4 Requirement Analysis

2.4.1 Use-Case Diagrams
Use Case diagrams show the various activities the users can perform on the system. The
System is something that performs a function. They model the dynamic aspects of the system.
A use case diagram illustrates a set of use cases for a system, the actors of these use cases,
the relations between the actors and these use cases, and the relations among the use cases.
[B. Meyer 1997].
 An oval represents a use case.
 A stick figure represents an actor.
 A line between an actor and a use case represents that the actor initiates and/or
participates in the process.
Use cases
A use case describes the sequence of events of some types of users, called Actors, using some
part of the system functionality to complete a process.
Actors
An actor represents a type of users of the system or external systems that the system interacts
with. An actor is a user of the system playing a particular role [4] [6]. The actors that interact
with student information system web portal are:- Table 1 Actors Identification
1.Student
2.Record Officer
3.Registrar Manager

17
4.Department Head
5.Instructor
6.System Administrator
7.College Dean
8.Dormitory manager

The identification of use cases is one key issue in the development of interactive systems.
The use cases that used in student information system web portal are the following:-

Table 2 Use Case Identification

ID Use Case Name Include/use
UC1 Login
UC2 Register course information UC1
UC3 View Course Information UC1
UC4 Edit course information UC1
UC5 Register in courses UC1
UC6 Enter course results UC1
UC7 Edit course Results UC1
UC8 View Course Result UC1
UC9 View registered students list on course UC1
UC10 Submit Grade UC1
UC11 Edit Grade UC1
UC12 View submitted Grade UC1
UC13 Approve Grade Submission UC1
UC14 View Grade Report UC1
UC15 Post Assignment UC1
UC16 View posted Assignments UC1
UC18 Submit Assignment UC1
UC19 View submitted Assignment UC1
UC20 Add user profile UC1
UC21 Edit user profile UC1

18
UC22 View User profile UC1
UC23 Block users UC1
UC24 View Log events UC1
UC25 Post notices UC1
UC27 View notices

UC29 View Report UC1

UC30 Print Report UC1

UC31 Send feedback UC1

UC32 View feedback UC1

UC33 Register Student information UC1

UC34 Edit Student Information UC1

UC35 Manage Users Uc1

U36 View dormitory

U37 Assign dormitory UC1

2.4.1.1 Essential Use Case Modeling

An essential use case is a simplified, abstract, generalized use case that captures the
intentions of a user .For this project the team designs the following Essential use case
diagrams.

19
Figure 1 course management essential use case diagram

20
Figure 2 Grade Management Essential use case diagram

Figure 3Assignment Management Essential use case Diagram

Figure 4 User Management essential use case diagram

21
Figure 5 Student information Registration Essential use case diagram

Figure 6 Dormitory Management essential use case diagram

Table 3 :Essential use case description

Name: Submit grade
ID UC10
Actors Instructor
Descriptio Instructor submits students grade to registrar
n

22
Preconditi Instructor must log onto the system
on

Post Instructor Easily submit students grade

condition

Includes Login
Basic User Action System
Course 1. Instructor Response 2.The
of
invoke on Grade System displays
Action
submission page. the Grade
3. Instructor submission Page
fills the 4.The System
necessary displays Success
information message
and 5.Use Case Ends
Submit the
forms.
Alternative A: If the submitted form is not filled completely or
invalid.
course of
Action A4.The system displays “unsuccessful” message
A5.Instructor fills the missing information and
corrects invalid inputs.A6.The use case continues
from step 3.
Name Log in
Actors: Student, Record Officer, Instructor,
System Administrator, Registrar
Manger, Department head, college
dean, dormitory manager
Description Users are authenticated and taken
to their own user interface

Pre-condition Users must get an account from the

system administrator

Post-condition User is authenticated and taken to

his/her own user interface

B User Action System

a 1. The user Response
s 2.the
i opens the
c system
main page by
display
c writing the

23
 o URL website. othe Main
u
3.The user Home page
r
inputs user
s 4.
name a
e
password and The
submits
o system
f
n
a validat
c es the
t
i accoun
o t and
n
display
s the
user
require
inform
ation.
5.use case ends
Altern A If the login name or password is invalid
ate
A 4.The system displays invalid user
Course
of name or password message

Action A 5.The user reenters the user

name and password
A 6.The use case continues from step 3

Name: Register course Information

ID UC4
Actors Record officer
Description The record officer can register course information the students take.

24
Pre-condition There should be available courses and record officer should log onto
the system.

Post condition The record officer can register course information

Includes Login
Basic Course of User Action System Response
Action 1. The Record officer invoke on 2.the System displays the register
register course information page course information Page.
3. The record officer fills the 4.The System displays a success
necessary information and Submit message
the forms. 4.Use Case Ends

Alternative course A: If the submitted form is not filled completely or invalid.

of action A4.The system displays “unsuccessful” message
A5.The record officer fills the missing information and corrects
invalid inputs
A6.The use case continues from step 4

Name: View course Information

ID UC3
Actors Student, Instructor, Department head
Description student ,department head and instructor views course information
Pre-condition Course information should be registered on the database and log
onto the system.

Post condition The student, department head and instructor view course
information

25
Includes Login
Basic Course of User Action System Response
Action 1. The student, department 2.The System displays the view
head and instructor invoke on course information Page
view course information page 4.The System displays
3. The student, department head course information 4.Use
Case Ends
and instructor fill the necessary
information and Submit the
forms.

Alternative course A: If the submitted form is not filled completely or invalid.

of action A4.The system displays “unsuccessful” message
A5.The student ,department head and instructor fills the missing
information and corrects invalid inputs
A6.The use case continues from step 4

Name: View grade Report

ID UC14
Actors Student
Description The student views grade reports
Pre-condition Student must have grades on registered courses and must log onto the system

Post condition The student view grade reports and makes decisions
Includes Login
Basic Course of User Action System Response 2.The
Action 1.The student invoke on Grade System displays the Grade
report page report Page
3. The student fills the necessary 4.The System displays students
information and Submit the Grade report
forms. 5.Use Case Ends

Alternative course A: If the submitted form is not filled completely or invalid.

26
of Action A4.The system displays “unsuccessful” message
A5.The student fills the missing information and corrects invalid
inputs
A6.The use case continues from step 4

Name: View dormitory

ID UC36
Actors Student
Description The student views student dormitory.
Pre-condition Student must be registered as a member and must enter their id number or
registration number in to the system.

Post condition The students view his/her dormitory.

Basic Course of User Action System Response
Action 1.The student invoke on home 2.The System displays the home
page 3. The student enters his/her Page
id number or registration number 4. The System displays student’s
room number with the
and click view dormitory button.
corresponding building number.
5.Use Case Ends

Alternative course of A: If the submitted form is not filled completely or invalid.

Action A4.The system displays “unsuccessful” message
A5.The student fills the missing information and corrects invalid inputs
A6.The use case continues from step 4

Name: View course results

ID UC8
Actors Student
Description The student views course Results by entering their IDNO and course
code into the system
Pre-condition Student must have marks and registered on courses and log onto the
system.
Post condition The student table to view course results using the system.

27
Includes Login
Basic Course of User Action System Response
Action 1.The student invoke on view 2.The System displays the view course
results page course result Page
3. The student fills the necessary 4.The System displays students
information and Submit the course result
forms. 5.Use Case Ends
Alternative course A:if the required fields are not valid of action
A4. The system notifies the filled values invalid.
A5. The student try to fill other valid inputs in input fields
A6. The use case continues from step 3

Name: Register student Information

ID UC33
Actors Record officer
Description The Record officer registers student with full information about
himself/herself and a list of other information.

Pre-condition The student provides full information that clearly identifies student’s
identity and record officer should log onto the system.

Post condition The student information is registered in the database of the new system.

Includes(uses) Login

Basic Course of User action System Response

Action 1. The Record officer invoke on 2.The System displays the student
the Register student Information Information Registration page
3.The Record officer fills the form
and clicks on register button 4. The System displays
“successful” message.
5. Use Case Ends
Alternate A: If the submitted form is not filled completely or invalid.
Course of A4.The system displays “unsuccessful” message
Action A5.The Record officer fills the missing information and corrects invalid
inputs
A6.The use case continues from step 4

28
Name: Enter course results
ID UC6
Actors Instructor
Description The instructor Enters course Results into the system
Pre-condition Instructor must log onto the system.
Post condition The instructor able to enter course results using the system.
Includes Login
Basic Course of User Action System Response
Action 1.The instructor invoke on enter 2.The System displays the
course results page view course result Page
3. The instructor fills the necessary 4.The System displays
information and Submit the forms. success message 5.Use Case
Ends

Alternative course of A:if the required fields are not valid

action
A4. The system notifies the filled values invalid.
A5. The instructor try to fill other valid inputs in input fields
A6. The use case continues from step 3

Name: Edit student Information

ID UC34
Actors Record Officer
Description Student information needs updating.

Pre-condition The Record officer must login

Post Updated student information

condition

Includes Login

29
Basic Course User action System response
of Action 1.the record officer Updates un 2.the system display the updated
updated student information and information to the user other
information and submit 3.The use Case Ends

Name: Print report

ID UC30
Actors Record Officer, registrar manager
Description The record officer prints student’s grade report and other related reports.

Pre-condition The reports must be generated properly and users must be login to the
system

Post The record officer and registrar manager prints reports

condition

Uses Login

Basic Course User action System Response

of Action 1.The record officer and registrar 2.The system displays the record
manager logs to the system officer and registrar manager home
3.The record officer and registrar page
manager looks for fully validated 5.The Use Case Ends
reports
4.The record officer and manager
prints the report

Name: View Report

ID UC29
Actors Registrar Manager
Description The manager views reports by generating from the system

Pre-condition The manager must log on to the system

Post condition The system displays a report

Includes Login

30
Basic Course 1.The system displays the manager home page
of Action 2.The Manger fills the report generation on the home page
and clicks on generate button 3.The system displays the report
4.Use Case Ends

Name: EditcourseInformation
ID UC4
Actors Record officer
Description The record officer can edit course information in case if there is
mistake.

Pre-condition Course information should be registered on the database and record

officer should log onto the system.

Post condition The record officer can edit course information

Includes Login
Basic Course of User Action System Response
Action 1. The Record officer invoke on 2.The System displays the edit
edit course information page 3. course information Page
The record officer fills the 4.The System displays a success
necessary information and message
Submit the forms. 4.Use Case Ends

A: If the submitted form is not filled completely or invalid.

A4.The system displays “unsuccessful” message
A5.The record officer fills the missing information and corrects
Alternative course invalid inputs
of action A6.The use case continues from step 4

2.4.1.1 System Use Case

Unlike Essential use cases, System use cases are use cases that bring technological concerns
into account. System use cases are the real implementations of the proposed system

31
(Kruchten 2000). for this project the team developed the following System Use Case
Diagram.

Figure 7 System Use Case Diagram

2.4.2. Sequence Diagram
A UML Sequence diagram showing the sequence of interactions among objects and used to
represent or model the flow of messages, events and actions between the objects or
components of a system. Sequence Diagrams are also used primarily to design, document and
validate the architecture and interfaces of the system by describing the sequence of actions
that need to be performed to complete a task or scenario.[3] [4] The elements we used on
sequence diagrams are:
Destroy Element
Represents the destruction of a header element

Message
A simple message between header elements

32
Return Message
A return message between header elements

Figure 8 View course result sequence diagram

33
Figure 9 View grade report sequence diagram

34
Figure 10 view course information

Figure 11 Register student information sequence diagram

35
Figure 12 Student register on course sequence diagram

36
Figure 13 Submit grade sequence diagram

Figure 14 student post Assignment sequence diagram

37
Figure 15 Instructor post Assignment sequence Diagram

38
Figure 16 View submitted grade sequence diagram

Figure 17 View report sequence diagram

39
Figure 18 View log event sequence diagram

Figure 19 create account sequence diagram

40
Figure 20 Manage account sequence diagram

Figure 21 update student information diagram

Figure 22 View dormitory sequence diagram

41
 2.4.3. Class diagram
A class diagram in the Unified Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects (Ambler 2004).for
this project the project team develop the following
class diagrams.

Figure 23 Class diagram

2.4.3. Activity Diagram

Activity diagrams are used to document the logic of a single operation/method, a single use
case, or the flow of a business process. Activity diagrams essentially a flowchart showing
flow of control from activity to activity. It includes modeling the sequential process. It also
includes modeling the flow of an object as object as it moves from one state to another state
at different points in the flow of control.

42
Figure 24 View Grade Report Activity Diagram

43
Figure 25 Submit Grade report Activity Diagram

44
Figure 26 Post Assignment Activity diagram

45
Figure 27 Enter course result Activity Diagram

46
Figure 28 View course result Activity Diagram

47
Figure 29 User management Activity Diagram

48
Figure 30 department management activity diagram

CHAPTER THREE
3.System design
3.1 Introduction
System design is the transformation of the analysis model into a system design model. Up to
now we were in the problem domain. System design is the first part to get into the solution

49
domain in a software development. This chapter focuses on transforming the analysis model
into the design model that takes into account the non-functional requirements and constraints
described in the problem statement and requirement analysis sections discussed earlier. The
purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of
design created by the designer. If one wants to change to the system after it has been put in to
operation depends on the quality of the system design. [4][9].
3.1.1 Design goals and objectives
The objectives of design are to model the system with high quality. The design goals are
derived from non-functional requirements that means non-functional requirement is the
description of the feature characteristics and attribute of the system as well as any constraints
that may limit the boundary of the solution.
Design goals describe the qualities of the system that the developers should consider:-
 Reliability: Debre markos university student information system portal should be reliable.
 Fault Tolerance: Debre markos university student information system portal should be fault
tolerant to loss of connectivity with the service.
 Security: Debre markos university student information system portal should be secured, i.e., not
allow other users or unauthorized users to access data that has no the right to access it.
 Modifiability: Debre markos university student information system portal should be modifiable
for further modification and enhancement of the application.
 Performance: - The system should respond fast with high throughput, i.e. it should perform the
task quickly possible as possible such as submitting student grades reports and generating
students’ grade reports, viewing student grade report and other related information etc.
 Cost: The system should be developed with minimum cost possible. In reality there is always
trade-offs or disadvantages and therefore from its previous experience the University prefers to
invest more on development cost than maintenance cost to minimize bugs which may appear at
the later stage.
 End User Criteria: - The system should have simple and understandable graphical user Interface
such as forms and buttons, which have descriptive names. It should give reliable response
for each user request at least before the session expires. All the interfaces, forms and buttons
are written or designed in a simple language or common language so that the user can access it
without any difficult [4][9]

50
 3.2. Design the class diagram
The class diagram represents the static view of an application. Class diagram is not only used
for visualizing, describing and documenting different aspects of a system but also for
constructing executable code of the software application. The class diagram describes the
attributes and operations of a class and also the constraints imposed on the system. The
classes diagrams are widely used in the modeling of object oriented systems because they are
the only UML diagrams which can be mapped directly with object oriented languages. The
class diagram shows a collection of classes, interfaces, associations, collaborations and
constraints. It is also known as a structural diagram for this the team developed the following
class diagram.

Figure 31 Design class diagram

3.2.1. Description of design class diagram

Documenting class model is used to document the detail about a class as well as the
reasoning behind any trade off .The following are the documentation of the class model for
the student information system.

51
Student class
Attribute Purpose Type
Sid Represent student unique String
identifier

Name Represent Name of student String

Age Represent Age of student Int
Sex Represent Sex of student String
Department Represent department of String
student

Year Represent academic year of Int

student.

Semester Represent at what semester Int

is the student study

Mother name Represent Mother name of String

student

Method for the student class

Method Purpose
View grade report() Used to view student SGPA,CGPA,PGPA
View course result() Used to view each individual course result
Submit assignment() Used to submit assignment for the teacher
Register on course() Used to register on course
View course info() Used to view relevant information about the
course matter.

View posted assignments() Used to view assignments submitted by the

teacher

View notice() Used to view notice which is posted

Send feedback() Used to send feed back
View dormitory() Used to view student dormitory

Instructor class
Attribute Purpose Type
Username Represent user name of the String
instructor used in the system

52
Password Represent the password used String
in order to access the system

Method for the instructor class

Method Purpose
view submitted assignment() View assignments submitted by the student
Post assignment() Post assignments for students
Submit grade() Submit grade to department
view course information() Used to view course related information
Enter course result() Enter course result of the course
Edit course result() Used to update course result if the error
happens.

login() Used to enter the site by entering username

and password

Department class
Attribute Purpose Type
Did Uniquely identify department String
Dname Represents name of the String
department

Course class
Attribute Purpose Type
Ccode Uniquely identify the course String
Cname Represents name of the course String
Prerequisite Represent Perquisite of String
course

Chrs Represents credit hour of the Int

course

Account class
Attribute Purpose Type
Username Uniquely identify the user to String
enter the site

Password Represents name of the course String

User type Represents privileges of the String
user

53
Status Represents status of the user Int
Record officer class
Attribute Purpose Type
Id Represent record officer String
unique identifier

Name Name of record officer String

Username Used to identify the user String
enter to the site

Password Used to enter to the system String

Method for Record officer class
Method Purpose
Register() To register new students as a member
Update stud information() Change/update student information when
necessary

View submitted grades() View/retrieve student grade

Approve grade submission() Approve grade submitted by the department
Post notices() Announce new notices
Login() Accessing the system
System admin class
Attribute Purpose Type
Id Represent system admin String
unique identifier

Name Represent Name of system String

admin

Username Used to identify the user String

enter to the site

Password Used to enter to the system String

Method for system admin class

Method Purpose
Add user profile() To record user profile
Block user() Block/ignore users when users are not
important

Change user profile() Change/update user profile when necessary

54
View user profile View/retrieve user profile
View log event() View log information to manage the users
Login() Accessing the system

Department head class

Attribute Purpose Type
Id Represent department head String
unique identifier

Name Represent Name of String

department head

Username Used to identify the user String

enter to the site

Password Used to enter to the system String

Method for department head class

Method Purpose
View course info() View information of the course
Post notices() Announcing when there is new thing
View student list() View how many students are present in the
department

Approve grade submission Approve grades that the teacher posts

View feedback() View feed feedback from users
Login() Accessing the system
Registrar manger class
Attribute Purpose Type
Id Represent registrar manger String
unique identifier
Name Represent Name of registrar String
manger

Username Used to identify the user String

enter to the site

Password Used to enter to the system String

Method for registrar manger class

55
Method Purpose
View reports() View deferent reports from users
print() Print reports
login() Accessing the system
College dean class
Attribute Purpose Type
Id Represent College dean String
unique identifier

Name Represent Name of College String

dean

Username Used to identify the user String

enter to the site

Password Used to enter to the system String

Method for college dean class
Method Purpose
Post notices() Announcing when there is new thing
View student list() View how many students are present in the
department

Approve grade submission Approve grades that the department posts

View feedback() View feed feedback from users
Login() Accessing the system

3.3. Collaboration diagram

A collaboration diagram describes interactions among objects in terms of sequenced
messages. Collaboration diagrams represent a combination of information taken from class,
sequence, and use case diagrams describing both the static structure and dynamic behavior of
a system.
The UML Collaboration diagram is used to model how objects involved in a scenario interact,
with each object instantiating a particular class in the system. Objects are connected by links,
each link representing an instance of an association between the respective classes involved.
The link shows messages sent between the objects, and the type of message passed.

56
Figure 32 Login Collaboration Diagram

Figure 33 Grade Report Submission Collaboration Diagram

57
Figure 34 View Grade Report Collaboration diagram

Figure 35 Grade submission Approval collaboration Diagram

58
Figure 36 register student collaboration diagram

Figure 37 create account collaboration diagram

59
 3.3.1. Physical data model
Physical data model represents how the model built in the database. A physical database
model shows all table structures, including column name, column data type, column
constraints, primary key, foreign key, and relationships between tables.]
Table 4 Student table
Colum Data type Primary Foreign key Uniqueness Nullable
n name key

Studen Varchar2(255)   No
t ID
Studen Varchar2(255) No
t Name
Studen Varchar2(255) No
t father
Name
Studen Varchar2(255) No
t G/F
Name
Birth Date No
date
Gender Varchar2(255) No
Nation Varchar2(255) No
ality
Region Varchar2(255) No
Zone Varchar2(255) No
College Varchar2(255)  No
Department Varchar2(255)  No
Academic year Date/Time No
Mother name Varchar2(255) No
Mother father name Varchar2(255) No
Program Varchar2(255) No

Table 5 course table

Column name Data Type Primary Foreign Key Uniqueness Nullable
key

Course Code Varchar2(255)   No

Course title Varchar2(255) No
Chr Number No

60
 college Varchar2(255) No
Department Varchar2(255)  No
year Number(1,2,3, No
4,5,6)
semester Number(1,2,3) No
Prerequisite Varchar2(255) Yes

Table 6 Department table

Column name Data type Primary key Foreign key Uniqueness Nullable
Deptno Varchar2(255)  No
DeptName Varchar2 (255)  No
Dept location Varchar2 (255) No
College Varchar2 (255)  No

Table 7 Student Course table

Data Type Primary Foreign key Uniqueness Nullable
key

Varchar2(255)   No
Course Varchar2(255)   No
Code
CrHrs Number No
Student Number(1,2,3,4,5,6) No
Year
Student Number(255) No
Semester
Student Varchar2(A, B, C, Yes
Grade D, F)
Accad Year Date/time No

Table 8 Instructor Table

Column name Data Primary Foreign key Uniqueness Nullable
Type key

61
 Instructor ID Varchar2   No
(255)
Instructor name Varchar2 No
(255)
Instructor father Varchar2 No
name (255)
Education status Varchar2 No
(255)
Email Varchar2 Yes
(255)
Phone Number Yes

Table 9 Instructor Course Table

Column Data Type Primary key Foreign key Uniqueness Nullable
name

instructor ID Varchar2(255)    No
Course Code Varchar2(255)   No

Table 10 Instructor Student Table

Column Data Type Primary key Foreign Key Uniqueness Nullable
name

Instructor id Varchar2(255)   No
StudentID Varchar2(255)   No

Table 11 grade Report table

Column Data Type Primary key Foreign Uniqueness Nullable
name key

SID Varchar2(255)   No
Student Number(1,2,3,4,5,6) No
year

Semester Number(1,2,3) No
SGPA Float Yes

62
 Stotalcrhr Number Yes
CGPA Float Yes
Ccrhr Number Yes
Academic Varchar2(255) Yes
Status
Academic Number No
year

Table 12 T college Table

Column name Data Type Primary key Foreign Key Uniqueness Nullable
College no Varchar2(255)  No
College name Varchar2(255)  No
College Varchar2(255) No
location

3.4. Component diagram

In the Unified Modeling Language, a component diagram depicts how components are wired
together to form larger components and or software systems. They are used to illustrate the
structure of arbitrarily complex systems. A component diagram displays the structural
relationship of components of a software system. These are mostly used when working with
complex systems that have many components. Components communicate with each other
using interfaces. The interfaces are linked using connectors. Component diagrams show the
physical placement of the components in the system. It is a type of design diagram that shows
overall system architecture and the logical components within it for how the system
implemented [2].

63
Figure 38 Component diagram

64
 3.5 Deployment diagram
Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagrams shows
how they are deployed in hardware.
UML is mainly designed to focus on software artifacts of a system. But these two diagrams
are special diagrams used to focus on software components and hardware components. So
most of the UML diagrams are used to handle logical components but deployment diagrams
are made to focus on hardware topology of a system [2] The purpose of deployment diagrams
can be described as:
 Visualize hardware topology of a system.
 Describe the hardware components used to deploy software components.
 Describe runtime processing nodes. For this project the project team developed the
following deployment diagrams.

65
Figure 39 Deployment diagram

66
3.6 User interface
3.6.1. Home page user interface

67
3.6.1.1 Student grade report user interface

68
3.6.1.2 Student grade edition user interface

69
 CHAPTER –FOUR
4. System Implementation
System implementation is the final stage in software development stage in which the design is
putting in to coding or real application.

4.1 Overview of Programming technology

This project used JSP and Servlet server side programming technology integrated with Oracle
11g database with a programming language.
Why use JSP Because:
 The Jsp programming language is more secure.
 It's available for free
 It runs on many different operating system
 easy to access other web-based tools through Jsp
In general Jsp is a widely-used open source general-purpose scripting language that is
especially suited for web development and can be embedded into HTML.
JSP (java server page) is a server-side scripting language designed for web development but
also used as a general-purpose programming language.

4.2 Sample Implementation code

<body>
<%@page import=" java.text.SimpleDateFormat"%>
<%@page import="java.util.Date;import java.text.*"%>
<%@page import="java.util.Calendar"%>
<!-- start header -->
<%@page import="java.sql.*" %>
<%@page import="java.io.*" %>
<%
int count=0;
String name="";

70
 String fname=""; try
{ Class.forName("oracle.jdbc.d
river.OracleDriver");

Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe", "student", "student");
String u = (String) request.getSession().getAttribute("userid");
Statement stmt=con.createStatement();
ResultSet rs = stmt.executeQuery("select * from SUBMITTEDGRADES where
approvalstatus='2'"); while(rs.next())
{
count=count+1;
}
PreparedStatement ps = con.prepareStatement("select *from login where un=?");
ps.setString(1,u); rs = ps.executeQuery(); if(rs.next())
{
name=rs.getString("name"); fname=rs.getString("fname");
} rs.close();
con.close();
ps.close();
}
catch(Exception ex) {

}
%>
<div id="header">
<div id="logo">
<h1 style="margin-left: 140px"><a href="#">Student Information System Web
Portal</a></h1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<img
src="images/30.JPG" height="138" width="160"/>
</div>
<div id="menu">
<ul id="main">
<li class="current_page_item"><a

71
<li><a style="color:#FFCB00;text-transform:uppercase;font-weight:bolder">WELCOME
&nbsp;&nbsp;<%=name%>&nbsp;&nbsp;<%=fname%></a></li>
<li><a href="logout.jsp"onclick="return confirm('Are you sure to logout')">logout </a></li>
</ul>
</div>
</div>
<!-- end header -->
<!-- end header -->
<div id="wrapper">
<!-- start page -->
<div id="page">
<div id="sidebar1" class="sidebar"style="margin-left:0px;width: 250px">

<ul>
<li>
<h2>Dormitory Manager Tasks</h2>
<ul>
<li><img src="images/lo.png"height="15"width="20"/><a href="addblock.jsp">Register
Block Information</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a href="reccourseinfo.jsp">Edit
BLock Information</a></li>
<li><img src="images/lo.png"height="15"width="20"/><a
href="addroomcap.jsp">Add Room Capacity</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a href="assign.jsp">Assign Students</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a href="assignedstud.jsp">Assigned
Students</a></li>
<li><img src="images/lo.png"height="15"width="20"/><a
href="unassignedstud.jsp">UnAssigned Students</a></li>
<li><img src="images/lo.png"height="15"width="20"/><a href="stud.jsp">Search
Students</a></li>

72
</ul>
</li>
<li>
<h2>Other Related Sites</h2>
<ul>
<li><img
src="images/lo.png"height="15"width="20"/><a
href="http://www.google.com">Google</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a
href="http://www.yahoo.com">Yahoo</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a
href="http://www.gmail.com">Gmail</a></li>
<li><img
src="images/lo.png"height="15"width="20"/><a href="http://www.dmu.edu.et">DMU
website</a></li>
</ul>
</li>
</ul>
</div>
<!-- start content -->
<div id="content">
<div class="wrapper">
<div id="main" style="padding:50px 0 0 0;margin-top:-30px">

<!-- Form -->

<input type="button" value="Print&nbsp;&nbsp;&nbsp;&nbsp;" onclick="
printContent('print_thistag');"style="height:34px;width:100px;color:red;text-align:
center;margin-top:-4px">
<form id="contact-form" action="#" method="post" class="print_thistag"style="margin-top:-
50px;width:565px;margin-left: -32px">
<br/>

73
<h3 style="font-family:Helventia"><center><i>Debre Markos University<br>Accademic
Year &nbsp;<%Date d11=new Date();%><%=d11%><br>Students Dormitary
Placement</i></center></h3>
<%@page import="java.sql.*" %>
<%@page import="java.io.*" %>
<%@page import="java.util.ArrayList" %>
<%
try
{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
conn=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","dorm","dorm");
Statement st=conn.createStatement();
String btype=request.getParameter("sex");
int bc=0; int size=0;
ResultSet rs=st.executeQuery("select * from block where btype='"+btype+"'");

ArrayList ar=new ArrayList(); while(rs.next())

{
String bno = rs.getString("bno"); bc
= rs.getInt("bcapacity");
%>
<%
ar.add(bno);
} rs.close();
size=ar.size();
%>
<p style="font-size:14px;color:red">Total Number of Buildings
Available are:<b style="color:blue"><%=size%></b></p><br/>
<%
for(int i=0;i<=size;i++)
{
int bcap=0; int
rcap=0;
74
Statement st3=conn.createStatement();
ResultSet rs3=st3.executeQuery("select * from block where bno='"+ar.get(i)+"'");
if(rs3.next())
{
bcap=rs3.getInt("bcapacity");
}
%>
<h3 style="font-size:15px">buildings &nbsp;:<%=ar.get(i)%></h3>
<%
for(int ii=1;ii<=bcap;ii++)
{
Statement st4=conn.createStatement();
ResultSet rs4=st4.executeQuery("select * from room");
Statement st9=conn.createStatement();
ResultSet rs9=st9.executeQuery("select * from stud where status='0'"); if(!(rs9.next()))
{
request.setAttribute("message", "There is No students unassigned all are assigned");
getServletContext().getRequestDispatcher("/assign.jsp").forward(
request, response);
} if(rs4.next())
{
rcap=rs4.getInt("rcapacity");
}
%>
Dorm Number <%=ii%><br/>

<div><div style="width:80px;float: left">No&nbsp;&nbsp;</div><div

style="width:100px;float: left">Id Number&nbsp;&nbsp;&nbsp;</div><div
style="width:145px;float: left">
Student Full
Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</div>
<div
style="width:80px;float:left">Department&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;</div>

75
<div style="width:80px;float:left">Class Year&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</div>
<div style="width:80px;float:
left">Gender&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</div></div>

<%
for(int iii=1;iii<=rcap;iii++)
{
ResultSet rs2=null;
Statement st2=conn.createStatement();
Statement st1=conn.createStatement();
ResultSet rs1=st1.executeQuery("Select * from stud where status='0' and
sex='"+btype+"'"); if(rs1.next()){

rs2=st2.executeQuery("insert into reg values('"+rs1.getString("sid")

+"','"+ar.get(i)+"','"+ii+"')");
} if(rs2.next())
{
%>
<div>
<div style="float:left;width: 80px"><%=iii%>)&nbsp; </div>
<div style="float:left;width:
100px"><%=rs1.getString("sid")%>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </div>
<div style="float:left;width: 145px"><%=rs1.getString("name")%>&nbsp;&nbsp; <
%=rs1.getString("fname")%>&nbsp;&nbsp;
</div>
<div style="float:left;width: 80px">
<%=rs1.getString("department")%>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
p;&nbsp; </div>
<div style="float:left;width:
80px"><%=rs1.getString("batch")%>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
sp;
</div>
<div style="float:left;width: 80px"><%=rs1.getString("sex")%>&nbsp;&nbsp;

76
</div>
</div> <br/> rs2=st2.executeQuery("update stud set status='1' where
sid='"+rs1.getString("sid")+"'");
}
}
%>
<%
}
}
}
catch(Exception ex)
{
}
%>
</form>

<!-- /Form -->

</div>
</div>
<script src="js/scriptslog.js"></script>
</div>
<!-- end content -->
<!-- start sidebars -->
<div id="sidebar2" class="sidebar"style="width:190px">
<ul>
<li>
<h2>Profile</h2>
<%@page import="java.sql.*" %>
<%
try {
Class.forName("oracle.jdbc.driver.OracleDriver");
Connectioncon =
DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe", "student", "student");
77
 String userid = (String) request.getSession().getAttribute("userid");
PreparedStatement ps = con.prepareStatement("select * from login where
un='"+userid+"'");
ResultSet rs = ps.executeQuery(); while
( rs.next()) {
out.println("<center><img width='180' height='180' src=photoservlet?un=" +
rs.getString("un") + "></img></center><p/>");
}

con.close();
}
catch(Exception ex) {

}
finally {

} %>

</li>
<li>
<h2>Calendar</h2>
<div id="div3_example" style="margin:10px 0 30px 0; border:dashed 1px red;
width:200px; height:230px;">
</div>

</li>
<li>
<h2>Photo Gallery</h2>
<ul>
<li><img
src="images/dd.jpg"width="180"height="230"/></li>

</ul>
</ul>
78
 </div>
<!-- end sidebars -->
<div style="clear: both;">&nbsp;</div>
</div>
</div>
<!-- end page -->
<div id="footer">
<p class="copyright" style="font-size: 15px">Copy
Right&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&copy;&nbsp;&nbsp;2007 e.c All Rights Reserved
&nbsp;&bull;&nbsp; Design by <a href="#">IT 4th year Group 10 members</a>.</p>
<p class="link"><a href="#">Privacy
Policy</a>&nbsp;&#8226;&nbsp;<a href="#">Terms of Use</a></p>
</div>
</body>
</html>

CHAPTER FIVE
5 Discussion and Results
The project is aimed at developing a web based system, for Debre Markos University
students’, staffs and community members’ by connecting and combining them into one
system which is “Student information system web portal” to use ICTs intervention in
education. In chapter one we have determined the title of the project to “Student information
system web portal”. Then the team described the problems of the existing system, the
objective of that project, the scope and limitation of the project, beneficiaries of the project,
feasibility and breakdown of the structure have been discussed including the methodology of
the project which describes what and which material the team used to accomplish the
proposed system. In Chapter two the team performed a detailed analysis that describes what
the current system looks. In analysis the team identified the problems of the current system.
Then we used an essential use case to model the features of the existing system by identifying
actors and use cases. After analysis we determined the requirements of the proposed system
in terms of functional and non-functional requirements. After these the team has studied

79
object oriented analysis and design techniques like activity diagram, sequence diagram, class
diagram with relations, attributes and methods.
The third chapter of the project discussed about the system design and prototyping which tries
to change the conceptual model of information for the problem domain that raised on the
chapter one of the existing system and solve that problem into actual interface. To accomplish
this, the team used different types of designing and analysis tools and component diagram.
Starting from the initial phase of the project life cycle the project team identifies the problems
appeared in the existing system and provide solutions. The existing system is limited only for
technology students and displays students semester grade point average and cumulative grade
point average not including the academic status of the student. After the complete analysis of
the project the team got the following results
-Developed a system that enables students to view grade report, view assignment, view
academic status of student, students view their dormitory.
-Developed a system that enables instructors to submit students’ grade, post assignments.
-Developed systems that minimizes the work load of work load registrar, teachers, students

5.1. Recommendation
This project gives some hint in web site developing as well as to know about Java technology
and Oracle database, also it gives better knowledge in Microsoft word and office than before
and it initiates for developing other web based projects in the future.
Any user who wants to interact student information system application should have some
knowledge. In order to clarify who required what knowledge the team Recommended:

1. On the users side

 User must have a basic firsthand experience with systems or other related
experiences.
 User must have a basic knowledge of computer.
 User must have a basic skill on how to use the system.
 Training user should be considering for best performance and efficiency of IT
technology.
 Behavioural change of the users of the system to adapt the new system.
2. On the organizations side:
 Organization should have adequate computer facilities to the activities of
student information system.

80
  Budget should be allocated to take specific measure:
1. To change the manual system into new system.
2. To maintain the system in a timely and speedy manner

5.2 Future enhancements

To enhance the performance and functionality of the system the next developer can include
the following tasks.
 Include withdrawal and readmission of students
 Online add and drop of courses
 Develop better security Mechanisms
 Include clearance and cost sharing system
 SMS module to notify instructors while they submit grade

References
1 Web Reference
[1]. [http://en.wikipedia.org/wiki/Software_development_methodology#Overview]
[2]. [http://e-articles.info]
[3].[http://www.techwrl.com/techwhirl/magazine/writing/softwarerequirementspecs.html](Co
nstantine and Lockwood 1999)
[4].[http://en.wikipedia.org/wiki/Object-oriented_analysis_and_design#Object oriented
analysis]
[5] [http://en.wikipedia.org/wiki/Non-functional_requirement].

2 Bibliography
[6]. [Ambler 2001] the object primer second edition (Scott W. Amber)
[7].[Hoffer 2000] Modern System Analysis and Design by Jeffery A. Hoffer Fred R.
Mcfaddan
[8].[Whitten] System Analysis and Design Methods (Jeffery l. Whitten and Loinnie D.
Bentley)
81
[9].Object Oriented Software Engineering book

Acronyms and abbreviations used in the project

We have used some abbreviation and acronyms throughout the development of the project.
These acronyms and abbreviation used in the project are the following –
 MS word 2010- Micro soft office 2010
 MS power point 2010-- Micro soft office power point 2010
 Chr- credit hour
 UC- use case
 Sid – student identifier.
 Dept no- department number
 Accad year-academic year
 SGPA-Semister
 CGPA-commulative grade point
 Crhr.commulative credit hour
 Col no-college number
 Insid –instructor identifier
 Ccode-course code
 Jsp –java server page
 Html –hypet text markup language  Css –cascading style sheet

82
83