The Two Key Roles
🔍 Systems Analyst (SA)
Business problem-solver who uses IT to find solutions.
- Needs Technical + Business + People skills
- Also called: programmer analyst, systems consultant, systems engineer
- Designs what the system should do
⚙️ Software Engineer (SE)
Code builder who applies engineering principles to software.
- Designs, develops, maintains, tests, evaluates software
- Works on how the system is built
- SA + SE together = complete product (hardware + software)
SA = "WHAT" · SE = "HOW"
Think of it like a restaurant: the SA is the designer who says "we need a menu with 20 dishes", and the SE is the chef who figures out how to cook them.
Problems Faced by SA / SE
There are 6 main problem areas. Use the mnemonic below to remember them all.
S·D·P·U·C·I
"Software Developers Please Use Code Integrity"
📋 Software Specification
- Most errors traced back to incomplete requirements
- A spec is complete only when it separates wanted from unwanted behaviour
🎨 Design Gaps
- Domain expert designs the system but hands off to a programmer who isn't a domain expert
- E.g. brake engineer → programmer → brake software. Communication gap = bugs
🔥 Extreme Pressure
- "Ship it fast" pressure causes known bugs to be ignored
- Quality cut under time-to-market demands
🏴☠️ Unauthorized Software
- Using open-source without crediting it
- Using illegal/pirated tools
- Hard to maintain systems built on illegal software
🔄 Changes in Software
- "Small fixes" can cause serious reliability drops
- Software maintenance ≠ replacing hardware
- Every change alters the design
👥 Incompetent Staff
- No project management methodology
- Bad planning and estimating
- Not enough senior staff on the team
The 3 Unethical Syndromes
R · S · C
"Really Shady Companies" — Red lies, Sweep-it-under-the-rug, Cancelled vacation
Red Lies
Telling clients/management something you know is false — e.g., "the project is on schedule" when your team knows it isn't. Named "red" because it's blatant deception.
Sweep it Under the Rug
Ignoring unforeseen problems hoping they'll disappear. This leads to much bigger failures down the line. Classic short-term thinking.
Cancelled Vacation Syndrome
Managers pressuring staff to cancel trips or personal time at the last minute for short-term deadlines — sometimes causing real financial loss (non-refundable bookings).
✅ How to Avoid These Problems
- Software Development Methodology: Standard process = controlled progress + fewer errors + legal protection
- Quality Assurance (QA): Built-in testing throughout the development cycle
Safety-Critical Systems
⚠️ What is a Safety-Critical System?
Any system where software failure may cause injury or death.
Examples Antilock brakes · Nuclear reactors · Airplane navigation · Elevators · MRI/CT scanners
Development requires 5 key practices. Mnemonic below:
R·H·T·R·N
"Really Hard To Run Naked" (unusual = memorable!)
Rigorous Process & Documentation
More thorough docs, vigilant checking and re-checking. No shortcuts.
Hazard Log
A logging/monitoring system tracks hazards from project start to finish. The system safety engineer owns this.
Thorough Testing
Decide: how much testing is enough when failure = loss of human life?
Risk Analysis
Formally assess: what can go wrong? How likely? How bad? How to avoid/warn?
Redundancy & N-Version Programming
Multiple interchangeable components for the same function. N independent versions run in parallel; a voting algorithm decides the winner if outputs differ.
Scenario 1 — Anti-Missile System
Military asks for immediate complex modifications within 1 week. The team agrees. Is this realistic? NO — safety-critical software changes require rigorous process. Rushing = catastrophic risk.
Scenario 2 — Fighter Jet Software
QA engineer suspects insufficient testing but signs off under employer pressure. Ethical? NO — personal/professional integrity trumps business pressure in safety-critical contexts.
IT System Administrator Ethics
to Everything
Activity
Responsibility
SysAdmins have privileged access to passwords, emails, databases, and full network activity. This power can be abused deliberately or inadvertently. There are 6 ethical issues:
I · E · S · W · C · F
"In Every System, Whistleblowers Challenge Fees"
| Issue | Situation | Ethical Dilemma |
|---|---|---|
| Privacy Invasion of Privacy | Monitoring employees' emails/browsing | OK if employment contract allows it; still feels invasive |
| Report Equality in Reporting | Deciding what infractions to report | Using personal values = unfair, selective enforcement |
| Info Sensitive Info | Moving to a new company with old employer's secrets | Check non-disclosure agreements; legal + ethical duty |
| ⚠️ Whistleblower | Discovers illegal/unethical company activity | Job security vs. legal/moral duty to report |
| 🔒 Compromising Security | Client asks to skip recommended security measures | Must explain risks; ethically wrong to comply silently |
| 💰 Consultation Fees | Fear of attacks = easy upsell | Playing on fear to overcharge is unethical |
The Slippery Slope
Starts small — "just scanning emails for fun" — and escalates to altering messages, blackmail, or abuse of power. Each step feels minor; the cumulative harm is severe. One rule: don't start.
🤝 Informed Consent Policy
The ethical foundation for SysAdmin policies:
- Users must know the rules they are living under
- Users must know how the system operates in various situations
- No surprises = no claims of unfairness
LOPSA Code of Ethics
LOPSA = League of Professional System Administrators (est. early 2000s). 10-point Code of Ethics for SysAdmins.
PP · PL · CS · ERS · E
"Professional People Please Laws, Communicate Strongly, Educate, Respect Society Ethically"
📜 User Code of Conduct — Key Questions
- Is personal use of company equipment allowed?
- What sites are restricted?
- What counts as harassing communication?
- What changes when working from home?
🔐 Privileged Access Code of Conduct
- Users must acknowledge responsibility for elevated access
- Clear limitations on what can be done with privileges
- Mistakes happen → have backups and retained software sources to limit damage
🏛️ Building a Security Culture
Security = not just technology. It's a culture. All employees must be security-conscious at all times, supporting the IT team. SysAdmins hold enormous power and must model ethical behaviour.
Integrity & Ethical Guidance
🛡️ Analyst Integrity Means…
- Keep employee & corporate data confidential
- Follow through on commitments
- Deal directly with mistakes (no cover-ups)
- Honest, open communication
- Know your limits; ask for help; help others
📚 Sources of Ethical Guidance
- Professional Bodies: codes of conduct (e.g. LOPSA)
- IS Methodologies: structured frameworks ensure completeness & ethical analysis of IT projects
- Deontological approach: following rules regardless of consequences
Quick Self-Quiz
Test yourself — click to reveal the answers.