In-class post, 07/11/2006
Well we're here once more, this is what sleep deprivation feels like...I almost forgot how it felt. :)
We're continuing with our discussion with Computer Ethics, but Dr. Mohan first went into a small discussion about the various courses that are associated with the I.T. degree, and what they entail.
He then gave good comments about people whose blogs for this course go beyond what he teaches, at how they research further into the various topics and get into greater depth than what is done within class...and that is what he intended for the blogs in the first place.
The template for Dr. Mohan's website was changed, and Dr. Mohan didn't really like how the new template looked, and that brings up another issue, with regards to User Interfaces, and how the interface needs to be easy to use, otherwise users may not be able to use the software efficiently.
He then went into the topic of Vaporware, which is when a company promises a new piece of software, but nothing ever materialises in the end. Also, there is also the issue where products are delayed, due to various reasons, and what has to be done as a result.
One option was to write an anonymous letter to the press, detailing the issue(s) with the software, but that brings up issues, where you as the employee would be reporting the company over such issues, showing a lack of faith with the employer.
Another option is where the software can be released on time (although there are still delays in some cases), but bugs are being worked upon at the same time, and then released in subsequent patches (a la Microsoft). This is often a solution used, but it cannot be used in all situations, since releasing bugs within certain applications can be of severe risk, so it is dependent upon the level of the application.
In virtually every industry, defects can occur - it is dependent upon the rate of defects that can occur that can be acceptable. This is where the feature of a warranty applies, so that way the customer is covered in case of any defect. There are limited warranties, where the company limits itself to handling issues with actual product defects, and comprehensive warranties, which repairs/replaces the product irregardless of the cause of the problem.
Ethics can cross so many topics and borders, but it's up to the professionals within the industry, who are responsible to enforcing ethical standards in the long run. There is a Code of Ethics that exists for Software Engineering, but not necessarily applicable for I.T.
Anyway, I'm done for now, until Thursday.
*wanders around zombie-like......sleeeeeeeeeeeeeeeeep...................zzzzzzzz*
We're continuing with our discussion with Computer Ethics, but Dr. Mohan first went into a small discussion about the various courses that are associated with the I.T. degree, and what they entail.
He then gave good comments about people whose blogs for this course go beyond what he teaches, at how they research further into the various topics and get into greater depth than what is done within class...and that is what he intended for the blogs in the first place.
The template for Dr. Mohan's website was changed, and Dr. Mohan didn't really like how the new template looked, and that brings up another issue, with regards to User Interfaces, and how the interface needs to be easy to use, otherwise users may not be able to use the software efficiently.
He then went into the topic of Vaporware, which is when a company promises a new piece of software, but nothing ever materialises in the end. Also, there is also the issue where products are delayed, due to various reasons, and what has to be done as a result.
One option was to write an anonymous letter to the press, detailing the issue(s) with the software, but that brings up issues, where you as the employee would be reporting the company over such issues, showing a lack of faith with the employer.
Another option is where the software can be released on time (although there are still delays in some cases), but bugs are being worked upon at the same time, and then released in subsequent patches (a la Microsoft). This is often a solution used, but it cannot be used in all situations, since releasing bugs within certain applications can be of severe risk, so it is dependent upon the level of the application.
In virtually every industry, defects can occur - it is dependent upon the rate of defects that can occur that can be acceptable. This is where the feature of a warranty applies, so that way the customer is covered in case of any defect. There are limited warranties, where the company limits itself to handling issues with actual product defects, and comprehensive warranties, which repairs/replaces the product irregardless of the cause of the problem.
Ethics can cross so many topics and borders, but it's up to the professionals within the industry, who are responsible to enforcing ethical standards in the long run. There is a Code of Ethics that exists for Software Engineering, but not necessarily applicable for I.T.
Anyway, I'm done for now, until Thursday.
*wanders around zombie-like......sleeeeeeeeeeeeeeeeep...................zzzzzzzz*
posted by SPK at 11/07/2006 10:15:00 AM
0 Comments:
Post a Comment
<< Home