System Sequence Diagrams (View History/Send Message)
0 views
Skip to first unread message
Cory Rosenwald
Feb 3, 2013, 8:27:45 PM2/3/13
to Info355
Hey guys,
I'm working on putting together the SSDs for the use cases mentioned in the subject. I wanted to get some feedback before creating the actual diagram in Vizio, and also have a few questions that I need to clarify before continuing if anybody is aware of the answer.
Here is the information so far:
#1
Case: View History
Actor(s): Physician
System: Sandia Patient Data Server
Input: viewHistory (patientName)
Output: Patient History
Output Additional Data: Patient History: Date, Incident ID, Details
Questions:
Should we also create a second diagram with Patient as the actor?
The only difference is that they would only be able to view their specific history, which would change the input. Currently, view history requires a patient name as input to bring up their history. I'm not sure what data the patient would have to input, if anything, as an identifier to view their personal data.
Also, should we use a patient ID instead for physicians to input? In the case that there are two John Smith's or something in that vein.
Another thing I'm unsure about is the structure of the server(s). Is there one all-encompassing server that handles all functions, or, like I listed above, is there a specific server that house patient data, and another for patient messaging, etc.?
#2
Case: Send Message to Patient
Actor: Physician
System: Sandia Message Alert Server
Input: recordMessage (patientName, text, audio)
Output: Send Message
Output Additional Data: Send message from physician to patient containing text and/or an audio file.
Overall, I'd like to know if you guys are OK with the terms I used for the inputs. The way they are labeled in the book, it almost seems like they are to be a function in the code at some point, though I'm not sure if this is true. Also, if there is any incorrect information, missing data, or anything wrong above please let me know.
Thanks for your help!
Cory
I'm working on putting together the SSDs for the use cases mentioned in the subject. I wanted to get some feedback before creating the actual diagram in Vizio, and also have a few questions that I need to clarify before continuing if anybody is aware of the answer.
Here is the information so far:
#1
Case: View History
Actor(s): Physician
System: Sandia Patient Data Server
Input: viewHistory (patientName)
Output: Patient History
Output Additional Data: Patient History: Date, Incident ID, Details
Questions:
Should we also create a second diagram with Patient as the actor?
The only difference is that they would only be able to view their specific history, which would change the input. Currently, view history requires a patient name as input to bring up their history. I'm not sure what data the patient would have to input, if anything, as an identifier to view their personal data.
Also, should we use a patient ID instead for physicians to input? In the case that there are two John Smith's or something in that vein.
Another thing I'm unsure about is the structure of the server(s). Is there one all-encompassing server that handles all functions, or, like I listed above, is there a specific server that house patient data, and another for patient messaging, etc.?
#2
Case: Send Message to Patient
Actor: Physician
System: Sandia Message Alert Server
Input: recordMessage (patientName, text, audio)
Output: Send Message
Output Additional Data: Send message from physician to patient containing text and/or an audio file.
Overall, I'd like to know if you guys are OK with the terms I used for the inputs. The way they are labeled in the book, it almost seems like they are to be a function in the code at some point, though I'm not sure if this is true. Also, if there is any incorrect information, missing data, or anything wrong above please let me know.
Thanks for your help!
Cory
Ariel Kirkwood
Feb 4, 2013, 12:52:16 PM2/4/13
to Cory Rosenwald, Info355
Responding to your questions:
For #1-
1) If it isn't too much trouble to create a second, slightly modified diagram from the patient's perspective, go for it. If it requires a ton of time, stick to just the physician's one.
2) I would say that Patient name should be sufficient, one could imagine the system returning multiple results if a name matches multiple patients (which the physician would then choose whichever one he meant). That way, we don't inconvenience the user (the physician) by requiring them to remember patient IDs.
3) I haven't quite read up on SSDs, how does the answer to your question affect how your SSD would look? I would venture a guess as "pretend the system is one big black box from the perspective of how servers are divided up", but if that makes things more difficult and a more specific answer would be better, I'd say try posting to the discussion board and ask the professor.
For #2-
1) I think everything looks good- if you're getting really technical here and you need to specify parameters (the "(patientName, text, audio)" part), I would suggest making "audio" a more generalized "attachments" parameter instead. That way, you allow for the possibility of multiple attachments, whether they are audio files or data files or whatever would need to be sent.
https://trello.com/board/info-355-term-project/50ff0f700f267b543600077a
> --
> You received this message because you are subscribed to the Google Groups "INFO 355 Team 3" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to info355team3...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
For #1-
1) If it isn't too much trouble to create a second, slightly modified diagram from the patient's perspective, go for it. If it requires a ton of time, stick to just the physician's one.
2) I would say that Patient name should be sufficient, one could imagine the system returning multiple results if a name matches multiple patients (which the physician would then choose whichever one he meant). That way, we don't inconvenience the user (the physician) by requiring them to remember patient IDs.
3) I haven't quite read up on SSDs, how does the answer to your question affect how your SSD would look? I would venture a guess as "pretend the system is one big black box from the perspective of how servers are divided up", but if that makes things more difficult and a more specific answer would be better, I'd say try posting to the discussion board and ask the professor.
For #2-
1) I think everything looks good- if you're getting really technical here and you need to specify parameters (the "(patientName, text, audio)" part), I would suggest making "audio" a more generalized "attachments" parameter instead. That way, you allow for the possibility of multiple attachments, whether they are audio files or data files or whatever would need to be sent.
https://trello.com/board/info-355-term-project/50ff0f700f267b543600077a
> You received this message because you are subscribed to the Google Groups "INFO 355 Team 3" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to info355team3...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Ariel Kirkwood
Feb 4, 2013, 12:56:46 PM2/4/13
to Cory Rosenwald, Info355
Oops, I forgot to mention (the reason I posted the Trello link at the bottom of my message)
Cory - when you get a chance, could you take a look at the two cards in the Review list on Trello and check off the boxes for you if you approve of the work done so far? If you've got comments, just put them on the individual cards.
0 new messages