Hostel Mess Administration Report

Chapter 1
1. Introduction
1.1 Existing System
Existing system maintain the student record manually. The enrollment of student,
assigning the room, maintaining items and room allocation, inventory of hostel is
maintained manually.
The record of staff and visitor who visit the student are maintained manually.
Attendance of student is marked manually. Current system keeps the maintenance record
of room manually and does keep the information about previous maintenance.
Student leave record is kept manually and document submitted are kept in files.
The fees collected from student are also done manually.
Current system generates very few reports which is generated by keeping all this
information in various books.
1.2 Need of System
Current system fails in providing correct information to management due to

which management can not take decision which affect on the providing poor facilities to
student. The current system does not hold the information about staff and visitor who
visit student.
The hostel management system needs to make system automated so that
information needed for day to day decision available easily.
To maintain the record of fees and student leave need to kept updated so that any
student need information about fees and information are available easily.
1
1.3 Proposed System
With the shortcomings in the existing system at every area of work a new system
has to be worked upon which may overcome all the inefficiencies that the present system
has.
In today’s high-tech world all the above mentioned characteristics of the system is
outdated and a need for a new, powerful, stable and result oriented software is required
which is why a new system based on .Net technology & SQL server as a database is
designed. .Net framework is used to provide front-end interfaces for user-friendly
ambience and SQL Server is used to maintain & update database for fast and reliable
retrieval of data and processing of queries.
1.4 Advantages of the Proposed System
 User friendly and simple in nature

 Compatible on all windows based systems
 Upgradeable with slight modification in coding
 Easy application maintenance due to its robustness
 Menu driven navigation to facilitate simple and quick access to required
functionality.
 A central database for all the data related to ensure data consistency
 Easier and faster data entry with menu support
 Can quickly produce required reports related to Daily, Weakly, monthly,
Yearly etc
1.5 Objectives of System
To assist and ease the works for the school, proposed system helps in maintaining
record of hostel student and the transaction happen at hostel side.
2
The proposed system helps hostel management to keep track of inventory
maintained at hostel side. Various reports regarding the hostel are generated through
system.
1.6 User Requirements
 User need to enter data of student in system.

 User must entered the items information in hostel and also provide data of
staff and maintenance of hostel.
 The student leave information must enter in the system.
 Data regarding the student fees is entered by user.
 While transferring the item from room to room user must enter in the system.
1.7 Detail Description of Technology Used
1.7.1 Java Programming Language
JAVA is a multi-paradigm programming language encompassing imperative,

functional, object-oriented ,class-based disciplines. It was developed by Microsoft within
the .NET initiative .JAVA is one of the programming languages designed for the Common
Language Infrastructure.
JAVA is intended to be a simple, modern, general-purpose, object-oriented programming

language. The most recent version is JAVA 3.0, which was released in conjunction with the .NET
Framework 3.5 in 2007. The next proposed version, 4.0, is in development.
SQL SERVER 2008
The current version of SQL Server, SQL Server 2008 was released on August 6,
2008 and aims to make data management self-tuning, self organizing, and self maintaining with
the development of SQL Server Always On technologies, to provide near-zero downtime. SQL
Server 2008 also includes support for structured and semi-structured data, including digital media
formats for pictures, audio, video and other multimedia data. In current versions, such multimedia
3
data can be stored as BLOBs (binary large objects), Intrinsic awareness of multimedia data will
allow specialized functions to be performed on them.
SQL SERVER store data in backend for different varieties of data: XML, email,
time/calendar, file, document, spatial, etc as well as perform search, query, analysis, sharing, and
synchronization across all data types.
Chapter 2
4
Feasibility Study
2.1 Types of Feasibility
2.1.1 Technical Feasibility
Is a project technically feasible? Is it within the state of the art? Can defects be
reduced to a level matching the application’s needs?
According to us our project is technical feasibility that it doesn’t require high cost
software and hardware measures. It can be run on any platform that means it is platform
independent.
2.1.2 Operational Feasibility
A system is suitable or it satisfies the need of system to become operationally

feasible is called as operational feasibility such as:
Whether the system is easy to operate by any person.
Whether the system is fulfilling the billing system of office.
2.1.3 Technical Feasibility
Technical feasibility is nothing but determination of system that whether it is

technically feasible or not. Whether the existing software can fulfill the technical
requirement of user. Whether the system can guarantee the reliability, accuracy, security
of the system.
2.1 .4 Economical Feasibility
It is very essential to have a system economically feasible; i.e. the system should be
financially well-known and liking to the customer. Following are the points related to
this: -Cost required by the hardware and the software used for this system.
To maintain this system some investigation is required.
Profit gained by considering both expenses on existing system and the expenses
on the developed system.
Chapter 3
5
System Requirement
Hardware:
Processor : Pentium IV and Above

RAM : 512 MB (Minimum) or Above (Recommended)
HDD : 80GB or Above
Software:
OS : Windows XP or Above
Front End : Java JDK1.6
Back End : MS ACCESS 2007
Chapter 4
Design
6
4.1 DFD Diagram
4.1.1 DFD Level 0 Diagram
Fig 4.1: DFD Diagram Level 0 for Hostel Mess Administration
4.1.2 DFD Level 1 Diagram
7
Fig 4.2: DFD Diagram Level 1 for Hostel Mess Administration
8
4.2ClassDiagram
StudClass
Course
+classname: string
Person +classcode: string +courseCode: string
+courseName: string
+no: string +addNewClass()
+name: string +deleteClass() +addNewCourse()
+add: string +editClass() +deleteCourse()
+state: string +editCourse()
+city: string
+pin: int 1
+phno: string 1 FeesReceipt
+gender: string
+receiptNo: string
+addNewPerson() +date: date
+deletePerson() +feesdescription: string
+editPerson()
+searchPerson() +addNewRecord()
1..* +editRecord()
+deleteRecord()
1..*
1..* 1
Student
Staff +dob: date Leave
Visitor
+addmissiondate: date
+designation: string +refNo: string
+relation: string 1 +email: string
1..* 1 +fromdate: date
+todate: date
0..* +documetsubmit
1..* +description
1..*
+addNew()
+deleteLeave()
+editLeave()
1
Item
0..*
Room +icode: string
Maintainance +iname: string
+roomno: string +iprice: float
+refid: string +roomtype: string
+date: date +roomcapycity: int 1..* +addNew()
+type: string +roomstatus: string 1..* +editItem()
+cost: int 1 +deleteItem()
1..* +addNewRoom()
+description: string
+deleteRoom()
+addNew() +editRoom()
+deleteMaintainanace()
+editMaintainanace()
Fig 4.3: Class Diagram for Hostel Mess Administration
9
4.3 Sequence Diagram:-
10
Room Item Staff Student Leave Visitor
: Rector
1 : Entered room()
2 : Entered Item()
3 : Entered staff()
4 : Allocate Item()
5 : Enroll student()
6 : Allocate Room()
8 : Takes()
7 : Maintain()
9 : Leave details()
10 : Visit()
11 : Visitor Details()
Fig 4.4: Sequence Diagram for Hostel Mess Administration
4.4 Use Case Diagram:
11
12
Fig 4.5: Use Case Diagram for Hostel Mess Administration
Chapter 5
Coding
/*
* To change this license header, choose License Headers in Project Properties.
* To change this template file, choose Tools | Templates
* and open the template in the editor.
*/
package hostelsystem;
import java.io.IOException;
import javax.swing.JOptionPane;
import net.sf.jasperreports.view.*;
import net.sf.jasperreports.engine.*;
import java.sql.*;
/**
*
* @author imp
*/
public class MasterForm extends javax.swing.JFrame {
Connection con ;
/**
* Creates new form MasterForm
*/
public MasterForm() {
initComponents();
}
13
/**
* This method is called from within the constructor to initialize the form.
* WARNING: Do NOT modify this code. The content of this method is always
* regenerated by the Form Editor.
*/
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">//GEN-
BEGIN:initComponents
private void initComponents() {
jMenuBar1 = new javax.swing.JMenuBar()-;
jMenu1 = new javax.swing.JMenu();
jMenuItem1 = new javax.swing.JMenuItem();
14
setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
getContentPane().setLayout(new org.netbeans.lib.awtextra.AbsoluteLayout());
jMenu1.setText("Master");
jMenu5.setText("Student Master");
jMenuItem1.setText("Student Master");
jMenuItem1.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jMenuItem1ActionPerformed(evt);
}
});
jMenu5.add(jMenuItem1);
jMenuItem2.setText("Fee Receipt");
}
});
jMenuItem5.setText("Leave Details");
}
});
jMenuItem4.setText("Class Master");
15
}
});
jMenuItem3.setText("Course Master");
}
});
jMenu1.add(jMenu5);
jMenu6.setText("Staff Master");
jMenu6.addActionListener(new java.awt.event.ActionListener() {
jMenu6ActionPerformed(evt);
}
});
jMenu1.add(jMenu6);
jMenu7.setText("Inventory");
jMenuItem7.setText("Item Master");
}
});
jMenuItem6.setText("Room Master");
16
jMenu1.add(jMenu7);
jMenuBar1.add(jMenu1);
jMenu2.setText("Maintaince");
jMenuItem10.setText("Student Room Allocation");
}
});
jMenuItem9.setText("Item Room Allocation");
jMenuItem8.setText("Maintance");
jMenuItem18.setText("Mess Allocation");
}
});
jMenu3.setText("Report");
jMenuItem11.setText("Student Report");
}
});
jMenuItem12.setText("Room Report");
17
}
});
jMenuItem13.setText("Fees Report");
}
});
jMenuItem14.setText("Mess Report");
jMenuItem15.setText("Room Allocation Report");
}
});
jMenuItem16.setText("Staff Report");
}
});
jMenuItem17.setText("Receipt Report");
18
}
});
jMenu4.setText("Help");
setJMenuBar(jMenuBar1);
pack();
}// </editor-fold>//GEN-END:initComponents
private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) {//GEN-
FIRST:event_jMenuItem1ActionPerformed
StudentDetails ss=new StudentDetails();
ss.setVisible(true);
// TODO add your handling code here:
}//GEN-LAST:event_jMenuItem1ActionPerformed
LeaveForm ll=new LeaveForm();
ll.setVisible(true);
FeeReceipt ff=new FeeReceipt();
ff.setVisible(true);
19
ClassMaster cm=new ClassMaster();
cm.setVisible(true);
CourseMaster cm=new CourseMaster();
cm.setVisible(true);
private void jMenu6ActionPerformed(java.awt.event.ActionEvent evt) {//GEN-
FIRST:event_jMenu6ActionPerformed
StaffFrame sf=new StaffFrame();
sf.setVisible(true);
}//GEN-LAST:event_jMenu6ActionPerformed
ItemMaster im=new ItemMaster();
im.setVisible(true);

RoomAllocation ra=new RoomAllocation();
ra.setVisible(true);
20
MessFrame mf=new MessFrame();
mf.setVisible(true);

new StudentReportHtml();
//ReportView rv=new ReportView("C:\\Users\\CSM\\Desktop\\StudentReport.jasper");
new RoomReport(); // TODO add your handling code here:
new FeeReportHtml(); // TODO add your handling code here:
new StaffReportHtml();
new FeeReportHtml();
21
new RoomReportHtml();
/**
* @param args the command line arguments
*/
public static void main(String args[])throws IOException {
/* Set the Nimbus look and feel */
//<editor-fold defaultstate="collapsed" desc=" Look and feel setting code (optional)
">
/* If Nimbus (introduced in Java SE 6) is not available, stay with the default look
and feel.
* For details see
http://download.oracle.com/javase/tutorial/uiswing/lookandfeel/plaf.html
*/
try {
for (javax.swing.UIManager.LookAndFeelInfo info :
javax.swing.UIManager.getInstalledLookAndFeels()) {
if ("Nimbus".equals(info.getName())) {
javax.swing.UIManager.setLookAndFeel(info.getClassName());
break;
}
}
} catch (ClassNotFoundException ex)
{ java.util.logging.Logger.getLogger(MasterForm.class.getName()).log(java.util.log
ging.Level.SEVERE, null, ex);
} catch (InstantiationException ex)
{ java.util.logging.Logger.getLogger(MasterForm.class.getName()).log(java.util.loggin
g.Level.SEVERE, null, ex);
} catch (IllegalAccessException ex) {
22
java.util.logging.Logger.getLogger(MasterForm.class.getName()).log(java.util.logging.L
evel.SEVERE, null, ex);
} catch (javax.swing.UnsupportedLookAndFeelException ex) {
java.util.logging.Logger.getLogger(MasterForm.class.getName()).log(java.util.logging.L
evel.SEVERE, null, ex);
}
//</editor-fold>
/* Create and display the form */

java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new MasterForm().setVisible(true);
}
});
}
// Variables declaration - do not modify//GEN-BEGIN:variables

private javax.swing.JMenu jMenu1;
private javax.swing.JMenuBar jMenuBar1;
private javax.swing.JMenuItem jMenuItem1;
23
// End of variables declaration//GEN-END:variables
}
24
Chapter 6
Testing
6.1 Black Box Testing:-
Black box testing assumes the code to be a black box that responds to input
stimuli. The testing focuses on the output to various types of stimuli in the targeted
deployment environments. It focuses on validation tests, boundary conditions, destructive
testing, reproducibility tests, performance tests, globalization, and security-related
testing.
Risk analysis should be done to estimate the amount and the level of testing that
needs to be done. Risk analysis gives the necessary criteria about when to stop the testing
process. Risk analysis prioritizes the test cases. It takes into account the impact of the
errors and the probability of occurrence of the errors. By concentrating on the test cases
that can lead to high impact and high probability errors, the testing effort can be reduced
and the application block can be ensured to be good enough to be used by various
applications.
Preferably, black box testing should be conducted in a test environment close to

the target environment. There can be one or more deployment scenarios for the
application block that is being tested. The requirements and the behavior of the
application block can vary with the deployment scenario; therefore, testing the
application block in a simulated environment that closely resembles the deployment
environment ensures that it is tested to satisfy all requirements of the targeted real-life
25
conditions. There will be no surprises in the production environment. The test cases being
executed ensure robustness of the application block for the targeted deployment
scenarios.
Input:-
The following input is required for black box testing:
 Requirements
 Functional specifications
 High-level design documents
 Application block source code
6.2 White Box Testing:-
White box testing assumes that the tester can take a look at the code for the
application block and create test cases that look for any potential failure scenarios.
During white box testing, you analyze the code of the application block and prepare test
cases for testing the functionality to ensure that the class is behaving in accordance with
the specifications and testing for robustness.
Input:-
The following input is required for white box testing:
 Requirements
 Functional specifications
 High-level design documents
 Detailed design documents
 Application block source code
26
Chapter 7
Cost Estimation
7.1 Effort Estimate Table:
Table 7.1: Effort Estimation
Task Effort Deliverables Milestones

weeks
Analysis of existing systems & compare 4 weeks
with proposed one
Literature survey 1 weeks
Designing & planning 2 weeks
o System flow 1 weeks
o Designing modules & it’s 2 week Modules
deliverables design document
Implementation 7 weeks Primary system
Testing 4 weeks Test Reports Formal
Documentation 2 weeks Complete Formal
project report
27
7.2 Phase Description:
Project Plan
Table 7.2: Project plan
Aug/15
Jun/15
Oct/15
Dec/15
Feb/16
Date
Phase
Nov/15
Jan/16
Jul/15
Mar/16
Sep/15
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
7.3 Estimation of KLOC
The number of lines required for implementation of various modules can be

estimated as follows:
Table 7.3: Estimation Of KLOC
Sr. No. Modules KLOC

1. Graphical User Interface 0.50
2. User authentication Code 0.20
3. Database Code 0.60
28
4. Web Design Code 0.50
5. Device Drivers 0.40
6. Interfacing Code 0.20
Thus the total number of lines required is approximately 2.40 KLOC
Efforts
E=3.2* (KLOC) ^1.02
E=3.2* (2.40) ^1.02
E=7.82 person-month
Development Time (In Months)

D=E / N
D=7.82 /4
D=3.91months.
Number of Persons
4 persons are required to complete the project with given time span successful
29
Chapter 8
Result
30
Fig 8.1: Student Master
Fig 8.2: Staff Master
31
Fig 8.3: Visitor Master
32
Fig 8.4: Class Master
Fig 8.5: Course Master
33
Fig 8.6: Room Master
34
Fig 8.7: Fee Receipt
35
Fig 8.8: Maintenance Receipt
36
Conclusion
The school management ERP is fully integrated software which helps schools to
upgrade their existing system. The various reports generated helps management in
decision making.
Hostel is one of important part of school in which student from outside city
live for their education purpose. So it is necessary to track all information of them.
Current system help managing these resources. Any school has its small or big inventory,
it is necessary to track all resources of school, inventory management system helps for
that.
If any school has transport facility for their student, this information also tracks
from the system.
37
Future Scope
The system should maintain the information of student, staff, visitor, inventory,
rooms, maintenance, fees of student and various reports for management purpose is
maintained in the database.
This system also keep records of maintaining the records of room wise student
allocated and items which are allocated according to room.
The various reports such as number of items available and number of student in
particular room are maintained in the system.
38
References
1) Rajesh Nikam,UmeshSurve,” A text book of Object Oriented Software
Engineering”, Vision publication, 2015-2016
2) Ravi Majithiya, “Programming in JAVA-II”, Techmax Publications, 2015-2016
3) NeelimaPadmawar, “Internet Programming-II”, Techmax Publications, 2015-
2016.
Links
1) www.w3schools.com
2) www.google.co.in
3) www.wikipedia.com
4) www.stackoverflow.com
39

Hostel Mess Administration Report

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Hostel Mess Administration Report

Загружено:

Авторское право:

Доступные форматы

Chapter 1

1.1 Existing System

1.2 Need of System

Current system fails in providing correct information to management due to

1.4 Advantages of the Proposed System

 User friendly and simple in nature

1.5 Objectives of System

1.6 User Requirements

 User need to enter data of student in system.

1.7 Detail Description of Technology Used

1.7.1 Java Programming Language

JAVA is a multi-paradigm programming language encompassing imperative,

JAVA is intended to be a simple, modern, general-purpose, object-oriented programming

SQL SERVER 2008

2.1.1 Technical Feasibility

2.1.2 Operational Feasibility

A system is suitable or it satisfies the need of system to become operationally

Whether the system is easy to operate by any person.

Whether the system is fulfilling the billing system of office.

2.1.3 Technical Feasibility

Technical feasibility is nothing but determination of system that whether it is

To maintain this system some investigation is required.

Processor : Pentium IV and Above

4.1.1 DFD Level 0 Diagram

Fig 4.1: DFD Diagram Level 0 for Hostel Mess Administration

4.1.2 DFD Level 1 Diagram

Fig 4.3: Class Diagram for Hostel Mess Administration

Fig 4.4: Sequence Diagram for Hostel Mess Administration

4.4 Use Case Diagram:

private void jMenuItem10ActionPerformed(java.awt.event.ActionEvent evt) {//GEN-

private void jMenuItem11ActionPerformed(java.awt.event.ActionEvent evt) {//GEN-

/* Create and display the form */

// Variables declaration - do not modify//GEN-BEGIN:variables

6.1 Black Box Testing:-

Preferably, black box testing should be conducted in a test environment close to

The following input is required for black box testing:

6.2 White Box Testing:-

The following input is required for white box testing:

Task Effort Deliverables Milestones

7.3 Estimation of KLOC

The number of lines required for implementation of various modules can be

Table 7.3: Estimation Of KLOC

Sr. No. Modules KLOC

Thus the total number of lines required is approximately 2.40 KLOC

Development Time (In Months)

Fig 8.2: Staff Master

Fig 8.5: Course Master

Вам также может понравиться