67% found this document useful (3 votes)
3K views

Architecture of Hostel Management Sysytem

This document provides an overview of the graphical user interface (GUI) and architecture design of a hostel management system (HMS). It describes the registration process, room allocation, mess flow, and how user data is stored in the database. It also explains how users can log in to access computer facilities and shows the architecture diagram with the main components of the system interconnected, including registration, room allocation, mess allocation, and administrative database access.

Uploaded by

Bilal Baber
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
67% found this document useful (3 votes)
3K views

Architecture of Hostel Management Sysytem

This document provides an overview of the graphical user interface (GUI) and architecture design of a hostel management system (HMS). It describes the registration process, room allocation, mess flow, and how user data is stored in the database. It also explains how users can log in to access computer facilities and shows the architecture diagram with the main components of the system interconnected, including registration, room allocation, mess allocation, and administrative database access.

Uploaded by

Bilal Baber
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 12

Topic: Architecture Design of Hostel Management System Submitted to: Sir Touseef Tahir

Department of Computer Science, COMSATS Uni ersity Of Sciences and Tecnology, !ahore
Submitted by: "ain #in Tan eer #cs$Sp%&$%&'A Abuba(ar )ounas #cs$Sp%&$&*+A

-1-

Table of Contents
,age Introduction Home Page. Registration Room Allocation Mess Flow. !ata"ase #$or Admin%. 1& How user 'og in Arc(itecture o$ t(e )*stem 1+ )ummar*.. 4 5 6 8

11 1,

-+-

.ntroduction
-(is is t(e .ra/(ical 0ser Inter$ace #.0I% and Arc(itecture !esign $or t(e Hostel Management )*stem #HM)%. First in t(e .0I1 it s(ows t(e Registration1 Room allocation1 Mess $low and !ata"ase $low o$ t(e s*stem and (ow t(e user logged in w(en t(e* want to use t(e P2s o$ t(e (ostel. -(en in t(e last t(e Arc(itecture s(ows (ow t(e w(ole s*stem is interconnected to one anot(er.

-,-

Home ,age

#For Administrator onl*%

-4-

/egistration flo0
First name

'ast name

2ontact num"er

3mail I!

Permanent address

-5-

!e/artment name

2lass roll num"er

Registration num"er

!egree name

!egree duration

A$ter t(is t(e an I! is issued to t(e student "* t(e warden

-6-

/oom Allocation flo0


I! 4 #gi5en to *ou at registration time%

6ame

!e/artment name

2ontact

6ote7

A room is onl* $or t(e two students. -(e dues o$ t(e (ostel is onl* $or 1 semester. -(e student will /a* t(e dues wit(in 1& da*s. In case o$ t(e una5aila"ilit* o$ a room t(e students will "e entered in a waiting list.

. A$ter t(is a room 4 is gi5en to t(e student.

-8-

Mess flo0
6ame I! 4

Room 4

1ote:
A student can ta9e onl* + messes at a time. At t(e end o$ t(e mont( t(e (ard co/* o$ mess details issued to t(e student:s room1 -(e student s(ould /a* t(e dues wit(in 1& da*s

-8-

Data #ase
2All the information from abo e arri es here3 1ame .D Address Contact /oom Department Dept4roll . . . . . . . . .

Ho0 user logs in55544


;(en t(e user want to use t(e P2 $or t(e use o$ t(e internet or some wor9 on P2 -(en (e<s(e can loged into t(e s*stem "* onl* gi5ing t(e I!4 and t(e /assword.

!O6 .1
I!4

Password

Remem"er me

- 1& -

Architecture of the system


-(e arc(itecture o$ t(e s*stem is "ased on some centrali=ed /ro/erties and some client ser5er.
Room Allo Mess allo

Registration

!ata"ase $low #$or admin%

Fig.1 Arc(itecture design $or t(e Hostel Management )*stem

- 11 -

Summary
-(e w(ole re/ort is a"out t(e .0I > Arc(itecture o$ t(e HM)4 First we discussed t(e registration o$ t(e students w(ic( gat(ers t(e w(ole in$ormation o$ a student1 t(en t(e room is allocated to t(e students1 and mess $low o$ t(e student is (andled1 "ot( contains onl* /ersonal in$ormation1 $or more in$ormation t(e* can contact to t(e main data"ase o$ t(e s*stem. 6e?t we discussed a"out t(e admin (ow can (e<s(e can add > delete in$ormation $rom t(e data"ase o$ t(e s*stem. 'ast we (a5e seen t(e arc(itecture o$ t(e s*stem.

- 1+ -

You might also like