Housing Society Management System project in Php and MYSQL

HOUSING SOCIETY AND MANAGEMENT SYSTEM Project in PHP and MYSQL

Note: Errors are not tested. So T4Tutorials is not responsible for any mistake in this SRS document.

CONTENTS

CHAPTER 01: INTRODUCTION

CHAPTER 02: REQUIREMENT ANALYSIS

CHAPTER 03: DESIGN

CHAPTER 04 : TESTING

CHAPTER 05: CONCLUSION

 
TABLE OF CONTENTS
CONTENTS PAGE
LIST OF TABLES, FIGURES, AND APPENDIXES ———————-

ABSTRACT ——————————————————————–

CHAPTER 01: INTRODUCTION ——————————————–

1.1 Research Objectives —————————————————

1.2 Research Questions —————————————————CHAPTER 02: REQUIREMENT ANALYSIS ——————————

2.1 Sub-Heading 01———————————————————–

2.2 Sub-Heading 02———————————————————-

2.3 Sub-Heading 03———————————————————-

CHAPTER 03: DESIGN —————————

3.1Data Source and Collection —————————————————

3.2 Statistical Analysis —————————————————-

3.3 Anti Plagiarism Test ———————————————————–

CHAPTER 04: TESTING ————————–

4.1 Sub-Heading 01————————————————— ————

4.2 Sub-Heading 01—————————- ——————————–

4.3 Sub-Heading 01———————————————————– —-

CHAPTER 05: CONCLUSION & FUTURE WORK

USER MANUAL ————————————————————–

REFERENCES —————————————————————–

APPENDIXES ——————————————————————

VIII

1

2

5

5

6

7

8

12

13

14

15

17

17

17

18

19

19

69

99

104

 
LIST OF TABLES, FIGURES, AND APPENDIXES
CONTENTS PAGE
TABLE-01: Heading ——————————————————————

TABLE-02: Heading ——————————————————————

FIGURE-01: Heading——————————————————————

FIGURE-02: Heading —————————————————————-

APPENDIX-01: Heading —————————————————–

100

100

102

102

102

 

CHAPTER 1

INTRODUCTION

CHAPTER-1

INTRODUCTION

Introduction

In Pakistan, Societies business booming exponentially. But, to run a business successfully, without a proper solution is close to impossible. Existing systems in the market are either too expensive or do not meet the requirements.

Online Housing Society is a Web-based used to provide guidance to the customers to choose plots according to their needs. It also helps customers to book their desired plots at reasonable rates. This Web based application also helps their customers for booking plots in installments. It is time to take advantage of the technology for a better and peaceful living.

    1. Background and Existing System
      1. Problems in Existing System

Societies using different software for booking of plot, Installment, Billing, and Accounting. Different system integration always remains a big challenge.

    1. Proposed System

Accurate data and information are key for Societies business. Therefore, we would be designing one solution that would be pre-integrated for all systems. The system would be flexible to configure and accurate information would be ensured via best architecture.

Main Modules

Cover main modules of the proposed system.

ADMIN

CUSTOMER

    1. Expected Outcome

We have developed the project according to our objectives. This project enables both admin and user with controlled functionalities. And these functionalities are in working condition.

Tools & Technology

We will use different software for the development of this system, which is given as

  1. Microsoft Visual Studio
  2. SQL Server
  3. Microsoft Visio
  4. Woo Commerce
    1. Activity Index

Schedule all the deliverables accordingly

No. Activity Duration Deliverables
       
       
       
       

CHAPTER 2

REQUIREMENT ANALYSIS

CHAPTER-2

REQUIREMENT ANALYSIS

2.1 Requirement Analysis

Provide analysis of proposed systems requirements

2.1 Functional Requirements

List all functional requirements of proposed system

2.1.1 Admin:

Admin can manage full system.

Admin can create detail of society and detail of houses of that society.

Admin can assign the house to a member.

Admin can create username and password for the member.

Admin can manage master data.

  • Blocks
  • Upfront Payments
  • Plots

2.1.2 Functionality of Member/Customer:

The customer can search the property.

The customer can use bidding for the commercial plots.

The customer can book the property.

The customer can pay via cash or card.

The customer can also pay in installments.

The customer can maintain his profile.

The customer can cancel his/her file.

The customer can transfer his/her file.

Customer providing personal data such as

  1. Create Customer
  2. First name
  3. Last name
  4. Email Address
  5. Password
  6. Contact Info

2.1.3 User:

This user is a visitor, who can only view the system and can perform the following steps:

The user can visit the website.

The user can search the property.

The user can also buy the property if he is interested in registered himself.

2.1.4 Plot Registration: To register plots in society this web application allows users to register plots. Following are the steps

  1. Plots Sizes
  2. Rates
  3. Ownerships
  4. Register Plots

Yes/No

2.1.5 Search: People can easily search and find the plots. The customer can search the plot according to his desired requirements. Plots can be searched by using these constraints such as

1. Plot Size

2. Plot Type

3. Plot Rates

2.1.6 Booking: Booking facility is also given to a user to book their property. After booking any property that property is reserved for a specific person. It will be reserved for further processing for a specific time.

2.1.7 Installments and Billing: If a member wants to pay in installments then he has to pay the down payments first. If a member can’t afford to pay fully in cash then he can pay the money in installments. We provide this facility to the user; so he can ease himself by paying the payment in installments.

2.1.8Receivables: Record of the installments will be maintained in receivables.

2.1.9File Transfer: Member can also transfer their plots to someone but if he is not already registered then he has to first register himself. We provide this facility so if a person has an issue while paying the rest of amount, then he can transfer this file. Then the rest of amount will be paid by the new owner of the property. This functionality is only for the user who will buy property in installments.

2.1.10 File Cancel: If a member is having some financial issues then he can cancel the plot. Member will have the ease to cancel his file but his registration fee and 10% will be deducted from his paid amount.

2.1.11Accounts: Accounts will be managed by admin in this functionality. People who pay the full payment and people who pay in installments will be managed in this section.

2.1.12 Maintain Record: The Online Housing Society Web-based app provides facilities to their customers to maintain their records.Customers record will be maintained properly by admin.

The customer can update his profile.

  1. Update
  2. Delete
  3. Insert

2.1.15 Comments: Commenting features is also included in to comment customers and sharing their views about plots if anyone wants to book someone’s plot then they can negotiate.

2.2.2 Non- Functional Requirements

List all non-functional requirements of proposed system

2.2.2.1 Availability: The system should be available 24 hours a day and 7 days a week. Customer will have the ease to use the system whenever he needs.

2.2.2.2 Reliability: The system should be reliable and efficient.

The system shall have 99% reliability during the operating hours.

The system shall generate error messages when the user attempts to enter the invalid data.

2.2.2.3 Performance: The system should provide high performance

  • The respond time for managing the settings, viewing reports, inserting and updating should be no more than few seconds.
  • The system should provide information to any user.
  • The system should be able to serve 100 users at a time.

2.2.2.4 User-Friendly: The system should provide a good user interface. Such Options must be created so that can help the users.

 

2.2.2.5 Maintainability: The system should be easy to maintain by administrators. The system’s database should be back up every week. After certain of time, the system should be added a new function, new features so that it can provide user good qualities.

2.2.2.6 Security: The system should protect itself from external attacks that may be accidental or deliberate such as viruses, unauthorized use of system services, unauthorized use of system services, unauthorized modification of the system or its data. All customers’ account information must be stored in the system’s database. Only the database administrators have direct access to the database for making any change related to the database and for maintenance purposes

2.2. Use Case Diagram

As use case is an important part that splits our SRS document into more particular SRS documents which integrate to cover all the functional requirements of our system.

Here we have three (3), actors

  1. Admin
  2. Customer
  3. Visitor

2.3. Use Cases

A customer is basically a person who will register himself if he is interested in buying a property after a search. After that, he will be able to use the other functionalities. Admin will make check and balance upon records. In this customer will first fill a built-in form to get registered after searching a property. Then they will select the method whether it will be through full payment or through installments. Customer will be also able to transfer this file if he is not able to pay his due installments. The customer can also cancel the file if he is not able to pay the remaining dues but registration fees and 10% of down payment will be deducted.

Admin will login in the system.Admin will manage the main functions. Admin will allocate the plots to the customers. Admin will manage the blocks like add, delete and update of blocks. Admin will be able to maintain all the records of the customer regarding installments and profile.

 

CHAPTER 3

DESIGN

CHAPTER-3

DESIGN

3.1 UML Diagrams

We use UML(Unified modeling language) diagram to make our system`s blueprint.We use it to make models of our system.

3.1.1 Class Diagram

Explaining Diagram:

The class diagram is considered to be an important building material in the development of the project (any). It describes the structure of a system by showing the system’s classes, their attributes, operations (or methods), and the relationships among objects.

In our project class diagram, we added some relationships with another attitude that are working accordingly in our project.

We created classes named as Admin, Customer, Plot, Records, File Transfer and File Cancel also describes their relationship among them.

The classes with the sign + shows the Functions and sign – shows the attributes of the classes. For example, Admin has a + sign and its attributes are like login, signup, email, name, passwords etc.

Then we defined their relationships among them. It is obvious that Admin is controlling the whole project so that he has a relationship with every class.

Admin can create Customers. So admin have one to many relations with customers whereas customer can visit and books many plots so customer have one to many and many to many relations with plot booking and plot searching. Therefore admin can update the records of customers so he has also one to many relations with record class. Thus this is the basic working of class diagram.

3.1.2 Sequence Diagram

18741196_448302755533246_1778273829_n

Explaining Diagram:

In above Sequence diagram, we have following major attributes

  • Customer
  • Admin
  • Plots
  • Plots booking
  • Customer database
  1. First of all the Customer is registered is by Admin in such a way that customer fill ups the basic data such as name, password, address, phone number etc. and all those data is accepted by Admin and thus customer register himself.
  2. Now the customer can search , visit and book the plot by which all the data is sent to the admin panel.
  3. If the customer books for the plot then all the regarding information is provided by the Admin. For example, if the plot is booked then k information about payment method and installments are shown to the customer by Admin.
  4. Then there comes a plot. There comes a variety of plots including Residential and Commercial plots. We provided a facility to our customer to visit every plot and if he is willing then he just click the Book button for booking a plot.
  5. At the end, all the records are saved in the Customer database in which the whole record of down payments and installments and remaining installment are provided by the Admin.

3.1.3 Architecture Diagram

Presentation Data Access

Business

Model DAO

Controller

Http Request

Http Response View

Database

Defining Diagram:

A graphical architecture is basically a graphical representation of the concepts, their principles, elements, and components that are part of your architecture.

In our project, there are three basic elements that we used

  • Presentation
  • Data Access
  • Business
  1. First, it comes the presentation of your project which defines how does your project look like. It can consist of visual concepts such as web pages or reports.
  2. Data Access is the layer where which defines how the data is accessed throughout in our project. It includes input and output commands and their processing method. How query is accessed and how does its processing take place this all includes in data access layer.
  3. The business logic layer, on the other hand, represents the business rules that are enforced via programming logic (computer instructions) regarding how those rules are applied.

In above diagram, it clearly defines the architecture of a system in which https request for something and then processing takes place in the controller and then it further goes in a model that is holding the information in a database and then at the end the view function gets the requested data and displays to https.

Activity Diagram

An activity diagram is another important diagram in UML to describe the dynamic aspects of the system.An activity diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. The control flow is drawn from one operation to another.

Activity diagram for Admin

Activity diagram for Customer

CHAPTER 4

TESTING

CHAPTER-4

TESTING

4.1 Testing

4.1.1 Forms attempting validation

4.1.2 Admin Panel

4.1.3 Customer Panel

      1. Evaluation forms attempting validation

Test Case Title

Test Engineer: Group members
Test Case ID: TC1
Related UC/FR/NFR UC1/FR1/NFR1
Date: 12-7-2017
Purpose: For valid outcome, and restriction to fill every form (Login, Signup,)
Pre-Req: Customer will, first of all, enter his credentials in order to get himself registered with the system.
Test Data: Foam consisting of different variable and data are tested in this test case.

A customer cannot leave a field empty.

Steps: Steps to carry out the test. See step formatting rules below.

  1. Visit Housing Society and Management System(HSMS) official website.
  2. click the link for evaluation
  3. Enter Customer name ( Required ).
  4. Enter Email ( Required )
  5. Enter Password ( Required )
  6. Enter Phone ( Required )
  7. Submit
Status: Pass
      1. Testing of Admin Panel

Test Case Title

Test Engineer: Group members
Test Case ID: TC1
Related UC/FR/NFR UC1/FR1/NFR1
Date: 12-7-2017
Purpose: To check everything is in order because Admin has all authority.
Pre-Req: First an Admin must be logged in to the system. (Required)
Test Data: Every data and variables related to admin panel are used in this testing. The Following major components

  • Add Property
  • Plot Allocation
  • Manage Blocks
  • Maintain Records
Steps:
  1. Login, (required).
  2. Admin will add plots(Optional)
  3. Admin will Allocate Plots(Optional)
  4. Admin will manage blocks(Optional)
  5. Admin will maintain (Optional)
  6. Submit
Status: Pass
      1. Testing of Customer Panel

Test Case Title

Test Engineer: Group members
Test Case ID: TC1
Related UC/FR/NFR UC1/FR1/NFR1
Date: 12-7-2017
Purpose: To check the availability of functionalities for a customer.
Pre-Req: First a user must have to Register and Login (Required).
Test Data: Every data and variables related to Customer panel are used in this testing. The Following major components:

  • Property Search
  • Property Book
  • Plot Registration
  • File Transfer
  • File Cancel
Steps:
  1. Login, Register (required).
  2. Customer will search the Property(optional)
  3. Customer will book the Property(optional)
  4. Admin will approve the booking request(optional)
  5. The Plot will be allocated to the customer(optional)
  6. Customer can pay full payment(optional)
  7. Customer also can pay in installments(optional)
  8. Customer can transfer his file(if required)
  9. Customer can cancel his file(if required)
  10. Submit
Status: Pass
 

CHAPTER 5

CONCLUSION &

FUTURE WORK

CHAPTER-5

CONCLUSION & FUTURE WORK

In the previous method of Housing Society Management System, there is a lot of paperwork to keep the whole records that become very difficult to integrate the system.

There is such system that does not meet the basic requirements of the customers and also they do not provide facility to the admin to manage records.

We provided such features in our project that can easily integrate the whole system by keeping their records and the admin can handle the whole process through himself.

As with the passage of time things change. In near future, their might be some kind of changes happens like online payment transaction and some further integration of different modules on a single platform.

USER MANUAL

USER MANUAL

User Manual

    1. Screen Shot I

    1. Screen Shot II

    1. Screen Shot III

REFERENCES

APPENDICES(Font 14, All Caps)

This section may contain the supporting data for the text. It shall include, questionnaire/data collection sheet(s), illustration, maps, figures or any supporting table.