This document describes a proposed hostel management system for Lucknow University. The existing manual system is time-consuming and prone to errors. The proposed computerized system would provide easy access to student data and records. It would use Java for the interface and Oracle for the database. The system would allow for features like fee payment, room allocation, and attendance tracking. Testing plans include unit, integration, and user acceptance testing to ensure quality. The full implementation would include training, documentation, and security measures.

1. THE PROJECT ON HOSTEL MANAGEMENT SYSTEM SUBMITTED TO- MR.RAJIV PANDEY SIR DEPARTMENT OF BUSINESS ADMINISTRATION UNIVERSITY OF LUCKNOW SUBMITTED BY- ALOK SINGH , ANAND VARDHAN ANAMIKA TIWARI , AKANSHA MBA(EB) 4TH SEM 2009-11 BATCH

2. INTRODUCTION (Problem definition) We have got nine hostels in LUCKNOW UNIVERSITY, which consist of four boy’s hostel and five girl’s hostel. All these hostels at present are managed manually by the hostel office. The Registration form verification to the different data processing are done manually. Thus there are a lot of repetitions which can be easily avoided

3. SYSTEM ANALYSIS EXISTING SYSTEM The existing system is a manually maintained system. All the Hostel records are to be maintained for the details of each student, Fee details, Room Allocation , Attendance etc. All these details are entered and retrieved manually Time Consuming updating process inaccuracy of data

4. PROPOSED SYSTEM The Proposed system is the computerized version of the existing system. provides easy and quick access over the data Authorization schemes Java has been chosen for this project

5. Requirement Hardware Requirements Processor : Pentium RAM : 512MB Hard Disk : 4GB CD Drive : LG Monitor : LG Monitor Keyboard : Logitech Software Requirements Language : JAVA Operating System : Windows XP Professional Software : JAVA (Swings) Tool : Command Prompt Database : Oracle 8.010

6. We use java becouse it is- Compiled and Interpreted Platform-Independent and Portable Object-oriented Robust and Secure Familiar, Simple and Small Multithreaded and Interactive High Performance Dynamic and Extensible

7. METHODOLOGY

8. Waterfall model

9. SDLC

10. DFD of Mess in Hostel

20. TESTING AND MAINTENANCE The ultimate aim is quality assurance. System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently before live operation commences. Testing is the process of executing the program with the intent of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied

21. Unit Testing- Unit testing focuses first on modules, independently of one another, to locate errors Integration Testing- Data can be lost across any interface, one module can have an adverse effect on another, sub functions when combined, may not produce the desired major functions. Integration testing is a systematic testing to discover errors associated within the interface

22. User Acceptance Testing -User acceptance of a system is the key factor for the success of any system. The system underconsideration is tested for user acceptance by constantly keeping in touch with the system users at time ofdeveloping and making changes whenever required

23. METHOD ASSSOCIATED WITH TESTING Module Testing-Module testing is a process of testing the system module by module, what are all the input given and what are all the output produced and whether they are required by testing in this method. We would be very clear of the bugs occurred. The project matrimonial is tested module wise

24. SYSTEM IMPLEMENTATION Implementation is one of the most important tasks in project development. The implementation phase is less creative than system design. Depending on the nature of the system, extensive user training may be required. Preparation of user and system documentation . Conducting user training with demo and hands on · Test run for some period to ensure smooth switching over the system

25. Security and Maintenance minor enhancements or corrections to problems fixing the problems reported Any system developed should be secured and protected against possible hazards to prevent unauthorized access of the database at various levels Password protection

26. THANKS