Weather Station Case Study. Prepared by : Ahmad Mujahid Ubaidilllah Zakaria

Size: px

Start display at page:

Download "Weather Station Case Study. Prepared by : Ahmad Mujahid Ubaidilllah Zakaria"

Shanon Parker
5 years ago
Views:

1 Weather Station Case Study Prepared by : Ahmad Mujahid Ubaidilllah Zakaria

2 Overall system organization Weather Station WS1 WS2 WS3 WS.. WSn Satellite information Weather information system Weather radar information Weather data archive

3 System context for the weather station

4 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

5 Installed instruments Anemometer wind speed measurement Barometer air pressure measurement Ground and air thermometers Rain/precipitation gauge Sunshine gauge Visibility gauge

6 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

7 High Level Software Architecture

8 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

9 Weather Station System Software 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.

12 Creating New Project 1. Click menu 2. New project 3. Choose save file location. Ex: C:\Users\Desktop\SOFTW ARE ENGINEERING\EA

13 New Project 1 Tick : i. Requirement ii. Use Case iii. Domain model iv. Class v. Component Click OK 2

14 New Project Project browser upper right

15 Create Requirement Model Functional Requirement Click to view/ expand Double click delete all the automatically generated package by right click and choose delete

Adding Package 2 4 1 1. Double click on functional requirement 5 3 2. Click on Package 3.

16 Adding Package Double click on functional requirement Click on Package 3. Click anywhere on diagram view 4. Fill meaningful name for the package. 5. Click OK button.

17 Adding requirement into functional requirement package 1 3 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 2 5. REPEAT THE SAME STEP UNTIL ALL THE REQUIREMENT IS COMPLETE 4

18 Complete Example of functional Requirement Diagram.

Creating Non- Functional Requirement a 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.

19 Creating Non- Functional Requirement a 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 d c Add Package a. Click Package b. Click anywhere in the diagram view c. Fill in meaningful name for package d. Click OK button b

20 Adding Package on Non-Functional Requirement Diagram Click

21 Example Final view of Requirement Model Diagram

22 Creating The Use Case Model

23 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 1 3 2 4 To Add Actor 1. Click on Actor 2.

24 Create Use Case Model To Add Actor 1. Click on Actor 2. Click anywhere in the diagram 3. Put Meaningful name 4. Click OK

Create Use Case Model 1 3 2 4 To Add Use Case 1.

25 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

26 Create Use Case Model 1 2 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

27 Complete of Use Case Diagram 1 2

An object-oriented design process. Weather system description. Layered architecture. Process stages. System context and models of use

An object-oriented design process Process stages Structured design processes involve developing a number of different system models. They require a lot of effort for development and maintenance of these