Ethical Dilemma in Software Development

The assignment presents a scenario where a software project is expected to go live on Monday, but has not undergone testing due to the absence of a tester. The project manager must decide whether to launch the system despite the lack of testing or take time to ensure its quality. This dilemma requires consideration of the potential risks and consequences of launching untested software, including vulnerability to attacks and damage to the organization's reputation.

SCHOOL OF COMPUTING AND MATHS, Charles Sturt University
IT Ethical Dilemma / Un-tested System
Assignment 1: Doing Ethics Technique
Your Name
Student Number
Word Count: 1000

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
Q1. What's going on?
The main thing, which is seen in the scenario, is that the organization had committed
to the client that the project would be going live on Monday. On the other hand, it is seen that
the project had not gone through the testing phase due to the absence of the tester. There can
be difference types of problem if the software is launched without any type of testing not
done on the software. The main concern sector is that the project manager wants the software
to be launched anyhow on the time which is given to the client that is on Monday.
Q2. What are the facts?
The main fact, which is seen from the scenario, is that a system is expected to be live
on Monday as discussed with the client. On the hand it is seen in the later stages of the
scenario that as stated that the system had not gone under the testing phase due to the absence
of the tester. The project manager had instructed the project director to make the system live
on the indicated date as per the planning. If the software is made live, there can be different
types of issue involved into it, which should be given first priority by the end of the
developers.
Q3. What are the issues?
The main issue, which is being faced according to the scenario, is that as per the
planning with the client the project has to go live. As per the absence of the tester, the project
had not gone through the testing phase. The system going live without testing phase may
impose different types of consequence relating to the project. The hackers can easily indulge
into unethical activities, which can have a direct impact on the working of the system.
Q4. Who is affected?
Your Name

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
In this context, it can be stated that the affected person in this scenario is the
organization who would be implementing the project and the organization who would be
delivering the product. Both the sector would be affected in a way that if the delivery of the
product is done without testing and it is made live the hackers can easily get the information
which is stored in the software quite easily. On the other, the reputation of the organization
would be at a stack because it is very much unethical to launch a product without any sort of
testing involved into the concept.
Q5. What are the ethical issues and their implications?
The main ethical issue, which is seen in the scenario, is that making a software live
without testing done on it is very much unethical due to the factor that the system would be
liable to be attacked by intruders. The implication of the aspect of delivering the project
without testing can make the system vulnerable to attacks. Most of the attackers in recent
times try to indulge into system, which does not involve the aspect of security involved into
the concept. It becomes and easy task for the attacker to get into the system when security
aspects are not involved into the system. The main motive of the attacker in most of the
situation is to get the information, which is stored in the system, and use the system for their
own benefit.
Q6. What could have been done about it?
It can be stated in this context that the client was expecting the software to be
launched on Monday (As per the scenario). It is not justifying extending the deadline form
the end of the developer. On the other hand, the aspect of the software not going through the
process of testing and making the software live is taking a risk. The risk can sometimes affect
the overall working of the organization. It can also hamper the overall aspect. It should be the
role of the developing organization to get together all the aspects of the software together and
accordingly make the software live.
Your Name

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
Q7. What are the options?
The main options, which are available from the scenario, can be categorized into three
sections, which are given below:
First section: Ken lets the system go live – The first option, which is stated in the
video, is that Ken lets the system go live. This means that the testing of the software would
not be done and the software would be delivered or made live.
Second section: ken Resigns – The second option, which is stated in the video is that
Ken resign. This can formally be stated, as the software would be delivered without the
testing. This is due to the factor that the head of the organization involved into the case is
willing to deliver the software within the time estimated and prefixed.
Third section: Ken Fights back – The third option which is stated in this context is
that ken fights back this can merely mean that he is not willing to deliver the software to the
client without proper testing involving into it.
Q8. Which option is the best and why?
The best option in regards to the option, which are stated above, would be the third
section, which states that ken would be fighting back. This is stated as the best option due to
the factor that he knows the importance of the testing of the software and knows what would
be the affect if it were made live within the period it is framed to do so. Here it can be said
that the option, which could be followed with it, should be to take some time from the client
and involve the necessary testing into the software. This option would be beneficial from the
point of view of the organization who is developing it and the organization who would be
implementing the software. A software without proper testing is liable to many different
types of issue which should be known by the head of the concern sector.
Your Name

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
Your Name

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
Bibliography
Barr, E. T., Harman, M., McMinn, P., Shahbaz, M., & Yoo, S. (2015). The oracle problem in
software testing: A survey. IEEE transactions on software engineering, 41(5), 507-
525.
Deak, A., Stålhane, T., & Sindre, G. (2016). Challenges and strategies for motivating
software testing personnel. Information and software Technology, 73, 1-15.
Harman, M., Jia, Y., & Zhang, Y. (2015, April). Achievements, open problems and
challenges for search based software testing. In Software Testing, Verification and
Validation (ICST), 2015 IEEE 8th International Conference on (pp. 1-12). IEEE.
Kanewala, U., & Bieman, J. M. (2014). Testing scientific software: A systematic literature
review. Information and software technology, 56(10), 1219-1232.
Karim, N. S. A., Al Ammar, F., & Aziz, R. (2017, September). Ethical Software: Integrating
Code of Ethics into Software Development Life Cycle. In Computer and Applications
(ICCA), 2017 International Conference on (pp. 290-298). IEEE.
Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.
Narayanan, A., & Vallor, S. (2014). Why software engineering courses should include ethics
coverage. Communications of the ACM, 57(3), 23-25.
Wolf, M. J., Grodzinsky, F., & Miller, K. W. (2016). Robots, Ethics and Software–FOSS vs.
Proprietary Licenses. In Computing and Philosophy (pp. 271-282). Springer, Cham.
Your Name

IT ETHICAL DILEMMA/ UN-TESTED SYSTEM
Your Name