Indira College of Commerce and

Science

Online Housing Society Management System

TY BSC COMPUTER SCIENCE (2019-2020)

Submitted by:

1. Akshta Ajit Jadhav(A-09)

2. Preksha Sudama Bodele(A-48)

ACKNOWLEDGEMENT
The success and final outcome of this project required a lot of guidance and
assistance from many people and we are extremely privileged to have got this
all along the completion of our project. All that we have done is only due to
such supervision and assistance and we would not forget to thank them.

We respect and thank Mrs. Kavita Dhakad and Mrs. Manisha Patil, for
providing us an opportunity to do the project work and give us all support and
guidance which made us complete the project duty. We are extremely thankful
to them for providing such a good support and guidance.

A special thanks to Dr. Janardan Pawar for his help and providing us ample IT
Services. We wish to record our appreciation to all our friends and others who
helped us throughout the project work directly or indirectly.

We owe a deep gratitude to our project guides for taking keen interest on our
project work and guiding us all along, till the completion of our project work by
providing all the necessary information for developing a good system.

We are thankful to and fortunate enough to get constant encouragement,

support and guidance from all teaching staff which helped us in successfully
completing our project work. Also, we would like to extend our sincere
esteems to all staff in laboratory for their timely support.
INDEX

Sr no. Index Page no.

1 Introduction to the System

1) Problem Definition
2) Scope of the system
3) Advantages and Disadvantages
2 System Analysis
1) Requirement Analysis
2) H/W and S/W Requirement
3) Feasibility Study
4) ER Diagram
5) Data Dictionary
3 System Design
1) Use Case Diagram
2) Class Diagram
3) Object Diagram
4) State Chart Diagram
5) Activity Diagram
6) Sequence Diagram
7) Collaboration Diagram
8) Deployment Diagram
9) Component Diagram
4 User Manual
1) Operational Instructions
2) Input Screens
3) Output Screens
4) Reports
5 Future Enhancement

6 Conclusion

7 Bibliography
 Introduction to the System

Problem Definition :

The purpose of this system is to develop with high priority in removing the
flaws and eliminate majority of errors prone situation of manual working. It
focuses on providing user friendly interface so the user can interact with system
with easy with bunch of options to maintain the database and retrieve
the information based on circumstances. Notifications proves to be
pivotal point in this system as proper ad appropriate message has been
conveyed to the localities without failures. No loss of records has been
assured up to some extent. It also provides the facilities to secretary to
view the information of the residents along with sending notification in
case of maintenance amount is pending or any of the matter of
inconvenience.

Scope of the System :

 This system aims to reduce the errors conducted during the day to day
working in the society.
 It addresses the way to store the data in database to retrieve and reduce
the chances of losing data.
 Secured access to the system and more authentication to the secretary,
because of the host of required information about the society members
along with information about the family members except the username
and passwords which is totally confined to the owner itself and not to
secretary.
 The proposed system will help maintaining owner details.
 Charges are calculated by the system.
Advantages and Disadvantages of the System

Advantages to proposed system

1. GUI - The proposed system provides better graphical user interface.
2. Search - Searching any detail about Owner made easy.
3. Increase work Speed - Due to automation of some part of system the
work speed would increase.
4. Less paper work - For proposed system less paper work is needed.
5. Reduces error - Due to computerization there is less possibility of errors.
6. Economical - Due to less errors and less work delay proposed system can
be economically beneficial to the organization

Disadvantages of existing System:

1. It is manual and time consuming.
2. It utilizes a large amount of space to store Owner and Society information
on paper files.
3. Sometimes manual calculations may be incorrect, thus leading to
incorrect information.
H/W and S/W Requirements:

1) Hardware Requirements
Client side
Ram 512 MB
Hard disk 10 GB
Processor 1.0 GHz

Server side
Ram 1GB
Hard disk 20 GB
Processor 2.0 GHz

2) Software Requirements
Client side
Web Browser Internet Explorer 6 or any compatible
Brower
Operating System Windows or any equivalent OS

Server side

Apache Tomcat Web Server

Postgres Database Server
HTML, Java, Javascript Programming Language
Firefox, Google Chrome Web Browser
Linux Operating System
FEASIBILITY STUDY

ECONOMIC FEASIBILITY
It helps the organizations determine the cost, viability and benefits associated
with a project before financial resources are allocated. It involves a
cost/benefits analysis of project. Cost Efficient Facilities provided with very
low cost

 Onetime payment of Software

 Less maintenance
 Less equipment required i.e. only Computer, Printer, etc.

OPERATIONAL FEASIBILITY
Following operational feasibilities have been encountered in project The
system development will be very useful in case of user and developer.

 The system will easily comply with user demand and use.
 The system performance will be better and user friendly.

TECHNICAL FEASIBILITY
 It helps organizations determine whether the technical resources meet
capacity and the technical team is capable of converting the ideas into
working system. The technical knowledge required to use proposed
system are basics of using computer & its peripherals The proposed
system is capable of expression.
 The proposed system will provide adequate accuracy.
 The proposed system will have data security.
Entity Relationship Diagram
 Data Dictionary
Schema |           Name           |   Type   |  Owner  
--------+--------------------------+----------+----------
 public | admin                    | table    | postgres
 public | charges                  | table    | postgres
 public | feedback               | table    | postgres
 public | owner                     | table    | postgres
 public | owner_payable      | table    | postgres
 
  Table admin

  Column   | Type | Modifiers

------------+----------+-----------
 admin_id   | text | not null
 admin_pwd  | text | not null
 admin_name | text | not null

Table charges

 Column   |       Type       | Modifiers

------------+------------------+-----------
 one_bhk    | double precision |
 two_bhk    | double precision |
 three_bhk  | double precision |
 parking    | double precision |
 event_fund | double precision |
 sink_fund  | double precision |

   Table feedback
    Column     |  Type   |                           Modifiers                        
  
---------------+---------+-------------------------------------------------------------

Table Owner
 Column      |  Type   |                        Modifiers                        
-----------------+---------+----------------------------------------------------------
 owner_id         | integer | not null
 owner_pwd       | text    | not null
 owner_name      | text    | not null
 owner_gender    | text    | not null
 owner_dob       | date    |
 owner_mobile    | text    |
 owner_email     | text    |
 owner_blg       | text    |
 owner_flat_no   | text    |
 owner_flat_type | text    |

Table owner_payable

Column    |       Type       | Modifiers

--------------+------------------+-----------
 amt_payable  | double precision |
 date_payable | date             |
 status       | text             |
 owner_id     | integer           |
System Design

1.Use case Diagram

2.Class Diagram
3.Object Diagram
4. State Chart Diagram

A. For Admin
b. For Owner
5. Activity Diagram

A. For Admin

.
B. For Owner
6. Sequence Diagram
7. Collabration Diagram

8. Deployment Diagram
9. Component Diagram
User Manual
Operational Instructions
You will need access to the internet and a web browser like Firefox, Chrome,
Opera etc.
User has to Register to the system as a new user.
Types of users:

1) Admin
 You can login as admin, to login you have to enter valid username
and password.
 After login you can add the Society members.
 You can add Charges and Edit member details.
 You can edit charges.
 You can view feedback given particular member of society.
 Now you can log out successfully.

2) Owner
 You can login as owner, to login you have to enter valid user id
and password provided by admin.
 After login owner can change its password.
 Owner can view the Maintainance Bill generated by admin.
 He can give a Feedback about the society to the admin.
 Now he can now logout from the system.

Input and Output Screens

A. For Admin
1. Login Page

2. Home Page
3. Add Member

4. Add Charges

5. Edit Member Details

6.Calculate Maintenance

7. View Feedback
 B. For Owner

1.Login Page

2.HomePage
3. View Profile

4. View Bill
5.Feedback

6. Feedback Sent
Future Enhancement

 This software can be integrated with various other programming

languages to overcome the limitations of the current system.
 Ease of navigation between forms could be increased.
 As per requirement the modifications and changes can be done.
 Option for more versatile and informative reports could be
included.
 Option could be given to customer to choose between vendors.
 Admin could fix their charges for the society.
 Admin could set the payment status.

Conclusion
 The objective of the project was to build a software programfor
maintaining the details of all the end users such as – admin,
Owner, Feedback, Charges, owner payment.
 The system developed is able to meet all the basic requirements.
The management of maintenance of all the records of the end
users will also be benefited by the proposed system, as it will
automate the whole process in-turn reducing the work load.
 The security of the system is also a prime concern.
 There is always a room for improvement in any software project,
however efficient the system may be.
 The important thing is that the system should be flexible enough
for future modifications.
 The system has been factored into different modules to make the
system adapt to the future changes.
 Every effort has been made to make the system user friendly.

Bibliography

Search Engine – www.google.com

Web sites:
1) https://www.w3schools.com/sql/
2) https://www.w3schools.com/JAVA/default.asp
3) https://examples.javacodegeeks.com/java-
basics/exceptions/java-lang-stackoverflowerror-how-to-solve-
stackoverflowerror/
4) https://www.geeksforgeeks.org/java-tutorials/