1.

SYNOPSIS

1.1 Title of the Project

Apartment Management

1.2 Objective of the Project

Main objective of this project is to help the users to manage the operations and
activities of apartments. It helps the owner to reduce the cost of maintaining the
records. This request for apartment owners, maintaining monthly expenses for every
apartment, billing details, issues etc.

1.3 Category

Web Application

1.4 Language to Be Used

Front end: HTML, CSS, Bootstrap

Back end: Python, Django

1.5 Structure of the Program

The project consists of admin, user and guest page that manages the Maintenance
request Payment history and user details. A customer has to login if user does not
have an account. Then the user will go for registration process. Apartment
management software should provide the Apartment manager with everything
they need relating to the property(s) in one centralized location. Apartment
management software should improve the management process for its users by
simplifying things.

1.5.1 Analysis

Apartment management is used to book a room, upgrade the room .It

contains admin, user and guest as the main module .The feature of this
software will make the user to register into Apartment.

1
1.5.2 Module Description

The program consists of following Module

1.5.2.1 Login

This Module allows to login three kinds user, guest and admin
the software authenticate the user by user id and password.

1.5.2.2 Forgot Password

When user clicks the forgot password the user needs to enter
registered email-id whenever the user provides exact
information it will allows the user to change the password.

1.5.2.3 Admin

1.5.2.3.1 Rooms

1.5.2.3.1.1 Add

It is used to add the rooms to the user.

1.5.2.3.1.2 Update

It is used to update the existing room

information.

1.5.2.3.1.3 Delete

It is used to delete the room.

1.5.2.3.2 Manage User

1.5.2.3.2.1 View

It is used to view the user information.

1.5.2.3.2.2 Delete

It is used to delete the user.

2
 1.5.2.3.2.3 Update

It is used to update the user information.

1.5.2.3.3 Payment History

1.2.2.3.3.1 View

It is used to view the payment history.

1.2.2.3.3.2 Delete

It is used to delete the payment history.

1.5.2.3.4 Emergency Service

1.5.2.3.4.1 View Request

It is used to view the emergency request

services.

1.5.2.3.4.2 Delete

It is used to delete the emergency request.

1.5.2.3.5 View Issues

It is used to view the issues reported by the user or

guest.

1.5.2.3.6 Notification

It is used to send notifications to the users.

1.5.2.3.7 Reservations

It is used to view the bookings of user.

3
1.5.2.4 User

1.5.2.4.1 Booking

It is used to book a room.

1.5.2.4.2 Emergency Services

Different emergency services available for the user such

as Ambulance, Fire, Security.

1.5.2.4.3 Check Facility

The user can check the facility of particular apartment
which has provided by the apartment manager.
Such as Gym, Meeting hall, Cafeteria, Garden, Play
ground.
1.5.2.4.4 Report Issues

The user can report the issues regarding the apartment.

1.5.2.4.5 Pay Bill

The user can pay various bill like water, Electricity and
pay the maintain fees.

1.5.2.4.6 My Profile

1.5.2.4.6.1 View

It is used to view the user profile.

1.5.2.4.6.2 Edit

It is used to update the user profile.

4
1.5.2.4.7 Notification

User gets notification from admin.

1.5.2.4.7.1 View

It is used to view the notification sent by admin.

1.5.2.4.7.2 Delete

It is used to delete the notification.

1.5.2.5 Guest User

1.5.2.5.1 Registration

It is used to create a new account if and only if a

guest user does not have an account.

1.5.2.5.2 Booking

It is used to book a room.

1.5.2.5.3 My Bookings

1.5.2.5.3.1 View

It is used to view the booking details.

1.5.2.5.3.2 Cancel

It is used to cancel the booking.

1.5.2.5.3 Emergency Services

Different emergency services available for the

user such as Ambulance, Fire, Security.

5
1.5.2.5.4 Check Facility

The user can check the facility of particular

apartment which has provided by the apartment
manager. Such as Garden, Cafeteria, Play
ground.

1.5.2.5.5 Report Issues

The user can report the issues regarding the

apartment.

1.5.2.5.6 Notification

User gets notification from admin.

1.5.2.5.6.1 View

It is used to view the notification sent by

admin.

1.5.2.5.6.2 Delete

It is used to delete the notification.

1.5.2.4.7 My Profile

1.5.2.4.7.1 View

It is used to view the user profile.

1.5.2.4.7.2 Edit

It is used to update the user profile.

6
1.5.2.6 Data Structure

Way of organizing and storing data.

Data structure of the database include the following

data.

1.5.2.6.1 Resident

 Username
 Password
 Email-id
 First name
 Last name
 Proof of identity
 Phone number

1.5.2.6.2 Guest

 Username
 Password
 Email-id
 First name
 Last name
 Proof of identity
 Phone number

1.5.2.6.3 Reservation

 Booking id
 Guest/Username
 Room no
 Check-in
 Check-out

7
1.5.2.6.4 Rooms

 Room type
 Capacity
 Price
 Size
 Location
 Status
 Room number

1.5.2.6.5 Bills

 User
 Type
 Amount

1.5.2.6.6 Emergency

 Room no
 Type
 Phone number

1.5.2.6.7 View-Issues

 User name
 Phone number
 Issues

1.5.2.6.8 Notification

 User name
 Notification type
 Message
 Created By

8
1.6 Other information
Not applicable.
1.7 Future scope
User can book a room and also he can see the booking information, can
receive notification from the admin.

9
 2. SOFTWARE REQUIREMENT SPECIFICATION

2.1 Introduction:

The goal of the requirement specification is to provide software requirement

document. The software requirement specification describe the completely an
external behaves of proposed software. Software requirement specification is
document that completely describes that what the proposed software should do
without describing how the software will do it. The specification may include
a set of use cases that describe iterations.

2.1.1 Purpose

The purpose of this document is to guide the developer of the software

about the requirement of the client. It also helps the developer about the
functionalities and their dependencies with each other of purposed
software. The software requirement specification acts as the medium
through which the client and the user needs are accurately specified. It
describes the interface requirement for the software system.

2.1.2 Scope

Software requirement specification document provides reference for

validation of the final software. In future by referring this software
requirement specification document developer can develop and
extends the software to provide the additional functionalities.

2.1.3 Definition, Acronyms and Abbreviation

SRS: Software Requirement Specification.

HTML: Hypertext Mark-up Language.

2.1.4 Reference
 Integrated approach to software Engineering
-Pankaj Jalote
 Synopsis

10
 2.1.5 Overview

The rest of Software requirement specification document describe the

various system requirement, interface, feature and functionalities in
detail.

2.2 Overall Description:

This describes the general factors that affect the product and its requirements.
Specification requirements are not mentioned, but a general overview is
presented to make the understanding of the specific requirements easier.

2.2.1 Product Perspective

Product perspective is essentially the relationship of the product to
other product. This product is an independent product it does not relate
with any other product.

2.2.2 Product Function

This project will work based on the modules, the modules are
managing the accounts, request status which are managed by the
admin. The client has to register first then he can login.

2.2.3 User Characteristic

It describes the user quality to operate this software. The user must have
qualities like type skills, to fill up the form, basic English language.

2.2.4 General Constraints

This product can run to any system.

2.2.5 Assumption and Dependencies

The basic assumption here is made about the user that the user should
have the computer knowledge. This product work independently.

11
2.3 Specific Requirements

Specific requirement session describe all the software developer needs to

known for designing and developing the application.

2.3.1 External Interface Requirement

External interface requirements specifies all the interfaces of the

software people, other software, hardware and other system.

2.3.1.1 User Interface

The interface is clearly a very important component. It is the

graphical interface specifies each interface of system, plan to
have textbox, buttons, screen, hyperlinks.

2.3.1.2 Hardware Interface

RAM: 2GB

HARD DISK: 500 GB

2.3.1.3 Software Interface

The product uses browser and it operates on windows

XP/7/8/10.

2.3.1.4 Communication Interface

Not applicable.

2.3.2 Function Requirements

This section gives functional capabilities of the system that requires

specifying the input and desired output and processing requirement

12
2.3.2.1 Login Module

2.3.2.1.1 Login

Input: User-Id, Password

Process: The login component is used to validate the

admin/user/guest login name and password to check if
person is an authorized or not.

Output: For the valid input the admin/user/guest can

successfully enter the main interface otherwise result is
unsuccessful.

2.3.2.1.2 Forgot Password

Input: Email-id

Process: It insert the input into table, user needs to

provide valid email-id whenever the user provides
exact information it will allow the user to change the
password.

Output: It will allow to change the password if the

valid input is provided otherwise result is
unsuccessful.

2.3.2.2 Admin Module

2.3.2.2.1 Rooms

2.3.2.2.1.1 Add

Input: Room type, Capacity, Price, Size,

Location, Status, Room number

Process: It stores data to the database.

Output: Room created successfully.

13
 2.3.2.2.1.2 Update

Input: Room type, Capacity, Price, Size,

Location, Status, Room number.

Process: It stores data to the database.

Output: Room updated successfully.

2.3.2.2.1.3 Delete

Input: Button click

Process: It will remove data from the database.

Output: Room deleted successfully.

2.3.2.2.2 Manage User

2.3.2.2.2.1 View

Input: Button Click

Process: It retrieves the data from the database.

Output: Display successful.

2.3.2.2.2.2 Delete

Input: Button Click

Process: It will remove the user from database.

Output: Display successful.

2.3.2.2.2.3 Update

Input: Email id, First name, Last name, User

name.

Process: It stores data to the database.

Output: It will update the user details.

14
2.3.2.2.3 Payment History

2.3.2.2.3.1 View

Input: Button-click

Process: Retrieves data from database

Output: Displays the payment history

2.3.2.2.3.2 Delete

Input: Button-click

Process: Retrieves data from database

Output: Delete the payment

2.3.2.2.4 Emergency Services

2.3.2.2.4.1 View

Input: Button Click

Process: It will retrieve the emergency services.

Output: Displays the emergency services.

2.3.2.2.4.2 Delete

Input: Button Click

Process: It will retrieve data from database.

Output: Deleted successfully.

15
 2.3.2.2.5 View Issues

Input: Button Click

Process: It will view the issues from the

database.

Output: View the issues reported by the user.

2.3.2.2.6 Notification

Input: User, Notification type, Message,

Created by.

Process: Store the information in the database

Output: Sends notification to particular user.

2.3.2.2.7 Reservation

Input: Type, Location, User name, Person,

Check-in, Check-out, Room Type, Price.

Process: Store the information in the database

Output: Reserves room for the users.

2.3.2.3 User Module

2.3.2.3.1 Booking

Input: Username, Password, Password confirmation,

Email, First name, Last name, Aadhar no, Phone no,
Room number.

Process: It will store to database.

Output: Display successful.

16
2.3.2.3.2 Emergency services

Input: Room no, Emergency type.

Process: It will store to database.

Output: Display successful.

2.3.2.3.3 Check Facility

Input: Button click

Process: It will retrieve all the facilities.

Output: It will display the facilities provided by the

apartment.

2.3.2.3.4 Report Issue

Input: Room no, Issues.

Process: It will store to database.

Output: Display successful.

2.3.2.3.5 Pay Bill

Input: Bill type, Amount.

Process: It will store to database.

Output: Display successful.

2.3.2.3.6 My Profile

2.3.2.3.6.1 View

Input: Button-click.

Process: Retrieves information from database.

Output: Displays the user details.

17
 2.3.2.3.6.2 Edit

Input: Email-id, Phone no, User name

Process: Updates information into database.

Output: Display successful.

2.3.2.3.7 Notification

2.3.2.3.7.1 View

Input: Button click.

Process: Retrieves information from database.

Output: Displays notifications.

2.3.2.3.7.2 Delete

Input: Button click.

Process: Retrieves information from database.

Output: Delete successful.

2.3.2.4 Guest User

2.3.2.4.1 Registration

Input: Username, Password, Password confirmation,

Email, First name, Last name, Aadhar no, Phone no.

Process: Stores information into database.

Output: Display successful.

18
2.3.2.4.2 Booking

Input: Location, Check-in, Check-out.

Process: It will store to database.

Output: Display successful.

2.3.2.4.3 My Bookings

2.3.2.4.3.1 View

Input: Button-click

Process: Retrieves data from the database

Output: Displays booking details

2.3.2.4.3.2 Cancel

Input: Button-click

Process: Retrieves data from the database

Output: Cancel successful.

2.3.2.4.4 Emergency service

Input: Room no, Emergency type

Process: It will store to database.

Output: Display successful.

2.3.2.4.5 Check facility

Input: Button click

Process: It will retrieve all the facilities.

Output: It will display the facilities provided by the

apartment.

19
2.3.2.4.6 Report Issues

Input: Room no, Issues.

Process: It will store to database.

Output: Display successful.

2.3.2.4.7 Notification

2.3.2.4.7.1 View

Input: Button click.

Process: Retrieves information from database.

Output: Display notification.

2.3.2.4.7.2 Delete

Input: Button click.

Process: Retrieves information from database.

Output: Delete successful.

2.3.2.4.8 My Profile

2.3.2.4.8.1 View

Input: Button-click.

Process: Retrieves information from database.

Output: Displays the user details.

2.3.2.4.8.2 Edit

Input: Email-id, Phone no, User name

Process: Updates information into database.

Output: Display successful.

20
2.3.3 Performance Requirements

This should satisfy both static and dynamic performance requirement.

2.3.3.1 Static requirement

Static requirement are those that do not impose constraint on

the execution behaviour of the system. These are also called
capacity requirement of the system.

2.3.3.2 Dynamic requirement

Dynamic requirement specifies constraint on the execution of

the system.

2.3.4 Design Constraints

2.3.4.1 Hardware Constraints

The hardware constraints specify the hardware which

requires developing the project

Hard disk: 500mb

Processor: CORE i3

2.3.4.2 Software Constraints

This project developed by Visual Studio Code editor, Django

server, web browser.

2.3.4.3 Fault Tolerance

It is the capacity of the system to behave properly when failure

occurs. Fault tolerance requirement can place major constraint
on how the system is to be designed.

21
 2.3.4.4 Security

This software provides the high-level security of data by

providing password, only authenticated person can operate this
software.

2.3.4.5 Standard Compliance

The software is design in such a way that it needs existing

standards. The software has graphical user interface ease of the
user.

2.3.5 System Attribute

This system specifies overall attribute that the system should have. The
attributes required to develop project Management are user login with
their user name and password are store in data base.

2.3.5.1 Accessibility

The user can access the software anywhere at the time 24*7 in
365 days.

2.3.5.2 Flexibility

The software is flexible to modify.

2.3.5.3 Portability

This application can be portable in all different types of

operation system.

2.3.6 Other Requirement

Not applicable

22
 3. SYSTEM DESIGN

3.1 Introduction

The purpose of the system design is planning the allocation of the problem
specified by domain the requirement document. This phase is the first step in moving
from the problem to solution domain. Design document includes system specification
as well as the design of the specification task, test specification and actual program.
The System design is used during implementation, testing, and maintenance.

System design which is sometimes also called top level design aims to identify
the module that should be in the system. The specification of the modules tells that
how they interact with each other to produce desired result. Much of the designing
webpage is spent in creating the system design. At the end of the system design all the
major data structure, file formats, and their major modules in the system and their
specification are decided.

3.2 Applicable Documents

System design uses the software requirement specification, synopsis

documents which are helpful in understanding or analyzing the requirements.

3.3 Functional Decomposition

Functional decomposition means large or complex problem is divided into

small phases. Each phase is view as software that has modules with sub modules.

3.4 Functional Components

3.4.1 Login

3.4.1.1 Login

Login module allows the user and the admin to login.

3.4.1.2 Forgot password

Forgot password allows the user to change the password.

23
3.5 Description of Program

3.5.1 Context Flow Diagram (CFD)

Context Flow Diagram is also called fundamental system model or

context model, which represents the entire software. It shows all the external entities
that interact with the system and the data flow between the external entities and the
system. CFD is a diagram in which the entire system is considered as a signal process
and all the inputs, outputs, sink and source are shown input data indicate by incoming
and outgoing arrows respectively.

ADMIN

Request for allocating Response for allocating

room, manage account, room, manage
view payment history, account, view payment
maintenance, history, maintenance,
emergency services, emergency services,
facilities. facilities.

APARTMENT
MANAGEMENT

Request for Response Request for Response for

registration, for registration, registration,
Emergency Services, registration, Reservation, Reservation,
Check facil ity, Emergency Emergency Emergency
Report issues, Services, Services, Services,
Pay bill. check check check facility,
facility, facility, Report issues,
Report Report
issues, issues,

USER GUEST

24
 3.5.2 Top level Data Flow Diagram

Data Flow Diagram is one of the structure system analysis models.

DFD shows flow of data through the system. It views the system as
function that transport input into desire output.

DFD Symbols:

Symbol Notification Object Name Description

Source or sink It is the net originator or

consumer of data which
interact with the system.

Process The agent that performs the

transformation of data from
input to output.

Data Flow It shows the direction of the

data flow.

Data Source It shows the place where the

data is stored.

25
Top level DFD for Admin:

User
Rooms

View
Delete
Add Update Payment
Delete

Manage Update

Rooms user
View

Payment Delete
Admin Login History

Issues
View
Emergency Issues
Reservation Service

Notification View

Emergency

Reservation Notification

26
Top level DFD for User:

Notification
User
s

View
View Edit
Delete Emergency

My profile
Notification

Emergency
Service

Check
User Registration Login
Facility

Report
issue
Pay Bill

Issue

Bill

27
Top level DFD for Guest:

Reservation

Cancel
View
View
Edit

My
booking
User My profile
Booking

Check
Guest Registration Login Facility

Emergency
Report Service
issues Notification

View Delete

Emergency
Issue

Notifications

28
3.5.3 Description of Components
3.5.3.1 Login Module
3.5.3.1.1 Input
User-ID, Password
3.5.3.1.2 Process Definition
Validating User-ID and Password
3.5.3.1.3 Output
Login successful
3.5.3.1.4 Interface with other functional component
Registration module
3.5.3.1.5 Resource Allocation
User
3.5.3.1.6 Scope prototyping, user interface
Textbox, button

Display
unsuccessful

Invalid Input

Valid Load to
User-name
User/admin Validation respective
Password page

User

29
 3.5.3.2 Forgot Password
3.5.3.2.1 Input
Email-ID
3.5.3.2.2 Process Definition
It insert the input into the table, user related hints will
be provided whenever the user provides exact
information it will allow the user to change the
password.
3.5.3.2.3 Output
Password changed successfully otherwise unsuccessful.
3.5.3.2.4 Interface with other functional
component
Not applicable
3.5.3.2.5 Resource Allocation
User
3.5.3.2.6 Scope prototyping, user interface
Textbox, Button

Display
unsuccessful

Invalid input
Change
Validation Valid password and
User
E-mail store to database

User

Display
Successful

30
3.5.3.3 Admin
3.5.3.3.1 Rooms
3.5.3.3.1.1 Add
3.5.3.3.1.1.1 Input
Room type, Capacity, Price, Size, Location, Status,
Room number.

3.5.3.3.1.1.2 Process definition

It stores data to the database.
3.5.3.3.1.1.3 Output
Room created successfully.

3.5.3.3.1.1.4 Interface with other functional

components
Not applicable
3.5.3.3.1.1.5 Resource allocation
Rooms
3.5.3.3.1.1.6 Scope prototyping, user interface
Textbox, Button

Display unsuccessful

Invalid
Input

Room Valid
Admin Validation Store to Data
Details base

Rooms

Display successful

31
 3.5.3.3.1.2 Update
3.5.3.3.1.2.1 Input
Room type, Capacity, Price, Size, Location, Status,
Room number.

3.5.3.3.1.2.2 Process definition

Stores data to the database

3.5.3.3.1.2.3 Output
Room updated successfully.

3.5.3.3.1.2.4 Interface with other functional

components
Not applicable
3.5.3.3.1.2.5 Resource allocation
Rooms
3.5.3.3.1.2.6 Scope prototyping, user interface
Textbox, Button

Display unsuccessful

Invalid

Room Valid
Admin Store to
Validation
Details Database

Room

Display successful

32
3.5.3.3.1.3 Delete
3.5.3.3.1.3.1 Input
Button click
3.5.3.3.1.3.2 Process definition
It will remove data from the database.

3.5.3.3.1.3.3 Output
Room deleted successfully.

3.5.3.3.1.3.4 Interface with other functional

components
Not applicable
3.5.3.3.1.3.5 Resource allocation
Rooms
3.5.3.3.1.3.6 Scope prototyping, user interface
Textbox, Button

Admin Button Retrieve data

Click from database

Rooms

Display successful

3.5.3.3.2 Manage user

3.5.3.3.2.1 View
3.5.3.3.2.1.1 Input
Button click
3.5.3.3.2.1.2 Process definition
It retrieves the data from the database.

33
 3.5.3.3.2.1.3 Output
It will view the user detail.
3.5.3.3.2.1.4 Interface with other functional
components
Not applicable
3.5.3.3.2.1.5 Resource allocation
User
3.5.3.3.2.1.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Admin Click
database

User

Details Displayed

3.5.3.3.2.2 Delete
3.5.3.3.2.2.1 Input
Button click
3.5.3.3.2.2.2 Process definition
It retrieve data from database.
3.5.3.3.2.2.3 Output
Display successful message.

3.5.3.3.2.2.4 Interface with other functional

components
Not applicable
3.5.3.3.2.2.5 Resource allocation
User

34
 3.5.3.3.2.2.6 Scope prototyping, user interface
Button

Admin Button Retrieve data

Click from database

User

Display successful

3.5.3.3.2.3 Update
3.5.3.3.2.3.1 Input
Email id, First name, Last name, User name.

3.5.3.3.2.3.2 Process definition

It stores data to the database.
3.5.3.3.2.3.3 Output
Update successful message.
3.5.3.3.2.3.4 Interface with other functional
components
Not applicable
3.5.3.3.2.3.5 Resource allocation
User
3.5.3.3.2.3.6 Scope prototyping, user interface
Button, Textbox

35
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
Admin

User

Display successful

3.5.3.3.3 Payment history

3.5.3.3.3.1 View
3.5.3.3.3.1.1 Input
Button click
3.5.3.3.3.1.2 Process definition
Retrieves data from the database
3.5.3.3.3.1.3 Output
Displays the payment history.
3.5.3.3.3.1.4 Interface with other functional
components
Not applicable
3.5.3.3.3.1.5 Resource allocation
Payment
3.5.3.3.3.1.6 Scope prototyping, user interface
Button

36
 Button
Retrieve data from
Admin Click
database

Payment

Details Displayed

3.5.3.3.3.2 Delete
3.5.3.3.3.2.1 Input
Button click
3.5.3.3.3.2.2 Process definition
Retrieves data from the database.
3.5.3.3.3.2.3 Output
Delete the payment successful.
3.5.3.3.3.2.4 Interface with other functional
components
Not applicable
3.5.3.3.3.2.5 Resource allocation
Payment
3.5.3.3.3.2.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Admin Click
database

Payment

Delete successful

37
3.5.3.3.4 Emergency Service
3.5.3.3.4.1 View
3.5.3.3.4.1.1 Input
Button Click
3.5.3.3.4.1.2 Process definition
It will retrieve data from database.
3.5.3.3.4.1.3 Output
Display the emergency services.
3.5.3.3.4.1.4 Interface with other functional
components
Not applicable
3.5.3.3.4.1.5 Resource allocation
Emergency
3.5.3.3.4.1.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Admin Click
database

Emergency

Details Displayed

3.5.3.3.4.2 Delete
3.5.3.3.4.2.1 Input
Button click
3.5.3.3.4.2.2 Process definition
Retrieves data from the database.
3.5.3.3.4.2.3 Output
Deleted successfully.

38
 3.5.3.3.4.2.4 Interface with other functional
components
Not applicable
3.5.3.3.4.2.5 Resource allocation
Emergency
3.5.3.3.4.2.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Admin Click
database

Emergency

Delete successful

3.5.3.3.5 View Issues

3.5.3.3.5.1 Input
Button Click
3.5.3.3.5.2 Process definition
It will retrieve data from the database.
3.5.3.3.5.3 Output
Issues displayed.
3.5.3.3.5.4 Interface with other functional components
Not applicable
3.5.3.3.5.5 Resource allocation
Report
3.5.3.3.5.6 Scope prototyping, user interface
Button

39
 Button
Retrieve data from
Admin Click
database

Issues

Details Displayed

3.5.3.3.6 Notification
3.5.3.3.6.1 Input
User, Notification type, Message, Created by
3.5.3.3.6.2 Process
Store the information in the database.

3.5.3.3.6.3 Output
Notification sent successfully.

3.5.3.3.6.4 Interface with other functional components

Not applicable
3.5.3.3.6.5 Resource allocation
Notification
3.5.3.3.6.6 Scope prototyping, user interface
Button, Textbox

40
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
Admin

Notification

Display successful

3.5.3.3.7 Reservation
3.5.3.3.7.1 Input
Type, Location, User name, Person, Check-in, Check-out,
Room type, Price

3.5.3.3.7.2 Process
Store the information in the database.
3.5.3.3.7.3 Output
Display successful message.
3.5.3.3.7.4 Interface with other functional components
Not applicable
3.5.3.3.7.5 Resource allocation
Reservation
3.5.3.3.7.6 Scope prototyping, user interface
Button, Textbox

41
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
Admin

Reservation

Display successful

3.5.3.4 User
3.5.3.4.1 Booking
3.5.3.4.1.1 Input
Username, Password, Password confirmation, Email, First
name, Last name, Aadhar no, Phone no, Room number.
3.5.3.4.1.2 Process definition
It will store to database.
3.5.3.4.1.3 Output
Display successful message.

3.5.3.4.1.4 Interface with other functional components

Not applicable
3.5.3.4.1.5 Resource allocation
Booking
3.5.3.4.1.6 Scope prototyping, user interface
Textbox, button

42
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

User

Display successful

3.5.3.4.3 Emergency Service

3.5.3.4.3.1 Input
Room no, Emergency type.
3.5.3.4.3.2 Process definition
It will store to database.
3.5.3.4.3.3 Output
Display successful.
3.5.3.4.3.4 Interface with other functional
components
Not applicable
3.5.3.4.3.5 Resource allocation
Emergency
3.5.3.4.3.6 Scope prototyping, user interface
Textbox, button

43
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

Emergency

Display successful

3.5.3.4.4 Check Facility

3.5.3.4.4.1 Input
Button click
3.5.3.4.4.2 Process definition
It will retrieve all the facilities.
3.5.3.4.4.3 Output
It will display the facilities provided by the apartment.
3.5.3.4.4.4 Interface with other functional components
Not applicable
3.5.3.4.4.5 Resource allocation
None
3.5.3.4.4.6 Scope prototyping, user interface
Button

44
 Button Retrieve all
User Click the facilities

Facilities displayed

3.5.3.4.5 Report Issues

3.5.3.4.5.1 Input
Room no, Issues.
3.5.3.4.5.2 Process definition
It will store to database.
3.5.3.4.5.3 Output
Display successful message.
3.5.3.4.5.4 Interface with other functional components
Not applicable
3.5.3.4.5.5 Resource allocation
Report
3.5.3.4.5.6 Scope prototyping, user interface
Textbox, button

Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

Report

Display successful

45
 3.5.3.4.6 Pay Bill
3.5.3.4.6.1 Input
Bill type, Amount.
3.5.3.4.6.2 Process definition
It will store to database.
3.5.3.4.6.3 Output
Display successful message.
3.5.3.4.6.4 Interface with other functional components
Not applicable
3.5.3.4.6.5 Resource allocation
Bill
3.5.3.4.6.6 Scope prototyping, user interface
Textbox, Button

Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

Bill

Display successful

46
3.5.3.4.7 My Profile
3.5.3.4.7.1 View
3.5.3.4.7.1 Input
Button click
3.5.3.4.7.2 Process
Retrieves information from the database.
3.5.3.4.7.3 Output
Displays the user details.
3.5.3.4.6.4 Interface with other functional
components
Not applicable
3.5.3.4.6.5 Resource allocation
User
3.5.3.4.6.6 Scope prototyping, user interface
Button

Button
Retrieve data from
User Click
database

User

Details Displayed

3.5.3.4.7.1 Edit
3.5.3.4.7.1 Input
Email-id, Phone no, User name
3.5.3.4.7.2 Process
Updates information into database

47
 3.5.3.4.7.3 Output
Update successful.
3.5.3.4.6.4 Interface with other functional
components
Not applicable
3.5.3.4.6.5 Resource allocation
User
3.5.3.4.6.6 Scope prototyping, user interface
Button, Textbox

Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

User

Display successful

3.5.3.4.8 Notification
3.5.3.4.8.1 View
3.5.3.4.8.1.1 Input
Button-click
3.5.3.4.8.1.2 Process
Retrieves data from database
3.5.3.4.8.1.3 Output
Displays notification

48
 3.5.3.4.8.1.4 Interface with other functional
components
Not applicable
3.5.3.4.8.1.5 Resource allocation
Notification
3.5.3.4.8.1.6 Scope prototyping, user interface
Button

Button
Retrieve data from
User Click
database

Notification

Details Displayed

3.5.3.4.8.1 Delete
3.5.3.4.8.1.1 Input
Button click
3.5.3.4.8.1.2 Process
Retrieves data from database.
3.5.3.4.8.1.3 Output
Delete successful.
3.5.3.4.8.1.4 Interface with other functional
components
Not applicable
3.5.3.4.8.1.5 Resource allocation
Notification
3.5.3.4.8.1.6 Scope prototyping, user interface
Button

49
 Button
Retrieve data from
User Click
database

Notification

Delete successful

3.5.3.5 Guest
3.5.3.5.1 Registration
3.5.3.5.1.1 Input
Username, Password, Password confirmation Email, First
name, Last name, Aadhar no, Phone no.

3.5.3.5.1.2 Process Definition

Stores information into database.
3.5.3.5.1.3 Output
Display successful message.
3.5.3.5.1.4 Interface with other functional component
Not applicable
3.5.3.5.1.5 Resource Allocation
User/guest

Display unsuccessful

Invalid

Valid
Details Validation Store to database
Guest

Guest/user

Display successful

50
3.5.3.5.2 Booking
3.5.3.5.2.1 Input
Location, Check-in, Check-out.
3.5.3.5.2.2Process definition
It will store to database.
3.5.3.5.2.3 Output
Display successful message.
3.5.3.5.2.4 Interface with other functional components
Not applicable
3.5.3.5.2.5 Resource allocation
Booking
3.5.3.5.2.6 Scope prototyping, user interface
Button, Textbox

Display unsuccessful

Invalid

Valid
Details Validation Store to database
Guest

Booking

Display successful

3.5.3.5.3 My Bookings
3.5.3.5.3.1 View
3.5.3.5.3.1.1 Input
Button-click

51
 3.5.3.5.3.1.2Process definition
Retrieves data from the database.
3.5.3.5.3.1.3 Output
Displays booking details.
3.5.3.5.3.1.4 Interface with other functional
components
Not applicable
3.5.3.5.3.1.5 Resource allocation
Bookings
3.5.3.5.3.1.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Guest Click
database

Bookings

Details Displayed

3.5.3.5.3.2 Cancel
3.5.3.5.3.2.1 Input
Button click
3.5.3.5.3.2.2 Process definition
Retrieves data from the database.
3.5.3.5.3.2.3 Output
Cancel successful message.
3.5.3.5.3.2.4 Interface with other functional
components
Not applicable
3.5.3.5.3.2.5 Resource allocation
Bookings

52
 3.5.3.5.3.2.6 Scope prototyping, user interface
Button

Button
Retrieve data from
Guest Click
database

Bookings

Cancel successful

3.5.3.5.2 Emergency Service

3.5.3.5.2.1 Input
Room no, Emergency type.
3.5.3.5.2.2 Process definition
It will store to database.
3.5.3.5.2.3 Output
Display successful message.
3.5.3.5.2.4 Interface with other functional components
Not applicable
3.5.3.5.2.5 Resource allocation
Emergency
3.5.3.5.2.6 Scope prototyping, user interface
Textbox, button

53
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

Emergency

Display successful

3.5.3.5.3 Check Facility

3.5.3.5.3.1 Input
Button click
3.5.3.5.3.2 Process definition
It will retrieve all the facilities.
3.5.3.5.3.3 Output
It will display the facilities provided by the apartment.
3.5.3.5.3.4 Interface with other functional
Components
Not applicable
3.5.3.5.3.5 Resource allocation
None
3.5.3.5.3.6 Scope prototyping, user interface
Button

Button Retrieve all

User Click the facilities

Facilities displayed

54
3.5.3.5.4 Report Issues
3.5.3.5.4.1 Input
Room no, Issues.
3.5.3.5.4.2 Process definition
It will store to database.
3.5.3.5.4.3 Output
Display successful message.
3.5.3.5.4.4 Interface with other functional components
Not applicable
3.5.3.5.4.5 Resource allocation
Report
3.5.3.5.4.6 Scope prototyping, user interface
Textbox, button

Display unsuccessful

Invalid

Valid
Details Validation Store to database
Guest

Report

Display successful

3.5.3.5.8 Notification
3.5.3.5.8.1 View
3.5.3.5.8.1.1 Input
Button-click

55
 3.5.3.5.8.1.2 Process
Retrieves data from database.
3.5.3.5.8.1.3 Output
Displays notification.
3.5.3.5.8.1.4 Interface with other functional
components
Not applicable
3.5.3.5.8.1.5 Resource allocation
Notification
3.5.3.5.8.1.6 Scope prototyping, user interface
Button

Button
Retrieve data from
User Click
database

Notification

Details Displayed

3.5.3.5.8.2 Delete
3.5.3.5.8.2.1 Input
Button click
3.5.3.5.8.2.2 Process
Retrieves data from database.
3.5.3.5.8.2.3 Output
Delete successful.
3.5.3.5.8.2.4 Interface with other functional
components
Not applicable

56
 3.5.3.5.8.2.5 Resource allocation
Notification
3.5.3.5.8.2.6 Scope prototyping, user interface
Button

Button
Retrieve data from
User Click
database

Notification

Delete successful

3.5.3.5.9 My Profile
3.5.3.5.9.1 View
3.5.3.5.9.1 Input
Button click
3.5.3.5.9.2 Process
Retrieves information from the database.
3.5.3.5.9.3 Output
Displays the user details.
3.5.3.5.9.4 Interface with other functional
components
Not applicable
3.5.3.5.9.5 Resource allocation
User
3.5.3.5.9.6 Scope prototyping, user interface
Button

57
 Button
Retrieve data from
User Click
database

User

Details Displayed

3.5.3.5.9.2 Edit
3.5.3.5.9.2.1 Input
Email-id, Phone no, User name
3.5.3.5.9.2.2 Process
Updates information into database
3.5.3.5.9.2.3 Output
Update successful.
3.5.3.5.9.2.4 Interface with other functional
components
Not applicable
3.5.3.5.9.2.5 Resource allocation
User
3.5.3.5.9.2.6 Scope prototyping, user interface
Button, Textbox

58
 Display unsuccessful

Invalid

Valid
Details Validation Store to database
User

User

Display successful

59
 4. DATABASE DESIGN

4.1 Introduction
Database is a collection of related data. Relational database store in tables or
relation. The data stored in relation are arranged in records. Each record consists of
set of attributes. Fields can be referred to as characteristics of record. This document
describes the table that is used to design software, its attributes, data type, constraints,
relationship among those tables.

4.2 Description of the tables and fields

1. User

Fieldname Datatype Size Constraints Description

Id Bigint 10 Primary key Id

Password Character 128 Not null Password

Email Character 60 Primary key Email-id

User-name Character 30 Not null User-name

Date-joined Timestamp - Not null Date joined

Last-login Timestamp - Not null Last login

phone int - Not null Phone Number

aadhar int - Not null Proof of identity

Is-resident Boolean - Not null Is staff

Is-guest Boolean - Not null Is super user

60
2. Reservations

Fieldname Datatype Size Constraints Description

Booking Id Bigint 10 Primary key ID

username char 20 unique Username

Check-in Timestamp - Not null Check-in

Check-out Timestamp - Not null Check-out

Payment Float 10 Not null Payment status

Room-no Bigint 10 Primary key Room-id

User-id Bigint 10 Not null User-id

3. Emergency

Field Datatype Size Constraints Description

name
Id Bigint 10 Foreign key Id

Room-no Bigint 10 Foreign key Room number

Category Character 50 Not null Category

4. room
Fieldname Datatype Size Constraints Description
Room-no Integer 10 Primary Key Room number

Beds Integer 10 Not null Beds

size Int 5 NotNull Sizes

Category Character 10 Not null Category

Capacity Integer 10 Not null Capacity

price float 10 Not Null Price

status Character 20 Not Null Status

61
5. Issues

Field name Data type Size Constraints Description

Id Bigint 10 Primary key User -id

Room Bigint 10 Foreign key Room number

Number
Issue Character 50 Not null Issue

6. Bill

Field name Data type Size Constraints Description

Id Bigint 10 Primary key User -id

Type Bigint 10 Foreign key Type

Amount Integer 50 Not null Amount

4.3 ER Diagram
ER Diagram is visual representation of data that describe how data is related
to each other in ER model we disintegrate data into entities, attributes and set up
relationship between entities or these can be represented visually using the ER
diagram. Symbolic nation and their description used in drawing the ER diagram are
follows:

62
Symbol Convention
Entity

Weak entity

Relation

Weak entity relation or identifying

relation
Derived attribute

Key attribute

Attribute

Cardinality ratio of 1:1 for E1:E2 in R

1 1
E1 R E2

Multi valued attribute

Composite attribute

Cardinality ratio of 1: N for E1:E2 in R

1 N
E1 R E2

1 1 Partial participation
E1 R E2

Total participation
1 N
E1 R E2

63
 4.3.1 User

Room
no
Id Id
Category
Room
no
Emergency Issues
Category
N N

Has
Has

Id
Phone no
Password 1 1
Aadhar
1
User
Email
Is guest
Date Joined 1
Is
Last login Has resident

Room

Id Amount
Type

64
4.3.2 Guest

Room
no
Id Id
Category
Room
no
Emergency Issues
Category
N N

Has
Has

Id
Payment
User
1 1
Room no
1
Guest
Check in
User id
Check out
1

Has

Room no N Status

Bill
Beds
Price

Size
Capacity
Category

65
 5. Detailed Design

5.1 Introduction
Detailed design or logical design concentrates on the internal logic of module
which is identified during the system design documents uses structure chart or logic
of the module identified and al so it uses flow chart for the procedural detail. The
detailed of the system is the last design activity before implementation begins the
detailed design should represent the system design in a verity of views where each
view uses a different modelling technique.
A template for detailed design would not be of much use since each detailed
design is likely to be unique and quite different from other design.

5.2 Application Document

 Synopsis
 Software Requirement Specification
 System Design

66
5.3 Structure of the software package

Apartment Management

Login Admin User Guest

Rooms Booking Registration

Login

Add Emergency Booking

Forgot
service
password
Update My bookings
Check facility
Delete
View

Manage user Report issue

Cancel

View Pay bill Emergency

service
Delete
My profile
Update
Check facility

View
Payment History Report issues
Edit
Notification
View
Notification
Delete View
View
Delete
Emergency Service
Delete
My profile
View
View
Delete
Edit

View Issues

Notification

Reservation

67
5.4 Modular Decomposition of Components
5.4.1 Login module
5.4.1.1 Login
5.4.1.1.1 Design Assumption
All fields are mandatory.
5.4.1.1.2 Identification of module
This module is used to login to the system with input
user Id and Password.
5.4.1.1.3 Hierarchy of login module
Main Module

Login

5.4.1.1.4 Data structure stored among modules

User/guest
5.4.1.1.5 Structured English (Design Logic)
INPUT user ID and password
IF user ID and password valid THEN
Load to respective page
ELSE
Error message displayed
END IF
5.4.1.2 Forgot password
5.4.1.2.1 Design assumption
All fields are mandatory.
5.4.1.2.2 Identification of module
This module is used to set the password if the user has
forgotten his password.

68
 5.4.1.2.3 Hierarchy of login module
Login

Forgot password

5.4.1.2.4 Data structure stored among modules

User/guest
5.4.1.2.5 Structured English (Design Logic)
INPUT email-id
IF email-id valid THEN
Allow to change password
Display successful message
ELSE
Error message displayed
END IF
5.4.2 Admin
5.4.2.1 Rooms
5.4.2.1.1 Add
5.4.2.1.1.1 Design assumption
All fields are mandatory.
5.4.2.1.1.2 Identification of module
It stores data to the database.
5.4.2.1.1.3 Hierarchy of login module
Rooms

Add

5.4.2.1.1.4 Data structure stored among

modules
Rooms

69
 5.4.2.1.1.5 Structured English (Design Logic)
INPUT room details
IF room details valid THEN
STORE room details into database
Display successful
ELSE
Display error message
END IF
5.4.2.1.2 Update
5.4.2.1.2.1 Design assumption
All fields are mandatory.
5.4.2.1.2.2 Identification of module
It stores data to the database.
5.4.2.1.2.3 Hierarchy of login module
Rooms

Update

5.4.2.1.2.4 Data structure stored among

modules
Rooms
5.4.2.1.2.5 Structured English (Design Logic)
INPUT room details
IF room details valid THEN
STORE room details into database
Display successful
ELSE
Display error message
END IF

70
 5.4.2.1.3 Delete
5.4.2.1.3.1 Design Assumption
Not Applicable.
5.4.2.1.3.2 Identification of Module
It will remove data from the database.
5.4.2.1.3.3 Hierarchy of Login Module

Rooms

Delete

5.4.2.1.3.4 Data Structure Stored Among

Modules
Rooms
5.4.2.1.3.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY successful
5.4.2.2 Manage User
5.4.2.2.1 View
5.4.2.2.1.1 Design Assumption
Not applicable.
5.4.2.2.1.2 Identification of Module
It is used to view the user information.
5.4.2.2.1.3 Hierarchy of Login Module
Manage User

View

71
 5.4.2.2.1.4 Data Structure Stored Among
Modules
User
5.4.2.2.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE information from database
DISPLAY user details
5.4.2.2.2 Delete
5.4.2.2.2.1 Design Assumption
Not applicable
5.4.2.2.2.2 Identification of Module
It is used to delete the user.
5.4.2.2.2.3 Hierarchy of Login Module
Manage User

Delete

5.4.2.2.2.4 Data Structure Stored Among

Modules
User
5.4.2.2.2.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE information from database
DISPLAY successful
5.4.2.2.3 Update
5.4.2.2.3.1 Design Assumption
All fields are mandatory.
5.4.2.2.3.2 Identification of Module
It stores data to the database.

72
 5.4.2.2.3.3 Hierarchy of Login Module
Manage User

Update

5.4.2.2.3.4 Data Structure Stored Among

Modules
User
5.4.2.2.3.5 Structured English (Design Logic)
INPUT user details
IF user details valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.2.3 Payment History
5.4.2.3.1 View
5.4.2.3.1.1 Design Assumption
Not applicable.
5.4.2.3.1.2 Identification of Module
Retrieves data from database.
5.4.2.3.1.3 Hierarchy of Login Module
Payment history

View

73
 5.4.2.3.1.4 Data Structure Stored Among
Modules
Payment
5.4.2.3.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.2.3.2 Delete
5.4.2.3.2.1 Design Assumption
Not applicable.
5.4.2.3.2.2 Identification of Module
Retrieves data from database.
5.4.2.3.2.3 Hierarchy of Login Module
Payment history

Delete

5.4.2.3.2.4 Data Structure Stored Among

Modules
Payment
5.4.2.3.2.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY successful
5.4.2.5 Emergency Services
5.4.2.5.1 View
5.4.2.5.1.1 Design Assumption
Not applicable.

74
 5.4.2.5.1.2 Identification of Module
It will retrieve data from the database.
5.4.2.5.1.3 Hierarchy of Login Module

Emergency Service

View

5.4.2.5.1.4 Data Structure Stored Among

Modules
Emergency
5.4.2.5.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.2.5.2 Delete
5.4.2.5.2.1 Design Assumption
Not applicable.
5.4.2.5.2.2 Identification of Module
It will retrieve data from database.
5.4.2.5.2.3 Hierarchy of Login Module
Emergency
Servies

Delete

5.4.2.5.2.4 Data Structure Stored Among

Modules
Emergency

75
 5.4.2.5.2.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY successful
5.4.2.6 View Issues
5.4.2.6.1 Design Assumption
Not applicable.
5.4.2.6.2 Identification of Module
It will view the issues from the database.
5.4.2.6.3 Hierarchy of Login Module

Admin

View issues

5.4.2.6.4 Data Structure Stored Among Modules

Issues
5.4.2.6.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.2.7 Notification
5.4.2.7.1 Design Assumption
Not applicable
5.4.2.7.2 Identification of Module
It is used to send notification to the users.
5.4.2.7.3 Hierarchy of Login Module
Admin

Notification

76
 5.4.2.7.4 Data Structure Stored Among Modules
Notification
5.4.2.7.5 Structured English (Design Logic)
INPUT details
IF details valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.2.8 Reservation
5.4.2.8.1 Design Assumption
Not applicable
5.4.2.8.2 Identification of Module
It is used to view the bookings of user.

5.4.2.8.3 Hierarchy of Login Module

Admin

Reservation

5.4.2.8.4 Data Structure Stored Among Modules

Reservation
5.4.2.8.5 Structured English (Design Logic)
INPUT details
IF details valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF

77
5.4.3 User
5.4.3.1 Booking
5.4.3.1.1 Design Assumption
All fields are mandatory.
5.4.3.1.2 Identification of Module
It is used to book a room.
5.4.3.1.3 Hierarchy of Login Module

User

Booking

5.4.3.1.4 Data Structure Stored Among Modules

User
5.4.3.1.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.3.2 Emergency Services
5.4.3.2.1 Design Assumption
All fields are mandatory.
5.4.3.2.2 Identification of Module
It is used to request the emergency services.

78
 5.4.3.2.3 Hierarchy of Login Module
User

Emergency
services

5.4.3.2.4 Data Structure Stored Among Modules

Emergency
5.4.3.2.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.3.3 Check Facility
5.4.3.3.1 Design Assumption
Not applicable
5.4.3.3.2 Identification of Module
It is used check the different facilities available.
5.4.3.3.3 Hierarchy of Login Module

User

Check Facility

5.4.3.4 Report issues

5.4.3.4.1 Design Assumption
All fields are mandatory.

79
 5.4.3.4.2 Identification of Module
It is used to report the issues.
5.4.3.4.3 Hierarchy of Login Module
User Module

Report issues

5.4.3.4.4 Data Structure Stored Among Modules

View-issues
5.4.3.4.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.3.5 Pay Bill
5.4.3.5.1 Design Assumption
All fields are mandatory.
5.4.3.5.2 Identification of Module
It is used to pay bill.
5.4.3.5.3 Hierarchy of Login Module
User

Pay Bill

5.4.3.5.4 Data Structure Stored Among Modules

Bill

80
 5.4.3.5.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.3.6 My Profile
5.4.3.6.1 View
5.4.3.6.1.1 Design Assumption
Not applicable
5.4.3.6.1.2 Identification of Module
It is used to view the user profile.
5.4.3.6.1.3 Hierarchy of Login Module

User

View

5.4.3.6.1.4 Data Structure Stored Among Modules

User
5.4.3.6.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.3.6.2 Edit
5.4.3.6.2.1 Design Assumption
All fields are mandatory.
5.4.3.6.2.2 Identification of Module
It is used to update the user profile.

81
 5.4.3.6.2.3 Hierarchy of Login Module

User

Edit

5.4.3.6.2.4 Data Structure Stored Among Modules

User
5.4.3.6.2.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.3.7 Notification
5.4.3.7.1 View
5.4.3.7.1.1 Design Assumption
Not applicable
5.4.3.7.1.2 Identification of Module
It is used to view the notification sent by admin.

5.4.3.7.1.3 Hierarchy of Login Module

User

View

5.4.3.7.1.4 Data Structure Stored Among Modules

Notification

82
 5.4.3.7.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.3.7.2 Delete
5.4.3.7.2.1 Design Assumption
Not applicable
5.4.3.7.2.2 Identification of Module
It is used to delete the notification.

5.4.3.7.2.3 Hierarchy of Login Module

User

Delete

5.4.3.7.2.4 Data Structure Stored Among Modules

Notification
5.4.3.7.2.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DELETE successful
5.4.4 Guest
5.4.4.1 Registration
5.4.4.1.1 Design Assumption
All fields are mandatory.
5.4.4.1.2 Identification of Module
It is used to register.
5.4.4.1.3 Hierarchy of Login Module

Guest

Registration
83
 5.4.4.1.4 Data Structure Stored Among Modules
Register
5.4.4.1.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.4.2 Booking
5.4.4.2.1 Design Assumption
All fields are mandatory.
5.4.4.2.2 Identification of Module
It is used to book a room.
5.4.4.2.3 Hierarchy of Login Module

Guest

Booking

5.4.4.2.4 Data Structure Stored Among Modules

Reservation
5.4.4.2.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF

84
5.4.4.3 My Bookings
5.4.4.3.1 View
5.4.4.3.1.1 Design Assumption
Not applicable
5.4.4.3.1.2 Identification of Module
It is used to view the booking details.

5.4.4.3.1.3 Hierarchy of Login Module

Guest

View

5.4.4.3.1.4 Data Structure Stored Among Modules

Reservation
5.4.4.3.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.4.4 Cancel
5.4.4.4.1.1 Design Assumption
Not applicable
5.4.4.4.1.2 Identification of Module
It is used to cancel the booking.

5.4.4.4.1.3 Hierarchy of Login Module

Guest

Cancel

85
 5.4.4.4.1.4 Data Structure Stored Among Modules
Reservation
5.4.4.4.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
CANCEL successful
5.4.4.5 Emergency Service
5.4.4.5.1 Design Assumption
All fields are mandatory.
5.4.4.5.2 Identification of Module
It is used to request the emergency services.
5.4.4.5.3 Hierarchy of Login Module
Guest

Emergency
services

5.4.4.5.4 Data Structure Stored Among Modules

Emergency
5.4.4.5.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF
5.4.4.6 Check Facility
5.4.4.6.1 Design Assumption
Not applicable

86
 5.4.4.6.2 Identification of Module
It is used check the different facilities available.
5.4.4.6.3 Hierarchy of Login Module

Guest

Check Facility

5.4.4.7 Report issues

5.4.4.7.1 Design Assumption
All fields are mandatory.
5.4.4.7.2 Identification of Module
It is used to report the issues.
5.4.4.7.3 Hierarchy of Login Module
Guest

Report issues

5.4.4.7.4 Data Structure Stored Among Modules

View issues
5.4.4.7.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF

87
5.4.4.8 Notification
5.4.4.8.1 View
5.4.4.8.1.1 Design Assumption
Not applicable
5.4.4.8.1.2 Identification of Module
It is used to view the notification sent by admin.

5.4.4.8.1.3 Hierarchy of Login Module

Guest

View

5.4.4.8.1.4 Data Structure Stored Among Modules

Notification
5.4.4.8.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.4.8.2 Delete
5.4.4.8.2.1 Design Assumption
Not applicable
5.4.4.8.2.2 Identification of Module
It is used to delete the notification.

5.4.4.8.2.3 Hierarchy of Login Module

Guest

Delete

5.4.4.8.2.4 Data Structure Stored Among Modules

Notification

88
 5.4.4.8.2.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DELETE successful
5.4.4.9 My Profile
5.4.4.9.1 View
5.4.4.9.1.1 Design Assumption
Not applicable
5.4.4.9.1.2 Identification of Module
It is used to view the user profile.
5.4.4.9.1.3 Hierarchy of Login Module
Guest

View

5.4.4.9.1.4 Data Structure Stored Among Modules

User
5.4.4.9.1.5 Structured English (Design Logic)
INPUT button-click
RETRIEVE from database
DISPLAY information
5.4.4.9.2 Edit
5.4.4.9.2.1 Design Assumption
Not applicable
5.4.4.9.2.2 Identification of Module
It is used to update the user profile.

89
5.4.4.9.2.3 Hierarchy of Login Module

Guest

Edit

5.4.4.9.2.4 Data Structure Stored Among Modules

User
5.4.4.9.2.5 Structured English (Design Logic)
INPUT details
IF details are valid THEN
STORE to database
Display successful
ELSE
DISPLAY error message
END IF

90
5.5 Detailed Design
Detailed design can be represented by using either a flowchart or a structure
chart.
Flowchart: Flowchart is a diagram that shows a pictorial representation of the
algorithm, a step by step approach to solving a task. Flowchart uses shapes to
represent types of action or step in the process.

Symbol Name Description

Terminator It indicates the beginning
and the end.
Process It is used to show a
process, task, action or
operation.
Input/Output It represents the user input
and output produced.

Decision It represents sequence in

process where end user
chooses an option and then
branches an alternate path.
Connector It indicates the continuity
of next step in another
page.

Flow It represents the flow of

control.

91
Structured chart: Structured chart illustrate the partitioning of the problem into
sub problems and shows the hierarchical relationship among the parts. A structured
chart is a top-down modular design tool, constructed of square representing different
modules in a system, and lines that connect them.

Symbol Name Description

Module It represents a sub-

ordinate and superior-
ordinate modules.

Dataflow It indicates the direction

flow of data.

Control flow It indicates the direction

flow of control.

Conditional invocation It indicates that the

invocation of sub-
ordinate modules.

Module invocation It represents sub-

ordinate modules being
invoked by superior-
ordinate modules.

Loop It represents the

repetition of the loop.

92
5.5.1 Module Design Of Components
5.5.1.1 Login Module
5.5.1.1.1 Login
5.5.1.1.1.1Input
User-ID, password.
5.5.1.1.1.2Procedural Details
 Structured Chart

Login

Input user-ID Display

Authentication
respective
password
page

Read inputs Validation

Load the Display

page unsuccessful
message
 Algorithm
Step1: Start
Step2: Input user_id and password
Step3: Validate the input
Step4: If input is valid then
Display successfully login done
Load to respective pages
Else
Display unsuccessful message
Go to step2
End if
Step5: Stop

93
  Flow Chart

Start

Input user_id
and password

User/ Validation
guest Display error
message

If input is False
valid

True
Load to respective page

Display successful
message

Stop

5.5.1.1.1.3 File I/O Interface

User/Guest
5.5.1.1.1.4 Output
It will login to the respective pages.
5.5.1.1.1.5 Implementation Aspects
It requires buttons and textbox.

94
 5.5.1.1.2 Forgot Password
5.5.1.1.2.1 Input
Email-id
5.5.1.1.2.2 Procedural Details
 Structured Chart
Forgot password

Input Email-id Display

Verification
successful
message

Read inputs validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Email-id
Step3: Validate the input
Step4: If input is valid then
Allow to change password
Display successful message
Else
Display unsuccessful message
Go to step2
End if
Step5: Stop

95
  Flow Chart

Start

Input Email-id

User/ Validation
Guest Display error
message
If input False
Is valid

True
Change password and Store to database

Display successful
message

Stop

5.5.1.1.2.3 File I/O Interface

User/Guest
5.5.1.1.2.4 Output
It will change the password
5.5.1.1.2.5 Implementation Aspects
It requires buttons and textbox.
5.5.1.2 Admin Module
5.5.1.2.1 Rooms
5.5.1.2.1.1 Add
5.5.1.2.1.1.1 Input
Room details

96
 5.5.1.2.1.1.2 Procedural Details
 Structured Chart

Add

Input room Display

Add room
information
details

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input room details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

97
  Flow Chart

Start

Input Details

If input False Display error

Rooms
Is valid message

True

Store to database

Display Successful

Stop

5.5.1.2.1.1.3 File I/O Interface

Rooms

5.5.1.2.1.1.4 Output

Room created successfully.

5.5.1.2.1.1.5 Implementation Aspects

Button, Textbox

98
 5.5.1.2.1.2 Update
5.5.1.2.1.2.1 Input
Room details
5.5.1.2.1.2.2 Procedural Details
 Structured Chart

Update

Input room Display

Update room
information
details

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input room details
Step3: Validate the input
Step4: If input is valid then
Update to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

99
  Flow Chart

Start

Input Details

If input False Display error

Rooms
Is valid message

True

Update to database

Display Successful

Stop

5.5.1.2.1.2.3 File I/O Interface

Rooms

5.5.1.2.1.2.4 Output

Room updated successfully.

5.5.1.2.1.2.5 Implementation Aspects

Button, Textbox

5.5.1.2.1.3 Delete
5.5.1.2.1.3.1 Input
Button-Click

100
 5.5.1.2.1.3.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop
 Flow Chart

Start

Rooms Input Details

Retrieve data from the database

Display Successful

Stop

101
 5.5.1.2.1.3.3 File I/O Interface

Rooms

5.5.1.2.1.3.4 Output

Room deleted successfully.

5.5.1.2.1.3.5 Implementation Aspects

Button

5.5.1.2.2 Manage User

5.5.1.2.2.1 View

5.5.1.2.2.1.1 Input
Button-Click
5.5.1.2.2.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

102
  Flow Chart

Start

User Input Details

Retrieve data from the database

Display information

Stop

5.5.1.2.2.1.3 File I/O Interface

User

5.5.1.2.2.1.4 Output

Display successful message.

5.5.1.2.2.1.5 Implementation Aspects

Button

5.5.1.2.2.2 Delete

5.5.1.2.2.2.1 Input
Button-Click

103
 5.5.1.2.2.2.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop

 Flow Chart

Start

User Input Details

Retrieve data from the database

Display successful

Stop

104
 5.5.1.2.2.2.3 File I/O Interface

User

5.5.1.2.2.2.4 Output

Display successful message.

5.5.1.2.2.2.5 Implementation Aspects

Button

5.5.1.2.2.3 Update

5.5.1.2.2.3.1 Input
User name, Email, First name, Last name, Phone
number
5.5.1.2.2.3.2 Procedural Details
 Structured Chart

Update

Input user Update user Display

information
Details Details

Read inputs Validation

Store to Display
database unsuccessful
message

105
  Algorithm
Step1: Start
Step2: Input user details
Step3: Validate the input
Step4: If input is valid then
Update to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

 Flow Chart

Start

Input User Details

User

If input False Display error

Is valid message

True

Update to database

Display Successful

Stop

106
 5.5.1.2.2.3.3 File I/O Interface

User

5.5.1.2.2.3.4 Output

It will update the user details.

5.5.1.2.2.3.5 Implementation Aspects

Button, Textbox

5.5.1.2.3 Payment History

5.5.1.2.3.1 View

5.5.1.2.3.1.1 Input
Button-Click
5.5.1.2.3.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

107
  Flow Chart

Start

Payment Input Details

Retrieve data from the database

Display information

Stop

5.5.1.2.3.1.3 File I/O Interface

Payment

5.5.1.2.3.1.4 Output

Displays the payment history

5.5.1.2.3.1.5 Implementation Aspects

Button

5.5.1.2.3.2 Delete

5.5.1.2.3.2.1 Input
Button-Click

108
 5.5.1.2.3.2.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop

 Flow Chart

Start

Payment Input Details

Retrieve data from the database

Display successful

Stop

109
 5.5.1.2.3.2.3 File I/O Interface

Payment

5.5.1.2.3.2.4 Output

Delete the payment

5.5.1.2.3.2.5 Implementation Aspects

Button

5.5.1.2.4 Emergency Service

5.5.1.2.4.1 View

5.5.1.2.4.1.1 Input
Button-Click
5.5.1.2.4.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

110
  Flow Chart

Start

Emergency Input Details

Retrieve data from the database

Display information

Stop

5.5.1.2.4.1.3 File I/O Interface

Emergency

5.5.1.2.4.1.4 Output

Display the emergency services.

5.5.1.2.4.1.5 Implementation Aspects

Button

5.5.1.2.4.2 Delete

5.5.1.2.4.2.1 Input
Button-Click

111
 5.5.1.2.4.2.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop

 Flow Chart

Start

Emergency Input Details

Retrieve data from the database

Display successful

Stop

112
 5.5.1.2.4.2.3 File I/O Interface

Emergency

5.5.1.2.4.2.4 Output

Deleted successfully message.

5.5.1.2.4.2.5 Implementation Aspect

Button

5.5.1.2.5 View Issues

5.5.1.2.5.1 Input
Button-Click
5.5.1.2.5.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

113
  Flow Chart

Start

Issues Input Details

Retrieve data from the database

Display information

Stop

5.5.1.2.5.3 File I/O Interface

Issues

5.5.1.2.5.4 Output

View the issues reported by the user.

5.5.1.2.5.5 Implementation Aspects

Button

5.5.1.2.6 Notification

5.5.1.2.6.1 Input
user name, notification type, message, created by

114
 5.5.1.2.6.2 Procedural Details
 Structured Chart
Notification

Input Display
successful
Details Verification

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

115
  Flow Chart

Start

Notification
Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.2.6.3 File I/O Interface

Notification

5.5.1.2.6.4 Output

Sends notification to particular user.

5.5.1.2.6.5 Implementation Aspects

Textbox, Button

116
 5.5.1.2.7 Reservation

5.5.1.2.7.1Input
Booking id, user name, room no, check-in, check-out.
5.5.1.2.7.2 Procedural Details
 Structured Chart

Reservation

Input Details Display

Verification
successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

117
  Flow Chart

Start

Reservation Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.2.7.3 File I/O Interface

Reservation

5.5.1.2.7.4 Output

Display successful message.

5.5.1.2.7.5 Implementation Aspects

Button, Textbox

118
 5.5.1.3 User
5.5.1.3.1 Booking

5.5.1.3.1.1Input
Booking details
5.5.1.3.1.2 Procedural Details
 Structured Chart

Booking

Input Details Display

Verification
successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

119
  Flow Chart

Start

User Input Details

False
If input Display error
Is valid message

True

Store to database

Display Successful

Stop

5.5.1.3.1.3 File I/O Interface

User

5.5.1.3.1.4 Output

Display successful message.

5.5.1.3.1.5 Implementation Aspects

Textbox, Button

5.5.1.3.2 Emergency service

5.5.1.3.2.1 Input
Details

120
 5.5.1.3.2.2 Procedural Details
 Structured Chart

Emergency Service

Input Details Create Display

emergency req. successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

121
  Flow Chart

Start

Emergency Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.3.2.3 File I/O Interface

Emergency

5.5.1.3.2.4 Output

Display successful message.

5.5.1.3.2.5 Implementation Aspects

Textbox, Button

5.5.1.3.3 Check Facility

5.5.1.3.3.1 Input
Button-click

122
 5.5.1.3.3.2 Procedural Details
 Structured Chart

Check facility

Input button Retrieve all the Display

click facilities Information

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve all the facilities
Step4: Display information
Step5: Stop

 Flow Chart

Start

Input Details

Retrieve all the facilities

Display information

Stop

5.5.1.3.3.3 File I/O Interface

None

123
 5.5.1.3.3.4 Output
It will display the facilities provided by the apartment.
5.5.1.3.3.5 Implementation Aspect

Button

5.5.1.3.4 Report Issues

5.5.1.3.4.1 Input
User id, room no, issues.
5.5.1.3.4.2 Procedural Details
 Structured Chart

Report Issues

Input Details Display

Report issues
successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

124
  Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

 Flow Chart

Start

Issues Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

125
 5.5.1.3.4.3 File I/O Interface

Issues

5.5.1.3.4.4 Output

Display successful message.

5.5.1.3.4.5 Implementation Aspects

Textbox, Button

5.5.1.3.5 Pay Bill

5.5.1.3.5.1 Input
User id, Bill Type Amount.
5.5.1.3.5.2 Procedural Details
 Structured Chart

Pay Bill

Input Details Display

Verification
successful
message

Read inputs validation

Store to Display
database unsuccessful
message

126
  Algorithm
Step 1: Start
Step 2: Input Details
Step3: Validate the input
Step 4: If input is valid then
Stores data into the database
Display successful
Else
Display Unsuccessful message
Goto Step 2
End if
Step 5: Stop
 Flow chart

Start

Bill Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

127
 5.5.1.3.5.3 File I/O interface
Bill
5.5.1.3.5.4 Output
Display successful message.
5.5.1.3.5.5 Implementation aspects
buttons and textbox

5.5.1.3.6 My Profile

5.5.1.3.6.1 View

5.5.1.3.6.1.1 Input
Button-Click
5.5.1.3.6.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

128
  Flow Chart

Start

User Input Details

Retrieve data from the database

Display information

Stop

5.5.1.3.6.1.3 File I/O Interface

User

5.5.1.3.6.1.4 Output

Displays the user details.

5.5.1.3.6.1.5 Implementation Aspects

Button
5.5.1.3.6.2 Edit

5.5.1.3.6.2.1 Input
User name, Emil id, Phone no.

129
 5.5.1.3.6.2.2 Procedural Details
 Structured Chart

Edit

Input user Update user Display

information
Details Details

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input user details
Step3: Validate the input
Step4: If input is valid then
Update to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

130
  Flow Chart

Start

Input User Details

User

If input False Display error

Is valid message

True

Update to database

Display Successful

Stop

5.5.1.3.6.2.3 File I/O Interface

User

5.5.1.3.6.2.4 Output

It will update the user details

5.5.1.3.6.2.5 Implementation Aspects

Button, Textbox

5.5.1.3.7 Notification

5.5.1.3.7.1 View

5.5.1.3.7.1.1 Input
Button-Click

131
 5.5.1.3.7.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

 Flow Chart

Start

Notification Input Details

Retrieve data from the database

Display information

Stop

5.5.1.3.7.1.3 File I/O Interface

Notification

132
 5.5.1.3.7.1.4 Output

Displays notifications.

5.5.1.3.7.1.5 Implementation Aspects

Button

5.5.1.3.7.2 Delete
5.5.1.3.7.2.1 Input
Button-Click
5.5.1.3.7.2.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop

133
  Flow Chart

Start

Rooms Input Details

Retrieve Data from database

Delete Successful

Stop

5.5.1.3.7.2.3 File I/O Interface

Rooms

5.5.1.3.7.2.4 Output

Displays Successful

5.5.1.3.7.2.5 Implementation Aspects

Button

5.5.1.4 Guest
5.5.1.4.1 Registration
5.5.1.4.1.1 Input
username, password, email, first name, last name, adhar
no, phone no.

134
 5.5.1.4.1.2 Procedural Details
 Structured Chart

Registration

Input user Display

Verification
details successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input user details
Step3: Validate the input
Step4:If input is valid then
Display successfully registration done
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

135
  Flow chart

Start

Input user
details

Guest
Validation
Display error
message
If user not False
exist

True
Store to database

Display successful
message

Stop

5.5.1.4.1.3 File I/O interface

Guest
5.5.1.4.1.4 Output
Display successful message.
5.5.1.4.1.5 Implementation aspects
It requires buttons and textbox
5.5.1.4.2 Booking

5.5.1.4.2.1 Input
Location, check-in, check-out.

136
 5.5.1.4.2.2 Procedural Details
 Structured Chart

Booking

Input Details Display

Verification
successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

137
  Flow Chart

Start

Reservation Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.4.2.3 File I/O Interface

Reservation

5.5.1.4.2.4 Output

Display successful message.

5.5.1.4.2.5 Implementation Aspects

Textbox, Button

5.5.1.4.3 My Bookings
5.5.1.4.3.1 View
5.5.1.4.3.1.1 Input
Button-Click

138
 5.5.1.4.3.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

 Flow Chart

Start

Reservation Input Details

Retrieve data from the database

Display information

Stop

5.5.1.4.3.1.3 File I/O Interface

Reservation

139
 5.5.1.4.3.1.4 Output

Displays booking details.

5.5.1.4.3.1.5 Implementation Aspects

Button

5.5.1.4.3.2 Cancel
5.5.1.4.3.2.1 Input
Button-Click
5.5.1.4.3.2.2 Procedural Details
 Structured Chart

Cancel

Input button Retrieve the data

Cancel
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Cancel successful
Step5: Stop

140
  Flow Chart

Start

Reservation Input Details

Retrieve data from the database

Display information

Stop

5.5.1.4.3.2.3 File I/O Interface

Reservation

5.5.1.4.3.2.4 Output

Cancel successful.

5.5.1.4.3.2.5 Implementation Aspects

Button

5.5.1.4.4 Emergency service

5.5.1.4.4.1 Input
User id, room no, emergency type

141
 5.5.1.4.4.2 Procedural Details
 Structured Chart

Emergency Service

Input Details Create Display

emergency req. successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

142
  Flow Chart

Start

Emerg Input Details

ency

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.4.4.3 File I/O Interface

Emergency

5.5.1.4.4.4 Output

Display successful message.

5.5.1.4.4.5 Implementation Aspects

Textbox, Button

5.5.1.4.5 Check Facility

5.5.1.4.5.1 Input
Button-click

143
5.5.1.4.5.2 Procedural Details
 Structured Chart

Check facility

Input button Retrieve all the Display

click facilities Information

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve all the facilities
Step4: Display information
Step5: Stop

 Flow Chart

Start

Input Details

Retrieve all the facilities

Display Facilities

Stop

144
 5.5.1.4.5.3 File I/O Interface

None

5.5.1.4.5.4 Output

It will display the facilities provided by the apartment.

5.5.1.4.5.5 Implementation Aspect

Button

5.5.1.4.6 Report Issues

5.5.1.4.6.1 Input
User id, room no, issues.
5.5.1.4.6.2 Procedural Details
 Structured Chart

Report Issues

Input Details Display

Report issues
successful
message

Read inputs Validation

Store to Display
database unsuccessful
message

145
  Algorithm
Step1: Start
Step2: Input details
Step3: Validate the input
Step4: If input is valid then
Store to database
Display successful
Else
Display unsuccessful message
Goto step2
End if
Step5: Stop

 Flow Chart

Start

Issues Input Details

If input False Display error

Is valid message

True

Store to database

Display Successful

Stop

5.5.1.4.6.3 File I/O Interface

Issues

146
 5.5.1.4.6.4 Output
Display successful.
5.5.1.4.6.5 Implementation Aspects
Textbox, Button

5.5.1.4.7 My Profile

5.5.1.4.7.1 View

5.5.1.4.7.1.1 Input
Button-Click
5.5.1.4.7.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

147
  Flow Chart

Start

User Input Details

Retrieve data from the database

Display information

Stop

5.5.1.4.7.1.3 File I/O Interface

User

5.5.1.4.7.1.4 Output

Displays the user details.

5.5.1.4.7.1.5 Implementation Aspects

Button
5.5.1.4.7.2Edit

5.5.1.4.7.2.1 Input
Email-id, phone no, User name

148
 5.5.1.4.7.2.2 Procedural Details
 Structured Chart

Edit

Input user Update user Display

information
Details Details

Read inputs Validation

Store to Display
database unsuccessful
message

 Algorithm
Step1: Start
Step2: Input user details
Step3: Validate the input
Step4: If input is valid then
Update to database
Display successful
Else
Display error message
Goto step2
End if
Step5: Stop

149
  Flow Chart

Start

Input User Details

User

If input False Display error

Is valid message

True

Update to database

Display Successful

Stop

5.5.1.4.7.2.3 File I/O Interface

User

5.5.1.4.7.2.4 Output

It will update the user details

5.5.1.4.7.2.5 Implementation Aspects

Button, Textbox

5.5.1.4.8 Notification

5.5.1.4.8.1 View

5.5.1.4.8.1.1 Input
Button-Click

150
 5.5.1.4.8.1.2 Procedural Details
 Structured Chart

View

Input button Retrieve the data

Display
click from the Information
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display information
Step5: Stop

 Flow Chart

Start

Notification Input Details

Retrieve data from the database

Display information

Stop

5.5.1.4.8.1.3 File I/O Interface

Notification

151
 5.5.1.4.8.1.4 Output

Displays notifications.

5.5.1.4.8.1.5 Implementation Aspects

Button

5.5.1.4.8.2 Delete
5.5.1.4.8.2.1 Input
Button-Click
5.5.1.4.8.2.2 Procedural Details
 Structured Chart

Delete

Input button Retrieve the data

Display
click from the successful
database

 Algorithm
Step1: Start
Step2: Input button click
Step3: Retrieve information from the database
Step4: Display successful
Step5: Stop

152
  Flow Chart

Start

Notification
Input Details

Retrieve Data from database

Delete Successful

Stop

5.5.1.4.8.2.3 File I/O Interface

Notification

5.5.1.4.8.2.4 Output

Display successful

5.5.1.4.8.2.5 Implementation Aspects

Button

153
 6. USER INTERFACE

Welcome Page

Login Page

Registration Page

154
Registration Page for User

User Page after Login

Guest Page after Login

155
For User/Guest Emergency

Check User/Guest Facility

For User/Guest Report Issue

156
Pay Bill

User/Guest Profile

Notification for User/Guest

157
User/Guest Notification Delete

Check Availability of Rooms

Available Rooms

158
Room Booking

Booking details

159
 7. TESTING
7.1 Introduction
Testing is the major quality control measures and during the software
development it is used to detect errors that could have occurred during any of the
phase like requirement analysis, design, coding. The goal of the testing is to uncover
errors in the program.

7.2 Levels of Testing

Testing is done in different levels which includes the following.
 Unit Testing
 Integration Testing
 System testing
 Acceptance testing

 Unit Testing
In Unit testing each module gets tested during the
coding phase itself. The purpose is to exercise the
different parts of the module code to detect the coding
errors.
 Integration Testing
After new testing the modules are gradually integrated
into sub systems. It is performed to detect design errors
by focusing on testing the interconnection between
modules.
 System Testing
System is tested against the system requirement if all
the requirements are met and if the system performs as
specified by the requirement.
 Acceptance Testing
It is performed to demonstrate to the client on real life
data of the client, the operation of the system.

160
7.3 Test Case
It is the input that tests the genuineness of the program and
successful execution of the test case revels. That there are no errors in the program
that are under testing. It is a set of conditions or variables under which tester will
determine whether an application or software is working currently.

161
Test case ID 01

Title Login

Purpose Testing the login

Test data User Name and Password

Steps Step:1IF Username and Password is valid THEN

Step:2 IF User is Resident
Step 3: Redirect to Resident page
Step 4:ELSE Redirect to Guest Page
Step:5 ELSE DISPLAY Login Invalid Username or Password
Expected Invalid output:
output

Valid output: For User

Valid Output :For Guest

162
163
Test case ID 02

Title Forgot Password

Purpose To recover the password.

Test data Email Id

Steps 1.Click on forgot password

2.Enter the Email Id
3.Click on Submit button
4.IF Email is Valid All the detail regarding the Info is sent to
registered email id
5.Else User will not get a Email
Expected Invalid output
output Valid input:

164
165
Test case ID 03

Title Registration For Resident/User

Purpose To create and Account

Test data Email Id,, username, Room Number, Password, Confirm

Password, Phone Number , Aadhar Number, First Name,
Last Name

Steps 1.Click Register In Navigation Bar

2.Then click On User
3.Enter all the Information
4.Submit
5. If All Record are Valid Redirect to User page
6. Else User Name Already Exist message.
Expected Invalid output
output

Valid Output

166
Test case ID 04

Title Registration For Guest

Purpose To create and Account

Test data Email Id,, user name, Password, Confirm Password, Phone
Number, Aadhar Number, First Name, Last Name

Steps 1.Click Register In Navigation Bar

2.Then click On User
3.Enter all the Information
4.Submit
5. If All Record are Valid Redirect to User page
6. Else User Name Already Exist, and all fields must be filled
message.
Expected Invalid output
output

167
Valid Output

168
Test case ID 05

Title Emergency Form

Purpose Requesting for Emergency Services

Test data Room Number ,Emergency Type(Drop Down List)

Steps 1.If
If user is Logged in Click On Emergency Link in
Navigation Bar
2.Fill the Form
3.Submit
4. If All Fields are Valid
5.Sends the data to Admin Panel With your User ID
6. Else Fill Out the Form.
Expected Invalid output
output

Valid Output:

169
Test case ID 06

Title Report Form

Purpose Submitting for Emergency Services

Test data Room Number ,Issue

Steps 1.If user is Logged in Click On Emergency Link in Nav Bar

2.Fill the Form
3.Submit
4. If All Fields are Valid
5.Sends the data to Admin Panel With your User ID
6. Else Fill Out the Form.
Expected Invalid output
output

170
Valid Output:

171
Test case ID 07

Title Check Facility

Purpose Facility Provided to User/Resident

Test data Nill

Steps 1.If user is Logged in Click On Check Facility Link in

Navigation Bar
2.View the Facility
Expected Valid Output:
output

172
Test case ID 08

Title Check Facility

Purpose Facility Provided to Guest

Test data Nill

Steps 1.If
If user is Logged in Click On Check Facility Link in
Navigation Bar
2.View the Facility
Expected Valid Output:
output

173
Test case ID 09

Title Book Room

Purpose To Book the Room

Test data User name , check in, check out, person

Steps 1.If user is Logged in Click On Room Booking in Navigation

Bar
2.Fill All the details
3.Check Availability
4. If Room Are Available
5.Click on Book a Room
6.It will Redirect to Booking Page fill out the Details
7.Validate
8.Click on Book
9.Click on My bookings in home page It will show the all the
Bookings
10.Else No Room Are Available Message will be displayed
Expected
output

Valid Output:

174
175
176
Test case ID 10

Title Notification

Purpose TO send Notification to Users

Test data To User, Type(Message),Id, Message, From

Steps 1.If user is Logged in Click On Notification Icon in

Navigation Bar
2.View the Notification
Expected Valid Output:
output

177
Test case ID 11

Title Notification Delete

Purpose To Delete Notification

Test data Notification id

Steps 1.If user is Logged in Click On Notification Icon in

Navigation Bar
2.View the Notification
3.Click On Delete button to delete Notification
4.Delete Conformation page
5.Return to Home page
Expected Valid Output:
output

178
Test case ID 12

Title Pay Bill

Purpose Pay the Bill

Test data Type ,Amount ,Room Number

Steps 1.If user is Logged in Click On Pay Bill in Navigation Bar

2.Enter all the Information
3.Submit
4. If All fields are filled It will send the information to admin
with user id
5. Else all fields must be filled message.
Expected Invalid Output:
output

Valid Output:

179
180
Test Case ID 13

Title Cancel Bookings

Purpose To cancel the booking

Test data Booking id

Steps 1.IF User Booked the Room

2.Click on Cancel Button in My bookings
3.It will ask conformation Then Cancel the booking
4. Else No Booking Found.
Expected Invalid output
output

Valid Output:

181
 8. FUTURE SCOPE
User can book a room and also he can see the booking information, can receive
notification from the admin.

182
 9. BIBLIOGRAPHY

 Textbook referred
o Integrated approach to software Engineering
-Pankaj Jalote
 www.javapoint.com
 www.stackoverflow.com

183