Here are 100 key things you need to know about Information Systems (IS) typically covered across a 4-year BCom Information Systems degree, structured for clarity:
Definition of Information Systems (IS)
Components of IS: hardware, software, data, procedures, people
Types of IS: TPS, MIS, DSS, EIS, ESS
Data vs Information vs Knowledge
Role of IS in organizations
IS supporting operational, tactical, and strategic levels
Systems theory and thinking
Socio-technical systems concept
Business process automation and re-engineering
Information as a business resource
Basic computer architecture (CPU, RAM, storage)
Input, output, storage devices
Cloud computing concepts
Networking basics (LAN, WAN, protocols)
Server-client models
Data centers and virtualization
Emerging hardware trends (IoT, edge computing)
Mobile computing and BYOD impact
Hardware scalability considerations
Green IT concepts
System software vs application software
Operating systems fundamentals
Enterprise systems (ERP, SCM, CRM)
Database Management Systems (DBMS)
Software development life cycle (SDLC)
Agile, Waterfall, and hybrid methodologies
APIs and web services
Software testing and QA
Open-source vs proprietary software
Software licensing and intellectual property
Relational database concepts (tables, keys)
SQL basics and advanced queries
Data modeling (ER diagrams, normalization)
Data warehousing and ETL processes
Big data concepts and technologies
Data quality and data governance
Master Data Management (MDM)
Data privacy and protection
NoSQL databases overview
Data visualization and reporting tools
Requirements gathering techniques
Use case modeling and user stories
Process modeling (DFDs, BPMN)
Object-oriented analysis and design
Feasibility analysis (technical, operational, economic)
Prototyping and wireframing
User interface and experience design
Change management principles
Testing and validation
System implementation strategies
OSI and TCP/IP models
IP addressing and subnetting basics
Network security fundamentals
Wireless networking standards
VPNs and remote access
Internet and intranet architectures
Email systems and protocols
Network monitoring tools
VoIP basics
Firewalls and network protection
Information security principles (CIA triad)
Common threats and vulnerabilities
Cryptography fundamentals
Authentication and authorization
Security policies and governance
Risk assessment and mitigation
Disaster recovery planning
Business continuity planning
Regulatory compliance (GDPR, POPIA, PCI DSS)
Security audits and penetration testing
E-commerce models (B2B, B2C, C2C)
Payment systems and gateways
Digital marketing basics
Mobile commerce
E-commerce platform architecture
Customer relationship management online
E-commerce security
Supply chain integration
User experience in online environments
Digital transformation principles
Aligning IS strategy with business strategy
IT governance frameworks (COBIT, ITIL)
Project management principles (PMBOK)
Budgeting and cost management in IS
Service management concepts
Vendor and contract management
Change management in IS
Innovation management in IS
Measuring IS effectiveness and ROI
Ethical and legal issues in IS
Artificial Intelligence and machine learning
Blockchain fundamentals
Internet of Things (IoT)
Cybersecurity trends
Data analytics and business intelligence
Robotics Process Automation (RPA)
Cloud services (SaaS, PaaS, IaaS)
Soft skills: teamwork, communication, and leadership
Critical thinking and problem-solving in IS
Career pathways in IS and professional certifications
Types of Information Systems (IS): TPS, MIS, DSS, EIS, ESS, as required in your BCom Information Systems studies:
What it is:
Handles day-to-day business transactions efficiently and accurately.
Collects, stores, modifies, and retrieves daily transactional data.
Examples:
Point-of-Sale (POS) systems in retail.
Payroll systems.
Inventory management systems.
Key features:
High volume processing.
Routine, structured tasks.
Reliability and consistency.
What it is:
Converts data from TPS into meaningful summarized reports for middle management to monitor organizational performance and make routine decisions.
Examples:
Monthly sales reports.
Budget summaries.
Production scheduling.
Key features:
Periodic reporting (daily, weekly, monthly).
Supports tactical decision-making.
Uses structured internal data.
What it is:
Helps managers make non-routine, semi-structured decisions using analytical models, data analysis, and “what-if” scenarios.
Examples:
Sales forecasting models.
Risk analysis tools.
Budget planning tools.
Key features:
Interactive and flexible.
Supports problem-solving.
Uses internal and external data with analytical tools.
(Also called ESS – Executive Support Systems)
What it is:
Provides top executives with easy access to key internal and external information for strategic decision-making.
Examples:
Dashboards showing KPIs.
Market trend analysis tools.
Competitive intelligence systems.
Key features:
Highly summarized and graphical information.
Drill-down capabilities for detailed views.
Supports unstructured decision-making.
Often used interchangeably with EIS.
What it is:
Designed for senior executives to monitor the organization’s health and performance easily.
Examples:
Balanced Scorecards.
Strategy maps with real-time data.
Key features:
Strategic focus.
Data from internal + external sources.
Easy-to-use interfaces with advanced visualization.
System
Main User
Purpose
Example
TPS
Operational staff
Record routine transactions
POS, payroll
MIS
Middle management
Monitor & control operations
Sales reports
DSS
Managers
Support complex decisions
Forecasting
EIS/ESS
Executives
Strategic insight
Dashboards
Here is a clear, BCom-level explanation of Systems Theory and Systems Thinking for your Information Systems studies:
Systems Theory is a framework for understanding complex entities as systems made up of interrelated and interdependent parts working together to achieve a common goal.
Developed from biology and engineering (Ludwig von Bertalanffy, 1940s), later applied to organizations and information systems.
A system:
Has inputs, processes, outputs, and feedback loops.
Exists within an environment.
Seeks equilibrium (balance) while adapting to changes.
System – A collection of components working together (e.g., an organization, a computer system).
Subsystem – Smaller systems within a system (e.g., HR system within an ERP system).
Boundary – Defines what is inside vs outside the system.
Environment – Everything outside the system that affects it.
Input – Resources/data entering the system.
Process – Transformation of inputs into outputs.
Output – The result/product of the system.
Feedback – Information about output used to adjust processes.
Open vs Closed Systems:
Open systems interact with the environment (most organizations).
Closed systems have limited interaction with the environment.
Systems Thinking is a mindset and analytical approach to view problems holistically, understanding:
The interconnections between system components.
How changes in one part affect other parts.
That problems are often caused by the system’s structure, not isolated events.
Example in business:
If sales drop, instead of only blaming sales staff, Systems Thinking looks at:
Marketing effectiveness,
Product quality,
Customer service processes,
Market conditions,
to find the root causes.
✅ Helps understand how IS interacts with other business functions.
✅ Guides system design with consideration of users, data, processes, and environment.
✅ Aids in problem-solving by seeing the big picture rather than isolated issues.
✅ Encourages continuous improvement through feedback loops.
✅ Supports alignment of IT systems with organizational goals.
When implementing a new ERP system:
Systems Theory: Recognize it affects finance, HR, supply chain (subsystems), and is influenced by regulatory environments (environment).
Systems Thinking: Anticipate how automating finance might impact HR reporting or inventory levels, requiring change management and training.
Aspect
Systems Theory
Systems Thinking
Definition
Framework to analyze systems
Mindset to understand systems holistically
Focus
Components, processes, feedback
Interrelationships and patterns
Application
System design & analysis
Problem-solving & decision-making
Here is a clear, BCom Information Systems-level explanation of the Socio-Technical Systems (STS) concept:
Definition:
The Socio-Technical Systems (STS) concept views an organization (or system) as composed of two interdependent parts:
1️⃣ Social System – people, culture, roles, relationships, and skills.
2️⃣ Technical System – tools, technologies, procedures, and processes used to perform tasks.
The key idea:
To optimize overall performance, both the social and technical systems must be designed and improved together, not in isolation.
Developed in the 1950s by Eric Trist and Fred Emery (Tavistock Institute, UK) while studying coal mining productivity.
They found that ignoring social factors (team structures, motivation) in favor of only technical efficiency led to poor outcomes.
✅ Joint Optimization – optimize both social and technical systems together for better results.
✅ Interdependence – changes in technology affect people and vice versa.
✅ Employee Involvement – users should participate in system design to improve acceptance and effectiveness.
✅ Adaptability – systems should allow flexibility for human judgment.
✅ Quality of Work Life – system design should enhance job satisfaction and productivity.
Technical Subsystem
Social Subsystem
Machines, hardware
People, teams
Software, processes
Culture, norms
Data flows
Communication
Procedures
Leadership, motivation
Both interact with the environment (external factors).
1️⃣ ERP Implementation:
Technical: software modules, data integration.
Social: user training, role changes, resistance to change.
STS ensures that user needs, workflows, and organizational culture are considered alongside software configuration.
2️⃣ Call Center Systems:
Technical: ticketing systems, call routing software.
Social: job design, stress levels, communication patterns.
STS would design the system to reduce repetitive stress while improving response times.
✅ Prevents system failures caused by ignoring user needs.
✅ Encourages user acceptance and effective system use.
✅ Improves productivity and employee satisfaction.
✅ Supports change management during system implementation.
✅ Ensures system design aligns with organizational culture and processes.
STS = Social + Technical subsystems working together.
Focus on human factors and technology simultaneously.
Leads to better system performance, user satisfaction, and organizational effectiveness.