Srs

1. StuDocu is not sponsored or endorsed by any college or university
Whether - software requirement specification srs
Software Engineering (Lovely Professional University)
StuDocu is not sponsored or endorsed by any college or university
Whether - software requirement specification srs
Software Engineering (Lovely Professional University)
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

2. Software Requirements
Specification (SRS)
Indian Weather:Accuweather.com
Prepared for – Manveer Kaur
By Name – Sunny
Section- K1507
Roll_No- B35
Reg_No- 11504494
1
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

3. Table of Contents
1 Introduction ................................................................................................................................ 3
1.1 Purpose ................................................................................................................................. 3
1.2 Scope ..................................................................................................................................... 3
1.3 Overview .............................................................................................................................. 4
1.4 Glossary of Terms ............................................................................................................... 4
1.5 Business Context .................................................................................................................. 5
2 Overall Description .................................................................................................................... 6
2.1 Product Perspective............................................................................................................. 6
2.1.1System Interfaces .............................................................................................................. 6
2.2Operations .................................................................................................................................7
2.2.1 Features………………………………………………………………………………………7
2.3 Similar Systems ................................................................................................................... 8
2.4 User Characteristics ............................................................................................................ 8
2.5 User Objectives .................................................................................................................... 8
2.6 Constraints ........................................................................................................................... 9
3 Specific Requirements ............................................................................................................... 9
3.1 Functional Requirements ................................................................................................... 9
3.2 User Interface Requirements ........................................................................................... 10
3.2.1 User Interface: Graphical (GUI) or Command-Line (CLI) ................................... 11
3.2.2 Application Programming Interface (API) .............................................................. 11
3.2.3 Diagnostics (Error Reporting and Usage Logs) ....................................................... 12
3.3 System Requirements ........................................................................................................ 12
3.3.1 Hardware Interfaces................................................................................................... 12
3.3.2 Communications Interfaces ....................................................................................... 13
3.4 Software Interfaces ........................................................................................................... 13
3.5 Non-Functional Requirements ......................................................................................... 13
3.5.1 Reliability .................................................................................................................... 13
3.5.2 Availability .................................................................................................................. 14
3.5.3 Security ........................................................................................................................ 14
2
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

4. 3.5.4 Maintainability............................................................................................................ 14
3.6 Logical Database Requirements ...................................................................................... 14
4 Software Life Cycle Model ...................................................................................................... 14
4.1 Choice of Software Life Cycle Model .............................................................................. 15
4.2 Justification for Choice of Model ..................................................................................... 15
5 References…………………………………………………………………………………………….15
3
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

5. 1.Introduction
1.1 Purpose
The purpose of this document is to layout the requirements for the system. The document will describe how the
product will collect and display local weather data and analyze the weather forecast. This product will be of use
to the society.
1.2 Scope
The product is named Accuweather.com. It will be able to collect and display local weather data, analyze
weather forecast and display a live stream of the local weather. The product will be able to predict the weather.
The product will be accessible through a website where you will have the benefit of seeing what the weather
looks like outside and see if the walkways have been shoveled. The main goal is to have a website that will
give you information about the weather. We can use the following;
-Automated process e-alert/warning
-Creation of infrastructure facilities
Service 4 Providing Information On Forecasted Weather & Agro-Met Advisory Services
-Provide G2G, G2C, G2B ,G2E services
4
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

6. 1.3 Overview
Section two will describe how the product will be accessible and its functions. The constraints of the product
and similar products will be discussed as well. Section three will describe the specific requirements for the
product. Section four will discuss the software life cycle model that was chosen and the reason.
1.4 Glossary of Terms
● API (Application Programming Interface) – a set of routines, protocols and tools for building software
and applications.
● ASP Pages (Active Server Pages) – Microsoft’s first server-side script engine for dynamically generated
web pages.
● C# - a multi-paradigm programming language encompassing string typing, imperative, declarative,
functional, generic, object-oriented (class-based), and component-oriented programming disciplines.
● Java – a general-purpose computer programming language that is concurrent, class-based, object-
oriented, and specifically designed to have as few implementation dependencies as possible.
● HTML (HyperText Markup Language) – the standard markup language used to create web pages.
● CSS (Cascading Style Sheets) – a style sheet language used for describing the presentation of a
document written in a markup language.
● Javascript – a high -level, dynamic, un-typed, and interpreted programming language.
5
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

7. ● SQL (Structured Query Language) – a special-purpose programming language designed for managing
data held in a relational database management system (RDBMS), or for stream processing in a
relational data stream management system (RDSMS).
● Git – a widely-used source code management system for software development.
● GitHub – a web-based Git repository hosting service.
● Google Docs – a word processor that is a part of a free, web-based software office suite offered by
Google within it Google Drive service.
2 .Overall Description
2.1 Product Perspective
The Accuweather.com will be using ideas based on weatherUSA (www.weatherusa.net) and the National
Weather Service (www.weather.gov). Both of these websites use cameras to show live feeds of the weather in
various locations.
6
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

8. 2.1.1 System Interfaces
The user interface for the project will host a website that will have the live feed along with the information
about the weather. This website will be using HTML and ASP along with CSS to add colors and order to the
website.
2.1.2 Operations
The website will host a live video feed of the weather and also a live status of the weather from a weather
website. The video feed will be live and up-to-date.
This service aims at providing disaggregated district/block level information in eachagroecological
sub-region on forecast weather.
2.2 Product Functions
The Accuweather.com will collect and display the local weather data from the live video feed. It will also
analyze the weather forecast to allow users to know what to expect for the forecast for that day. The
Accuweather.com will also have a link to a weather website where it will show the current temperatures along
with a 5-day forecast.
Features:
•Smart Dissemination System
•Feedback option for end users
7
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

9. •Less expensive
•Monitoring & Review
.Providing Information On Forecasted Weather & Agro-Met Advisory Services
.user interaction programs -Conducted at State, District levels
.
2.3 User Characteristics
The intended audience for Accuweather.com will not need technical expertise or any technical experience at all.
They will only need basic computing skills and basic knowledge of how to operate Internet web pages.
2.4 User Objectives
● Collect & display local weather data.
● Analyze weather forecast.
● Show a live video feed of the current weather outside.
8
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

10. 2.5 Constraints
The constraints for the project will rely on the amount of disk space that is use for storing the images, videos or
the forecasts. There is also a network constraint for the internet speeds and how fast the website will run.
2.6 Geographical Information System ‘GIS’
•‘GIS’system captures, integrates, stores, edits, analyzes, shares, and displays geographic information.
•It is digitally creates and "manipulates"
•It is digitally creates and "manipulates" spatial areas.
•Allow users to create interactive queries, analyze spatial information, edit data, maps, and present the results
of all these operations.
9
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

11. 3 .Specific Requirements
3.1 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.
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.
10
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

12. 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.
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.
11
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

13. b. Criticality Rating: 2
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. 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.
12
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

14. 3.2 User Interface Requirements
3.2.1 User Interface: Graphical (GUI) or Command-Line (CLI)
This system will provide a graphical user interface. The layout of the system will be a webpage that has a
header on the top displaying the name of the website, under the header there will be a navigation bar to go to
related pages, under the navigation bar is the body or main focus which will have a live weather stream on one
half of the page while displaying the forecast on the other half, and at the bottom of the page will be a footer
that will have contact information.
3.2.2 Application Programming Interface (API)
This system will not be an API.
3.2.3 Diagnostics (Error Reporting and Usage Logs)
There is no need for error reporting in this system once the system is complete.
3.3 System Requirements
3.3.1 Communications Interfaces
There are two interfaces that our system will interact with. The first interface is the Weather Channel website to
provide the forecast. The second interface is the camera that the live weather feed will come from.
13
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

15. 3.3.2 Software Interfaces
The software interfaces that will be used are Visual Studio and SQL Management Studio. Visual Studio will be
used for coding the website. SQL Management Studio will be used to maintain the database to store the
forecast.
3.4 Domain Requirements/Constraints
There are no domain requirements or domain constraints.
3.5 Non-Functional Requirements
3.5.1 Reliability
The reliability of the system is to make sure the website does not go offline.
3.5.2 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.
3.5.3 Maintainability
The attribute that will help maintain the system is clean code.
3.6 Logical Database Requirements
The information that will be put into the database are the photos (if the system has progressed that far) and the
database would be accessed daily if the photos are stored.
14
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

16. 3.7 Product requirements
Requirements which specify that the delivered product must be have in a particular way e.g. execution
speed,reliability,etc.
3.8 Organizational Requirements
Requirements which are a consequence of organizational policies and procedures e.g. process standards used,
implementation requirements, etc.
3.9 External requirements
Requirements which arise from factors which are external to the system and its development process e.g.
interoperability requirements, legislative requirements, etc
4 .Software Life Cycle Model
4.1 Choice of Software Life Cycle Model
We will use Evolutionary Prototyping Software Lifecycle Model to create Accuweather.com. We will not make
any modifications to the standard cycles of the model for this project.
15
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963

17. 4.2 Justification for Choice of Model
We felt that the Evolutionary Prototyping Software Lifecycle Model was the best lifecycle model for
Accuweather.com as it is the easiest model to create a product with a strict deadline and loose requirements.
References
1.http://www.accuweather.com/en/in/india-weather
2.http://weatherclimate.com/alert.html
3.http://indianweather.com/Glossary.html
4.Accuweather – Wikipedia, the free encyclopedia
5.http://en.wikipedia.org/wiki/accuweather.html
16
Downloaded by ABHISHEK Rajput (abhishekrajput2310@gmail.com)
lOMoARcPSD|16024963