Meet with Jun

On Sunday the 12th of December I meet with Jun to see the progress he has made. Due to him now having work commitments and moving houses he hasn't had much time to work on the project but the work he has done looks very good.

The progress he had made with his demo allowed the knot we go under or over existing rope, undo and redo points that have been added and also animation of all the steps the user took to get to the final stage. From what he showed me it look very impressive. We worked discussed possible ideas to go from here and also the debate of whether the user should start with a string or nothing on the screen was raised. Either way he was confident he could cater for either option we chose for the final project.

He also told me he had been in contact with Allen and the two of them had been discussing ideas of how they could represent the knots within the database. It was good to hear that these two are working close together and showing good team work. By them working close together this makes communication latter on down the track easier but also allows for the design of the database to me more consistent with the actual knots being created.

From here I will email Allen and see what progress he has made and have some length discussion with him to see how he is going

Now with the documentation submitted it can be pushed to the side for bit and move my focus onto helping Allen design the website. My task was to create a banner or graphic that would sit at the top of the website.

Over the past few days all that i have been doing is working on the documentation. This just involved proof reading all the parts done by others and putting everyones work together so it looks well presented and of a high standard. Besides that i havent been doing alot but now that documentation is done i can put it to the side for a moment and help Allen with the designing of the website for our project

over the break

recently over the break i was assigned a few things to do because there was about 2 weeks between meetings. I got this done and now its just a matter of putting all the information i and everyone else has done together in the one document. hopefully we have the right sections and information within the user manual and the technical manual to get some good marks. Its hard trying to know what should be included and what should be left out. i did get some technical manuals off luke and went through them as a guide to see what we should include.

so for now im just trying to make the technical manual look good and well presented, i know its not the final version and it can be rough but i still want good marks for this section. hopefully everyone is happy with the technical and we can agree on what we will submit some time mid week

Today i just filled out some information tables in realtion to the the use case and activity diagrams jernej will be doing for the first few icon within the graphical user interface.
The tables were in the following format

Requirement #:	Requirement Type:	Use case #:
Description:
Rationale:
Source:
Fit Criterion:
Dependencies:
Rank of importance:
Supporting Materials:

These tables were filled out for the following:

• new
• open
• save
• print
• print preview
• undo
• redo
• select point
• delete point
• add point
• lock point

Today i went and got some past technical manuals off Luke. For now I am just reading through them to see what we should include in ours and gain a better understanding of what is needed.

Hopefully tomorrow or sometime on the weekend I will get stuck into writing some parts of our technical manual

what ive been doing

Recently i have been looking into some of the example from the Bepu physics library trying to get an understanding of how these work and how the library operates. At first this was complicated, but after a while i got use to it now have a better understanding.

Besides that i have made a few small changes to the user manual such as spelling mistakes and a few things like that. I have also been looking at templates on the internet for a technical manual. Hopefully we will start this soon because its due at the end of this semester and the technical manual contains a lot more information then the user manual.

Today i just added all the user interface that Jun had done to the user manual. Hopefully this make the user manual around 70 to 80 percent complete. The rest wont be done until we get more of the actual program done.

I have also been looking at ways to start and represent the technical manual because this should be started very soon

After going through several examples of past user manuals from previous years I added and changed around our user manual to make it more appropriate.

Without having a meeting with Daniel for a few weeks now its hard to tell if we need a lot more information, less or we have enough information for our user manual. Hopefully when we have a brief meeting with him on Tuesday things will be a lot clearer.

Also today I just made a few simple picture within Visual Studio of (hopefully) what i final program will look like. These simple pictures are within the user manual.

User Manual and RUP templates

Today i just filled in a few sections of the user manual. This sections filled out were the introduction and the features. Some of these features will change over time, some may get added but for now those features written are definitely going to be in the final program.

As for the RUP templates Jun gave me a heap of documents in regards to RUP. All i did today was read through these to get a better understanding

User Manual

Today was mainly about getting a start on the user manual. This is our first thing that is done for a group project. What i mainly did today was read the lecture notes about what should go into a user manual and then created the layout for the manual.

From here i filled out some sections that were relevant to what we have accomplished so far.

first few individual diaries

This is my first blog post for my individual diary however here a a quick recap on what i have been doing in the past few weeks.

• gaining a better understanding on simple types of knots
• learning some basic C# programming
• meting with the group to discuss and plain ideas
• looked into other program or application out there that are similar to what we want to achieve
• thought about how the user manual may look