One important concept in Business Systems Analysis and Design is Systems Theory.
At first, systems theory might sound like a purely theoretical topic. However, it is directly connected to the applications we build, the databases we design, and the business processes we automate.
In this article, let's explore the fundamentals of systems theory using practical examples that make sense to IT students and aspiring developers.
What Is a System?
A system is a collection of interconnected parts that work together to achieve a common objective.
Think about a restaurant management application. It may contain several components, including:
- Customer management
- Menu management
- Order processing
- Inventory management
- Payment processing
- Reporting
Each component performs a specific function, but they work together to support the restaurant's operations.
For example, when a customer places an order, the system records the order, updates the relevant order status, and may adjust inventory when ingredients are consumed.
The components depend on one another to help the application achieve its overall purpose.
1. Understanding the Properties of a System
A system has several important properties that help us understand how it works.
Input
Input refers to the data or resources entering a system.
In a payroll application, inputs might include:
- Employee details
- Hours worked
- Basic salary
- Allowances
- Applicable deductions
Processing
Processing refers to the operations performed on the input to produce a useful result.
For example, a payroll system calculates an employee's gross salary, deductions, and net salary according to the applicable payroll rules.
Output
Output is the result produced by the system after processing the input.
In the payroll example, outputs may include payslips, payroll reports, and payment instructions.
The basic relationship can be represented as:
Input → Processing → Output
This pattern appears in many applications, from online shopping platforms to banking systems.
Subsystems
A subsystem is a smaller system that performs a particular function within a larger system.
For example, an accounting system may contain:
- Sales ledger
- Purchase ledger
- Payroll
- General ledger
Each subsystem has its own responsibilities, but together they support the organization's accounting activities.
System Boundaries and Environment
A system boundary defines what is included in a particular system and what lies outside it.
The environment consists of external people, processes, organizations, or systems that interact with the system being studied.
Consider an online shopping application. Its boundary might include product listings, shopping carts, and order processing. External payment gateways, delivery companies, and customers may be part of its environment.
Defining these boundaries is important during systems analysis because it helps developers and business analysts determine which processes belong to the project and which depend on external systems.
Systems Are Hierarchical
Systems can be organized into levels.
A subsystem can belong to a larger system, while that larger system can itself be part of an even bigger system.
For example:
Sales ledger → Accounting system → Business information system
Understanding this hierarchy helps analysts break complex systems into smaller, more manageable components.
2. Deterministic vs. Probabilistic Systems
Systems can also be classified according to how predictable their outcomes are.
Deterministic Systems
A deterministic system produces predictable results when the same inputs, conditions, and rules apply.
For example, imagine a program that calculates the total price of products:
def calculate_total(price, quantity):
return price * quantity
print(calculate_total(2000, 3))
The output is:
6000
Given the same inputs and unchanged rules, the function returns the same result.
Traditional computer programs generally execute their instructions deterministically, although a complete application may interact with external services or other components whose outcomes are less predictable.
Probabilistic Systems
A probabilistic system involves uncertainty. Its outcomes cannot always be predicted with complete certainty, although probabilities or likely outcomes may be estimated.
Examples include:
- Card games involving shuffled cards
- Weather forecasting systems
- Business forecasts affected by market changes
- Predictive models that estimate the likelihood of customer purchases
For example, a business might use historical sales data to estimate the probability that demand for a product will increase next month.
The estimate can support planning, but it cannot guarantee the outcome.
The main difference: Deterministic systems produce predictable results under the same conditions, while probabilistic systems involve uncertainty.
3. Open vs. Closed Systems
Another way to classify systems is by how they interact with their environment.
Open Systems
An open system interacts with its environment by receiving inputs and producing outputs.
For example, an e-commerce application interacts with customers, payment providers, warehouse systems, and delivery services.
A typical order process might look like this:
- A customer submits an order.
- The application validates the order.
- A payment provider processes the payment.
- The system records the order status.
- A delivery service receives the information needed to fulfil the order.
Because the application exchanges information with people and external services, it is an example of an open system.
Closed Systems
A closed system is treated as isolated from its environment for the purpose of analysis.
In practice, completely isolated business systems are uncommon. The term is often useful when studying a process independently from its surrounding environment.
For example, a business analyst might examine only the internal salary calculation process within a payroll department, temporarily excluding recruitment, banking, and other departmental activities.
This does not necessarily mean the payroll system has no external interactions. It means the analysis focuses on a defined boundary.
Can the Same System Be Open and Closed?
Yes. A system can be viewed differently depending on the boundaries and perspective used.
For instance, an analyst may study payroll calculations as a standalone process. Another analyst may examine the entire payroll operation, including employee records, bank payments, and accounting.
This is why defining system boundaries is a fundamental part of systems analysis.
4. Quantitative vs. Qualitative Systems
Systems can also be distinguished by the types of information they process or the outcomes they produce.
Quantitative Systems
Quantitative systems deal primarily with numerical and measurable values.
Examples include:
- Accounting systems
- Payroll applications
- Inventory management systems
- Sales reporting systems
A sales system might calculate revenue using:
Revenue = Unit Price × Quantity Sold
If a business sells 10 products at KSh 1,500 each, the total revenue from those sales is KSh 15,000, assuming no discounts or adjustments.
Quantitative information makes it easier to perform calculations, compare results, and measure performance.
Qualitative Systems
Qualitative systems focus on qualities, experiences, and outcomes that may be difficult to express using numbers alone.
Examples include:
- Customer satisfaction assessments
- Employee feedback systems
- Service quality evaluations
- User experience research
For instance, a company might collect customer comments about whether its delivery service is reliable, friendly, or convenient.
Although qualitative information can sometimes be categorized or converted into numerical ratings, the underlying focus is on understanding qualities and experiences.
The main difference: Quantitative systems emphasize measurable numerical values, while qualitative systems emphasize qualities and less directly measurable outcomes.
5. Why Systems Theory Matters in Software Development
Understanding systems theory helps developers design applications that solve real problems rather than simply writing isolated pieces of code.
Before building a system, developers and business analysts should ask:
- What is the system's main objective?
- What inputs does it require?
- What processing must take place?
- What outputs should it produce?
- What subsystems are required?
- Where should the system boundary be drawn?
- Which external systems will it interact with?
- Which outcomes are predictable, and which involve uncertainty?
Consider a restaurant management system.
The menu, orders, inventory, and payments may be separate subsystems. The application receives inputs from customers and employees, processes orders, and produces outputs such as receipts and reports.
It also interacts with its environment through payment services, suppliers, and customers.
Applying systems theory helps developers understand these relationships before designing the database, APIs, and business logic.
Conclusion
Systems theory provides a foundation for understanding how interconnected components work together to achieve a common objective.
The key concepts covered in this article are:
- System properties: Inputs, processing, outputs, subsystems, boundaries, and environments.
- Deterministic systems: Produce predictable results under the same conditions.
- Probabilistic systems: Involve uncertain outcomes.
- Open systems: Interact with their environment.
- Closed systems: Are treated as isolated within a particular analysis.
- Quantitative systems: Focus on numerical and measurable information.
- Qualitative systems: Focus on qualities and less directly measurable outcomes.
As IT students and aspiring developers, we should remember that a business application is more than code, tables, and endpoints. It is a system of connected components that must work together to fulfil a purpose.
My takeaway: Before designing a software solution, understand the system as a whole, identify its components, define its boundaries, and determine how information flows between them.
That understanding is one of the first steps toward building reliable and useful business systems.
This article is based on my learning in Business Systems Analysis and Design as a Bachelor of Information Technology student. I hope it helps fellow students and beginner developers connect systems theory with practical software development.
Top comments (0)