Prepared by :
Ahmad Mujahid Ubaidilllah Zakaria
Weather Station Case Study
Overall system organization Weather Station
Weather information system
Weather data archive
WS1 WS2 WS3 WS.. WSn
Satellite information
Weather radar
information
System context for the weather station
Weather station characteristics
Must be self-contained and completely autonomous Integral power supplies and power generation
Satellite communications
Ruggedized to tolerate extreme weather
Self-testing
May exist in several version for different types of deployment
o Highland areas based on wind power
o Desert areas based on solar power
Remote control to support autonomous operation
Dynamic software re-configuration
Installed instruments
Anemometer – wind speed measurement
Barometer – air pressure measurement
Ground and air thermometers
Rain/precipitation gauge
Sunshine gauge
Visibility gauge
Essential system functionality
Collect weather information from instruments at regular intervals
Transmit this information, on request, to the weather information system over the satellite link
Store information if communications are not available
Monitor external conditions and shut down power generation/instruments if threat of damage from extreme weather
Run regular diagnostic tests to assess overall health of system
High Level Software Architecture
Weather Station System Software
Embedded software but not real-time in the sense that rapid reaction to events is required.
Developed using an object-oriented approach Object Oriented approach associates objects with
the physical entities in the system e.g. Weather data collection instruments Power supply and generation Communications
Data may be stored as objects No requirement for large-scale database
Each weather station is battery-powered and must be entirely self-contained – there is no external power or network cables available. All communications are through a relatively slow speed satellite link and the weather station must include some mechanism (solar or wind power) to charge its batteries. As they are deployed in wilderness areas, they are exposed to severe environmental conditions and may be damaged by animals. The station software is therefore not just concerned with data collection. It must also:
1. Monitor the instruments, power and communication hardware and report faults to the management system.
2. Manage the system power, ensuring that batteries are charged whenever the environmental conditions permit but also that generators are shut down in potentially damaging weather conditions, such as high wind.
3. Allow for dynamic reconfiguration where parts of the software are replaced with new versions and where backup instruments are switched into the system in the event of system failure.
Weather Station System Software
Creating New Project
1. Click menu
2. New project
3. Choose save file location.
Ex: C:\Users\Desktop\SOFTWARE ENGINEERING\EA
New Project
• Tick :
i. Requirement
ii. Use Case
iii. Domain model
iv. Class
v. Component
• Click OK
1
2
New Project
• Project browser upper right
Create Requirement Model
Functional Requirement
• Double click
• delete all the automatically generated package by right click and choose delete
Click to view/
expand
Adding Package
1. Double click on functional requirement
2. Click on “Package”
3. Click anywhere on diagram view
4. Fill meaningful name for the package.
5. Click OK button.
5
1 2
3
4
Adding requirement into functional requirement package
Click on REQ01- Collecting Weather Data
1. Click “Requirement”
2. Click anywhere on diagram view
3. Fill meaningful name for the requirement
4. Click OK button
5. REPEAT THE SAME STEP UNTIL ALL THE REQUIREMENT IS COMPLETE
1
2
3
4
Complete Example of functional Requirement Diagram.
Creating Non-Functional Requirement
1. Click on to expand
2. Click on “Non-Functional” to expand
3. Double click on Non-Functional Requirements. There will be some package auto generated.
4. Right Click on each of generated package and choose DELETE
Add Package
a. Click Package
b. Click anywhere in the diagram view
c. Fill in meaningful name for package
d. Click OK button
a
b
c
d
Adding Package on Non-Functional Requirement Diagram
Click
Example Final view of Requirement Model Diagram
Creating The Use Case Model
Relationships:
Association relationship: to show the relationship between a
use case and an actor
There are three types of relationships between use cases:
• includes relationship
• extends relationship
• generalization relationship
There is only one relationship allowed between actors =
generalization relationship
Create Use Case Model
To Add Actor
1. Click on “Actor”
2. Click anywhere in the diagram
3. Put Meaningful name
4. Click OK
4
1
2
3
Create Use Case Model
To Add Use Case
1. Click on “Use Case” 3. Put Meaningful name
2. Click anywhere in the diagram 4. Click OK
4
1
2
3
Create Use Case Model
To Add Use Case
1. Click on “Association” relationship/ Choose suitable relationship in Use Case Relationship Panel
2. Click and Drag the pointer/curser from actor to the suitable use case
1
2
Complete of Use Case Diagram
2
1