Software Engineering Weather Forecasting System PDF

Preview

Summary

Software Engineering ProjectWeather ForecastingSystemGroup Members- Aviral Mehrotra  Pratham Mandloi  Simran SinghABSTRACT The SRS document contains the details of the team members involved in project successful completion and the client who requested to develop an application. This SRS document ...

Description

Software Engineering Project

Weather Forecasting System

Group Members  

Aviral Mehrotra Pratham Mandloi Simran Singh

ABSTRACT

The SRS document contains the details of the team members involved in project successful completion and the client who requested to develop an application. This SRS document enables the contract between the client and team members and ensures client satisfaction. This document will contain details of the requirements for the application being developed by team. A list of functional and nonfunctional requirements will be given.

TABLE OF CONTENTS

1 Introduction .................................................................................................................................... .5 1.1 Purpose .................................................................................................................................. 5 1.2 Scope ..................................................................................................................................... 5 1.3 Overview ................................................................................................................................ 5 1.4 Glossary of Terms .................................................................................................................. 5 2 Overall Description ......................................................................................................................... 6 2.1 Product Perspective............................................................................................................... 6 2.1.1 System Interfaces ......................................................................................................... 6 2.2.1 Operations ..................................................................................................................... 6 2.2 Product Functions……………………………………………………………………………………. 6 2.3 User Characteristics................................................................................................................ 7 2.4 User Objectives....................................................................................................................... 7 2.5 Constraints............................................................................................................................... 7 2.6 2.6 Geographical Information System “GIS” ……………………...........................................7 3 Specific Requirements .................................................................................................................... 7 3.1 Functional Requirements ...................................................................................................... 8 3.2 User Interface Requirements ................................................................................................ 9 3.2.1 User Interface: Graphical (GUI) or Command-Line (CLI) ......................................... 9 3.2.2 Diagnostics (Error Reporting and Usage Logs) ............................................................9

Weather Forecasting System

PAGE 3

3.3 System Requirements ...........................................................................................................9 3.3.1 Hardware Interfaces.....................................................................................................9 3.3.2 Communications Interfaces .......................................................................................10 3.3.3 Platform Requirements……………………………………………………………………….10 3.4 Software Interfaces ...............................................................................................................10 3.5 Non-Functional Requirements .............................................................................................10 3.5.1 Reliability .......................................................................................................................10 3.5.2 Availability ....................................................................................................................10 3.5.3 Security ..........................................................................................................................10 3.5.4 Maintainability...............................................................................................................10 3.6 Logical Database Requirements .........................................................................................10 3.7 Product Requirements ..........................................................................................................11 3.8 Organisational Requirements ..............................................................................................11 3.9 External Requirements ..........................................................................................................11 4 Entity Relationship Diagram……………………………………………………………………………….12 5 Domain Analysis…………………………………………………………………………….……………….13 5.1 Requirements………………………………………………………………………………………….13 5.1.1 Functional Requirements……………………………………………………………………..13 5.1.2 Non-Functional Requirements……………………………………………………………….13 5.2 Problem Statement………………………………………………………………………………...…13 5.3 Resources………………………………………………………………………………………………13 5.4 General Knowledge……………………………………………………………………………….…14 5.5 Task and Procedures ……………………………………………………………………………..…14 5.6 Environment……………………………………………………………………………………………15 5.7 Competing Softwares ……………………………………………………………………………….15 References……………………………………………………………………………………………………....15

Weather Forecasting System

PAGE 4

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 tempestascorrecto.com. The word “tempestascorrecto” is made up of 2 words i.e., tempestas and correcto, in Latin “Tempestas” means “Weather” and in Spanish “Correcto” means “Correct”. 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: 1. Automated process e-alert/warning 2. Creation of infrastructure facilities 3. Service for Providing Information on Forecasted Weather & Agro-Met Advisory Services 4. Provide G2G, G2C, G2B, G2E services. 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, classbased, 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.

Weather Forecasting System

PAGE 5

● 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. ● 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 its Google Drive service. 2. Overall Description 2.1 Product Perspective The tempestascorrecto.com will be using ideas based on weather USA (www.weatherusa.net) and the National Weather Service (www.weather.gov). Both websites use cameras to show live feeds of the weather in various locations. 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 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 each agroecological subregion on forecast weather. 2.2 Product Functions The tempestascorrecto.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 •Less expensive •Monitoring & Review •Providing Information on Forecasted Weather & Agro-Met Advisory Services •User interaction programs -Conducted at State, District levels.

Weather Forecasting System

PAGE 6

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. 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 creating and manipulating spatial areas. •Allows users to create interactive queries, analyze spatial information, edit data, maps, and present the results of all these operations.

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.

Weather Forecasting System

PAGE 7

1. Camera Position a. Description: Cameras will be placed all over. b. Criticality Rating: 3 c. Technical Issues: No technical issues to report at that 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 a 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. 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 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.

Weather Forecasting System

PAGE 8

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. 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 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.

Weather Forecasting System

PAGE 9

3.3.2 Software Interfaces The software interfaces that will be used are Visual Studio Code and SQL Management Studio. Visual Studio Code will be used for coding the website. SQL Management Studio will be used to maintain the database to store the forecast. 3.3.3 Platform Requirements

Hardware /Software

Hardware /Software Elements

Specification/Version

Hardware

Processor RAM HDD OS

i3 4th gen 4gb 250 GB Windows/ Linux/ Mac OS

Browser

Chrome/ Mozilla/ Edge

Software

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. Weather Forecasting System

PAGE 10

3.7 Product Requirements Requirements which specify that the delivered product must 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.

Weather Forecasting System

PAGE 11

4. Entity Relationship Diagram

Weather Forecasting System

PAGE 12

5. Domain Analysis 5.1 Requirements 5.1.1 Functional Requirements Functional requirements are the requirements that describe the functionalities of the system elements. It may involve functional user requirements or functional system requirements. For example:  The operator shall be able to input the weather periods to the system to view the desired weather parameters within the periods.  The system shall be able to produce minimum, maximum and the average data of a particular weather parameter when it is requested by an operator.  The system shall provide the following weather parameters: temperature, pressure, wind speed & direction, rainfall, and humidity. 5.1.2 Functional Requirements Non-functional requirements describe the system properties and constraints. Whereas these may not describe directly what the system should do or perform, instead they describe the standard of the objectives that the system should achieve. For example:  The weather system shall be ready by 31 November 2017.  It shall not exceed the budget that has been stated in the MOU ($1.3 million).  System’s operational and location of remote station and central station shall not violate the current Government regulations of environment.  The weather sensors shall be able to be upgraded every 5 years. 5.2 Problem Statement The two problems are the primary concerns when you consider a weather monitoring system and we have come up with cost effective innovative solution to provide the layman's weather monitoring system. 5.3 Resources Key players in the weather forecasting systems market are The Weather Company (US), Vaisala (Finland), Sutron Corporation (US), Campbell Scientific (US), Airmar Technology Corporation (US), All Weather, Inc. (US), Morcom International (US), Columbia Weather Systems (US), G. Lufft Mess-und Regeltechnik (Germany), and Skye Instruments (UK), among others.

Weather Forecasting System

PAGE 13

5.4 General Knowledge Weather forecasting and prediction involves formulating and disseminating information about future weather conditions based upon the collection and analysis of meteorological observations. Numerical weather prediction is the prediction of weather phenomena by the numerical solution of the equations governing the motion and changes of condition of the atmosphere. Weather analysis and forecasting involves collecting global meteorological surface and upper-air observations, preparing global surface and upper air pressure, temperature, moisture, and wind analyses at frequent time intervals based upon these observations, solving...