Professional Documents
Culture Documents
Home Away Managemen T System (HA MS) : MA'AM
Home Away Managemen T System (HA MS) : MA'AM
TTED
TO:
MA’AM.
Home Away Hareem Aslam
Managemen SUBMI
TTED
t BY:
AYESHA ZAFAR
System(HA DAR- (BITF19M043)
MS)
1. INTRODUCTION
1.1 Purpose:
This Home Away Management System (HAMS) is designed for the managing
Hostels, which assists them with saving the students' records about their rooms and
other things. It helps them from manual work from which is exceptionally hard to
track down the record of the student and the mess bills of the students, and the data
of about the individuals who had left the hostel years before.
1.2 Scope:
The software product “Home Away Management System” could be an
application with a purpose to be used for preserving the records in a prepared way
and to replace paper working on the system. This project aims at automating the
hostel management for the easy working of the hostel by automating nearly all
the calculations and accounting work.
Hostel Management System is designed for hostel-like (colleges and
Universities Students).
He tests the attested application form of students acquired from the net &
confirms it with the student database.
If the students are eligible then they allotted to the hostel room
Definition:
The Home Away Management System (HAMS) is an online Hostel
Administration System used to provide quick and efficient means for gathering the
student information like room, fees & finally check-in and check-out report of
student.
Abbreviations:
SRS SOFTWARE REQUIREMENT SPECIFICATIONS
HAMS HOME AWAY MANAGEMENT SYSTEM
OS OPERATING SYSTEM
DBMS DATABASE MANAGEMENT SYSTEM
API APPLICATION INTERFACE
Project Members:
AYESHA ZAFAR DAR
Name ROLL # Email Address
AYESHA ZAFAR DAR BITF19M043 Bitf19m043@pucit.edu.pk
Project Goal: Provision of maximum information and facilities with the wide range
of institutions and cities coverage’s.
Objectives:
Sr. Objective
#
01 Hassle-Free Management of Bookings
02 Payments are easier and faster
03 Clear pricing with no hidden fees
04 Avoid manual and boring work
05 Provide website that a user can search and reserve a room
Project Success Criteria: To facilitate students with availability of hostels in the
fastest way.
Assumptions, Risks and Obstacles: In the future, our project would be affected by
the feedback of customer’s satisfaction on the online reservation system.
Organization Address (if any): PUCIT Old Campus
1.9.2 ASSUMPTIONS:
As software is to be integrated, so our project could be divided into
components.
We need sufficient human resources to complete it.
To create a totally new project, prototyping would be necessary.
This system is designed in favor of the hostel management which enables
them to save the records of the students about their rooms and different
things.
It allows them from the manual work from which it's very difficult to find
the record of the students and the mess payments of the students, and the
information of about the ones who had left the hostel years before.
This system gives a concept about how a student and fee info, room
allocation, mess expenditure is maintained in a higher manner.
The hostel management system can even contain special capabilities like
what numbers of students are in a room, student’s identification and
free rooms or space available.
The administration has a unique identification for every member as well as
hostel student’s info.
HAMS
INTERACTION
SYSTEM
USER
Sign up Username
Institute ID mess password, Biometric attendance system
4
2
3
3
4
5
3
2
3
4
5
4
2
4
Σ Fi = 48
Analyzing the Information Domain & weight:
Measurement parameters Count Weightage factor
Simple avg
complex
Number of user inputs 12 X 10 12 15 180
Number of user Outputs 09 X 09 11 14 81
Number of user inquiries 07 X 05 07 12 49
Number of files 06 X 05 08 12 72
Number of ext. Interfaces 07 X 05 08 12 84
Count total = 466
Complexity Multiplier =
Function points = 526.58
FP = Count Total * [0.65 + 0.01 * Σ (Fi)]
FP = 466 * [0.65 + 0.01 * 48] = 526.58
1. Student view
Optimistic LOC = 5800
Most Likely LOC = 7600
Pessimistic LOC = 9200
(Opt .+4∗Most Likely + Pessi.)
Estimated LOC =
6
(5800+ 4∗7600+9200)
Estimated LOC = = 7567 LOC
6
E = effort (person-month)
E=ai ( kdLOC )b i∗EAF
=3.6∗( 480 )1.20∗0.9737=3.6∗(1650.02 )∗0.8645 ≈5136 PM
D = Deployment time (month)
D = c i (E)d =2.5∗(5136)0.32=2.5∗(15.40 ) ≈ 39 P
i
P = productivity (KLOC/PM)
KLOC 480
P= = ≈ 0.094
E 5136
2. THE OVERALL
DESCRIPTION
2.1 Product Perspective:
The Home Away Management System (HAMS) is a fully independent product.
Our product is not a part of any other system. We have user interfaces. User
interfaces will be:
Administrator Interfaces
Staff Interfaces
Administrator Interfaces:
List of interfaces are listed as bellow:
Account View:
In this view, the User will add remove, new staff in the system. In
administrator view, an administrator will verify the newly added
department. The administrator will be able to get access to all
information about hostel staff, hostel students & controlled them.
Staff Interfaces:
At the begin, there will be a login screen wherein the user has to enter
its login name & password to authenticate himself or herself.
After the log in a homepage can be displayed showing all of the info.
and operations provided through Home Away Management System
(HAMS).
A record could be generated for each student containing fee info,
fines dues & check-in or check-out info.
2.1.2 Interfaces:
Our System is web based software, we use web interface and
server sided database.
Administrator Interfaces
View Account
Login Screen
Homepage
Report
Edit Data
Student Interfaces
Request for Room
Pay Bill
Check Mess Bill Report
There must be a network connected for connecting all the systems of the hotels.
This should provide updating data in every computer after each and every
transaction from each computer.
Our web based Software will be light and system friendly but minimum 256MB of
RAM is necessary. User need 500MB storage to install software.
2.1.7 Operations:
The client will utilize this application to keep up the database of students and the
mess of the room. The utilization of HAMS has an easy-to-understand interface.
The software gives precision along with a wonderful interface. Make the current
manual system more intuitive, expedient, and easy to understand.
Administrator
Student
Database manager
Administrator:
The administrator is the person who monitors all clients and client transactions.
The administrator needs to keep up the information of each student profile in the
database. At the point when the solicitation/request given by the client
administrator to checks the accessibility of the client account at that point it is sent
to the student database. The administrator has the complete data related to each
student database. All the information is kept up at the Administrator level. The
administrator is reserving the privilege to confine/restrict any database.
The administrator can:
Allot different students in different hostels.
Vacate the Students for the hostels.
Control the status of the fee payment/installment.
Edit the details of the students and modify the student record
Student:
Every student who has room in the hostel has a database and a student record to
get to his information. These consents will appear after head
endorsement/approval. The understudy can check his information whether it's
actual or need a few changes. Additionally, he can check the month-to-month
reports of their fines, mess bills, and other stuff.
Database manager:
Database manager is the user/client who has the administrator's authorization to
refresh the whole database. In this undertaking, the Database set administrator has
the authorizations to refresh the student details, room details, student attendance
details, & update mess item expenditure.
2.1.10 Constraints:
The developed framework should run under any stage for example Unix, Linux,
Macintosh, Windows, and so on.
All compulsory fields ought to be filled by a person.
There can be security risks involved.
Details given by the person during his sign-up ought to be stored in a
database.
Student details can refresh or change by just the administrator or database
manager.
3. SPECIFIC
REQUIREMENTS
Registration:
Input:
o Name
o Id
o Password
o Roll number
o Fee data
o University name
o Email
o Room type
o Mess time
o Laundry time
Output:
o Submission view
Sign in:
Input:
o Username
o Password
Output:
o Student/manager home interface
3.2 Functions:
The data of student is added into the SQL server site database at the time of
registration, which includes:
o Name
o Id
o Password
o Roll number
o Fee data
o University name
o Email
o Room type
o Mess time
o Laundry time
Register account.
Sign in home page.
Edit daily formalities.
3.6.1 Reliability:
The project shall give storage of all databases on redundant PCs with oracle
database.
3.6.2 Availability:
The system should have chrome or any order website loader to load web, to run
software, system could be of 32 bit or 64 bit. The hosting of website is googling
related so availability of HAMS is 24/7.
3.6.3 Security:
This project gives real security to each one of those people who are having
their records on the database as they are password ensured.
This is a vital part of the plan and should cover areas of hardware
dependability, fallback methods, actual security of information, and arrangement
for identification of fraud and misuse.
3.6.4 Maintainability:
3.6.5 Portability:
The project is made in HTML and CSS as front end and SQL database as
back end and will work upon all OS productively.