History: Wild Woods Apartments is a property management company. They own around 20 different building, each of which is composed of anywhere from 10-60 different units. Each building has a lot of information to maintain such as occupancy, leases, payments and maintenance requests and expenses. This is expected to be done by the manger on site and then they are to send a report to cooperate every quarter. Every quarter, cooperates receives the information form all 20 sites and has to then manage that. Doing all of this paper work and managing by hand or even in spreadsheets is very inefficient and wastes time. Creating a database that can record and organize all of this pertinent information would help both the managers, cooperate and even the tenants.
Scope: The Wild Wood Apartments Database will manage leases, maintenance requests and expenses, and rent amount and payments. The information will be kept secure and the information will only be viewable to those that have a need to se e it. It will track tenants that have already paid rent and ones that are late. It will also track when a maintenance request is submitted and when it is completed.
Constraints: The database will be good for managers to be able to manage a tenants rent and maintenance requests. It will show when a maintenance request is submitted and when it was completed. It will not show the status of the maintenance order as it is being completed, or if they are waiting for supplies, etc. It will show the managers when a tenant is late on a payment but will not show the tenant with they are current or not.
Objective The objective is to create a database for Wild Woods Apartments that can help them organize all of their properties information into one system t help streamline some of the work both the onsite managers have to do as well as the cooperate workers. The objective is to make the database record and use all of the important information in once place The objective is to be able to use the database for managers to be able to generate the quarterly reports with ease.
Tasks and Timeline
Gathering Data: This task will consist of gathering of current data to find what information fields will be needed. It will also consist of a questionnaire. Time allotted: 2 weeks
Deliverables: a text with the questionnaire on it, and a list of the required data. Analyzing Data: Analyze the data to find the most efficient way to organize and display it Time allotted: 2 weeks
Deliverable: a sample layout of how the information will be used Normalization: A model will be made using normal entities and relationship Time allotted: 3 weeks
Deliverable: A diagram showing the relationships and entities Building the physical database: The model will be turned into an actual RDBMS system. Time allotted: 4 days
Deliverable: a schema of the database
Testing and security: test data will be entered and the system will be tested to make sure all of the rules and the security protocols are working properly. Time allotted: 5 days
Deliverable: A record of the tests ran and the results
Database Completion and Installation: Any final changes will be made and then the database will be put on the server. The test data will be removed and the network connections will be tested. Time allotted: 2.5 Weeks