I know this is several days late but as a group we only recently decided that this would be the easiest way.
So far as a group we have meet several times and I will discuss in more detail what happened on those dates.
First group meeting 2/8/2010
For our first group meeting we all gathered and introduced ourselves, everyone was excited to start project and also very happy with the group overall. As three of us had just done CSCI222 together we knew we could count on each other for group work and no letting anyone done. The new member (Phil) was also excited to join the group because he helped round out having each person doing a different major which can help the group in the long run.
From there we all went through the list of available projects, some sounding more interesting then others. Instead of chossing a project straight from the list we though we should try and brain storm other ideas and try and push that as a potential project. After trying to find a need for a software application, the idea to try and create a mobile based UOW student helper arose. Everyone was keen on this idea and looking forward to trying to undertake this as our project. However due to leaving it a little late and not knowing the right procedure to get a project proposal confirmed as a group we had to just face the fact that we needed to chose one straight from the list.
In the end we chose the Knot program - a graphical and mathematical representation of knots. Everyone is happy and willing to do this project. It will be challenging but rewarding experience for everyone.
Second meeting 9/8/10
This was a first formal meeting with our supervisor Luke McAven. Below is the meeting minutes.
| Date | 9/8/10 |
| Absent | No one |
| Agendas raised | · What do we want the final product to be like? Will it be educational? Will it be a puzzle solving game? Or could it be used as research software? · How will different types of knots be stored within the system? Will there be a database of knots to compare with? How will these knots be stored within the database? · How will these knots be displayed within the program? · How will the knots be manipulated? |
| Things to look into further | · How to represent these knots · Simple types of knots including line, circle, loop. · Will the user be able to join or cut a string |
| What should be done by next meeting | · As a group have a better understanding of what knots are · A better understanding of C# and XNA source code for the group member who haven’t used such resources before |
| Task assigned to individual members | None |
| Task completed | - |
| Summary | As the first group meeting with our co-ordinator today was more about everyone gaining a better understanding of what is required for the project. Luke raised many good points as to which direction as a group we want the project to take. Other points raised where how things could be done to help represent the system such as representing the knots either in 2D or 3D and the manipulation of the knots. Overall for a first group meeting everyone walked away with a better concept on what this project will require and what will be needed. |
Third Meeting 12/8/2010
Absent: Allen ( work)
Agendas rasied: How will we do our individual and group diaries? a possible blog
To see if anyone knows how to setup an SVN
Maybe some mook pictures so people can get an understading of what we want the final product to look like, a common goal.
To see if it is going to be possible to model rope or string and allow the user to manipulate it.
Get group members who dont know much about XNA and C# to look into it.
Also a possible group name.
Things to look further into:
Different types of knots. Help demonstrate to other group members what types of knots there and show the how to tie such a knot so they can gain a better understanding.
Task assigned to individual members:
Tim : Mook pictures and gain and understanding of C# and XNA
Jun: to see if the modeling of curves and loops is possible
Phil: try to setup an SVN for the group or look into it
Tasks Completed:
Summary:
This was only a short but brief meeting so everyone knows where to go from here and what to do. Hopefully by the next time we see our supervisor we have something to show him. He will probably also recommend other ideas.
No comments:
Post a Comment