SYSTEM REQUIREMENT SPECIFICATIONS(SRS)

FOR
WEATHER APPLICATION
1. Introduction:

1.1 Purpose:
The document is meant to delineate the features of Weather Application (WA), so as to serve as a guide to the
developers on one hand and a software validation document for the prospective client on the other.
The weather application is intended to provide the ease of access to the weather details of the present location
where the user is and also any other city that he/she wishes to look out for. The access to not only the present
weather status of the present location, but also the forecast for the desired location throughout the day is now
at the fingertips.

1.2 Scope:
The system allows an individual to keep a track of the daily weather conditions and the day-long forecast that allows
one to be prepared for the now precedent weather conditions.

1.3 Definitions :
WA- Weather Application (for live weather conditions and forecast for the day)
SRS- Software Requirement Specification
GUI- Graphical User Interface
Stackholder- The person that will be the participant in the system I.e the user.
API- Application Programming Interface

1.4 Overview:
The system is designed to provide an easily accessible weather application that will not only tell about the present
weather conditions in the searched city but also will estimate a forecast for the day from morning to the night.
The proposed application can be used by any of naive user too due to its user friendly interface. The usage does not
require any specific qualification, educational level, experience or technical expertise in the computer field.

2. Overall Description:
The Weather Application(WA) enables the user to look up any city that they desire to and obtain the accurate the weather
stats of the location. The person sitting in Delhi can look up the weather conditions in Maharashtra at the ease of
fingertips with just the help of an internet connection. Keeping the live temperature in accord, the user is also displayed a
full day weather forecast for the desired city.

2.1 Product Perspective:

The product is aimed at the general public who wish to keep their plans in handy in accordance with the anticipated
weather conditions. It also interests those who are living away from their loved ones and wish to keep a watch over
the weather conditions and take necessary gesture of care if needed.

2.2 User Characteristics:

User should be acquainted with the basic details of weather terminologies and symbols which display the weather
conditions like sunny, cloudy, oC etc.

2.3 Principle Actors:

The application requires three principle actors namely the user, administrator, and the weather provider API.

2.4 General Constraints:

An internet connection and location services(GPS).

3. Specific Requirements:

3.1 Functional Requirements:

This section will be providing with the requirement overview of the system.
Various Functional modules that can be implemented by the system will be as follows:-
 3.1.1 Search:
The user will have to enter the location of the city they wish to see the weather conditions of.

3.1.2 Touch Interface:

The user can access the full screen of the weather condition by tapping on the icons. Also the forecast division
which is displayed on the lower side of the screen can be displayed in a bigger view on the ease of a tap.

3.2 Non-Functional Requirements:

The Non-Functional Requirements define the system properties and the constraints.
Following are the non functional requirements which will be there in the insurance to the internet.
 The user location to be secured.
 Ease of design and optimum performance through good component design.
 Flexible architecture for future extensions to be inculcated.

A few other Non-Functional Requirements that are targeted are:

 Security
 Reliability
 Maintainability
 Portability
 Extensibility
 Compatibility
 Optimum resource utilization

3.3 Performance Requirements:

The server will be a 24*7 active element but the connections to them will be based on the attributes of the user like
their location and internet connectivity. In order to maintain an acceptable speed at the maximum number of
requests by an arbitrary ‘N’ number of users will equivalent number of requests, optimum designing is required.

3.4 Technical Constraints:

The application works on a client-server architecture, which will require an active internet connection able to run PHP
application.

4. Interface Requirement:
The various interfaces for the product are:
 The temperature display.
 The forecast zone.
 The symbolic representation of the current and future conditions.
 City search interface.

4.1 Software Interface:

The software interface requirements for the developer are as follows:
 Operating System: Windows 7 or later.
 JAVA Development Toolkit.
 Android Studio application.
The software interface requirements for the user are as follows:
 An android phone.
 Operating System: Android 5 (Android Lolipop) or later.
 GPS accessibility.
 Active connection to the internet.

4.2 Hardware Interface:

Hardware requirements for the developer are as follows:
 Processor: Dual Core or later.
 RAM: Minimum of 2GB.
 Hard Disk: 320GB and above.
 NIC: Basic requirement for each party.
Hardware requirements for the user are as follows:
 Processor: Any processor launched over the past 10 years.
 RAM: 2GB or above.
 Secondary Storage: Minimum requirement for the application.
  NIC: Basic requirement for both the parties.

4.3 Communication Interface:

The user should be connected to any active connection to the internet. The server must keep an eye on the
maintenance of the API key so as to not let it expire.

5. System Design Specification:

5.1 Architectural Design:

5.1.1. Data Flow Diagram(DFD):

5.1.2 1 Level DFD For User:

5.1.3 Entity Relationship (ER) Diagram: