SE401:33:Meeting Minutes Semester 1

Inter Semester Break - 21st June

Present: James, Lauren, Gill

Discuss our progress with our tool

• Demonstrated our application so far
• Looks like good progress

Discuss what to do next

• Continue with Iteration 3 and perhaps look at doing Yahoo Maps as well
• Good to try Google and Yahoo maps and then compare pros/cons of each
• Could do regular expression support
• Could try think of a new original application

IR feedback

• Mostly good
• Robert likes evaluations of work done

Exams Week 2 - 14th June

Cancelled this week - exams

Exams Week 1 - 7th June

Cancelled this week - exams

Week 12 - 31st May

Present: James, Lauren, Gill

Discuss our progress with our tool

• Discussed the new buttons, side bar and successful dummy code insertion

Discuss future meetings during exam time

• No meetings until after last exam - 15th June

Discuss what to do next

• Inter semester break is time to finish implementation
• Need to get RSS importing and Google maps implemented
• Yahoo pipes - similar work to ours, need to have differences and reasons for our tool
• Finish iteration 2

Week 11 - 24th May

Cancelled this week - project on hold

Week 10 - 17th May

Cancelled this week - updated via email

Week 9 - 10th May

Present: James, Lauren, Gill

Discuss our progress with our tool

• Discussed the Open Source tool "Kafenio" that we found

-Sounds like a good idea to proceed with

-Will read code and gain good understanding

-Should try to edit it and see if we can work with it

• Discussed what we plan to do

-Future iterations not planned yet

-Should do this soon as time is running out

-Will try to get a Google Maps object working in the WYSIWYG view and code generation

Week 8 - 3rd May

Cancelled this week - Gill double booked, updated via email

Week 8 - 2nd May - Second Examiner

Present: James, Lauren, Robert

Discuss what we have done so far for the whole project

• Told Robert about the project in general
• We can report our future progress by emailing Robert when we reach significant milestones or demonstrations

Discuss the Interim Report

• Discuss our Interim report contents page

- Robert would prefer more focus on the Project Specification, Architecture Research

- and less focus on the Project Approach and Iterations/Implementation

- Give an overall context for our XP Stories - add an extra section?

• Need to sort out a way to measure our finished system

- Usability testing with people needs to be sorted out soon as processing can take a while

- Other methods such as heuristics and expert evaluations

Week 7 - 26th April

Present: James, Lauren, Gill

Discuss what we have done so far

• Mid-semester break progress update
• Keep it simple - don't use the complicated open source software we found
• Could use Java since it's familiar and we have to remember it's only a prototype

Discuss our Interim Report contents page

• Happy with what we've got
• Should discuss risk analysis somewhere
• Could plan that each team member focuses on different aspects and refer to each others reports
• Don't use same diagrams

Discuss work separation

• Working together for implementation is fine
• But try to have some separate parts - to show individual work
• Should state who did what

Discuss if summer research is enough for the report

• Have a few good references
• Summer report is good
• Should mention the example tools from the summer report - RoboMaker and MapBuilder

Week 6 - 5th April

Present: James, Lauren, Gill

Discuss what we have done so far

• Gill is happy with stories and plans for mid-semester break

Discuss what to do next

• Try find open source html editor we can extend
• If not start framework from scratch
• We can email contents page for Interim report to Gill to check

• Should ask Robert if he would mind too

Week 5 - 29th March

Cancelled this week - Gill out of town

Week 4 - 22nd March

Present: James, Lauren, Gill

Discuss what we have done so far

• New content looks good.
• Need to change our unit testing measure.
• Plugin architecture would be good for extensability
• Mashup categories can be used to show the scope of our project

Discuss what to do next

• Create more detailed user stories.
• Research how difficult a plugin based architecture would be.
• Decide on what architecture we should use (may not need to decide this week, may be able to make a offline based tool and make it plugin based later).
• Organise Mashup catergories further.
• Make sure we don't encounter too many technical problems straight off

Week 3 - 15th March

Present: James, Lauren, Gill

Discuss what we have done so far

• Project Aims look good
• But we need to define how we will measure the genericness of our tool

Discuss what to do next

• Compare what architectures we could use

- Online vs Offline tool?

- Generic framework vs Application specific?

• Work out pros and cons of each method
• Determine the project style we wish to use (RUP, XP or a hybrid?)
• Look at ways to categorize mashups

- By application or technologies etc

- What things limit or prevent genericness?

Week 2 - 6th March

Present: James, Lauren, Gill

Discuss where to begin with the project

• Find what we are aiming for - what question are we trying to solve
• Make a list of requirements for the system

Week 1 - 1st March

Present: James, Lauren, Gill

Discuss weekly meeting times

• Week 2 meeting will be Tuesday 5:00pm
• Week 3 and onwards will be Thursday 2:00pm-3:00pm

◄ Back