1.

INTRODUCTION 5

1.1.Objective of the System

1.2.Justification and need for the system 5
1.3. Advantage of the system
6
1.4 Previous work or related systems, how they
are used. 6

REQUIREMENT ANALYSIS 7
2
2.1 Analysis Study 7-8
2.2 User Requirements
2.3 Final Requirements 9
10
3 DESIGN OF THE SYSTEM

3.1 Hardware, Software requirements 10

3.2 System requirements 10-11
3.3 Design Requirenment 11-12
3.4 DFDs
13

4 IMPLEMENTATION & CODING 14-15

16
4.1 Operating System 16
4.2. Languages 17-43
4.3 Coding

44
5 TESTING & TEST RESULTS
44-47
1. Software Testing and Objective of Testing
48-49
5.2 Sample test data/ Output screen printouts
etc.

6 CONCLUSION 50

1. Conclusion 50
50
2. Future Scope

51
Biblography
 Chapter 1
INTRODUCTION

Weather forecasting is the application of science and technology to predict

the state of the atmosphere for a given location. Ancient weather forecasting
methods usually relied on observed patterns of events, also termed pattern

recognition. For example, it might be observed that if the sunset was particularly
red, the following day often brought fair weather. However, not all of these

predictions prove reliable

1.1OBJECTIVE OF THE SYSTEM

This project will serve the following objectives:

1. Provides the user with an casy and friendly interface

2. Provides the user with the temperature of a particular region

3. It will also show humidity, wind speed and cloud

1.2 JUSTIFICATION AND NEED FOR THE SYSTEM

Weather is something everybody deals with, and accurate data about it like what is coming can help
users tomake informed decisions. With weather apps for iOS and Android, people can exactly know
when to expect a change in the weather conditions. Weather apps can give urgent alerts too.

Undoubtedly, weather forecasting has come a long way, helping people to know aboutweather
conditions. So, if you are in an area where weather frequently changes from sunny to torrential rain in a
matter of minutes, then what is the easiest way to make sure to be prepared? A suitable answer is a
weather application.
1.3 Advantages of the system
1. Real-TimeData
One of the biggest advantages of weather monitoring systems and also the reason why people have
been going in for weather stations is because of the ability to get their information in real-time.

2. Accurate Local Forecast

In reality, the meteorological department may be located far from your home and weather forecasts are
made for regions, not a specific area. That's a reason why in these instances, the weather predictions that
they give are not always the most accurate.

3. Ease Of Use
Ease to use is definitely a big advantage of the weather monitoring system. Weather stations like all
other weather devices are designed to be efficient and straightforward, therefore, everyone can use them.
It is so convenient and comfortable for users to get the most accurate information in the simplest way
possible.

1.4 Previous work or related systems; how they are used.

Before we begin a new system it is important to study the system that will be improved or replaced (if
there is one). We need to analyze how this system uses hardware, software, network and people
resources to convert data resources, such as transaction data, into information products.

Following are the problems associated with the previous project which led to the creation of the
proposed project:

1. Not user-friendly: The existing system is not user-friendly because the information like humidity
cloud and wind etc are not in oneplace.

2. Not a good UI: The user interface of the previous systems are not that good.
 Chapter 2
REQUIREMENT ANALYSIS

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:
OThe operator shall be able to input the region to the system toview the desired weather parameters.

OThe system shall provide the following weather parameters: temperature, pressure, wind speed ,date /
time and humidity.

2.1 ANALYSIS STUDY

1. Lower Installation Charges:

We neither require any high-configuration systems for the smooth running of the server program nor do
we require any high-configuration systems for the smooth running of a client program. This application
is designed with ease to supportany ordinary system having an internet connection.
2. Secured and Reliable:

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

3. Availability

The availability of the system is that the website will be active on the Internet and people

will be able to browse it.

 Chapter 3
DESIGN OF THE SYSTEM

3.1 Software requirements

Platform Platform Independent

TheOperating System Windows 7

Framework Bootstrap
Front-End Tool Google Chrome
API OpenWeatherMap

3.1 Hardware Requirements

Processor Intel Pentium IV 2.9 GHz Other

RAM Minimum 4 GB

Graphics Integrated graphics card

Hard Disk Minimum 500 GB

3.2 System Requirements

To know the detailed system requirements an SRS has to be prepared. Software requirement
specification abbreviated as SRS is a means of translating the idea of files into a formal document. The
main features of SRS include:

Establishing the basis for an agreement between the client and the developer.

Producing areference for validation of the final product. SRS assist clients in determining if the
software meets their requirements.
Mainly there are six requirements which an SRS must satisfy.

(a) It should specify the external behaviour.

(b) It should specify the constraints.

(c) It should be easy to change.

(d) It should be a reference tool.

(e) It should record throughout the lifecycle.

() It should have the capacity to expect an undesired event.

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 region to the system to view the desired weather parameters.

o The system shallprovide the following weather parameters:temperature, pressure, windspeed &
direction, rainfall, and humidity.

3.3 Design Requirements

The main objectives of input design are:

(a) Controlling the amount of input

(b) Keeping the process simple.

(c) The best thing in the input design is to achieve all the objectives mentioned in the simplest manner
possible.

The main objectives of output design are:

(a) Identifying the specific outputs.

The primary goal of the system analysis is to improve the efficiency of the existing system. For that the
study of specification of the requirements is very essential. For the development of the new system, a
preliminary survey of the existing system will be conducted. Investigation done whether the upgradation
of the system into an application program could solve the problems and eradicate the inefficiency of the
existing system
3.5 DATA FLOW DIAGRAM (DFD)
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modelling its process aspects. Often they are a preliminary step used to create an overview of
the system which can later be elaborated. DFDs can also be used for the visualization of data
processing (structured design).

Fig3.4 DFD

A DFD Shows what kinds of information will be input into and output from the system, where the data
will come from and go to, and where the data will be stored. It does not show information about the
timing of processes, or information about whether processes will operate in sequence or in parallel
(which is shown on a flowchart).
 4.1OPERATING SYSTEM
Platform Independent: Since the project is done completely in HTML, CSS and JavaScript, it also
executes the main properties of the language. The application is platform-independent.

4.2Languages used
HTML

The HyperText Markup Language or HTML is the standard markup language for documents
designed to be displayed in a web browser. It can be assisted by technologies such as Cascading Style
Sheets (CSS) and scripting languages such as JavaScript.
Web browsers receive HTML documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes thestructure of a web page semantically and
originally included cues for the appearance of the document.

CSS

CSS stands for Cascading Style Sheets. It is a style sheet language which is used to describe the look
and formatting of a document written in markup language. It provides an additional feature to HTML. It
is generally used with HTML to change the style of web pages and user interfaces. It can also be used
with any kind of XML documents including plain XML, SVG and XUL.

CSS is used along with HTML and JavaScript in most websites to create user interfacesfor web
applications and user interfaces for many mobile applications.

JavaScript
JavaScript is a dynamic computer programming language. It is lightweight and most commonly used as
a part of web pages,whose implementations allow client-side seript to interact with the user and make
dynamic pages. It is an interpreted programming language with object-oriented capabilities.
 Chapter 5
TESTING & TEST RESULT'S

5.1 SOFTWARE TESTING

Software testing is a critical element of software quality assurance and represents the ultimate review of
specification design and coding. Testing is an exposure of a system to trial input to see whether the
software meets the correct output. Testing cannot be determined whether the software meets the user's
needs, only whether it appears to conform to requirements. Testing can show that a system is free of
errors, only that it contains errors. Testing finds errors, it does not correct errors. Software success is a
quality product, on time and within cost. Testing can reveal critical mistakes. Testing should, therefore,

Validate Performance

Detects Errors

Identify Inconsistencies

5.2 Test Objective

There is strong evidence that effective requirement management leads to overall project cost
savings. The three primary reasons for this are,

Requirement errors typically cost wellover 10 times more to repair than other errors.

Requirement errors typically comprise over 40% of all errors in a software project.

A small reduction in the number of requirement erTors pays a big dividend in avoided rework
costs and schedule delays.

Systems are not designed as entire systems nor are they tested as single systems the analyst must
perform both unit and system testing. For this different level of testing are used:
5.2.1 Unit Testing
In unit testing Module is tested separately and the programmer simultaneously along with the coding of
the module performs it.

In unit testing the analyst tests the programs making up a system. For this reason, unit testing is
sometime called program testing. Unit testing gives stress on modules independently of one another, to
find errors. This helps the tester in detecting errors in coding and logic that are contained within that
module alone. The errors resulting from the interaction between modules are initially avoided.

Unit testing can be performed from the bottom up, Starting with smallest and lowest-level modules and
proceeding one at a time., for each module in Bottom-up testing a short program is used to execute the
module and provides the needed data, so that the module is asked to perform the way it will when
embedded within the larger system.

5.2.2 System Testing

This isperformed after the system is put together. The system is tested against the system requirement to
check if all the requirements are met and if the system performs by specifying the requirements.

Testing is an important function of the success of the system. System testing makes a logical assumption
that if allthe parts of the system are correct, the goal will be successfully activated. Another reason for
system testing is its utility as a user-oriented vehicle before implementation.
The function of testing is to detect defects in the Software. The main goal of testing is to uncover
requirement, design and coding errors in the progranms. The types of testing are discussed below:

5.2.3 MODULE TESTING

Module tests are typically dynamic white-box tests. This requires the execution of the software or parts
of the software. The software can be executed in the target system, an emulator, simulator or any other
suitable test environment.

The focus of the tests is:

Set up of regression tests. This means the test environment once set up for a function can be re
used to check its performance e.g. after maintenance.
 Coverage of the relevant state of the art test methods like equivalence class building, boundary
value analysis and condition coverage are used.
5.2.3 INTEGRATION TESTING
"If they all work individually, they should work when we put them together." The problem of course is
"putting them together . This can be done in two ways:
1. Top down integration: Modules are integrated by moving downwards through the control
hierarchy, beginning with main control module are incorporated into the structure in either a
depth first or breadth first manner.
2. Bottom up integration: It begins with construction and testing with atomic modules i.e. modules
at the lowest level of the program structure. Because modules are integrated from the bottom up,
processing required for the modules subordinate to a given level is always available and the need
of stubs is eliminated.

5.2.4BLACK-BOX TESTING

Black-box testing is a method of software testing that tests the functionality of an application as opposed
to its internal structures or workings.
The system is tested just to assure whether it is meeting all the expectations or requirements from it,
tester is not concerned with the internal logic of the module or system to be tested. Some inputs are
given to system and it isobserved whether the system is working as per the client's requirements or not
or according to the requirements specified in SRS document. Specific knowledge of the application's
code/internal structure and programming knowledge in general is not required.
Test cases are built around specifications and requirements, i.e., what the application is supposed to do.
It uses external descriptions of the software, including specifications, requirements, and designs to
derive test cases. These tests can be functional or non-functional, though usually functional. The test
designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the
test object's internal structure. This method of test can be applied to all levels of software
testing: unit, integration, functional, system and acceptance. It typically comprises most if not all testing
at higher levels, but can also dominate unit testing as well. Black box testing or functional testing is used
tocheck that the outputs of a program, given certain inputs, conform to the functional specification of
the program. The term black box indicates that the tester does not examine the internal implementation
of the program being executed
5.2.5 WHITE-BOX TESTING
A software testing technique where by explicit knowledge of the internal workings of the item being
tested are used to select the test data. Unlike black box testing, white box testing uses specific
knowledge of programming code to examine outputs. The test is accurate only if the tester knows what
the program is supposed to do. He or she can then see if the program diverges fronm its intended goal.
White box testing does not account for errors caused by omission, and all visible code must also be
readable.

Contrary to black-box testing, software is viewed as a white-box, or glass-box in white-box testing, as

the structure and flow of the software under test are visible to the tester. Testing plans are made
according to the details of the software implementation, such as programming language, logic, and
styles. Test cases are derived from the program structure. White-box testing is also called glass-box
testing, logic-driven testing or design-based testing. There are many techniques available in white-box
testing, because the problem of intractability is eased by specific knowledge and attention on the
structure of the software under test.
 Chapter 6
CONCLUSION

6.1CONCLUSION

Now a day's there is a big demand of different types of applications, which is because IT has become the
main part of our New World. There is a big need of different applications. People want application for
every specific task from work to entertainment. We have developed the application Weather
WebApp which works easy on any given web browser.

The application has been tested and found to be working as per the given criteria. It can be safely
concluded that the application possesses a highly efficient UI system and is working properly and
meeting to all the requirements of the user. The application gives the user maximum flexibility in the
typesof touch and other device movements.

6.2 FUTURE SCOPE

Every project whether large or small has some limitations no matter how diligently
developed. In some cases, limitations are small while in other cases they may be broad also. The new
system has got some limitations. Major areas where modifications can be done are as follows:

Our system does not have weather information for foreign countries or cities.

There is no provision for complaint handling so further it can be added.

 BIBLOGRAPHY

http://www.w3schools.com

http://www .stackoverflow.com

http://wikipedia.com