Introduction to System Analysis and Design

System Analysis and Design (often called SAD) is a process used to create new systems or improve
existing ones in a planned and organized way. These systems could be software applications,
websites, business processes, or even an entire network of computers working together.

Just like how a builder plans a house before building it, or how a doctor examines a patient before
giving treatment, SAD helps us understand problems, find solutions, and then design systems
that work better.

What is a System?

Before we go deeper, let's first understand what a system is.

A system is a collection of parts that work together to achieve a specific goal. These parts could be
people, machines, software, or processes.

For example:

 A banking system helps manage customer accounts, money transfers, and records.
 A school management system helps with student admissions, exams, and attendance.
 A shopping website is a system that helps people browse products, place orders, and make
payments.

So, whenever you see a group of things working together to do a job — that’s a system.

What is System Analysis?

System Analysis is the first step. It means studying and understanding the current system and
identifying any problems or needs for improvement.

For example:

 Why is the system slow?

 Are users facing difficulties?
 Are there repeated errors?
 What do users want in a new system?

System analysts talk to users, look at documents, observe how things are done, and gather as much
information as possible. The goal is to understand the current situation clearly before making any
changes.

Imagine a car mechanic checking a broken car to understand what’s wrong. That’s similar to system
analysis.
What is System Design?

Once the analysis is done and the problems are understood, the next step is System Design.

System Design is about planning a new system or improving the old one based on what was
learned during the analysis. This includes:

 Deciding what features the new system should have

 Designing the layout of the software or interface
 Choosing which technologies to use
 Creating flowcharts, diagrams, and models to explain how the system will work
 Ensuring the system will be user-friendly, fast, and secure

Think of it like an architect creating a blueprint of a building before the workers start building. In the
same way, designers create a detailed plan before programmers write the actual code.

Phases in System Analysis and Design

SAD usually follows certain steps or phases, including:

1. Requirement Gathering – Understanding what users need

2. Feasibility Study – Checking if the new system is possible and cost-effective
3. System Analysis – Studying the current system in detail
4. System Design – Planning the new system
5. Development – Building (coding) the new system
6. Testing – Checking the system for errors
7. Implementation – Installing and using the system
8. Maintenance – Fixing any future issues and updating the system when needed

Why is System Analysis and Design Important?

 It helps build systems that are effective, efficient, and user-friendly
 It reduces mistakes by planning before building
 It ensures that users’ needs are properly understood
 It saves time and money by avoiding rework and failure
 It helps in managing complex projects in a step-by-step manner

Real-Life Example
Let’s say a hospital is using paper records for patients, and it’s causing delays and mistakes. A team
starts a system analysis to find out what the problems are. After talking to doctors and staff, they
learn the system is slow, data gets lost, and it's hard to search records.
Next, the team designs a new digital hospital management system. It allows patient records to be
stored online, can be searched easily, and is secure. After building and testing it, the hospital starts
using it and finds that work is faster, more accurate, and better organized.

System Concept and the Need for System Approach

What is a System? (System Concept)

A system is a set of connected parts that work together to achieve a goal or solve a problem.

You can think of a system like a machine or even your body. Each part has a role, and when all
parts work together properly, the whole system works smoothly.

👉 Examples of systems:

 Computer System – Includes hardware, software, and users working together.

 School System – Includes students, teachers, classrooms, rules, and management.
 Transport System – Includes vehicles, roads, traffic signals, and drivers.

Each of these systems has:

 Inputs (what goes in)

 Processes (what happens inside)
 Outputs (what comes out)
 Feedback (used to improve the system)

Elements of a System

The following diagram shows the elements of a system –

Outputs and Inputs:

 The main aim of a system is to produce an output which is useful for its user.
 Inputs are the information that enters into the system for processing.
 Output is the outcome of processing.

Processor(s):

 The processor is the element of a system that involves the actual transformation of input into
output.
 It is the operational component of a system. Processors may modify the input either totally or
partially, depending on the output specification.
 As the output specifications change, so does the processing. In some cases, input is also
modified to enable the processor for handling the transformation.

Control:

 The control element guides the system.

 It is the decision making subsystem that controls the pattern of activities governing input,
processing, and output.
 The behavior of a computer System is controlled by the Operating System and software. In
order to keep system in balance, what and how much input is needed is determined by Output
Specifications.

Feedback:

 Feedback provides the control in a dynamic system.

 Positive feedback is routine in nature that encourages the performance of the system.
 Negative feedback is informational in nature that provides the controller with information for
action.

Environment:

 The environment is the supersystem within which an organization operates.

 It is the source of external elements that strike on the system.
 It determines how a system must function. For example, vendors and competitors of
organizations environment, may provide constraints that affect the actual performance of the
business.

Boundaries and Interface:

 A system should be defined by its boundaries. Boundaries are the limits that identify its
components, processes, and interrelationship when it interfaces with another system.
 Each system has boundaries that determine its sphere of influence and control.
  The knowledge of the boundaries of a given system is crucial in determining the nature of its
interface with other systems for successful design.

Types of System
1. Physical System vs. Abstract System

 Physical System

 These are real things you can touch and see.

 They are made of physical parts like wires, machines, or people.
 They perform tasks in the real world.

Example:

 A car is a physical system – it has tires, engine, seats, etc., and all parts work together to
transport you.
 A computer is another physical system – its parts like the CPU, monitor, and keyboard
work together to help you perform tasks.

 Abstract System

 These are ideas or concepts, not physical things.

 They exist only in our minds or as drawings and models.
 They help us understand or manage physical systems.

Example:

 A timetable for a school – it's a plan (not a thing you can touch) that tells when each class
happens.
 A mathematical formula is also an abstract system.

2. Open System vs. Closed System

 Open System

 An open system interacts with its environment.

 It takes input from outside, processes it, and gives output.
 It can change or adapt based on feedback.

Example:

 A restaurant: It takes orders from customers (input), cooks the food (process), and serves
meals (output). It reacts to customers’ feedback.
  An e-commerce website like Amazon is an open system – it interacts with users, takes
orders, and delivers products.

 Closed System

 A closed system does not interact much with the outside world.
 It works on its own without being affected by what’s happening outside.
 These are rare in real life.

Example:

 A watch (the mechanical kind) can work without needing any outside input.
 A sealed chemistry experiment in a lab can be a closed system.

3. Deterministic System vs. Probabilistic System

 Deterministic System

 This type of system gives the same result every time you use it with the same input.
 It is predictable and follows a set of rules.

Example:

 A calculator is deterministic – 2 + 2 will always be 4.

 A traffic light system changes lights in a fixed pattern.

 Probabilistic System

 This system involves chance or uncertainty.

 The same input can give different results.
 It cannot be predicted exactly.

Example:

 Weather forecasting – Even with lots of data, we can’t always say for sure what the
weather will be.
 The stock market – Prices go up and down based on many unknown factors.

4. Man-made System vs. Natural System

 Man-made System

 These are designed and built by humans to do a specific job.

 They are artificial systems.
 Example:

 A railway system: Built by engineers to move people.

 A banking system: Created to handle money and transactions.

 Natural System

 These systems occur naturally in the environment.

 Humans do not create them.

Example:

 The solar system with the sun and planets.

 The human body is a natural system with organs working together to keep you alive.

5. Permanent System vs. Temporary System

 Permanent System

 These are meant to last for a long time.

 They keep working unless they are replaced.

Example:

 A hospital information system: It's always needed and used daily.

 The education system in a country.

 Temporary System

 These are used for a short time.

 They are often created for special events or tasks.

Example:

 A system used to manage a music concert.

 A COVID-19 vaccination appointment system that was used during the pandemic and
then removed.

6. Social System, Human-Machine System, and Machine System

 Social System

 Made up of people working together.

 It depends on communication and relationships.
 Example:

 A school – students, teachers, and staff interact to provide education.

 A company where employees work together to achieve business goals.

 Human-Machine System

 Combines humans and machines to complete a task.

 The machine helps, but humans are still involved.

Example:

 A car – the driver (human) controls the machine.

 ATM machines – people use them to withdraw money.

 Machine System

 A system where machines do everything automatically.

 No human help is needed during operation.

Example:

 A robotic assembly line in a car factory.

 A dishwasher that washes dishes automatically once started.

7. Information Systems (Special Category)

These systems are used to manage data and information in businesses or organizations.

 Transaction Processing System (TPS)

 Handles day-to-day transactions like buying or selling.

Example:

 A billing system in a supermarket.

 Management Information System (MIS)

 Helps managers make decisions by giving them reports and summaries.

Example:

 A system that shows monthly sales reports.

 Decision Support System (DSS)

 Helps with complex decisions by analyzing data.

 Example:

 A system that helps a manager choose the best supplier based on cost and reliability.

 Expert System

 Uses Artificial Intelligence (AI) to act like a human expert in a specific field.

Example:

 A medical diagnosis system that suggests possible illnesses based on symptoms.

✅ Summary
Type Description Example

Physical Real, touchable things Car, computer

Abstract Conceptual, invisible Plan, formula

Open Interacts with outside Restaurant, website

Closed Self-contained Watch, lab experiment

Deterministic Predictable Calculator

Probabilistic Unpredictable Stock market

Man-made Created by people Banking system

Natural Found in nature Solar system

Permanent Long-term Hospital system

Temporary Short-term Concert ticket system

Social People-based School

Human-Machine People and machines Driving a car

Machine Fully automatic Robot arm

Information Systems For managing data TPS, MIS, DSS, Expert System
Different System Behavior

System behavior refers to how a system responds to inputs, events, or changes in its environment.
It helps us understand how the system works in real life — how it reacts to users, to other systems, or
to changing conditions.

When analyzing and designing a system, it's important to know how the system behaves so we can
build it to meet user needs, handle different situations, and work efficiently.

Let’s explore the different types of system behavior in detail:

1. Reactive Behavior

A system with reactive behavior waits for something to happen (an event or input) and then
responds to it.

Simple Example:

 A fire alarm is a reactive system. It stays quiet until it detects smoke. When smoke is
detected, it starts ringing.
 Another example is an ATM machine — it waits for you to insert your card, then reacts by
showing you options.

Why it's important:

Reactive systems are designed to be responsive and only act when needed, which saves energy and
resources.

2. Proactive Behavior

A system with proactive behavior acts ahead of time. It tries to prevent problems or prepare for
future conditions.

Simple Example:

 A weather app sends you a rain alert before it starts raining. It uses forecast data to warn you
in advance.
 Antivirus software that scans your system regularly to catch threats before they harm your
files.

Why it's important:

Proactive systems are smart and preventive. They help avoid problems before they happen and
improve user experience.
3. Deterministic Behavior

A deterministic system is predictable. It always gives the same result for the same input. There's
no randomness involved.

Simple Example:

 A calculator is deterministic. 2 + 2 will always equal 4, no matter how many times you try.
 An online booking system that gives you the same ticket price for the same inputs every time.

Why it's important:

Deterministic behavior makes the system reliable and easy to test. It’s important in banking, billing,
and other critical systems where consistency is necessary.

4. Non-Deterministic Behavior

In contrast to deterministic systems, non-deterministic systems can behave differently for the
same input. This happens when the system involves random choices or external factors.

Simple Example:

 A traffic signal that changes based on live traffic data may behave differently at the same
time on different days.
 A computer game that has different outcomes every time you play, even if you make the
same moves.

Why it's important:

Non-deterministic systems are flexible and handle real-world situations better, especially where
exact outcomes can't always be predicted.

5. Adaptive Behavior

Adaptive systems can learn from experience or adjust themselves based on how they are used or
changes in the environment.

Simple Example:

 A smart thermostat learns your temperature preferences and adjusts heating/cooling

accordingly.
 A music streaming app like Spotify that suggests new songs based on what you’ve been
listening to.
Why it's important:

Adaptive systems provide a personalized experience and can improve themselves over time,
making them smarter and more useful.

6. Interactive Behavior

Interactive systems engage with users or other systems. They exchange information back and forth,
allowing communication and cooperation.

Simple Example:

 A chatbot that answers your questions on a shopping website.

 A video conferencing app like Zoom that lets multiple people communicate in real-time.

Why it's important:

Interactive systems are designed to support communication and are essential in customer service,
education, and collaborative tools.

7. Autonomous Behavior

Autonomous systems can make decisions and act on their own without needing help from humans
or other systems.

Simple Example:

 A self-driving car that drives itself, follows traffic rules, and makes turns without human
control.
 A robotic vacuum cleaner that moves around your house, avoids obstacles, and charges itself.

Why it's important:

Autonomous systems help reduce human effort and can work in situations where human presence is
hard or dangerous (e.g., space exploration, deep-sea research).

🧠 Summary
Type of Behavior What It Means Real-Life Example

Reactive Responds to events or actions Fire alarm, ATM machine

Proactive Takes action in advance to avoid problems Weather app, antivirus software
Type of Behavior What It Means Real-Life Example

Always gives the same output for the same

Deterministic Calculator, fixed-price ticket system
input

Non- Output may vary due to random or unknown Smart traffic light, game with random
Deterministic factors events

Learns and changes based on use or Smart thermostat, music recommendation

Adaptive
environment app

Interactive Communicates with users or systems Chatbot, Zoom app

Autonomous Works independently without human help Self-driving car, robotic vacuum

What is the System Approach?

The system approach means looking at the “whole picture” rather than focusing only on one part.
It helps us understand how all parts of a system are connected and how they affect each other.

Instead of solving a problem by only fixing one piece, the system approach looks at how every part
interacts, so we can find a complete and long-term solution.

Why Do We Need a System Approach?

✅ 1. Solves Complex Problems

Many problems today (like managing a hospital or running a company) are complicated. We need to
look at the entire system to find smart solutions.

✅ 2. Better Planning and Decision Making

The system approach helps in making better decisions because it shows how changing one part
affects the others.

✅ 3. Avoids Blame Game

Instead of blaming one person or one part, the system approach helps understand the root cause of
the problem.

✅ 4. Improves Efficiency

When all parts of a system work well together, things get done faster and with less waste.
✅ 5. Useful in All Fields

The system approach is used in business, education, engineering, healthcare, and even
government to create better services and systems.

Real-Life Example: A School

Let’s say students are getting low marks.

Without the system approach, someone might blame only the teachers.
But with the system approach, we look at the whole system:

 Are the books good?

 Is the timetable okay?
 Are students getting enough support?
 Is there a distraction at home?
 Are the exams fair?

By checking all parts of the system, we find better, long-lasting solutions.

What is Factoring into Subsystems?

Factoring into subsystems means dividing a big system into smaller, logical parts, where each part
is responsible for doing a specific task. These smaller parts are called subsystems. The idea is to
make the big system easier to understand, develop, test, maintain, and improve by working with
smaller pieces instead of one large, complicated system.

Just like when building a house, you don’t build the entire house all at once — you build the
foundation, then the walls, then the roof, plumbing, electrical wiring, and so on. Each of these is like
a "subsystem" of the house.

Why Do We Use Subsystems?

In software development or system design, large systems are often too complex to deal with as one
whole unit. Trying to design or build the entire system at once can lead to confusion, mistakes, and
delays.

To solve this problem, we break the system into subsystems, so that each part focuses on one area
of responsibility. This helps in many ways:

1. Better Understanding

Small parts are easier to understand. When you look at one subsystem, you can focus only on that
part without being distracted by the rest of the system.
2. Easier Development

Different teams or individuals can work on different subsystems at the same time. This saves time
and makes teamwork more efficient.

3. Easier Testing and Debugging

You can test each subsystem on its own before combining them. If there’s an error, it's easier to find
and fix it in a small part than in a large system.

4. Reusability

Some subsystems can be reused in other projects. For example, a "Login System" designed for one
website could be used for another with little change.

5. Flexibility and Maintenance

When the system needs updates or improvements, it's easier to make changes to one part without
affecting the whole system.

How to Factor a System into Subsystems?

Here’s how you typically break down a system Into subsystems:

Step 1: Understand the Whole System

First, analyze what the system is supposed to do. Identify all the main tasks or services it must
provide.

Step 2: Group Related Tasks

Next, put related functions together into groups. Each group should represent a major function or
area of responsibility.

Step 3: Define Subsystems

Give each group a name and treat it as a subsystem. Each subsystem should be able to do its job
mostly on its own, but also communicate with other subsystems.

Step 4: Design Interfaces

Decide how the subsystems will communicate with each other. This is usually done using interfaces
— clearly defined ways for sending and receiving information between subsystems.

Example: Online Shopping System

Let’s say we are designing an Online Shopping System. The system is big and has many features,
so we break it into subsystems like:

 Product Catalog Subsystem

Handles product listings, categories, product details.
 User Account Subsystem
Manages user registration, login, profiles.
 Shopping Cart Subsystem
Lets users add, remove, or update items in their cart.
 Payment Subsystem
Processes payments using credit cards, wallets, etc.
 Order Management Subsystem
Handles order processing, shipping, delivery status.

Each of these subsystems works on a specific part of the overall system. They may interact with each
other, but each one focuses on its own job.

Black Box System

In system analysis and design, a Black Box System is a way of looking at a system from the outside
only. This means we focus only on:

 What goes into the system (inputs)

 What comes out of the system (outputs)

But we do not look at or worry about what happens inside the system — that is, how the inputs
are processed to produce the outputs is hidden or unknown. It's like a "closed box" where we can’t
see the inner workings.

That's why it's called a “black box” — the inside is invisible, like it's in darkness.

Why Use the Black Box Approach?

The black box approach is especially useful during the early stages of system analysis, when we are
trying to understand:

 What the system is supposed to do

 What data or actions it needs to perform
 What results it should give back

By ignoring how the system works internally (which can be complex), we can focus on what the
system must do from a user’s point of view. This makes things simpler, clearer, and easier to
communicate.
🔁 Inputs and Outputs: The Core Idea

Let’s say you’re designing a simple calculator app. If we treat the calculator as a black box:

 Input: Two numbers and a selected operation (like add or subtract)

 Output: The result of the calculation

We don’t care how it does the calculation inside — whether it uses addition formulas, programming
logic, or mathematical libraries. We just care that if we give it 2 + 3, it gives back 5.

How the Black Box Helps in System Design

Here’s how the black box idea is used during system design:

1. Focus on What the User Wants

Users don’t care about how the system works behind the scenes. They just want to know what
they need to input and what output they will get. The black box model helps us design the
system from the user’s perspective.
2. Helps Define System Requirements
Before building the system, we need to know what it should do. By using a black box
approach, we define those requirements in terms of input and output, which is easier to
understand.
3. Avoids Unnecessary Details
At the start, we don’t need to get into how the system will work internally. That can come
later. The black box model keeps things simple.

Real-Life Examples of Black Box Systems

✅ Example 1: ATM Machine

 Input: Card inserted, PIN entered, withdrawal amount selected

 Output: Cash dispensed, receipt printed, balance updated

We don’t know or care how the machine checks the PIN or connects to the bank. We only care that
if we do these steps, we get our money.

✅ Example 2: Vending Machine

 Input: Insert money, select item (e.g., B3)

 Output: Item drops, change returned

We don’t need to know how the machine works inside. We just use it based on what we put in and
what we get out.

✅ Example 3: Search Engine

 Input: A search query (like “weather today”)

 Output: A list of search results
You don’t know how Google finds those results — that part is a black box.

What Happens Inside the Black Box?

In the black box model, the internal processes — like algorithms, logic, data processing — are not
shown. These are handled by developers and designers later when we move to a more detailed stage
of design or development. That stage is sometimes called the “white box” approach, where we
actually look inside the system.

But during the black box phase, we simply define:

 What the system gets (input)

 What it returns (output)
 What it’s supposed to do — without talking about how

Benefits of Using Black Box in System Analysis

1. Clarity and Simplicity

Everyone can understand it — even people without technical knowledge.
2. Focus on System Behavior
Helps define the "what" before worrying about the "how."
3. Easier Communication with Users and Stakeholders
Users don’t care how things work inside; they just care what the system does for them.
4. Improves Planning and Requirement Gathering
By focusing on input and output, analysts can gather clear and specific requirements from
users.
5. Supports Modular Design
You can design systems in blocks or modules where each one works like a black box —
making the whole system easier to build and manage.
Assignment:-
1. Define a system. Give two real-life examples of systems.
2. Explain types of system with example.
3. Explain the system concept and discuss the importance of a system approach in solving
complex problems.
4. What is factoring into subsystems? Explain its purpose and give a suitable example from a
real-world application.
5. Discuss the different behaviors of a system. Explain static vs dynamic, deterministic vs
probabilistic, and adaptive vs non-adaptive systems with examples.
6. Describe the concept of a black box system. How is it useful in system analysis and design?
7. Explain the basic elements of a system in detail. How do they interact with each other?