DEBRE TABOR UNIVERSITY

FACULTY OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
PROPOSAL ON

Dormitory and Cafeteria

MANAGEMENT SYSTEM
FOR DEBRE TABOR University

BY:
Seid Nurhussen..0217/07
Rediet Tilahun..............0063/07
Moges Belachew.....................0211/07
ADVISOR:
Main Advisor Mr. Nibretu Kebede (MSc)

Date November/2010E.C
 1.1.Statement of the Problem
Today in the 21st century every activity is done by the help of computerized system or
automated system, even though anything which is done anywhere that is already known by
the genuine technology rather Debre Tabor University has no any automated system for
dormitory placement and student cafeteria menu it is totally manual system. Due to this the
institute has face some categorized problems.

Time:
The existing system is totally done by manual system to place the student dorm and
announcing the cafeteria menu, so the system takes more time, tedious and complicated to
run it for the students and workers.

Resource:
It needs high energy or human powers to do the activity around the student management
system in dormitory and cafeteria or to reduce the human power we must be automate the
system. In addition to this it requires much more resource like paper and pen.

Lose of Data:
When the paper is lost all the data recorded on that paper is destroyed or loss. Finally
the students do not get relevant data. Generally the student files are fully risky
because it has not any com

1.2.Objectives of the project

1.2.1 General Objective

Our proposed system mainly aims to change current manual system to automated system, to
make the system fast and easy to access.

1.2.2 Specific objective

To design the automate system regarding to student management system in WSU.
Develop the forms with functional buttons displayed on the webpage which is the
students are insert there profile and retrieve or access the wanted data.
To build the students record on the database.
 Develop the building, dorm and bed records.
Develop dynamic webpage to display the students cafeteria menu in our web based
system.

1.3 Scope of the Project

The scope of the project is the boundary of the project. So after we are developing the
system we have the hope handle the following difficulties.
The system will have large Storage Capacity of students profile, building and
dormitory profile on the database.
Personal information for the students such as:
Student name
Student ID No
Students sex (male or female)
Department of the student and also
Building profile as well, such as:

Block Number
Dorm Number
Quick search facility for the users (students) if the user (student) has been entered the
relevant information means that he/she type the correct name and department the system
computerized or moderate system to keep the data lost.

replay the students dorm placement and any one can access the databases easily by
using the graphical interfaces with simple computer knowledge and also everywhere
when it is connected to the internet.
Make Computerize all the activities of the system, so it makes Easy to update the
students profile and also provide all necessary services for databases such as updating
and searching information.
Delete and retype the student profile when the student has been leaved in the
organization or institution by any means.
In the cafeteria we will try to develop the dynamic webpage for displaying the
students cafeteria menu or preparing a menu on the web.
View the block and dorm placement then the students are distributed to the
dorm.
 View or access the cafeteria menu.

1.4. Requirements of the proposed system

Requirements of the new system can be categorized in to Functional and Non-Functional.

1.4.1. Functional requirement

Functional requirements capture the intended behaviour of a system and it defines what a
system is supposed to do.

Therefore the following functional requirements are stated for the new automated system.

It has login form in some authors except students, because students have their
own form to access the database on the system.
It displays the student block and dorm numbers.
The system administrator can create, remove and update account.
The users or students can access the database by inserting the information on the
provided form.
The officer can insert, delete and update the students and blocks information.
The students or users can access the cafeteria menu.

1.4.1. Non-functional requirement

Non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors. It is simply things that our system
may not include as functional requirement. Some of the non-functional requirement listed
below:

Performance
The system should work properly with its storage capacity, accuracy, speed and the likes.

User Interface
The developed software should be user friendly by making it easily accessible.

Compatibility
The system would be fully compatible with different type of browser like Microsoft Internet
Explorer, Mozilla Firefox, opera mini and Google chrome.

System modification
The system can be modified when every the authorized body needed to modification.
Response time
The automated system will have a great response time it access with a fraction of minute.

Portability
The system needs to be portable on all major platforms. This system should not be restricted
by any specific technology such as operating system.

Reliability
Reliability is the probability that the system will be able to process work correctly and
completely without being aborted.

Recoverability
Our system is the ability to restore function and data in the event of a failure.

Backup and recovery requirement:

The process of backing up refers to the copying and archiving of computer data by using
removable storage media such as Disk, CD-R and CD-RW so it may be used to restore the
original data after a data loss event is performed by our system.

Security
The security Section describes the need to control access to the data. This includes
controlling who may view and alter application data by using strong password on the system.

Maintainability
Our system has been easily maintained when some difficulty or problems will occur. This
covers a wide variety of activities, including removing program and design errors, updating
documentation and test data and updating user support in Adaptive Maintenance.