Data Design v2.0 (updated)

This is most updated data design after some discussion among fmemf group members.

ERD v2.0 (click to view enlarged image)

Some new entities have been added including new attributes for each entity. Business rules and entity attributes is defined as below:

Business Rules:

===========

1. A target may has many control data, a control data only belongs to one target

2. A sensor node can monitor one and only one target.

3. A target may has many status data

4. A target may has many abnormal events

5. A sensor node may has many sensors

6. A sensor belongs to one sensor type

7. An area may has many targets

Table/entities structure:

=================
target (t_id, t_name, t_desc, t_xpos,t_ypos, start_time, duration, s_node_id, a_id)
sensor_node( s_node_id, s_node_desc)
control_data( c_id, t_id, s_type_id, max_val, min_val, avg_val, upper_bound, lower_bound)
sensor_type( s_type_id, s_type_name, data_type)
sensor(s_id, s_type_id, s_node_id)
abnormal_event(event_id, d_id, t_id, data_type)
area( a_id, image1_path, image2_path, a_desc)

*red colour text is primary key

*blue colour text is reference key

The comment for data design v2.0 is welcome and opened for discussion.