CSCI321 Autumn Project Group Meeting 10

Title: CSCI321 Autumn Project Group Meeting 10
Time: Thursday, 15th May
Location: Building 3 UOW
Attendees: All members
Recorder: Guanqiao Huang

Objective:
Depth discuss about documentation

Basic discussion about documentation
The first step to do is
1. The content on the document
for technical document
1. Class diagram
2. Use case
3. Sequence diagram
...

for user manual
1. the screen shot need to be added
...

Team leader allocate the work to the team mate. If the time is free possible, we are going to finished it as soon as possible.

CSCI321 Autumn Project Group Meeting 9

Title: CSCI321 Autumn Project Group Meeting 9
Time: Thursday, 8th May
Location: Building 3 UOW
Attendees: All members
Recorder: Guanqiao Huang

Objective:
Discuss about the further documentation and final coding

Discuss about the further documentation and final coding
1. Some coding need to implement and fix
--avalanche affect algorithm
--hash chain for all the possible bits
--collision for hash function (if have time)
--Ubuntu version (if have time)
--mac OS version  (if have time)
--Android Hash kit assistant  (if have time)
--iOS Hash kit assistant  (if have more time)
--all possible warning message

2. Documentation
--functional testing
--final user manual
--final technical manual

We got many works to do in project. :(

CSCI321 Autumn Project Group Meeting 8

Title: CSCI321 Autumn Project Group Meeting 8

Time: Thursday, 1th May

Location: Building 3 UOW

Attendees: All members

Recorder: Qing Ren

Objective:

1. Update Hash Kit

We checked through the whole hash kit, and discussed with the supervisors. As a result, there are some things we need to update.

For the whole program, there are three main problems need to be fixed.

1. When run an external exe, it will appear a black block first, and the result need to be stored in a text first, and then our program will read the text to get the result. It seems the program is informally, so we need to use a better function instead of call system().

2. In the all functions, the result will show in a table, but so far, the table will leave some gaps. The supervisor suggested us to use a smile face fill in the blanks for a friendly view.

3. Sometimes, during run the program, the crash will appeared. We didn't know the reason, but we must make a much more stable system.

And there are some problems existed in the each part of the program, some of them just list below:

1. In the birthday attack test function, user can input a hash value to calculate the desire test time or the probabilities for finding the collision. But actually it is against with the second-image properties, so we need to take off this part.

2. In the part of performance test, the front size is too small to look clearly, and the block size is also have the same problems. Need to be changed.

3. In the part of avalanche effect test part, some crash will appear, and if the input value is too big, something output will be wrong. So maybe we need to add a limit with the input value.

4. In the part of hash chain test, we need to add a new function to test the all probabilities of hash chains within a limit length of bits.

And there are others we need to update. So we assigned the tasks, and prepare the phototype in next week.

CSCI321 Autumn Project Group Meeting 7 plus

CSCI321 Autumn Project Group Meeting 7 plus

Title: CSCI321 Autumn Project Group Meeting 7 plus
Time: Thursday,24th April
Location: Online
Attendees:All members
Recorder: Guanqiao Huang

Objective:

1. Grasp the progress of each group member

2. Start to put the sub function into Hash Kit

3. Some bug in Hash kit need to fixed.

1. We have meeting online by Wechat , and we grasp the developing progress from each member.  Some team mate might talking with Group leader by mobile phone.

2. Some sub function is finished, and it is time to put it into the main program Hash kit. 

3. We discussed and found out some bugs from current Hash kit program. We list it and try to fix it as soon as possible.

CSCI321 Autumn Project Group Meeting 7

Title: CSCI321 Autumn Project Group Meeting 7
Time: Thursday,17th April,10:30-12:30 & 14:30-16:30
Location:Building 3 & Library
Attendees:All members
Recorder: Xing Pan

Objective:
1.Threads apply to the project
2.Finish basic Avalanche Effect GUI
3.Start to design warnings for our project

1.During this week, we have a meeting in building 3 to discuss current process that we have reached.We have decided to finish the core part of hashkit before week8 due to prototype. The leader also distributed the work that each of us need to do these days.

Yew found the solution for us on the weekend, which is a good way to avoid GUI freeze.And he also provided a sample threaded-program to modify the code that we have done.


2.Guanqiao and I finished the basic Avalanche Effect GUI based on the code that I have done. At the beginning, we have a bit misunderstanding on the Avalanche Effect. But with the help of Yew, we got over it by using a recursive function.

3. We make a plan to handle the warnings on the weekend. Basically, we have got the clues on how to deal with them.

CSCI321 Autumn Project Group Meeting 6

This is week 6, we have no group meeting in this week.

In next week, we may have an important meeting on Thursday. We are going to complete most function before the week 8 prototype. There have a Easter break after week 7, so we totally left about 2 weeks. I hope all the person can attend the next group meeting, and show their result for each work. Thx

CSCI321 Autumn Project Group Meeting 5

Title: CSCI321 Autumn Project Group Meeting 5
Time: Wednesday, 2 April, 2014 12:30-15:30
Location: Online
Attendees: Guanqiao Huang, Xing Pan, Wi Yew Hong, Qing Ren
Recorder: Guanqiao Huang

Objective:
1. Discuses Online by using Wechat
2. Finished summary sheet
3. Continued the work

1.In this week, we have no group meeting with supervisor because supervisor has been to Singapore. We meet online by using Wechat and QQ instead of physical meeting. The discussion is mainly cover the specific implement of  birthday attack, hash chain and avalanche effect.

For the hex to binary, I had send email to ask Luke, and I share that information to group mate

for example: hash chain
 user input a hash value "1f3870be274f6c49b3e31a0c6728957f"
selected 8 bit, it means "1f" ("1f" be a string)
hash("1f") = "0cde80d4d65fc5307a07f86ac9dfa34c"
selected 8 bit, it means "0c"
hash("0c") = "0fa2fc5954ab40ecfe658625c4adbea5"
selected 8 bit, it means "0f"
hash("0f") = "7dff51ca8eb990122513f24ffdaa4d9a"
selected 8 bit, it means "7d" ...and so on
until for example it have a chain

Ask:

So,if I choose MD5 and cut to 5 bit, not multiple of the basic number of 4. 

What is input and display?

for hash value "1f3870be274f6c49b3e31a0c6728957f"

hex "1f", the binary is 00011111

cut into 5 bit, the binary result is 00011 or 00000011

the hex is "3", so for the next input in chain is string "3"?

The main point is that if we translate the hex value into binary, for example MD5,  a multiple of 4 size is easy to shown on the Hash Kit. I would like to make the selected bit value be multiple of 4, so the it makes sense on most hash function(hex).

2. I give the work of summary sheet to Xing Pan, and he finished before due day.

3. Each group mate continue their work.
Guanqiao Huang: Hash Chain, Bruteforce attack&Dictionary attack(include search attack,role search attack)
Xing Pan: Avalanche effect
Qing Ren: Birthday attack, random value(separate Upper letter and lower letter)
Wi Yew Hong: Multi-thread and so on

CSCI321 Autumn Project Group Meeting 4

Title: CSCI321 Autumn Project Group Meeting 4

Time: Saturday, 29 March, 2014 10:30-15:30 & Wednesday, 27 March 2014

Location: Building 3 UOW

Attendees: Guanqiao Huang, Xing Pan, Wi Yew Hong, Qing Ren

Recorder: Wi Yew Hong

Objective:
1. Review and feedback on our current prototype.

1. Firstly we take a look back into our prototype and identify which one we should be focusing on. For now we have already have most of the function requirement so we decided to move into something which is non-functional. Below are the feedback we needed to improvise:-

a) Font- make it bigger

b) Adjusting textboxes

c) Notify user if user trying to hash too much

Other than that, we will still follow up undone task from previous week. And modifying a few errors on our prototype version.

Group diary 3 (Autumn session)

Title: CSCI321 Autumn Project Group Meeting 3

Time: Thursday, 20 March, 2014 12:30-15:30

Location: Building 3 & library, UOW

Attendees: Guanqiao Huang, Xing Pan, Wi Yew Hong, Qing Ren

Recorder: Xing Pan

Objective:

1. Review the priority we have done

2. Plan to finish our session components as the priority aim

3. Discuss algorithm for estimating time.  

1. In the meeting with supervisor on this week, we were not quite sure how much work we have done, even started getting worried due to so much pressure from other subjects. However, we have confirmed we do have basically done well the base parts in terms of whole project. And also we allow some typical changes happening that were set at the beginning of our project. It is acceptable with the changes of priority. Because these kind of changes make the project more realistic as we go on the project. There are always some differences between the original plan and the reality. The project is, to be then more executable and flexible when we're done with it.

2. Actually we do not have a significant move in our project. We started to think about what leads to. we realised that almost all of us are waiting  for a specific step which will make the project more or less efficient. So that we stopped individual tasks for a while. Luckily, we found this was not a good way to go. Finishing each session component is more important than making project efficient. So we decided to leave the step for a while and make our project work first.

3. We spent around two hours on discussing how to compute the time to show user show much time left to the some functions.
Here goes some notes which we discussed on:

                

Group diary 2 (Autumn session)

Title: CSCI321 Autumn Project Group Meeting 2
Time: Wednesday & Thursday, 12 March, 2014 12:30 & 13 March 2014
Location: Library, 204, UOW
Attendees:  Guanqiao Huang, Xing Pan, Wi Yew Hong, Ren Qing
Recorder: Wi Yew Hong

Objective:
1. Summarize previous risk analysis.
2. Summarize first iteration and objective completed.
3. Re-establish working environment.
4. Assigning task to each member based on member understanding on requirement

In this meeting, the main task is to speed up our project where deploying our project in a new working environment.

1. In previous risk analysis, Microsoft Visual Studio was considered as a base GUI for our project. But it was quite complicated with multiple library and there are some problem with Microsoft Visual Studio 10 RTM version which we did not realize we should use a later version of it. After some discussion, we decided to abandon Microsoft Visual Studio cause of uncertain feeling if this problem will exist on other version of Microsoft Visual Studio too. So we are currently using Qt 5.2 which comes with Qt library and Qt creator. Other than that, risk of program not able to execute properly due to ran out of memory space, so we decided to push some of the output into a file and process it later.

2. Under first iteration, we were able to run commands on windows platform, execute hash executable, developed hash chain function. There are some other function we did too but it does not perform as expected such as brute force with dictionary attacks, There are some special character which are consider as a command in windows platform and we will try to identify all of them as soon as possible. Other than that, comparing result require lots of time too, so performance is one of our minor concern too and we decided to take a look into windows pthread which might be able to help us to improve our overall performance.

3. As we re-establish on our new working environment, we also set a standard of how functions should be called and named, the base execution of hash management which are similar to many analyzer then we group it into a class called hashmng. Hashmng which will able to execute hashes in it, perform command, storing hash directory, retrieving information about hashes, etc.

4. Task assigned to member this week are:-

Guanqiao: Hash chain with heap sort for analysis (Not finalized yet)
Wi Yew: functions to handle binary data & Win OS threading
Xing Pan: Avalanche effect
Qing Ren: Birthday Attack

Group diary 1 (Autumn session)

Title: CSCI321 Autumn Project Group Meeting 1
Time: Thursday, 6 March, 2014 10:30-12:30
Location: Office, Building 3, UOW
Attendees:  Guanqiao Huang, Xing Pan
Recorder: Guanqiao Huang


Objective:
1.Function for Brute-force attack
2.Function for Birthday attack
3.Function for Performance
4.Function for Benchmark
5. Statistics the similar by changing the text
6. Hash Chain

In this meeting, the main idea is to refresh and re contribute what we need to do in the project.

1.Function for Brute-force attack & 2. Birthday attack
Dictionary attack is the main way for perform the brute-force attack in our hash kit.
In this meeting, we make sure the the relation in brute-force attack and birthday attack, birthday attack is the special case in brute-force attack. So we are going to separate these two attacks.

for birthday attack, we will use this formula

3.Function for Performance & 4.Function for Benchmark

Performance and benchmark are very similar things. In performance part. it will analysis the collision and the hash speed. The key is random.After analysis, the report can be output from the performance analyzer.

Benchmark is a function for load the performance report and then compare the hash function.

5. Statistics the similar by changing the text
After each change in the string text, the hash value can be compare automatically by this function. for example, add one blank in each character each time, and compare the hash value. If the similar rate is high, the hash function might have some problem.

6. Hash Chain
Hash Chain not only compare the first hash, the first version Hash Chain is not actually meet the fact. So we need to redesign the Hash Chain.


Some note for objective:
(The note is wrote by Xing Pan and Qing Ren)

Group Diary 23

Title: CSCI321 Project Group Meeting 23
Time: Friday, 25 October, 2013 12:30-16:30
Location: Libary 203 and Building 3, UOW
Attendees:  Guanqiao Huang, Qing Ren, Hong Wi Yew, Xing Pan
Recorder: Hong Wi Yew， Xing Pan


Objective:
Check the draft of manuals with supervisor
Ready to go all the documents

Check the manuals with supervisor

We spent almost three hours before going to meet supervisor.It will come as the benefit of such action we thought and it does considerable impact of later work. During that time, we retrieved carefully the whole structure of user manual and technical manual that we currently reach. 

After meeting with supervisor, apparently, we've got hints from him about manuals, especially the technical manual. Thing's getting easier due to the former work. Around two hours being in building 3, we finished our whole draft of the user manual and technical manual. 

Ready to go all the documents

Pretty much work is done by Guanqiao for the documentation stuff after a few days.For the further discussion about all of the diagrams, some source of manuals being checked from internet to make sure a good structure for the documents.

In the next few days, we'll show the draft of user manual and technical manual to supervisor to obtain the further details. 

Group Diary 24

Title: CSCI321 Project Group Meeting 23
Time: Friday, 30 October, 2013 14:30-18:00
Location: Libary 203 and Building 3, UOW
Attendees:  Guanqiao Huang, Qing Ren, Hong Wi Yew, Xing Pan
Recorder: Xing Pan

Objective:
Identify the problems on the manuals
Distribute work and fix problems

Identify the problems on the manuals

During this week, we discussed the our the problems that supervisor identified on our technical manual and user manual.

We spent almost three hours in the building to figure out what is going on.

We realized that we need to move the interface stuff from technical manual to the user manual.

Lack of the class diagram may be the deadly problem in our manual. So we should to catch it up.

Also it is quite importance to specify the analyzer part on the activity diagram. Make sure it will work.

Distribute work and fix problems

Individual working maybe not feasible and not easy to result in good work. Thus, we decide to divide our group four people into pair small groups to fix our problems. We've spent three hours and half in building 3 and handled most fixing jobs for sure. Pretty much work as said above, we've got so much else work from other subjects to do as the last study week in the uni. For this reason,, we make a decision that working home individually and contact each other to make sure everything is going well. And so far, so good.

We'll end up the project with manuals after fixing all problems and basic website in this semester and need to prepare our final exams. Coding and further product information will be started next semester.

Group Diary 22

Title: CSCI321 Project Group Meeting 22
Time: Friday, 18 October, 2013 11:30~1:30, 2:30~5:00
Location: Libary 203 and Building 3, UOW
Attendees:  Guanqiao Huang, Qing Ren, Hong Wi Yew, Xing Pan
Recorder: Guanqiao Huang

Objective:
Continue work on the technical manual document
Start to work do user manual document


Continue work on the technical manual document
We allocate the work in library, and discuses some part of content about technical manual.
We work on the technical manual by using uni computer in the lab.

We used some content from our requirement specification, and putting into the technical document. We edited some function in the part of requirement on technical document, like F8.3 File location history, we changed into F8.3 Log history recorder.

We have been finished introduction, glossary, requirement specification, operational requirement, use case diagram, activity diagram and sequence diagram. (Before this meeting)

Today, we continued finished the part like position statement, user constraints, software Technologies, development tools, development methodology, general user interface layouts, user interface detail, use case scenarios, explanation of activity diagram, explanation of sequence diagram.


Start to work do user manual document
We finished a draft user manual today.

Group Diary 21

Title: CSCI321 Project Group Meeting 21
Time: Friday, 11October, 2013 14:00
Location: Building 3, UOW
Attendees:  Guanqiao Huang, Xing Pan, Qing Ren
Recorder: Guanqiao Huang

Objective:

Organize the user interface

Organize the user interface

Hong Wi Yew is sick totay,so we got 3 attendees in this meeting. After we meet with supervisor, we got a new idea to create the whole program interface.

Before the new idea, we decide to use new windows for each analyze. To be specific, if we test one hash file, and then if we want to test another hash file, we user can create a new windows of Hash Kit and then run the another hash file, and then continue and so on. The process control panel (stop, start,pause) is separate into each analyze.

The new idea is use sub-tab for each analyze. and then only one process control panel, the control panel like a list, it include list of task. And all the task with process control (start, stop and pause).

We are going to continued the document next week.

Group Diary 20

Title: CSCI321 Project Group Meeting 20
Time: Friday, 27 September, 2013 14:00
Location: Building 3, UOW
Attendees: Hong Wi Yew, Guanqiao Huang, Xing Pan, Qing Ren
Recorder: Guanqiao Huang

Objective:
Complete UML diagram
Continued design the User interface

Complete some diagram
We continued fix some problem in UML diagram, such as use case diagram, sequence diagram and activity diagram.

In use case part, except use case diagram, we also need to write the scenario of each use case.
These include use case name, primary actor, supporting actors, summary, pre-conditions, normal flow of events, extensions,post-conditions.

To be specific,
Use case name: the same name as each use case in use case diagram.
Actor: we separate two kind of actor, which are student and developer.
Summary: Specific description of use case
Conditions: Pre conditions of each use case
Flow of Events: In this part we need according to the user inter face, so we need to draw a basic interface. And then each steps following the user interface.
And so on


Continued design the User interface
We continued discuses user interface,  each one got their own idea about user interface, we draw several style about Hash Kit on the paper, it is difficult to summarize those user interface.

Some user interface very good but we might difficult to code it, some interface is very basic we might easy to code. Actually on the draft user interface, we need to focus on the basic function.

Group Diary 19

Group Diary 19

Title: CSCI321 Project Group Meeting 13
Time: Friday, September 20th, 2013 14:00
Location: Building 3 & UOW Library
Attendees: Hong Wi Yew, Guanqiao Huang, Xing Pan
Recorder: Hong Wi Yew

Objective:-
Discuss mainly about use case.
Discuss about GUI
Discuss about other UML diagram

Use Case Diagram

A preliminary Use Case Diagram has been done on our discussion and it was quite complex and messed up, our leader will clean and arrange it and let us have a view on it. After a brief final discussion, we decided to ask our supervisor for some advice so we decided to send a copy to him and let him have a look.

GUI

On this side, we have yet know the detail of the graphical user interface yet, but the Basic User Interfaces(Educational Use) will be a lot different from the Advance User Interfaces(Developer User). Mainly because Educational Use have a lot of explanation on the hash but Developer User will exclude all that and mostly related to efficiency and flexibility. The Educational Use will not have a saving option but the Developer User will have an option to save for the user to load in the future.

Other UML Diagram

After a small discussion, we decided to divide our job no this UML Diagram to speed up progress. All UML Diagram will be re-visited on our next meeting to make sure we are doing it correctly.

Group Diary 18

Group Diary 18

Title: CSCI321 Project Group Meeting 18
Time: Friday, September 13th, 2013 14:00
Location: Building 3 & UOW Library
Attendees: Hong Wi Yew, Guanqiao Huang, Xing Pan, Qing Ren
Recorder: Guanqiao Huang

Objective:
1.Finished submit the requirement specification
2.Understand the next two task for our project in this session
2.Share some resource about User Manual and Technical document


Finished submit the requirement specification
In this week, we finished a complete requirement specification. And submit it before Friday.

Understand the next two task for our project in this session
After submit the requirement specification, we meeting with Luke which is our supervisor for our project. We discussed the next step for our project. We know that we need to do a two program which is User Manual and Technical Document. In short User Manual is for the user, and the technical document is for the developer.

We have a look for the previous project document, there are some good example and also some bad example. We take one of the hard copy example for our guidelines.

Share some resource about User Manual and Technical document 
We searched some resource from the internet about the user manual and technical document. If the resource is useful, we putted it into the dropbox. We are going to list some context of our document in next week meeting.

Group Diary 17

Group Diary 17

Title: CSCI321 Project Group Meeting 17

Time: Friday, September 6th, 2013 13:30

Location: Building 3 & UOW Library

Attendees: Hong Wi Yew, Guanqiao Huang, Xing Pan, Qing Ren

Recorder: Hong Wi Yew

Objective:

1. Finalize requirement specification

2. User interfaces pre-design phase

Finalizing requirement specification

In this discussion, we arranged our requirement specification and changed some detail of the requirement specification. We look further into file/data set handling for our program for better resource management. For efficiency, we decided to store only the seeds for random generate and only generating it when needed, then remove it when it is not in use. We are still deciding on because of processing power. If we decide to random generate when it is needed, it might save memory spaces, but how much will it cost on processing.Other than that, we look into parallel processing for a better calculation process and analysis process, but we have yet finalize it.

User interfaces pre-design phase

We designed a few pattern for educational use, Some of the user interfaces are suitable for beginner use, but there is a lot of restriction such as number of hash function to be analyzed and we consider to disable user to test their own hash function. As for this case, we will provide a few sample of hash function for user to analyze and study about hash functions.

We also did some review on suggestion that our supervisor gave, such as changing and adding the functional and non functional detail. 

Group Diary 16

Title: CSCI321 Project Group Meeting 16
Time: Wednesday, September 4, 2013 15:30
Location: Room 203&204, Library, UOW
Attendees: Attendees: Guangqiao Huang, Xing Pan, Qing Ren, Hong Wi Yew
Recorder: Qing Ren

Objective:
1. Working on formal presentation continuously
2. Working on formal requirement specification continuously

Working on formal presentation continuously
According to some advises from the supervisor, we found some evidences for supporting our choices, such as some data about people use Linux for coding. We put evidences on PPT, and add the comments in each page for answer the questions that teacher may be asked. We modified the PPT to solve the problems leave in the last week, and as well as, adjust the speech. Now, we don’t need to change anything about the presentation any more. The only thing we need to do is just practice.

Working on formal requirement specification continuously
The category has been re-ordered. We completed the part of description of all the functional requirement and the non-functional requirement. We also finished the part of introduction. Now, we just leave the part of project overview didn’t finish.

We review the functional requirement again. Some priority of requirement have been adjusted. We set base, high, medium and low four priorities instead of must, should and may three priorities before. It can make the description more clearly.

We merged some test functions and online functions. Because we used the mode of spiral, so far, we didn’t make sure the whole part of the test functions, so we just call it test performance. In the future, we need to modify this part.

 In the next group meeting, we should complete the final version of the requirement specification, and start our coding design as soon as possible.