The UnReal Estate Catalog System (UECS) contains many characteristics which emphasize ease of use and convenience. The system is structured so each level of user can view all the major tasks available to him or her on one screen. This allows navigation between tasks with little time and effort.
The database engine powering UECS supports multi-user access, allowing several agents to make queries simultaneously. Searches may be conducted using any number of criteria as outlined in the specifications. These criteria are inputted by the user primarily with point-and-click procedures. This makes it very easy to change the nature of the search. The results of the search can be displayed in a summary format or in a detailed format. Each listing in the query results may be accessed by clicking on it. To view the next closest listing match the user simple can click on the next selection in the displayed listings.
The system also contains features that ensure the safety of pertinent data. For example, listings may be deleted by the listing agent only, and this function is password protected by that listing agent. After a deletion is made, the system notifies the system administrator of the deletion. The administrator then has the option of PURGING listings from the deleted listings storage area or restoring the listing if it was deleted by mistake. This policy will ensure that the untimely deletion of active files is avoided as much as possible.
For all tasks, at every point of the application, on-line help will be available by pressing a HELP button. The assistance provided shall be relevant to the work in progress, allowing members of Unreal Estate Inc. to learn how to complete their business efficiently.
As indicated by Unreal Estate Inc., there will be three levels of access to the Property Management System: On-line Tutorial level, Browsing level, and an Administration level. The user may access any one of these levels at the Application Entry Point. Access to Administration is password protected.
It has yet to be determined what the exact nature of this tutorial will be. One possibility is a series of HTML or hypertext pages that will guide a novice user through major tasks. Another possibility is an interactive system that allows the user to manipulate a 'pseudo' database. More information on this area is in the discussion on a minimal system and enhancements.
This level of access allows the user to have access to the database of real estate listings for viewing and generating customer reports:
All of the functions that are available at the browsing level are also available at the administration level. The administration level is broken down into 2 access levels:
The agent and administrator have access to the following:
The following are functions available exclusively to the system administrator:
Fields | Note |
---|---|
Multiple Listing Service (MLS) Number | Primary Key |
Agent ID | Foreign Key Agent |
Price | |
Picture | |
Lot Size | |
Square Feet | |
Property Type | |
Property Condition (Sale/Rental) | |
Status | |
Bedrooms | |
Bathrooms | |
Total Rooms | |
Garage Type (None, Attached, etc.) | |
Garage Size | |
City Area | Foreign Key Area |
House Address | |
House Postal Code | |
Property Comments | |
Amenities: (Boolean Fields)
|
|
Taxes | |
Conditions of Sale | |
Expiry Date | |
Commission on Sale | |
Client Name | |
Client Address | |
Client Postal Code | |
Client Phone | |
Client Fax | |
Client Cellular | |
Rental Smoking/Non-Smoking | |
Rental Damage Deposit | |
Rental Pets | |
Rental Utilities Included | |
Deleted Flag |
Fields | Note |
---|---|
Agent ID | Primary Key |
Agent Type | |
Name | |
Address | |
Postal Code | |
Phone | |
Fax | |
Cellular | |
User Name | |
User Password |
Fields | Note |
---|---|
City Area | Primary Key |
Quadrant of City (NW,SW,...) |
Fields | Note |
---|---|
Offers ID | Primary Key |
Offer Type | |
Multples Listing Service (MLS) Number | Foreign Key Listing |
Agent ID | Foreign Key Agent |
Price |
For our implementation of the real estate catalogue, we will be using Delphi 2.0. Delphi is based on the Microsoft Windows 95/NT operating system, thereby making all programs written for it automatically incorporate the Windows graphical user interface. As well, Delphi encourages that the programs written in it are Windows standard. So, any user who knows how to operate one Windows program will find it easy to adapt to our program. Menu bars, command buttons, mouse usage, etc. all look and feel the same as in other standard Windows programs. This is a big bonus since it allows the user to more easily adapt and learn our software. The nature of Delphi involves the use of pre-made components for much of the program development. This means that there is less coding and more manipulation of these components. This is important to us because it means that we can very quickly develop our application to customer specifications, due to less coding, and less testing since many of the components are pre-tested and perform uniformly under all conditions. The use of components in Delphi means that we can more easily modify the program for later enhancements. For the database section of our program, we are using Borland's Interbase database engine. This engine comes fully equipped with multi-user, network accessible database functionality. It also includes full SQL capabilities for advanced queries and database management.
Much of the coding that we have to do is very simple, due to the use of pre-made components that handle much of the complex nature of our program. The most difficult aspects of our program as far as coding goes is the database management with SQL, prioritizing queries, and developing a user friendly help system. By prioritizing, what we mean is that the user may select features that are important in the query, and then the query results will be listed in order that they are most relevant to the user's choices.
There are numerous possible enhancements, and many more will come up as true development of the programs continues. One potential enhancement would be to include query reports. This is similar to combining the print and query features together. It would allow the user to perform a query based on certain criteria such as house location, realtor, total square feet, etc., and then print all instances applicable from the query. This would allow reports for specific information to be generated, rather than simply printing for a single record at a time, with no correlation between them other than logical order in the database.