=====g1=====not improved
=====g2=====

We Added the ability for the SPO2 monitor to accept message 45, and then it
runs after receiving it.
This was done by modifying the g2SPO2Monitor.java, and updating the
Createg2SPO2Monitor.xml to accept message 45

g2GUI.java was updated to show the alert box when receiving the blood sugar
message, and the panel was updated to show the reading.
 The Createg2GUI.XML has been updated to accept message 42.

The report (g2rpt.doc) has been updated as well.
Changes include:
updating UML diagrams to show the messages we added (42 for GUI, 45 for
SPO2)
updated source code for g2GUI.java
updated source code for g2SPO2Monitor.java
updated Createg2GUI.XML
updated Createg2SPO2Monitor.xml
added new screenshots showing: the new panel with blood sugar, the
SPO2Monitor accepting message 45 (user profile), and the GUI receiving
message 42 (blood sugar alert)
updated the revision history to v6 noting these changes.



John Wilt
=====g3=====
We updated the source code to reflect the changed made. System does not send
an unexpected msg26.  Monitor waits for msg 45 and once the profile is
recieved, begins processing msg 31's.

=====g4=====

The report was changed to include the modified source code. Changes to the
source code were:
  -corrected the no low blood pressure alert bug
  -corrected null pulse return
  -corrected a previously unnoticed bug that double returned systolic value
The revision history was also changed to reflect these modifications.

Josh Hauenschild

=====g5=====OK
OK
=====g6=====
Attached WORD doc file is the revised final project report from group 6
by Luke Weng and Bin Gao. Added contents in the report including a
revision history, two modified and highlighted XMLs, and two revised
source code java files.

The final report is revised with new bookmarks and updated Table of
Contents with its new associated page numbers for you to quickly and
easily view the document.

Thank you and have a great summer,
Luke Weng

-----

Usually g6bloodsugar will first receive message 45 (user
profile).  Then the bloodsugar reading will be
received, and g6bloodsugar reacts to that.  The
interaction between g6bloodsugar and g6kb is internal
(within the coarse grained component).  I see what
you are doing.  You divide the responsibilities between
g6bloodsugar and g6kb.  I can accept that, as long as
SOMEONE would received message 45 and store information
(user profile) SOMEWHERE.  If g6kb receives it, that is
fine.  But it needs to send the information to g6bloodsugar,
because it is g6bloodsugar that sends out the alert message
which should contain user-id, and user-id comes from
message 45 user profile.

Prof. Chang

On Thu, 29 Apr 2010 big5@pitt.edu wrote:

> Hi,
>
> We have two fine grained components, g6bloodsugar and g6kb. Component g6kb
> sends new Msg160(Thresholds) to component g6bloodsugar after receiving
> Msg45(User Profile). Component g6bloodsugar sends Msg42(Blood Sugar Alert)
> to server after receiving Msg41(Blood Sugar Reading). They have separate
> responsibilities. Therefore, g6bloodsugar doesn't response to Msg45, but
> g6kb will do it. I'm not sure the comment, G6 should run after receiving
> Msg45(User profile), means which component doesn't response to Msg45.
> Could the current TA give more detailed comment before we revise the code?
>
> The previous version has just one coarse grained G6 component responding
> to both messages. We do need a clear explanation of the problem and the
> TA's notion of the proper implementation in order to pick a close version
> to revise. Response soon so we can act quickly.
>
> Regards,
>
> Bin Gao
=====g7=====

Professor Chang and Yao Sun,

I have attached the resubmission of our files and report. The only thing we
changed was the date formatting. You stated that we had hardcode in our
results, but that was because you were using the wrong code. I thought you
had the correct/updated versions of our code, but apparently not. If you
check my original final report the source code was in there, so that is our
proof that we did have what you wanted prior to the submission. I have
reattached the report and the files you need with the date formatting
working correctly. Please let me know if anything is missing. Thank you.

 

 

Jake Gress
=====g8=====OK
OK
=====g9a=====
Mateen Firoz