Development of a feature-rich web based application for real Estate
1. Title of the project: Property Search
2. Domain: Real Estate
3.
Sub Domain:
Sales and Marketing
4.
Project Architecture: N-Tire Architecture
5.
SDLC
methodologies: RAD / Waterfall model
Abstract of
the project:
This
project is aimed at developing an Online Real
Estate Agent: Property Search, which is
of beneficial to either a real estate agent or a prospective. The Property Search
is an Internet based application. This system can be used to store and search
the property portfolios.
Property
Search is a unique virtual platform that allows any user to post a property
related advertisement on the Internet without incurring costly advertisement
fees. User-friendliness, reliable service together with maximum and continuous
exposure is
the qualities that Property Search stands
for. We believe that whether you are searching or selling your property online, a pleasant
and hassle free experience is of
utmost importance. Being available 24 hours a day, 7 days a week and equipped
with a list of essential tools
and information. Property Search
offers a one-stop property search for your ideal property. Searching for a
property is made easier with our property search engine. In this
project we provide one stop property search for both
residential and commercial properties. It saves your time by narrowing down
your search for buyers, tenants or investors. Property Search
offers a one-stop property search for interested buyers, tenants or investors. We
are dedicated to make search fast and easy.
Property
Search offers a one-stop property search for your ideal
property. Searching for a property is
made easier with our property search engine.
Property
Search provides one stop property search for both residential
and commercial properties. It saves your time by narrowing down your search for
buyers, tenants or investors.
6.
Modules: There are four main modules in this
system. These are:
- Administration
- Registered User (Agent/Owner)
- General User (Visitor)
- Services
Administration
·
Admin login / logout
function
a.
One portal admin
ID and password will be assigned
b.
Change Admin
password
·
Member
list
i.
Tabulate list base on Member Name,
Member Id, Date of Birth, and Email
Id.
ii.
Search function for Member’s name.
iii.
Add / Edit / Delete registered users.
iv.
Sort functions for Member Name,
Member Id, Date of Birth, and Email
Id.
·
Post-A- Property list –
i.
Tabulated list base on Project Name, Property Type (HDB / Private /
Commercial), Rent/Sales, District, Price,
Published Date, Expiry Date, Member Name, Status (Active/Inactive)
ii.
Search function base on Member’s name and posted date of the Property.
iii.
View / Delete / Publish Property.
iv.
Property will only publish after Admin has been notified and approved.
·
Sponsor’s Ads
i.
Tabulated list base Title, Ads Type (Small
Ads / Banner), Company, Published Date, Expiry Date, Status
ii.
Search function base on Ads Type, Status,
period of Published Date and period of Expiry Date.
iii.
View / Edit / Delete / Publish Ads.
iv.
Ads Detail
§ Type
§ Title
§ Company Name
§ Publish date
§ Expiry Date
§ Fee
§ Target URL
§ Short Write Up
§ Image Upload
§ Status
§ Display Time
§ 780x105 pixels for banner
& 63X100 pixels for Small Ads
7.
Functional
components of the project:
There
are registered people in the system. They are real estate agents. Registered
real estate agents can create/modify property portfolios. Non-registered people
can also use the system to search the desired property.
Whenever
a new real estate agent registered himself then Auto acknowledgement email to
member and Admin upon successful registration
- A registered person should be able to
- Login to the system through the first page of the application
- Change the password after logging into the system
- See his/her property portfolios
- Create new property portfolio
- Modify an existing property portfolio.
- Auto acknowledgement email to member and Admin upon successful submission of ads, payment of ads and published of ads.
- A property portfolio contains details about the property like description of property, area, to be sold or to be rented, approximate price, name and details of the person to be contacted.
- Details in property portfolio are editable except property id.
- A new realtor should be able to register himself.
- When a new property portfolio is created, it will be assigned a unique property id. System will generate this id.
- System should not let unauthorized/non-registered persons to create/modify property portfolios.
- Another realtor cannot modify property portfolio created by a realtor.
- A prospective buyer should be able to search for the property. She/He can enter search criteria like area name, price range, sell purchase/rent etc.
10.
Latest Property
·
2 latest Residential Property and 2 latest Commercial Property
·
Details will comprise of:
i. Address,
ii. Type
iii. Price
8.
Keywords:
·
Generic Technology
Keywords: Databases, User Interface, Programming
·
Specific
Technology Keywords: ASP.Net, C#.Net, MS SQL Server
·
Project
Type Keywords: Analysis, Design, Implementation, Testing
·
SDLC
Keywords: Presentation, Business, Data Access Layers
9.
Environment:
·
Servers:
Operating System Server: - Microsoft
Windows 2000 or Higher
Data Base Server: Microsoft
SQL Server 2000/2005
·
Clients: Microsoft
Internet Explorer,
·
Tools: Microsoft
Visual Studio .Net
·
User
Interface: ASP.NET with AJAX
·
Code
Behind: VC#.NET
10. Requirements:
·
Hardware
requirements:
Number
|
Description
|
1
|
PC with 2 GB
hard-disk
and 256
MB RAM
|
·
Software
requirements:
Number
|
Description
|
1
|
Windows 2000/ XP/ or
Higher with MS-office
|
2.
|
MS-SQL server2000/2005
|
3.
|
Ms-Visual Studio .Net 2005
|
4.
|
Ms-Internet Explorer
|
·
Manpower
requirements:
3 to 4 Developers can complete this in 3-4
months.
11. Milestones:
No.
|
Milestone Name
|
Milestone
Description
|
Remarks
|
1
|
Requirements
Specification
|
Complete
specification of the system including defining hierarchies constitutes this
milestone. A document detailing the same should be written and a presentation
on that be made.
|
Attempt should be
made to add some more relevant functionality other than those that are listed
in this document.
|
2
|
Technology
familiarization
|
Understanding of the
technology needed to implement the project.
|
The presentation
should be from the point of view of being able to apply it to the project,
rather than from a theoretical perspective.
|
3
|
Database creation
|
A database of at
least 10 entries of users with at least 1 should application admin.
|
It is important to
finalize on the database at this stage itself so that development and testing
can proceed with the actual database itself.
|
4
|
High-level and
Detailed Design
|
Listing down all
possible scenarios and then coming up with flow-charts or pseudo code to
handle the scenario.
|
The scenarios should
map to the requirement specification
|
5
|
Development of front
end functionalities.
|
Implementation of
the main screen giving the login, screen that follows the login giving
various options, screens for each of the options
|
During this
milestone period, it would be a good idea for the team to start working on a
test-plan for the entire system. This test-plan can be updated as and when
new scenarios come to mind.
|
6
|
Integrating the
front-end with the database
|
The front-end
developed in the earlier milestone will now be able to update the database.
Other features should be functional at this stage. In short, the system
should be ready for integration testing.
|
|
7
|
Integration Testing
|
The system should be
thoroughly tested by running all the test cases written for the system (from
milestone 5).
|
Another 2 weeks
should be there to handle any issues found during testing of the system.
After that, the final demo can be arranged.
|
8
|
Final Review
|
Issues found during
the previous milestone are fixed and the system is ready for the final
review.
|
During the final
review of the project, it should be checked that all the requirements
specified during milestone number 1 are fulfilled
|
12. The following steps will be helpful to start off the project:
- Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.
- Gather some knowledge of product hierarchies and maintenance before starting the design.
- Create a user database with different access levels.
- Start with creating the login screen.
- Create menus for navigation and group the functionalities as sub menus.
- Create the help-pages of the application in the form of FAQ. This will helps user.
No comments:
Post a Comment