Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 90 views

    SDDJ

    Uploaded by

    jhateshkolipakula
    This document outlines the proposed system design for a real estate management system. The system will allow users to search property listings from multiple real estate companies in one centralized location. It describes 5 subsystems (Registration, Data Maintenance, Contact, Search, Complaints) that will handle the key functions. The system is designed to have a 3 second response time, handle 5 transactions per hour, and use 512MB RAM and 5GB storage. It aims to be robust, reliable, available, fault tolerant and secure.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as RTF, PDF, TXT or read online from Scribd

    SDDJ

    Uploaded by

    jhateshkolipakula
    90 views8 pages
    This document outlines the proposed system design for a real estate management system. The system will allow users to search property listings from multiple real estate companies in one centralized location. It describes 5 subsystems (Registration, Data Maintenance, Contact, Search, Complaints) that will handle the key functions. The system is designed to have a 3 second response time, handle 5 transactions per hour, and use 512MB RAM and 5GB storage. It aims to be robust, reliable, available, fault tolerant and secure.

    Original Description:

    System Design Document for Real Estate Management System

    Original Title

    sddj

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    RTF, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the proposed system design for a real estate management system. The system will allow users to search property listings from multiple real estate companies in one centralized location. It describes 5 subsystems (Registration, Data Maintenance, Contact, Search, Complaints) that will handle the key functions. The system is designed to have a 3 second response time, handle 5 transactions per hour, and use 512MB RAM and 5GB storage. It aims to be robust, reliable, available, fault tolerant and secure.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as RTF, PDF, TXT or read online from Scribd
    Download as rtf, pdf, or txt
    90 views8 pages

    SDDJ

    Uploaded by

    jhateshkolipakula
    This document outlines the proposed system design for a real estate management system. The system will allow users to search property listings from multiple real estate companies in one centralized location. It describes 5 subsystems (Registration, Data Maintenance, Contact, Search, Complaints) that will handle the key functions. The system is designed to have a 3 second response time, handle 5 transactions per hour, and use 512MB RAM and 5GB storage. It aims to be robust, reliable, available, fault tolerant and secure.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as RTF, PDF, TXT or read online from Scribd
    Download as rtf, pdf, or txt
    of 8

    Prepared by: 680751034, 680751035, 680751036

    SYSTEM DESIGN DOCUMENT FOR REAL ESTATE MANAGEMENT SYSTEM


    Table of contents
    1. INTRODUCTION 1.1 PURPOSE OF THE SYSTEM 1.2 DESIGN GOALS 1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS 1.4 REFERENCES 1.5 OVERVIEW 2. CURRENT SOFTWARE ARCHITECTURE 3. PROPOSED SOFTWARE ARCHITECTURE 3.1 OVERVIEW 3.2 SUBSYSTEM DECOMPOSITION 3.3 HARDWARE AND SOFTWARE MAPPING 3.4 PERSISTENT DATA MANAGEMENT 3.5 ACCESS CONTROL AND SECURITY 3.6 GLOBAL SOFTWARE CONTROL 3.7 BOUNDARY CONDITIONS 4. SUBSYSTEM SERVICES 5. GLOSSARY

    1. INTRODUCTION
    1.1 PURPOSE OF THE SYSTEM
    The main purpose of this software is to maintain and provide the information about several properties owned by several real estate companies. This software will act as an interface between buyer and seller. This software aims at efficient utilization of time of both buyers and sellers.

    1.2 Design goals


    Response time: system responds within 3 seconds for user request. Throughput:system can complete five transactions in an hour if all conditions are satisfied. Memory: system requires 512MB RAM and 5GB hard disk. Robustness: system can survive from invalid user input. Reliability: system will model the specified and observed behavior without any difference. Availability: system is available throughout 24 hours. Fault tolerance: system can operate in erroneous conditions unless they are more. Security: system can withstand malicious attacks such as viruses, malwares etc. Extensibility: it is easy to add a new functionality to our system. Modifiability: it is easy to change the existing functionality as per requirement in our system. Portability: it is easy to change the frontend and backend platforms of this system. Readability: it is easy to understand the coding of the system. Utility: system supports the work of user very well. Usability: user with basic knowledge can easily use the system.

    1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS


    Rems :- Real estate management system User :- The person who can access property listings. PID :- property identification number. It is used to identify the property. Receo :- Real estate company executive officer. These are the persons who can add, modify and remove their property listings. Admin :-Administrator. He/She is a person who manages the ceos and content. This person will provide logins to owners. HTTP :-Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. HTTPS :- Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer). TCP/IP:-Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. Cname :-company name Fname :-Full name

    1.4 REFERENCES
    1. http://en.wikipedia.org/wiki/Software_Requirements_Specification 2. Google URL: http://www.google.co.in 3. Answers.com, Online Dictionary, Encyclopedia and much more. URL: http://www.answers.com

    1.5 OVERVIEW
    This system provides an information about several properties of different companies which are permitted by admin. This system allows users to access information about companies. Users can give their information to contact the company. The database will be maintained efficiently.

    2. CURRENT SOFTWARE ARCHITECTURE


    There are several architectures available for this purpose but they are not centralized. That is, if user want to buy a property he has to go each company through their website to search for relevant one. That is, the companies available as single modules separately.

    3. PROPOSED SOFTWARE ARCHITECTURE


    3.1 OVERVIEW
    RegisterSubsystem is used to allow users to register their companies, properties (if individuals). MaintainDataSubsystem is used to view the whole system and is used by administrator. ContactSubsystem is used to allow users to contact receos and individuals. SearchSubsytem is used to allow users to search website for relevant property. ComplaintsSubsystem is used to allow users to give complaints on fake properties.

    3.2 SUBSYSTEM DECOMPOSITION


    RegisterSubsystem-This subsystem is responsible for registering users. MaintainDataSubsystem This subsystem is responsible for providing system overview to the administrator.

    ContactSubsystem This subsystem is responsible for allowing customers to contact Receos. SearchSubsytem-This subsystem is responsible for providing search results to users. ComplaintsSubsystem-This subsystem is responsible for complaints submission to Admin.

    3.3 HARDWARE AND SOFTWARE MAPPING


    These diagrams are used to describe the physical components (hardwares), their distribution and association. To clarify it in details we can visualize deployment diagrams as the hardware components/nodes on which software components reside. We select database as the webserver and internet explorer as virtual machine for the webclient. This describes how subsystems are assigned to hardware and off-the-shelf components. It also lists the issues introduced by multiple nodes. This is the node diagram containing client and server interaction.

    Fig 1 deployment diagram for nodes


    webcli ent webse rver

    Components relationship is represented by following figure

    3.4 PERSISTENT DATA MANAGEMENT


    The database used here is relational database. This database is selected because our system supports concurrent accesses to different users. This system also has multiple applications over the same data. We use bridge pattern for abstracting database vendors. We use ODBC and JDBC to provide these abstractions.

    3.5 ACCESS CONTROL AND SECURITY


    Access control describes the user model of the system in terms of an access matrix. Security describes the issues such as selection of an authentication mechanism, use of encryption management of keys. 1 2 3 4 5 6 7 Administrator can access all details of the companies and sales that are already completed Receo can view sales of their company through the system. Administrator has all the privileges to view data of the system and he can also modify data to preserve integrity. Data is secure from malicious attacks Data is retrieved and inserted very fast. Encryption is provided for passwords. Authentication is done through ID and PASSWORD.

    3.6 GLOBAL SOFTWARE CONTROL


    This describes how requests are initiated and how subsystems synchronize. For our systems we use procedure driven control. This system will give a form and waits for user input. It proceeds further only after all the details are filled in current form. It then provides a result or another form.

    3.7 BOUNDARY CONDITIONS


    These describe the startup, shutdown and error behavior of the system. Any new conditions identified by administrator should be added. This system can

    withstand data that is deliberately or mistakenly inputted by the user which is out of bounds. This system can also withstand some hardware failures. This can also withstand software bugs to some extent.

    4. SUBSYSTEM SERVICES
    RegisterSubsystem-This subsystem is responsible for identifying fake companies. This is the initial step of the system. The main responsibilities of this subsystem are to get company name , details of it such that it is easy to identify whether it is fake company or not. MaintainDataSubsystem-This subsystem is responsible for providing system overview to the administrator. ContactSubsystem-This subsystem is responsible for allowing customers to contact Receos. After customers finding their relevant property can contact Receo for information about it. SearchSubsytem-This subsystem is responsible for providing search results to users. This subsystem collects data from customers and displays results. ComplaintsSubsystem-This subsystem is responsible for complaints submission to Admin. This subsystem collects data from user and post it to Admn.

    5. GLOSSARY
    REMS- Real estate management system PID- property identification number. SDD- system design document HTML - Hyper Text Markup Language JDBC - Java Database Connectivity

    ODBC- Open Data Base Connectivity

    You might also like