First meeting Since break

Date	8/12/10
Away	-
Agendas Raised	·         Where we go from here ·         A target we would like to be at before Uni starts next year ·         Setting up an SVN
Tasks assigned	Allen ·         Look into possible ways to store the database Everyone Else ·         Work together to get the rope looking more realistic ·         Try and make the rope have certain limitations ·         Work out ways to store the rope to help Allen
Summary	Overall  this wasn’t a very long meeting, only for an hour but many topics were raised as to what we want to be completed by the time Uni resumes next year and what we should tackle first in order to complete this. Other ideas were raised as to possible ways to continue on what we have done so far in terms of using Jun’s demo to continue his work. Or use Jun’s demo as a base and work out ways to continue from here in terms of storage and representation of the rope.

Although as a group we have having a break to after exams so people can study and put their focus on their other subjects. Allen and I have been working together to produce the website to put onto the web space provided by the uni.

Before we split at a group we brainstormed ideas, layout and content that would look good on the website. All Allen and I did was put these ideas into appropriate design layout and a nice and well presented website for our project. At the moment there is little content but we will continue to keep this website up to date and add more content as well go along.

Here is a link to the website:
http://zim.cs.uow.edu.au:50321/~321lm01s/

Last group meeting for this semester

Date	18/10/10
Away	Jernej
Agendas Raised	·         Design layout of the website ·         Information needed for the website ·         Possible graphics for the website
Tasks assigned to individuals	Allen ·         Work on the website Tim ·         Graphics for the website Phil ·         When he gets time continue with his demo
Summary	Today was a simple and quick meeting and the last one for this semester so people can focus on other subjects and their exams. The meeting was also quick because there was not much to talk about. We had a simple discussion about what the website should look like and what would be needed to make the website look professional.

Date	15/10/10
Away	Jun , Jernej
Agendas Rasied	·         Things to add to the documentation ·         Possibility of a better documentation template
Tasks assigned to individuals	Jun ·         Continue to work on his XNA to winform import process Allen ·         Think about possible ways to implement the website Phil ·         Continue to work on his demo Jernej ·          Will help Allen with the implementation of the website Tim ·         Help Allen with the website, the design layout and possible graphics
What should be done by next meeting	Hopefully by next meeting everyone can get together and have a better idea of how to implement the website and a possible design target they want the website to look like
Summary	Today was a fairly simple meeting it was mainly about getting all the work of everyone and putting them within the required documentation that was due today. Everyone seems happy with the work we submitted, some sections where left out but this was because we haven’t reached that part in the project or we just didn’t have enough time to get around to it.

Date	11/10/10
Away	-
Agends rasied	·         What is required within the technical manual
Tasks assigned to individuals	Phil ·         Continue to work on his demo ·         Proof read the user manual and technical manual Jun ·         Insert more information into the techincal manual in regards to extra diagrams ·         Proof read the technical and user manual Allen ·         Insert more information into the techinal manual, more diagrams and text where appropriate Jernej ·         The functional design section of the technical manual Tim ·         Fill out the testing section of the techincal manual
What should be done by next meeting	The user manual and technical manual should be done by next meeting because they are due on that day
Summary	Todays meeting was simple and fairly quick, we meet with Luke to discuss what we had done since we last meet and how we are going with the technical manual. We tried to get a rough idea of what and how much should be put within the technical manual but it seems the more information the relavent it will be in the end

Date	8/10/10
Away	Jun – Had something he had to go to
Agendas raised	Today was mainly about trying to get the technical manual ready for submission. A lot of the discussion raised was about what is required and what we could leave out and put in other sections of the documentation. After this was discussed the conversation was then about Phil’s demo and parts that could maybe change around latter on in the project such as the user interface and things like that
Things to look into further	·         What else is required within the technical manual
Tasks assigned to individuals	Phil ·         Continue to work on his demo Allen ·         Technical manual sections that include the file structure and other parts that are required Jernej ·         Will continue doing his flow and sequence diagrams, he doesn’t have many to go. ·         Once these are done he will read over the technical manual and see if any sections are need / not needed Tim ·         Is putting together the technical manual with the section completed by other students ·         He is also filling is some sections of the technical manual to make it more professional
What should be done by next meeting
summary	After having there been about two weeks since we had last meet everyone had something to present to the group. Everyone did what they were assigned over the break, from this the technical manual is now starting to fill out with the work done by individual people. There is still some more information that can be put in by the end of next week when its due. As for Phil’s demo he is still working on it and making progress however its just taken the back seat at the moment due to him having another assignment due in the next few days. From what he has told us its sounds be looking good and hopefully may have something to present to the group by the end of semester.

Date	20/9/10
Away	-
Agendas Raised	Today Jun showed us the demo he was working on. Below are some picture of the types of curves and in his blog is some more detailed pictures. He demo was great to see a lot of our ideas being represented graphically. The demo works well for the time being but with more tweaking and adjustments this demo and concept will become much more powerful and better looking for the end result we are looking for.
Things to look into further	·         Adjustment of the demo ·         More technical diagrams
Tasks assigned to individuals	·         Jun – use his demo in win form, within the user interface ·         Phil – work on his demo ·         Jernej – will get his sketches of the use case and activity diagrams into to rational rose ·         Allen – more work on the class diagrams and the activity diagrams ·         Tim – look into the code done by Jun, get a better understanding of the code and more technical manual work
What should be done by next meeting	By the next meeting the technical manual should be starting to get a move on. Focus will now be on the technical manual mainly because what we have done so far is due by the end of semester
Summary	The demo shows today helps give everyone an understanding of the direction we are aiming. Now before we take this demo and really get into the programming we will wait and see how Phil’s demo works. Then with theses two demo we will chose which is best or possibly even use the best from each demo

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.

Mondays Metting

Date	13/9/10
Away	Jernej
Agendas Raised	Adding some features to the program such as ·         The possibility of allowing two ends of the rope to join ·         Generate a random knot so a user can undo this knot ·         Adding a friction factor to the different types of textures with ropes ·         How to possibly store the knots, either within a database or a simple text file Besides these Luke raised another idea of how to represent the string within the program. Instead of having a set length of string at the start the user can then draw the string by clicking and dragging. A similar principle to rope being pulled out of a role of string.
Things to look into further	·         Luke’s idea of implementation ·         Advantage of stroing the knots within a database or a simple text file
Tasks assigned to individuals	Jun ·         Continuing on his example which will focus on the collisions Phil ·         See if looks idea of how to represent the string is possible. For now he will only look at it in a 2D sense and not worry about the collisions Allen ·         System architecture Tim ·         Technical Documentation ·         Exploring ideas and technical diagrams
Summary	From the new idea of how to represent a string raised by Luke, this has changed how we will approach the project now. His idea of having a user being able to essentially click and drag a string as if being pulled from a roll of string makes implementation possibly easier. Now we just have to explore this idea further as it seems to be a great idea in practice now it’s just a matter or trying to implement this.

Date	10/9/10
Absent	No one
Agendas raised	·         A few typos within the user manual
Thinks to look into further	-
What should be done by next meeting	·         Architectural overview of the system
Tasks assigned to individual users	·         Jun and Phil are still trying to get their examples going. This is taking time due to it being a difficult tasks and other subjects having assignments due which take up most of their time. ·         Allen will do an architectural overview of the system ·         Jernej will look more into the mathematical side of knots and see if he can gain an understanding and report back to the group ·         Tim will look into the technical documentation and get this started very soon.
Tasks completed	·         Jernej presented his finds on common types of knots that should/could be presented within our program
Summary	Overall things are moving but moving slowly due to other subjects requiring more attention. Jernej did a fair amount of research into types of knots to convey in the program. Most of his finding can be found in his blog. Phil an Jun are still trying to get a working example to see which one will be best to implement. Tim and Allen are slowly starting to work on the technical documentation. Sometime next week they plain to have the technical manual started with user case and other technical diagrams started and near completed.

Mondays Metting

Date	6/9/10
Absent	No one
Agendas raised	·         Time to start on the technical menu ·         Look to have the user manual 70 to 80 percent complete by the end of the week
Things to look into further	Nothing for the time being
What should be done by next meeting	·      The user manual should be around 70 to 80 percent complete by the next time we meet ·      Phil and Jun should be moving along with their examples, not finished but comfortably on their way to a complete example
Tasks assigned to individual users	Phill and Jun are still working on their examples of possible ways to model the main part of our program Allen – is going to look out the program from a hierarchial view. This means the layout of the whole program and possible ways to orgainised different classes Jernej – is looking into common knots. This common knots are what we hope to try and model within our program. He will gain a full understanding of these knots and the steps required to construct these knots. Tim – will add all the user interface stuff to the user manual. This includes the interface created by Jun and all the functionality related to it
Tasks completed	·         Everyone is happy how the user interface looks and the menu system behind it ·
Summary	Overall this was a fairly brief meeting because of the direction we take from here depends on which example from Phil and Jun is best for us to implement and continue with. Everyone is happy with the way the user interface looks and will work in relation to the user. The interface is simple and visually pleasing to any regular windows user. It isn’t over powering and is very basic but gives the user the options they would need to be able to complete a knot