2010/02/11

Chocolate browny


I went to my host family's house, so I made chocolate browny. But they are big family, and this was not enough. Next time I want to make bigger than this one.
However, my host mother and father said to me,"you are a part of my family!" I'm very glad to hear that.

ホストファミリーの家に呼ばれたので、チョコブラウニーをつくってもっていきました。でも大きな家族だから全然足りなかった。
次はもっと大きいのをつくらないと^^;
でもホストファミリーは「あなたは家族の一員よ」といってくれてとってもうれしかった!!




2010/02/10

orkut

One of my class mates told me about orkut, which is like a facebook. He uses this site and he is Indian student. Firstly, I thought orkut is popular in India. But this site is provided by Google. I didn't know Google has already run SNS service!!

私のクラスメイトがorkutというfacebookのようなサイトを紹介してくれた。彼はインド人なので、てっきりインドで有名なSNSサイトかと思ってたら。。。。グーグルが運営してたのね。。。
グーグルがSNSをやってたなんて、しらなかった!

C# week3_2

if : 2choice

int i = 4;
if(i<0) i =" 10;" j =" 10;">10){
if(j>0){
Console.WriteLine("j is positive");
} else {
Console.WriteLine("j is negative");
}
}

switch : multiple choice

switch()
case
break;

for : loop

int i = 10;
for (i;i<15;i++)
{
Console.WriteLine("Hello");
}

Result: Hello*5

C# week3_1

Datatype
  1. Value type
  2. Reference type
Operator
% Moduly operator
&& And operator
|| Or operator (左からチェックしてTrueだったら次はチェックしない)

6/0 Error

bool k = (5>0 && 6>10) || (5>0 || 1/0);
= false || true
= true

Compound
int i = i+10; = i+ = 10;

Ex1 ? Ex2 : Ex3;
(true) Ex2
(false) Ex3

int i = 5;
string s = i>6 ? "abc" : "edf";
Console.WriteLine(s);

Result: edf

Chilli con carne (チリコンカン)


I bought mince of beef at only $7!! So I cooked Chilli con carne. Mexican is popular in New Zealand, and my host family loved Nachos. Chill con carne is made easily and it's delicious.And my flat mates gave me spinach, so I made a spinach salada. The spinach of New Zealand is quite different from Japanese one.

500gで7ドルの牛肉ミンチを買ったので。
半分をチリコンカンに。残りはミートソース。メキシカンはこっちでも大人気です。
付け合せはフラットメイトからもらったスピナッチ(ほうれん草)のサラダ。
日本のほうれん草とは全然違いますー。

Data Base week3_2

Table ≠ Entity = Relation
Relational model : collection tables
Referencing : Referential integrity

Normalization : separate many tables → put into relation

Entity : identifiable thing (only one thing)

determinant ex. employee
dependent ex. phone no

Data Base week3_1

  1. Problem solving - practical job
  2. Understanding consolidating - practical exam
Exam
  1. close book
  2. open book (use anything ex. internet)
Flat Table Problem
  1. repetition
  2. Anomalies (Data integrity)
  1. update: many times
  2. insert: need all information or some information NULL
  3. delete: vital information lost
column : class
row : attribute
cell : object
table : entity

Computer Consept week3_1

RAM : for fast
  • fetch
  • execute
  • decode
  • write - back
FSB (Front Side Bus) : internal clock GHz/sec

CPU = brain
FSB = nervous system

Cache Memory
HD → RAM → Cache memory (L1,L2,L3)
permanent   temporary

Combination
  • Memory
  • RAM
  • CPU
  • FSB
HD : dot not portable
CD/DVD : pit portable

IDE : slower
SATA : faster

2010/02/09

Buy 1 Get 1!!


"Buy 1 Get 1!!" is the most populer way to sell products in New Zealand. When I went to an ice cream shop and ordered double ice cream, thery gave me tripule ice cream!!
They launched a new flavour of Manuka Honey now, so it is trial to order an ice cream getting one more ice cream:)

1個買うともう1個ってこっちではとってもポピュラーな販売手法だけど。アイスまでBuy 1 Get 1!! でした。ダブルのアイスを頼んだところ、マヌカハニーフレーバーを新発売したので、おまけにつけてくれて、なんと3段^^
食べすぎ!?

HIV Screen Test



I wanted to extend my student visa, so I had to take a medical check. The medical check was required HIV screen test, other blood test and a chest's X-ray test.
I have never checked HIV screen test. One week later, I got the result, which is no problem. Also, I got my chest of X-ray:)

スチューデントビザを延長するために必要なメディカルチェックをうけました。メディカルチェックはHIVテストや、血液検査、肺のレントゲンの結果が必要。
HIVテストなんて受けたことなかったのでちょっと緊張。1週間後、健康ですの結果をもらって、レントゲンもこっちは自己保管みたい^^

2010/02/08

System development integration Week2_1

Software Development Life Cycle (SDLC)


  1. Requirement (Analysis)
  2. Design
  3. Implementation
  4. Testing
  5. Deployment
  6. Maintenance
Waterfall Model
*It must be reviewed all broader concept phases before next step.


  • System Requirement Definition (How many users? How many Locations?)
  • Software Requirements Analysis
  • Preliminary design
  • Detailed design
  • Coding and unit testing
  • Component integration and testing
  • Integration testing
  • System testing
  • Maintain software
- Pros

  1. System is well documented.
  2. Phases correspond with project management phases.
  3. Cost and schedule estimates may be lower and more accurate.
  4. Details can be addressed with more engineering effort if software is large or complex.
- Cons


  1. All risks must be deal with in a single software development effort.
  2. Because the model is sequential, there is only local feedback at the transaction between phases.
  3. A working product is not available until late in the project.
  4. Progress and success are not observable until the later stages. If a mistake or deficiency exists in the documentation of earlier phases, it may not be discovered until the product is delivered.
  5. Corrections must often wait for the maintenance phase.
- Concluding


  • The waterfall model can be successfully used when requirements are well understood in the beginning and are not expected to change or evolve over the project. Project risks should be relatively low.

Incremental Model
- Pros


  1. Provides some feedback, allowing later development cycles to learn from previous cycles.
  2. Requirements are relatively stable and may be better understood with each increment.
  3. Allows some requirements modification and may allow the addition of new requirements.
  4. It is more resposive to user needs than the waterfall model.
  5. A usable product is available with the first release, and each cycle results in greater functionality.
  6. The project can be stopped any time after the first cycle and leave a working product.
  7. Risk is spread out over multiple cycles.
  8. This method can usually be performed with fewer people than the waterfall model.
  9. Return on investment is visible earlier for smaller, incremental project.
  10. Testing may be easier on smaller portions of the system.

- Cons

  1. The majority of requirements must be known in the begining.
  2. Formal reviews may be more difficult to implement on incremental releases than on a complete system.
  3. Because development isspread out over multiple iterations, interfaces between modules mesut be well-known defined in the beginning.
  4. Cost and schedule overruns may result in an unfinished sysrtem.
  5. Operations are impacted as each new release is deployed.
  6. Users are required to learn how to use a new system with each deployment.

- Concluding

The incremental model is good for projects where requirements are known at beginning, but which need functionality early in the project or which can benefit from the feedback of earlier cycyles.

Evolutionary Model (Prototyping)

- Pros

  1. Project can begin without fully defining or understanding requirements.
  2. Final requirements are improved and more in line with real user needs.
  3. Risks are spread over multiple software builds and controlled better.
  4. Operational capability is achieved earlier in the program.
  5. Newer technology can be incorporated into the system as it becomes available durinng later prototypes.
  6. Documentation emphasizes the final product instead of the evoluition of the product.
  7. This method combines a formal specification with an operational prototype.

- Cons

  1. Because there are more activities and changes, there is usually an increase in both cost and schedule over the waterfall method.
  2. Management activities are increased.
  3. Instead of a single switch over to a new system, there is an ongoing impact to current operations.
  4. Configuration management activities are increased.
  5. Greater coordination of resources is required.
  6. Users sometimes mistake a prototype for the final system.
  7. Prototypes changes between cycles, adding a learning curve for developers and users.
  8. Risks may be increased in the areas.

- Concluding

  • The evolutionary model can be employed on the most type of acquisitions. However, it is usually employed on medium to high-risk systems.

Old house (古い家)



In New Zealand, there are almost all old houses. My house is also around 100 years old, but it is still beautiful, because people maintain their house.
My flat mate said buying a new house isn’t a smart idea, because New Zealand houses have often defection. When I started living in new house, this house was leaking of rain. Therefore, the owner sold this defect house.
The smart way of buying a new house is to buy old house.

ニュージーランドは古い家が多い。私の家も100年ぐらいたってるらしい、でも手入れしているからまだぜんぜんきれいだけどねー。
私のフラットメイトが言うには家を買うときは新しい家は買っちゃだめなんだって、ニュージーランドの家は必ず欠陥があるらしい^^
新築の家にフラットで入ったら、外に雨が降ってると家の中にも雨が降ってきたので、結局オーナーもその家を売ったそうです。
一番いいのは古い家を買うのがいいんだって。こうやって聞くと日本の欠陥住宅なんてかわいいもんかも。。。。

2010/02/07

Food court (フードコート)


This is food court in St. Luke's shopping center. This shopping center is near my house and next to city library, so this area is convenient. In weekend, there are a lot of people in the food court.

このフードコートはセントルクスショッピングセンターという私の家の近くのフードコート。隣に市民図書館(Wifiが使える)があるのでとっても便利。週末はたくさんの人がここに集まります。

Computer Consept week2_2

Binary 0,1
Decimal o-9
Bit : binary digit (data transfer rate)
byte : 8bit o-9, A-Z

System Unit
  • to allow upgrade
Front panel
  • internal drive
  • external drive
  • port (128devices)
PC
  • information system → entertainment system
CPU
  • 3 billion tasks/sec
  • fetch
  • decode
  • execute
  • write-back
RAM ←→ Hard disk (permanent)
  • temporary memory
Homework : search new technology

2010/02/06

Cheese cake & Cappuccino (チーズケーキ&カプチーノ)



I have a day off on Thursday every week. I went to the library and ate cake. Sweets are very good for my mentality. However, New Zealand sweets flavor different from Japanese ones. This cheese cake was sticky, but it's not really bad:)

毎週木曜はお休みになったので、図書館へいってケーキを食べた。甘い物は私の精神安定剤。
が、しかし、ニュージーランドのケーキはたいてい見た目と味が日本のと違う。このチーズケーキはちょっと粘りけというか説明が難しいんだけど、あった。まーでも味はそんなに悪いわけではないので良しとしよう。

2010/02/05

PHP Aplication


These days, I have studied about PHP & SQLite. Now I am making "Life expense application", which is a very compact program. I use iphone application to record my life expense, but sometimes I think this application is not convenient. Therefore, I want to make it.
First, I thought I could make it one day, however, I have made for 4 days. Maybe my plan is a little bad. For example, I realized I can't use int type for amount, because $ has a decimal:)

このごろ、PHPとSQLiteを勉強していて家計簿ソフト(そんな大がかりなもんじゃないけどね)をつくってます。今はiphoneアプリをつかっているのですが、あまり使い勝手がよくないのでつくってます。で、最初は1日でできちゃうなーなんて思ってたものの作り始めてすでに4日。たぶんプランニングが甘かったのね

Bagles (べーぐる)



I like bagles. My flat mates gave me hand made jam, so I wanted to eat it with this jam.
ベーグルが好きなので、ベーグル買いました。フラットメイトが手作りジャムをくれたので、そのジャムと一緒に食べようと思って。。。。



It was cheap, but....
とっても安かったんだけどね。。。。



Maybe someone mistook. It wasn’t contained poppy seed. I think it is clear to undearstand.
だれかが間違えたんだろうねー。ポピーシードは入ってないよ。でも見ればわかる!

2010/02/04

System Development Integration Week2-1

Week5 Exam (close cook)
Design : functionality
Feasibility : applicable, solution
Find solution (not answer)
Analysis phase
  • direct observation (must contained)
  • prototype (must contained, even though we chose water fall.)
stake holder : affect company directly /indirectly
Share holder : financial input

C# week2_2

Rule
  1. define variables
  2. name first letter is letter or underscore
  3. define & declaration
  4. variable can take two values
Casting
  • implicit data type casting (widening data conversion) automatically
  • explicit data type casting (narrow data conversion) if we don't indicate, it doesn't work.
ex.
1) OK widening data conversion
int i =10;
double d = i;
2)Error narrow data conversion
double d = 10.5;
int i = d;
3)OK narrow data conversion
double d = 10.5;
int i = (int)d;
4)Error data type conversion must be compatible (changeable).
string s = "abc";
double d = (double)s;
5)OK char:0-255
char c = 'A';
int j = c;
6)Same meaning
int i = 100;
long l = (long)i; / long l = 100L;

Data Base week2_2

Important points
  • repetition,redundant (同一項目の重複を避ける)
  • referential(参照する)
  • integrity (完全性)

Anomalies
  • Insert
  • Update
  • Delete
Primary key (unique key)
Foreign key (to refer from other tables)
Composite key(the key is made up of more than one key)

Homework
word excise file
UA-9417263-1