Perfect Property Information Management System - Case Study Example

Perfect Property Information Management System Name Institution of Afiliation Date Introduction The job requirement for this task is to analyze and design the Perfect Property Information System using Object Oriented methodology. The analysis of the company’s performance need also to be performed in details and realize the practical and working system for the company’s management. The tasks to fulfill encompass the following steps: Requirement Gathering You will develop an information management system for Perfect Property Company to capture the required company profile information. In the preliminary task, it is required to: 1 Owner’s view chart for the aforementioned business narrative that can be shown to stakeholders for feedback. An Owner’s view of PPIMS Existing Problem Apparently, the Perfect Property limited does its processing of tasks manually using pen and paper. The file cabinets are filled with papers and no structured data storage is in existence. Without an online platform, the process of property identification and matching criterion that are specific to a potential client are hard and difficult to carry out. Aims and Objectives of the New System The PPIMS is to design and create a web portal that would capture all potential customers’ details and store the record in a structured format. The new system would seek to ease the process of registration of customers and clients effectively, detailing their preferences and therefore getting to serve the customers’ personal interests The new system also seeks to achieve is to offer search tool for records based on preferences of clients and for ease of identification of the product that is customer specific. To record all transaction details that would prove relevant to the making informed decisions as well ease the task of auditing and measuring the general health of the business System Prerequisites System development requires an integration of a number of tools for successful and complete product generation. Tailored to the intended functionality of PPIMS, a number of key components are mandatory. That includes an html editor program for writing the hypertext documents that constitute the web portal, its styling cascaded style sheet codes, a Database Management System (DBMS), a PHP coding environment otherwise referred to as IDE and a domain name to identify the portal not forgetting an Internet Service Provider (ISP) for online hosting. For the purpose of demonstration, a limited number of tools will be made available that are found best to prototype. For html and CSS documents, a simple notepad will be of use. A notepad is a text-editing program that allows plain text to be typed without defined formatting styles. For the PHP server, the Apache version 5 will be used which runs both on local machine or dedicated server machine. The DBMS environment will be the Open Source application: MySQL that integrates with Apache server. The services will run from a local host server installed in a local machine that emulates real server running. Functional Specifications and Requirements This section refers to the document that describes the expected performance of the system proposed. The sub procedures independent and inter dependent operations are described in this document. The main sub functions in the PPIMS include client registration, property management, sales/transaction management, property search, booking an appointment, and notification system. Domain Analysis Step 1. Write domain definitions and domain scope for the system and each subsystem. Real Estate Management System Domain Scope Domain Scope Outline Web-Portal Offers the access platform into the system and links the users of the system to the back end processes The Internet and Web The internet is a worldwide network of computers accessed via the World Wide Web (www). The network enables distant but prospective clients to access the system, for which it expands the business customer base. It makes the site available to many more people and improves efficiency of use, by offering self-service kind of platform. The RDBMS The relational database management system is the core engine for structuring data systematically to ease the process of searching and indexing of the specific data. All data stored in the RDBMS can be accessed and manipulated using the sequential querying language and be availed upon a request. Web Application The underlying program that runs and executed by the server is the web application. It is PHP based and it is what offers the platform to accept user arguments and parameters and parse them to the MySQL database. Step 2. Domain dictionary Real Estate Management Domain Dictionary Name Type Description Web-Portal Web based access platform Brings a program interaction of the system to the User in remote place such as to have a desktop experience and UI that replaces the need for physical interaction. The Internet and Web Online Service provider and support Makes a real time interaction of the system to remote users who are distant from each other, separated by a significant geographical space. The RDBMS Database It is the server-based main storage component. It serves entities that exchange data. Web Application Software Automated server based system that controls the data flow between user and the storage devices in place of a human agent. Behavioral Modelling 1. Scope Description Real Estate Management Sales Management: Use Cases Summary ID Use Case Name Description Actors 100 Record Buyer Information Potential client creates a user account in to the system, fills the bio data form and enters his preferences and points of interest. Customer, sales agent 110 System authentication and login The client enters his username and password. The system queries the database to find a match or not. The system loads the portal or redirects the user to try again. Customer, Sales Agents 120 Match property The client enters his preferences and initiates a search. The system searches through the available property and displays the results in an index within the portal Customer 130 Site visit appointment Customer requests for a site visit appointment and enters into the system the property ID. System checks for a possible date that the property sales agent is available and sends back a feedback, both to the customer and agent. Customer, property 150 Property Management Sales agent feeds in a new property into the database and fills in the field details. It then notifies the customers who meet the criteria for the property. Sales agent, Property 160 Finalize Sales Contract Records the transaction ID and updates the database with the details of the transaction. Customer 2. Case Diagram for Match property, Finalize Sales Contract. Use Case: Match property, Finalize Sales Contract ID: Search Item Scope: Find identical item in the DBMS Priority: Checked criteria Summary: The customer selects his preferences, clicks on search button for which his preferences form the search criteria from the database, and returns the property results. Primary Actor: Customer Supporting Actors: Stakeholders: Property agent, Real Estate Management system Generalization: Available property units Include: Rentals and residential units Extend: Price range with an error margin of 5% Precondition: Registered customer Trigger: Sales/ transaction sub system Normal Flow: Customer – query database – return search results Sub-Flows Alternate Flow/ Exceptions: Post-Condition: Finalize Sales contract and Log out of system Non-Behavioral Requirements: Open Issues: Data security if portal is idle. Source: Web portal Author: Revision & Date 3. Case diagram for Sales Management Subsystem with dependency (include & extend) relationships. Use Case: Sales Management sub system ID: 160 Scope: Finalize sales contract Priority: New search by a new or existing customer Summary: The customer selects the wanted property, keys in the property ID and makes necessary payment after agreeing to terms and conditions. Primary Actor: New Customer search Supporting Actors: system Stakeholders: Property agent, property owner, legal team Generalization: Available property units Include: 120: Match property 150: Property management Extend: 160: Finalize transaction Precondition: Registered customer, choice selection Trigger: Sales/ transaction sub system Normal Flow: 1. Customer logs in. 2. Update the search preference. 3. Search the property database. 4. Customer makes fiscal transactions. 5. Agent affirms the property ownership transfer. 6. log out Sub-Flows Check legal conditions Alternate Flow/ Exceptions: 1. a. Enter username b. Enter pass code (Extend 150: property management) Post-Condition: Log out of system Non-Behavioral Requirements: Open Issues: Source: Web portal Author: Revision & Date Real time date and time 4. Activity diagram for selling a property process (sales management process). Flow diagram: Structural and Dynamic Modelling 1. Summary of the grammatical objects Grammatical Objects Class Comments Property ID, Location, type, size, cost, Description property Details of the property objects that can take a form and have a description Customer ID, Name, Preference Customer Represents a customer who is potential buyer Agent ID, Agent name, contact address, telephone, property name Agent Describes details of the agent that can relate to other classes and represents a property owner Transaction ID, date, type, amount, property id, customer name, agent id, agent name, Transaction The transaction class holds objects that are shared about the other classes whose instance form a new class entity 2. entity classes and their responsibilities Class Description Responsibilities Use Case Customer Each customer has a unique identity and an instance Is the main driver of the system without whom the program won’t initialize Register member Agent Is also a key component in authenticating a client and transfer of objects Authenticates users and clients Register member Property Is the item of trade about which the system exists Ownership is transferred between agent and client Register property 3. Attributes, operations, and collaborators for each class that identified. CUSTOMER Customer ID, Name, Preferences, Telephone Attribute Collaborators preference Client and property Customer ID Property and transaction OPERATIONS Operation Collaborators Registration Agent AGENT Agent ID, Agent name, contact address, telephone, property name Attribute Collaborators Agent ID Property Property name Client OPERATIONS Operation Collaborators Clear client Customer PROPERTY Property ID, Location, type, size, cost, Description Attribute Collaborators Property ID Customer and Agent OPERATIONS Operation Collaborators Issued Customer and agent 4. A complete class diagram with associations and multiplicity of a contract class. 5. Sequence diagram of “Match Property” for Real Estate company case study. Read More