Date	17/09/10
Away	-
Agendas Raised	How much detail should the technical manual include without being redundant How Jun and Phil are going with their demos Which technical diagram should be done first. I.e start with use case then move onto other diagrams
Things to look into further	At the moment there isnt much to look into further because we are trying to get a base to work from with the demos that Jun and Phil are working on
Tasks assigned to individuals	Phil – again continuing with his demo, he feels like he is making some progess. Just came up with a better idea that incorporates all the ideas that have been raised during over group meetings Jun – again still continuing with his demo, he too is making progress and giving it his full attention while he can Allen – will elaborate on the class diagram he did early in the session by adding more detail to it. He will also do a rough overview use case of the system Jernej – is going to do use case and activity diagrams on a few of the basic functionality within or programs user interface Tim – will add descriptions to the diagrams created by Jernej is a table format.
What should be done by next meeting	Hopefully most of the above tasks are completed by our next meeting and the technical manual is under way and starting to take shape.
Summary	Overall everyone knows what they are required to do and are willing to do it while they can put it as their main focus. This are moving forward in terms of documentation however for the program a lot hinges on which demo we decide to use out of Jun and Phil's.