Chapter one

1. Introduction
Now a day, education plays a great role in development of any country because education system
is the backbone of every nation to provide a strong educational foundational to the young
generation to ensure the development of open-minded global citizens securing the future for
everyone. Many of education organizations try to increase education quality .One of the aspects
of this improvement is managing of school systems.

The ministry of model school of Haramaya University education organizations has perform
management of education system to help the community of that area. However, there is no
computerized system processed support school management system since, changed to
computerized ways to minimize this problem that the school management system faces to
redesigning process takes a long time.

Education is central to development which is one of the most powerful instruments for reducing
poverty and inequality foundation for sustained economic growth.

Objective of our project is to change the current manual Haramaya university model school
management system into computerized one that consists of tasks such as registering students,
attendance record keeping controlling absentees, producing report cards producing official
transcript, preparing timetable and producing different reports.

Automation is the utilization of technology to replace human with a machine that can perform
more quickly and more continuously.

However, the school system in the Haramaya University Model School is not automated and the
record officers generate transcripts and reports manually and the school administrators use their
experienced knowledge of miss and hint approaches to prepare timetables.

1
1.1. Background
Haramaya university model school was established in 1956 E.C (Ethiopian Calendar) years after
the commencement of the late Alemaya College of Agriculture. And for eleven years, only
children of American staff attended the school, all teachers being of American nationals.

However, stands first among junior schools in Hariri region in the 2011 Grade Eight Regional
Examination result. The school is also expansively working to upgrade the services of the day
care. Currently, however, applications from potentially deserved haramaya university staff have
crowded the center.

Explaining the groundwork leading to these achievements emphasized Small class size; practical
engagements and special tutorials are also highly valued and implemented by the school. They
added, intensive follow up of HU and the accessibility of student-parents have also contributed
to the promising achievements of the school. The school is closely working with pedagogy and
language departments of Haramaya University. Though it is provided with different laboratory
inputs, it has not yet adequately sustained its relation and cooperation with science concerning
student admission, the school implements a chain of admission circle by which Haramaya
university academic staff members get primary advantage followed by permanent workers,
contract workers, other stakeholders such as bank workers, and the community. And, informs,
every new coming students of any grade attend entrance examinations by which those who fail to
score the set limit are rejected.

1.2. Prototype of the Problem

As we observed when dealing with the existing system of HU Model school management system
we have analyzed the following problems such as:-

 Wastage of resource or data redundancy (i.e. wastage of time, human, cost )

 Lack of good service for the students.
 Improper management of Record office service.
 Exhausting documentation which is manual.
 Poor schedule management system.

1.2.1. Solution of our proposed system.

2
  Everything is documented on the computerized system so that it will reduce the time, cost
and resource wastage that was found in the existing manual system.
 Provide better schedule using automate system (computerized system).
 Provide better Generated transcript using automate system.
 Provide better student registration using automate system.

General our project is to solve the current manual system of Haramaya university model school
management system listed in specific objective into computerized one (automate).

Team Composition
As one team member, we communicate each other by discussing on the issues concerning our
project. And sometimes we divide and do a separate task for the seek of time scheduled
consuming to facilitate (forward) the project for the target of succeeding in. we regularly contact
our advisor to test on our work background direction way either on right way or on wrong way to
submit the progression of work and irregularly to ask questions related to the project
development, to get advice, information and resources necessary to our system development. The
following table summarizes the team subdivision and their responsibilities.

Responsibility

The member responsibility is prepared as below diagram that we do everything

by helping each other.
Participants Group Documentation Coding and Idea Data Testing
coordinator part Designing sharing gathering

Kasaye Binega      

Stagaye Tilahun      

Wakjira Lema      

Table Team members or Participants and their Responsibilities.

3
 1.3. Objective
1.3.1. General objective
General objective of our project is to change the current manual Haramaya university model
school management system into computerized one (automate).

1.3.2. Specific objective

The main objective of this project is to computerize the manual system & reduce the time
consumption.

In other words we can say that our project has the following objectives:-

 To develop the registration of the students.

 To Generate Transcript of the students.
 To assign Time table.
 To facilitate attendance record keeping.
 Generating report for a task performed.

1.4. Scope of the project

Generally our project scope is limiting to the data processing of manual works in Haramaya
university model school using software that:-

 Proposing an automated Student registration form.

 Proposing an automated generate Transcript of students.

 Proposing an automated Generate timetable.

 Proposing an automated recording attendance

 Investigation of the drawbacks of the existing manual HU model school

management system.

 Study of the existing problem HU model school management system.

The project will not include (Out of scope)

 The system by itself cannot decide to whom it gives the privilege of accessing it rather
what it does is affording partitioned privileges (accounts) with passwords when asked by

4
 the system administrator. This is done in considering that the director of school
(administrator) assigns user types to access the system according to their limitation.
This is to mean the system is not going to allow any ordinary users to access it, rather
gives access to those who are already got there privilege(accounts) by the system.

1.4.1. Significant of the project

The main significant of this project is to help the HU model school management system to
perform their work: -

 Faster
 Efficient
 Accurate
 Secure and with wise use of resources available
 Technological advancement of the school.
 Helps to administer, employees and any users.

Chapter 2 Proposed Systems

For our proposed system we preferred the object oriented system analysis and design (OOSAD)
approach, which is by using unified modeling language (UML). This is because it includes the
overall features of OOSAD. The other reason is that using object-oriented programming we can
write clear, more reliable, more easily maintained programs.

We preferred Object-oriented approach for the following advantages: -

 To simplify the design and implementation of complex programs.
 Increase reusability: support reusability of the system’s code
 Increased extensibility: to add and change the existing module without affecting the rest
of the program.

5
  To make it easier for teams of designers and programmers to work on
 To decrease the burden of maintenance.

2.1. Proposed system overview

The proposed system aim to alter the task of the student registration form ,produce transcript of
student ,produce attendance and produce timetable in different direct by removing the bulky
process of manual system preparation by a computerized system.

2.1.1. Activities of proposed system

 Save the resource such as paper, pen, time, manpower and etc
 Avoiding overlapping of schedule of class.

2.2. Functional Requirements

Functional requirement describe the interaction between the system and it environment
independence of implementation.

The functional requirements of our projects done the following functions:-

 To display registration information.

 The project automates the activities by providing updating, searching,

inserting, and saving information’s.

 To display generate Transcript.

 To display schedule.

 To display attendance report information.

6
  View generating reports
2.3. Non _Functional Requirements
These requirements do not directly affect the performance of the system but there presence is
useful for the system. A non-functional requirement relates to the technical aspects of system
must fulfill, such as performance-related and reliability issue. Some of the non _functional
requirements are: -

Robustness: - The system should be tolerant errors the produce error reports that are simple to
unsorted by the user.

Security:-To protect students and employee’s data and system misuse, the system should provide
restriction in using system functionality and information access by its user, i.e. the system uses
Role based authorization technique.

In short, system must be protected from being accessed by unauthorized user.

Availability: - The system should easily be available at any desired time.
Performance: -The system should be well fit to perform operations clearly without any problem.
Since the system is automated that provide to installed by user and viewing the current
application.

2.4. System Models

The system model is composed of three individual models:-

The functional model: represented by use case and Scenario,

The system object model: represented by classes and objects diagrams and

The dynamic model: represented sequence diagram based on this our new proposed system.
Modeling of Existing system

The very objective of the study modeling of existing system is to have a complete understanding
of the existing manual system. As we have tried to mention in the previous chapter the existing
manual system has drawback that is costly, time wasting in use of labor, and other material, and
many more. This is due to its model. In the following section we have tried to mention proposed
modeling of the existing manual system which includes:-

7
  Use case Diagram of Automated system

 Activity diagram of the automated system.

 Class diagram of the Automated system and

 Sequence diagram of the Automated system

System Development Environment

We use the following System Development Environments for documentation’s new proposed
system. Those are:

 Microsoft word 2007 for documentation part.

 Microsoft Visio 2003 for designing part.

 Era max 6.1 software for designing part

 Dia software for designing part.

 Wamp server for coding (PHP and MYSQL)

 HTML and web development

2.4.1. Use cases

Use case defines set of interaction between actors and proposed system models considerations. It
is a methodology used in system analysis to identify, clarify and organize all system activities
that have significations to contain. Use cases of the system are identified as can be seen from the
diagram each actor has access to different Use Case. The following use cases have been
identified from the system specification.

 Request
 Register

8
  Create account

 Login

 Record attendance

 Distribute schedule

 Distribute transcript

 Report card

2.4.1.1. Use Case Description

Use case name Login

Description The user can login if they have user name and
password

9
Pre-condition Admin of the school should have their own
user account and password

Actors Admin

Flow of events 1.Admin wants to access the system

2.Admin don’t forget his /her user name and
password
3.The system confirms the validity of the user
name and password
4.Admin must close to exit
5.Use case end

Alternative flow 1.If step2 is not ,user can’t login

2.If step 4 is open valid for any user

Post condition The user logs to the system and directs to the
correct page according to admin position

Table1: use case description of login system.

Use case name Record attendance

Description To record attendance of students in each school day

Precondition
must log A home A homeroom teacher must login as the home room teacher of the class to
record attendance .

10
Actors Home Room Teachers

Step1. A home room teacher wants to record absentees from the class
Step2. The home room teacher fills in the attendance slip in the class
room.
Flow of event Step3. Having the attendance slip the home room teacher logs in to record.
Step4. Home Room Teacher records absentees and submits.
Step5. System acknowledges.
Step6. Use case ends.

Alternative flow of Step1.User is not a home room teacher of the class

events Step3. User can’t record attendance for the required class of students.
Step4. Use case ends.

Post condition Record attendance will be generated.

Table1: use case description of record attendance.

Use case name Distribute Transcript.

Description To produce Transcript for students per semester

Precondition A student must have complete grade marks in all subjects of the
semester

Actor Record Officer

11
 Step1. The record officer for prepare Transcript to arrange the
class/section to which the student belongs.
Step2. The record officer select criteria need necessary define
Transcript
Step3. The Transcript processes if the student complete in all
Flow of events subject marks.
Step4. System displays and prints the result.
Step5. Use case ends.

Alternative flow of events Record office can’t distribute Transcript

Step1. The student is incomplete at least in one subject
Step3. The system cannot generate the Transcript.
Step4. Use case ends

Post condition Distribute Transcript generated

Table2: use case description of Generate Transcript system.

Use case name Register.

Description To register someone as a student of the school.

12
Precondition Student has to be Student has to be eligible (has to be from the pre-
specified junior schools that the school will accept)

Actor student

Step1. Student wants to be register as a student of

the school
Step2. Admin verifies that the student is eligible.
Step3. Registration form will be given to the
student.
Step4. The student completes the registration form
that contains student’s full name, address, sex, age,
Flow of events phone no and nationality.
Step5. Admin of the school checks whether the
contents of the registration form is properly
completed.
Step6.Admin submits the register form to the
record office with student’s name.
Step7.System registers.
Step8. Use case ends

Post condition Registered.

Table3: Use case description of Registration system.

Use case name Generate timetable

Description To generate timetable for the classes

Precondition There should be subject teachers and classes for

which the timetable is to be produced.

Actor Admin

13
 Step1.Admin wants to generate timetable.
Step2. Admin login and search, delete, update
and add any systems.
Flow of event Step3.admin registers student.
Step4.admin assign classes for each teachers by
filling a forms and the submit it.
Step5.Admin generates timetable
Step6.systems displays the result.
Step7.use case ends.

Alternative flow of events Alternative flow:

No teacher is registered to be assigned to classes.
Step5. The system cannot generate timetable.
Step6. Use case ends.

Post condition Generated timetable.

Table4: use case description of Generate Timetable system.

2.4.1.2. Actor Description

For our new systems actors that we identified are: -

 Record Officer.
 Home room Teacher.
 Student.
 Administrator.
14
Actor: Home Room Teacher
Description: The homeroom teacher is able to view information about attendance. On the other
hand, in case he/she is given permission, he is able to update attendance.
Actor: Admin.
Description: The administrator is able to manage different resources. It means that
Administrator can add modify/update, search, delete and distribute timetable information related
to those resources.
Actor: Student
Description: student should be register to request the admin of school and must fulfill the
criteria necessary need the school, in case of something the student drop the seminar and also
finish seminar.
Actor: Record Officer
Description: A Record Officer is a person who produce report card of student and produce
transcript of the student per semester.

2.4.1.3. Use case Diagram

According to the UML specification a use case diagram is a diagram that shows the relationships
among actors and use cases with a system

Use case diagram often used to:

 Provide an overview of all part of the usage requirements for a system.

 Communicate the scope of development project.
 Model the analysis of our usage requirements in the form of a system use
case model.

15
General Use case Diagram of Haramaya university model school
management system.

16
 2.4.2. Class diagram
Class diagrams are used to describe the structure of the system in terms of classes and
describe the system in terms of objects, classes, attributes, operations, and their association.
Identified classes and relationship among them is shown below

Account Registration Transcript

Stud name
Fname Name
Studid
Lname Id
Age
Username Age
Password 1 * Sex
Sex
Semester
Privilege Address
Mark
Phone no
Rank
Create account () Conduct
Delete account () Year
Get request ()
Check account ()
Get student ()
Determine average ()
1 1 * 1 1
1 1

* 1 * 1
Schedule Record
Name 1
Subject name Id
Teacher name Age
Section Sex
Room Class
Day 1 * Date
Time Year
User code

Assign teacher ()
Assign present ()
Assign room ()
Assign absent ()

17
 2.4.3. Sequence Diagram
Sequence diagrams show the interaction between participating objects in a given use case. They
are helpful to identify the missing objects that are not identified in the analysis object model. To
see the interaction between objects, the following described the sequence diagram of each
identified use cases.

Sequence Diagram to Create Account

Logically the create account form is functions like a below sequence or order.

1. Create account menu.

2. Generate account form.
3. Display account form.
4. Account form.
5. Click ok.
6. Validate account form.
7. Display error report
8. Save account information.
9. Error report.
10. Display acknowledgment.
11. Acknowledgment.
12. Close account form or go to the next form

18
Fig: Sequence diagram for creating account

19
 Actor Login control Login<<UI>> Student Main menu
<<student>>

wants to login
Create login UI

Enter user name & password

Is valid user name & password

Login is successful

Explore mainpage

20
 Transcript Select
Transcript Distribute
Button( Year, Grade &Semester
controller Transcript
Record <<UI>> Form<<UI>>
Officer
Press Button ()
Create ()

Create ()

Fill Data ()

Submit ()

Generate

Acknowledge ()

21
 Record Attendance
Control Attendance
Attendance
Record Form
Button<<UI>>
Home
Room
Teacher
Press Button
Create ()

Display ()

Fill Data() Validate(

)

Submit()

Submit Form ()

Acknowledge ()

22
Figure sequence diagram for generate Timetable

23
Figure Login Form

24
Figure Activity Diagram of Student Registration.

25
 Chapter 3 System Design Document
3.1. INTRODUCTION
 System Design is the transformation of the analysis model into a system design model.
During system design, we define the design goals of the project and decompose the
system into smaller subsystems that can be realized by individual’s teams.
 We also select strategies for building the system, such as the hard ware /soft ware
platform on which the system will run, the persistent data management strategy, the
global control flow, the access control policy, and the handling of boundary conditions.
The result of system design is a model that includes a clear description of each these
strategies, subsystem decomposition, and a UML deployment diagram representing the
hardware/software mapping of the system.
 System design is not algorithmic or things want define for professionals and academics,
however, developed pattern solutions to common problems and defined notations for
representing software architectures. There is also subsystem of the design which provides
services to other subsystem that related to the operations shared as common purpose for
the user of the system.

3.2. Purpose
When we design the system after the requirements analysis specification, there is a System
Design Document (SDD) for the design which described by the following points:

 A set of nonfunctional requirements and constraints reliability for the system.

 The use case model, describing the functionality of the system from the actors’ point of
view.
 The object model, describing the entities manipulated by the system.
 The sequence diagram for each use case, showing the sequence of interactions among
objects participating in the use case.
 The list of design goals, describing the qualities of the system that the developers should
optimize.
However, the system design models, describe the system completely from the actors’
point of view and serves as the basis of the communication between the client and the
developers. The software architecture of the system describes the subsystem
decomposition in terms of subsystem responsibilities, dependencies among subsystems,

26
 subsystem mapping to hardware, and major policy decisions such as control flow, access
control, and data storage, which can be described as follows:
 Hardware/software mapping: - are leads to the definition of additional subsystems
dedicated to moving data from one node to another which dealing with concurrency,
and reliability issues.
 Data management: - is the persistent data represents in the system on many different
fronts which concerned with creating or manipulating persistent data. For this reason,
access to the data should be fast and reliable which lead to the selection of the
database management system of an additional subsystem dedicated to the
management of persistent data.
 Access control: - is the system wide issues which must be consistent across the
system used to specify who can and cannot access certain data should be the same
across all subsystems.
 Control flow: - is the choice of the impact on the interface of the subsystems of the
system flow and if the event driven control flow is selected, subsystems will provide
event handlers.
 Boundary condition: - is the system initialization and shutdown often represent the
larger part of the complexity of the complexity of the system, especially in a
distributed environment.

3.3. Design goals

 In the way we want do our system, the first thing is to design the system completely.
After we designed the system properly, we want to implement our system by entering the
interface of the system to interact within the code of the program.

27
  Know the design helps the developer of the system or the programmer to implement the
system through coding the code properly by having the general idea of the design
virtually of the systems idea in mind to come back to check the way the system could like
if the programmer can have an error in the coding during the implementation of the code
line by line, we want to check the error by referring the design until the error completely
executable. Then the developer can ensure themselves on the way we design to perform
the system correctly.
 So the design has the general idea of the system on which the user could also interact
with to understand what the system like. But if we cannot design the system correctly, it
is difficult in order to interact within the system phase of code which creates the system
logically.
In generally our design provides performances, dependability, maintenance, and end of
user criteria concepts in order to interact within the system as described below:
 Performance
 Dependability
 Maintenance
 End User Criteria

Performance Criteria
The part of the system to be used for the record office should have a fast response time (real
time) with maximum throughput. Furthermore, the system should not be taking up too much
space in memory. The record officer has chosen fast response time over through put and hence
the system should try to be more interactive. In the case of the timetabling subsystem, the
system should be more reliable in order to satisfy the constraints than fast response time.
System is handling sensitive data of the school high emphasis should be given with regards to
security, as there are subsystems to be accessed through web.

Dependability
The school needs the system to be highly dependable as it is expected to be used by non-IT
professionals. The system should be robust and fault tolerant. Furthermore, as the system is
handling sensitive data of the school, high emphasis should be given with regards to security, as
there are subsystems to be accessed through web.

28
 Maintenance
The system should be easily extensible to add new functionalities at a later stage. It should also
be easily modifiable to make changes to the features and functionalities.

End User Criteria:

Usability: Usability is the extent to which a product can be used by specified users to achieve
specified goals with effectiveness, efficiency and satisfaction in a specified context of use. From
the end users’ perspective the system should be designed in such a way that it is easy to learn and
use, efficient and having few errors if any.

Trade-off is inevitable in trying to achieve a particular design goal. One best case is the issue of
security versus response time. Checking User-Id and Password before member can enter to the
school management system (SMS) creates response time problem/overhead. The other case is the
issue of response time versus quality. There is some amount of time taken by the system to
generate the timetable. So the user has to wait a little after telling the system to generate the
timetable and getting the result to get a quality timetable.

3.3.1. Architecture of the System

The proposed system is expected to replace the existing manual system by an automated System
in all facets. It is mainly based on the system Analysis document.

The architecture used for the system is a 3 tier Client/Server Architecture where a client can use
Internet browsers to access the online report provided by the system within the local area

29
network of the school or any where using the Internet. The data tier maintains the applications
data such as student data, teacher data, and timetable data etc. It stores these data in a relational
database management system (RDBMS).The middle tier (web/application server) implements
the business logic, controller logic and presentation logic to control the interaction between the
application’s clients and data. The controller logic processes client requests such as requests to
view student’s result, to record attendance or to retrieve data from the database. Business rules
enforced by the business logic dictate how clients can and cannot access application data and
how applications process data. A web server is a program that runs on a network server
(computer) to respond to HTTP requests.

The most commonly used web servers are Internet Information Server (IIS) and Apache. The
web server used in this system is IIS. HTTP is used to transfer data across an Intranet or the
Internet. It is the standard protocol for moving data across the internet.

The client tier is the applications user interface containing data entry forms and client side
applications. It displays data to the user. Users interact directly with the application through user
interface. The client tier interacts with the web/application server to make requests and to
retrieve data from the database. It then displays to the user the data retrieved from the server.

30
 3.4. System Design Model
 System Design Model is the way the objects of our systems will be collaborate with other
objects to fulfill their responsibilities, and because of the only an object can interact with

31
 another is if it knows about it , and then some sort of relationship must exist between the
subsystems of the system.
 It is the model for the system design which the designer of the system can be understands
the way he/she decided to act on the whole of the system to implies the activities to be
performed by modeling the system.

3.4.1. Subsystem Decomposition

Subsystem Decompositions will help to reduce the complexity of the system through partition of
the system by dividing into simple sub parts. The subsystems can be considered as the packages
holding the related classes/objects in which the system decomposed to the subsystems in order to
easily control the problem or the limitation of our system If we want to improve our system
within the specification of the requirement for the time cannot be sufficient such as time, budget,
knowledge, and other related requirement for the system. Then we can easily improve our system
to the extent wanted even if what we design before is incorrect.

32
Figure Layered Representation of the systems

33
Further decomposed of some subsystem shown as figure bellow

Figure Deployment diagram of the system

34
 3.4.2. Hardware/Software mapping
The hardware/software mapping is leads to the definition of additional subsystems dedicated to
moving data from one node to another which dealing with concurrency, and reliability issues.
One of the major tasks in the system design deals with the components would be part of
hardware, and software during the broad system that performs many functions of the systems we
want to develop.

The system requires a computer with description:

Hardware:

RAM: 256 MB or above

Hard disk: 80 GB or above

Tools:

Database: SQL server 2005

Application: .Net frame work 3

Operating system: Windows XP

Quality issues
The system is assumed to be reliable.

Compatibility: - Compatible with standard web application.

35
The system has two nodes such as the web server and client which can represent to a specific
instances (workstations) or a class of computers (web server), which is a virtual machine. The
application of the system will run on the web server connected to the database server by ado.net
as shown below diagrammatically:

Figure Deployment diagram of the system

36
 3.4.3. Persistent data management

 The Persistent data management deals with how the persistent data (file, database,
etc) are stored and managed its out lives a single execution of the system.
 Information related to student basic information and other related information are
persistent data and hence stored on a database management system, this allows all
the programs that operate on the SMS data to do consistently.
 Moreover, storing data in a database enables the system to perform complex queries
on a large data set and the schools register students every year in thousands per grade
level. For complex queries over attributes and large data set Microsoft SQL server is
implemented, which is a rational Database Management System.
 The persistent data represents in the system on many different fronts which
concerned with creating or manipulating persistent data. For this reason, access to
the data should be fast and reliable which lead to the selection of the database
management system of an additional subsystem dedicated to the management of
persistent data.

3.4.4. Access control

The access control describes the user model of the system in terms of an access
matrix for the security of the system through the selections of an authentication
mechanism, the use of encryption, and the management of keys.
When we are also control the system globally within the software, in order to
describe how requests are initiated and how subsystems synchronize to list and
address synchronization to concurrency issues for the system to be access for the
retrieval from the surrounding environment to back up.
Yet the access control describes the user model of the system in terms of access
matrix and provided free access for any interested applicant, it doesn’t require
authentication mechanism for registration of the user wants to register, it needs
authenticating using password.

37
 3.5. Detail design
 The detail design of our design is to specify the information on the part of the
systems designed clearly in all aspect within the necessary activities to perform
instead it is detail to designed, and the system design can extent smoothly easier
as the designer want to act on the way we assigned to do within the design of the
system.
 Also it developed as completed within the expected things to do during system
design in order to bring it to the implementation phase of our system to be
obviously to develop the system. So the detail design can it self help the way want
to performed within less effort of the programmer of the system well without
having some difficulties within the system.
 In generally the detail design is the heart of system in which the idea of our
system could like to be generated from the detail design for the programmer of the
system during implementation, and there is no more expect problem within the
system we already able to develop for their or for other users.

3.5.1. Object design model

HUMSMS is a system to be developed to change the manual system into computerized. It will
have user friendly interfaces to interact with the users easily. User will type their user name and
password on the login form and the system will check the validity of the user in the database. If a
match is found the user will be allowed to access the system with the privilege level assigned to
him/her. If a match is not found in the database the system will display a message telling the user
to re-enter the user name and password or else service will be denied. System design reduces the
gap between the problem and the machine by defining a hardware and software platform that
provides a higher level of abstraction than the computer hardware.

38
Figure of Object design model

39
3.5.2. Database design
The design of the DB is portrayed as a special model, database schema. It is the physical model
or blueprint for a DB, which represents the technical implimentations of the logical data model.
A relational DB schema defines the DB structure interms of tables, keys,indexs and integrity
rules. A DB schema specifiece details based on the capablities, terminologies, and constraints the
chosen DBMS as follows:

3.5.3. User interface form

Interface is a device or program enabling a user to communicate with a computer, or for

connecting two items of hardware or software. User interface design shows interfaces of this
system how it interacts to its users. In the following section we are going to show the UI
design we are going to use to our Web application system. In addition to hardware and
software interfaces, an interface may refer to the means of communication between the
computer and the user by means of peripheral devices such as a monitor or a keyboard and
point of communication involving a computer.
The following sample user interface of the proposed system is may be changed.

40
Figure Screen of login form

41
Figure Screen Of Student Registration form

42