Sample SRS For Social Networking Website

Group 3
Project IQ Social Networking Component

Systems Requirements Specification
Version 1.1
pril !"# !$$%
Copyright 2009 by <client name>, and <team name>
CSE 772 Systems Requirements Specification
Project IQ Social Networin! Component Intro"uction
#$out %&is 'ocument
Purpose of t&is
'ocument
The Systems Requirements Specification SRS! is designed to e"press the
beha#ioral, performance, and de#elopment requirements of this product and
ser#es as the fundamental requirements document for the de#elopment of
the product$ The Systems Requirements Specification includes a
description of e#ery input into the system, e#ery output from the system and
all functions performed by the system in response to input or in support of
an output$ The SRS meets %&&&'(0 standards and is the e"clusi#e
requirements document to be used in de#elopment) all design and testing
choices must be compatible *ith this document$
'ocument
Prepare" for
+hio State CS& ,,2
Inten"e"
#u"ience
-an.s in possession of foreclosed property
'ate of
Pu$lication
/ast sa#ed0 1ay 9, 2009
This printing0 September ', 2023
Pa!e Count <nn> pages
'ocument
(ocation
<path>
Prepare" )rom SRS4+utline$doc
#ssociate"
Proce"ures
CS&,,2, %nformation Systems Capstone, S509
Prepare" $y Tyler Scheerens, Ste#e 6ohl*end
Scheerens$37osu$edu, *ohl*end$'7osu$edu
Copyri!&t
Notice
5ermission to ma.e digital or hard copies of all of this *or. for personal or
classroom use is granted *ithout fee pro#ided that copies are not made or
distributed for commercial ad#antage and that copies bear this notice and
the full citation on the first page$ 8bstracting *ith credit is permitted$ To copy
other*ise, to republish, to post on ser#ers, or to redistribute to lists, requires
prior specific permission and9or a fee$ Request permission to republish from
Tyler Scheerens <scheerens$37osu$edu>$
ii Proprietary an" Confi"ential sc&eeren
Pro"uct Requirements 'ocument CSE 772
Re*ision +istory Project IQ Social Networin! Component
Re*ision +istory
'ate Re*ision 'escription #ut&or
392(92009 2$0 %nitial 5ro:ect ;escription
Sections0 2$2$3, 2$2$<, 2$2
Tyler Scheerens
392'92009 2$2 Sections0 2$2$2, 2$2$2, 2$2$(, 2$2 Tyler Scheerens
<90992009 2$2 Sections0 2$2, 2$2, 2$(, 2$3 Ste#e 6ohl*end
sc&eeren Proprietary an" Confi"ential iii
%a$le of Contents
,- IN%R.'/C%I.N------------------------------------------------------------------------------------------------------------------------------------- ,
2$2$ 5=R5+S&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$ SC+5&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$($ R&>&R&?C&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$3$ ST8?;8R;S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$<$ ;&>%?%T%+?S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2- .0ER#(( 'ESCRIP%I.N---------------------------------------------------------------------------------------------------------------------- ,
2$2$ 5R+@&CT 8-STR8CT$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$2$ 5ro:ect Scope$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$2$ -ac.ground$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$($ System 5urpose$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$3$ System 1ission $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$<$ System >unctions 9 Responsibilities $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$2$ >=?CT%+?8/ +-@&CT%A&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
2$($ SBST&1 C+?STR8%?TS $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
2$($2$ =ser %nterface Constraints $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
2$($2$ Card*are Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
2$($($ Soft*are Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
2$($3$ Communications Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3
2$($<$ ;ata 1anagement Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3
2$($D$ +perational Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3
2$($,$ Site 8daptation Constraints$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3
2$($'$ ;esign Standards Compliance$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ <
2$3$ +TC&R C+?STR8%?TS$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ <
3- S1S%E2 E0EN%S #N' '#%# )(.3S-------------------------------------------------------------------------------------------------- 4
($2$ &A&?T T8-/&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ D
($2$ C+?T&ET ;%8FR81$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ D
($($ 5R+;=CT >=?CT%+?S G SBST&1 8CT%A%T%&S $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ ,
($3$ =S&R CC8R8CT&R%ST%CS$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ ,
5- SPECI)IC REQ/IRE2EN%S------------------------------------------------------------------------------------------------------------------ ,
3$2$ =S& C8S& ;%8FR81 G +RF8?%H&; -B S=-SBST&1$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
3$2$ =S& C8S&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
3$2$2$ =se Case Scenario <I>$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2
i* Proprietary an" Confi"ential sc&eeren
Pro"uct Requirements 'ocument CSE 772
Re*ision +istory Project IQ Social Networin! Component
3$2$2$ =se Case <I> 5rototype$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
3$2$($ =se Case <I> +b:ect %nteraction ;iagram $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (
6- 0#(I'#%E' .78EC% 2.'E(--------------------------------------------------------------------------------------------------------------- 5
<$2$ C/8SS ;%8FR81$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3
<$2$ C/8SS S5&C%>%C8T%+?S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ <
sc&eeren Proprietary an" Confi"ential *
Systems Requirements Specification CSE 772
Intro"uction Project IQ Social Networin! Component
1. Intro"uction
1.1. Purpose
The 5ro:ect %J Social ?et*or.ing Component pro#ides the functionality of a message board, user
comment system, and a means of uploading appraisals$
1.2. Scope
The Social ?et*or.ing component integrates the open source Bet 8nother >orum message board
code$ %t also in#ol#es modification to the 5roperty %J master page to integrate a user login
system$ %t includes a nested page for each property that lists forum threads about that particular
property$ %t finally includes an appraisal hosting and uploading system$
1.3. References
This is a complete list of all documents referenced else*here in this document$
2$ Systems 8nalysis and ;esign in a Changing 6orld , SatKinger, -urd, @ac.son, (rd edition$
2$ The +b:ect +riented 8pproach Concepts, System ;e#elopment and 1odeling *ith =1/,
SatKinger, +r#i., 2nd edition$
1.4. Stan"ar"s
This is a complete list of all standards used in this document$
2$ %&&& '(0G299( L The content and qualities of a good Systems Requirements Specification
SRS! are described and se#eral sample SRS outlines are presented$ This recommended
practice is aimed at specifying requirements of soft*are to be de#eloped but also can be
applied to assist in the selection of inGhouse and commercial soft*are products$
1.5. 'efinitions
This section contains a list of definitions for organiKational specific *ords that are not uni#ersal$
F=% L Fraphical =ser %nterface
6S%; L 6or.station %dentification ?umber
;- G ;atabase
sc&eeren Proprietary an" Confi"ential ,
2. .*erall 'escription
This section of the SRS describes the general factors that affect the product and its requirements$ This
section does not state specific requirements$ %nstead, it pro#ides a bac.ground for those requirements,
*hich are defined in detail in section (, and ma.es them easier to understand$
2.1. Project #$stract
Project Name9 5ro:ect %J Social ?et*or.ing Component
#ut&ors9 Ste#e 6ohl*end, Tyler Scheerens, &rdem 1yalcin, Mim
'ate9 9 1ay 2009
2.1.1. Project Scope
5roperty %J *ill be a real estate property and foreclose tool gi#ing users access to
statistical data, maps and pictures of all real estate properties in an area, tools to help
model past and future #alues of the property, and a social net*or.ing aspect that allo*s
users to communicate *ith each on a dedicated forum, or post information on specific
listed properties$ This document deals *ith the social net*or.ing component$
2.1.2. 7ac!roun"
8 recent credit crisis in the =nited States has led to a significant increase in the number of
distressed and foreclosed homes$ The system being de#eloped *ill pro#ide a multiG
purpose tool for handling a #ariety of tas.s associated *ith these properties$
+ne component of the mashup *ill sho* static information on all properties in an area$
Things li.e recent selling price, number of bedrooms, and other commonly a#ailable
information$
8 second component *ill gather all F%S data and pictures associated *ith a home,
including pro#iding a tool to locate other properties sold in the area$
The third component *ill pro#ide trends data on the future price of the home based on
information gathered by the statistical data group and an in house de#eloped formula$
The fourth group *ill pro#ide a social net*or.ing aspect to the *ebsite, enabling users to
post on real esateGrelated message boards, or comment and attach information on specific
properties$
2.1.3. System Purpose
3&o 1ortgage bro.ers, real estate agents, prospecti#e home buyers
3&ere The system *ill be *ebGbased and accessible to all users$
3&at Scope0
o The system *ill be responsible for pro#iding up to date information on
all properties in an area and allo* users to communicate on general
topics or specific properties$
o The system *ill not allo* users to buy and sell properties on the site$
3&y 8 credit crisis in the =nited States has led to a high number distressed
and foreclosed properties$
2.1.4. System 2ission
-uild a social net*or.ing component for a real estate and foreclosure mashup that *ill
allo* user interaction *ith the real estate system in the form of a user discussion board, a
property listing ser#ice, and the ability for users to post topics dedicated to specific
properties *here information li.e pictures and appraisals about that property can be
posted$
2.1.5. System )unctions : Responsi$ilities
2$ ;iscussion board a#ailable to mashup users to discuss rele#ant real estate and
foreclosure topics$
2$ /isting resource *here users can list or begin discussions about specific properties$ This
aspect *ill also list information a#ailable from other components of the mashup that are
rele#ant to the specific property hard data, maps, and price models!$
($ The ability to attach appraisal information to a specific property$ That appraisal
information *ill be shared *ith the trends component of the mashup to ma.e better price
pro:ections on a gi#en property$
3$ ;e#elop a simple and efficient search feature to find topics and information on specific
properties$
<$ ;e#elop and manage a user registration and login system for the *eb site$
2.2. )unctional .$jecti*es
2$ The system shall pro#ide a user message board, allo*ing users to post real
estate related discussion topics on the site$
2$ The system shall pro#ide the ability for users to post topics on specific properties,
allo*ing users to request information on said property, post images and other
related data, and discuss the property *ith other users$
($ The system shell pro#ide the ability for users to register and login before they are
allo*ed to interact *ith the social net*or.ing aspect of the *eb site$
3$ The system shall pro#ide hosting for and the ability to upload appraisal
documents for appropriate users$
2.3. System Constraints
System Constraints restrict options of design, beha#ior, appearance or operation$ They become
requirements due to factors outside the normal problem domain$ System Constraints describe
ho* the product operates inside #arious circumstances and limit the options designers ha#e if
building the product$ This section specifies design constraints imposed by other standards,
hard*are limitations, communication interface limitations, etc$ There are a number of attributes of
soft*are that can ser#e as requirements$
2 Proprietary an" Confi"ential sc&eeren
2.3.1. /ser Interface Constraints
=sing this system is fairly simple and intuiti#e$ 8 user familiar *ith basic bro*ser
na#igation s.ills should be able to understand all functionality pro#ided by the system$
2.3.2. +ar"ware Constraints
The system should *or. on most home des.top and laptop computers$
2.3.3. Software Constraints
The system is designed to run on >irefo" ( and %nternet &"plorer ,$
2.3.4. Communications Constraints
System must ha#e access to the included database$ +ther components of the 5roperty
%J system may require access to certain data and *eb ser#ices) refer to those
componentsN documentation for details$
2.3.5. 'ata 2ana!ement Constraints
This is a detailed description of constraints for data flo* to data management soft*are
and equipment outside the scope of the pro:ect$
>or e"ample,
System must e"port financial data to a financial data management program
gnucash!
2.3.6. .perational Constraints
The system is limited by its operating ser#er in terms of the ma"imum number of
users it can support at a gi#en time
2.3.7. Site #"aptation Constraints
The component *ill be adapted to the o#erarching system at the conclusion of the
system creation$
2.3.8. 'esi!n Stan"ar"s Compliance
The system shall be implemented in 8S5
2.4. .t&er Constraints
?one$
sc&eeren Proprietary an" Confi"ential 3
3. System E*ents an" 'ata )lows
3.1. E*ent %a$le
E*ent %ri!!er Source #cti*ity Response 'estination
O+ccurrences
at a specific
time and place
that trigger
system
processingP
Odata inflo* or
time that
system
detectsP
Oultimate
creator of
trigger$ 1ay be
a person,
department, or
system$ %f
e#ent type is
temporal, this
is left blan.$P
Osystem
process that
results from
triggerP
Odata that
system
produces$ %f
only internal
effects are
made, then this
is Qn9aRP
Oultimate
destination of
data response$P
3.2. Conte;t 'ia!ram
Conte"t diagrams use data flo* diagramming ;>;! notation to illustrate the scope of a problem
and the source, sin.s of data and control that flo*s into and out of a system$
<system
name>
<e"ternal0 data
source or
destination>
<e"ternal0 data
source or
destination>
<e"ternal0 data
source or
destination>
<outflo*0 group
data item>
<outflo*0 group
data item>
<inflo*0 group
data item>
<inflo*0 group
data item>
3.3. Pro"uct )unctions < System #cti*ities
This subsection of the SRS pro#ides a summary of the ma:or processes that the soft*are *ill
perform, *hich includes the system tas.s and features from the 5roduct Requirements document
and 5ro:ect Charter$
2$2$2 O8cti#ityP
O;escriptionP
<repeat for all acti#ities>
3.4. /ser C&aracteristics
=ser Characteristics describe those general characteristics of the intended users of the product
including educational le#el, e"perience, and technical e"pertise$
<system name> users consist of the follo*ing0
1anagers *ho *ish to perform system administration functions as *ell as e"port
company financial information$
<repeat for all users and system e"ternals>
4. Specific Requirements
This section of the SRS contains all the system requirements to a le#el of detail sufficient to enable
designers to design a system that satisfies those requirements$ Testers can use this section to test that
the system satisfies those requirements and technical *riters can create the necessary support
documentation for operations and maintenance$ ?ote0 =se Cases are in priority order$
4.1. /se Case 'ia!ram < or!ani=e" $y su$system
<user>
<system name G
subsystem name>
<verb
obj>
4.2. /se Cases
=se Cases are requirements from the Client translated into unambiguous language$ 8 =se Case
may ha#e multiple inputs or outputs as part of the same functional flo*$ 8 =se Case *ithout any
input or output is not #alid$ The detailed requirements of a =se Case tend to be e"tensi#e$ >or
this reason, it is recommended that careful consideration be gi#en to organiKing the requirements
in a manner optimal for understanding$ Subcases are identical to use cases e"cept *here noted$
This section pro#ides descriptions of all the use cases de#ised for this system$
&ach use case description pro#ides the follo*ing information0
4.2.1. /se Case Scenario >?@
>/se Case Name@
Purpose
8 brief description of *hat the user is trying to accomplish$
#ctor
8 person or e"ternal system outside the scope of the system
that triggers step one of the ;etailed ;escription$
Input 'ata
8 list of all e"ternal data needed for the use case to be
performed$
.utput 'ata
8 list of all data produced by the use case e"ecution$
In*ariants
8 condition *hich is maintained throughout the use case$ This
section is used to highlight assumptions made for the sa.e of
the use case$
Pre<con"itions
Conditions *hich must hold for the use case to be applicable$
%t is assumed that these conditions are true prior to the
beginning of the use case, and *ill not be true *hen the use
case completes$
Post<con"itions
Conditions *hich are guaranteed to hold after completion of
the use case$
7asic )low9
8 single, errorGfree path, *hich may contain subflo*s,
calculations, logical structures, etc$
#lternati*e )lowAsB9
8ll e"ception and error cases, including *here9ho* they *ere
triggered
E;tension Points9
<<includes>> and <<e"tends>> cases and *here they *ere
referenced
7usiness Rules9
The rationale for this case, also e"plains e"ceptions and errors
Notes
8ny other rele#ant information not included in the abo#e
sections$
4.2.2. /se Case >?@ Prototype
OComplete set of simple disco#ery prototypes sho*ing all user interaction for basic and
alternate flo*s$P
4.2.3. /se Case >?@ .$ject Interaction 'ia!ram
OSequence or Collaboration diagram sho*ing all participating classes and messages that
trigger response for basic and alternate flo*s$P
<S repeat for all =se CasesS>
5. 0ali"ate" .$ject 2o"el
The Aalidated +b:ect 1odel is a #isual representation of the idealiKed problem domain$ The consistency
bet*een the Sequence ;iagrams and the +b:ect model #alidates the requirements$
5.1. Class 'ia!ram
The Class diagram sho*s the structural scopeGof controlG entities and relationships in the
problem domain of the +b:ect 1odel$
<class name>
<attributes>
<methods>
<class name>
<attributes>
<methods>
<class name>
<attributes>
<methods>
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$
<repeat for each class>
Class <class name>
5arent <if any>
;escription <in prose>
8ttributes
<attribute name> <description>
1ethods
<method name> <description and any parameters>

Sample SRS For Social Networking Website

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sample SRS For Social Networking Website

Uploaded by

Copyright:

Available Formats

Group 3

Project IQ Social Networking Component

You might also like