SE401:33:Meeting Minutes Semester 2

Week 6 - 20th August

Present: James, Lauren, Gill

Discuss the final report

• Don't have to write in 3rd person if it makes it clumsy
• Can discuss the implementation depending on what we decide are the important outcomes

- if the process is an important finding then discuss how you did it

- if the product is more important then show the tool and discuss why we did what

• Can use screenshots where relevant, eg. UI description.
• Look at last years reports

Discuss the "public.html" folder problem

• Email Richard and see what he can do
• If needed email Gill

Discuss the presentations

• Can invite Gill to our practices, even if not polished

Week 5 - 13th August

Cancelled - No significant progress

Week 4 - 6th August

Present: James, Lauren, Gill

Discuss our evaluation progress

• Evaluation process is complete
• Should write up formal evaluation process - aims, methods, findings etc

Discuss our implementation

• Implementation is pretty much finished
• AFS has been down and preventing any further progress anyway
• Gill thinks we have done enough and should try present it in the best possible way
• May fix tiny things for presentation/conference

Discuss final report

• We can send Gill our contents page for checking
• Think of it as writing for a part 4 student who will continue your work
• Only need to put things relevant for our target audience
• Think of it as completely separate from the interim
• Code details/read me will all go in the compendium

Discuss what to do next

• Work on final report structure
• Final report will help poster and its good to reuse

Week 3 - 30th July

Cancelled - Gill not here

Week 2 - 24th July - Second Examiner

Present: James, Lauren, Robert

Discuss our tool

• Talked about how it went since the last time we met
• Demonstrated our tool and what functionality we added to it
• Robert seemed happy with what we've done

Discuss what to do next

• Could do Cognitive Dimensions of our tool and another to compare the differences
• Fix up small usability issues found by usability heuristics
• Think about a scenario to demonstrate our tool with

- should be short and quick to demonstrate

- should be visual and show the power of the tool

Presentations

• Robert is happy to sit in on rehearsal presentation
• Robert is happy to look at contents pages for final report

Week 2 - 23rd July

Present: James, Lauren, Gill

Discuss what changes we made

• Differences between Yahoo and Google maps

- Yahoo has better location estimation

- Google has better NZ road maps

• Regular expressions are common but difficult to make user friendly

- probably some good applications already built

- possible future work for formatting options

Discuss the findings of our Usability Evaluation

• List of possible improvements
• Good for report to list and say what we fixed and future work
• Attempt to fix small problems and leave rest for future
• Try a different evaluation to perhaps identify different problems

- Cognitive Dimensions

- Good to have multiple evaluations

- Draws from knowledge of 2 other courses

Week 1 - 16th July

Present: James, Lauren, Gill

Discuss our progress with our tool

• Demonstrated our application so far
• Implementation is done if we can confidently say it is

Discuss what to do next

• Evaluate and improve any problems we find (dialog boxes etc.)
• Try make intuitive dialogs - specifically formatting data dialog
• Industry officials are impressed by intuitive interfaces
• Think about presentations (poster, conference etc)
• Can use the summer project for poster etc
• Meet with Robert & sell what we've done

◄ Back