Property Management System. Department of Computer Science & Information Technology. University of Sargodha. Version1.0

Transcription

1 Property Management System Date:March 9,2018 Department of Computer Science & Information Technology University of Sargodha Property Management System Version1.0 IT-HUB Sargodha. 1

2 Contents CHAPTER 1: FINAL PROJECT PROPOSAL INTRODUCTION PROJECT TITLE: PROJECT OVERVIEW STATEMENT: PROJECT GOALS & OBJECTIVES: LIST OF OPTIONAL FUNCTION UNITS HIGH-LEVEL SYSTEM COMPONENTS: EXCLUSIONS: APPLICATION ARCHITECTURE: GANTT CHART: HARDWARE AND SOFTWARE SPECIFICATION: Hardware and Software Requirements: Hardware Specification: TOOLS AND TECHNOLOGIES USED WITH REASONING: Front-End /Back-End technologies Tools... 8 CHAPTER 2: FIRST DELIVERABLE INTRODUCTION PROJECT/PRODUCT FEASIBILITY REPORT Technical Feasibility Operational Feasibility Economic Feasibility Schedule Feasibility Specification Feasibility Information Feasibility Motivational Feasibility Legal & Ethical Feasibility PROJECT/PRODUCT SCOPE PROJECT/PRODUCT COSTING TASK DEPENDENCY TABLE CPM - CRITICAL PATH METHOD GANTT CHART INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET TASK AND MEMBER ASSIGNMENT TABLE TOOLS AND TECHNOLOGY WITH REASONING VISION DOCUMENT RISK LIST PRODUCT FEATURES/ PRODUCT DECOMPOSITION.16 CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED APPROACH.17 2

3 3.1 INTRODUCTION: EXISITING SYSTEM ORGANIZATIONAL CHART SCOPE OF THE SYSTEM SUMMARY OF REQUIREMENTS (INITIAL REQUIREMENTS ) EXTERNAL ENTITIES CAPTURE SHALL STATEMENT ALLOCATE REQUIREMENTS PRIORITIES REQUIREMENTS REUQUIREMENTS TRACEABILITY MATRIX HIGH LEVEL USECASE DIAGRAM ANALYSIS LEVEL USE CASE DIAGRAM USECASE DESCRIPTION..24 CHAPTER 4: THIRD DELIVERABLE FOR OBJECT ORIENTED APPROACH DOMAIN MODEL SYSTEM SEQUENCE DIAGRAM COLLABORATION DIAGRA.M DESIGN CLASS DIAGRAM STATE CHART DIAGRAM DATA MODEL..32 Table of Figure Figure 1 Application architecture... 7 Figure 2 Gantt chart... 7 Figure 3Network Diagram.13 Figure 4 Gantt chart...15 Figure 5 Organizational chart 18 Figure 6 High level Use case diagram...22 Figure 7Analysis Level diagram 21 Figure 8 Domain Model.27 Figure 9 System Sequence Diagram..28 Figure 10 Collaboration Diagram..29 Figure 11 Design class diagram.30 Figure 12 State Transition diagram 31 Figure 13 Data Model 32 3

4 Chapter 1: Final Project Proposal 1.1 Introduction Successful property management system promotes property dealing and maintains all records regarding to this, sell and property, Renting property, Collects rent and payment. Efficient and effective management of property dealing is an increasingly imperative for business sustainability and competitiveness. The property management system is a complex process. It consists of various operations, including: 1. Management of buying property. 2. Management of the selling property 3. Management of accounts. 4. Leases and tenant management. 5. Management of rent amount and payment status. 6. Expenses and cost measurement. 7. Management of legal and security issues. 8. Management information of and Admins. Currently, many organizations use a manual system. The existing system leads to many errors like data redundancy, data inconsistency, more paper work that wastes valuable time and money. Followings are some other disadvantages: 1. Maintenance of personal information and information about properties are difficult and time consuming. 2. The files and shelves occupy a lot of physical space. 3. It includes lot of paper work that may cause data redundancy. 4. Documents may be misplaced and lost. 5. Searching and maintaining process of properties record is complicated and slow. Keeping these limitations in mind, we aim to develop a user friendly property Management System which will provide a graceful solution to the above mentioned problems Project Title: Property Management System 1.3. Project Overview statement: Project Title: Property Management System Project Manager: Sir Muntazir Mehdi Project Members: Name Registration # Address Signature Ume Amara Umeamara790@yahoo.com Project Goal: To develop a property management system that provides effective and transparent functionalities for managing all the dealings between property dealer and customers regarding to the property. And to make an effectual system that keeps all record of selling, buying, renting and existing property. 4

5 Objectives: To develop an effective and transparent property management system for achieving following objectives: Sr. # 1 Time effective and cost effective. 2 To provide a complete information for Admin and customers. 3 To.provide regular detailed and accurate accounting reports 4 To maintain the tenant s records and information. 5 To keep record of available property utilization. 6 To manage the accounts of payment, Expenses, leases and rents. 7 To maintain record of selling and purchased property. Project Success criteria: 1 Adaptability: The system should be able to adjust to new conditions. 2 Availability: The system ensures 24/7 availability. 3 Reliability: The system functions according to the stated conditions. All transactions perform successfully. 4 Response time: The system must have a fast response time. 5 Usability: The system provides ease of use, effectiveness, efficiency, learnability and an overall users satisfaction. Assumptions, Risks and Obstacles: 1 It is assumed that the team members will cooperate and work seriously on this project. 2 It is assumed The users who are not familiar with these tools would face difficulty to use the system. 3 Users will require special training how to use the functionalities of the system. It is also assumed that administrators/managers will require more training. 4 Willingness, cooperation, and support of all executive level management would be required from 5 requirement engineering to deployment phase. Lack of Willingness, cooperation, and support of all executive level management can lead to an unfinished system. 6 IT infrastructure with proper hardware and high speed Internet connectivity would be required for the effective and successful deployment and running of the system. A slow internet would restrain the accessibility, performance and functioning of the system. 7 Time, technical expertise & budget constrains may introduce serious obstacles towards the completion of the project. Organization Address (if any): It-Hub 113/stadium road Sargodha Type of project: Research Development Target End users: Property Dealers and landlords. Development Technology: Object Oriented Structured Platform: Web based Distributed Desktop based Setup Configurations Other Approved By: Sir Muntzair Mehdi Date:

6 1.4. Project Goals & Objectives: Goals: To develop a property management system that provides effective and transparent functionalities for managing all the dealings between property dealer and customers regarding to the property. And to make an effectual system that keeps all record of selling, buying, renting and existing property Objectives: To develop an effective and transparent property management system for achieving following objectives: 1. To manage property order according to customer s requirements. 2. To provide a complete information for Admin and customers. 3. To provide regular detailed and accurate accounting reports. 4. To maintain the tenant s records and information. 5. To maintain registered customer's personal information. 6. To keep record of available personal property utilization. 7. To manage the accounts of payment, Expenses, leases and rents. 8. To maintain record of selling and buying property High-level system components: 1. Admin registration and login is important for a secure system. 2. Admin add new property with its status either it is for selling, buying or renting. and manage record all type of property with client and property information. 3. Personal property management. 4 Manage Record of renting property. 5. Add Leases and manage Tenants record. 6. Add property repairs Expenses all that amount that is used for selling and purchased property and advertisement etc. all these with their title and expense amount is recorded in Expense table. with their title and expense amount is recorded in Expense table. 7. Generate reports of monthly and yearly profit and loss. 8. Add payments and make record with their status. How many payments are receive or pending Provides the ability to store easement and encumbrance information related to leases or properties, and where needed account for them (payments, etc.). 9. Add and subtract amounts from accounts, account management will help out to generate reports List of optional functional units: 1. Videos of property location can make it easier for clients they can see the property and its location without site visit. 2. Legal investigation of property either the property that is available for sell, buy and renting is personal asset of the client 3. Design and photography services can be add for clients and easier to select a Property according to their wish. Accounting system can be made with complete trail balance, general and ledger. than it an enterprise application. 6

7 1.7. Exclusions: A complete accounting system can be include Application Architecture: 3 Tier Architecture is being used in our system. Figure 1 Application architecture 1.9. Gantt chart: Figure 2 Gantt chart Hardware and Software Specification: Hardware and Software Requirements: 1 Operating System: Windows 10 2 Front End: HTML5, CSS3, JavaScript, Bootstrap, JQuery 3 Back End: WAMP Server, MySQL, PHP 4 Languages Used: PHP Hardware Specification: 1 Processor: x86 compatible processor 2 RAM: 512 MB or greater 3 Hard Disk: 20 GB or greater 7

8 4 Keyboard: 104 keys standard 5 Mouse: 2/3 button. Optical/ Mechanical Tools and technologies used with reasoning: Front-End /Back-End technologies Front-End: HTML It is used to generate web pages. HTML, an initialize of Hypertext Markup Language, is the predominant markup language for web pages. It provides the means to describe the structure of text based information in a document by denoting certain text as headings, paragraphs, list and so on JAVASCRIPT It is used for checking User information before sending to JavaScript. It is a scripting language most often used for client side web development. It is a dynamic, weakly typed, prototype based language with a lot of functions CSS CSS is used to design for front end designing. With the help of CSS we can make our webpages more attractive and good Back-End: My SQL My SQL is used to access the database. SQL stands for structured query language and is used to perform different operations on the data stored in database PHP PHP is a technology that lets you mix regular, static HTML with dynamic generated HTML. PHP receive any process request from HTML and give the result to HTML after processing to show the result Tools 1 Adobe Dreamweaver 2 XAMPP 3 Google chrome 8

9 Chapter 2: First Deliverable 2.1. Project/Product Feasibility Report There are many types of feasibilities: 1. Technical 2. Operational 3. Economic 4. Schedule 5. Specification 6. Information 7. Motivational 8. Legal and Ethical Technical Feasibility As the project is property management system having three tier architecture with client, server and database to maintain the saved data. PHP is backend server language to respond all the HTML requests from the user using all these platforms this project is possible and it is technically feasible. In property management system we are using: These languages having the capability to done all the operations applied or used in our project Operational Feasibility Property management system makes it easy to manage the record of Property. This system is used by the admin of the property database administrator will manage all the data of the database. This system will ease all the mentioned above user and gather on a single platform to interact with system and reduce the burden of all the manual Economic Feasibility The economic perspective of any project plays important role in its completion. It is affordable for a company. In economic feasibility we discuss two features. Cost Estimate We define cost estimate with the help of functional point. We define cost estimate with the help of Function Point Analysis. Those benefit which focus on reduced cost and are responsible for increase in the revenue. 1 Reduced costs 2 Increased revenue 3 Intangible benefit Information quality and job satisfaction are example of intangible benefits. Cost required in our project depends upon scope of our project. When scope of project increases cost also increases. Cost depends upon our hardware configuration, software required in our project and team member skills cost Schedule Feasibility Our project will be completed within 1 month. As we planned all the development phases of the projects very carefully, like requirement phase will be completed within 5 days etc. 9

10 Specification Feasibility All requirements are completed within time. All requirements are clear. We have no Confusion to understand these requirements. New requirement are implemented within time. All Requirements are the features that our system must have or a constraint that must be accepted for end users. Specification feasibility also included hardware and software specification required for completion of our project Information Feasibility Our system contents are as much clearer that a common person can understand it. Complete information about the products are here all the terms of buying and selling are clear Motivational Feasibility Evaluation of the client staff regarding the motivation to perform the necessary steps correctly and promptly must occur Legal & Ethical Feasibility Here is no legal permission needed for our system or projects because all the property we are selling or buying are legally allowed to sell and buy in Pakistan Project/Product Scope Manage the property of landlord as well as property dealer can manage record of the property.manage record of rented property with all their information. Manage expenses and payments record with their description, generate invoices for clients. Manage accounts and generate loss and profit. This data once entered can be edited/deleted as required there will be vast entries of data administrator can scroll the data Project/Product Costing Project Cost Estimation by Function Point Analysis types of component Complexity of components Low Average High Total External Inputs External Outputs External Inquiries Internal Logical Files External Interface Files Total 1016 Number Multiplied 1016*0.4 value Adjustment Factor Total Adjusted Function

11 Table 1 project cost estimation Activity Based Costing: Activity Cost Feasibility Report Cost Estimation by Function Point Analysis 7000 Activity based Costing 7000 Critical Path Method Task Dependency and Duration Vision Document 5000 Risk List Allocate Requirement Design Interface Modeling Test and Evaluate Improve Test Show Result Total Cost

12 2.4. Task Dependency Table Task# Task Dependencies T1 Proposal None T2 Feasibility Report T1 T3 Cost Estimation T2 T4 System Specification and Analysis T2 T5 Domain Model T1, T2 T6 Allocate Requirements None T7 Application Development T4, T5 T8 User T7 T9 Processing T7, T8 T10 Testing T9 T11 Showing T7, T8, T9, T10 Table 2 task dependency table 2.5. CPM - Critical Path Method: Specify the Individual Activities Individual activities are as follow: 1 Planning 2 Analysis 3 Logical design 4 Physical design 5 Testing 6 Implementation 7 Deployment 12

13 2.5.2 Determine the Sequence of the Activities All activities are dependent on each other like, first planning and then go to second activity which is named as Analysis. And then logical designing after it physical designing, then testing it all and then deployment Draw the Network Diagram A B C D E F Figure 3 Network Diagram Estimate Activity Completion Time: Activity Duration ES EF LS LF TS FS Planning (A) Analysis (B) Logical designing (C) Physical designing (D) Testing (E) Deployment (F) Identify the Critical Path: The critical path is the longest-duration path through the network. The significance of the critical path is that the activities that lie on it cannot be delayed without delaying the project. Because of its impact on the entire project, critical path analysis is an important aspect of project planning. Critical path is: (A,B,C,D,E,F). 13

14 2.6. Gantt chart Figure 4 Gantt chart 2.7. Introduction to Team member and their skill set Name Roll No Skill Asma Bashir 15MIT111 Bootstrap, CSS,PHP, SQL Ume Amara 15MIT109 Bootstrap, CSS,PHP SQL 2.8. Task and Member Assignment Table Member name Ume Amara Task assigned Backend development Logical Database Design Documentation Frontend development Asma Bashir Table 3 Task and Member Assignment Table Frontend development Proper functioning of system Testing and troubleshooting Documentation 2.9. Tools and Technology with reasoning LANGUAGE REASON HTML Frontend Development CSS Designing and styling Java Script Validation and dynamic interface SQL For Database PHP Backend development Table 4 Tools and Technology with reasoning 14

15 Bootstrap Bootstrap Bootstrap is widely used and most advanced browser language used to view and display the content on browser XML is used to carry the data while on other hand bootstrap is used in this project to develop the front end CSS CSS or cascade style sheet is frontend designing language to design the web pages. As the aesthetics and the user interface of any application does matter a lot so CSS is being used to design look and feel of the project Java Script This language allows us to make the website more interactive, as different data entry forms are being used in this project in form validation checks SQL Structured query language is used to create, update, delete and view the database records and tables PHP PHP is server or backend language it is widely used in making MVC to create the dynamic webpages. TOOLS Tool Dreamweaver XAMPP MS Word Reason Coding Virtual server For Documentation Dreamweaver Dreamweaver is all in one powerful editor that supports bootstrap, CSS, Java Script and PHP XAMPP XAMPP is a virtual server used to run the application on the web browser as for this time we are not going to buying a domain for our project so that using XAMPP Vision Document The Vision of the project is This system is capable of maintaining details of various Properties and storing all day to day transactions such as generation of rents, payments and expenses. Primary features of property management system are high accuracy, design flexibility and easy availability. It uses databases tables representing entities and relationships between entities. 15

16 2.11. Risk List: We may encounter following risks: 1 Scalability In future may be we need to enhance the database. 2 Lack of time or human effort can be a risk to some of component not implement. 3 Hardware failure Product Features / Product Decomposition: Our product features are as follows: 1. Secure because only admin can login after registration. 2. Generate fine and accurate result. Chapter 3: Second Deliverable 3.1 Introduction: 16

17 Property Management is a management system. This system is beneficial for the companies or organizations which deal with a large number of properties. The system will keep record of all properties. It will manage all expense and payments. End user of the system will be an admin who has to register him and then login to work with the system. Add new property and keep record of previous sell or buying information with clients information. The system will automatically generate monthly and annual expense report. It will also contain information about organization accounts Existing System: Currently, many organizations use a manual system. The existing system leads to many errors like data redundancy, data inconsistency, more paper work that wastes valuable time and money. Followings are some other disadvantages: 1. Maintenance of personal information and information about properties are difficult and time consuming. 2. The files and shelves occupy a lot of physical space. 3. It includes lot of paper work that may cause data redundancy. 4. Documents may be misplaced and lost. 5. Searching and maintaining process of properties record is complicated and slow. Keeping these limitations in mind, we aim to develop a user friendly property Management System which will provide a graceful solution to the above mentioned problems Organizational Chart Figure 5 Organization chart 3.4 Scope of the System: 17

18 Scope of the System The system will be utilized by any organization or company. End user of the system is only an admin who will have the access to the system. The admin will be able to add new projects, update or cancel the existing projects. Admin will add expense and tasks of each project. He will be able to add new account and add amount into those accounts. 3.5Summary of Requirements: (Initial requirements): 1 Admin registration 2 Admin can login 3 He can add, update and delete property. The system will be utilized by a landlord or a company. End user of the system is only an admin who will have the access to the system. The admin will be able to add new property, update or cancel the existing property. He will be able to add new account and add amount into those accounts. 3.6 External entities Admin is only one in this system: 3.7 Capture shall Statement: Para# Initial Requirements 1.0 System Shall give user interface and log in option too. 1.0 System Shall have a form to enter data for property. 1.0 System Shall have a database. 1.0 System Shall save the data entered by the user (Admin). 1.0 System Shall system allow user to add, delete or update property. 1.0 System Shall show reports projects, customers and expense. 1.0 System Shall allow admin to add new accounts and amounts. 3.8Allocate Requirements: Para# Initial Requirements Use case name 1.0 Admin registration Property Management system 1.0 Admin can login Property Management system 1.0 He can add, update and delete property. Property Management system 1.0 The system can manage company accounts. Property Management system 18

19 3.9. Priorities Requirements: Para# Rank Initial Requirements 1.0 Highest Admin will register himself Use case ID Uc.1 Use case Name UC_Admin_Registeration 1.0 Highest Admin will login. Uc.2 UC_Admin_Login 1.0 Highest He will add, Uc.3 UC_My_Property update and delete property. 1.0 Highest Admin will Uc.4 UC_selling_Proporety manage property tasks 1.0 Highest Will system save Uc.5 the data entered by UC_buying_property. the admin. 1.0 Highest System will Uc.6 UC_Manage_expense manage expense and payment of user. 1.0 Highest Add and manage Uc.7 UC_Rents_&_payments accounts. 1.0 Highest Add leases and Uc.8 UC_Leases_&_Tenants manage tenants. 1.0 Medium Generate reports Uc.9 UC_Generate_Reports 19

20 3.10. Requirements Traceability Matrix: S.No Para# System specification test System will show interface to register admin System will show page to login System will show a page to view property System will show a page from where admin can delete and update selling property System will show a page from where admin can delete and update buying property Admin will add expense of each task from add expense page System will show a page to add new rents and payments Admin will add leases and tenants information in page Admin will add amount in these accounts on add amount page. Build B1 B2 B3 B4 B5 B6 B7 B8 B9 Use case Name UC_Register_Admin UC_Login_Admin UC_My_property UC_selling_Property UC_buying_Property UC_Manage expense UC_Manage Rents_&_Payments UC_leases and tenants UC_generate_reports 20

21 3.11. High Level Use-case Diagrams: Figure 6 High level Usecase 21

22 3.12. Analysis Level Use case Diagram: Figure 7 Analysis level Usecase 22

23 3.13. Use case Description: 1: User Registration: Use case name: User registration Pre-Conditions: Basic flow: Alternative flow : Post -Conditions: Use case ID: 1 System is open. Enter user detail. Not done. Registered. 2: Log in: Use case name: Login admin Use case ID: 2 Pre-Conditions: Registered. Basic flow: Enter password and name. Alternative flow : Wrong password or name. Post -Conditions: Logged in. 3: Manage my Property: Use case name: view property Use case ID: 3 Pre-Conditions: Logged in Basic flow: Manage all personal property. Either that is buying or for selling or rented. Post -Conditions: Logged in. 4: Selling property: Use case name: Manage selling property Pre-Conditions: Basic flow: Alternative flow : Use case ID: 4 Property has been added. Fill form to add property. Fill form to add of property. Delete or update already registered property. 23

24 Post -Conditions: Property added and deducted from sale property. 5: buying property: Use case name: Manage buying property Pre-Conditions: Basic flow: Alternative flow : Post -Conditions: Use case ID: 5 Logged in Fill form to add property. Fill form to add of each property. Delete or update already registered property. Logged in. 6: Manage expenses: Use case name: Manage expense Use case ID: 6 Pre-Conditions: Property has been added. Basic flow: Alternative flow : Post -Conditions: Enter amount paid to complete any task of any property. Expense added and amount deducted from any selected amount. 7: Rents and Payments: Use case name: rents and payments Pre-Conditions: Basic flow: Alternative flow : Post -Conditions: Use case ID: 7 Property has been added. Enter amount paid to complete any task of any property. Rents and payments added and amount deducted from any selected amount. 8: Leases and Tenants: Use case name: Leases and Tenants Pre-Conditions: Basic flow: Use case ID: 8 Property has been added. Enter amount paid to complete any task of any 24

25 Alternative flow : Post -Conditions: property. And add new tenants also manage their information. Leases and Tenants added and delete. 9: Accounts: Use case name: Generate reports Use case ID: 9 Pre-Conditions: All data has been entered. Basic flow: Alternative flow : Post -Conditions: System will fetch data from database and show the Accounts status. Data has been entered in database. 10: Generate reports: Use case name: Generate reports Use case ID: 10 Pre-Conditions: All data has been entered. Basic flow: Alternative flow : Post -Conditions: System will fetch data from database and show the final report. Data has been entered in database. 11: logout: Use case name: Generate reports Use case ID: 10 Pre-Conditions: Admin login. Basic flow: logged out. Alternative flow : Not Log out Post -Conditions: Logged out 25

26 Chapter 4: Third Deliverable for Object Oriented Approach. 1. Domain Model 2. System Sequence Diagram 3. Collaboration Diagram 4. Design Class Diagram 5. State Transition Diagram 6. Data Model 4.1 Domain Model: Figure 8 Domain Model 26

27 4.2 System Sequence Diagram: Figure 9 System Sequence Diagram 27

28 4.3 Collaboration Diagram: Figure 10 Collaboration Diagram 28

29 4.4 Design Class Diagram: Figure 11 Design ClassDiagram 29

30 4.5 State Transition Diagram: Figure 12 State Chart Diagram 30

31 4.6 Data Model Figure 13 Data Model 31