Software

Requirements

Specification (SRS)
Project For: Accuweather.com

Submitted to: DALWINDER SINGH

Sumitted by
Name: ALIMINETI BALA SHIVA SAI RAM
REDDY
Reg No: 11803644
Roll No: 68 || Section: K18PD

0 0
 Introduction
This section describes the purpose, intended audience, and overview of the
document as well as the scope and intended use of the systems being developed.

1.1.Purpose and Scope of Product

The purpose of the Software Requirements Specification (SRS) document is to

provide a clear and precise description of the functionality of the Weather History
(WH) system. The SRS will serve as a reference for the development teams
during the design, implementation and verification phases; the SRS is also an
agreement between the client and the development teams regarding the
functionality the finished product will perform.

In recent years, the Earth has experienced drastic climate changes. It has become
of great importance to understand and study these changes and their impact on the
human race. Scientists all over the globe including at the Systems Ecology Lab at
University of Texas at El Paso (UTEP) have put an enormous amount of effort
into gathering and analyzing weather data. Currently, the UTEP research team
utilizes the Circumarctic Environmental Observatories Network (CEON) web-
based mapping and information system. CEON allows access to near real-time
reports of earthquakes, climate data, and webcam images. The success of this
powerful application has inspired interest in extending both the functionality of
the system and the geographical scope to which it applies. Weather History system
will serve as an extension to CEON which will allow users to access historical
climate data from weather stations from across the North American continent.

To provide scientists with enough information to understand the changes in the

climate, the WH system will provide means to access historical data from
historical weather data sources such as National Oceanic and Atmospheric
Administration (NOAA). The tool will search for historical weather data
specified by a list of weather stations, types of weather data to be collected, and a
time range supplied by an end-user. This tool will provide a means for
environmental scientists, researchers, university professors, students, and the
general public to have easy access to historical weather data for further analysis
and therefore will improve the research community’s ability to understand and
make inferences about certain phenomena regarding our climate system.

1.1. Overview
The SRS is divided into six major sections: Introduction (Section 1), General Description (Section 2),
External Interface Requirements (Section 3), Behavioral Requirements (Section 4), Non-behavioral
Requirements (Section 5), and Other Requirements (Section 6). This overview describes Section 2
through Section 6 of the SRS.

0 0
Section 2 provides a general description of the system including its overall structure and
functionality, users and actors of the systems, the operating environment in which the system will
run, existing constraints on the system, and assumptions and dependencies.
Section 3 describes the specification of requirements for interfaces between the system and external
components, both human and other systems. It contains specifications with respect to user,
software, hardware, and communication interfaces.
Section 4 includes five subsections. It describes the behavioural requirements of the system. The
requirements are organized in the following categories: same class of user, related real-world
objects, stimulus, related features, and functional requirements.
Section 5 includes three subsections. It outlines the non-behavioural requirements of the system
which consists of performance, security and qualitative requirements with respect to availability,
maintainability, portability, and design and implementation constraints.

Functional Requirements
Criticality Scale: Low (1) – Medium (2) – High (3)
1.Low: Items that can be eliminated should the need arise, without
adversely affecting the product.

These items are not urgent and not as important to the final product.

2.Medium: Items that are desired by the customer and/or users of

the system, but that may be postponed until a future release. These
items are not urgent but are important parts of the final product.

3.High: Items that are mission critical and without which the system
cannot function in a manner that is satisfactory to the customer.
These items are urgently needed and important to the success of the
final product.

1. Camera Position
a. Description: Cameras will be placed all over.

b. Criticality Rating: 3

c. Technical Issues: No technical issues to report at the

moment.

0 0
 d. Risks: Public may tamper with the camera.
e. Dependencies: The system is dependent on the quality of
the camera.

2. Live Stream
a. Description: The system will display a live stream from the

camera view from requirement 1 on a functional website.

b. Criticality Rating: 3
c. Technical Issues: We are unsure what type of camera we

are using and how to connect to said camera.

d. Risks: Possible loss of this feature.

e. Dependencies: The system is dependent on the quality of

the camera.

3. Current Weather
a. Description: The system will retrieve the current weather

conditions and display them on the webpage.

b. Criticality Rating: 3

c. Technical Issues: The website that the system uses to

retrieve this information may change format.

d. Risks: Possible loss of this feature.

0 0
 e. Dependencies: The system is dependent on the website that

retrieves current weather data.

4. Weather Forecast
a. Description: The system will get the forecasted weather

conditions and display them on the webpage.

b. Criticality Rating: 2

c. Technical Issues: The website that the system uses to

retrieve this information may change format.

d. Risks: Possible loss of this feature.

e. Dependencies: The system is dependent on the website that

retrieves current weather data.

5. Forecasting Accuracy
a. Description: The system will retrieve the forecasted

weather conditions and measure the accuracy of said

predictions.

b. Criticality Rating: 2

0 0
 c. Technical Issues: The website that the system uses to

retrieve this information may change format. Also, the

development team needs a way to store this information.

d. Risks: Possible loss of this feature.

e. Dependencies: The system is dependent on the website that

retrieves current weather data.

6. Snapshots
a. Description: The system will display snapshots of the daily

weather on an hourly basis.

b. Criticality Rating: 1

c. Technical Issues: The development team needs to design a

way to store the images.

d. Risks: Possible interference with the live stream.

e. Dependencies: The system is dependent on the quality of

the camera.

7. Timestamps
a. Description: The system will place timestamps on the

snapshots in requirement 6.

0 0
 b. Criticality Rating: 1

c. Technical Issues: The development team needs to figure

out a way to place the timestamp on the photos.

d. Risks: Possible interference with the live stream and

snapshots.

e. Dependencies: The system is dependent on the quality of

the camera and the storage space.

Non-Functional
Requirements

Reliability
The reliability of the system is to make sure the website does not go
offline.

Availability
The availability of the system is that the website will be active on the
Internet and people will be able to browse to it.

Maintainability
The attribute that will help maintain the system is clean code.

Capacity

0 0
The capacity of the system is how it can take a update within a short
time.

Serviceability
How it services to the users and also for the exact information.

Security
The system must have some security for that the other system can’t
take it easily.

Data Integrity
It is an old concept made essential in today's digital age, and means
data that is accurate, complete, and repeatable.

0 0
2. Other Requirements
2.1. Database
[REQ 1] The system shall store the weather data in the CEON Weather Database managed by
PostgreSQL.
[REQ 2] The system shall not store duplicate set of data into the database.

0 0