Professional Documents
Culture Documents
Version 1.1
April 28, 2009
Scheerens.4@osu.edu, wohlwend.8@osu.edu
Copyright Permission to make digital or hard copies of all of this work for personal or
Notice classroom use is granted without fee provided that copies are not made or
distributed for commercial advantage and that copies bear this notice and
the full citation on the first page. Abstracting with credit is permitted. To copy
otherwise, to republish, to post on servers, or to redistribute to lists, requires
prior specific permission and/or a fee. Request permission to republish from
Tyler Scheerens <scheerens.4@osu.edu>.
Revision History
Table of Contents
1. INTRODUCTION.....................................................................................................................................1
1.1. PURPOSE.................................................................................................................................................1
1.2. SCOPE.....................................................................................................................................................1
1.3. REFERENCES.............................................................................................................................................1
1.4. STANDARDS.............................................................................................................................................1
1.5. DEFINITIONS..............................................................................................................................................1
2. OVERALL DESCRIPTION......................................................................................................................1
2.1. PROJECT ABSTRACT....................................................................................................................................1
2.1.1. Project Scope.....................................................................................................................................1
2.1.2. Background........................................................................................................................................1
2.1.3. System Purpose.................................................................................................................................1
2.1.4. System Mission ................................................................................................................................2
2.1.5. System Functions / Responsibilities .................................................................................................2
2.2. FUNCTIONAL OBJECTIVES.............................................................................................................................2
2.3. SYSTEM CONSTRAINTS ...............................................................................................................................3
2.3.1. User Interface Constraints ................................................................................................................3
2.3.2. Hardware Constraints........................................................................................................................3
2.3.3. Software Constraints..........................................................................................................................3
2.3.4. Communications Constraints.............................................................................................................3
2.3.5. Data Management Constraints..........................................................................................................3
2.3.6. Operational Constraints.....................................................................................................................3
2.3.7. Site Adaptation Constraints...............................................................................................................3
2.3.8. Design Standards Compliance...........................................................................................................3
2.4. OTHER CONSTRAINTS..................................................................................................................................3
4. SPECIFIC REQUIREMENTS..................................................................................................................1
4.1. USE CASES..............................................................................................................................................1
4.1.1. Use Case Scenario 1.........................................................................................................................1
4.1.2. Use Case 1 Prototype........................................................................................................................1
1. Introduction
1.1. Purpose
The Project IQ Social Networking Component provides the functionality of a message board, user
comment system, and a means of uploading appraisals.
1.2. Scope
The Social Networking component integrates the open source Yet Another Forum message
board code. It also involves modification to the Property IQ master page to integrate a user login
system. It includes a nested page for each property that lists forum threads about that particular
property. It finally includes an appraisal hosting and uploading system.
1.3. References
This is a complete list of all documents referenced elsewhere in this document.
1. Systems Analysis and Design in a Changing World , Satzinger, Burd, Jackson, 3rd edition.
2. The Object Oriented Approach Concepts, System Development and Modeling with UML,
Satzinger, Orvik, 2nd edition.
1.4. Standards
This is a complete list of all standards used in this document.
1. IEEE 830-1993 – The content and qualities of a good Systems Requirements Specification
(SRS) are described and several sample SRS outlines are presented. This recommended
practice is aimed at specifying requirements of software to be developed but also can be
applied to assist in the selection of in-house and commercial software products.
1.5. Definitions
This section contains a list of definitions for organizational specific words that are not universal.
GUI – Graphical User Interface
WSID – Workstation Identification Number
DB - Database
2. Overall Description
2.1.2. Background
A recent credit crisis in the United States has led to a significant increase in the number of
distressed and foreclosed homes. The system being developed will provide a multi-
purpose tool for handling a variety of tasks associated with these properties.
One component of the mashup will show static information on all properties in an area.
Things like recent selling price, number of bedrooms, and other commonly available
information.
A second component will gather all GIS data and pictures associated with a home,
including providing a tool to locate other properties sold in the area.
The third component will provide trends data on the future price of the home based on
information gathered by the statistical data group and an in house developed formula.
The fourth group will provide a social networking aspect to the website, enabling users to
post on real estate-related message boards, or comment and attach information on specific
properties.
2. Listing resource where users can list or begin discussions about specific properties. This
aspect will also list information available from other components of the mashup that are
relevant to the specific property (hard data, maps, and price models).
4. Develop a simple and efficient search feature to find topics and information on specific
properties.
5. Develop and manage a user registration and login system for the web site.
2. The system shall provide the ability for users to post topics on specific properties,
allowing users to request information on said property, post images and other
related data, and discuss the property with other users.
3. The system shall provide the ability for users to register and login before they are
allowed to interact with the social networking aspect of the web site.
4. The system shall provide hosting for and the ability to upload appraisal
documents and other media for appropriate users.
5. The system shall allow profiles to tag properties as claimed, and list a price for
them.
6. The system shall list recently tagged properties on a feed along the left hand side
of the master page.
Login
Property information
IQ
Profile data
Master page
Appraisal page
Hosted file
information
Property Topic
IQ information
Forum topic
page Topic page
Property Post
IQ information
Forum page
Post page
4. Specific Requirements
Basic Flow: Webpage looks up profile data and returns the matching
cookie. Webpage is updated to match new user data.
Business Rules: This allows users to log in to their profile from anywhere that
hosts the master page.
Input Data User data, file data, appraisal flag, appraisal value (optional)
Basic Flow: User selects file to upload, toggles appraisal flag, provides
appraisal value if appropriate. Server receives file and hosts it.
File name is placed on media page with link to file. If appraisal
flag is toggled, appraisal valuation is listed next to link.
Alternative Flow(s): User canceling during file selection returns to media page.
Extension Points: Tab is an extension of existing tab system. Page exists within
master page.
Business Rules: This allows users to host relevant files on the website.
Notes The page supports the hosting of any kind of file, media,
appraisal or otherwise. It does not filter these or sort them.
Output Data Updated page with property holder listed under property.
Post-conditions User's profile lists property as claimed, property data lists user
as holder.
Basic Flow: User presses “claim property” link and provides listing price.
Necessary table are updated.
Alternative Flow(s): User may cancel when prompted for a list price. This sends
the user to the previous screen.