Ethical Issues in Information Technology covers the historical, social, and economic considerations of the ethics discipline as it applies to computing. It includes the study of professional conduct, risks and liabilities, and intellectual property as they relate to the software engineering and computing professions, and it is taught through case studies drawn from software engineering and computing practice.
Within the SCNS taxonomy, CIS is the Computer Information Sciences prefix, and the 4000-level number places this in the upper division — the senior year of a B.S. in computer science, software engineering, or information technology. Daytona State publishes it at 1 credit with prerequisite ENC1101, offered summer and fall. It appears at approximately three Florida institutions.
Worth flagging prominently because the assumption runs the other way. Daytona State publishes CIS4250 at one credit — a short, focused course rather than a full-semester ethics survey. Two practical consequences: a student planning a term's credit load should not budget three credits for it, and a student who needs to fill a three-credit requirement will need something alongside it.
Credit values for computing ethics courses vary substantially across institutions, from one-credit seminars to three-credit courses with substantial writing. Confirm the value at your own institution before building a schedule around it, and expect the depth to scale accordingly.
This is a required professional course rather than a career pathway. Its practical relevance is direct and worth stating:
SOC codes 15-1252 Software Developers, 15-1212 Information Security Analysts, and 11-3021 Computer and Information Systems Managers.
The distinction the course exists to establish. "Is it legal?" and "should I do it?" are separate questions, and computing produces a steady supply of situations where the answers differ.
Practices that are lawful and ethically contested: extensive behavioral data collection under a consent that nobody reads; dark patterns that make cancellation deliberately difficult; shipping software with known defects because the release date is fixed; and algorithmic decision-making whose outputs are disparate but whose inputs contain no protected attribute. Conversely, some ethically defensible actions carry legal risk — security research and disclosure being the standard example.
The professional framing worth carrying: the law is a floor, not a ceiling, and "it's legal" is an answer to a different question than the one being asked. Students who leave the course able to identify which question they are answering have got the main thing.
The heart of the course, and the reason it uses case studies rather than abstractions.
Software controls medical devices, vehicles, aircraft, power systems, and financial infrastructure, and defects in it have killed people. The Therac-25 radiation therapy machine delivered massive overdoses through a race condition combined with removed hardware interlocks and inadequate reporting of earlier incidents; the Boeing 737 MAX MCAS system's behavior and the decisions surrounding its disclosure and certification were central to two fatal accidents; the Volkswagen emissions defeat device was software written deliberately to detect testing conditions and behave differently.
What the cases teach in common is that the failures were organizational as well as technical. Engineers raised concerns that did not travel upward; schedule pressure displaced verification; and responsibility was distributed until nobody held it. That pattern is the thing to recognize, because it recurs in ordinary workplaces at lower stakes.
The professional obligations that follow are stated plainly in the ACM/IEEE code: approve software only if you have a well-founded belief it is safe and meets specifications; disclose danger; be honest about limitations; and accept responsibility for your own work. These are not aspirational — they are the profession's stated standard, and a graduate should be able to quote them.
The most immediately practical content. Computing graduates routinely mishandle intellectual property without malice.
The current wrinkle: AI code-generation tools raise unresolved licensing and provenance questions, since models are trained on code under varied licences and may reproduce it. Organizations have adopted differing policies, courts are actively considering the questions, and rule 11 applies — verify your employer's policy and the current legal position rather than assuming.
The content students find most uncomfortable and most valuable. The professional codes contemplate that a practitioner may face a situation in which an employer's direction conflicts with public safety or professional obligation.
What the course should convey honestly: escalate internally first and in writing — a documented, dated concern raised through proper channels is both the ethical first step and the practical protection; document contemporaneously; understand that legal whistleblower protections are narrow, sector-specific, and slow; and recognize that the personal cost is frequently high even when the whistleblower is entirely vindicated.
None of that argues against it. It argues for knowing the terrain before standing on it, and for recognizing that the more common and more useful intervention is the early one — raising a concern while it is still a design question rather than a scandal.
This course appears at roughly three institutions statewide, which is a small base. Content, credit value, and emphasis vary more than they would for a widely taught course, and one of the three may be a private institution rather than a Florida public college. Read your own institution's catalog description and syllabus rather than assuming this guide describes your section exactly, and have any transfer evaluated in writing.
Daytona State publishes CIS4250 at 1 credit with prerequisite ENC1101, offered summer and fall. The 15 contact hours follows the standard one-credit convention. The composition prerequisite is meaningful: assessment in an ethics course is written argument, and a one-credit course concentrates that work rather than diluting it.
Expect the case study method — a scenario, a structured analysis identifying stakeholders and obligations, and a defended recommendation. The skill being built is not agreement with a particular position but the ability to reason to a defensible one and state why, including acknowledging the strongest opposing argument. That is what distinguishes a professional judgment from an opinion.
The first digit of an SCNS number denotes the year of offering, not transferability. Courses at the 1000 and 2000 levels transfer transparently between Florida public institutions, and 3000 to 4000 is unproblematic since both are upper division. The boundary that actually matters is 2000 to 3000, where lower-division credit generally cannot satisfy an upper-division requirement.
CIS4250 is upper division: a lower-division ethics or philosophy course will not substitute for it in an ABET-accredited computing program, because the requirement is for ethics within the computing discipline. Students transferring should have it evaluated specifically against the receiving program's professional responsibility requirement rather than as a general humanities course.
Generated September 2, 2026 · Updated September 2, 2026