Sunday, April 13, 2008

1.
Technician - He have to understand how to use calibrating a fule value. He has responsibility to read a documentation and need to know which value will give a error before using the program because he will be the one who will use this program. Without test, this kind of problem
can occur. If he did the test, he would be put value zero.

Person who wrote the fuel-value calibration program - He has responsibility to check the program which works fine. When he modified or changed some code, he needed to bug from the beginning that changes works fine or not. Depending on how much time he spend to build this program, the bug time will be longer. He need to think all the cases that may give an error.

Person who selected and purchased - He has responsibility to know about the program. This program will use for his company. Then he needs to do research about the program and gets information. After that, when he purchases this program, he needs to check and run the program that it works fine or not. It means that this person should have some knowledge of this program that how does it work. Another option is that he can go with technician that he can check the program and if he says ok, then they can purchase the program. Or they can make an insurance for the program that if there is a problem on the program, the company of program will do something for them.

The software company that sells the network software - When the company sells the products, it needs to tell about the good, but also it needs to mention the bad or weak of the program.
Just saying about the good, then how the company will handle if the program have errors. Every program can not be a perfect because programs are humans that they can miss some of the cases. These cases may appear when users are using it. So they need to make some of way to handle this problems. For exmaple, the insurance may be one of the solve this problem.

The captain of the ship - The captain is controlled all kinds of things of the ship. Without his permission, this software can not install in the ship. So captain need to what the problem is all about and he need to ask a technician to test the program before installing it. And After installed the program, they have to test again to make sure it work correctly.

2. D-U-E Process
Describe - The first day of Service Learning, partners who are from the company and we (I and Derrick) decided to make a web application which controls the database. We want to use django to make it, but their ITS people disagreed with it. They just gave their own opinions that it would be not worked at all. We thought that it would be alright to build using django, but their opinions were very strong that we gave up to build the web application. Rather than making it, we got other job to do such as work on the survey and make Microsoft Access more friendly. What I felt was that it was really hard to convice people who are in the real world.

Understand - I could understand what their ITS people disagreed with the our way to make the web application, but what I thought was they did not listen to us. I thought that we could not solve their opinions which gave us some problems about the web application. This would be the biggest reason that they did not listen to us. We tried to figure out, but it was really hard to solve. We were doing service learning, not work for a job.

Encourage Communication- The acutal problems which ITS people came with are 1) who will fix or control the web application when it breaks down or it has a problem? they want to have a supporter after we leave. 2) How about the security? The content of database is very important to them, so they want to very secure. I never thought about this kind of problems before I met them. Also, ITS people said that they can make a web application for our partners, but it was only saying. After that, there was no action. I thought, this is kind of a failure when I was doing my service learning because I could not convince them. My expectation of service learning is changed a lot compare to before.

No comments: