2. Online Real Estate System

3. Group Members Introduction Member 1 Name: Awais Khalil VU ID: BC060400489Introduction: Assalam-o-Alaikum, I am Awais Khalil and I am 21 years old studying in Virtual University of Pakistan as a CS Student and have just completed my BSCS.

4. Group Members Introduction Member 2 Name: Muhammad Adeem VU ID: BC060400502Introduction: Assalam-o-Alaikum, I am Muhammad Adeem Mughal and I am 22 years old studying in Virtual University of Pakistan as a CS Student and have just completed my BSCS and also working in an NGO as a Computer Lab Incharge from last 3 years.

5. INTRODUCTION OF PROJECT The Online Real Estate System (ORES) web application is intended to provide complete solutions for Customers, Owners of the Property and Property Advisors through a single get way using the internet as the sole medium. It will enable Property Advisors to setup online Property, Customers to browse through the property and purchase them online without having to visit the real estate physically. Online Real Estate System becomes increasing popular nowadays. It brings many advantages to sellers, buyers and property advisor. In our project, we developed an online Real Estate system for sellers and buyers.

6. Adopted Methodology The adopted methodology is the VU Process Model which is the combination of Waterfall and Spiral Model. Advantages of Waterfall Model: System is well documented. Phases correspond with project management phases. Cost and Schedule estimates may be lower and more accurate. Details can be addressed with more engineering effort if software is large and complex. It is composed of independent phases to be done sequentially. Advantages of Spiral Model: It provides better risk management than other models. Requirements are better defined. System is more responsive to user need. The spiral size corresponds to system size, while the distance between the coils of the spiral indicates resources.

8. Actors Catalog Actors in our ORES are Customer (Seller/Buyer, Registered User, Visitor) Estate Agent / Property Dealer Administrator

9. Use Case Diagram The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted.

10. Business Rules Catalog The Core Functional Requirements are: Customers to search for properties to buy/rent: Registered Buyers will be able to make inquiries and advance reservation for a property of their choice. Whether they want to sell property, Buy property or rent a property. Register client/Agent: Secure registration and profile management facilities for registered users and estate agent. Login: Registered user and agent must be login to see the property ads and updates. Property Price: If customer found a property of their own choice then the payment process must be fulfilled by online credit card facilities. Maintain and updates records of customers: The records of customers should be maintain and updated by the database administrator. Manage Property: Estate agent should manage any type of property that the customer looking for. Handling Biding: The system must capable of handling Biding process on buying a property. Handling advertisements: How advertisements for a new property or firm should be handled? Agents Directory Management: The system will provide an environment to Registered Buyer, Advisor and Seller to perform and control their business transactions more effectively and professionally. Reports of all the things: Finally reports of all the things should be made.

11. Architectural Design Block diagram is a diagram of a system, in which the principal parts or functions are represented by blocks connected by lines, that show the relationships of the blocks.

12. Project Scope/ DFD’s Context Diagram of Online Real Estate system A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. A level 0 / context diagram is a data flow diagram which shows how the system will receive and send data flows to the external entities involve.

13. Level 1 Data Flow Diagram The level 1 diagram, which shows the main functional areas of the system.

14. Team Structure Group ID: S10205053 Name: Awais Khalil VU ID: BC060400489 Major Responsibilities: Software Engineering & diagrammatic work Name: Adeem Mughal VU ID: BC060400502 Major Responsibilities: Introduction & Coding, Forms filling

15. Project Schedule (Gantt Chart) A Gantt chart is a graphical representation of the duration of tasks against the progression of time. A Gantt chart is a useful tool for planning and scheduling projects. A Gantt chart is helpful when monitoring a project's progress.

16. Sequence Diagrams A sequence diagram is a kind of interaction diagram that shows how processes operate with one another and in what order. Sequence Diagram for Registration

17. Sequence Diagram for Sign In

18. Sequence Diagram for Search

19. Sequence Diagram for View Advertisement

20. Logical Model/Class Diagram

21. Entity-Relationship Diagram

22. Database Design

23. User Interfaces

24. Tools The various tools that we have used during the development of this application are: Visual Studio 2010 Visual Studio 2010 MS SQL Server 2008 MS SQL Server 2008.Net Framework.Net Framework Other’s Diagrammatic & planning tools are: Smart Draw 2010 Smart Draw 2010 MS Project 2007 MS Project 2007 MS Visio 2010 MS Visio 2010

25. Test Cases Test Case # 1 Test Case # 1 Test Case Title: Testing the Search Property mechanism of ORES System Preconditions User may search the property in the specific search area. Actions Click the search button on the page Expected Outputs All the list of the property in the specified area is displayed. Tested by Awais Khalil ResultPass

26. Test Case # 2 Test Case # 2 Test Case Title: Testing the Registration mechanism of ORES System Preconditions Web Access Actions User enters all necessary information. Expected Outputs Register successfull. Tested by Awais Khalil ResultPass

27. Test Case # 3 Test Case # 3 Test Case Title: Testing the Login mechanism of ORES System Preconditions Web Access Actions User enters all necessary information. Expected Outputs login successfully. Tested by Awais Khalil ResultPass

28. Test Case # 4 Test Case # 4 Test Case Title: Testing the Admin login mechanism of ORES System Preconditions Web Access Actions Click on the login button on the page. Expected Outputs System should login admin successfully. Tested by Awais Khalil ResultPass

29. Test Case # 5 Test Case # 5 Test Case Title: Testing the property advertising mechanism of ORES System Preconditions Web Access Actions Click on the post an ad button on the page. Expected Outputs System should display advertisements posted successfully. Tested by Awais Khalil ResultPass

30. The End