Please enable JavaScript.
Coggle requires JavaScript to display documents.
Case Study: Privacy – Diane asked to build insecure personnel database -…
Case Study: Privacy – Diane asked to build insecure personnel database
Choice 1: Build the system as requested
Pros: Meets client demands and saves money
Pros: Preserves business relationship
Cons: Sensitive employee data at risk
Cons: Violates professional duty to protect privacy
Ethical Theory: Egoism
ACM Imperative: 1.7 Respect Privacy
ACM Imperative: 1.8 Honor Confidentiality
Choice 3: Educate the client and persuade them to adopt stronger security
Pros: Promotes understanding of risks
Pros: May achieve compromise that balances cost and security
Cons: Client may still reject stronger security
Ethical Theory: Utilitarianism
ACM Imperative: 2.7 Improve Public Understanding of Computing
ACM Imperative: 3.5 Organizational Leaders Must Protect Privacy
Choice 2: Refuse to build the system without proper security
Pros: Protects employee privacy and rights
Pros: Upholds professional integrity
Cons: Risk of losing client or contract
Ethical Theory: Deontology
. ACM Imperative: 1.2 Avoid Harm
ACM Imperative: 1.7 Respect Privacy
Should We Have a Professional Code of Ethics?
Yes: Provides guidance and shared standards
Yes: Protects both professionals and the public
Yes: Builds accountability and trust
Other Cases Still Applicable Today?
Yes: Data privacy remains critical
Yes: Software risks and liability still common issues
Yes: Fairness and discrimination remain urgent
My Choice
My Choice: Choice 3
Why: Balances duty to protect privacy with maintaining professional relationship
Why: Aligns with ACM Code
Why: Practical compromise before outright refusal