Professional Documents
Culture Documents
Software Requirements
Specification
for
ACCUWEATHER
FURC
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................4
3.1 User Interfaces................................................................................................................................4
3.2 Hardware Interfaces........................................................................................................................4
3.3 Software Interfaces.........................................................................................................................4
3.4 Communications Interfaces............................................................................................................4
4. System Features.......................................................................................................................5
4.1 System Feature 1............................................................................................................................5
4.2 System Feature 2 (and so on)..........................................................................................................5
5. Other Nonfunctional Requirements.......................................................................................6
5.1 Performance Requirements.............................................................................................................6
5.2 Safety Requirements.......................................................................................................................6
5.3 Security Requirements....................................................................................................................6
5.4 Software Quality Attributes............................................................................................................6
5.5 Business Rules................................................................................................................................6
6. Other Requirements................................................................................................................7
Appendix A: Glossary....................................................................................................................7
Appendix B: Analysis Models.......................................................................................................7
Appendix C: To Be Determined List............................................................................................7
Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 Purpose
The main purpose of this document is to layout the requirement of this system. The document will describe
how the application will collect and display local area weather and analyze weather forecast. This document
serves as a layout for the user interface, software and hardware dependencies. The SRS will serve as a
reference for the development team for design, implementation and verification phases; the SRS is also an
agreement between the client and the development teams regarding the functionality of the finished product.
1.5 References
<List any other documents or Web addresses to which this SRS refers. These may include user interface
style guides, contracts, standards, system requirements specifications, use case documents, or a vision and
scope document. Provide enough information so that the reader could access a copy of each reference,
including title, author, version number, date, and source or location.>
2. Overall Description
SYSTEM INTERFACE
The user interface for the task will have a site that will have the live feed alongside the data about
the climate. This site will utilize HTML and ASP alongside CSS to add color and request to the site.
OPERATIONS
The site will have a live video feed of the climate and furthermore a live status of the climate from
a climate site. The video feed will be live and up-to-date. This administration targets giving
disaggregated locale/square level data in eachagroecological sub-area on figure climate.
FUNCTIONS
Smart Dissapation System
Evaluation Option For Users
Economical
Supervision And Review
Providing Information On Forecasted Weather & Agro-Met Advisory Services
user interaction programs -Conducted at State, District levels
Current Weather
a) This will show us the current weather
b) It is displayed on the main screen.
Hourly weather
a) By swiping right one time we can see hourly weather
b) Further info can be displayed by clicking on any hour
Daily weather
a) User can view weekly weather by swiping right
b) We can click on any day of the week for further information.
What to Wear
a) User will be able to know how to dress accordingly.
Allergies
a) User will be updated about the dust and dander
b) User will be able to look at the weekly rate of dust.
Fahrenheit
a) User can change the temperature into Celsius or Fahrenheit.
Global news
a) User will be able watch recent news update.
Multiple forecasts
a) Users can see forecast of multiple places at a time
Internal Dependencies:
The product will be only depending upon hardware which is the only internal dependency that we have to
care about.
Hardware Dependency
Some of the features of accuweather will rely on some of the hardware components of the android mobile
systems. First the app will be depending upon the memory of the android mobile systems. Therefore the
product installation will be depending upon available storage memory in the android mobiles. It also
depends on the location. We can manually put in our location to check weather. But we turn on our location
services, things will be way easier.
5. System Features
Following are the functionalities of the Accuweather application that are must for the system to work
properly, to fulfil its purpose, and provide a desirable output.
When the application is installed, user presses the icon and run it. Accuweather will display a
logo screen, and afterwards ask permission to locate the user automatically. If granted,
Accuweather will find the user location using the device’s GPS, otherwise, the user can
manually input his location by entering his desired city/state name.
5.4 ALLERGIES
This feature shows expected allergies of the current day. For all the people who need precautions. It
is a very useful app for them. It tells us about the dust and dander rate whether it is high or low. It
has an option of weekly outlook. By clicking on it tells us about weekly dust rate.
This is for user to wear a jacket or take an umbrella when going outside. It has comapretively
low priority.
This is for user to be updated about the global Weatherly news. It has medium priority.
5.8 SETTINGS
Settings enable user to manipulate context according to their ease. Through settings we can change
units of the wind gust, dew point, pressure, visibility etc. we can change date and time. Seetings
give us authority to decide if we want this app to notify us about clothes, weather and news. We can
chage themes. We can go through terms and conditions and privacy.
4.1.1 Description and Priority
Settings enable us to make changes according to our ease. We can change the notification settings.
This feature has high priority
It is for the user to see over view of the week. User shall know what weather to expect in the
week
It is for user to view weathers of multiple places. This feature has a high priority since no one
restricts themselves to one place only.
5.11 FARREHIET
This application enables user to converts the temperatures according to their ease. They can
view it in Fahrenheit as well as Celsius degree. If a company is using it for business
purposes they might require temperature in Fahrenheit. This function will then come in
handy.
It is for user to view weathers of multiple places. This feature has a high priority since no one
restricts themselves to one place only.
7. Other Requirements
Product Requirements
Requirements which specify that the delivered product must be have in a particular way e.g.
execution, speed, reliability, etc.
Organizational Requirements
Requirements which are a consequence of organization policies and procedures e.g. process
standers used, implementation requirements, etc.
External Requirements
Requirements which arise from factors which are external to the system and its development
process e.g. interoperability requirements, legislatives requirements, etc.
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You
may wish to build a separate glossary that spans multiple projects or the entire organization, and just include
terms specific to a single project in each SRS.>