[groupi] Re: Deliverable C TASKS!!
- From: Lorin Tauss <taussl01@xxxxxxxxxxxxxxxxxx>
- To: groupi@xxxxxxxxxxxxx
- Date: Wed, 7 Oct 2009 23:36:17 +0800
Youve got the photos now right???????
On Wed, Oct 7, 2009 at 10:06 PM, Michelle Le <lem04@xxxxxxxxxxxxxxxxxx>wrote:
> Do you know exactly where?? Because I just did a spell check, and there was
> only like one doublespace and another grammar error. Hmmm?
>
> I'll send you the final one tomorrow night, when the Troubleshoot Section
> is
> complete and also when Lorin sends me a photo to put in.
>
>
> Michelle.
>
>
> -----Original Message-----
> From: groupi-bounce@xxxxxxxxxxxxx [mailto:groupi-bounce@xxxxxxxxxxxxx] On
> Behalf Of Beau Trepp
> Sent: Wednesday, 7 October 2009 9:21 PM
> To: groupi@xxxxxxxxxxxxx
> Subject: [groupi] Re: Deliverable C TASKS!!
>
> Michelle. Apparently the user documentation (manual) has some spelling
> errors.
>
> Could you fix these so i can send illya and sam a new version. Thanks.
>
> Michelle Le wrote:
> > Yeah sorry about that. I had a previous appointment and really couldn't
> stay
> > any longer.
> >
> > I'm not coming in during the day, but exactly what time will you be at
> uni
> > tomorrow? If it's late arvo then I can come. Else, maybe you can pass it
> on
> > to someone who lives near uni, and then I'll get it off them when I come
> > home from work.
> >
> > Sorry about that.
> > Michelle
> >
> >
> >
> > -----Original Message-----
> > From: groupi-bounce@xxxxxxxxxxxxx [mailto:groupi-bounce@xxxxxxxxxxxxx]
> On
> > Behalf Of Beau Trepp
> > Sent: Wednesday, 7 October 2009 8:39 PM
> > To: groupi@xxxxxxxxxxxxx
> > Subject: [groupi] Re: Deliverable C TASKS!!
> >
> > What time are you at uni tommorrow?. You left before i came back, so i
> > was unable to give you the filled out acceptance test sheet form.
> >
> > Michelle Le wrote:
> >
> >> Hey guys, here's an update of tasks for Deliverable C. I'm really
> >> sorry there's a lot of dot points. Hope I haven't missed anything. Let
> >> me know if I did.
> >>
> >> - Everyone:
> >>
> >> o *PLEASE SEND IN YOUR TIMESHEET ASAP*. So that the Time Analysis
> >> Report can be done.
> >>
> >> o *Obviously to help everyone else out wherever you can*.
> >>
> >> o *Someone to go over/review documentation/comments in the code.*
> >>
> >> o *Your individual submission for contributions thing.*
> >>
> >> - Michelle:
> >>
> >> o *Test Report. *I'll do as much as I can tonight and send to you all
> >> by the morning for review and feedback and whatnot.**
> >>
> >> o *Acceptance Test Report.* To analyse the surveys and report on it.
> >> I'll do as much as I can tonight and send to you all by the morning
> >> for review and feedback and whatnot.
> >>
> >> o Make a *copy of all the surveys* and to email it to Beau to send to
> >> clients.
> >>
> >> o Wait for Troubleshoot parts from Kia, Beau, Lorin and *update the
> >> User Manual* as appropriate.
> >>
> >> o Field Manual. I'll do this tomorrow night.
> >>
> >> - Beau:
> >>
> >> o *Readme.txt*
> >>
> >> o *Install.txt*
> >>
> >> o *Time Analysis Report.* Beau you might want to ask Rishabh for help?
> >>
> >> o *Troubleshoot. (Mobile Application)* Can you please write any
> >> (solvable) problems/error messages the user might face and how they
> >> can fix it. Please draw a table up with two columns labelled "Problem"
> >> and "Solution". It makes it easier for me to read through, edit, and
> >> format into the User Manual.
> >>
> >> - Lorin:
> >>
> >> o Finish off the *Ethics Checklist*
> >>
> >> o Write a *short summary of how you tested the GPS stuff*
> >>
> >> o *Troubleshoot. (GPS Issues)* Can you please write any (solvable)
> >> problems/error messages the user might face and how they can fix it.
> >> Please draw a table up with two columns labelled "Problem" and
> >> "Solution". It makes it easier for me to read through, edit, and
> >> format into the User Manual.
> >>
> >> o *Send me that photo?* (to update the User Manual).
> >>
> >> - Rishabh:
> >>
> >> o You may want to help Beau with *Time Analysis Report?*
> >>
> >> o *How did you test XML files? *If you did, can you please write a
> >> little summary and please email it to me ASAP.
> >>
> >> o In my test report I'm leaving sections for *"Known Issues" and
> >> "Future Extensions"* or something like that (it was in your notebook
> >> from today). Can you please write for this (because you jotted it all
> >> down in your notebook) and email it to me ASAP.
> >>
> >> - Kia
> >>
> >> o *Write about any testing (if any)* you did besides the official
> >> checklist Xiaohang and myself did, and please email it to me ASAP.
> >>
> >> o *Troubleshoot. (Desktop Application)* Can you please write any
> >> (solvable) problems/error messages the user might face and how they
> >> can fix it. Please draw a table up with two columns labelled "Problem"
> >> and "Solution". It makes it easier for me to read through, edit, and
> >> format into the User Manual.
> >>
> >> - Xiaohang
> >>
> >> o If you have anything to add to the Test Report, please email me.
> >>
> >> Michelle
> >>
> >>
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
Other related posts:
