Scripting is complete UPDATE**

UPDATE**

Only left to do now is the objectives when selecting the scenario; otherwise the coding has been put to bed!

:D


______________________________

Hey guys an update on the scripting

Once Joel shares the script in the Defib (yes I can't believe I missed that it wasn't shared when I checked everything a couple of weeks ago), Then I can put the script I've made into the actual correct object.

Then all that remains is a couple of Patient conversations (for scenario's 4-6)
And those test says for the objects that require multiple user's to agree. I'm gonna clean those up to make them useful and not totally confusing as they are now

I'm also gonna make Says from the scenario selector; So that when a scenario is selected that scenario's objects will be sayed llSay(0,"This scenario's objectives are: blah blah and blah").

After those few things I'm practically done. I should be able to get those done on Sunday night. But I will post back here when they are all done to let everyone know.

Peace Out

(Can't believe how close it is now! :D)

User doc - video status

I've just completed capturing the user doc footage.
I've emailed an outline of the footage captured - let me know if I'm missing something.

As part of the user doc (dylan) we will need to outline the 3 stage process for accessing the simulation:
1. Creating an account
2. Obtaining access (request access)
3. Accessing the siumaltion

I've created a access request form and have created some screen caps for the admin user doc. Have a look at these and let me know if there should be any additions.
Dylan I have left the doc fairly un-formatted as i'm not sure how you are going to do these but i reccomend numbering the points and arrows.

That's A Wrap!

Chaddy and I have completed the recording of all of the cutscenes, with extra thanks to Matt for helping us out.

The acting was especially well done, although the same could not be said for the framerates in the videos. But I still have complete faith that the videos will get the point across.

Both Chaddy and I will tackle the editing stages next week, and aim to have them fully completed by the end of the lecture break.

I will have to put all these videos past our coding master Ben, to ensure that they are consistent with the simulations.

Peace Out

Update on the Completion of the scripting ***UPDATE***

UPDATE

Currently I have scenario's 1 -> 4 almost completely finished (barring some of the patient talking and connections for the rest of the module) i have the drugs for scenario 5 almost finished (most are done); And then I just have to do scenario 6 (which is just clicking on the paddles and then clicking the met team button - plus ecg monitor).

I managed to find some heartbeat sounds for the stethoscope in scenario 3 - try them out to see for yourself. Also managed to find a suitable alarm sound for the probe coming loose in scenario 2.

I reckon its really coming together well guys. Great job EVERYONE!!

I should be done in the next couple of days. (I'll keep you guys posted)

----------------------------------------------------------------------------------------------------------------

Hey guys

Just letting everyone know where I'm at so you don't think I've disappeared (of the planet!)

I won't have much time to script over this weekend coz I've gotta play Uncle In-Law (to my Nephew-In-Law's 1st birthday). But I'll try and get some stuff done on Sunday night.
Then I plan to get stuck in (and hopefully finished) Monday/Tuesday (22nd/23rd).

I'll make sure to Update this post (or make a new one) with any updates that are relevant for all to know.

Cheers

Happy Project doing break to all!

llCheers(0,"I can see LSL in my sleep...");

Updates

I have submitted a hard copy of the test plan to Charlynn and would like to congratulate matty for his excellent work on the test plan. I hope everyone has a relaxing and productive lecture break, and I look forward to seeing the final product come together. A lot of hard work has gone into this so it will be very gratifying for everyone when it is done and dusted.

Minutes 16/9/08

TEAM CRITICAL LIFE – Minutes 16/9/08

TEAM MEETING

AGENDA

• Where are we up to on the Test Plan
  
• Where are we up to on the Scripting
  
• Go through Team H's individual review
  

ABSENTEES - NIL

NOTES

• Matty's pretty much got the Test Plan document finished
  
• Luke to do all the video for the User Doc's in the first week of the break
  
• Luke, Dylan and Matty to meet on Tuesday 30th of September to bring all the user doc's stuff together
  
• Dylan to look after the changes to each of the documents
  
• except the traceability matrix (which matty is doing)
  
• Ben to fix up his section 2 of the SRS (the wording in the assumptions/contraints)
  
• Dylan to have all updates to documents by Friday 26th of September and give them to Matty to put
  
• We went through the individual reviews and wrote down what changes need to be made by Dylan
  
  

ACTION

• Matty to get the Test Plan to Luke by Wednesday night
  
• Luke to hand in by Friday
  
• Dylan to have the User Doc's template done by this Friday
  
• Also get stuck into the all document updates
  
• Do scripting Ben
  
• Do Cut - scenes Joel and Chaddy
  
  

NEXT MEETING: - Possibly Tuesday 10:30AM 30/9/08 - TEAM MEETING

--- PLEASE SIGN OFF ON BLOG!!!!!!! ---

Minutes 9/9/08

TEAM CRITICAL LIFE – Minutes 9/9/08

TEAM MEETING

AGENDA

• Individual Review to be done for Friday
• Deadlines for the next couple of weeks
• Discuss what needs to be done over the break
• Discuss the changes that have come about since last Friday's meeting
• Especially from the chat with Blake

ABSENTEES - NIL

NOTES

• Once we get the individual review docs on Friday look over them on the weekend and add what changes need to be made to the changes doc
• Divide up the review one each, talk about what changes need to be made
• Reference the textures used in the SDD
• Wait till we do all the changes
• Updates to the cut scenes and props and costumes (not the actual stuff) to be got/done by the 20 September (Including when you need Dylan's Computer)
• Cut scenes to be actually recorded and done by 3rd of October
• All Scripting to be done by 22nd of September
• All New objects to be done by the 15th of September
• Get the 3 tanks set up asap
• Template for the User Documentation done by the 19th of September
• Final User Docs by October 3rd
• Luke to do the videos, give to Dylan
• Dylan to do the DVD menu and paper based bit
• Test Plan done by the 19th of September
• All Documents updates over the break to be put together by Dylan by the 3rd October
• Updates to flowchart (images) talk about next week
• Organise the user testing for week 10 (once Blake sends us the names)
• Matty send the User Tests to Dylan in the holidays for him to go through
• Also send the unit tests to Ben for him to go through in the holidays (add tests that may have been missed)

ACTION

• See above for all the many actions that need to be taken from this week's meeting
• If Joel/Chaddy have any questions regarding the changes to the scripts (videos especially week 8) see the Module plan (on google docs) it has been changed Or just send Ben an email.
• Everyone do their individual review for Friday's meeting with the other team
• Give Dylan a five minute break.....

NEXT MEETING: - Friday 9:30AM 12/9/08 - TEAM MEETING (INDIVIDUAL REVIEW HANDOVER)

--- PLEASE SIGN OFF ON BLOG!!!!!!! ---

Minutes 5/9/08

TEAM CRITICAL LIFE – Minutes 5/9/08

CLIENT MEETING

AGENDA

• Run through of the clinic as it is now for Client

• Talk about the test plan
• Organise when we need Blake's students

• Blake sign off on changes
• Sort out some technical details with Blake

ABSENTEES - Joel, Charlynn

NOTES

• run through of the clinic was good
• Blake was happy with the look of the current clinic
• youtube help videos load in external browser
• personal log has questions from the case study and ones to do with the simulation itself
• To guide the students thinking
• Blake suggested when max people in simulation is reached you should teleport to the viewing room
• make sure that the family aspect of the patient comes over in the videos
• ie that the wife is worried etc...
• Make the mouth go blue (not the whole face)
• Possible have the whole face go a slightly less dark blue
• Look into the notecards sending to Blake so that he can see the student's discussion and progress
• Blake was overall happy with the look of the User Documentation
• Is also happy for us to do the DVD idea with the user docs
• Blake suggested that we make clear the collaborative function of the virtual clinic since it is unlike real life (ie waiting for all to make a decision instead of just one person doing it)
• Blake suggested that we have an overall comments section in the User Acceptance Tests document that we showed him
• When do we need the students for User Acceptance Tests
• week 10 would be good (6 - 10 October)
• Blake to nominate some nursing students for the user acceptance testing
• Changes/Additions to the oxygen tanks
• Make the suction tank yellow (use in the coughing scenario - make heart drop) oxygen tank white; air tank black
• Blood pressure cuff needs to be made
• Luke and Ben spoke with Blake at the end of the meeting
• Many small additions to be made to the clinic to make it more alive

ACTION

• Luke to look into the notecard sending (for Blake)
• Ben to make a list of changes to be made to the videos/simulation (from the talk at the end with Blake)
• Bring to next Tuesday's meeting and discuss with team
• New objects will need to be made
• Blake to email us with list of drugs that are applicable to the week 8 scenario
• Also email us about the students that we require to test our simulation
• Matty make changes to the User Acceptance Test
• All to do your individual reviews for next friday

NEXT MEETING: - Tuesday (After Lecture) 9/9/08 - TEAM MEETING

--- PLEASE SIGN OFF ON BLOG!!!!!!! ---

Updates on the Scripting...

Hey all; Been doing some late night updates :S

This is whats been done:

• Oxygen tank only functions (as it used to) in scenario 4; since that is when it is meant to be used
• Therefore scenario 1 is totally complete, all the user needs to do is look at the patient, click on the patient to check him out; and finally turn the alarm off and move on (personal log and so on)
• Scenario 2 is almost done; I have the IV stand and Mask moving into the correct positions since they need to be on the patient. All I need is to adapt the coughing (maybe a slightly different version of the coughing - more a asthmatic hard to breathe sound as per the case study) and the blue face/patient talking stuff
• scenario 4 is done basically (since its the oxygen tank one
• scenario 3 need to do the bleeding from the mouth stuff/ more talking patient stuff
• scenario 5/6 don't have that much to do besides different talking from the patient and turning the other bits of equipment on
  

So yeah its definitely taking on a more complete feel since the scenario's are coming(ish) together.

Also I was able to fix that problem of the chest not responding to a change in scenario (dam timer events) by using a trick in the scripting. I've tested the chest heaps of times (and since its the way the arm shaking works as well - and they always have responded correctly :D) and its responded correctly each time :D. I also reworked the monitor thing so that it responds correctly to the scenarios (and fits with the rest of the scripts so far).
Also as I eluded to above when you left click the different objects they will say something (in scenario's 1,2,4 at the moment). When you click the patient's head he cycles through 2 quotes in scenario 1 at the moment (will expand for further scenarios) - I did this for the parts where the case study says "the patient is anxious and talkative and so on".
Also left clicking the chest says "chest is pumping fast" - this feature means that the user can appear to examine the different parts of the patient both visually, audibly, and by text prompt

Cheers

From your underground scripter... :D

Minutes 2/9/08

TEAM CRITICAL LIFE – Minutes 2/9/08

TEAM MEETING

AGENDA

• Go through the client meeting what needs to be done

• What needs to be done this week

• Go over the change requests to be made

ABSENTEES - NIL

NOTES

• Dylan to get the User Doc done ASAP, Blake needs to see it on Friday.
• Need to discuss about the DVD section.
• Get the template done and sent out ASAP

• Present it in the client meeting (discuss DVD idea).

• Put up the meeting details on the blog (they are on the team calendar)

• Put transitions into the ends of both the videos and scenarios to guide the user to the next part of the clinic (module)
• example at the end of the cut-scene a screen saying "Next go to Simulation 1"

• Get into the cut scenes ASAP (get stuck in before the break) (Joel and Chaddy)

• Get the codes (scripts) done by this week (Ben)

• Luke has contacted Blake for 2 or 3 nursing students to do usability test (Dylan and Matt)

• This Friday Meeting:

• Second Life video;
• run through of the documentation (and DVD discussion);
• run through of usability test (organise the usability test);
• sign off on changes;
• talk about the oxygen level rules with Blake.

• Test Plan review for next week (get done for the weekend - due officially in week 9) (Matt)
• Make a flowchart that can be used as a texture in SL that gives the user an order for using the module (videos and simulations) (Ben - plan, Dylan - Beautification)
• Need to make formal change docs for the changes that need to be made to the functional requirements to be signed off on Friday (sent out tonight in email)

ACTION

• What needs to be done this week (and beyond)

• Dylan
• User Doc done ASAP (Template) need for Friday meeting (As above)
• Beautify the flowchart
• Matt
• Test plan complete for meeting next week - we will go through a review of whats been done
• Also need the usability tests for Friday meeting
• Luke
• Finish formal change document for the functional requirement changes being made
• Send out in email tonight
• To be signed off on Friday meeting
• Ben
• DO THE CODES!!!! Scripts to be finished (.....) by the end of the week
• Do the plan for the flowchart and send to Dylan
• Joel and Chaddy
• Do the Cut - scenes (Videos)
• Beautify the subtitles
• Everyone
• Do your Individual Review of another team's Document (find info on what document to be done in previous minutes)
• This is Due on Friday of next week in the meeting (with the other team)

NEXT MEETING: - Friday 9:30AM 5/9/08 - CLIENT MEETING

--- PLEASE SIGN OFF ON BLOG!!!!!!! ---