CoDe3100-2015-Daming YAN

2015年6月8日星期一

2015年6月4日星期四

Week 13. Presentation feedback

On the presentation day, our group is the first team to present our project. Actual model is working well and russell gave us some useful feedback.

Improvement point: I was really nervous during the presentation, My talking is really bad and needs to improve.

2015年5月30日星期六

Week 12. Project Complete

In week 12, our project nearly finish and i'm helping with the wiki and make a video for it.

2015年5月21日星期四

Week 11. Group presentation and feedback(Remuneration)

Group presentation 11: Remuneration

Key notes:

What is Remuneration?

"Fuck you" video
Is it as difficult to understand as it is to pronounce
How much are you worth? what is your value proposition?

Remuneration work in the real world

"What do I have to pay for" vs "what do I want my remuneration package to say"
Successful remuneration package
Dollar per hour
Non monetary remuneration
Direct remuneration
Indirect remuneration

The employer:contractors (unsw)

The employees: student(us/student)

Remuneration as a student

Experience is key!
23.8% of UNSW FBE job seeker rate
$53.27 per hour for graduating student

How do I add value to myself?

Partake in study tours
General Education
Quality subject selection
Outstanding marks
Networking
Peer to peer competition
Extra curricular projects
Esteem work
Internships

What do I add value to myself?

35%(first year), and increase every year, maximum 95%

How do I move forward?

Drawings
Co-ordinate documentation
Site conditions
Codes,regulations and legislation
Project evaluations,programs and feasibility studies
Consultants,contractors and suppliers
Project contract

Feedback:

Good explanation and clear understanding for the topic
Have video and which is a good video
Good examples for different jobs
Clear and fluent voice during the presentation

Improvement points:

Powerful start but weak when present
Should talk about own project
Self employ scenario missed
Should use more images to make the presentation more vivid

After presentation comments:

There are only 2 members in their team to present the topic. And I learned a lot information from this presentation like how could I value myself,etc.

How about our group for Remuneration :

For our group, we still study the course and there is no-one employed by any architect or design company right now. So we dont have any experience at the moment.

This week programs:

My part is already done for the group project, and Elliott already done with the coding part. Then we just wait Verdan to finish off the modeling truck and Peter will building the actual model and put everything together.So what I'm doing at the moment is helping to documenting the Wiki Blog for group.

2015年5月13日星期三

Week 10. Group presentation and feedback(Conflict)

Group presentation 10: Conflict

Key notes:

Source of conflict

Change the adapt
Personalities different characteristics
Poor leadership
Poor communication
Misunderstanding
Subpar performance
Inability to control emotions
Distrust

Types of people causing conflict

My idea is better (no collaboration)
Drama queen (talking too much in the team)
Never on time (poor management)
Dr lazy (the teammate who is not doing own working part)
No group work (poor leadership)
Carry (the person doing almost the work for team)
Ninja (visible teammate)
My clueless (no communication don't know what's going on)

Avoiding conflict

Snowball conflict (no escape)

Strategies to resolve conflict

Identify each member strengths and weakness
Define acceptable behavior in a group a good leader

Negative impacts of conflict

Conflict cause stress
Reduced communication

Positive impacts of conflict

Brainstorming
Opportunities to redefine ways to find solutions
Experiment with new negotiation styles

Hextic Installation

Redoing pixels,reproducing incorrect work
Tensions between peers
Learning experience for collaboration
Conflict between parties of interest
Failing to plan
Importance of leadership

Feedback:

Good explanation and clear understanding for the topic
Clear images and texts
Interest starting of presentation(good example)
Clear and fluent voice during the presentation
Good examples of conflict

Improvement points:

Should relate the topic to their own project

After presentation comments:

Listen is the key, be straight and direct

How about our group for conflict:

Actually we don't have many conflict in our group, because we doing well communication, all for the teammates are so friendly and positive attitude.

This week programs:

Elliott is still doing the coding for the project, and he is trying to separate different function on 2 arduino chip-boards. But after the studio, he already solve the coding problems and he will build buttons and potentiometer into 1 board.

So I'm build a new arduino what has 2 buttons and 1 potentiometer.

Final version for arduino chipboard

And I'm using Fritzing software to make it more clearly

Final version - 1 potentiometer and 2 buttons

2015年5月6日星期三

Week 9. Group presentation and feedback(Intellectual Property)

Group presentation 9: Intellectual Property

Key points:

4 main types of intellectual property:

Trademark => logos secrets, rights protection.Industrial and commercial use Words,images or smiles.
Copyright => art work and writing.
Design => physical design.
Patent => process of function.

Renewal:

Design - last up to 5-10 years. Fee $320
Trademark - last up to 10 years. Fee $300
Copyright - last up to 70 years. Fee N/A
patent - last up to 20 years. Fee $300-$2300

Feedback:

Good explanation and clear understanding for the topic.
Clear images and texts
Giving tips to other groups to protect their designs.
Using the example of previous uni works and example of other project in the class (Blacktown project)
Using the video to show the comments

Improvement point:

Reading notes from paper during the presetation.
Better release to topic to own project.

How about our group for intellectual property:
For the our project, we already use the references from other people( on internet),So we cant apply the copyright.but we can apply the design for the driving model(set) and coding for the patent.

After presentation comments:

we all learning the intellectual property to protect self. and getting some useful ideas from russell.

This Week program:

After the last week working programs, I noticed we don't really need to use LED lights for the arduino board, the LED lights just for the signs, and we can check the coding by using serial-monitor. And after this week studio, we make the final decision to build the arudino board what is using 2 buttons and 1 potentiometer. The 2 buttons which control the acceleration and reverse, potentiometer for the steering wheel function. Elliott still working on the coding to make it working.

And Russell shows us a program called Fritzing. this program can make a blueprint for build the arduino board. and clearly shows the details. So I will use it to make the previous works more clearly and detailed, also for the final version of arduino board.

Here is the sketch in Fritzing: