Hostel Management Essay

ABSTRACT Hostel management by manual way is tedious process, since it involves work load and time consumption. In this system, we can easily manage the hostel details, room details, student records, mess expenditure, mess bill calculation, easy way of room allocation and hostel attendance. The main feature of this project is easy to allocate for the student and also easy to calculate mess bill. This project is carried out using Visual Basic as front end and oracle as back end. TABLE OF CONTENTS |CHAPTER NO |CONTENTS |PAGE NO | | |ABSTRACT | | | |LIST OF FIGURES | | |1. |INTRODUCTION | | | |1.1.TO THE PROBLEM | | | |1.2.TO THE SOFTWARE TOOL | | |2. |PROBLEM DEFINITION | | |3. |METHODLOGY | | |4. |SYSTEM ENVIRONMENTS | | | |4.1.HORDWARE REQUIREMENTS | | | |4.2.SOFTWARE REQUIREMENTS | | |5. |FUNCTIIONAL REQUIREMENTS | | |6. |REQUIREMENTS ANALYSIS | | | |6.1.USECASE DIAGRAM | | | |6.2.CLASS DIAGRAM | | |7. |DESIGNS | | | |7.1.SEQUENCE DIAGRAM | | | |7.2.COLLABRATION DIAGRAM | | | |7.3.STATE DIAGRAM | | | |7.4.ACTIVITY DIAGRAM | | LIST OF TABLES CHAPTER 1 INTRODUCTION 1. TO THE PROBLEM Hostel management gives on idea about how the students details, room allocation, mess expenditure are maintained in the particular concern. The hostel management system also includes some special features. The administration has the unique identity for each members as well as students details. The stock management has also held by mess expenditure, the mess expenditure that used to calculate the mess bills of each of the students. The modules of this project are student details, attendance details, room details, mess modules. Visual Basic6.0 is used as the front end tool and Oracle is used as a backend tool. Visual Basic is one of the driven programming languages. The application wizards, menu editor and data reports etc is very much useful for creating very good professional software. 1.2. TO THE SOFTWARE TOOL The â€Å"visual† part refers to the method used to create the graphical user interface (GUI). Rather than writing numerous lines of code to describe the appearance and location of interface elements, you simply drag and drop pre-built objects into place on screen. If you’ve ever used a drawing program such as paint, you already have most of the skills necessary to create an effective user interface. It revolves around ready-made objects and it is event-driven that is all the activities in a program are triggered by one event or another. Each object has its own properties, determining its position, size, color, appearance and nature of its text and much more. Each object also has its own event-handling procedures. Visual basic knows what a button is and how it works? It also works how to handle images, menus, dialog boxes, drive and directory list and much else. The programmer does not have to write code to trap these events the system does that automatically because th e program code runs in response to events. The flow of execution is not as fixed in a traditional program. Operations do not have to follow a set of sequence and can be easily interrupted, suspended or abandoned. The process of program design reflects the nature of the system. You begin by the screen layout events and then any necessary code to co-ordinate the whole program. Overall Diagram: USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. [pic] CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. [pic] Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. [pic] Collaboration Diagram: [pic] State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. [pic] Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states. [pic] METHODOLOGY It contains four modules in it. They are given below †¢ Student details †¢ Attendance details †¢ Room details †¢ Mess modules Students details: This module consists of the details of the student such as roll number, name, date of birth, address, phone number, year, degree, room no, department name nad etc. here the details are entered and are updated. USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. [pic] CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. [pic] Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. [pic] Collabration Diagram: [pic] State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. [pic] Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states. [pic] Attendance details: In this module,attendance details are maintained. Hence the upto date attendance of the each students are maintained. USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. [pic] CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. [pic] Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. [pic] Collabration Diagram: [pic] State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. [pic] Activity diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states. [pic] Room details: In this module, the room number for the hostel student is allocated and the details of the each students are maintained and updated regularly. USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. [pic] CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. [pic] Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. [pic] Collabration Diagram: [pic] State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. [pic] Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states. [pic] Mess Modules: In this module, the mess item expenditure for each student in the hostel is calculated for each month and the mess bill for each student in calculated and displayed. USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. [pic] CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. [pic] Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. [pic] Collabration Diagram: [pic] State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. [pic] Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states. [pic] SYSTEM ENVIRONMENT Hardware specification: Processor: Pentium IV Process speed: 1.6 GHz Memory: 512MB Hard drive: 80 Keyboard:107keys Mouse :Microsoft Software specification: Operating system:Microsoft windows 2000,windows XP Development:Microsoft visual studio Front End:Visual basic6.0 Back End:oracle PROBLEM DESCROPTION The project HOSTEL MANAGEMENT SYSTEM has been developed to reduce manual effort and making things faster and efficient. REQUIREMENT ANALYSIS 6.1.USE CASE DIAGRAM: Use case diagram is a diagram that shows the interaction between user and system to capture the user’s goals. CLASS DIAGRAM: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other. DESIGN 7.1. Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program. 7.2. State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object. 7.3. ACTIVITY DIAGRAMS: