Sample SRS For Social Networking Website

5/20/2018 Sample SRS For Social Networking Website

1/16

Group 3

Project IQ Social Networking Component

Systems Requirements Specification

Version 1.1

pril !"# !$$%

Copyright 2009 by , and


2/16

CSE 772 Systems Requirements SpecificationProject IQ Social Networin! Component Intro"uction

#$out %&is 'ocument

Purpose of t&is'ocument

The Systems Requirements Specification SRS! is designed to e"press thebeha#ioral, performance, and de#elopment requirements of this product andser#es as the fundamental requirements document for the de#elopment of

the product$ The Systems Requirements Specification includes adescription of e#ery input into the system, e#ery output from the system andall functions performed by the system in response to input or in support ofan output$ The SRS meets %&&&'(0 standards and is the e"clusi#erequirements document to be used in de#elopment) all design and testingchoices must be compatible *ith this document$

'ocumentPrepare" for

+hio State CS& 2

Inten"e"#u"ience

-an.s in possession of foreclosed property

'ate ofPu$lication

/ast sa#ed 1ay 9, 2009This printing September ', 203

Pa!e Count pages

'ocument(ocation

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!&tNotice

5ermission to ma.e digital or hard copies of all of this *or. for personal orclassroom use is granted *ithout fee pro#ided that copies are not made ordistributed for commercial ad#antage and that copies bear this notice andthe full citation on the first page$ 8bstracting *ith credit is permitted$ To copyother*ise, to republish, to post on ser#ers, or to redistribute to lists, requiresprior specific permission andor a fee$ Request permission to republish fromTyler Scheerens $

ii Proprietary an" Confi"ential sc&eeren


3/16

Pro"uct Requirements 'ocument CSE 772Re*ision +istory Project IQ Social Networin! Component

Re*ision +istory

'ate Re*ision 'escription #ut&or

32(2009 $0 %nitial 5ro:ect ;escriptionSections 2$$3, 2$$, 2$2 Tyler Scheerens

32'2009 $ Sections 2$$, 2$$2, 2$$(, 2$2 Tyler Scheerens

092009 $2 Sections $, $2, 2$(, 2$3 Ste#e 6ohl*end

sc&eeren Proprietary an" Confi"ential iii


4/16


%a$le of Contents

,- IN%R.'/C%I.N------------------------------------------------------------------------------------------------------------------------------------- ,

$$ 5=R5+S&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$2$ SC+5&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$($ R&&R&?C&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$3$ ST8?;8R;S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$$ ;&%?%T%+?S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2

2- .0ER#(( 'ESCRIP%I.N---------------------------------------------------------------------------------------------------------------------- ,

2$$ 5R+@&CT8-STR8CT$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

2$$$ 5ro:ect Scope$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

2$$2$ -ac.ground$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

2$$($ System 5urpose$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

2$$3$ System 1ission $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$2

2$$$ System unctions Responsibilities $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$2

2$2$ =?CT%+?8/+-@&CT%A&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2

2$($ SBST&1C+?STR8%?TS $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (

2$($$ =ser %nterface Constraints $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ (

2$($2$ ard*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$ +T&RC+?STR8%?TS$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

3- S1S%E E0EN%S #N' '#%# )(.S--------------------------------------------------------------------------------------------------4

($$ &A&?TT8-/&$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ D

($2$ C+?T&ET;%8FR81$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$D

($($ 5R+;=CT=?CT%+?SG SBST&18CT%A%T%&S $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ ($3$ =S&RC8R8CT&R%ST%CS$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

5- SPECI)IC REQ/IREEN%S------------------------------------------------------------------------------------------------------------------ ,

3$$ =S&C8S&;%8FR81G +RF8?%H&;-BS=-SBST&1$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

3$2$ =S&C8S&S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 2

3$2$$ =se Case Scenario $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$2

i* Proprietary an" Confi"ential sc&eeren


5/16

Pro"uct Requirements 'ocument CSE 772Re*ision +istory Project IQ Social Networin! Component

3$2$2$ =se Case 5rototype$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$(

3$2$($ =se Case +b:ect %nteraction ;iagram $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ $$$$(

6- 0#(I'#%E' .8EC% .'E(--------------------------------------------------------------------------------------------------------------- 5

$$ C/8SS;%8FR81$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 3

$2$ C/8SSS5&C%%C8T%+?S$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

sc&eeren Proprietary an" Confi"ential *


6/16

Systems Requirements Specification CSE 772Intro"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, usercomment system, and a means of uploading appraisals$

1.2. Scope

The Social ?et*or.ing component integrates the open source Bet 8nother orum message boardcode$ %t also in#ol#es modification to the 5roperty %J master page to integrate a user loginsystem$ %t includes a nested page for each property that lists forum threads about that particularproperty$ %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$

$ 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$

$ %&&& '(0G99( L The content and qualities of a good Systems Requirements SpecificationSRS! are described and se#eral sample SRS outlines are presented$ This recommendedpractice is aimed at specifying requirements of soft*are to be de#eloped but also can beapplied 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 ,


7/16


2. .*erall 'escription

This section of the SRS describes the general factors that affect the product and its requirements$ Thissection 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 tostatistical data, maps and pictures of all real estate properties in an area, tools to helpmodel past and future #alues of the property, and a social net*or.ing aspect that allo*susers to communicate *ith each on a dedicated forum, or post information on specificlisted properties$ This document deals *ith the social net*or.ing component$

2.1.2. ac!roun"

8 recent credit crisis in the =nited States has led to a significant increase in the number ofdistressed and foreclosed homes$ The system being de#eloped *ill pro#ide a multiGpurpose 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#ailableinformation$

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 oninformation 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 topost on real esateGrelated message boards, or comment and attach information on specificproperties$

2.1.3. System Purpose

&o1ortgage bro.ers, real estate agents, prospecti#e home buyers

&ereThe system *ill be *ebGbased and accessible to all users$

&atScope

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



8/16


topics or specific properties$

o The system *ill not allo* users to buy and sell properties on the site$

&y8 credit crisis in the =nited States has led to a high number distressed

and foreclosed properties$

2.1.4.System ission

-uild a social net*or.ing component for a real estate and foreclosure mashup that *illallo* user interaction *ith the real estate system in the form of a user discussion board, aproperty listing ser#ice, and the ability for users to post topics dedicated to specificproperties *here information li.e pictures and appraisals about that property can beposted$

2.1.5. System )unctions : Responsi$ilities

$ ;iscussion board a#ailable to mashup users to discuss rele#ant real estate andforeclosure topics$

2$ /isting resource *here users can list or begin discussions about specific properties$ Thisaspect *ill also list information a#ailable from other components of the mashup that arerele#ant to the specific property hard data, maps, and price models!$

($ The ability to attach appraisal information to a specific property$ That appraisalinformation *ill be shared *ith the trends component of the mashup to ma.e better pricepro:ections on a gi#en property$

3$ ;e#elop a simple and efficient search feature to find topics and information on specificproperties$

$ ;e#elop and manage a user registration and login system for the *eb site$

2.2. )unctional .$jecti*es

$ The system shall pro#ide a user message board, allo*ing users to post realestate 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 otherrelated data, and discuss the property *ith other users$

($ The system shell pro#ide the ability for users to register and login before they areallo*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 becomerequirements due to factors outside the normal problem domain$ System Constraints describeho* the product operates inside #arious circumstances and limit the options designers ha#e ifbuilding the product$ This section specifies design constraints imposed by other standards,hard*are limitations, communication interface limitations, etc$ There are a number of attributes ofsoft*are that can ser#e as requirements$

2 Proprietary an" Confi"ential sc&eeren


9/16


2.3.1. /ser Interface Constraints

=sing this system is fairly simple and intuiti#e$ 8 user familiar *ith basic bro*serna#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 thosecomponentsN documentation for details$

2.3.5.'ata ana!ement Constraints

This is a detailed description of constraints for data flo* to data management soft*areand 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 ConstraintsThe component *ill be adapted to the o#erarching system at the conclusion of thesystem 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


10/16


3. System E*ents an" 'ata )lows

3.1. E*ent %a$le

E*ent %ri!!er Source #cti*ity Response 'estination

O+ccurrencesat a specifictime and placethat triggersystemprocessingP

Odata inflo* ortime thatsystemdetectsP

Oultimatecreator oftrigger$ 1ay bea person,department, orsystem$ %fe#ent type istemporal, thisis left blan.$P

Osystemprocess thatresults fromtriggerP

Odata thatsystemproduces$ %fonly internaleffects aremade, then thisis QnaP

Oultimatedestination odata respon

3.2. Conte;t 'ia!ram

Conte"t diagrams use data flo* diagramming ;;! notation to illustrate the scope of a problemand the source, sin.s of data and control that flo*s into and out of a system$



11/16


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 *illperform, *hich includes the system tas.s and features from the 5roduct Requirements document

and 5ro:ect Charter$2$2$ O8cti#ityP

O;escriptionP

3.4. /ser C&aracteristics

=ser Characteristics describe those general characteristics of the intended users of the productincluding educational le#el, e"perience, and technical e"pertise$

users consist of the follo*ing

1anagers *ho *ish to perform system administration functions as *ell as e"port

company financial information$


12/16


4. Specific Requirements

This section of the SRS contains all the system requirements to a le#el of detail sufficient to enabledesigners 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 supportdocumentation for operations and maintenance$ ?ote =se Cases are in priority order$

4.1. /se Case 'ia!ram < or!ani=e" $y su$system



13/16


4.2. /se Cases

=se Cases are requirements from the Client translated into unambiguous language$ 8 =se Casemay ha#e multiple inputs or outputs as part of the same functional flo*$ 8 =se Case *ithout anyinput or output is not #alid$ The detailed requirements of a =se Case tend to be e"tensi#e$ orthis 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 information

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 beperformed$

.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$ Thissection is used to highlight assumptions made for the sa.e ofthe use case$

Pre> cases and *here they *erereferenced

usiness Rules9 The rationale for this case, also e"plains e"ceptions and errors

Notes 8ny other rele#ant information not included in the abo#esections$



14/16


4.2.2. /se Case >?@ Prototype

OComplete set of simple disco#ery prototypes sho*ing all user interaction for basic andalternate flo*s$P

4.2.3. /se Case >?@ .$ject Interaction 'ia!ram

OSequence or Collaboration diagram sho*ing all participating classes and messages thattrigger response for basic and alternate flo*s$P



15/16


5. 0ali"ate" .$ject o"el

The Aalidated +b:ect 1odel is a #isual representation of the idealiKed problem domain$ The consistencybet*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 theproblem domain of the +b:ect 1odel$



16/16


5.2. Class Specifications

Class Specifications are the prose detail necessary to elaborate the definitions of eachclass attribute and algorithm of each class operation$

Class

5arent

;escription

8ttributes

1ethods


Documents

Sample SRS For Social Networking Website