Scribd
Upload
742 views4 pages

Data Acquisition - Weather Monitoring System

The document describes the requirements for a weather monitoring station system. It must measure wind speed and direction, temperature, barometric pressure, and humidity. It must also calculate derived values like wind chill. The system uses sensors to collect data and displays it along with recording high and low values over 24 hours. The system is bounded to use a PC or handheld computer with sensors, a clock, display, and keypad for user input. Classes are defined to represent the time/date, temperature, pressure, and humidity sensors that interface with the hardware sensors. The system architecture will either involve synchronizing autonomous actor classes or using time-frame based processing.

Uploaded by

Halamathi Habibo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
742 views4 pages

Data Acquisition - Weather Monitoring System

The document describes the requirements for a weather monitoring station system. It must measure wind speed and direction, temperature, barometric pressure, and humidity. It must also calculate derived values like wind chill. The system uses sensors to collect data and displays it along with recording high and low values over 24 hours. The system is bounded to use a PC or handheld computer with sensors, a clock, display, and keypad for user input. Classes are defined to represent the time/date, temperature, pressure, and humidity sensors that interface with the hardware sensors. The system architecture will either involve synchronizing autonomous actor classes or using time-frame based processing.

Uploaded by

Halamathi Habibo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Data Acquisition: Weather Monitoring Station

11.1 Inception
Our Weather Monitoring System is a simple application, encompassing only a
handful of classes. Indeed, at first glance, the object-oriented novice might be
tempted to tackle this problem in an inherently non-object-oriented manner by
considering the flow of data and the various input/output mappings involved.
Requirements for the Weather Monitoring
Station
This system shall provide automatic monitoring of various weather conditions.
Specifically, it must measure the following:
■ Wind speed and direction
■ Temperature
■ Barometric pressure
■ Humidity
The system shall also provide these derived measurements:
■ Wind chill
■ Dew point temperature
■ Temperature trend
■ Barometric pressure trend
The system shall have a means of determining the current time and date, so that it
can report the highest and lowest values of any of the four primary measurements
during the previous 24-hour period.
Defining the Boundaries of the Problem
We begin our analysis by considering the hardware on which our software must
execute. This is inherently a problem of systems analysis, involving manufacturability
and cost issues that are far beyond the scope of this text. To bound our problem and
thus allow us to expose the issues of its software analysis and design, we will make
the following strategic assumptions.
■ The processor (i.e., CPU) may take the form of a PC or a handheld device.
■ Time and date are supplied by a clock.
■ Temperature, barometric pressure, and humidity are measured via remote
sensors.
■ Wind direction and speed are measured from a boom encompassing a wind vane
(capable of sensing wind from any of 16 directions) and cups (which advance a
counter for each revolution).
■ User input is provided through a keypad.
■ The display is an off-the-shelf LCD graphic device.
■ A timer interrupts the computer every 1/60 second.
The Deployment Diagram for the Weather Monitoring System

One responsibility of our time and date class must therefore include setting the date
and time. Carrying out this responsibility requires a new set of services to set the
time and date, which we provide via the operations setHour, setMinute,
setSecond, setDay, setMonth, and setYear.
We may summarize our abstraction of a time/date class as follows.
Class name:
TimeDate
Responsibility: Keep track of the current time and date.
Operations:
currentTime
currentDate
setFormat
setHour
setMinute
setSecond
setMonth
setDay
setYear
Attributes:
time
date
The TimeDate LifeCycle

The class Temperature Sensor serves as an analog to the hardware


temperature sensors in our system. Isolated class analysis yields the following first
cut at this abstraction’s outside view.
Class name:
Temperature Sensor
Responsibility: Keep track of the current temperature.
Operations:
currentTemperature
setLowTemperature
setHighTemperature
Attribute:
Temperature
We can express our abstraction of the barometric pressure sensor in the following
specification.
Class name:
Pressure Sensor
Responsibility: Keep track of the current barometric pressure.
Operations:
currentPressure
setLowPressure
setHighPressure
Attribute:
Pressure
Our abstraction of the humidity sensor can be expressed in the following
specification.
Class name:
Humidity Sensor
Responsibility: Keep track of the current humidity, expressed as a percentage of
saturation from 0% to 100%.
Operations:
currentHumidity
setLowHumidity
setHighHumidity
The Architecture Framework
In data acquisition and process control domains, we might follow many possible
architectural patterns, but the two most common alternatives involve either the
synchronization of autonomous actors or time-frame-based processing.
The Architecture of the Weather Monitoring System

You might also like