Sie sind auf Seite 1von 43

CS 4311 Fall 2004

A Virtual Supermarket for Remote Sensing Data and


Images
Version <0.91>
2004 Software Engineering II CS 42311 Fall 2004
Software Requirements Specification
6212014!ocument Control
"ppro#al
The Guidance Team and the customer shall approve this document.
!ocument C$ange Control
Initial Release: 0.1
Current Release: 0.1
Indicator o! "ast #a$e in %ocument: &
%ate o! "ast Revie': 0()2()04
%ate o! *e+t Revie': 0()31)04
Tar$et %ate !or *e+t ,pdate: 0)0-)04
!istri%ution &ist
This !ollo'in$ list o! people shall receive a cop. o! this document ever. time a ne' version o! this document
/ecomes availa/le:
Guidance Team 0em/ers:
%r. Steve Roach
%r. 1nn Gates
%r. 2oonsi3 Cheon
4mar 4choa
Customer: %r. G. Rand. 5eller
#an61merican Center !or 7arth and 7nvironmental Studies
So!t'are Team 0em/ers:
1ll6#ro$rammatic Stars
CST
Sputni3
C$ange Summar'
The !ollo'in$ ta/le details chan$es made /et'een versions o! this document
8ersion %ate 0odi!ier %escription
0.1 0-)2-)2004 4mar 4choa 0er$in$ o! %ocuments
0.2 09)0:)2004 Steve Roach Sections 1 and 2 revised
0.3 09)12)2004 4mar 4choa Chan$ed %e!initions and Section 2
0.4 0()01)2004 4mar 4choa Revised Section 2
0.- 0()1:)2004 4mar 4choa Section 3
0.: 0()20)2004 Steve Roach Section 3
0.9 0()2-)2004 Steve Roach Section 3; 1ppendices
0.( 0()29)2004 4mar 4choa ,se Case %ia$ram; 1ppendices; Section 3
0. 0()31)2004 4mar 4choa)Steve
Roach
,se Cases; Section 3; 1ppendices
0.1 0)02)2004 4mar 4choa 1ppendices
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
ii
Software Requirements Specification
T1<"7 4F C4*T7*TS
6212014!)C*+E,- C),-R)&...........................................................................................................II
1##R481"......................................................................................................II
%4C,07*T C=1*G7 C4*TR4"......................................................................II
%ISTRI<,TI4* "IST.........................................................................................II
C=1*G7 S,001R2........................................................................................II
1. I,-R)!*C-I),..................................................................................................................................../I
1.1. #,R#4S7 1*% I*T7*%7% 1,%I7*C7.......................................................8I
1.2. SC4#7 4F #R4%,CT.................................................................................8I
1.3. %7FI*ITI4*S; 1CR4*20S; 1*% 1<<R78I1TI4*S..................................8II
1.4. 487R8I7> ..............................................................................................I?
1.-. R7F7R7*C7S.............................................................................................?
2. 0E,ER"& !ESCRI(-I),...................................................................................................................1I
2.1. #R4%,CT #7RS#7CTI87...........................................................................?I
2.2. ,S7R C=1R1CT7RISTICS.........................................................................?I
2.3. #R4%,CT F71T,R7S..............................................................................?II
2.4. G7*7R1" C4*STR1I*TS......................................................................??II
2.-. 1SS,0#TI4*S 1*% %7#7*%7*CI7S.....................................................??II
3. S(ECIFIC RE2*IRE+E,-S................................................................................................................23
3.1. 7?T7R*1" I*T7RF1C7 R7@,IR707*TS.................................................23
3.2. C400,*IC1TI4*S I*T7RF1C7S ............................................................2-
3.3. <7=18I4R1" R7@,IR707*TS................................................................2-
3.4. *4*6<7=18I4R1" R7@,IR707*TS........................................................2
3.-. 4T=7R R7@,IR707*TS..........................................................................2
4. "((E,!I1 "3 4E5 ("0E -R",SI-I),S.......................................................................................31
6. "((E,!I1 53 !"-"5"SE FIE&!S ...................................................................................................33
6. "((E,!I1 C3 "/S S7S-E+ C&"SS !I"0R"+.............................................................................36
8. "((E,!I1 !3 "/S S7S-E+ !"-" F&)4 !I"0R"+.................................................................36
9. "((E,!I1 E3 "/S S7S-E+ (R)-)-7(E......................................................................................39
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
iii
Software Requirements Specification
T1<"7S
-"5&E 13 !EFI,I-I),S........................................................................................................................./II
-"5&E 23 "CR),7+S ",! "55RE/I"-I),S.................................................................................I1
-"5&E 33 "CC)*,- I,F)R+"-I),..................................................................................................33
-"5&E 43 +E-"!"-"..............................................................................................................................33
-"5&E 63 I,S-R*+E,- I,F)R+"-I),............................................................................................33
-"5&E 63 0&)SS"R7 I,F)R+"-I),.................................................................................................34
-"5&E 83 &I,: CE,-ER !"-".............................................................................................................34
FIG,R7S
6212014!)C*+E,- C),-R)&...........................................................................................................II
1##R481"......................................................................................................II
%4C,07*T C=1*G7 C4*TR4"......................................................................II
%ISTRI<,TI4* "IST.........................................................................................II
C=1*G7 S,001R2........................................................................................II
1. I,-R)!*C-I),..................................................................................................................................../I
1.1. #,R#4S7 1*% I*T7*%7% 1,%I7*C7.......................................................8I
1.2. SC4#7 4F #R4%,CT.................................................................................8I
1.3. %7FI*ITI4*S; 1CR4*20S; 1*% 1<<R78I1TI4*S..................................8II
1.4. 487R8I7> ..............................................................................................I?
1.-. R7F7R7*C7S.............................................................................................?
2. 0E,ER"& !ESCRI(-I),...................................................................................................................1I
2.1. #R4%,CT #7RS#7CTI87...........................................................................?I
2.2. ,S7R C=1R1CT7RISTICS.........................................................................?I
2.3. #R4%,CT F71T,R7S..............................................................................?II
2.4. G7*7R1" C4*STR1I*TS......................................................................??II
2.-. 1SS,0#TI4*S 1*% %7#7*%7*CI7S.....................................................??II
3. S(ECIFIC RE2*IRE+E,-S................................................................................................................23
3.1. 7?T7R*1" I*T7RF1C7 R7@,IR707*TS.................................................23
3.2. C400,*IC1TI4*S I*T7RF1C7S ............................................................2-
3.3. <7=18I4R1" R7@,IR707*TS................................................................2-
3.4. *4*6<7=18I4R1" R7@,IR707*TS........................................................2
3.-. 4T=7R R7@,IR707*TS..........................................................................2
4. "((E,!I1 "3 4E5 ("0E -R",SI-I),S.......................................................................................31
6. "((E,!I1 53 !"-"5"SE FIE&!S ...................................................................................................33
6. "((E,!I1 C3 "/S S7S-E+ C&"SS !I"0R"+.............................................................................36
8. "((E,!I1 !3 "/S S7S-E+ !"-" F&)4 !I"0R"+.................................................................36
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
iv
Software Requirements Specification
9. "((E,!I1 E3 "/S S7S-E+ (R)-)-7(E......................................................................................39
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
v
Software Requirements Specification
1. Intro;uction
The 8irtual Supermar3et !or Remote Sensin$ %ata and Ima$es A18SB is a s.stem under development at the
,niversit. o! Te+as at 7l #aso A,T7#B %epartment o! Computer Science. This document; the so!t'are
reCuirements speci!ication ASRSB; descri/es the s.stem in su!!icient detail !or its implementation. The SRS is
divided into !our sections. Section 1 descri/es the purpose and scope o! the s.stem and a $lossar. o! terms used
in the document. Section 2 descri/es the s.stem in $eneral terms. Section 3 contains the detailed reCuirements.
The appendices provide additional in!ormation.
This section o! the SRS contains a description o! the #urpose and Intended 1udience; the Scope o! the #roduct;
1//reviations and %e!initions and an overvie' o! the document. This section o! the SRS contains a description
o! the product and !unctionalit. provided /. the product; main !eatures o! the product; a description o! each
t.pe o! user o! the s.stem; constraints on the development team; and !actors that a!!ect the reCuirements stated
in the SRS. In order to descri/e 'hat the s.stem 'ill do at a hi$h6level; use case dia$rams and scenarios are
used in this section.
1.1. (urpose an; Inten;e; "u;ience
The purpose o! the SRS is to clearl. and accuratel. de!ine the reCuirements o! the 8irtual Supermar3et !or
Remote Sensin$ %ata and Ima$es s.stem /ein$ developed. The SRS documents and descri/es all !unctions that
the !inal product should per!ormD thus; it serves as a developer re!erence !or product desi$n and implementation.
The SRS descri/es the s.stem !rom the user perspective and then $roups s.stem reCuirements into t'o sections;
/ehavioral and non6/ehavioral. <ehavioral reCuirements de!ine 'hat the s.stem does /. e+aminin$ inputs to
the s.stem; outputs !rom the s.stem; and the relationships /et'een these inputs and outputs. *on6/ehavioral
reCuirements de!ine the attri/utes o! the s.stem as it per!orms its Eo/; includin$ e!!icienc.; relia/ilit.; securit.;
maintaina/ilit.; and porta/ilit..
The intended audience o! this document is the client; ; the $uidance team; and the so!t'are development team.
The SRS is an a$reement amon$ these parties on reCuirements re$ardin$ the 8S# s.stem.
1.2. Scope of (ro;uct
Remote sensin$ is the science o! acCuirin$; processin$; and interpretin$ measurements acCuired !rom a distance
as 'ith instruments /orne on aircra!t and satellites. 4! particular concern here are data a/out 7arth. 4ur client;
#1C7S; specialiFes in the acCuisition and distri/ution o! "andsat data coverin$ the South'est ,nited States and
portions o! 0e+ico.
*umerous remote sensin$ instruments are currentl. active in or/it around the 7arth. 7ach instrument provides
datasets to the instrument teams; 'ho then ma3e the data availa/le to clients. In some cases; data acCuired /.
clients can then /e made availa/le to other users. The result o! current practices is that remote sensin$ data o!
various !orms is availa/le !rom a variet. o! data providers. 0an. data sets are availa/le online; and much o! it
is !ree o! char$e. Scientists and the $eneral pu/lic currentl. must use a variet. o! search en$ines that tend to
!avor commercial sites over non6commercial sites. #1C7S 'ould li3e to !acilitate locatin$ various remote
sensin$ data sets. %evelopin$ a centraliFed location and specialiFed search en$ine 'ill !acilitate locatin$
datasets and 'ill /e $reatl. appreciated /. the scienti!ic communit..
The 18S s.stem 'ill ena/le users to locate remote sensin$ datasets availa/le online. It 'ill maintain a list o!
data sets that are made availa/le /. a variet. o! remote sensin$ or$aniFations. 18S 'ill store; or$aniFe; search;
and displa. lin3s to commercial and non6commercial data sets that are availa/le online. The so!t'are developed
'ill provide a /ro'ser6/ased inter!ace !or users to search throu$h an inde+ o! remote sensin$ data that various
or$aniFations ma3e availa/le. %ata providers 'ill use the so!t'are to ma3e their data sets availa/le to users /.
providin$ descriptions o! the data that is availa/le; includin$ the location o! the data; ho' the data 'as
o/tained; and ho' the user can access the data. 18S 'ill allo' a user to search !or data usin$ a natural
lan$ua$e Cuer.; and it 'ill provide a list o! relevant matches and lin3s to the data. %escriptions o! the data 'ill
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
vi
Software Requirements Specification
resolution. The so!t'are 'ill o!!er Gone stop shoppin$H !or commercial and non6commercial remote sensin$
data located on various online 'e/sites.
1.3. !efinitions< "cron'ms< an; "%%re#iations
This section provides the reader o! the SRS 'ith a list o! de!initions; acron.ms and a//reviations that 'ill /e
use!ul !or the understandin$ o! the terms used throu$hout this document.
1.3.1. !efinitions
Ta/le 1 lists the de!initions used in this document 'ith respect to 18S. The de!initions $iven /elo' are speci!ic
to this document and ma. not /e identical to de!initions o! these terms in common use. The purpose o! this
section is to assist the user in understandin$ the reCuirements !or the s.stem.
-a%le 13 !efinitions
-ER+ !EFI,I-I),
1ctor 1n e+ternal entit. such as a user; a data/ase; or application so!t'are that interacts 'ith the
s.stem.
1dministrator 1 person 'hose responsi/ilit. is to mana$e and maintain the in!rastructure o! the s.stem.
<and 1 'avelen$th interval in the electroma$netic spectrum.
<inar. %ata 1n. !ile !ormat !or di$ital data encoded as a seCuence o! /its /ut not consistin$ o! a
seCuence o! printa/le characters Ate+tB.
Class 1 set; collection; $roup; or con!i$uration containin$ mem/ers re$arded as havin$ certain
attri/utes or traits in commonD a 3ind or cate$or.
Class %ia$ram 1 dia$ram consistin$ o! a $roup o! classes and inter!aces re!lectin$ important entities o!
the domain o! the s.stem /ein$ modeled; and the relationships /et'een these classes and
inter!aces.
Clic3 throu$h The process o! selectin$ a h.perlin3 and trans!errin$ a /ro'serIs displa. !rom the current
site to the h.perlin3ed site.
%ata Flo'
%ia$ram
1 !unctional model o! a so!t'are s.stem that descri/es ho' outputs are derived !rom
inputs. 1 dia$ram contains processes; data !lo's; actors and data stores.
%ata/ase 1 collection o! data or in!ormation t.picall. stored on a computer s.stem and or$aniFed to
!acilitate retrieval and modi!ication.
%ata/ase
0ana$ement
S.stem
1 so!t'are s.stem that ena/les users to de!ine; create; maintain; and control access to a
data/ase.
%o'nload To trans!er data or pro$rams !rom a server or host computer to oneJs o'n computer or
device.
%.namic 0odel 1 model o! a so!t'are s.stem that descri/es the seCuence events and states in the s.stem.
7vent 1n occurrence or happenin$ o! si$ni!icance to a tas3 or pro$ram; such as the completion o!
an as.nchronous input)output operation.
7+ternal #ro$ram 1 pro$ram that interacts 'ith the s.stem to /e /uilt. 1n actor.
Field 1n element o! a data/ase record in 'hich one piece o! in!ormation is stored.
Footprint 1 rectan$ular or circular area that is the result o! the proEection o! the !ield o! vie' o! an
instrument onto a sur!ace or a selection o! an area o! an ima$e or map.
Forei$n 5e. 1 set o! !ields in a relational data /ase ta/le that is a primar. 3e. in a di!!erent ta/le and
that is used to lin3 the ta/les.
Geo6re!erenced
ima$es
1n ima$e !or 'hich the ima$e pi+els have /een assi$ned real6'orld coordinates
AproEection and datumB on the 7arth.
Graphical ,ser
Inter!ace
1 user inter!ace /ased on $raphics Aicons and pictures and menusB instead o! te+tD uses a
mouse as 'ell as a 3e./oard as an input device.
=it 1 reCuest to a 'e/ server !rom a 'e/ /ro'ser or other client.
=over #lacin$ the cursor over a G,I element 'ithout clic3in$ on this element.
=.perlin3 1n electronic lin3 providin$ direct access !rom one h.perte+t document to another either
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
vii
Software Requirements Specification
located in another area or in the same document.
Ima$e #ictorial representation o! a scene recorded /. a remote sensin$ s.stem.
Interactive 0ap 1 map displa.ed on a $raphical displa. device that can detect mouse clic3s and respond
usin$ the location o! the mouse clic3 on the map to determine the action ta3en.
5e. 7ither a #rimar. 5e. or a Forei$n 5e..
"andsat 1 series o! earth or/itin$ *1S1 satellites that acCuire multi6spectral ima$es in various
visi/le and IR /ands.
"atitude "atitude is the 1n$ular distance north or south !rom the earthIs eCuator measured throu$h
0 de$rees.
"in3 1 h.perlin3.
"inu+ The operatin$ s.stem "inu+; a ,ni+6li3e operatin$ s.stem availa/le !or most hard'are
computin$ plat!orms.
"o$in The process o! $ainin$ access to certain !eatures o! the 18S s.stem.
"on$itude The an$ular distance measured on a $reat circle o! re!erence !rom the intersection o! the
adopted Fero meridians 'ith this re!erence circle to the similar intersection o! the meridian
passin$ throu$h the o/Eect.
0ac4S The 0acintosh operatin$ s.stem !eatures a $raphical user inter!ace AG,IB that utiliFes
'indo's; icons; and a mouse to ma3e the computer simple to use.
0etadata %ata descri/in$ the data contained in a data/ase.
0ulti6spectral The use o! t'o or more /ands in remote sensin$.
4/Eect 1n instance o! a class used to descri/e real6'orld entities that have a counterpart 'ithin
the s.stem.
4/Eect64riented 1 pro/lem6solvin$ paradi$m that is /ased on a/stractin$ real 'orld entities includin$ their
attri/utes and !unctions. Interactions /et'een o/Eects $enerate the !unctionalit. o!
pro$rams.
#i+el 1 picture element. The smallest unit o! in!ormation in an ima$e.
#recondition 1 condition that must /e true prior to the e+ecution o! a piece o! code.
#rimar. 5e. 1 set o! !ields in a data/ase ta/le that is used to uniCuel. identi!. records in the ta/le.
#rovider 1n or$aniFation or individual that 'ill provide metadata !or the 18S s.stem.
@uer. 1 userJs reCuest !or in!ormation; $enerall. as a !ormal reCuest to a data/ase.
Radar 1n active !orm o! remote sensin$ that operates in the micro'ave and radio 'avelen$th
re$ions.
Record 1 uniCue ro' in a ta/le in a data/ase consistin$ o! a set o! !ields that descri/e a sin$le
occurrence o! some entit. descri/ed /. the ta/le.
Re$istered ,ser 1 user o! the 18S s.stem that has an account; !or e+ample a validator; provider or an
administrator.
Relational
%ata/ase
1 data/ase 'here data is stored in ta/les; 'hich contain records; 'hich contain !ields.
Relationships /et'een ta/les are de!ined /. !orei$n 3e.s.
Remote Sensin$ The measurement or acCuisition o! in!ormation a/out the 7arth /. a recordin$ device that
is not in ph.sical contact 'ith the 7arth.
Resolution The !ineness o! detail that can /e distin$uished in an ima$e. The real 'orld siFe o! the
!ootprint o! a pi+el in a remote sensin$ ima$e.
Scenarios #art o! a use case consistin$ o! a seCuence o! steps descri/in$ the interactions /et'een a
user and a s.stem.
Search 7n$ine 1 pro$ram that uses a search pattern to identi!. a set o! 'e/ pa$es matchin$ the search
pattern.
Server 1 computer that provides services to other computers or to people.
Spatial Resolution The smallest o/Eect or !eature detecta/le /. the sensor. 1lso 3no'n as pi+el siFe or
resolution.
Spectral
Resolution
The num/er and 'idth A'avelen$thB o! /ands Ameanin$!ul portionsB o! electroma$netic
ener$. detecta/le /. a $iven sensor.
Ta/le 1 collection o! records in a relational data/ase.
Tri$$er Condition 1n event that leads to some conseCuence in the s.stem either caused /. an outside entit.;
or a chain o! events.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
viii
Software Requirements Specification
,pdate The process o! modi!.in$; addin$ or removin$ e+istin$ data.
,se Case %escriptions; !rom the userIs point o! vie'; o! the important operations that provide value
to a user. The. descri/e the interactions /et'een actors and the s.stem.
,se Case %ia$ram 1 dia$ram that represents the use cases o! the s.stem; i.e.; interaction amon$ the s.stem;
e+ternal entities; and the principal users o! the s.stem.
8alidator The actor 'ho is responsi/le !or veri!.in$ the accurac. o! ne' or su/mitted data.
8isitor The actor that is the main user o! the s.stem and 'ho searches the s.stem !or data.
>indo's
4peratin$ S.stem
1 computer operatin$ s.stem /. 0icroso!t that provides a $raphical user inter!ace AG,IB;
virtual memor. mana$ement; multitas3in$; and support !or man. peripheral devices.
1.3.2. "cron'ms an; "%%re#iations
Ta/le 2 lists the acron.ms and a//reviations used in this document 'ith respect to 18S.
-a%le 23 "cron'ms an; "%%re#iations
"CR),7+S +E",I,0
18S 1 8irtual Supermar3et !or Remote Sensin$ %ata and Ima$es
%<0S %ata/ase 0ana$ement S.stem
%F% %ata Flo' %ia$ram
7SC 7scape
G74* Geosciences C./erin!rastructure *et'or3
GIF Graphic Interchan$e Format
GIS Geo$raphic In!ormation S.stem
G,I Graphical ,ser Inter!ace
K#7G Koint #hoto$raphic 7+perts Group AIma$e FormatB
*1S1 *ational 1eronautics and Space 1dministration.
4S 4peratin$ S.stem
#1C7S #an 1merican Center !or 7arth and 7nvironmental Studies
S@" Structured @uer. "an$ua$e
SRS So!t'are ReCuirements Speci!ication
ST% State Transition %ia$ram
TIFF Ta$$ed Ima$e File Format
,R" ,niversal Resource "ocator.
,T7# ,niversit. o! Te+as at 7l #aso
>>> >orld >ide >e/
e.$. !or e+ample
R1%1R Radio %etection 1nd Ran$in$
i.e. that is
1.4. )#er#iew
The SRS is divided into !our maEor sections: Introduction; General %escription; Speci!ic ReCuirements; and
1ppendices.
Section 2 AGeneral %escriptionB contains:
1B #roduct #erspective: description o! the product and !unctionalit. provided /. the product.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
i+
Software Requirements Specification
2B #roduct Features: main !eatures o! the product; includin$ use cases
3B ,ser Characteristics: description o! each t.pe o! user o! the s.stem
4B General Constraints: constraints on the development team includin$ or$aniFational !actors; hard'are
limitations; and securit. considerations.
-B 1ssumptions and %ependencies: !actors that a!!ect the reCuirements stated in the SRS.
Section 3 ASpeci!ic ReCuirementsB contains:
1B 7+ternal Inter!ace ReCuirements: descri/es reCuirements !or user; hard'are; so!t'are; and
communication inter!aces.
2B <ehavior ReCuirements: same class o! user; related real6'orld o/Eects; stimulus; related !eatures; and
!unctional reCuirements
3B *on6<ehavioral ReCuirements: per!ormance; Cualitative; and desi$n)implementation constraint
reCuirements.
4B 4ther ReCuirements: data/ase; operations; and site adaptation reCuirements.
1ppendi+ 1 contains the 18S 'e/ pa$e transition dia$ram.
1ppendi+ < contains the 18S data /ase entries.
1ppendi+ C contains the 18S class dia$ram.
1ppendi+ % contains the 18S data !lo' dia$ram.
1ppendi+ 7 contains the 18S protot.pe.
1.6. References
L1M Roach; Steve. GReCuirements %e!inition: 0etadata !or 7arth/ound Remote Sensin$.H Kan 2004.
L2M 5eller; G. Rand.. First Intervie'. 2( Kan 2004.
L3M 5eller; G. Rand.. Second Intervie'. 0- 0arch 2004.
L4M 5eller; G. Rand.. Third Intervie'. 10 0arch 2004.
L-M 1ll6#ro$rammatic Stars; CST; Sputni3. Intervie' Report. 0: Fe/ruar. 2004.
L:M So!t'are 7n$ineerin$ I Class. Second Intervie' Transcript. 0- 0arch 2004.
L9M 1ll6#ro$rammatic Stars. Third Intervie' Transcript. 10 0arch 2004
L(M 1ll6#ro$rammatic Stars; CST; Sputni3. #rotot.pe #resentations. 10 0arch 2004.
LM 1ll6#ro$rammatic Stars; CST; Sputni3. Team SRS. 10 0arch 2004.
L10M Roach; Steve. GReCuirementsH 7mail. 11 Fe/ruar. 2004.
L11M Roach; Steve. GRe: 0704H 7mail. 04 1pril 2004.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+
Software Requirements Specification
2. 0eneral !escription
This section o! the SRS contains a description o! the product and !unctionalit. provided /. the product; main
!eatures o! the product; a description o! each t.pe o! user o! the s.stem; constraints on the development team;
and !actors that a!!ect the reCuirements stated in the SRS. In order to descri/e 'hat the s.stem 'ill do at a
hi$h6level ,se Case dia$rams and Scenarios are used in this section.
2.1. (ro;uct (erspecti#e
The 18S s.stem 'ill serve as a search en$ine !or remotel. sensed data and it 'ill allo' scientists and the
$eneral pu/lic to search over a vast amount o! remotel. sensed data !or sets o! in!ormation. The s.stemIs search
inter!ace 'ill allo' the user to speci!. various characteristics o! the data in order to !ind data sets that match the
$iven search criteria; e.$. spatial resolution; spectral resolution; $eo$raphical location; costs. The result o! the
Cueries 'ill /e lin3s A,R"sB to the location o! the matchin$ data. This s.stem 'ill also allo' its users to
provide data sets o! their o'n 'hich; a!ter a validation process; 'ill /e supplied to the in!ormation repositor. in
order to ma3e it availa/le to other users. This s.stem is sel!6contained ho'ever; it is not independent $iven that
its !unctionalit. relies on the data/ase that #1C7S 'ill provide; 'hich 'ill not /e a part o! the s.stem.
18S is a 'e/6/ased so!t'are s.stem that provides services !or re$istered and non6re$istered users. Re$istered
users; 3no'n as data providers; are a/le to store descriptions o! their online remote sensin$ data sets. These
data sets ma. include Gprett. picturesH; $eo6re!erenced ima$es; and /inar. data. #roviders add metadata to the
s.stem /. providin$ a lin3 to their data and a speci!ic description o! the data; includin$ location; date; data t.pe;
lon$itude; and latitude. *on6re$istered users; 3no'n as visitors; can search and /ro'se throu$h the metadata.
To maintain the securit. and inte$rit. o! the metadata; validators veri!. and data posted /. data providers
/e!ore it is availa/le to visitors.
18S is /ein$ developed !or #1C7S. The technical mission o! #1C7S is to contri/ute to *1S1Is 7arth and
Science 7nterprise /. conductin$ research in several areas o! the $eolo$ical; ph.sical and environmental
sciences. 4ther search en$ines are availa/le on the >orld >ide >e/ A>>>B to search !or remotel. sensed
data ho'everD these search en$ines are not uni!ied as a common entit.. The inter!aces !or each o! these search
en$ines var.; and the in!ormation the. contain ma. not /e as relia/le as needed !or scienti!ic purposes. The
18S so!t'are s.stem intends to mer$e all o! the most important and dependa/le remotel. sensed data sources
into one entit. that 'ill provide this in!ormation !or !ree to the $eneral pu/lic; accordin$ to #1C7S mission
statement.
2.2. *ser C$aracteristics
This section descri/es the actors o! the s.stem and $ives a description o! !eatures and characteristics that
in!luence the so!t'are s.stem. The use case model consists o! actors; use cases and relations amon$ them.
2.2.1. "ctors
This section descri/es all o! the users o! the s.stem and their di!!erent roles and $eneral !unction in it. 1n actor
is an outside entit. that interacts 'ith the proposed s.stem. >hen an actor interacts 'ith a s.stem it per!orms a
use case.
2.2.1.1. /isitor
This actor is a person 'ho comes to the s.stem to search !or remotel. sensed data. The visitor is a person 'ho
can either have a stron$ educational level or have no pro!essional /ac3$round; e.$. a #h.%. and a hi$h school
student; respectivel.. The visitor ma. per!orm t'o t.pes o! search; a simple search /. su/mittin$ a Cuer. to the
search en$ine; or an advanced search; 'here the user is $iven a set o! descriptions o! t.pe o! data to /e
searched.
2.2.1.2. (ro#i;er
1 provider is ever. entit. that 'ill provide descriptions and locations o! remotel. sensed data throu$h our
s.stem. The perspective providers include research centers and commercial or$aniFations 'hich o'n remotel.
sense data.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+i
Software Requirements Specification
2.2.1.3. /ali;ator
This actor is the person in char$e o! revie'in$ and validatin$ data !or the s.stem. 7ver. time a set o! data is
proposed; it 'ill /e the responsi/ilit. o! the validator to veri!. the content o! the data and validate it; so it can /e
either accepted and uploaded into the s.stem or reEected. The perspective validator is an administrative sta!!
mem/er !rom a research center.
2.2.1.4. !ata%ase
The data/ase 'ill hold relations containin$ all the in!ormation that the s.stem needs such as userIs pro!iles;
metadata !or /oth approved remotel. sensed data and unapproved remotel. sensed data and help topics.
2.3. (ro;uct Features
The main !eatures o! this so!t'are s.stem are:
The s.stem provides an inter!ace !or searchin$ !or remotel. sensed data that is availa/le on6line.
The s.stem provides an inter!ace that ena/les data providers to descri/e the data sets the. have
availa/le.
The s.stem provides an inter!ace that allo's validators to accept or reEect su/mitted metadata.
It is important to mention that the s.stem 'ill not mana$e actual pieces o! remotel. sensed data; /ut instead; it
mana$es metadata that points to the actual location o! remotel. sensed data. Fi$ure 1 contains the ,se Case
%ia$ram !or the 18S s.stem.
Figure 2=13 *se Case !iagram
2.3.1. *se Case !escription
In this section each use case o! the s.stem 'ill /e descri/ed. ,se cases contain scenarios; 'hich are the
seCuence o! steps involved in the use case. ,se cases are a/stractions o! the operations per!ormed /. the
s.stem that are valua/le to the user. This modelin$ helps as a communication tool /et'een developers and
clients. The !ollo'in$ is a description o! each use case; its actors and the scenarios !or that use case.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+ii
Software Requirements Specification
2.3.1.1. *se Case 13 Searc$ for !ata
*se Case !escription3 1 visitor uses a simple search !or remote sensin$ data /. enterin$ a set o! 3e.'ords or
a more advanced search /. enterin$ parameters such as source; visual6in!rared or radar; date and location. The
s.stem 'ill displa. the results o! the search.
"ctors3 8isitor; %ata/ase.
2.3.1.1.1. Scenario 13 Simple Searc$
(recon;itions3 The visitor is vie'in$ the Home Search Page as sho'n in Fi$ure 3 6-: =ome)Search #a$e.
(ostcon;itions3 The visitor is vie'in$ the Search Results Page.
1. The visitor enters a list o! 3e.'ords descri/in$ the Cuer..
2. The visitor selects ima$e A1"T 1B.
3. The visitor clic3s the submit /utton.
4. The s.stem processes the visitorIs search Cuer. and constructs an S@" Cuer..
-. The s.stem su/mits an S@" search Cuer. to the data/ase.
:. The data/ase returns ,R"s and descriptions o! metadata to the s.stem.
9. The s.stem orders the results accordin$ to ho' 'ell the metadata matches the Cuer. and ho' availa/le the
site is.
(. The s.stem displa.s the ordered matches !ound; !ive results at a time. A1"T 2B.
. The visitor scrolls !or'ard throu$h the list; !ive results per pa$e.
10. The visitor selects a search result A1"T 3B.
11. The s.stem redirects the visitor to the ,R" associated 'ith that metadata and records the visitors I#
address; the time; and the tar$et o! the clic3 throu$h.
12. 7nd o! use case.
"&- 13 The visitor selects the dataset option.
1161: The s.stem continues 'ith the 1dvanced Search; ,se Case 1; Scenario 2.
"&- 23 The data/ase returns no matches.
1161: The s.stem displa.s the messa$e G*o match !oundH on the Search Results Page.
1162: 7nd o! use case.
"&- 33 The visitor re!ines his search Cuer. and enters a ne' list o! 3e.'ords descri/in$ his Cuer..
1461: Return to Scenario 1; step num/er 2.
2.3.1.1.2. Scenario 23 ";#ance; Searc$
(recon;itions3 The visitor is vie'in$ the Advanced Search Page as sho'n in Fi$ure 262: 1dvanced Search
(ostcon;itions3 The visitor is vie'in$ the Search Results.
1. The visitor enters a list o! 3e.'ords descri/in$ his Cuer..
2. The visitor selects a source !rom the sources ta/le A1"T 1; 1"T 2B.
3. The visitor selects a !ootprint !rom the map o! ,S N *orth 1merica A1"T 1; 1"T 3; 1"T 4; 1"T -; 1"T
:B.
4. The s.stem displa.s the coordinates o! the selected area.
-. The visitor clic3s the submit /utton.
:. The s.stem processes the visitorIs search Cuer. and constructs an S@" Cuer..
9. The s.stem su/mits an S@" search Cuer. to the data/ase.
(. The data/ase returns ,R"s and descriptions o! metadata to the s.stem.
. The s.stem orders the results accordin$ to ho' 'ell the metadata matches the Cuer. and ho' availa/le the
site is.
10. The s.stem displa.s the ordered matches !ound; !ive results at a time. A1"T 9B.
11. The visitor scrolls !or'ard throu$h the list; !ive results per pa$e.
12. The visitor selects a search result A1"T (; 1"T ; 1"T 10B.
13. The s.stem redirects the visitor to the ,R" associated 'ith that metadata and records the visitors I#
address; the time; and the tar$et o! the clic3 throu$h.
14. 7nd o! use case.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+iii
Software Requirements Specification
"&- 13 The visitor selects path and ro' option.
1161: The visitor enters the path and ro' as search parameters.
1162: Return to Scenario 2; step num/er -.
"&- 23 The visitor clic3s on the sensor guide lin3.
1261: The s.stem redirects the visitor to the Guided Sensor Search Page as sho'n in Fi$ure 263: Guided
Sensor Search.
1262: The visitor selects the free radio /utton.
1263: The visitor selects a spectral resolution !rom the spectral resolution drop do'n list.
1264: The visitor selects a spatial resolution !rom the spatial resolution drop do'n list.
126-: The visitor clic3s the submit /utton.
126:: The s.stem processes the visitorIs source search Cuer. and constructs an S@" Cuer..
1269: The s.stem su/mits an S@" search Cuer. to the data/ase.
126(: The data/ase returns the matchin$ sensors.
126: The s.stem redirects the visitor to the Advanced Search Page.
12610: The s.stem populates the sources ta/le usin$ the results o! the matchin$ sensors Cuer..
12611: Return to Scenario 2; step num/er 3.
"&- 33 The visitor selects coordinates option.
1361: The visitor enters the lon$itude and latitude as search parameters.
1362: Return to Scenario 2; step num/er -.
"&- 43 The visitor selects another continent !rom the continent options.
1461: The s.stem displa.s a map !or the selected continent.
1462: The visitor selects an area !rom the selected map A1"T 1; 1"T 2; 1"T 3B.
1463: Return to Scenario 2; step num/er 4.
"&- 63 The visitor selects the option to Foom in.
1-61: The s.stem chan$es the cursor pointer into a crosshair cursor.
1-62: The visitor le!t clic3s on a point in the map.
1-63: The s.stem re!reshes the 'e/pa$e displa.in$ the Foomed map.
1-64: Return to Scenario 2; step num/er 3.
"&- 63 The visitor selects the option to Foom out.
1:61: The s.stem chan$es the cursor pointer into a crosshair cursor.
1:62: The visitor le!t clic3s on a point in the map.
1:63: The s.stem re!reshes the 'e/pa$e displa.in$ the Foomed map.
1:64: Return to Scenario 2; step num/er 3.
"&- 83 The data/ase returns no matches.
1961: The s.stem displa.s a match not !ound messa$e and an option to return to the Advanced Search Page.
1962: The visitor selects the return option.
1963: Return to Scenario 2; step num/er 1.
"&- 83 The visitor selects ne+t pa$e.
1(61: The s.stem displa.s the results associated 'ith the ne+t pa$e.
1(62: Return to Scenario 2; step num/er 11.
"&- >3 The visitor selects the N pa$e.
161: The s.stem displa.s the results associated 'ith the N pa$e.
162: Return to Scenario 2; step num/er 11.
"&- 103 The visitor 'ishes to re!ine his search Cuer. and selects the advanced search option.
11061: The s.stem redirects the visitor to the Advanced Search Page.
11062: Return to Scenario 2; step num/er 2.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+iv
Software Requirements Specification
2.3.1.1.3. Scenario 33 ?elp
(recon;itions3 The visitor is vie'in$ the Home Search Page; or Advanced Search Page; or Search Results
Page.
(ostcon;itions3 The visitor is vie'in$ the Search Help Page.
1. The visitor selects the help option.
2. The s.stem redirects the visitor to the Search Help Page and to the section associated 'ith the pa$e !rom
'hich the visitor came !rom.
3. 7nd o! use case.
2.3.1.1.4. Scenario 43 /iew 0lossar'
(recon;itions3 The visitor is vie'in$ the Home Search Page; Advanced Search Page; or Search Results Page.
(ostcon;itions3 The visitor is vie'in$ the Glossary Page.
1. The visitor selects the $lossar. option.
2. The s.stem redirects the visitor to the Glossary Page.
3. 7nd o! use case.
2.3.1.1.6. Scenario 63 /iew &in@ Center
(recon;itions3 The visitor is vie'in$ the Home Search Page; or Advanced Search Page; or Search Results
Page.
(ostcon;itions3 The visitor is vie'in$ the Link enter Page.
1. The visitor selects the lin3 center option.
2. The s.stem redirects the visitor to the Link enter Page.
3. The visitor selects a lin3 !rom the list A1"T 1B.
4. The s.stem redirects the visitor to the ,R" associated 'ith that lin3.
-. 7nd o! use case.
"&- 13 The visitor selects the option to return to the Home Search Page.
1161: The s.stem redirects the visitor to the Home Search Page.
1162: 7nd o! use case.
2.3.1.1.6. Scenario 63 /iew Site +ap
(recon;itions3 The visitor is vie'in$ the Home Search Page; Advanced Search Page; or Search Results Page.
(ostcon;itions3 The visitor is vie'in$ the Site !ap Page.
1. The visitor selects the site map option.
2. The s.stem redirects the visitor to the Site !ap Page.
3. 7nd o! use case.
2.3.1.1.8. Scenario 83 /iew Contact *s
(recon;itions3 The visitor is vie'in$ the Home Search Page; Advanced Search Page; or Search Results Page.
(ostcon;itions3 The visitor is vie'in$ the ontact "s Page.
1. The visitor selects the contact us option.
2. The s.stem redirects the visitor to the ontact "s Page.
3. The visitor selects the donate ima$e option A1"T 1B.
4. The s.stem redirects the user to the #aces %onation >e/pa$e.
-. 7nd o! use case.
"&- 13 The visitor selects the option to return to the Home Search Page.
1161: The s.stem redirects the visitor to the Home Search Page.
1162: 7nd o! use case.
2.3.1.2. *se Case 23 Register
*se Case !escription3 1 prospective provider must re$ister /e!ore s)he can ma3e data availa/le ARefer to *se
Case 4B. Re$istration is a one6time process a!ter 'hich the provider 'ill /e a/le to lo$in.
"ctors3 #rovider; %ata/ase.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+v
Software Requirements Specification
2.3.1.2.1. Scenario 13 First -ime (ro#i;er
(recon;itions3 The provider is not re$istered. The provider is vie'in$ the Provider Registration Page.
(ostcon;itions3 The provider has success!ull. re$istered and an email 'ith in!ormation has /een sent to the
provider.
1. The s.stem displa.s the Provider Registration Page. This pa$e contains a !orm !or the user to !ill out 'ith
the attri/utes listed /elo'. The attri/utes mar3ed 'ith O are reCuired.
a. The providerIs !irst name. O
/. The providerIs middle initial.
c. The providerIs last name. O
d. The providerIs email address. O
e. The providerIs or$aniFation.
!. The providerIs address.
$. The providerIs cate$or.; i.e. commercial; $overnment; educational or other.
h. The providerIs lo$in name. O
i. The providerIs pass'ord. O
E. The providerIs pass'ord veri!ication. O
2. The provider !ills out the !orm 'ith the reCuested in!ormation and selects the option to su/mit A1"T 1B.
3. The s.stem veri!ies that the reCuired attri/utes are present; that the email address has a valid !orm; that the
lo$in name does not e+ist in the data/ase; and that the pass'ord and pass'ord veri!ication are identical.
A1"T 2; 1"T 3B.
4. The s.stem displa.s a than3 .ou pa$e 'hich contains instructions.
-. The provider presses continue #ith login link option.
:. The s.stem displa.s the "o$in pa$e ARefer to *se Case 3B.
9. 7nd o! use case.
"&- 13 The user selects the option to clear the !orm.
1161: The s.stem sets the 'e/pa$e to its de!ault state; 'ithout su/mittin$ an. in!ormation.
1162: S.stem returns to Scenario 1; step num/er 1.
"&- 23 The s.stem detects invalid re$istration in!ormation. ReCuired !ields are empt.; email address does not
have a valid !ormat; the lo$in name is alread. in use; or the pass'ords do not match.
1261: The s.stem displa.s the re$istration 'e/pa$e.
1262: The s.stem in!orms that one or more o! the reCuired !ields are incorrect Asuch as invalid lo$in name; or
lo$in name alread. e+istsB; mar3s them in red; and includes description o! appropriate corrective
actions.
1263: The user corrects the mar3ed !ields and resu/mits the in!ormation pressin$ the su/mit /utton A1"T 1B.
1264: S.stem returns to Scenario 1; step num/er 3.
2.3.1.2.2. Scenario 33 ?elp
(recon;itions3 The provider is vie'in$ the Provider Registration Page.
(ostcon;itions3 The visitor is vie'in$ the Provider Registration Page.
1. The visitor selects the help option.
2. The s.stem redirects the visitor to the Search Help Page and to the section associated 'ith the pa$e !rom
'hich the visitor came !rom.
3. 7nd o! use case.
2.3.1.3. *se Case 33 &ogin
*se Case !escription3 1 provider or validator must lo$in 'ith a valid lo$in name and pass'ord in order to
access restricted !unctions. These include providin$ data ARefer to *se Case 4B and validatin$ data ARefer to
*se Case 6A.
"ctors3 #rovider; 8alidator; %ata/ase.
2.3.1.3.1. Scenario 13 &ogin
(recon;itions: The 1ctor must /e re$istered ARefer to *se Case 2B. The 1ctor is vie'in$ the Login Page.
(ostcon;itions3 The 1ctor has success!ull. lo$$ed into the s.stem.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+vi
Software Requirements Specification
1. The s.stem displa.s the Login Page.
2. The 1ctor enters a lo$in name; a pass'ord and selects the su/mit option A1"T 1B.
3. The s.stem su/mits an S@" search Cuer. to the data/ase usin$ the lo$in name.
4. The data/ase returns the encr.pted pass'ord.
-. The s.stem encr.pts the pass'ord entered and compares to the pass'ord returned /. the data/ase. The
pass'ords match A1"T 2B. *4T7: The pass'ord is encr.pted on the client side and compared on the
server side. The server does not send an encr.pted pass'ord to a client; and an unencr.pted pass'ord is
never trans!erred over the net'or3.
:. The s.stem redirects the 1ctor to the 1ctor Page.
9. 7nd o! use case.
"&- 13 The 1ctor selects the cancel option.
1161: The s.stem returns to the Home Search Page.
1162: 7nd o! use case.
"&- 23 The s.stem detects invalid lo$in name or pass'ord.
1261: The s.stem displa.s an error pa$e.
1262: The s.stem 'aits - seconds.
1263: S.stem returns to Scenario 1; step num/er 1.
2.3.1.3.2. Scenario 23 (asswor; Reco#er'
(recon;itions: The 1ctor must /e re$istered. The 1ctor is vie'in$ the Login Page.
(ostcon;itions3 The 1ctor has success!ull. received an email 'ith his pass'ord.
1. The s.stem displa.s the Login Page.
2. The 1ctor selects forgot pass#ord option.
3. The s.stem displa.s the Pass#ord Recovery Page.
4. The 1ctor enters his lo$ in name.
-. The s.stem su/mits an S@" search Cuer. to the data/ase usin$ the lo$in name A1"T 1B.
:. The data/ase returns the 1ctorIs email address.
9. The s.stem creates a ne' temporar. pass'ord and emails it to the 1ctor.
(. The s.stem su/mits the ne' pass'ord to the data/ase.
. The s.stem sends the ne' pass'ord to the 1ctorIs email address.
10. The s.stem displa.s the Pass#ord Recovery $nstructions Page 'ith instructions.
11. 7nd o! use case.
"&- 13 The 1ctor lo$in name is not !ound.
1161: The s.stem displa.s a 'e/pa$e indicatin$ that the provider lo$in name 'as not !ound.
1162: The 1ctor hits the o3 /utton.
1163: The s.stem redirects the 1ctor to the Provider Registration Page ARefer to *se Case 2B.
1162: 7nd o! use case.
2.3.1.3.3. Scenario 33 ?elp
(recon;itions3 The visitor is vie'in$ the Login Page.
(ostcon;itions3 The visitor is vie'in$ the Login Help Page.
1. The visitor selects the help option.
2. The s.stem redirects the visitor to the Login Help Page and to the section associated 'ith the pa$e !rom
'hich the visitor came !rom.
3. 7nd o! use case.
2.3.1.4. *se Case 43 (ro#i;e !ata
*se Case Summar'3 The provider 'ants to su/mit a description o! metadata !or considerationD the proposed
metadata must /e validated /e!ore added to the s.stem ARefer to *se Case 6B.
"ctors3 #rovider; %ata/ase.
2.3.1.4.1. Scenario 13 Su%mit !ata
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+vii
Software Requirements Specification
(recon;itions3 The provider must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The provider is vie'in$
the Provider Page.
(ostcon;itions3 0etadata has /een success!ull. su/mitted.
1. The provider selects the su/mit metadata option on the Provider Page.
2. The s.stem displa.s the Submit !etadata Page !or data su/mission.
3. The provider enters the !ollo'in$ metadata:
a. 1 ,R" !or the data set.
/. 1 description 'hich 'ill not e+ceed 2-0 'ords descri/in$ the data set.
c. Source o! the data set.
4. The provider enters the coordinates o! the data set 'hich can /e A1"T1; 1"T2B:
a. "on$itude and "atitude.
/. #ath and Ro'.
-. The provider selects the option to su/mit the data A1"T 3B.
:. The s.stem in!orms provider that the in!ormation supplied has /een stored into the data/ase and 'ill /e
validated.
9. The s.stem returns the provider to the Provider Page.
(. 7nd o! use case.
"&- 13 The provider selects an area on the map o! ,S N *orth 1merica
1161: The s.stem displa.s the coordinates entered.
1162: Return to Scenario 1; step num/er -.
"&- 23 The provider selects another continent.
1261: The s.stem displa.s the map !or the selected continent
1262: The provider selects an area on the selected map.
1263: Return to Scenario 1; step num/er -.
"&- 33 The provider selects the clear option.
1361: The s.stem clears all !ields in the su/mission !orm.
1362: Return to Scenario 1; step num/er 2.
2.3.1.4.2. Scenario 23 Su%mit Software +eta;ata
(recon;itions3 The provider must /e lo$$ed in to the s.stem ARefer to *se Case 2B. The provider is vie'in$
the Provider Page.
(ostcon;itions3 So!t'are 0etadata has /een success!ull. su/mitted.
1. The provider selects the su/mit so!t'are metadata option on the Provider Page.
2. The s.stem displa.s the Submit Soft#are !etadata Page !or su/mission.
3. The provider enters the !ollo'in$ metadata:
a. 1 ,R" !or the so!t'are.
/. 1 description 'hich 'ill not e+ceed 2-0 'ords descri/in$ the data set.
c. 1 num/er representin$ the cost o! the so!t'are.
4. The provider selects the option to su/mit the data A1"T 1B.
-. The s.stem in!orms provider that the in!ormation supplied has /een stored into the data/ase and 'ill /e
validated.
:. The s.stem returns the provider to the Provider Page.
9. 7nd o! use case.
"&- 13 The provider selects the clear option.
1161: The s.stem clears all !ields in the su/mission !orm.
1162: Return to Scenario 2; step num/er 2.
2.3.1.4.3. Scenario 33 Su%mit 0lossar' Entr'
(recon;itions3 The provider must /e lo$$ed in to the s.stem ARefer to *se Case 2B. The provider is vie'in$
the Provider Page.
(ostcon;itions3 Glossar. entr. has /een success!ull. su/mitted.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+viii
Software Requirements Specification
1. The provider selects the su/mit $lossar. entr. option on the Provider Page.
2. The s.stem displa.s the Submit Glossary %ntry Page !or su/mission.
3. The provider enters the !ollo'in$ metadata:
a. 1 term.
/. 1 description 'hich 'ill not e+ceed 2-0 'ords descri/in$ the term.
4. The provider selects the option to su/mit the data A1"T 1B.
-. The s.stem in!orms provider that the in!ormation supplied has /een stored into the data/ase and 'ill /e
validated.
:. The s.stem returns the provider to the Provider Page.
9. 7nd o! use case.
"&- 13 The provider selects the clear option.
1161: The s.stem clears all !ields in the su/mission !orm.
1162: Return to Scenario 1; step num/er 2.
2.3.1.4.4. Scenario 43 !onate !ata to ("CES
(recon;itions3 The provider is vie'in$ the ontact "s Page.
(ostcon;itions3 The provider has /een redirected to #1C7S.
1. The provider selects the donate metadata option on the ontact "s Page.
2. The s.stem redirects the provider to the #1C7S donations 'e/ pa$e.
3. 7nd o! use case.
2.3.1.4.6. Scenario 63 C$ange "ccount Information
(recon;itions3 The provider must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The provider is vie'in$
the Provider Page.
(ostcon;itions3 The provider has chan$ed his in!ormation.
1. The provider selects the chan$e account option on the Provider Page.
2. The s.stem su/mits an S@" search Cuer. to the data/ase usin$ the lo$in name !or the provider.
3. The data/ase returns all the account in!ormation associated 'ith that provider lo$in name.
4. The s.stem redirects the provider to the hange Provider $nformation Page.
-. The s.stem displa.s a !orm 'ith all the attri/utes associated 'ith that user.
:. The provider chan$es a !ield.
9. The provider selects su/mit chan$es A1"T1B.
(. The s.stem sends the ne' in!ormation to the data/ase.
. The s.stem displa.s a messa$e sa.in$ that the account has /een updated.
10. The s.stem redirects the provider to the Provider Page.
11. 7nd o! use case.
"&- 13 The provider selects the cancel option.
1161: The s.stem redirects the user to the Provider Page.
1162: 7nd o! use case.
2.3.1.4.6. Scenario 63 ?elp
(recon;itions3 The visitor is vie'in$ the Provider Page; Submit !etadata Page& Submit Soft#are !etadata
Page& Glossary %ntry Page& and hange Provider $nformation Page.
(ostcon;itions3 The visitor is vie'in$ the Provider Help Page.
1. The visitor selects the help option.
2. The s.stem redirects the visitor to the Provider Help Page and to the section associated 'ith the pa$e !rom
'hich the visitor came !rom.
3. 7nd o! use case.
2.3.1.6. *se Case 63 /ali;ate !ata
*se Case !escription3 The validator 'ants to revie' selected metadata in the data/ase. 1!ter revie'; the data
ma. /e accepted or reEected. I! the data is accepted; then it is added to the data/ase and 'ill /e availa/le !or
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
+i+
Software Requirements Specification
othersD other'ise; it 'ill not /e added and a noti!ication 'ill /e sent to the provider. The 8alidator 'e/ site is
distinct !rom the 8isitor)#rovider site. This is to simpli!. the user inter!aces.
"ctors3 8alidator; %ata/ase.
2.3.1.6.1. Scenario 13 Re#iew !ata
(recon;itions3 The validator must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The validator is vie'in$
the 'alidator Page.
(ostcon;itions3 0etadata has /een revie'ed.
1. The validator selects the validate metadata option on the 'alidator Page.
2. The s.stem redirects the validator to the !etadata 'alidation Page.
3. The validator selects the revie' metadata option associated 'ith that dataset !rom the ta/le A1"T 1B.
4. The s.stem displa.s the data !rom the dataset.
-. The validator approves the data A1"T 2B.
:. The s.stem mar3s the dataset as revie'ed and ma3es the metadata availa/le !or visitor searches ARefer to
*se Case 1B.
9. The s.stem sends an email to the provider indicatin$ that the data set has /een accepted.
(. The s.stem redirects the validator to the 'alidator Page.
. 7nd o! use case.
"&- 13 The validator selects the cancel option.
1161: The s.stem redirects the user to the Provider Page.
1162: 7nd o! use case.
"&- 23 The validator selects the disapprove option.
1261: The s.stem mar3s the data as disapproved.
1262: The s.stem prompts the validator !or an e+planation.
1263: The validator enters an e+planation.
1264: The validator selects the su/mit option.
126-: The s.stem sends an email to the provider indicatin$ that the data has /een reEected; includin$ the
validatorIs e+planation.
126:: The s.stem redirects the validator to the 'alidator Page.
1269: Return to Scenario 1; step num/er 1.
2.3.1.6.2. Scenario 23 /ali;ate Software +eta;ata
(recon;itions3 The validator must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The validator is vie'in$
the 'alidator Page.
(ostcon;itions3 So!t'are has /een revie'ed.
1. The validator selects the validate so!t'are option.
2. The s.stem redirects the validator to the Soft#are 'alidation Page.
3. The validator selects the revie' so!t'are option associated 'ith that dataset !rom the ta/le A1"T 1B.
4. The s.stem displa.s the so!t'are in!ormation !rom the list.
-. The validator approves the data A1"T 2B.
:. The s.stem mar3s the dataset as revie'ed and ma3es the metadata availa/le !or visitor searches ARefer to
*se Case 1B.
9. The s.stem sends an email to the provider indicatin$ that the data set has /een accepted.
(. The s.stem redirects the validator to the 'alidator Page
. 7nd o! use case.
"&- 13 The validator selects the cancel option.
1161: The s.stem redirects the user to the Provider Page.
1162: 7nd o! use case.
"&- 23 The validator selects the disapprove option.
1261: The s.stem mar3s the data as disapproved.
1262: The s.stem prompts the validator !or an e+planation.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
++
Software Requirements Specification
1263: The validator enters an e+planation.
1264: The validator selects the su/mit option.
126-: The s.stem sends an email to the provider indicatin$ that the data has /een reEected; includin$ the
validatorIs e+planation.
126:: The s.stem redirects the validator to the 'alidator Page.
1269: Return to Scenario 2; step num/er 1.
2.3.1.6.3. Scenario 33 Su%mit 0lossar' Entr'
(recon;itions3 The validator must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The provider is vie'in$
the 'alidator Page.
(ostcon;itions3 Glossar. has /een revie'ed.
1. The validator selects the validate $lossar. entr. option.
2. The s.stem redirects the validator to the Glossary (erm 'alidation Page.
3. The validator selects the revie' $lossar. term option associated 'ith that term !rom the ta/le A1"T 1B.
4. The s.stem displa.s the $lossar. term de!inition !rom the list.
-. The validator approves the data A1"T 2B.
:. The s.stem mar3s the $lossar. term as revie'ed and ma3es the term availa/le !or visitor vie'in$ the
$lossar. ARefer to *se Case 1B.
9. The s.stem sends an email to the provider indicatin$ that the data set has /een accepted.
(. The s.stem redirects the validator to the 'alidator Page
. 7nd o! use case.
"&- 13 The validator selects the cancel option.
1161: The s.stem redirects the user to the Provider Page.
1162: 7nd o! use case.
"&- 23 The validator clic3s disapprove option.
1261: The s.stem mar3s the data as disapproved.
1262: The s.stem prompts the validator !or an e+planation.
1263: The validator enters an e+planation.
1264: The validator selects the su/mit option.
126-: The s.stem sends an email to the provider indicatin$ that the data has /een reEected; includin$ the
validatorIs e+planation.
126:: The s.stem redirects the validator to the 'alidator Page.
1269: Return to Scenario 2; step num/er 1.
2.3.1.6.4. Scenario 43 C$ange "ccount Information
(recon;itions3 The validator must /e lo$$ed in to the s.stem ARefer to *se Case 3B. The validator is vie'in$
the 'alidator Page.
(ostcon;itions3 The validator has chan$ed his in!ormation.
1. The validator selects the chan$e account option on the 'alidator Page.
2. The s.stem su/mits an S@" search Cuer. to the data/ase usin$ the lo$in name !or the validator.
3. The data/ase returns all the account in!ormation associated 'ith that validator.
4. The s.stem redirects the validator to the hange 'alidator $nformation Page.
-. The s.stem displa.s a !orm 'ith all the attri/utes associated 'ith the user.
:. The validator chan$es a !ield.
9. The validator selects su/mit chan$es A1"T1B.
(. The s.stem sends the ne' in!ormation to the data/ase.
. The s.stem displa.s a messa$e sa.in$ that the account has /een updated.
10. The s.stem redirects the validator to the 'alidator Page.
11. 7nd o! use case.
"&- 13 The validator selects the cancel option.
1161: The s.stem redirects the user to the 'alidator Page.
1162: 7nd o! use case.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
++i
Software Requirements Specification
2.3.1.6.6. Scenario 63 ?elp
(recon;itions3 The visitor is vie'in$ the 'alidator Page; 'alidate !etadata Page& 'alidate Soft#are Page&
'alidate Glossary %ntry Page& and hange 'alidator $nformation Page.
(ostcon;itions3 The visitor is vie'in$ the 'alidator Help Page.
1. The visitor selects the help option.
2. The s.stem redirects the visitor to the 'alidator Help Page and to the section associated 'ith the pa$e !rom
'hich the visitor came !rom.
3. 7nd o! use case.
2.4. 0eneral Constraints
The !ollo'in$ constraints are reco$niFed.
The data/ase mana$ement s.stem 'ill /e 4racle. The 4racle s.stem 'ill run on a server; and the user
'ill access the server via the Internet.
The clients ma. chan$e the data/ase !rom 4racle to some other commercial product. The desi$n
should minimiFe the impact o! this chan$e.
The s.stem 'ill /e completed /. %ecem/er 1; 2004.
%eveloped 'ith intent o! inte$ratin$ 'ith G74*: use .*7T plat!orm
2.6. "ssumptions an; !epen;encies
1 'indo's compati/le version o! all the 7+ternal #ro$rams 'ill /e made availa/le.
7+amples o! data sets 'ill /e made availa/le prior to *ovem/er 2004.
The #1C7S server 'ill /e a =# #roliant %"3(0; %ual processor; Intel ?74* 3.2 G=F 'ith >indo's
Server 2003; 7nterprise 7dition.
Software Engineering II CS 4311 Fall 2004 !ate
:)21)2014 : %
)#
(age
++ii
Software Requirements Specification
3. Specific Requirements
This section contains e+ternal inter!ace reCuirements; /ehavioral reCuirements; and non6/ehavioral
reCuirements.
3.1. EBternal Interface Requirements
This section contains the speci!ication o! reCuirements !or inter!aces amon$ di!!erent components and their
e+ternal capa/ilities; includin$ all its users; /oth human and other s.stems.
3.1.1. ?ar;ware Interfaces
There are no hard'are inter!ace reCuirements !or this s.stem.
3.1.2. Software Interfaces
3.1.2.1. 0eneral Interface Requirements
[ 1] The s.stem shall have a 'e/6/ased $raphical user inter!ace AG,IB constructed !rom standard
'e/6inter!ace elements such radio /uttons; te+t /o+es; chec3 /o+es; drop do'n lists; ta/les; and
,R"s.
[ 2] The s.stemIs 'e/ inter!ace shall accept user input !rom the 3e./oard and !rom the mouse.
[ 3] The s.stem shall have scroll /ars !or 'e/ pa$es displa.in$ a more te+t than !its in the currentl.
displa.ed 'indo'.
[ 4] The s.stem shall present a con!irmation prompt to the user 'ith the options to continue or cancel
the operation 'henever a user selects an operation that ma. modi!. the contents o! the data/ase.
[ 5] The title !or all the 'e/pa$es on the s.stem shall /e composed o! the te+t GRemote Sensin$
Supermar3etH and the title o! the speci!ic pa$e. Speci!ic pa$e names are $iven in the pa$e
transition map $iven in 1ppendi+ 1: >e/ #a$e Transitions.
[ 6] 7ach 'e/pa$e 'ill displa. h.perlin3s to adEacent pa$es as sho'n in 1ppendi+ 1: >e/ #a$e
Transitions.
[ 7] 1ll 'e/pa$es shall contain the lo$os !rom appropriate sponsors. These include; ,T7#; #1C7S;
*1S1; and G74*. These lo$os shall /e h.perlin3ed to the homepa$es o! these or$aniFations.
[ 8] 7ach 'e/ pa$e that responds to user actions shall have an associated help pa$e. #a$es reCuirin$
help pa$es are sho'n in 1ppendi+ 1: >e/ #a$e Transitions. 7ach help pa$e shall contain
instructions and e+planations on ho' to use the 'e/pa$e associated 'ith it.
3.1.2.2. /isitor (ages
[ 9] The Home)Search 'e/pa$e shall contain a description o! the motivation and purpose /ehind the
s.stem /ein$ /uilt; as sho'n Fi$ure 3 6-: =ome)Search #a$e.
[ 10] The Glossary Page shall contain lin3s to approved remote sensin$ $lossaries availa/le on line
and a list o! terms and de!initions provided /. the client and 18S users.
[ 11] >hen the len$th o! the num/er o! entries displa.ed in The Glossary Page e+ceeds t'o standard
'indo' len$ths; the Glossary Page shall have h.perlin3ed shortcuts to each letter o! the alpha/et
to !acilitate !aster searches.
[ 12] The Site !ap Page shall contain a $raphical representation o! the la.out o! the s.stemIs
'e/pa$es.
[ 13] The Link enter shall displa. a ta/le containin$ lin3s to other sites o! interest.
[ 14] The ontact "s Page shall displa. in!ormation on ho' to contact the persons responsi/le !or the
s.stem and a lin3 to the #1C7S donations 'e/pa$e.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
23
Software Requirements Specification
[ 15] The Advanced Search Page shall displa. ta/le containin$ sensor sources and an interactive map
as sho'n in Fi$ure 364: 1dvanced Search.
LSRSreC 1M The Guided Sensor Search Page shall allo' a visitor to descri/e a source and the s.stem 'ill
search the data/ase !or matchin$ sources as sho'n in Fi$ure 36(: Guided Source Search.
LSRSreC 2M The interactive map in the Advanced Search Page shall allo' !or Foom in; Foom out and placin$
!ootprints on the map.
LSRSreC 3M The Search Results #a$e shall contain the total num/er o! results returned /. the Cuer.; result
descriptions; and lin3s to the ,R" o! the result.
LSRSreC 4M The Search Results Page shall contain a numeric seCuence o! lin3s la/eled 'ith num/ers that
/ehave as !ollo's:
o 4nl. the ne+t - pa$es shall /e displa.ed at a time; !or e+ample G1 2 3 4 - *7?TH
o 1!ter the !irst - results the lin3s la/el shall displa. G#R78 : 9 ( 10 *7?TH
o 4n the last - results the lin3s la/el shall displa. G#R78 11 12 13 14 1-H
o 7ach num/er shall act as a lin3 to that pa$e in the order o! ho' the matchin$ pa$es 'ere
sorted.
Figure 3=63 ?omeSearc$ (age
3.1.2.3. (ro#i;er (ages
LSRSreC -M The Login Page shall provide !or the entr. o! a userIs lo$in name and pass'ord. It 'ill provide a
clic3a/le /utton la/eled G"o$onH.
LSRSreC :M The Pass#ord Recovery Page shall provide !or the user entr. o! an email address. It shall provide
a clic3a/le /utton la/eled GSu/mit.H
LSRSreC 9M The Register Page shall provide !ields !or users to enter the !ollo'in$ te+t elements Athe elements
mar3ed 'ith GOH are reCuiredB:
First *ameO
0iddle Initial
"ast *ameO
7mail 1ddressO
4r$aniFation
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
24
Software Requirements Specification
1ddress
4r$aniFation T.pe
"o$in *ameO
#ass'ordO
8eri!. #ass'ordO
LSRSreC (M The hange Provider $nformation Page shall provide an inter!ace that displa.s all o! the provider
in!ormation o/tained !rom the Register pa$e and allo's a user to modi!. the data.
LSRSreC M The Submit !etadata Page shall allo' a provider to enter a ,R"; a te+t description o! up to 2-0
'ords; a sensor source and the o/served location o! the metadata /. either enterin$ the
coordinates or /. dra'in$ a !ootprint on a map. A1 'ord is a ma+imum o! - characters.B
LSRSreC 10M The Submit Soft#are !etadata Page shall allo' a provider to enter a ,R"; a te+t description o!
up to 2-0 'ords; and a cost. A1 'ord is a ma+imum o! - characters.B
LSRSreC 11M The Submit Glossary (erm Page shall allo' a provider to enter a term and a de!inition. The
de!inition ma. contain up to 2-0 'ords. A1 'ord is a ma+imum o! - characters.B
3.1.2.4. /ali;ator (ages
LSRSreC 12M The validator inter!ace shall /e accessed throu$h a di!!erent ,R" than the visitor and provider
,R".
LSRSreC 13M The 'alidate Soft#are !etadata Page shall displa. the ,R"; description; metadata; and cost o!
metadata entries that have not .et /een validated.
LSRSreC 14M The 'alidate Glossary (erm Page shall displa. the term and description !or each entr. that has
not .et /een validated.
LSRSreC 1-M The hange 'alidator $nformation Page shall provide an inter!ace that displa.s all o! the
validator in!ormation and allo's a user to modi!. the data.
3.2. Communications Interfaces
#1C7S is currentl. involved in the development o! the G74* $rid; a c./erin!rastructure !or the $eolo$ical
sciences. To this end; the 18S s.stemIs !unctionalit. must /e adapta/le to $rid services. The !ollo'in$
reCuirements ena/le the s.stem to /e ported to $rid services in the !uture.
LSRSreC 1:M The 18S s.stem shall provide all o! the search !unctionalit. as >e/ Services.
3.3. 5e$a#ioral Requirements
3.3.1. Same Class of *ser
LSRSreC 19M The primar. s.stem shall support t'o 3inds o! user: 8isitors and #roviders.
LSRSreC 1(M 1 separate site shall support 8alidators. This site shall /e accessed throu$h a di!!erent ,R" than
the ,R" o! the primar. s.stem.
LSRSreC 1M The s.stem shall allo' a user to access the help pa$e !or an. pa$e to 'hich the user has access.
3.3.1.1. /isitor
LSRSreC 20M The s.stem shall allo' a visitor to search !or ima$es or datasets.
LSRSreC 21M The s.stem shall allo' a visitor to search /. usin$ a simple search or an advanced search.
LSRSreC 22M The s.stem shall allo' a visitor to vie' a $lossar. term.
LSRSreC 23M The s.stem shall allo' a visitor to read the help 'e/ pa$es.
LSRSreC 24M The s.stem shall allo' a visitor to vie' a site map.
LSRSreC 2-M The s.stem shall allo' a visitor to read the contact in!ormation to the or$aniFation responsi/le
!or maintainin$ the s.stem.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
26
Software Requirements Specification
LSRSreC 2:M The s.stem shall allo' a visitor to access the lin3 center.
3.3.1.2. (ro#i;er
LSRSreC 29M The s.stem shall reCuire a provider to lo$in /e!ore allo'in$ access to provider !unctions.
LSRSreC 2(M The s.stem shall allo' a provider to su/mit remote sensin$ metadata into the s.stem.
LSRSreC 2M The s.stem shall allo' a provider to su/mit so!t'are metadata into the s.stem.
LSRSreC 30M The s.stem shall allo' a provider to su/mit $lossar. terms into the s.stem.
LSRSreC 31M The s.stem shall allo' a provider to chan$e his)her account in!ormation.
3.3.1.3. /ali;ator
LSRSreC 32M The s.stem shall reCuire a validator to lo$in /e!ore allo'in$ access to provider !unctions.
LSRSreC 33M The s.stem shall allo' a validator to validate remote sensin$ metadata.
LSRSreC 34M The s.stem shall allo' a validator to validate so!t'are metadata into the s.stem.
LSRSreC 3-M The s.stem shall allo' a validator to validate $lossar. terms into the s.stem.
3.3.2. Relate; Real=worl; )%Cects
*o !urther related real6'orld o/Eect reCuirements have /een identi!ied.
3.3.3. Stimulus
LSRSreC 3:M >hen the visitor selects a h.perlin3 on an. o! the s.stemIs pa$es; the s.stem shall redirect the
visitorIs /ro'ser to the lin3Is tar$et pa$e. "in3s internal to the s.stem are descri/ed in 1ppendi+
1: >e/ #a$e Transitions.
3.3.3.1. /isitor Stimulus
LSRSreC 39M >hen a visitor selects the Search option and no search criteria have /een entered or selected; the
s.stem shall i$nore the selection and continue to displa. the current pa$e.
LSRSreC 3(M >hen a visitor selects the Search option and a search Cuer. has /een entered on the Home Search
pa$e; the s.stem shall scan the search Cuer.; e+tract 3e. 'ords; construct and su/mit an S@"
Cuer. to the %<0S; and displa. the results in a Search Results pa$e.
LSRSreC 3M >hen a visitor selects the su/mit option on the Advanced Search Page; the s.stem shall construct
an S@" Cuer. /ased on the visitorIs entries. The S@" Cuer. shall /e sent to the data/ase.
LSRSreC 40M >hen the s.stem receives results !rom the data/ase !or a Cuer.; the s.stem shall /uild and
displa. the results d.namicall..
LSRSreC 41M 4n the Advanced Search Page; upon the visitor clic3in$ on another continent lin3 the s.stem
shall s'itch the de!ault map to that continentIs map.
LSRSreC 42M >hen the visitor clic3s on the Footprint /utton the s.stem shall chan$e the cursor into a crosshair
and ena/le dra'in$ !ootprints on the map.
LSRSreC 43M >hen dra'in$ !ootprints is ena/led; i! the visitor clic3s and holds the le!t /utton o! the mouse on
the map the s.stem shall start dra'in$ a !ootprint.
LSRSreC 44M >hen dra'in$ !ootprints is ena/led and i! the visitor is holdin$ the le!t /utton o! the mouse; i!
the visitor dra$s the mouse over an area a !ootprint shall /e dra'n on the map.
LSRSreC 4-M >hen dra'in$ !ootprints is ena/led and i! the visitor is holdin$ the le!t /utton o! the mouse; i!
the visitor releases the le!t /utton o! the mouse the s.stem shall disa/le dra'in$; chan$e the
crosshair cursor into a normal cursor and !ill in the coordinates.
LSRSreC 4:M >hen dra'in$ !ootprints is ena/led; and the user clic3s on an area outside o! the map the s.stem
shall disa/le !ootprint dra'in$ and s'itch the crosshair cursor to the normal cursor.
LSRSreC 49M 4n the Guided Sensor Search Page upon the user ans'erin$ at least one Cuestion; the s.stem
shall construct an S@" Cuer. /ased on options selected. The S@" Cuer. shall /e sent to the
data/ase.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
26
Software Requirements Specification
LSRSreC 4(M >hen the s.stem receives results !rom the data/ase !or a source search Cuer.; the s.stem
shall redirect the user to the Advanced Search Page and !ill the d.namic ta/le 'ith the
returned matches.
LSRSreC 4M 4n the Search Results Page; upon the visitor clic3in$ on a ,R" lin3 the s.stem shall redirect the
/ro'ser to that ,R" and capture the I# address o! the visitor; the time; and the tar$et ,R".
LSRSreC -0M 4n the Search Results Page; upon the visitor clic3in$ on the numeric lin3 the s.stem shall
redirect the /ro'ser to the results o! that pa$e.
LSRSreC -1M 4n the Search Results Page; upon the visitor clic3in$ on the #R78)*7?T lin3 the s.stem shall
redirect the /ro'ser to the results o! the previous)ne+t pa$e respectivel..
3.3.3.2. (ro#i;er Stimulus
LSRSreC -2M >hen a user selects the Su/mit option on the Register Page; the s.stem shall validate the entr.;
store the entr. in the data/ase; and send an email to the user.
LSRSreC -3M The s.stem shall consider a re$istration entr. to /e valid i! all the reCuired !ields have te+t; the
pass'ord and veri!. pass'ord entries are identical and non6empt.; the lo$in name does not
alread. e+ist in the user ta/le o! the data/ase; and the email address consists o! letters and di$its;
periods; and e+actl. one GPH s.m/ol. The !ollo'in$ !ields are reCuired:
o First *ame
o "ast *ame
o 7mail 1ddress
o "o$in *ame
o #ass'ord
o 8eri!. #ass'ord
LSRSreC -4M >hen a user selects the Su/mit option on the Login Page; the s.stem shall attempt to authenticate
the user. The s.stem shall create an S@" Cuer.; su/mit it to the data/ase; and accept a response.
The Cuer. 'ill consist o! the user lo$in name and the pass'ord. The s.stem must encr.pt the
lo$in in!ormation prior to sendin$ data across the internet.
LSRSreC --M >hen the s.stem authenticates a provider; the s.stem shall displa. the Provider pa$e.
LSRSreC -:M >hen the s.stem !ails to authenticate a provider; the s.stem shall 'ait !ive seconds and then
displa. the !ollo'in$ error messa$e GIncorrect pass'ord or incorrect user.H
LSRSreC -9M >hen the user selects the su/mit option on the Pass#ord Recovery pa$e; the s.stem shall
construct an S@" Cuer. usin$ the data entered in the email address input area. The Cuer. shall /e
sent to the data/ase.
LSRSreC -(M I! a pass'ord recover. Cuer. returns a match; an email containin$ a temporar. pass'ord shall /e
sent to the email address. AThis is actuall. a securit. hole.B
LSRSreC -M I! a pass'ord recover. Cuer. !ails to return a match; the s.stem shall displa. an error messa$e.
LSRSreC :0M >hen a provider selects the lo$o!! option on an. provider pa$e; the s.stem shall lo$ the user o!!
the s.stem and return to the Home Search Page.
LSRSreC :1M >hen a provider selects the su/mit option on the Submit !etadata; the Submit Soft#are
!etadata& or the Submit Glossary (erm pa$e; the s.stem shall capture the input in!ormation and
send a S@" Cuer. storin$ this in!ormation as unveri!ied metadata.
LSRSreC :2M >hen the s.stem displa.s the hange Provider $nformation pa$e; the s.stem 'ill e+tract
re$istration in!ormation !rom the data/ase !or the currentl. lo$$ed in provider. The pa$e 'ill
appear as the re$istration pa$e does; e+cept that the !ields 'ill /e !illed 'ith the provider
in!ormation.
LSRSreC :3M >hen a provider selects the su/mit option on the hange Provider $nformation pa$e; the s.stem
shall validate the in!ormation in the same manner as !or the Re$ister ,ser pa$e.
LSRSreC :4M >hen a provider selects the su/mit option on the hange Provider $nformation pa$e and the
s.stem validates the in!ormation; the s.stem shall su/mit an S@" Cuer. to update the data/ase
'ith the ne' data.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
28
Software Requirements Specification
3.3.3.3. /ali;ator Stimulus
LSRSreC :-M >hen the validator selects the accept option on a 'alidate !etadata Page; the s.stem shall mar3
the data as veri!ied; update the data/ase; and send an email to the provider noti!.in$ the provider
that the metadata has /een accepted.
LSRSreC ::M >hen the validator selects the reEect option on a 'alidate !etadata Page the s.stem shall open a
dialo$ to allo' the validator to enter an e+planation !or the reEection. >hen the validator has
completed this and selects send; the s.stem shall update the data/ase and send an email to the
provider includin$ the e+plaination.
LSRSreC :9M >hen the validator selects the accept option on a 'alidate Glossary Page; the s.stem shall mar3
the data as veri!ied; update the data/ase; and send an email to the provider noti!.in$ the provider
that the $lossar. term has /een accepted.
LSRSreC :(M >hen the validator selects the reEect option on a 'alidate Glossary Page the s.stem shall open a
dialo$ to allo' the validator to enter an e+planation !or the reEection. >hen the validator has
completed this and selects send; the s.stem shall update the data/ase and send an email to the
provider includin$ the e+plaination.
LSRSreC :M >hen the validator selects the accept option on a 'alidate Soft#are !etadata Page; the s.stem
shall mar3 the data as veri!ied; update the data/ase; and send an email to the provider noti!.in$
the provider that the metadata has /een accepted.
LSRSreC 90M >hen the validator selects the reEect option on a 'alidate Soft#are metadata Page the s.stem
shall open a dialo$ to allo' the validator to enter an e+planation !or the reEection. >hen the
validator has completed this and selects send; the s.stem shall update the data/ase and send an
email to the provider includin$ the e+plaination.
LSRSreC 91M >hen the s.stem displa.s the hange 'alidator $nformation pa$e; the s.stem 'ill e+tract
re$istration in!ormation !rom the data/ase !or the currentl. lo$$ed in validator. The pa$e 'ill
appear as the re$istration pa$e does; e+cept that the !ields 'ill /e !illed 'ith the validator
in!ormation.
LSRSreC 92M >hen a provider selects the su/mit option on the hange 'alidator $nformation pa$e; the s.stem
shall validate the in!ormation in the same manner as !or the Re$ister ,ser pa$e.
LSRSreC 93M >hen a provider selects the su/mit option on the hange 'alidator $nformation pa$e and the
s.stem validates the in!ormation; the s.stem shall su/mit an S@" Cuer. to update the data/ase
'ith the ne' data.
3.3.4. Relate; Features
3.3.4.1. 2uer'ing
LSRSreC 94M The input to searches shall /e T<%QQQ. The s.stem shall T<%QQQ
LSRSreC 9-M The results o! searches shall /e ordered. The orderin$ shall /e determined /. the de$ree o! match
o! the result to the Cuer. and the availa/ilit. o! the 'e/ pa$e server !or the tar$et site. Given the
same de$ree o! match; a more availa/le server shall appear a/ove a less availa/le one.
3.3.4.2. "utomate; !ata Collection
LSRSreC 9:M The s.stem shall test and record the availa/ilit. o! provider sites /. chec3in$ the site !our times
per da..
LSRSreC 99M The s.stem shall detect and record the I# address o! each visitor. The I# address; the date and
time o! the visit; and an. site visited via clic3 throu$h shall /e recorded.
3.3.4.3. Creating ";ministrati#e Reports
LSRSreC 9(M The s.stem shall support the creation o! the !ollo'in$ reports: S.stem ,sa$e Report; 1vaila/le
"in3 Report; and #endin$ 0etadata Report.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
29
Software Requirements Specification
LSRSreC 9M The S.stem ,sa$e Report shall contain data a/out the num/er o! Cueries !or a $iven time; the
avera$e Cueries /. time o! da.; and the avera$e Cueries per month. The reports shall contain
ta/ular as 'ell as $raphical outputs.
LSRSreC (0M The 1vaila/le "in3 Report shall displa. a summar. o! the availa/ilit. o! sites re$istered 'ith the
s.stem.
LSRSreC (1M The #endin$ 0etadata Report shall displa. a summar. o! metadata su/mitted /. providers /ut
not .et approved /. validators.
3.3.6. Functional
*o !urther !unctional reCuirements have /een identi!ied.
3.4. ,on=%e$a#ioral Requirements
3.4.1. (erformance Requirements
LSRSreC (2M The s.stem shall /e a/le to service at least 100 hits per second.
LSRSreC (3M The s.stem shall send an email 'ith a pass'ord 'ithin 1 second o! reCuest.
LSRSreC (4M The s.stem shall /e a/le to process 20 Cueries per second 'ith a response time o! 1 second or
less.
3.4.2. 2ualitati#e Requirements
3.4.2.1. "#aila%ilit'
*o availa/ilit. reCuirements have /een identi!ied.
3.4.2.2. Securit'
LSRSreC (-M The s.stem AserverB shall restrict access to provider and validator !unctions /. usin$ a userid and
pass'ords.
LSRSreC (:M The s.stem shall encr.pt the pass'ords in the %<0S.
LSRSreC (9M The s.stem shall never send an unencr.pted pass'ord over the internet.
LSRSreC ((M #ass'ords shall al'a.s /e encr.pted usin$ the .*7T 7ncr.ption component.
3.4.2.3. +aintaina%ilit'
*o maintaina/ilit. reCuirements have /een identi!ied.
3.4.2.4. (orta%ilit'
LSRSreC (M The s.stem shall /e compati/le 'ith the !ollo'in$ 'e/ /ro'sers: Internet 7+plorer; 0oFilla;
4pera; and *etscape. 1ll input !unctions shall /e tested under these s.stems.
3.4.3. !esign an; Implementation Constraints
LSRSreC 0M The s.stem desi$n shall /e an o/Eect6oriented desi$n. This desi$n shall /e documented usin$ the
CRC %esi$n 1ssistant.
LSRSreC 1M The s.stem shall /e implemented usin$ the .*7T architecture. The s.stemIs G,I shall /e /uilt as
>e/ 1pplications.
3.6. )t$er Requirements
3.6.1. !ata%ase
LSRSreC 2M The s.stem shall inter!ace 'ith a %<0S descri/ed in 7rror: Re!erence source not !ound
LSRSreC 3M The data/ase s.stem on the server side shall /e an 4racle data/ase. The %<0S shall /e provided
/. #1C7S.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
2>
Software Requirements Specification
LSRSreC 4M The data/ase shall /e !actored into third normal !orm or <o.ce6Codd normal !orm in order to
avoid update and delete anomalies.
3.6.2. )perations
LSRSreC -M 4peration o! the s.stem shall /e handed over to the #1C7S sta!! upon deliver. o! the s.stem.
3.6.3. Site ";aptation
Since the s.stem 'ill /e installed and 'ill run on the #1C7S server; no additional site adaptation is necessar..
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
30
Software Requirements Specification
4. "ppen;iB "3 4e% (age -ransitions
Figure 4=63 /isitor 4e% (age -ransition !iagram
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
31
Software Requirements Specification
Figure 4=83 /ali;ator 4e% (age -ransition !iagram
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
32
Software Requirements Specification
6. "ppen;iB 53 !ata%ase Fiel;s
The !ollo'in$ ta/les descri/e the data and in!ormation reCuired. It is or$aniFed /. topic.
This ta/le contains all the accounts !or re$istered users.
-a%le 33 "ccount Information
!ata Element !escription
"o$in name 1 user lo$in name. This must /e uniCue in the s.stem Ano t'o users can have
the same lo$in nameB. The lo$in name ma. /e upto 32 characters lon$.
76mail 1ddress 1 valid email address. 8alid email addresses must have the !ollo'in$ !ormat:
RusernameS P RhostnameS R. Su/domainST . RdomainS
The username in the email does not need to match the lo$in name.
#ass'ord 1 pass phrase used to access the s.stem. #ass phrases must /e at least 4
characters lon$; and the. ma. /e up to 2-: characters. Spaces and special
characters are allo'ed. #ass phrases are case sensitive.
*ame The name Atitle; !irst; middle; and lastB o! the account holder.
Contact in!ormation The ph.sical mail address o! the account holder. >or3 and !a+ phone num/ers
AoptionalB.
4r$aniFation The name and location o! the or$aniFation and department 'ith 'hich the
account holder is a!!iliated.
1ccount T.pe The t.pe o! user: 8isitor; #rovider; 8alidator; 1dministrator.
This ta/le contains all the metadata !or the s.stem.
-a%le 43 +eta;ata
!ata Element !escription
,R" The internet location o! the data descri/ed /. this metadata entr.
Title 1 /rie! A(0 characterB phrase used to identi!. the data set.
%escription
1 natural lan$ua$e description o! the dataset descri/ed /. this metadata
entr.. %escriptions can /e up to 10;000 characters.
4r$aniFation The name and contact in!ormation !or the or$aniFation sponsorin$ the ,R".
Source The sensor used to collect the data.
Ran$e The minimum and ma+imum latitudes and lon$itudes /oundin$ the dataset.
8alidated 1 <oolean !la$ that 'hen true; indicates the metadata has /een validated and
is availa/le to the $eneral pu/lic.
8alidation entr. ,ser name o! validator and the date and time o! validation. 1lso; notes added
/. validator such as Eusti!ication !or reEection.
0etadata T.pe So!t'are or %ataset
This ta/le contains all the sensors and their respective attri/utes.
-a%le 63 Instrument Information
!ata Element !escription
Instrument title Instrument title; such as "andsat.
Spectral Resolution
Spatial Resolution
Cost %escription o! the cost structure.
%escription *atural lan$ua$e description o! instrument; up to 10;000 characters.
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
33
Software Requirements Specification
This ta/le contains $lossar. entries.
-a%le 63 0lossar' information
!ata Element !escription
7ntr. >ord or phrase to /e de!ined.
%e!inition ,p to 204( characters de!inin$ the entr..
T.pe
8eri!ied 1 <oolean !la$ that 'hen true; indicates the metadata has /een validated and
is availa/le to the $eneral pu/lic.
8alidation entr. ,ser name o! validator and the date and time o! validation. 1lso; notes added
/. validator such as Eusti!ication !or reEection.
This ta/le contains the lin3s !or the "in3 Center
-a%le 83 &in@ Center !ata
!ata Element !escription
Title Title to appear as the h.per lin3.
%escription ,p to 10;000 characters descri/in$ the lin3
,R" The tar$et o! the lin3
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
34
Software Requirements Specification
6. "ppen;iB C3 "/S S'stem Class !iagram
Provider Validator
Help
SearchEngine Results
0..* 1 0..* 1
LinkCenter
Map
Glossar
G!"
1..*
1
1..*
1
1
1
1
1
1..* 1..*
1
1
1
1
1
1
1
1
Login
1..*
1
1..*
1
#ccount
11
Registered
!ser
1
1..*
1
1..*
1
1
1
1
%ata&ase
"nter'ace
1
1
1
1
1
1..*
1
1..*
1
11
1
Figure 6=93 Class !iagram
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
36
Software Requirements Specification
8. "ppen;iB !3 "/S S'stem !ata Flow !iagram
Figure 8=>3 !ata Flow !iagram D /isitor
Figure 8=103 !ata Flow !iagram D (ro#i;er
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
36
Software Requirements Specification
Figure 8=113 !ata Flow !iagram D /ali;ator
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
38
Software Requirements Specification
9. "ppen;iB E3 "/S S'stem (rotot'pe
Figure 9=123 C$ange (ro#i;er Information
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
39
Software Requirements Specification
Figure 9=133 ";#ance; Searc$
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
3>
Software Requirements Specification
Figure 9=143 +eta;ata /ali;ation
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
40
Software Requirements Specification
Figure 9=163 &ogin
Figure 9=163 (ro#i;er Registration
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
41
Software Requirements Specification
Figure 9=183 Su%mit +eta;ata
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
42
Software Requirements Specification
Figure 9=193 /ali;ator ?omepage
Figure 9=1>3 0ui;e; Source Searc$
E
So!t'are 7n$ineerin$ II CS 4311 Fall 2004 %ate
6212014 3 !
(
#a$e
43

Das könnte Ihnen auch gefallen