Product Requirements Document Revision History

CSE 772 Project IQ Social Networking Component

Project IQ Social Networking Component

Systems Requirements Specification

Ahsan

Proprietary and Confidential

i

performance. Ohio State CSE 772 Banks in possession of foreclosed property Last saved: This printing: <nn> pages <path> SRS_Outline. The SRS meets IEEE830 standards and is the exclusive requirements document to be used in development.edu>.CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction About This Document Purpose of this Document The Systems Requirements Specification (SRS) is designed to express the behavioral.edu. SP09 Tyler Scheerens. wohlwend. 2011 Document Prepared for Intended Audience Date of Publication Page Count Document Location Prepared From Associated Procedures Prepared by ii Proprietary and Confidential Ahsan . Information Systems Capstone. or to redistribute to lists. to post on servers. Request permission to republish from Tyler Scheerens <scheerens.4@osu. Steve Wohlwend Scheerens. requires prior specific permission and/or a fee. all design and testing choices must be compatible with this document.edu Copyright Notice Permission to make digital or hard copies of all of this work for personal or 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.4@osu. The Systems Requirements Specification includes a description of every input into the system. To copy otherwise.doc CSE772.8@osu. to republish. every output from the system and all functions performed by the system in response to input or in support of an output. Abstracting with credit is permitted. and development requirements of this product and serves as the fundamental requirements document for the development of the product. May 9. 2009 December 5.

2.3.1.3.2.1.1. 2. 2.2 Sections: 2.5.2 Sections: 1.4.0 1.2. 2.2 Description Initial Project Description Sections: 2. 1. 2.1 1.4 Author Tyler Scheerens Tyler Scheerens Steve Wohlwend Ahsan Proprietary and Confidential iii .1.Product Requirements Document Revision History CSE 772 Project IQ Social Networking Component Revision History Date 4/23/2009 4/28/2009 5/09/2009 Revision 1.1. 2.1.1. 2.

..................................1 1.1.................... System Mission ................ FUNCTIONAL OBJECTIVES...... Design Standards Compliance................1.......................... Site Adaptation Constraints................................................... PRODUCT FUNCTIONS ...............................................................3...............................................3..4 3..2 2.................................................................2.............................1 2..................... System Functions / Responsibilities ..............................1.................................................3 2................3 3............................................................. Project Scope. PROJECT ABSTRACT......................................................3 2........2.............................................3....1............................ USE CASE DIAGRAM .2................1.................2............ DEFINITIONS......................3....1 2................................................................................................. Background........................................................................1 4...................................................................................................................................................... CONTEXT DIAGRAM........................1 2......................................................................................................................... SYSTEM EVENTS AND DATA FLOWS.3.2......................................................................................2 4............. System Purpose................................... SYSTEM CONSTRAINTS .......................3.......................................................7.......................... Operational Constraints.....................................1 1................................................................5..................................4............................................................. USE CASES.................................................................................................................................................................... INTRODUCTION.........................................................3...............1 2............2.......1... Hardware Constraints......................................................................................................................................................................................................... SCOPE............. Data Management Constraints...ORGANIZED BY SUBSYSTEM...............3..........................................................2 iv Proprietary and Confidential Ahsan .....1 1...............................2 2......................................................................................1............................................................................................................................................3 2.........................4............................CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction Table of Contents 1... Use Case Scenario <#>...............4 3...................................................................................................4.....................3...........4......3 2..........................3.................................................................................5 3...................5..................................................1....................... OVERALL DESCRIPTION.......3............. OTHER CONSTRAINTS............ User Interface Constraints ............................................................1 1...............3 2........3 2.........................................................1 2.........1...............................4 3.................3............................3 2...................................................................................................1.....................3 2........1................................5..............1 4.........................5 4..2 2....................................................................... Software Constraints...................................................... PURPOSE...................................................1 1.............................................3.................... EVENT TABLE.............................................................. USER CHARACTERISTICS........................................................................................................................................................... REFERENCES......2 2.............1.........4..........................8........... STANDARDS............. Communications Constraints........................................1 2..........................................................6...............................................................................................................2..............................SYSTEM ACTIVITIES ...... SPECIFIC REQUIREMENTS.............................

VALIDATED OBJECT MODEL..3 4.........................................................................................Product Requirements Document Revision History CSE 772 Project IQ Social Networking Component 4....................................................1......................4 5........................................2................3 5............... CLASS DIAGRAM..........................................................................................................2............................3.............2.................. Use Case <#> Prototype.....................................................4 5............................... Use Case <#> Object Interaction Diagram .................................................................5 Ahsan Proprietary and Confidential v ... CLASS SPECIFICATIONS..............................2......

Burd.Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 1. The Object Oriented Approach Concepts. Satzinger. 1. References This is a complete list of all documents referenced elsewhere in this document. Introduction 1. 1. 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. Orvik. 1. Scope The Social Networking component integrates the open source Yet Another Forum message board code. 2nd edition. 1. Ahsan Proprietary and Confidential 1 . Satzinger. It finally includes an appraisal hosting and uploading system. 2.Database This section contains a list of definitions for organizational specific words that are not universal. 1. Definitions GUI – Graphical User Interface WSID – Workstation Identification Number DB .3.4. user comment system. 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.2. IEEE 830-1993 – The content and qualities of a good Systems Requirements Specification (SRS) are described and several sample SRS outlines are presented. Standards This is a complete list of all standards used in this document.5. Purpose The Project IQ Social Networking Component provides the functionality of a message board. System Development and Modeling with UML. 1. and a means of uploading appraisals. Jackson. 3rd edition. Systems Analysis and Design in a Changing World .

The system being developed will provide a multipurpose tool for handling a variety of tasks associated with these properties. real estate agents. Tyler Scheerens.2. including providing a tool to locate other properties sold in the area. A second component will gather all GIS data and pictures associated with a home. it provides a background for those requirements. Project Scope Property IQ will be a real estate property and foreclose tool giving users access to statistical data.1. or comment and attach information on specific properties. and makes them easier to understand. Background A recent credit crisis in the United States has led to a significant increase in the number of distressed and foreclosed homes. This document deals with the social networking component. The fourth group will provide a social networking aspect to the website. 2. number of bedrooms. • • • System Purpose Who Mortgage brokers.3. which are defined in detail in section 3. tools to help model past and future values of the property.1. Erdem Myalcin. Kim 9 May 2009 Project Name: Authors: Date: 2. 2. Things like recent selling price. 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.1. This section does not state specific requirements.1. and a social networking aspect that allows users to communicate with each on a dedicated forum. Instead. Project Abstract Project IQ Social Networking Component Steve Wohlwend.Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 2.1. prospective home buyers Where The system will be web-based and accessible to all users. One component of the mashup will show static information on all properties in an area. or post information on specific listed properties. Overall Description This section of the SRS describes the general factors that affect the product and its requirements. and other commonly available information. 2. What Scope: o The system will be responsible for providing up to date information on all properties in an area and allow users to Proprietary and Confidential 1 Ahsan . maps and pictures of all real estate properties in an area. enabling users to post on real esate-related message boards.

behavior. 2. The ability to attach appraisal information to a specific property.1. 4. 2. System Functions / Responsibilities 1. 4. 5. System Constraints System Constraints restrict options of design. post images and other related data. System Mission foreclosure mashup that will of a user discussion board. 2. Functional Objectives 1. System Constraints describe how the product operates inside various circumstances and limit the options designers have if building the product. 2. Develop a simple and efficient search feature to find topics and information on specific properties. and discuss the property with other users. Listing resource where users can list or begin discussions about specific properties. allowing users to post real estate related discussion topics on the site. 3.CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction communicate on general topics or specific properties. 2.4. • Why A credit crisis in the United States has led to a high number distressed and foreclosed properties. 2. The system shell provide the ability for users to register and login before they are allowed to interact with the social networking aspect of the web site. The system shall provide hosting for and the ability to upload appraisal documents for appropriate users. Develop and manage a user registration and login system for the web site. Discussion board available to mashup users to discuss relevant real estate and foreclosure topics. o The system will not allow users to buy and sell properties on the site. The system shall provide a user message board.3. The system shall provide the ability for users to post topics on specific properties. This section specifies design constraints imposed by other standards. and price models).5. This aspect will also list information available from other components of the mashup that are relevant to the specific property (hard data. 2 Proprietary and Confidential Ahsan . That appraisal information will be shared with the trends component of the mashup to make better price projections on a given property.1. appearance or operation. 3. allowing users to request information on said property. maps. They become requirements due to factors outside the normal problem domain. a topics dedicated to specific about that property can be Build a social networking component for a real estate and allow user interaction with the real estate system in the form property listing service. and the ability for users to post properties where information like pictures and appraisals posted.2.

2. 2.3. 2.3.3. Other Constraints Ahsan Proprietary and Confidential 3 . 2. Software Constraints The system is designed to run on Firefox 3 and Internet Explorer 7.6. None. • Design Standards Compliance The system shall be implemented in ASP 2. Data Management Constraints This is a detailed description of constraints for data flow to data management software and equipment outside the scope of the project.7.1. refer to those components' documentation for details.8.3.3.2.4. Other components of the Property IQ system may require access to certain data and web services. There are a number of attributes of software that can serve as requirements. communication interface limitations.3. For example.3.Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component hardware limitations.4.5. etc. 2. Operational Constraints • The system is limited by its operating server in terms of the maximum number of users it can support at a given time 2. 2.3.3. Hardware Constraints The system should work on most home desktop and laptop computers. User Interface Constraints Using this system is fairly simple and intuitive. Site Adaptation Constraints The component will be adapted to the overarching system at the conclusion of the system creation. A user familiar with basic browser navigation skills should be able to understand all functionality provided by the system. • System must export financial data to a financial data management program (gnucash) 2. Communications Constraints System must have access to the included database.

or system. sinks of data and control that flows into and out of a system. System Events and Data Flows 3. Context Diagram Context diagrams use data flow diagramming (DFD) notation to illustrate the scope of a problem and the source. May be a person. <external: data source or destination> <inflow: group data item> <inflow: group data item> <external: data source or destination> <system name> <outflow: group data item> <external: data source or destination> <outflow: group data item> 4 Proprietary and Confidential Ahsan .CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction 3. If only internal effects are made.] Activity [system process that results from trigger] Response [data that system produces. this is left blank.2. Event [Occurrences at a specific time and place that trigger system processing] Event Table Trigger [data inflow or time that system detects] Source [ultimate creator of trigger. then this is ‘n/a’] Destination [ultimate destination of data response. department. If event type is temporal.] 3.1.

experience. <repeat for all users and system externals> Ahsan Proprietary and Confidential 5 . <system name> users consist of the following: • • Managers who wish to perform system administration functions as well as export company financial information.Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 3.System Activities This subsection of the SRS provides a summary of the major processes that the software will perform. and technical expertise.2. User Characteristics User Characteristics describe those general characteristics of the intended users of the product including educational level.1 [Activity] [Description] <repeat for all activities> 3. which includes the system tasks and features from the Product Requirements document and Project Charter.3.4. 2. Product Functions .

Note: Use Cases are in priority order. Use Case Diagram .1. Testers can use this section to test that the system satisfies those requirements and technical writers can create the necessary support documentation for operations and maintenance.organized by subsystem <verb obj> <user> <system name subsystem name> Ahsan Proprietary and Confidential 1 .Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 4. 4. Specific Requirements This section of the SRS contains all the system requirements to a level of detail sufficient to enable designers to design a system that satisfies those requirements.

A Use Case without any input or output is not valid. Use Case Scenario <#> <Use Case Name> Purpose Actor Input Data Output Data Invariants A brief description of what the user is trying to accomplish. All exception and error cases. A condition which is maintained throughout the use case. which may contain subflows. This section is used to highlight assumptions made for the sake of the use case. and will not be true when the use case completes. A list of all external data needed for the use case to be performed. A single. A list of all data produced by the use case execution.CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction 4. Conditions which must hold for the use case to be applicable. etc. error-free path.2. The detailed requirements of a Use Case tend to be extensive. For this reason.1. logical structures. A person or external system outside the scope of the system that triggers step one of the Detailed Description. Conditions which are guaranteed to hold after completion of the use case. This section provides descriptions of all the use cases devised for this system. Pre-conditions Post-conditions Basic Flow: Alternative Flow(s): Extension Points: Business Rules: Notes 2 Proprietary and Confidential Ahsan . calculations. including where/how they were triggered <<includes>> and <<extends>> cases and where they were referenced The rationale for this case. It is assumed that these conditions are true prior to the beginning of the use case.2. A Use Case may have multiple inputs or outputs as part of the same functional flow. Use Cases Use Cases are requirements from the Client translated into unambiguous language. it is recommended that careful consideration be given to organizing the requirements in a manner optimal for understanding. Subcases are identical to use cases except where noted. Each use case description provides the following information: 4. also explains exceptions and errors Any other relevant information not included in the above sections.

] 4.2. Use Case <#> Object Interaction Diagram [Sequence or Collaboration diagram showing all participating classes and messages that trigger response for basic and alternate flows.2.2.Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 4. Use Case <#> Prototype [Complete set of simple discovery prototypes showing all user interaction for basic and alternate flows.3.] <… repeat for all Use Cases…> Ahsan Proprietary and Confidential 3 .

Class Diagram The Class diagram shows the structural scope-of control.CSE 772 Project IQ Social Networking Component Systems Requirements Specification Introduction 5. Validated Object Model The Validated Object Model is a visual representation of the idealized problem domain.1. 5. The consistency between the Sequence Diagrams and the Object model validates the requirements.entities and relationships in the problem domain of the Object Model. <class name> <attributes> <methods> <class name> <attributes> <methods> <class name> <attributes> <methods> 4 Proprietary and Confidential Ahsan .

Systems Requirements Specification Introduction CSE 772 Project IQ Social Networking Component 5. <repeat for each class> Class Parent Description Attributes <attribute name> <description> <class name> <if any> <in prose> Methods <method name> <description and any parameters> Ahsan Proprietary and Confidential 5 .2. Class Specifications Class Specifications are the prose detail necessary to elaborate the definitions of each class attribute and algorithm of each class operation.

Sign up to vote on this title
UsefulNot useful