Question

Write an essay on the following case study You are a new hire at a large software firm and have been working overtime for the last two months trying to complete the final testing of a new software release for the firm's flagship productwhich is used by thousands of organizations worldwide. Unfortunately, the software has many bugs and testing has taken weeks longer than expected. This afternoon your boss stopped by and asked you to "sign off on the completion of your portion of the testing. He explains that the project has gone over budget and is in danger of missing the committed release date for customers. When you object because you feel the software is still buggy, he says not to worry, whatever bugs remain will be fixed in the next release of the software. What do you do? Source: Reynolds, G.W. (2019)Ethics in Information Technology (6th ed.)Cengage Instructions: You must present an introduction (or backgroundto your topic and your essay (1 mark); present a comprehensive analysis of the identified related ethical issue(s) using appropriate Code of Professional Conduct to support your analysis (6 marks; present a conclusion that briefly outlines your point of view 2 marks); and ensure that your essay is well written and structured . You are not required to include any references in your essay, but where applicable you should cite relevant researchers support your arguments, State any assumptions before you start writing your essay marks)

Answer 1

Developing and testing a software require much time and dedication. A software may have so much bugs and the bugs should be cleared as much as possible before the release. Releasing an incomplete product with bugs to the market cannot be appreciated. First impression is the best. The case is explaining there are so much bugs, and therefore the chances for encountering an error while using the application by customer is very high. A company should not make a try on such a chance. This will endup in loosing many customers and clients.

When an application is releasing, it should be able to impress customers in the first stage of usages. Any problem encountered later can be treated later but initially there should not be any bugs. But the bugs identified in the initial stage itself will make a very bad impression and under rating of the application.

The idea is not care about budget and date, the idea is to publish a reliable well structured product which makes the customers perky while using. The budget and all can be compesated later with the next update probably but the lost customers cannot be returned. Therefore while releasing a product, the product should be perfect.

Next issue is the chances for vulnerabilities and attacks. If an applicaion is carrying so much bugs, the attackers may exploit it and pave a path to intrude. This will endup in the total collapse of the application backend or data base. They may even intrude to customer databases and breach the valuable datas. All these will result in the fall of the company. Any such risks should not be given a chance while releasing an application.