3.2. Behavioral Requirements - Courses - University of Texas at El ...

herbunalaskaΔιαχείριση Δεδομένων

30 Ιαν 2013 (πριν από 4 χρόνια και 11 μήνες)

199 εμφανίσεις

DRAFT


Software Engineering Fall 2007















CS 4310 Fall 2007

herbunalaska_666e293c
-
4a75
-
4e54
-
a0fc
-
192a98db7a02.doc


Meteorological


Image


Environmental

Repository

Software Requirements Specification


Version

1.4

3/18/2013

Meteorological, Image, ‘n Environmental Data Repository

DRAFT

Meteorological, Image, ‘n Environmental
Data Repository



CS 4310 Fall 2007


Page
ii





Document Control

Approval

The Guidance Team and the customer will approve this document.

Document

Change Control

Initial Release:

January

15
, 200
8

Current Release:

February

7
, 200
8

Indicator of Last Page in Document:



Date of Last Review:

February 6
, 2008

Date of Next Review:

February 10
, 2008

Target Date for Next Update:

February 11
, 2008

Dis
tribution List

This following list of people will receive a copy of this document every time a new version of this document
becomes available:

Guidance Team Members:

Dr. Ann Gates

E
rnesto Medina





Customer
(s)
:

Dr.
Craig Tweedie






Santonu Goswami


Soft
ware Teams
:

Synergy

Circular Logic

Black Lab

Edge
d

Solutions

Change Summary

The following table details changes made between versions of this document


Version

Date

Modifier

Description

1.0

01/05/08

Medina


Created
baseline SRS

1.1

1/26/08

Medina; Gates

Corrections to Sections 1
-
2; revised interface diagrams;
moved scenarios to appendix; revisions to Section 3.1;
revised name of system

1.2

1/30/08

Medina

M
odified interface templates; a
dded panel display a
nd
menu screenshots in Appendix
B
.

1.3

1/30/08

Me
dina
; Gates

U
p
dated references to figures in S
ection 3. Updated
Sections 3.1 and 3.2
.

Meteorological, Image, ‘n Environmental Data Repository

DRAFT

Meteorological, Image, ‘n Environmental
Data Repository



CS 4310 Fall 2007


Page
iii






Version

Date

Modifier

Description

1.4

2/6/08

Medina; Gates

Consistency Check, References, and Corrections

1.4.1

2/8/08

Gates

Complete Stimulus Response; modifications to
all
requirements; screen shots
and scenarios need
corrections; validation with customer pending

Meteorological, Image, ‘n Environmental Data Repository

DRAFT

Meteorological, Image, ‘n Environmental
Data Repository



CS 4310 Fall 2007


Page
iv





T
ABLE OF
C
ONTENTS

DOCUMENT CONTROL

................................
................................
................................
...........................

II

A
PPROVAL

................................
................................
................................
................................
..................

II

D
OCUMENT
C
HANGE
C
ONTROL

................................
................................
................................
................

II

D
ISTRIBUTION
L
IST

................................
................................
................................
................................
...

II

C
HANGE
S
UMMARY

................................
................................
................................
................................
...

II

1.

INTRODUCTION

................................
................................
................................
................................
.

1

1.1.

P
URPOSE AND
I
NTENDED
A
UDIENCE

................................
................................
..............................

1

1.2.

S
COPE OF
P
RODUCT

................................
................................
................................
........................

1

1.3.

D
EFINITIONS
,

A
CRONYMS
,

AND
A
BBREVIATIONS

................................
................................
..........

2

1.3.1.

Definitions

................................
................................
................................
...............................

2

1.3.2.

Acronyms

................................
................................
................................
................................
.

4

1.3.3.

Abbreviations

................................
................................
................................
...........................

4

1.4.

O
VERVIEW

................................
................................
................................
................................
......

4

1.5.

R
EFERENCES

................................
................................
................................
................................
...

5

2.

GENERAL DESCRIPTION

................................
................................
................................
.................

6

2.1.

P
RODUCT
P
ERSPECTIVE

................................
................................
................................
.................

6

2.2.

P
RODUCT
F
EATURES

................................
................................
................................
.......................

6

2.2.1.

Actors

................................
................................
................................
................................
.......

8

2.2.2.

Use Cases

................................
................................
................................
................................

8

2.2.
3.

Scenarios

................................
................................
................................
................................
.

8

2.3.

U
SER
C
HARACTERISTICS

................................
................................
................................
................

8

2.4.

G
ENERAL
C
ONSTRAINTS

................................
................................
................................
................

9

2.5.

A
SSUMPTIONS AND
D
EPENDENCIES
................................
................................
................................

9

2.6

.

F
UTURE
E
NHANCEMENT

................................
................................
................................
..............

9

3.

SPECIFIC REQUIREMENT
S

................................
................................
................................
...........

11

3.1.

E
XTERNAL
I
NTERFACE
R
EQUIREMENTS

................................
................................
.....................

11

3.1.1.

User Interfaces

................................
................................
................................
......................

11

3.1.2.

Hardware Interfaces

................................
................................
................................
..............

18

3.1.3.

Software Interfaces

................................
................................
................................
................

18

3.1.4.

Communications Interfaces

................................
................................
................................
...

18

3.2.

B
EHAVIORAL
R
EQUIREMENTS

................................
................................
................................
.....

18

3.2.1.

Same Class of User

................................
................................
................................
................

18

3.2.2.

Related Real
-
world Objects

................................
................................
................................
...

19

3.2.3.

Related Features

................................
................................
................................
....................

24

3.2.4.

Stimulus Response

................................
................................
................................
.................

24

3.2.5.

Functional

................................
................................
................................
..............................

28

3.3.

N
ON
-
BEHAVIORAL
R
EQUIREMENTS

................................
................................
.............................

28

3.3.1.

Performance Requirements

................................
................................
................................
...

28

3.3.2.

Qualitative Requirements

................................
................................
................................
......

28

3.3.3.

Maintainability

................................
................................
................................
......................

29

3.3.4.

Portability

................................
................................
................................
..............................

29

3.3.5.

Security

................................
................................
................................
................................
..

29

3.3.6.

Design and Implementation Constraints

................................
................................
...............

29

3.4.

O
THER
R
EQUIREMENTS

................................
................................
................................
...............

29

APPENDIX A. SCENARIO
S

................................
................................
................................
.....................

30

APPENDIX B. INTERFAC
E SCREENSHOTS

................................
................................
.......................

36

4.

APPENDIX C FILE FORM
A
TS

................................
................................
................................
.......

43

Software Requirements Specificatio
n



DRAFT

Software Requirements Specification

CS 4310 Fall 2007


Page

1


1.

Introduction

1.1.

Purpose and Intended Audience

The purpose of the Software Requ
irements Specification (SRS) document is

to provide a clear and precise
description of the fu
nctionality of the
Meteorological, Image, ‘n Envi
ronmental Data Repository

(
MInER
). For
the customer, the SRS serves as a list of all

the

functions that
the final product will perform.
Throughout the
development process
,

the SRS will serve as a reference for product design
, implementation

and
maintenance
.
Finally the SRS is an agreement among
st

the client and
the
development team on requirements regarding the
MInER

system to be developed.

The

requiremen
ts are separated into two parts:

behavioral and non
-
behavioral requirements. The behavioral
requirement
s describe the interaction
s

between the system and
user
s as well as define

the system’s inputs,
outputs, and processing of data
.
The n
on
-
behavioral requirements relate to the attributes of the system.

The
intended audience of this document is the client,
the Environmental Sciences program at the University of
Texas at El Paso (UTEP)
, the guidance team, and the software development team. All the
presented
requirements have been gathered from the customer
through a variety of

elicitation techniques
, includin
g
interviews, observation, and prototyping
. Throughout the document
,

acronyms and abbreviations are used; the
definitions, acronyms, and abbreviations are

provided in Section 1.3

for clarification purposes
.

1.2.

Scope of Product

In recent years
,

environmental s
cientists have
been observing
significant ch
anges in Earth’s climate. Studying

the consequ
ences of climate trends requires data
-
driven
techniques
. To meet this need, t
he

scientists at

UTEP

have developed a sophisticated autonomous data collection system

th
at uses a
robotic

tram
equipp
ed with
multiple sensors and

deployed at an arctic research site. This tram system is capable of taking and recording
environmental data at regular intervals for a
total of

300 meters. The data collected by this tram consists
of
spectral rea
dings, ground temperature, ground moisture, wind velocity, light spectrum
,

and

temperature under
the shade

and photographs.

Currently the
UTEP
research team submits and ret
rieves their collected data
from a PostrgreSQL

database

using

Struct
ured Query Language

(SQL)
. There are no automated data entry

tool, data

retrieval tools, data integrity
tools,
automated data analysis tools, or
a
common

interface
to retrieve data from

multiple data sources. The

development

team’s goal is to develop a d
ed
icated tool
that will replace
the UTEP research team
’s

current
process with a much m
ore efficient and practical one
.

Such
a
tool will be a web
-
based application that integrates
multip
le data sources
. As a web
-
based application
,

the

system will provide the
research team with flexibility
and accessibility over the Web. Additionally
,

it will provide functionality for data retri
eval,

filtered and

p
rocessed data downloads
,

and

data an
alysis and data integrity.

Software Requirements Specificatio
n



DRAFT

Software Requirements Specification

CS 4310 Fall 2007


Page

2



1.3.

Definitions, Acronyms, and Abbreviations

1.3.1.

Definiti
ons

The definitions in this section are given in the context of the product being developed. This intention is to assist
the user in their understanding of the requirements for the system.

TERM

DEFINITION

Actor

An
external
entity
that

interacts with

the

MInER

system.

Action button

A GUI element that causes an event to occur.

Apache

Server


A server developed by the Apache Software Foundation used to serve web pages.

Approved Data

Data
that

has been allowed entry into the
MInER

Postgres database by an

Administrator.

Authenticate

To verify that a given username and password pair are included in the
MInER

set of
valid user name and password pairs.

Button

An action button in a GUI.

Configuration Options

Settings
defined by a user
that control the beh
av
ior of a system
.

Data Logger

A device deployed in the field that records weather data from one or more external
sensors
.

Data Set

A collection metadata and readings of a particular type
.

Flat File

A text file

that contains a data set
.

GUI elements

Gra
phical user interface options used for user input, e.g., checkbox, action button,
pull
-
down box, radio button, and textbox.

Hyper Spectral
Spectrometer

An instrument that is u
sed to take spectral readings
.

Irradiance

R
adiometry

terms for the power of
electromagnetic radiation

at a surface, per unit
area

[5]
.

JPEG

A
digital image file format
.

Linux

A

Unix
-
like operating system available for most hardware computing platforms.

Message boxes

A GUI interface that warns the user when an incorrect action has occurred or when
more

information is required from the user. There are two types of message boxes
in MInER: warning
-
message box and confirmation
-
message box.

Metadata

Data describing
a set of readings that includes
date, time, location that the data was
collected
.

Mouse

Any
cursor input device supported by the operating system.

Option

A control used

to make a selection
; examples include

button,

Universal Resources
Locator link,
slide

or other common GUI construct
.

Panel

A container for organizing the contents of a window
.

Pending Data

Data
awa
iting Administrator approval before being
enter
ed into

the
MInER

PostgreSQL

database

Software Requirements Specificatio
n



DRAFT

Software Requirements Specification

CS 4310 Fall 2007


Page

3


PostgreSQL

An

object
-
relational database management system that is used by
MInER

to store
and retrieve data.

Privileges

A
ccess rights

associated wi
th

differ
ent types of users
.

Quality Flags

An indication
.
of how similar a data set’s trend or pattern is to the data set’s
expected trend or pattern.

Query

A request to a database for accessing information.

Radiance

radiometric

measures that describe the amount of light that passes through or is
emitted from a particular area, and falls within a given
solid ang
le

in a specified
direction. They are used to characterize both emission from diffuse sources and
reflection from
diffuse

surfaces

[6]
.

Reflectance

Incident radiation

reflected by a surface
[7]. Reflectance = Radiance/Irradiance

Retrieved Data Summary

A summary containing information about previously retrieved data sets. Includes
the following: user name, date and time of data retrieval and data type.

Robotic Tram

A
system consisting of a cart traveling on an elevated track used to take different
measurements.

Session

A length of time defined by how long a user is logged into the
MInER

system.

Spectra
l Data

The most precise description of the color of an object. Si
nce an object

s color
appearance results from light being changed by it and reflected to the viewer,
spectral data describes how that reflected light was changed. The percentage of
reflected light is measured at several intervals across its spectrum of wav
elengths,
which is then visually represented as a spectral curve.

Structured

Query
Language

A computer language to retrieve data stored in a database management system.

Tab Section

A graphical navigation element that is used for navigating through
differ
ent p
ages.

Text Box

A
rectangular area
where text can be typed.

Text Field

A
rectangula
r area
where text can be typed

and that i
ncludes scrolling capability.

Weather Station:

A collection of different sensors that gather
data
. A weather station may b
e
compri
sed of the following sensors:



Rain: The amount of rain measured at the weather station



Humidity: Measures atmospheric moisture



Temperature: Measures air temperature



Wind: Measures wind speed and velocity



Barometer: Measures atmospheric pressure



Th
aw Depth Probe: Measures the
thawed depth of the permafrost
covered

ground.



Soil Moisture Probe: Measures the moisture saturation in the soil.


Web browser

An application used to display html documents.

Web
Programming
Language


A language used to develo
p web pages
, e.g., PHP or
JavaScript.

Web servers

A program
that

accepts and replies to HTTP requests from clients.

Web
-
based Application

An application
that is accessed via the Internet or an I
ntranet.

Software Requirements Specificatio
n



DRAFT

Software Requirements Specification

CS 4310 Fall 2007


Page

4


1.3.2.

Acronyms

ACRONYM


DESCRIPTION

GMT

Greenwich Mean

Time

GPS

Global Positioning System

GUI

Graphical User Interface

HTTP

Hypertext Transfer Protocol

JPEG

Joint Photographic Experts Group

MInER

Meteorological, Image, ‘n Environmental Data
Repository

NDVI

Normalized Difference Vegetation Index

nm

nano
meter

PAR

Photosynthetically Active Radiation

PHP

PHP
-

Hypertext Pre
-
Processor

RH

Relative Humidity

SRS

Software Requirements Specification

SQL

Structured Query Language

TCP/IP

Transmission Control Protocol/ Internet
Protocol

UTEP

University of Texa
s at El Paso

WBI

Water Band Index

VWC

Vegetation Water Content

1.3.3.

Abbreviations

ABBREVIATION

MEANING

Admin

Administrator

C
onfig

Configure

e.g.

For example

i.e.

That is

1.4.

Overview

The SRS is divided into three four sections: Introduction (Section 1), Ge
neral Description (Section 2), Specific
Requirements (Section 3), and Appendices (Section 4).

Section 1
presents

the purpose and int
ended audience of the document, the scope of the product, organization of
Software Requirements Specificatio
n



DRAFT

Software Requirements Specification

CS 4310 Fall 2007


Page

5


the document, and references. In addition, the s
ection defines terms used in the document, and it lists
acronyms
and abbreviations. Section 2
describes the system to be developed
, its overall structure,
and its functionality. In
addition, the section presents a use
-
case diagram and scenarios as well as

general constraints
,
assumptions and
dependencies of the
proposed system
. Section 3 includes four major subsections
:
Section 3.1
presents

requirements that are re
lated to the external interface;

Section 3.2
presents

the functional requirements;
Section
3.
3
describes the

non
-
behavioral requirements
; and
Section 3.4 outlines database, operations and site adaptation
requirements.
Section 4 provides supplementary material discussed in the document.

1.5.

References


[1]

Black Lab Team, Quality Flags memorandum. Universi
ty of Texas at El Paso, Software Engineering
class Fall 2007, November 2007.

[2]

Edged Solutions, Additional Questions memorandum. University of Texas at El Paso, Software
Engineering class Fall 2007, November 17, 2007.

[3]

Goswami, S. et al.
Spectral Data Process
ing Software: SpecPro
. Technical Report. The University of
Texas at El Paso, Environmental Science, 2008.

[4]

Guidance Team, “Requirements Definition Document”, El Paso, University of Texas at El Paso
,
August 2007
.

[5]

Wikipedia, “Irradiance,” accessed February 6,

2008.

[6]

Wikipedia, “Radiance,” accessed February 6, 2008.

[7]

Wikipedia, “Reflectance,” accessed February 6, 2008.



Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

6


2.

General Description

2.1.

Product Perspective

The system
described in this document
is called the
Meteorological, Image

‘n Environmental Data Reposit
ory

(
MInER
)
. The system will integrate data obtained from multiple weather sensors operating in the Arctic region.
It will also provide a web
-
based tool that will allow researchers and the general public to access this data. In
addition, users will be a
ble to submit data for an approved upload to the system database.
The system will also
provide functionalities that would allow the users to study the dat
a as well as quality flags that indicate the
quality of data sets.


2.2.

Product Features

Fig
ure

1 present
s a
level
-
1
use case diagram
for

the

MInER

from a user’s perspective.

Figure 2 presents

a more
detailed view of the
MInER
. In both figures, t
he
stick figures

represent
actors
, i.e., entities

that interact with the
MInER
,
and the ovals represent the use cas
es supported by the
MInER
. Each are
described next
.



Figure 1.

Level 1 Use Case diagram

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

7



Figure 2.

Level 2 Use Case diagram

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

8


2.2.1.

Actors

The
MInER

classifies actors into
the following

groups:

o

General User
: The general user
represents
a user
who

perform
s

“non
-
administrative tasks
”. This a
ctor
has the ability to
view graphical data.


o

Registered

User
: The registered user

represents
a
user
who

must register with the
MInER

in

order to
visualize, download, a
nd submit
data.


o

Administrator
: The administrative

user
represents

a

user
who

perform
s

“admin
istrative tasks”.
In
addition to having the abilities of a
registered

user, t
his

actor has the ability to
create new users, modify
user accounts, delete users, validate submitted data, and view session logs of the system.

o

Data
Repository
: Th
e data repository represents the various databases that hold data col
lected from
sensors,
weather station
data
, the
spectral
data
, and
images
.


2.2.2.

Use Cases

The
MInER

supports the
following

main

use cases
:

o

Register


the activity of entering information need
ed to

gain research access

o

Retrieve Data


request

data from data stores for use by the system.

o

Submit Data
-

upload

data to be entered into the data repository.

o

Manage Users
-

perform the duties needed to control user access to the system.

o

Manage Submitted
Data
-

approve or reject submitted data

o

Manage
Sites
-

change the settings of current sites, delete sites, or add new sites.


The
MInER

supports the following include/extend use cases:

o

Login
-

enter

a username and password.

o

Plot

Data
-

graph
data that has bee
n retrieved from the
MInER
.

o

Analyze

Data

-

perform analysis on data retrieved from the
MInER
.

o

Download Data

-

store data retrieved from the MInER
to a local computer.

o

View Tabular Data
-

view retrieved data as a table.

o

Create User
-

create a new user of th
e system
.


o

Delete User
-

delete user from the system
.

o

Edit User
-

modify
user

information

currently in the system
.



2.2.3.

Scenarios

Refer to Appendix A for the scenarios associated with each of the user cases described in the previous section.
The scenarios dep
ict how the system will be used.

2.3.

User Characteristics

There are three classes of users

that will interact with the
MIn
ER
. A description of the users follows:

1.

The General User class represents u
sers interested in
viewing environmental science data. The typ
ical
user of this class has basic computer usage skills and is
knowledgeable
,
but not necessarily
an expert in
Environmental Science.

2.

The Registered

User class represents users interested in analyzing, viewing, or downloading
environmental science data. T
he typical user of this class has basic computer usage skills and is
knowledgeable in Environmental Science.

3.

The Administrator
class represents users
who

are either owners and/or research scientists of weather
stations. They are interested in analyzing, v
iewing, downloading, launching deployment, managing
hardware, and contributing data to the environmental science community. They can also perform
Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

9


administrative tasks on the system. The typical user of this class has average (i.e., without necessarily
bein
g an expert user) computer usage skills and is an expert environmental scientist or has
commanding knowledge to evaluate contributions from others.

2.4.

General Constraints

The general constraints on the development of the system are as follows:

1.

The system

as
defined by the team’s contract with the Guidance Team will be completed by

May 200
8
.

2.

The data repository will be stored in a PostgreSQL database management system.

3.

Basic data entry via the keyboard and mouse will conform to Microsoft Standards.


4.

Basic navi
gation of windows via the mouse and keyboard will conform to Microsoft Standards.


2.5.

Assumptions and Dependencies

The assumptions are as follows:

1.

The design and implementation will satisfy

the

requirements as defined by the
SRS.

2.

The schema
of existing
databa
se

tables

will be provided

by the Guidance Team
.

3.

The metadata from a
data logger

will be a separ
ate file and that t
he
collected
data is stored in separate files
for each type of sensor

(see future work)
.

4.

Users who are
Registered Users

or Administrators wil
l have a
n

.edu, .org or .gov email address
.

5.

Special data analysis formulas used by the researchers will be provided to the developers.

6.

A
User T
able

that is populated with user logins,
passwords
, and class
ification will be provided to the
development teams
.

7.

The Download option will save all datasets and accompanying metadata.

8.

Satellite images are maintained in a database independent of MInER.

9.

Metadata will always be entered by a user via a form.

10.

The time zone will be

stored

in GMT

unless otherwise specified
.


11.

Users are automatically given an account and the administrator is notified. The administrator will be notified
of new accounts and can act on suspicious accounts.

2.6

.

Future Enhancement

1.

Wireless data logging will be incorporated in
the
MIn
ER
.

2.

The retrieve

data feature will include the ability to search for data using a maximum value and a minimum
value
.

3.

The option
s

for analysis of data will be
expanded.

4.

Data will be combined into a single database.

5.

Create a parser that will disaggregate data sets retrieved

from the
data logger

according to type.

6.

An Edit User interfac
e will be added that allows Registered U
ser
s or A
dministrator
s

to update user
information.

7.

An Edit Site interface will

be

added that allows A
dministrator
s

to update site information
.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

10


8.

A Reset Pas
sword interface will be added.

9.

The user will have an option to download metadata.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

11


3.

Specific Requirements

3.1.

External Interface Requirements

This section contains the specification of requirements for interfaces
.

3.1.1.

User Interfaces

This section presents the genera
l GUI elements that are used in the interfaces, Next it presents general
requirements about the interfaces followed by the main interfaces.
All major interfaces can be found in
Appendix B
.


3.1.1.1.

GUI Elements


Figure 3.

Basic GUI Elements: (a) checkbox, (b) action butto
n, (c) pull
-
down box, (d) radio button, and
(e) textbox


[Rq1]

The graphical look of a check

box shall be as shown in Fig. 3
a.


[Rq2]

Check boxes shall be used to toggle between true (on) and false (off) states.

[Rq3]

The default

setting for a check box is false (off).

[Rq4]

When

the user clicks on
a

check box that is in a false (off) state, the box shall
display

a checkmark.


[Rq5]

When the user clicks on
a

check box that is in a true (on) state, the box shall clear.


[Rq6]

The graphical look of a bu
tton shall be as shown in Fig. 3
b.

[Rq7]

An act
ion button shall initiate an action (see Section 3.2.3) when the mouse cursor is placed on the
button and the user clicks the left button of the mouse.


[Rq8]

The graphical look of a list

box shall be as shown in Fig. 3
c.


[Rq9]

The user shall be able to select a valu
e in a list box by browsing through a list of predefined values and
highlighting an element of the list by a single click of the left button of the mouse.



[Rq10]

The entries in a list box shall include all predefined values associated with the list box.

[Rq11]

The gra
phical look of a radio bu
tton shall be as shown in Fig. 3
d.



[Rq12]

When a display area contains a group of related radio buttons, the radio buttons shall represent
mutually exclusive options.


[Rq13]

Radio buttons shall display a black dot in the center when the funct
ionality associated with the radio
button is set and shall be clear when it is not set.


[Rq14]

The defau
lt setting for a radio button shall be

not set unless otherwise specified.

[Rq15]

The graphical look of a text

box shall be as shown in Fig. 3
f.


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

12


[Rq16]

Text boxes shall be

used for user’s input from a keyboard.


If the space required for input to a text box
is larger than the space displayed by the text box, a vertical scroll bar shall be displayed and the input
text shall wrap around to the next line.


[Rq18]

A warning
-
message
box shall display as

shown in Fig. 4
a.


[Rq19]

A confirmation
-
message box
shall display as shown in Fig. 4
b.




Figure 4
a:

Warning
-
Message box

Figure 4
b:

Confirmation
-
Message box

3.1.1.2.

General

Interfaces

3.1.1.2.1.

Template

[Rq20]

All interfaces of the system shall ha
ve the title bar and menu options as shown in
Fig.
5
.

[Rq21]

The system shall provide the following interfaces:



Welcome



Retrieve Data



Submit Data



Manage Users



Manage Data



Manage Sites

[Rq22]

The
Save As
interface shall be displayed as a standard
“Save As”
dialog box
.




Figure 5.

Title bar and menu options



Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

13


3.1.1.2.2.

Display
s


There are several displays for the interfaces.
The
History

display

presents

selected fields from a data set’s
metadata
as

a series of rows and columns.

This

display is referred to as
History
.

The
DataSet

display lis
ts the
data from a selected data set. The
Thumbnail

display presents a thumbnail of the image from a selected data set.

[Rq23]

The

History

display shall be presented as
a data grid object as

shown in
Fig.
6
.

[Rq24]

Each

column in
History

shall correspond
each of

the fol
lowing
fields (and labels)

(see Section

3.2.2.8

for detailed description):



Dataset type and subtype (Type)



Site (Site)



Tramline (Line)



Last name of collector
(
Source)



Date collected (Date)



Query start date

(
Query

Start

Date)



Query end date (Query End Date)



Query start t
ime

(Query Start T
ime)



Query end time (Query End Time)


[Rq25]

If the space required for displaying the total number of rows is larger than the space d
isplayed by
History
, a vertical scroll bar shall

be displayed.


[Rq26]

If the space required for displaying the total number of columns is larger than the space d
isplayed by
History
, a horizontal scroll bar shall be displayed.




Figure 6.

Data Grid Object

[Rq27]

Dataset

shall display as a data grid object as shown in
Fig.
6
.

[Rq28]

Datas
et

shall display all

fields and

records from a selected data set.

[Rq29]

If the space required for displaying the total number of rows is larger than the space displayed by
Datas
et
, a vertical scroll bar shall be displayed.


[Rq30]

If the space required for displa
ying the total number of columns is larger than the space displayed by
Datas
et
, a horizontal scroll bar shall be displayed.


[Rq31]

Thumbnail

shall display
a thumbnail

of
a selected photograph and satellite image
.

[Rq32]

The following
identifying
information


shall be d
isplayed under
the

thumbnail:

1.

Source: <source of image>

2.

Location: <
North boundary>, West boundary>;

<
South boundary>, <East boundary
>

3.

Date
: <
date of data set>

4.

Time: <time of data set>

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

14


3.1.1.3.

Welcome Interface

[Rq33]

The
W
elcome
I
nterface

shall
be displayed as shown in
Fig B
-
1 in Appendix B

[Rq34]

The
Welcome Interface

shall
display the following message:

Welcome
to the
Meteorological ▪

Image


Environmental Repository

(MInER) system.

MIn
ER

is
a Web
-
based system
desi
gned to provide access to

environmental

science data and
image
s

from a variety of sites in the Arctic. Through MInER,

users can
submit,
download
,
view, integrate, and analyze

environmental data

from
a variety of

sources
.

3.1.1.4.

Retrieve Data
Interface

[Rq35]

The
Retrieve Data
interface shall be displayed as shown in Fig.
B
-
2 in
Appendix B
.

[Rq36]

The
Retrieve Data
interface shall display the following title at the top of the page: Retrieve Data

[Rq37]

The
Retrieve Data Selection

panel display, as shown in
Fig. B
-
3 in Appendix
B
,

shall appear on the
left
-
hand side of all the
Retrieve Data
inter
faces

described in
this section.

[Rq38]

The
Retrieve Data Interface

shall display a progress bar in the general message box.

[Rq39]

The
GUI elements associated with each of the interface fields shall be as follows:

1.

Site:
List
box (
see Section
3.2.2.7
)

2.

Tram Line: check box

3.

Start Date:
t
ext box

4.

End Date: t
ext box

5.

Start
Time: text box

6.

End Time: text box

7.

Hyperspectral: c
heck box

8.

Meteorological
: c
heck box

9.

Campbell

Logger: c
heck box

10.

Temperature
: c
heck box

11.

Soil Moisture
: c
heck box

12.

H
umidity
: c
heck box

13.

Wind Speed
: c
heck box

14.

Wind Direction
: c
heck box

15.

Radiation
: c
heck box

16.

PAR
: c
heck box

17.

Photograp
h
: c
heck box

18.

Satellite

Image
: c
heck box

19.

West Boundary Coordinate (decimal degrees): text box

20.

East Boundary Coordinate (decimal degrees): text bo
x

21.

North Boundary Coordinate (decimal degrees): text box

22.

South Boundary Coordinate (decimal degrees): text box


[Rq40]

The
Retrieve Data Interface
shall
have two buttons labeled “Retrieve” and “Reset”

that are centered
and appear below the data entry area
.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

15


3.1.1.4.1.

Analyze

Interface

[Rq41]


The
Analyze

i
nterface
shall display the title “Analyze” at the top of the page.

[Rq42]

The
Analyze

interface shall display the following instructions below the title of the interface:

Select the hyperspectral dataset to be analyzed.

[Rq43]

The
Analyze

interf
ace shall display
History

(see Section
3.1.1.2.2
)
.

[Rq44]

The
Analyze

interface shall have an action button labeled “Analyze” that is centered and appears below
the history displays.

[Rq45]

The
Analyze

interface shall have a display area und
er the “Analyze” action button.

3.1.1.4.2.

Download Interface

[Rq46]

The
Download
interface shall display the title
“Download” at the top of the page.

[Rq47]

The
Download
interface shall display the following instructions
below the title of

the interface:

Select the dataset(s) an
d image(s) to be downloaded or click on the check box below to select
all.

[Rq48]

The
Download
interface shall display a checkbox labeled “All”

that
is left
-
justified

under the
instructions

and above the history displays
.

[Rq49]

The
Download
interface shall
display

Hist
ory

(see Section
3.1.1.2.2
)
.

[Rq50]

The
Download
interface shall
have an action button labeled “Save

As


that is centered and appears
below the history displays
.

3.1.1.4.3.

Plot

Interface

[Rq51]

The
Plot

i
nterface
shall
display the title
“Plot” at the
top of the page.

[Rq52]

The
Plot
interface shall display the following instructions below the title of the interface:

Select one dataset below. Weather station data will be plotted over a range of
time. Hyperspectral data will be plotted as reflectance over wavel
ength for the
length of the tramline.

[Rq53]

The
Plot
interface shall

have a
History
display

(see Section
3.1.1.2.2
)
.

[Rq54]

The
Plot

i
nterface
shall have an action button labeled “Submit”

that is centered and appears below the
history displ
ay
.

[Rq55]

The
Plot

i
nterface
shall
display

a plot

that conforms to the selected data set

(see Section
3.2.4.4
) and
that is centered and appears
below the
Submit

action button.

[Rq56]

The
Plot

i
nterface
shall have an action button labeled “S
ave As”
that is centered and appears
below the
displayed plot.

3.1.1.4.4.

View

[Rq57]

The
View

i
nterface
shall display the title

“View” at the top of the page.

[Rq58]

The
View
interface shall display the following instructions below the title of the interface:

Select the dataset
or image to be viewed.


[Rq59]

The
View
interface shall
display

History

(see Section
3.1.1.2.2
)
.

[Rq60]

The
View
interface shall have an action button labeled “View”

that is centered and appears below the
history displays
.

[Rq61]

The
View

interface

shall have a
display area
u
nder the “View” action button.

3.1.1.5.

Submit Data

Interface

[Rq62]

The
Submit Data

Interface shall display the title

“Submit Data”
at the top of the page
.


[Rq63]

The
Submit Data

Interface shall display a checkbox that is labeled

Restore
F
orm
”.

[Rq64]

The

Submit Data

Interface shall pr
esent a metadata form that con
tains the following information as
specified in Section
3.2.2.1
.

[Rq65]

The
Submit Data

Interface shall display
an action button

bel
ow the form

and centered

that
is labeled

Save

Form”.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

16


[Rq66]

The
Submit Data

Interface shall display a checkbox below the action button and left justified that is
labeled “Transfer File”.

3.1.1.6.

Manage Users Interface

[Rq67]

The
Manage Users

Interface

shall

display

a dat
a grid object as shown in Fig.
6
.

[Rq68]

Each column o
f the data grid object shall correspond each of the following fields (and labels)

(see
Section
3.2.2.9

for

detailed description):



User Identifier (ID)



Name (Name)



Affiliation

(
Affiliation
)



Title (Title)



E
-
mail A
ddress (e
-
mail)



User classification (Account type)

[Rq69]

The
Manage Users

Interface

shall display three buttons
that
are
centered and labeled as follows
:


Approve

User”
, “Edit User”

and “Delete User”
.

3.1.1.7.

Manage Data Interface

[Rq70]

The
Manage Data

i
nterface

shall

display

the title “Manage Data”.

[Rq71]

The
Manage Data
interface shall display

a data grid object below the title that
display
s

a list of
submitted data
sets

in the system.

[Rq72]

The
Manage Data
interface shall display
the

Retrieve Data Selection
panel of the left
-
hand side o
f the
interface.

[Rq73]

Each column in the data grid shall correspond each of the following fields (and labels)

(
see Section
3.2.2.1

for detailed description):



Dataset type and subtype (Type)



Site (Site)



Tramline (L
ine)



Last name of collector
(
Source)



Date collected (Date)

[Rq74]

The
Manage Data

Interface

shall disp
lay three action buttons that are centered and labeled as

“Add
Quality Flags”, “Approve”,
and “
Reject”.

3.1.1.8.

Manage Sites Interface

[Rq75]

The
Manage Sites

i
nterface

shall
display
the title “Manage Sites” at the top of the interface.

[Rq76]

The
Manage Sites

i
nterface

shall display a

data grid object as shown in Fig.

6.

[Rq77]

The
Manage Sites
data grid object shall display the following fields (and labels) for a site (see Section
3.2.2.7
):



Site Name (Name)



North boundary coordinate and west boundary coordinate (Upper left coordinate)



South boundary coordinate and east boundary coordinate (
Lower right coordinate)


[Rq78]

The
Manage Sites

Interface

shall display three
buttons

that are centered and

labeled as
“Create New
Site”, “Edit Site” and “Delete Site”.

3.1.1.9.

Login

Interface

[Rq79]

The
Login Interface

shall display
the following text at the top of the page:

[Rq80]

Welcome
to the Meteorological ▪ Image ▪ Environmental Repository (MInER
) system.

[Rq81]

The
Login Interface

shall display a text box labeled as
Username
.

[Rq82]

The
Login Interface

shall display a text box labeled as
Password
.

[Rq83]

The
Login Interface

shall display two

action

button
s

labeled as

Login

and “Forgot Password?”

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

17


3.1.1.10.

Registration Interf
ace

[Rq84]

The
Registration

i
nterface
shall display the title “Registration” at the top of the page.

[Rq85]

The
Registration

i
nterface
shall display the following at the top of the page: “All fields marked with an
asterisk must not be blank.”

[Rq86]

The

Registration

i
nterface

shal
l display twelve

text boxes
(unless otherwise noted)
labeled as
follow
s:



First N
ame*



Middle I
nitial



Last N
ame*



Affiliation
*



Title



A
ddress



C
ity



S
tate

(pull
-
down box)



C
ountry

(pull
-
down box)



Zip C
ode



Phone N
umber



E
-
mail*



P
assword*



C
onfirm
P
assword*

[Rq87]

The
Registration

Interface

shall display action
button
s that are centered and

labeled
“R
egister
” and
“Reset”.

3.1.1.11.

About Us Interface

[Rq88]

The system shall display “About Us” at the top of the
About Us
interface.

[Rq89]

The system shall display the following information after
the title:


MInER manages
data
sets collected from a robotic tram system
at

different sites as well as
photographs, satellite images, and other measurements. The robotic tram system consists of
three 300 meter tramlines and a robotic cart. It collects a ran
ge of data using sensors that are
activated along the path of the tramline. Measurements include photographs (taken every other
week) and spectral reflectance at 256 spectral bands (taken every time the tram runs). The
spectrometer writes a file of data f
or every measurement (every meter along the tramline plus
calibration measurements). Hand measurements of soil moisture, active layer depth (depth to
permafrost, every 2 weeks) and surface temperature are also taken when the tram is operated
and a static c
entrally located weather station is also activated during measurement periods. The
types of data that can be collected from the weather station include: wind speed, wind direction,
temperature, humidity, radiation, and at times several other measurements.
Full metadata
records are available for each time the tram was run and also include attributes s
uch as local
weather conditions and
potential

faults with the tram system
.



Contact Information:

John Gamon

Professor

Virtual Center for Spatial Analysis and
Remote Sensing (VCSARS)

Dept of Biological Sciences

School of Natural and Social Sciences

California State University, Los Angeles

5151 State University Drive

Los Angeles, CA 90032

Phone:(213)
-
343
-
2066

FAX: (213)
-
343
-
6451

Email:
jgamon@calstaatela.edu


jgamon@gmail.com

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

18


Website:
http://vcsars.calstatela.edu/personnel/faculty/John_Gam
on.htm


Craig Tweedie

Assistant Professor

Dept of Environmental Science and Engineering and

Dept of Biological Sciences

500 West University Ave

University of Texas at El Paso

El Paso, TX 79968

Tel.: (915) 747
-
5844

Fax: (915) 747


5808

Email:

c
weedie@utep.edu

Website:
http://faculty.utep.edu/ctweedie


Santonu Goswami

Graduate Research Assistant

Systems Ecology Laboratory

500 West University Ave

University of Texas a
t El Paso

El Paso, TX 79968

Tel.: (915) 747
-
7314

Email:
sgoswami2@utep.edu


Kuldeep Matharasi

Graduate Research Assistant

Systems Ecology Laboratory

500 West University Ave

University of Texas at El Paso

El Paso,

TX 79968

Tel.: (915) 747
-
5736

Email:
kmatharasi@utep.edu

3.1.2.

Hardware Interfaces

There are no requirements for software interfaces.

3.1.3.

Software Interfaces

[Rq90]

The system shall interact with
tables stored in a PostgreSQL da
tabase management system
.

3.1.4.

Communications Interfaces

There are
no requirements for communication interfaces.

3.2.

Behavioral Requirements

This section contains behavioral requirements related to Same Class of User, Related Real
-
World Objects,
Related Features
, Stimulus, and Functional.

3.2.1.

Same Class of User

This section presents the requirements associated with a particular class of user.

[Rq91]

The system shall support the following classes of users
:




General
User

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

19




Registered User



Administrator


[Rq92]

The Administrator class

of user shall have access to
the

functionality

associated with all interfaces

of
the system.

[Rq93]

The Registered User shall have access to all functionality of the system except the
functionality
associated with the
following

interfaces
:



Manage Users



Manage Da
ta



Manage Sites

[Rq94]

The General User shall have access only to the following interfaces:



Retrieve Data



Plot Data



Analyze Data



Register

3.2.2.

Related Real
-
world Objects

Real
-
world objects are entities with either physical or conceptual counterparts in the real world.

The class
diagram motivates the real
-
world objects described in this section.

3.2.2.1.

Metadata

[Rq95]

The metadata fields associated with spectral data shall be stored as shown in Table 1.

[Rq96]

The values assigned to CloudCover and CloudClass for spectral metadata shall be
consistent.


Table 1:
Spectral

Metadata

F
IELD

TYPE

C
OMMENTS

StartDate

Date

yyyymmdd is preferred input

EndDate

Date

Same as above

StartTime

Time

GMT

EndTime

Time

GMT

SiteID

Int(3)

Site Identifier

Tramline

Varchar(1)

N
-
North

S
-
South

C
-
Central

UserID

Int(10)

Identification of recorder

Model

Int(10)

Model number of Spectrometer

Bands

Int(3)

Number of bands

IntTime

Int(3)

Integration time

Wavelength

Int
(4)

Start of wavelength

(310nm)

FilePrefix

Char(3)

n,s,m; ref

People

Varhar(50)

List of people

present at experiment

CloudCover

Int(3)

Percent of cloud cover

Weather

Varchar(20)

Weather conditions

CloudClass

Int(1)

Cloud Classification:

0
-

No Clouds 0%

1
-

Clear 0
-
10%

2
-

Isolated 25
-
50%

3
-

Scattered Clouds 25
-
50%

4
-

Broken 50
-
90%

5
-

Overcast >90
%

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

20


SkyPhoto

Varchar(25)

Path to photograph of sky conditions

DarkScanCorrection

Bool

Dark scan correction on?

0
-

No

1
-

Yes

DarkScanCollected?

Bool

Dark scan collected?

0
-

No

1
-

Yes

TimeScan

Time

Time of dark scan (GMT)

RaworCalibrated

Bool

0
-

Raw data

1
-

Calibrated data

FrequencyMeasurement

Int(6)

Frequency of measurement: given as
mmmmss

QCID

Char(6)

Quality test identifier (version
number)

QCFlag

Int(2)

Quality Flag (1
-
9)

FilePathname

Varchar(25)

Path to dataset


[Rq97]

The metadata asso
ciated with a we
ather station shall be as

given in Table 2.

[Rq98]

The value assigned to Measurement shall be consistent with the sensor type.

TBD


Table 2:
Weather Station Metadata table

F
IELD

T
YPE

C
OMMENTS

Model

Int(10)

Datalogger model

SerialNo

Int(10)

Datalogger serial num
ber

Class

Bool

Classification of datalogger

0
-

Meteorological

1
-

Campbell

UserID

Int(10)

ID of recorder

SiteID

Int(3)

Site identifier

DeployName

Varchar(10)

Deployment name

SeriesInfo

Varchar(50)

Information about series

Sensor

Int(2)

Sensor types

as

coded in Section
3.2.2.3
.

Points

Int(10)

Points used

Measurement

Char(5)

Units of measurement

StartDate

Date

yyyymmdd is preferred format

EndDate

Date

Same as above

StartTime

Time


GMT

EndTime

Time


GMT

Duration

Int(6)

Interval duration

Max

Float(5.3)

Maximum value

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

21


Min

Float(5.2)

Minimum value

Avg

Float(5.2)

Average value

QualityFlag

Int(2)

Quality of data

Pathname

Varchar(25)

Path to dataset


[Rq99]

The metadata associated with photographs shall

be as given in Table 3.


Table 3:

Metadata for photographs


F
IELD

TYPE

C
OMMENTS

Date taken

Date

yyyymmdd is preferred input

Time taken

Time

GMT

SiteID

Int(3)

Site Identifier

Tramline

Varchar(1)

N
-
North

S
-
South

C
-
Central

North Boundary Coordinate

Float(6.3)

[
-
90 ,
90
]

South B
oundary Coordinate

Float(6.3)

[
-
90,90]

East Boundary Coordinate

Float(6.3)

[
-
180,180]

West Boundary Coordinate

Float(6.3)

[
-
180,180]

UserID

Int(10)

Identification of recorder

FilePathname

Varchar(25)

Path to photograph


3.2.2.2.

Spectral Data


[Rq100]

Spectral data sh
all be
obtained from
SPU files

that contain a set of wavelength bands and

the following
readings:



I
rradia
nce measurements taken per band



Radiance measurements taken per band



Reflectance measurements taken per band

[Rq101]

The system shall parse the SPU files to re
trieve the relevant data.

[Rq102]

The format of the SPU files shal
l be as provided in Figure C
-
1

in
Appendix
C
.

[Rq103]

Indices measurements shall be stored
in a file with fields
for NDVI, PRI, and WBI

for each meter of
the tram
.

3.2.2.3.

Sensor Data

[Rq104]

Sensor
data
shall be stored
as

shown in Table 4
.


Table
4
:

Sensor data table

F
IELD

T
YPE

C
OMMENTS

Date

Date

Date of reading

Reading

Float

Sensor reading


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

22


[Rq105]

The system shall code the type of sensors as follows:

1.

Temperature

2.

Soil Moisture

3.

Humidity

4.

Wind Speed

5.

Wind Direction

6.

Radiation

7.

PAR

3.2.2.4.

I
mages

[Rq106]

The system shall maintain the links to photographs in the photograph metadata table.

[Rq107]

The system shall be able to query existing satellite image repositories based on latitude, longitude, and
date to retrieve satellite images.

3.2.2.5.

Quality Flags

[Rq108]

The
descriptions associated with a quality flag shall be as follows:

0 = No quality control has been assigned to this element

1 = The element appears to be correct

2 = The element appears to be probably good

3 = The element appears probably bad

4 = The el
ement appears erroneous

5 = The element has been changed

6 to 8 = Reserved for future use

9 = The element is missing

[Rq109]

The syst
em shall store a quality flag in the metadata table for spectral and sensor data.

[Rq110]

The default code for a quality flag in the metad
ata of a dataset is 0.

[Rq111]

The user shall be able to add a quality flag to a dataset through a message box, referred to as
Quality
Message Box

that presents a pull
-
down box of codes and quality flag descriptions, an action button
labeled
Add

and an action butt
on labeled
Cancel.

3.2.2.6.

Measurements

[Rq112]

The default measurement for location is degrees, minutes, and seconds.

[Rq113]

The default measurement for soil moisture is percentage
VWC
.

[Rq114]

Date shall be represented
as yyyymmdd
.

[Rq115]

Time shall be represented as mmmmss.

[Rq116]

The system shall

be able to translate from English to Metric measurements.

[Rq117]

Latitude and longitude shall be stored as decimal degrees.

3.2.2.7.

Site

[Rq118]

The default codes associated with each site shall be:

1.

Barrow

2.

Beringer

3.

Atqusuk

4.

Ivotuk

[Rq119]

The system shall
store

the next available site c
ode

starting at 5
.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

23


[Rq120]

The system shall store the following information regarding a site:

1.

Name

2.

Description

3.

Latitude and longitude of the upper left hand corner of the footprint of the site

4.

Latitude and longitude of the lower right hand corner of the footprint
of the site

5.

User id of creator

6.

Date created

7.

User id of person who last modified

8.

Date modified

9.

Description of modification

3.2.2.8.

History

[Rq121]

The system shall store the
history of a search result, where the history is the metadata of each

search

result during a sessio
n as shown in Table
5
.


[Rq122]

The system sh
all store an entry for each search result from a query and for all queries in a session.


Table 5
:

The metadata stored as history.


Field

Value

Comments

Dataset type

I
nt
(1)

1.

Hyperspectral

2.

Meteorological

3.

Campbell logger

4.

Photograph

5.

Satellite Image


Dataset subtype

Int(2
)

Pertinent only when Dataset type is 2 or 3
.
Refer to Sensor field in the weather station
metadata table given in Section
3.2.2.1
.


Site

Int
(2
)

See Section
3.2.2.7

for codes

Tramline

Char(1)

Complete for Dataset type 1
; see same field
in the spectral metadata table given in
Section
3.2.2.1
.

Collector ID

Int
(
10)

ID of collector

Date collected

Date

Date of dataset

Qu
eryStartDate

Date

Query date range

QueryEndDate

Date


QueryStartTime

Time

Query time range

QueryEndTime

Time



3.2.2.9.

User


[Rq123]

The system shall maintain a table of users that contains the fields presented in Table
6
.


Table 6
:

User Table

Field

Type

Common

User

ID

Int(10)

Assigned by system

Classification

Int(1)


N. o敧楳瑥t敤

†††† ††
2. Admin楳瑲慴ar

䅳Aign敤 by sys瑥m㬠;敦au汴⁩s
o敧is瑥t敤

Approv敤

Boo汥慮

M
-

No

1
-

Yes

First Name

Char(25)

Required

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

24


Middle Initial

Char(1)


Last Name

Char(25)

Required

Af
filiation

Char(25)

Required

Title

Char(25)


Address

Char(25)


City

Char(25)


State

Char(2)


Country

Char(10)


Zip code

Int(5)


Phone Number

Int(10)


e
-
mail

Char(15)

Required

Password

Char(10)

Required

Locked

Bool

0


Account not locked (default)

1
-

Account locked


[Rq124]

The system shall assign a unique identifier

(User ID)

for each person that registers.

[Rq125]

The system shall use the user’s e
-
mail address as the person’s login.

[Rq126]

The syste
m shall check that all fields marked with an asterisk (*) have val
ues entered.


3.2.3.

Related Features

There are no additional requirements for this section.

3.2.4.

Stimulus Response

3.2.4.1.

General

[Rq127]

The options on the Retrieve Data Selection panel shall be disabled for the general user.

[Rq128]

The Manage User on the Welcome Interface shall be disa
bled for the general user.

[Rq129]

The Manage Data button on the Welcome Interface shall be disabled for the general user.

[Rq130]

The Manage Sites button on the Welcome Interface shall be disabled for the general user.

[Rq131]

The system shall classify a user as a General User i
f the user has not logged onto the system with a
valid login and password.

[Rq132]

The system shall retrieve the classification of a user from the User table for a user who has
successfully logged onto the system.

[Rq133]

When the user selects the Retrieve Data
option
, th
e system shall display the Retrieve Data
i
nterface.

[Rq134]

When the user selects the Submit Data option, the system shall display the Submit Data interface.

[Rq135]

When the user selects the Manage Data option, the system shall display the Manage Data interface.

[Rq136]

When the

user selects the Manage Users option, the system shall display the Manage Users interface.

[Rq137]

When the user selects the Manage Sites option, the system shall display the Manage Sites interface.

[Rq138]

When the user clicks on

the

Login

option, the system shall displ
ay the Login interface.

[Rq139]

When the user clicks on the Logout option, the system shall display the Logout interface.

[Rq140]

When the user clicks on the Register option, the system shall display the Register interface.

[Rq141]

When the user clicks on the About Us option, the

system shall display the About Us interface.

[Rq142]

When the user exits a session, the system shall clear the
table

that holds all the temporary datasets.

[Rq143]

When the user clicks on Reset, the system shall clear all the data

entered on a form
.

[Rq144]

If the user clicks o
n more than one check
-
box in a Grid Object and the system expects only one
selection, the system shall display the following error message: More than one data set has been
selected.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

25


3.2.4.2.

Login and Logoff

[Rq145]

When the user clicks on Login,
the system shall
check

tha
t

the user name entered into the login text
box and the password entered into the password text box
correspond to an entry
in the User table.

[Rq146]

If the system is not able to verify the

entered

password, the sy
s
tem sh
all display

a

warning message

box that stat
es: Login information is incorrect. Please resubmit.

[Rq147]

When a user enters an incorrect password, t
he system shall
increment a counter that tracks the number
of times that the

person

has attempted

to login.

[Rq148]

If the number of attempted logins exceed three times
, the system shall

lock the account.


[Rq149]

When the account of a person who is attempting to login is locked, the system shall display the
following warning message box:
Your account has been locked. Contact the Administrator to have
your account reset (
MInERAdmin@utep.edu
).

[Rq150]

If the user clicks on Forget Password?, the system shall verify that the e
-
mail address is stored in the
User table, and it shall send a message to the e
-
mail address

with the password.

3.2.4.3.

Register Use
r

[Rq151]

When the user clicks
S
ubmit

in the
Register User

interface
, the system shall check that all required
fields have entries
.

[Rq152]


When the user clicks
Submit

in the
Register User

interface
, the system shall check
that the first
password matches the second pass
word.

[Rq153]

If a required field
in the form (of the
Register User

interface)

does not have an entry, the system shall
display the following message on the screen: “All fields marked with an asterisk must not be blank.”

and the system shall highlight the missing
fields in red.

[Rq154]

If the first password does not match the second password

in the form of the
Register User

interface
, the
system shall display the following message on the screen: “Reenter password,” and the password fields
shall clear.

[Rq155]

If the user clicks on

Submit

in the
Register User

interface
, the system shall check that the user’s e
-
mail
address adheres to the following template: <series of characters>@<series or characters>.<org | com |
edu>.

[Rq156]

If the user’s e
-
mail address

in the form (of the
Register User

interface)

is not in a valid format, then the
system shall display the following
warning
message: Please re
-
enter your e
-
mail address.

Note that you
must use an account ending in .org, .com, or .edu.

[Rq157]

If

the user clicks on
S
ubmit

in the
Register User

inter
face
,
if
all required fields have entries,
and

if

the
user’s e
-
mail address is in a valid format, then the system shall
create a unique user ID, set the user
classification to 1, and store the ID, classification and

all information from the form

in the
Use
r
table.

[Rq158]

If the system successfully stores the user registration information in the
User
table
, then
the system
shall send an e
-
mail message
with the following text
to the registrant
and

a blind
copy to all
Administrators
:



Thank you for registering

with the MInER System



Your login is: <local name>



Your password is: <password>.

3.2.4.4.

Retrieve Data

[Rq159]

If the user selects a start date that occurs after the end date

in the
Retrieve Data

interface
, the system
shall display an error message

in the mes
sage display area
: Incorrect range of date.

[Rq160]

If the user selects a start date or end date that is beyond the current date

in the
Retrieve Data

interface
,
the system shall display an error message

in the message display area
: Incorrect date.

[Rq161]

If the user sele
cts a latitude

that is out or range (see Section
3.2.2.1
)

in the
Retrieve Data

interface
, the
system shall display an error message

in the message display area
:

Latitude out of range
.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

26


[Rq162]

If the user selects a longitude that is out

or range (see Section
3.2.2.1
)

in the
Retrieve Data

interface
,
the system shall display an error message

in the message display area
: Longitude out of range.

[Rq163]

If the user
clicks on
more than one type of data in the
Retrieve Dat
a

interface

and clicks on
Retrieve
,
the system
shall

search for the data
, retrieve the metadata, and
store

the metadata for history
.

[Rq164]

When the system is retrieving data, the system shall display a progress bar that depicts the status of the
retrieval in th
e message display area.

[Rq165]

When the user selects
Retrieve

in the
Retrieve Data
interface
,

the system shall store the
history data

in
History

(as described in
3.1.1.2.2
)
, including the date range and the time range

of the query
.

3.2.4.4.1.

An
alyze

[Rq166]

When the user selects
Analyze Data,

the system shall display
History

(as described in
3.1.1.2.2
)

only
for retrieved hyperspectral data

stored as history

and the query date and time ranges
.

[Rq167]

When the user clicks on the met
adata for a single data
set

in the Grid Object in the
Analyze Data

interface and clicks on
Submit
, the system shall:

1.

R
etrieve the reflectance file associ
ated with the selected metadata.

2.

Retrieve the data that corresponds to the query date and time ranges.

3.

G
enerate a plot, where the x
-
axis denotes the
length in meters of the point at which the measurement
is taken (0
-
300m), the y
-
axis denotes a unit of measurement (
-
0.2
-
1.2), and the measurements for
NDVI, WBI, and PRI are plotted in three different colors.

3.2.4.4.2.

D
ownload

[Rq168]

When the user selects
Download Data,

the system shall display
History

(see Section
3.1.1.2.2
)

for the
retrieved datasets and images stored as history

and the query date and time ranges
.

[Rq169]

When the user clicks on
the metad
ata for
a
single
dataset

or image

in the
Download Data

interface and
then clicks on
Save As
, the system shall
d
isplay a
Save As

dialog box
.

[Rq170]

When the user clicks on
Save As

in the
Save As

dialog box
, the system shall zip the selected metadata
and its associ
ated dataset or image and save it in the selected drive and directory.

[Rq171]

If the user clicks on
Save As

in the
Download Data

interface and the user has not selected a dataset

or
image

in
History
, the system shall display

the following
warning

message: Please
select a dataset or
image to be downloaded.

[Rq172]

If the user clicks on more than one dataset and/or image in the Grid Object in the
Download Data

interface, the sy
stem shall store all selected metadata, datasets, and images

as a single zip file.

3.2.4.4.3.

Plot

[Rq173]

When the u
ser selects a weather station dataset

in the
Plot

interface

and clicks on
Submit
,
the system
shall generate a plot of the dataset over the range
of dates associated with the dataset
, where the x
-
axis
denotes dates
.

[Rq174]

When the user selects hyperspectral data
and clicks on
Submit
,
the system

shall read

the
selected
irradiance (rad
iance) dataset, and it shall

determine the number of plots to be generated, where each
plot is a maximum of 100 measurements taken over time.

[Rq175]

After the system determines the number of
plots to be generated
, the system shall generate

a plot for
each

100 point
s

for irradiance

(radiance)

fr
om the irradiance

(radiance) dataset
, where

t
he
x
-
axis of the

irradiance

(radiance)

plot denotes wavelength 310
-
1130 nm, the y
-
axis denotes irradiance f
or ranges 0
-
35000 units

(radiance for ranges 0
-
6000)

and, for each wavelength, there are
a maximum
100 points
plotted (for each irradiance

(radiance)

measurement at a

given point in time).

3.2.4.4.4.

View Data

[Rq176]

When the user selects
View Data,

the system shall display

History

each populated with history

and the
query date and time ranges
.

[Rq177]

When the user selects
View Data,

the user clicks on a dataset, and the user clicks on
View
, the system
shall display
the dataset in a grid object as described in Section
3.1.1.2.2
.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

27


[Rq178]

When the user selects
View Data,

the user clicks on an image, and the user clicks on
View
, the system
shall display a
full

image and the metadata for the image shall be displayed below the image as
described in Section
3.2.2.4
.

3.2.4.5.

Submit Data

[Rq179]

After

the user completes the metadata form

and clicks on
Submit

in the
Submit Data
interface
, the
system shall
check that all
required

fields are completed.

[Rq180]

If the user clicks on
Save Form

in the
Submit Data
interfa
ce, the system shall
store the information
from the m
etadata form and associate it with the user
.

[Rq181]

If the user clicks on
Restore Form

in the
Submit Data
interface, the system shall retrieved the saved
metadata information associated with the user, and it sh
all display the information on the form.

[Rq182]

When the user selects the file from the local machine and clicks on
Transfe
r
in the
Submit Data
interface
, the system shall move the file from the local machine to a temporary directory on the server.

[Rq183]

When the user

clicks on
Transfer
in the
Submit Data
interface, the system shall send an e
-
mail
message to all administrators stating:
A user has submitted data to MInER.

3.2.4.6.

Manage Data

[Rq184]

When the user selects
Manage Data,

the system shall display a Grid Object (as given in
Fig. 3)

using
the fields
specified in the History table

in Table 5

with exception of the query time and date ranges
.

[Rq185]

`
When the user selects
Manage Data
, the Grid Object shall be populated
with the

corresponding

metadata for the uploaded data
a
waiting appro
val
, with the caveat that codes are replaced with the
description

of the code
.

[Rq186]

When the user clicks on the check bo
x of a photograph
and then clicks on
Add Quality Flag
, the
system shall

display the following
warning

message: A photograph cannot be tagged

with a quality
flag
.

[Rq187]

If the
user

clicks on
Add
on the
Quality Message Box
after selecting a quality code

from the pull
-
down
text
,

the system shall set the value of the
quality flag in the metadata of

the associated data set

to the
selected code.

[Rq188]

If the

us
er clicks on
Approve
, the metadata of the selected data
set

shall be moved from a temporary
area to the repository
, and the selected dataset
shall move from a temporary directory on the server to a
permanent directory on the server
.

[Rq189]

If the user clicks on
Re
ject,
the metadata of the selected dataset shall be deleted from the temporary
area and the file of the dataset shall be deleted.

3.2.4.7.

Manage Users

[Rq190]

When the user selects
Manage Users
, the system shall display
a Grid Object that displays
the list of all
users wh
o have registered and not been approved
, i.e., reviewed
.

[Rq191]

When the user clicks on the check box of the users to be approved and then clicks on
Approve Users
,
the system shall mark the selected users as approved.

[Rq192]

When the user clicks on
View Users

on the
Man
age Users

interface, the system shall display the list of
all users as Data Grid object.

[Rq193]

When the user selects
Edit
User

on the
Manage Users

interface

and the user has not selected a
user

on
the display via the check box, the system shall display a warning

message: Please select a
user

to be
edited.

[Rq194]

When the user selects
Edit
User

on the
Manage Users

interface
and the user has selected a site on the
display via the check box, the system shall display an
Edit
User

window that allows the user to edit
all

user

attributes, as provided in Section
3.2.2.9

except for User ID
and a description of the modification.

[Rq195]

When the user selects
Save

on the
Edit
User

window, the system shall save the
user

information, the
description of the modifi
cation, the user ID of the modifier, and the date of the modification.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

28


[Rq196]

When the user selects
Delete

on the
Manage Users

interface

and the user has not selected a
user

on the
display via the check box, the system shall display a warning message: Please sele
ct a
user

to be
deleted.

[Rq197]


When the user selects
Delete

on the
Manage Users

interface
and the user has selected a site on the
display via the check box, the system shall delete the
user
.

3.2.4.8.

Manage Sites

[Rq198]

When the user selects
Create New Site

on the
Manage Sites

interface
, the system shall do the
following:

1.

Retrieve the next unique site number.

2.

Prompt the user to enter the name of the new site.

3.

Prompt the user to enter a description.

4.

Prompt the user to enter the latitude and longitude of the upper left hand corne
r of the footprint of the site.

5.

Prompt the user to enter the latitude and longitude of the lower right hand corner of the footprint of the site.

[Rq199]

When the user selects
Save
on the
Create New Site

window, the system shall do the following:

1.

Increment the next

unique site number.

2.

Save the site name,

the description,

the upper
-
left and lower
-
right hand corner of the footprint of
the site, the user ID,
and

the current date.

[Rq200]

When the user selects
Edit Site

on the
Manage Sites
interface
and the user has not selecte
d a site on the
display via the check box, the system shall display a warning message: Please select a site to be edited.

[Rq201]

When the user selects
Edit Site

on the
Manage Sites
interface
and the user has selected a site on the
display via the check box, the s
ystem shall display an
Edit

Site
window that allows the user to edit the
site name,

the description,
the coordinates of the footprint
, and a description of the modification
.

[Rq202]

When the user selects
Save

on the
Manage Sites
interface
, the system shall save th
e site information
,
the description of the modification, the user ID of the modifier, and the date of the modification.

[Rq203]

When the user selects
Delete

on the
Manage Sites
interface

and the user has not selected a site on the
display via the check box, the sy
stem shall display a warning message: Please select a site to be
deleted.

[Rq204]


When the user selects
Delete

on the
Manage Sites
interface

and the user has selected a site on the
display via the check box, the system shall
delete the site
.

3.2.5.

Functional

There are
no functional requirements specified at this time.

3.3.

Non
-
behavioral Requirements

This section includes requirements relating to performance, qualitative requirements, maintainability,
portability, security, and design implementation and
constraints
.

3.3.1.

Perform
ance Requirements

There are no performance requirements specified at this time.

3.3.2.

Qualitative Requirements

There are no qualitative requirements specified at this time.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

29


3.3.3.

Maintainability

There are no maintainability requirements specified at this time.

3.3.4.

Portab
ility

There are no portability requirements specified at this time.

3.3.5.

Security

There are no security requirements specified at this time.

3.3.6.

Design and Implementation Constraints

There are no design and implementation requirements specified at this time.

3.4.

Other
Requirements

This section includes requirements relating to database structures and operations, any special operations
required by the user, and any installation or software portability issues.

There are no other requirements specified at this time.


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

30


Appen
dix A.
Scenarios


Scenario for Register Use Case

Description:
The user applies for user account

Actors:

General User

Precondition:
The user is not logged on to the system and is not a registered user in
MIn
ER

Trigger Condition:

The user
clicks on

Register
.

Steps:

1.

The system
displays the registration form.

2.

The user
completes the

registration
form.

3.

The user
clicks on
Register.

4.

The system
checks

that all
required

information is present.

5.

The system saves the regis
tration information.

6.

The system sends a
n e
-
mail

message

to the user and a blind copy to all Administrators
.

7.

End use case.


Alt1: Step4: The system determines that required information is missing.


Step4
.1:
The system displays a warning message and displays the missing fields in red.

Th
e use case contin
ues at step 1.



Scenario for Retrieve Data

Description:

T
he user retrieves data from the repository


Actors:

General U
ser,

Data Repository

Precondition:

The user is a General User and is not logged into the system

Trigger Condition:

The user initiates t
he functionality to
retrieve

data.

Steps:

1.

The user specifies search criteria

2.

The system retrieves
data matching user specified criteria

3.

The system informs user that data retrieval was successful.

4.


The system displays the data for the user in a graphical f
ormat

5.

End use case



Scenario for Retrieve Data

Description:

T
he user retrieves data from the repository


Actors:

Registered User
,
Administrator,
Data Repository

Precondition:

The user is registered in MInER as a Registered User or Administrator.

Trigger

Condition:

The user initiates the functionality to
retrieve

data.

Steps:

1.

Include <<Login>>

2.

The user specifies search criteria including: site, date range, and type of data.

3.

The user selects the option to retrieve

4.

The system retrieves data matching user s
pecified criteria.

5.

The system informs user that data retrieval was successful.

6.

The system adds a new entry into the retrieved data log describing the retrieved data type and time of
data retrieval.

7.

Extend <<
View

Tabular Data
>>

8.

Extend <<
Analyze Data
>>

9.

Exten
d <<
Visualize Data
>>

10.

Extend <<
Download Data
>>

11.

End use case

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

31




Scenario for Submit Data Use Case

Description:
The user

submits data for upload to the system.


Actors:

Administrator, Registered

User

Precondition:

The us
er is registered in the MINER as an Ad
ministra
tor

or
Registered

User.


Trigger Condition:

The user initiates the
functionality to submit data.

Steps:

1.

Include <<
Login
>>

2.

The system prompts the user for information on the data being submitted which includes the type of
data submitted, the sky con
ditions at the time of collection, calibration, frequency of measurements,
number of bands, resolution, and spectrometer specifications.

3.

The user enters the data information and selects the option to submit.

4.

The system determines that all required informat
ion is present.

5.

The system saves the data submitted.

6.

The system informs the user that the submission was successful

7.

End of use case.


Alt1: Step
4: The system determines that required information is missing.

Step
4.1: The use case continues at Step 2



Scen
ario for Manage Users Use Case

Description:
The user
manages users of the system. The user can add, delete, or modify users.


Actors:

Administrator

Precondition:

The user is registered in the MINER as an Administrator
.


Trigger Condition:

The user init
iates the
functionality to manage users.

Steps:

1.

Include <<
Login
>>

2.

The system displays a list of users.

3.

Extend <<
Create User
>>

4.

The user selects a user from the list.

5.

Extend <<
Delete User
>>.

6.

Extend <<
Edit User
>>.

7.

End of use case.


Alt1: Step
2: The system dis
plays an empty list of users

S
tep
2.1: Extend <<
Create User
>>

Step2.2: End of use case.



Scenario for Manage Submitted Data Use Case

Description:
The use
r manages data submitted for upload to the repository.

Actors:

Administrator
, Data Repository

Precondit
ion:

The user is registered in the MINER as an Administrator
.


Trigger Condition:

The user initiates the
functionality to manage submitted data

Steps:

1.

Include <<
Login
>>

2.

The system displays a list data submitted for upload.

3.

The user selects a data file.

4.

Th
e user approves the submission.

5.

The system uploads the data to the repository.

6.

The data file submission is deleted.

7.

End of use case.


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

32


Alt1: Step4: The user rejects the submission

Step4.1: The system deletes the data file

Step4.2: End of use case.


Alt2: St
ep2: The system displays an empty list of submitted data.

Step2.1: End of use case.



Scena
rio for Manage Sites

Description:
The user
manages research sites of the system.


Actors:

Administrator

Precondition:

The user is registered in the MINER as an Ad
ministrator
.


Trigger Condition:

The user initiates the
functionality to manage sites.

Steps:

1.

Include <<
Login
>>

2.

The system displays a list of sites.

3.

The user selects a site from the list.

4.

The users selects the option to delete the site

5.

The system prompts t
he user for confirmation.

6.

The user confirms

7.

The system deletes the selected research site.

8.

End of use case.


Alt1: Step
4: The user selects the option to update a site

S
tep
4.1: The system displays information for the selected site.

Step4.2: The user modif
ies the site information and selects the option to save

Step4.3: The system saves the modified information.

Setp4.4: The system informs the user that the save was successful.

Step4.5: End of use case.


Alt2
: Step
3: The user selects the option to create a

new site

S
tep
4.1: The system prompts the user for site information.

Step4.2: The user enters the site information and selects the option to save

Step4.3: The system saves the modified information.

Setp4.4: The system informs the user that the save wa
s successful.

Step4.5: End of use case.



Extend and Include Scenario:


Scenario for Login Use Case

Description:
The user enters a username and a password

if not already logged onto the system
. The system
authenticates the user’s identity.

Actors:

Admini
strator
,
Registered

User

Precondition:

The user is a Registered U
ser

or an Administrator
.

Trigger Condition:

The user initiates the following functionalities:

1.

Visualize
Data

2.

Download Data

3.

Submit Data

4.

Mange Users

5.

Manage Submitted Data

6.

Manage Registration

Requests

Steps:

1.

The system checks if the user is logged in and determines that the user is not one logged in.

2.

The system prompts the user for username and password.

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

33


3.

The user enters a username.

4.

The user enters a password.

5.

The user clicks login.

6.

The system
authenticates the user’s identity.

7.

The system changes the status of the user to log
ged

in.

8.

End of use case.


Alt1: Step
6
: The authentication fails. The system does not recognize the user as a legitimate user.

Step
6
.1: The system displays error message.

Ste
p
6
.2:

The use case continues at Step 2
.


Alt2: Step
6
: The system fails to authenticate any user.

Step
6
.1: The system displays error message.

Step
6
.2: End of use case.


Alt3: Step3: The user forgets his/her password. The user clicks on forgot password.

Ste
p3.1: The user enters username and selects the option to submit..

Step3.2: The system displays a notification message: Password will be sent to his/her email address associated
with the account.

Step3.3: End of use case.


Alt4
: Step
1
: The system
checks if
the user is logged in and determines that the user is logged in.

Step
4.1
: End of use case.



Scenario for Visualize Data Use Case

Description:
The user would like to visualize data that has been retrieved.

Actors:
Administrator, Registered

User

Preconditio
n:

The us
er has retrieved data

Trigger Condition:

The user initiates the
functionality to visualize data.

Steps

1.

The system prompts user to select the appropriate data visualization style for the data set chosen
including: scatter plot or histogram for num
eric data, maps depicting the locations of measurements
that have been taken and summary of those measurements, or show photographic data.

2.

The system processes the retrieved data and constructs the data visualization. The result is displayed to
the user.

3.

End of use case.



Scenario for Download Data Use Case

Description:
The

user downloads retrieved data


Actors:

Administrator
, Registered

User

Precondition:

The us
er has retrieved data.

Trigger Condition:

The user initiates the
functionality to download

data.

Steps:

1.

The user specifies the destination directory on the user’s machine using the internet browser’s file
explorer.

2.

The system creates the appropriate file, either a numeric flat file or jpeg and downloads the file to
specified directory on the us
er’s machine.

3.

The system informs the user that file transfer was successful.

4.

End use case.



Scenario for Analyze Data Use Case

Description:
The

user analyses retrieved data


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

34


Actors:

Administrator
, Registered

User

Precondition:

The us
er has retrieved da
ta

Trigger Condition:

The user initiates the
functionality to analyze data.

Steps:

1.

The user enters information specifying whether they want NDVI, PRI, or WBI.

2.

The user selects the option to submit.

3.

The system analysis the data.

4.

The system displays the res
ults.

5.

End use case.



Scenario for Create User Use Case

Description:
The user

creates a new user in the MINER.


Actors:

Administrator

Precondition:

The user is logged on as an Administrator
.

Trigger Condition:

The user initiates the functionality to

cre
ate a new user
.

Steps:

1.

The
system prompts the user for registration information
.

2.

Th
e user enters the registration information.

3.

The user clicks create user

4.

The system checks for missing registration information and determines that all required information i
s
present.

5.

The system creates a new user using provided registration information

6.

End of use case.


Alt1: Step4
: The

system checks for missing registration information and determines that information is missing.

Step4
.1:
The system displays an error message

Step4.2: The use case continues at Step 1



Scenario for Delete User Use Case

Description:
The user deletes a user from the system


Actors:

Administrator

Precondition:

The user is logged on as an Administrator and there is at least one Registered U
ser
in the system

Trigger Condition:

The user initiates
the functionality to delete a user
.

Steps:

1.

The user clicks on delete user

2.

The system prompts the user for confirmation of delete.

3.

The user selects ok.

4.

The system removes the user.

5.

End of use case.


Alt1:
Step
3
: The user
selects cancel

Step
3
.1:
End of use case



Scenario for Edit User Use Case

Description:
The user cha
nges the user’s information


Actors:

Administrator

Precondition:

The user is logged on as a
n Administrator and there is at least one user re
gistered in the system
.

Trigger Condition:

The user initia
tes the functionality to edit a

user
.

Steps:

1.

The system displays current registration information

2.

The user modifies the user information.

3.

The user clicks save

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

35


4.

The system prompts the user for confirm
ation

5.

The system saves the modified user information

6.

End of use case.


Alt1: Step
3
: The

user clicks cancel

Step
3.1: The system prompts the user for confirmation.

Step3.2: End of use case

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

36


Appendix B. Interface Screenshots



Figure A
-
1

Welcome Interface




Figure
B
-
2

Retrieve Data Interface

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

37




Figure
B
-
3

Retrieve Data Selection Panel




Figure
B
-
4

Analyze Data


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

38



Figure
B
-
5

Download

Data




Figure
B
-
6

Plot Data


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

39



Figure
B
-
7

View Tabular

Data




Figure
B
-
8

Submit Data


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

40



Figure
B
-
9

Manage Users




Figur
e
B
-
10

Manage

Data



Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

41



Figure
B
-
11

Mange Sites




Figure
B
-
12

Login

Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

42



Figure
B
-
13

Register




Figure
B
-
14

About Us


Software Requirements Specification




Software Requirements Specification

CS 4310 Fall 2007


Page

43


4.

Appendix C File Formats


"File:
\
Storage Card
\
070806m
\
m00001.spu"

"Remarks: SW=UniSpec Dual Channel NETCF Version=1.3 Comment="

"
Time: 8/6/2007 1:58:56 PM"

"Limits: 303.9081
-

1132.709"

"Environment: DegreesC=13.42 BattV=7.5465 A1=0 A2=2 A3=12 A4=8"

"Minimum: 1110.5nm 0"

"Maximum: 459.5nm 28620"

"Integration: 40 ms"

"Number Scans: 20"


303.9

36

26

307.2

42

2
9

310.6

45

30

313.9

56

31

317.2

68

35

320.5

85

45

323.8

111

54

327.2

136

67



1116.8

2

430

1120.0

10

427

1123.2

0.

424

1126.4

0.

419

1132.7

0.

415


Figure
C
-
1

SPU file format